SMART RPA

Guy Kirkwood, COO & Chief Evangelist at UiPath, and Neil Murphy, Regional Sales Director at ABBYY talk about enhancing RPA with OCR capabilities to widen the scope of automation.

The Holy Grail Of RPA Guy Kirkwood (COO & Chief Evangelist at UiPath) and Neil Murphy (Regional Sales Director at ABBYY) uncover "The Holy Grail of RPA" in a talk about enhancing ...

From today onward we are publishing series of articles that shows difference between test automation and RPA.
Stay tuned...!

After discussing phases in RPA project , this week let’s talk about what are the key roles in a project.

To successfully implement an RPA project it is recommend to specify the roles at the start of the project. The roles can be filled by external (consultants or interim) or internal resources.

The three roles mentioned below make up the core team, the bare minimum. There are other roles that will help the project succeed. People with skills such as change management, IT architecture and Operation and maintenance will play crucial roles during the project but these roles should be defined when scoping the project. Often there are other IT projects ongoing and co-ordinating with these is crucial.

1.Project Manager
Books have been written about project management. Read those for a more extended role description.

In short, the project manager is responsible for the whole project, from assigning resources to getting the KPIs and measurements correct and getting the budget approved. These have to be done before the project starts.

During the project, the project manager is also responsible for developing the business case and present this to the steering committee. The business case is the formal document that outlines how profitable the RPA implementation is likely to be in pounds and pence (or dollars and cents) and its expected pay-back time.

Four phases of success part V
4.Implementing
Implementing the robot is the exciting part. The robot is now released into the working environment, mimicking an employee’s behaviour. When installed, it is up to the business side to monitor the robot and handle any exceptions. If there are changes in the process, the robot may have to be reprogrammed and it is the business side’s responsibility to either do it themselves (if they have the programming knowledge) or bring it to the IT departments attention.

After having been in operation it is time to measure how productive it is and what the business impact is. Is the process faster? Do we save time? Does it increase revenue? Do we save resources?

After evaluating this first project, it might be time to look at your next automation project.😀😀😀

Four phases of success part IV
3.Design stage
----------------------
At the design stage we would look at the process and start looking at which software vendor best fulfills the criteria outlined in the business case. Different software have different advantages which might and these might be better suited to the organizations needs and future demands. When that choice has been made we would acquire the license from the preferred vendor.

During this phase we would design the exact process and have it signed off by the business. It is then a question of designing the robot.

This stage ends with testing the robot. The robot should first be aimed for quick wins – activities in processes that do not add value but take time and effort. With agile iterations the robot will be programmed to increase the level of automation.

This is an iterative process and several iterations are performed as the robot is fine tuned. When the robot mimics the users behavior to a very high degree and when all exceptions have been programmed it can be ready for release.