RPA Process Assessment (Not Limited Too)
2 min readJun 3, 2021
- Identification — Organization, business area, business process, systems and software utilized
- Execution Details — Total number of Full Time Employee’s utilized for this process, cycle times used in process (minutes, hours, days, weeks), average handling time (End-to-End), error rate calculated (how often/what percentage)
- Process Details — Standardization (logic defined, consistent, repeatable, or ad-hoc), throughput (Volume of Work, number of Tasks processed by FTE’s)
- Complexity Level — number of target systems, distinct screens, output destinations and input destinations, as well as execution scenarios (i.e. exceptions)
- Implementation Effort — Systems (number in execution), screens (number of distinct screens used), outputs (destination & formats), inputs (OCR/ digital data format), execution and happy path, security access (highly secure, or no access)
Process Selection Model
- Process Interaction — Volume, repetitive interactions, rule complexity, number of systems
- Maturity — Consistent, well defined, measurable, implied knowledge
- Business — Business significance, business priority, regulatory/compliance, business change, current costs
- Process Intelligence — Decision patterns, percentage of exceptions, sentiment analysis, visual analysis
- Implementation — Computer vision, operational costs, capital costs, cognitive technology needs, security constraints
To mitigate Risk with Suitability Analysis, you might want focus on these characteristics during key implementation stages:
- Process Optimization/Simplification — This is RPA in the works, not Business Process Management (like Appian). It’s necessary to evaluate the process optimization points and to be able to simplify and adjust ad-hoc after analysis from RPA implementations. Lessons learned will provide great dividends in how you can optimize processes while still allowing the bots to perform their functions
- Human FTE Impact Effect — Executive level vision on where potential mundane roles might or might not shift too, allowing time to evaluate best fit areas, role modifications, and re-deployment opportunities on-shore and off-shore
- New Exceptions and Workflow Configuration — reducing error handling and confirming smooth workflow configuration is vital:
- System vs. Business Exception reporting — Your RPA Analyst or System Architect will need to run daily exception failure reports to analyze stats like the percent of transactions
- Operational Manual — utilizing this function to coordinate RPA implementations from the RPA team to IT; compliance, audit, and governance is imperative for pre- and post-deployment
- Bottleneck via Manual Inputs — Avoiding the bottle-necking via bot to manual and back to bot; again, this can cause delays, make sure this situation is limited