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

When to consider hyper-automation

As we saw, hyper-automation is an amalgamation of technologies. When an organization needs to automate complex processes that involve RPA, ML, advanced analytics, BPMS, and iPaaS, then hyper-automation should be considered. Hyper-automation helps in business process optimization and helps businesses to automate processes that are spread across business units, geo-locations, and continents.

Let’s understand this using an example. Assume that your banking client has a central email inbox that receives emails of all types, such as those related to appeals, grievances, complaints, accolades, marketing, requests, and accounts; the list goes on. Now, on average, this main inbox receives anywhere from around 3,000 to 12,000 emails per day. A team of six full-time resources works on reading each of these emails and categorizing or forwarding them to their respective mailboxes for further review based on the intent and sentiments of the email, if...