WHERE TO START

CHOOSE A BUSINESS AREA BASED ON BELOW CRITERIA’S FOR OUR INITIAL PROOF OF CONCEPT

• High volume of transactions – Task considered for RPA is performed frequently or includes a high volume of sub-tasks
• Need to access multiple systems – Task involves accessing multiple systems. Example: copying data from a spreadsheet to a customer registry
• Low cognitive requirements – Task does not require creativity, subjective judgment, or complex interpretation skills
• Easy decomposition into unambiguous rules – Task is easy to break down into simple, straightforward, rule-based steps, without space for ambiguity or misinterpretation. Example: Allocate all incoming invoices from Company X with a value €3000 or more to Category Y
• Proneness to human error – Task is prone to human specific errors, not occurring ton computers. Example: matching numbers across multiple columns.
• Limited need for exception handling – Task is highly standardized. Little or no exceptions occur while completing a task
• Clear understanding of the current manual costs – Company understands the current cost structure of a task. It is able to estimate the difference in cost and calculate the return on investment (ROI) of RPA.