RPA Implementation

How to achieve a successful RPA implementation?

This question is often asked at the start of considering a Robotic Process Automation (RPA) activity and there are many possible approaches to an RPA implementation. Deciding which approach is a conversation to be held between a client and Ether Solutions where they factors can be discussed and balanced to reach a conclusion.

There can be many stages to an RPA Implementation depending upon business that is operating the processes and the level of automation knowledge available in the business.

One of stages for some businesses is the selection of RPA technology. As Ether Solutions only implements UiPath solutions for RPA projects. There is no technology selection shown in the following activities.

This is a typical approach for an RPA implementation undertaken by Ether Solutions.

Discovery Process

Workshop to exchange knowledge of “What RPA can do”
Identify and review existing business processes as candidates for RPA (see How to Select a Process for Automation)
Conduct business case analysis for RPA of candidate processes (See RPA ROI Calculator)
Agree success criteria
Agree change management approach
Agree risk and compliance approach
Agree technical architecture and resources (see UiPath Architecture)

Build Activity

Undertake POC (Proof of concept) for any unusual features in automation
Formulate development plan and work breakdown
Agree testing plan, methods, criteria and resources
Implement robot software infrastructure with development and production environments plus potentially one or more test environments
Design robot(s) including use of features for security, audit trail, monitoring, backup, re-start and recovery
Agree any “Pilot” implementations, phases of implementation and agile sprint delivery factors
Agree “Naming” standards, “Password” management and source control method
Build robot(s) for automation of business process
Test robot(s) both functional and non-functional aspects
Document development and operation of robot(s)
Document deployment of robots into production environment
Conduct any required skills transfer and knowledge sharing for client staff involved with RPA

Operation Activity

Agree “Centre of Excellence” role, scope, responsibilities and objectives (Robot on-going support, bug fix, enhancements, new developments, skills and training)
Agree “Robotics Operation Centre” role, scope, responsibilities and objectives
Complete the deployment of tested robot(s) into production
Perform the on-going monitoring of robot(s) operation

Infrastructure activity

Maintain a capacity plan on robot(s) usage
Plan for software upgrades and patches
Maintain usage of robots section of business continuity plans
Develop and periodically review the standards for robot development and deployment

Ether Solutions is able to undertake all of the activities but can also act as an adviser to client staff while they perform the activities or any hybrid combination of the tasks to meet the overall business needs of the client both during the initial RPA implementation and the on-going operation of the RPA software robots.

How to Implement RPA Successfully?

Ether Solutions has used its wide experience of implement RPA to create a 90 Day Automation Method.

This covers the People, Process and Technology aspects of implementing RPA. All three areas need to be managed to deliver a successful RPA Implementation which delivers the expected benefits and can evolved into an on-going automation programme with subsequent RPA Implementation projects.

In the early days of RPA technology some technical enthusiasts would dive into the rapid use of the RPA software and expect great benefits. It is why some early RPA projects failed. The RPA technology has matured and experienced consultants know that good design principles, the use of standards, effective security controls, appropriate development skills and clear support processes are all factors which will contribute an RPA Implementation success.

Business leaders will always want the benefits of RPA, however they are best achieved as part of an Automation programme rather than a one off project.