Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
RPA Solution Architect's Handbook

You're reading from   RPA Solution Architect's Handbook Design modern and custom RPA solutions for digital innovation

Arrow left icon
Product type Paperback
Published in Jun 2023
Publisher Packt
ISBN-13 9781803249605
Length 302 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Sachin Sahgal Sachin Sahgal
Author Profile Icon Sachin Sahgal
Sachin Sahgal
Arrow right icon
View More author details
Toc

Table of Contents (25) Chapters Close

Preface 1. Part 1:Role of a Solution Architect
2. Chapter 1: Why Do We Need a Solution Architect? FREE CHAPTER 3. Chapter 2: Case Study of a Banking Client 4. Chapter 3: Extracurricular Activities 5. Part 2:Being Techno/Functional
6. Chapter 4: Studying the Lay of the Land 7. Chapter 5: Designing Framework for Consistency and Resiliency 8. Chapter 6: Need for Documentation and Working with SIT/UAT Scripts 9. Chapter 7: RPA Development Phases 10. Chapter 8: Customer Obsession in the RPA Journey 11. Part 3: Tool Agnostic Approach
12. Chapter 9: Intelligent Automation 13. Chapter 10: Hyperautomation: The Future of RPA 14. Chapter 11: Reusable Components 15. Chapter 12: RPA as a Service (RPAaaS) 16. Chapter 13: Finding the Best Solution 17. Part 4:Best Practices
18. Chapter 14: Design Best Practices 19. Chapter 15: Data, Security, and Logs 20. Chapter 16: Key Performance Indicators (KPIs) 21. Chapter 17: Reporting, Analytics, Efficiency, and Efficacy 22. Epilogue
23. Index 24. Other Books You May Enjoy

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image