What is an RPA CoE? Session 4 – CoE Scaling

How to scale a COE to meet organizational missions.

Topics covered:

• What is the original focal area?

• How to expand the COE globally.

• Is a centralized or decentralized model better for scaling?

Speaker:

Chris Bolin, Senior Intelligent Automation Architect Anika Systems

1. Standing up a COE

2. Scaling

3. 3
1.Session 1 –Vision
2.Session 2 –Roles
3.Session 3 –Environment
4.Session 4 –Scaling
Agenda Slide

4. 4
Systems–
“Growth is never by mere chance; it is the result of forces working
together.”

5. 5
Organization Model and Strategy
As the COE and steering committee work together to prioritize pipelines and
deliver automations, the strategy of the COE and the organization’s adoption of
RPA should evolve.
•A Model to scale is identified
•Divisional
•Will each business unit have its own RPA COE based upon adoption, change
management and opportunity identification?
•Federated
•Central platform with standards with each business unit delivering RPA themselves
with the guidance of the COE.
•Centralized
•All functions are performed by the COE with global standards.
•Downside is prioritization of the pipeline –some business units may wait a period of
time before being considered.
•Process Mining tools or other method to build a robust pipeline are
incorporated.
•Citizen Development
•Growth Roadmap
•Invest in onboarding talent to fit roadmap
Continuous Growth

6. 6
Governance
•Development Standards
•Code Reviews
•Code Libraries
•Decision making
•Change Control and approvals
•Normal –changes the business process –approval needed
•Standard –does not change the business process –no approval needed
•Emergency –typically system centric –no approval needed
•How effective are the out-of-the-box PDD or SDD –do they need to be unique
to the organization, provide more detail, etc.
•Transform from Change Reactive organization to a Change Proactive
organization.
Controlling the RPA
Program

7. 7
Processes, Metrics, KPI, ROI and Monitoring
•Optimize Processes before applying RPA
•Obtain a credible baseline for As-is cost, FTE involvement, etc
•Use UiPath Insights, Tableau or another solution to provide rich analytics that easily
inform and allow for pro-active decision making
•Process complexity
•Systems and Applications involved
•Run time
•Transaction volume
•Maintenance vs. development ratio
•Business value lost during downtimes
•Break-even on cost of RPA implementation for a solution vs. manual process
•Rework
Return on Robot
Investment