Dir., Resource Management Systems and Data at a healthcare company with 10,001+ employees
Real User
2022-06-30T18:56:04Z
Jun 30, 2022
Our main pain points have been:
1) Not building in all the 'what ifs'. A BOT is expecting certain values in a given field. If the expected value is not met, the Bot needs to maneuver around it, not stop the process. The process should include writing an exception and keep going. We learned the hard way that we didn't know all those exceptions - until they happened.
2) Train the BOT to keep you posted on what they have/have not done. Don't wait until the file/output is late to try to figure out what happened. Stay informed!
We love our BOT, and it has allowed us to function as Humans at a higher level - we would not want to go back.
Search for a product comparison in Robotic Process Automation (RPA)
Project Manager at a tech services company with 51-200 employees
User
2022-07-01T02:19:30Z
Jul 1, 2022
1. Unexpected exception. Customers are usually familiar with normal processes, but it is difficult to enumerate all exceptions during requirements analysis. When a new exception occurs, it can be catastrophic in a production environment.
2. Unexpected changes. RPA depends on third-party apps, but they do not depend on RPA, especially for external applications. RPA responds passively to their changes.
Unknown exceptions should be handled by human, and bots should be improved at the same time. But to be honest, it will affect user experience and ROI.
What is RPA? Robotic process automation (RPA) is a software technology that enables enterprises to build, deploy, and manage a virtual workforce made up of software robots (“bots”) that emulate the actions of humans in interactions with software and digital systems.
Our main pain points have been:
1) Not building in all the 'what ifs'. A BOT is expecting certain values in a given field. If the expected value is not met, the Bot needs to maneuver around it, not stop the process. The process should include writing an exception and keep going. We learned the hard way that we didn't know all those exceptions - until they happened.
2) Train the BOT to keep you posted on what they have/have not done. Don't wait until the file/output is late to try to figure out what happened. Stay informed!
We love our BOT, and it has allowed us to function as Humans at a higher level - we would not want to go back.
The main "pains" is to know and understand the architecture of every vendor, their business model and the time to learn to code and develop a bot.
The solution was to make our own classification, in order to compare the terms and ratings according to what is a priority to us.
1. Unexpected exception. Customers are usually familiar with normal processes, but it is difficult to enumerate all exceptions during requirements analysis. When a new exception occurs, it can be catastrophic in a production environment.
2. Unexpected changes. RPA depends on third-party apps, but they do not depend on RPA, especially for external applications. RPA responds passively to their changes.
Unknown exceptions should be handled by human, and bots should be improved at the same time. But to be honest, it will affect user experience and ROI.