Six Stages of an RPA Implementation

Ⅰ. Prepare RPA

➽ The processes are defined, assessed, prioritized and the implementation is planned.

Ⅱ. Solution Design

➽ Each process to be automated is documented ("as is" and "to be"), the architecture is created and reviewed,
the test scenarios and environments are prepared and the solution design is created and documented for each process.

Ⅲ. Build RPA

➽ The processes are automated, the workflow is tested and validated and the UAT prepared.

Ⅳ. Test RPA

➽ The UAT is performed, the workflow is debugged and the process is signed off.

Ⅴ. Stabilize RPA

➽ The Go-Live is prepared, the process is moved to production, monitored, measured and the lessons learned are documented.

Ⅵ. Constant Improvement

➽ The process automation performance is assessed, the benefits tracked and the changes managed.




Following are some of the roles encountered in RPA implementations that drive the change

Ⅰ. Solution Architect

➽ Is in charge of defining the Architecture of the RPA solution.
The Solution Architect translates the requirements captured by the functional analysts, creating the architecture and design artifacts.
They lead, advises, and is responsible for the developers' team delivery.

Ⅱ. Business Analyst

➽ Is responsible for mapping of the AS IS and proposed TO BE processes.
Business Analysts hold knowledge of the business process that gets automated, general business process theory and RPA capabilities.
They are responsible with listing the process requirements for automation, clarifying the inputs and expected outputs,
creating RPA documentation (Process Design Documents, Process maps.

Ⅲ. Implementation Manager or Project Manager

➽ Forms and manages the RPA team, does resource planning and teams availability, in order to hit automation goals.
Most of the times the PM is the Single Point of Contact (SPOC) for questions, RPA initiatives, or parallel RPA product projects.

Ⅳ. Infrastructure & IT Security admin

➽ With good technical and security skills, they are responsible for setting up and maintaining hardware &
software resources for UiPath product installations. They set up accounts for all the devs, end users and robots.

Ⅴ. Process Owner

➽ Is the key stakeholder and beneficiaries of the RPA solution.
Usually Senior Management level, with some 10-15+ years of experience, possibly split across domains.
Multiple people can have this role, based on department (Finance, IT, HR, etc).

Ⅵ. RPA Support

➽ Manage the robots after the processes have been moved to production,
with support from the original RPA devs who have performed the automation.
May have multiple levels of support: L1- Client, L2- client/ partner, (L0 – Super users; L3 – UiPath)

Note:- I will be updating this blog frequently.✍

Thank you for visiting this blog☕️

“Learn this from water: loud splashes the brook but the oceans depth are calm”