Book Image

RPA Solution Architect's Handbook

By : Sachin Sahgal
Book Image

RPA Solution Architect's Handbook

By: Sachin Sahgal

Overview of this book

RPA solution architects play an important role in the automation journey and initiatives within the organization. However, the implementation process is quite complex and daunting at times. RPA Solution Architect’s Handbook is a playbook for solution architects looking to build well-designed and scalable RPA solutions. You’ll begin by understanding the different roles, responsibilities, and interactions between cross-functional teams. Then, you’ll learn about the pillars of a good design: stability, maintainability, scalability, and resilience, helping you develop a process design document, solution design document, SIT/UAT scripts, and wireframes. You’ll also learn how to design reusable components for faster, cheaper, and better RPA implementation, and design and develop best practices for module decoupling, handling garbage collection, and exception handling. At the end of the book, you’ll explore the concepts of privacy, security, reporting automated processes, analytics, and taking preventive action to keep the bots healthy. By the end of this book, you’ll be well equipped to undertake a complete RPA process from design to implementation efficiently.
Table of Contents (25 chapters)
1
Part 1:Role of a Solution Architect
5
Part 2:Being Techno/Functional
11
Part 3: Tool Agnostic Approach
17
Part 4:Best Practices
22
Epilogue

Contribution to presales activities

SAs' responsibilities are divided into two groups: business as usual (BAU) and ad hoc contribution requests. BAU activities are defined and listed in the job description and are related to the given project. These activities generate revenue for the company and are called billable activities. It can also be said that these are the primary activities of an SA.

Then comes activities that are ad hoc in nature and can be added to an SA’s to-do list as and when required. These activities are not revenue-generating but will require a significant amount of the SA’s time. You might wonder why an SA should invest their time in a non-revenue-generating activity. In a real-world scenario, contributing to a project is one part of an SA's role, while keeping a healthy project pipeline is the other part.

Imagine a scenario where you are almost at the delivery end of a project. The go-live date is set for the next week. Now, you can...