Defining robotic process automation
- 1. By Suhruth Dantu Robotics-Center of Excellence
- 2. Defining Robotic Process Automation Robotics Process Automation (RPA) is a GUI based software toolset than can be used to automate the work of a real person through the use of existing systems and user interfaces, essentially mimicking the actions of real users RPA toolset also called as Virtual FTE (VFTE) are trained to execute repetitive rules driven process tasks through recording of procedural steps and defined business rules. It quickly integrates with multiple enterprise systems and applications and is non-intrusive. Process improvement methodologies such as Lean and Six Sigma have limits Enabling quick productivity realization and efficiency gains through Robotics Bigger transformation projects can span across years delaying ROI Large scale IT transformation business case may not always stack up. Need alternatives Quick deployment window – Just train the Robot with reusable modules Reduced CapeX by avoiding costly IT integration Achieve non intrusive transformation Avoid costly system integration Carry out repetitive tasks via Robotics Enable zero touch end to end processing Quick alternative to large scale deployment Eliminate non value add activities 24 hour productivity window Accuracy – Right first time ~40% Faster processing Seasonal scalability Automate for productivity improvements
- 3. When a transaction fallout happens • If any mandatory field which BOT needs to process is missing in application or Input sheet • Pre defined out of scope tasks. For example Manual invoicing for xxx region • Application throws an unknown exception or error message while processing a task. • Applications gone down or not reachable While we try to automate as many transactions as possible, there will be still fallouts which bot cannot handle and would be need manual team to perform transaction processing What will happen when a Fallout happens is BOT will terminate the transaction processing, updates the Input and output files with status as fallout and the reason for fallout so that Manual Ops team can pick for processing or analysis where required. BOT Fallout process
- 4. Super Admin (Ops Delivery Lead) Complete control, Provides privileges to Admin to create BOT agents, BOT monitoring Admin (Team Lead) Provides privileges to agent to execute tasks. Task Execution using an Bot, Agent monitoring BOT Runner (Ops Agent) Execute tasks assigned using BOTs and BOT monitoring BOT Runner (Ops Agent) Execute tasks assigned using BOTs and BOT monitoring BOT Runner (Ops Agent) Execute tasks assigned using BOTs and BOT monitoring BOT Support Team (RPA Team) Development client access, deployment access BOT Control Mechanism BOT Control Access will be controlled by access privileges and below are the roles and privileges
- 5. Below is the snapshot of BOT output report I am looking in a possibility of dashboard creation for giving a summary view of bot transactions and progress. Will keep the forum updated on possibilities BOT Reporting and Dashboard view