‘Time spent on process by Human ‘– ‘All time saved by Bots’ = 100 % time and money saved

Unfortunately, it doesn’t work that way !! Real life Automation isn’t a Sci-fi movie, so let’s get some facts straight!  Here are some checks  to ground expectations on how your RPA deployment is most likely to pan out.

While RPA helps you radically decrease time spent on certain processes (assuming a wise RPA Optimization), there are various overheads that RPA itself will introduce.

  • Monitoring & Exception handling

Undoubtedly the Achilles heel of the RPA implementation is exceptions and its handling. Exceptions happen due to improperly designed workflows, poor execution set-ups, data errors, false triggers amongst other factors. Catching error(s) and then figuring out what went wrong and where is going to eat up a lot of time.

Especially in large orchestrated set-ups, the whole automation execution may be stalled till troubleshooting is complete and a fool proof exception handling path is defined.

  • BOT maintenance activities

Performance monitoring and optimization, Logs management, security monitoring, exception handling, re-configurations are all standard maintenance tasks which will consume time and resources. You will need to have an AMC with your RPA provider who can provide these services for you.

  • Change Management

BOTs are extremely sensitive to changes. A change in font/color of an element can be a disruptor or even a calamity – based on how the automation workflow is designed. So any change in your RPAed software/application will need to be carefully calibrated into the BOT workflow.

  • Assisted Automation

This is what an assisted automation scenarios look like

A bundle of repetitive tasks – > A Human Decision – > A bundle of repetitive tasks

Based on the process you are automating, assisted automation may be required. While this is not an overhead, it is not autonomous automation either – hence, does not translate to complete removal of human decision making. So yes there always be some processes that are best left semi automated.

In conclusion, it is best to take account of these aspects to set realistic expectations when you are selling RPA internally or externally.