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)
Part 1:Role of a Solution Architect
Part 2:Being Techno/Functional
Part 3: Tool Agnostic Approach
Part 4:Best Practices

Benefits of reusable components

An IT service organization can reduce the risk of problems and save time and money by managing process templates and investing in reusable components. Whether we code or not, reusing information, templates, and components effectively can save costs and reduce the chance of making mistakes due to errors in the code. It also follows the principle of not reinventing the wheel. A perfect example of this is RPA. A system can’t be blamed for making a mistake or giving out misinformation when it is following an already-set-out prewritten plan. If a procedure being followed doesn’t have to be designed specifically for one company, organization, department, or LOB, then it’s worth implementing reusable components or templates rather than having IT do it again and again for the same reasons.

Suppose you have a few RPA projects that you know will have similar data extraction requirements from Portable Document Format (PDF) files. One common...