2. 2
Ruchir Mahajan
RPA POD Lead
Profile Summary
Ruchir has 8+ years of IT experience with more than 5 years of
experience in RPA technology with end-to-end RPA UiPath lifecycle.
Passionate about mentoring the community to upskill on
Automation/RPA/UiPath
Globant Experience
● Has been working with Globant since May 2022
● Led the implementation (Power automate, PowerBI) and won
the RPA hackathon 2022 from Rockwell Automation
● Contributed to multiple clients in automating their business
process.
Past Experience
● AtoS India, Capita India, Fulcrum Digital
Career Highlights
● Involved into end to end RPA lifecycle activities to help
multiple clients to automate their processes
● Delivered guest lectures in multiple engineering colleges
to introduce RPA/UiPath and demonstrated respective use
cases
● Assisted more than 350 individuals to start their RPA
UiPath journey
● Contributes in the community space in different forms
● Chapter Lead for UiPath Pune Community
3. 3
Gajanan Patil
Automation Tech Lead
Profile Summary
Gajanan has around 8+ years of IT experience with more than 4.5
years of experience in RPA technology with end-to-end RPA UiPath
lifecycle. Passionate about mentoring the community to upskill on
Automation/RPA/UiPath
Accelirate Experience
● Has been working with Accelirate since Dec 2019
● Led the implementation (Workato - Best practices | Power
Automate and integrations
● Mentoring Juniors
● Contributed to multiple clients in automating their business
process.
Past Experience
● Atos
Career Highlights
● Involved into end to end RPA lifecycle activities to help
multiple clients to automate their processes
● Speaker for 2021 and 2022 for various RPA products such
as UiPath Apps and Document Understanding
● Assisted more than 3000 studends and 300+ Faculties to
start their RPA UiPath journey – Initiative Tamil Nadu
Government Program Naam Mudhavan
● Contributes in the community space in different forms
● Chapter Lead for UiPath Pune Community
● Upcoming Pune Event 14th May 2022 UiPath Apps and
Integration Services
4. 4
Sripad Mhaddalkar
Solution Architect - Reckitt
Profile Summary
Process Automation Technologies Practitioner | SAFe POPM | ITIL |
Agile Enthusiast | Practicing Digital & Service Transformation with
BOTs
Talks about RPA, UiPath, Automation, Process Automation, and
Intelligent Automation
Reckitt Experience
● Has been working with Reckitt since April 2021
● Setup the IT COE Ops
● Delivered 20 % of Automation across the IT enterprise { Fully
Automation }
Past Experience
● 3 Startups – RPA Delivery Head
● Sharaf DG
● DXC Technologies
● Tech Mahindra
● Wipro
Career Highlights
UiPath Excellence Award – IT Operations Excellence 2022
3 * UiPath Hackathon Winner
Partner Award – Automation Anywhere – 2021 / 2020
5. 5
“As has been said elsewhere the architect is the
interface between the business and the technology
team, the architect must understand every aspect
of the technology to be able to represent the team
to the business without having to constantly refer
others. Similarly, the architect must understand the
business in order to drive the team toward their
goal of serving the business.”
― Richard Monson-Haefel, 97 Things Every Software Architect Should Know: Collective
Wisdom from the Experts
6. 6
Role Of a Solution
Architect
Defines the architecture
Oversees End to End Lifecycle,
supports both development and
implementation phases.
Selects the appropriate set of
technology { tools and features }
Makes sure the solution aligns
with enterprise guidelines. { PI, Cyber,
Architecture and Compliance }
7. 7
Discovery &
Kick off
Development &
Unit Testing
Solution Design
Process
Analysis
Deployment &
Hypercare
Integration &
UAT
Solution Architect
Solution Architect Solution Architect
Solution Architect Solution Architect
Solution Architect
Project Manager Project Manager
Project Manager Project Manager
Project Manager
Business Analyst Developer
Business Analyst Developer
Developer
Project Manager
Automation Lifecycle
8. 8
• Make sure :
• Input data processing and filtering, as well as the exception handling is
represented by rule-based logic.
• A check of the applications used in the process.
• Run Few steps to make sure the Ui Automation steps are properly
documented.
• Ensure Steps that aren't feasible/suited for Automation are called off
explicitly.
• Required Reporting is in place and will be build via Automation as an output.
Requirement Gathering + Preparation Stage
– Works Closely with Business Analyst and Business Teams
Review and Sign off the Process & Solution Design Document
Step-by-step guide, Input data samples, Diagrams, etc.in PDD and SDD should
provide enough information so that the process can be fully understood with no
other context.
9. 9
Prerequisites Missing
• Lack of documentation, automation branches, licenses,
environment, applications
Solution Architect’s – No Good Friend’s
Logic Missing
If an input file is necessary
to be downloaded or not
Uploading data on every
BOT run in the ERP
Unsuitable for
automation
Processing of
Unstructured Data
No exceptions listed
for the process
Undocumented
Decision
Process Maps detail the
Yes branch, and No
branch is always Grey.
Ambiguities in the step-by-step document
• Missing screenshot from the applications or templates. Test applications in
scope to discover potential challenges or improvements
10. 10
The workflow development, Orchestrator configurations, and dashboard builds
are included in the estimation.
Collaborate with DEV Team to test :
• Integrations between applications
• Simulate certain selectors in UI Explorer {if doing a GUI automation }
• Access across the apps and infra for the process
Consider the Estimation Timelines with below :
• The complexity of the applications and business rules when handling exceptions.
• The skill level of developers
• Unit and functional testing
Additional time should be considered—typically 30% or more for :
• Change Requests post PDD sign off
• Change requests in Hyper care delivery
• UAT leading to new change requests
Dev Effort Estimation
– Works Closely with Business Analyst, Project Manager and DEV team
11. 11
Build
Recommend & Build
- Consistent standards
Regular code,
documentation reviews
Recurrent status meetings
- Business Stakeholders & Internal
COE Team
Provide constructive
feedback on the spot
Guide Developers in
finding the best solution
Being Approachable, Available
& Encourage Teamwork
12. 12
Design – Push for build & use of Reusable
Components
Linking these layers can create issues with
maintainability and the reusability of the code.
A layer which is used to extract and input data into the
application.
A which contains all the data validation,
processing and any other logical
instructions needed for the process flow
13. 13
Design – Push for build & use of Reusable
Components
Data Service Activities Object Repository
Object Repository : Helps in reusing UI interaction. Ensures the management, reusability and reliability
of UI elements by capturing them in a DOM-like repository, sharable across projects.
Projects will have a better reusability in terms of UI interactions, it will be easier to :
• Capture not only classic selectors
• Descriptors
• UI structure of the application and
• To upgrade processes to a new version of the same application.
14. 14
Design Solution Architect strives to achieve modularization, maintainability,
reusability, scalability of the code and overall project.
Benefits of Reusable components methodology :
• One could build only one layer without interfering with the other one
• Reusing already existing code, without the need for it to be rewritten each time when it is
used
• This methodology makes it easier to change the UI Interaction when an update in the
application occurs and to push the change to all the processes using the library without
having to republish them
• Sharing the UI Interaction Layer between multiple processes means that the same module is
tested more thoroughly and that any fixes can for all processes at once, resulting in very
robust and reliable automations
• Having a dedicated GUI Interaction library makes it very easy to build dedicated Test
Automation Projects for testing the Ui automation for a specific application
15. 15
Design - Integrations
Look for integrations between the applications you automate via REST APIs, SOAP APIs, ODBC, and
more.
Why Integrations :
Ease of use: Often you get connectors which are pre-built and ready to use, saved writing any custom
code. If not, we connect with App Team and incorporate the API’s
Flexibility: Makes it easy to connect virtually any external system or application
Customizability: Connectors prebuilt or built can be customized to meet specific business requirements,
allowing users to tailor their integrations to meet their unique needs.
Security: Connectors are designed with security in mind, ensuring that data is transferred securely
between systems
Avoid traditional issues – GUI broken, Unavailable, Latent and issues with presentation layer
Application Upgrades do not have a major impact if integrations are in place, since we are not dependent
on GUI
16. 16
Design - Integrations
Food for thought
UiPath Integration Service is a
powerful platform that allows
organizations to seamlessly integrate
their disparate systems and
applications.
With its wide range of connectors,
triggers, and workflow designer,
Integration Service enables users to
automate their workflows, eliminate
manual tasks, and streamline their
operations.
The platform's user-friendly interface
and drag-and-drop functionality make
it easy for users to create and deploy
integrations, even if they have little or
no coding experience.
17. 17
Workflow Analyzer uses a set of rules to check for various inconsistencies
unrelated to project execution.
The rules are based on Automation Best Practices and consider variable and
argument naming, empty sequences or workflows, package restrictions, and
so on
It's available in the Design ribbon tab, on the Analyze File and Analyze Project
buttons
The analyzer doesn't identify errors in execution or compilation
The first performs an analysis on the file currently focused in the Designer
panel, while the second analyzes all files in the automation project.
Workflow Analyzer – Tool as a Boon
18. 18
Hypercare Continuous Improvement
• Make sure that no unhandled
exceptions occur during process
execution.
• Use analytics through different reports,
like Orchestrator dashboard, to verify
that from a technical standpoint
everything is working as expected.
• Look into Orchestrator to see if the
jobs execution was successful, look
through the logs, and look over any
other project-specific output files
outside Orchestrator.
• Document any changes in the DSD or
PDD.
• Perform the handover to the
Operations team.
• Support the team in understanding
what the process is and how to
manage it correctly.
Continuous Improvement
19. 19
RPA Solution Architecture definition
Overseeing the end-to-end performance of the agreed solution
Automation process optimization
Effort estimation
Code review
Workflow component and reusable definition
PDD and DSD sign-off
Number of robots used, config file, asset, queue, and schedule definition
Logging and Reporting dashboards
Responsibilities
20. 20
How to become a Solution Architect
RPA Solution
Architect
Course
Dev Ops
Practices
IT
Architecture
Know How
Know How of
the Business
and Tools
Know How of
Automation
Tools in the
enterprise
RPA
Business
Analyst
Foundation
RPA Starter
Course
Hands on Experience, Failures and lots of Learnings
21. 21
“Usually, now with the benefit of hindsight, the best
solution to the problem is apparent to everybody.
The architect does not have to make the decision,
he or she merely orchestrates the decision-making
process.”
― Richard Monson-Haefel, 97 Things Every Software
Architect Should Know: Collective Wisdom from the
Experts
22. 22
Principal Team – A Big Thank You
Tag us in your Post on LinkedIn with your
Key take away’s from this session.
Looking forward to interact
