ROM2 Strategy : Introduction

1. Introduction to the Roboting Operating Model(ROM2) 

 

- Operating Model은 Hybrid Workforce를 제공해야 함

 

 

 

2. ROM2 Foundations

 

 

 

 

 

3. ROM2 Workflow

 

 

Plnning  - The Purpose of this phase is for a project team or steering committee to review all potential RPA opportunities. These would then need to be approved and prioritized for progression to the next phase. It is critical that all dependent stakeholdes are engaged. 

 

Defining - The Define phase involves looking at the 'as-is' process and working out the scope, requirements and succes criteria for the automation. 

 

Desining - Here a design to satisfy their requirements is presented to the client. The automation scope and success critera are agreed, the design is apporved, and development and test plans are signed off. 

 

Builing - The development team build the automation accoring to the designer's instructions. Best practice recommends an incremental delivery where building and testing are done iteratively. 

 

Test Phase - Testing done by the delivery team to check their development work is ready to be handed over to the Business for acceptance testing. 

 

UAT- The purpose of User Acceptance Testing is to prove the automation is ready to be released into the production enviroment. Business users check the automation fuilfuils the scope, satisfies the requirements and meets the performance and success criteria agreed in the Define and Design phases. 

 

Deploy Phase - Here the automation enters production and is gradually rolled out over an agreed period. Once deployed to full sacle, Business as Usual(BAU) operation of the automation can commence, using the Control Room to effectively manage the digital workfoce. 

 

 

 

4. ROM2 Maturity Model