Dry goods丨4 stages of RPA process automation and 4 important reference points in implementation
RPA implementation usually does not involve the adjustment of the company’s existing IT architecture, but most of the existing RPA platforms and platforms are not compatible with each other. Therefore, once a platform is selected, as the application scenarios running on it increase, it may be in the future. It is difficult to migrate platforms in a relatively long period of time. Therefore, when selecting platforms, it is necessary to comprehensively consider the advantages and disadvantages of their respective platforms, and fully compare user ease of use, system integration, and platform charging models.
Once the RPA platform is determined, the enterprise needs to face all kinds of RPA requirements. Therefore, good requirements and implementation management are equally important.
The implementation of process automation on a clear RPA platform is mostly scenario-based, relatively short process process node optimization. The overall goal is to eliminate business steps that require extensive manual processing but clear logic in the process.
However, whether its improvement needs match the RPA platform requires certain evaluations, such as estimated benefits, estimated RPA initial investment, etc., and enters the design and implementation links after confirmation. The implementation of most lightweight RPA scenarios can ensure that the design is completed within a week And landing, and then combined with the improvement of operational feedback.
The 4 stages of RPA process automation
Most organizations will go through four stages in the process of successfully expanding automation. When a company's automation project passes these stages, the executive sponsor, the source of the automation pipeline, and the rationality of funding will all change. The scope of the automated business model will also mature.
1: Verification phase
In the verification phase, the initial process determined for automation begins to prove the automation technology and seek sponsors for this value. Typically, this is done in a department with fewer than 10 software robots, because the initial process is designed to ensure that RPA "works properly" in its specific environment. Some organizations may take up to three months at this stage, while others need to conduct pilots faster (sometimes several weeks).
2: The establishment phase
In this phase, the focus is on the production and delivery of multiple processes, usually within a single business unit. This phase may take 3-6 months. If the automation awareness of a business unit is restricted, then the entire business unit may face the risk of business stagnation. In addition, if the leader of the business unit does not set up and require the organization to be responsible for discovering and delivering impressive business results with automated functions, it is difficult to demonstrate its potential.
The automated operation model of each organization will be iterated to deal with key elements in the correct way, such as organizational structure, acceptance strategy, governance, risk control, and change management.
3: Expansion phase In
this phase, the automated operation model has been fully defined and a standardized method is provided for additional business units. This phase can last one to three years, because the full benefits of RPA are understood at the top, and multiple business units begin to automate on a large scale. During the expansion phase, key performance indicators (KPIs) are well defined and measured.
Given that the developers of the Center of Excellence (CoE) will focus on high ROI opportunities, it is clear that to solve many simple, team-level and personalized automation opportunities, organizations must: Improve employee skills. Technicians include helping some employees become citizens and developers to build automation for their teams, departments or themselves.
4:
At this stage, CoE can use a combination of technologies to produce complex automation products to meet the customer needs of the entire organization. Developers are providing bottom-up, employee-led task automation and simpler processes. In the scale phase, the executive sponsor is the CEO or CFO, and RPA is now the backbone of the overall digital transformation plan.
Important reference point in the implementation of RPA
In addition, there are some important reference points in the RPA implementation process.
1. Pilot-type RPA projects (within 3 processes, generally called "quick-win" projects), generally completed within 1-2 months. For this type of project, it is recommended to adopt an overall waterfall model, in which two stages of blueprint and realization can be used for 2-3 iterations.
2. For large-scale RPA projects, it is recommended to start a management consulting project separately, and the follow-up implementation is recommended to learn from the results of management consulting, including the principles of system top-level design.
3. The RPA project involving the entire department will inevitably have an impact on the positions and job responsibilities dealing with the change process. The work related to business process combing and management change should be followed up in a timely manner, regardless of whether the project is in charge of an independent consultant or an RPA implementer. Enough attention should be given to project leaders.
Fourth, the implementation of the RPA project system can be implemented in phases and batches, but should follow the constraints of the top-level design of the system, and the construction period should be reasonable. For projects involving management or process changes, 6-8 months is appropriate, but it is best not less than 4 Months.