Robotic Process Automation

Robotic Process Automation2019-03-09T07:22:05+00:00


Automation of rules-based processes with software that utilizes the user interface (UI) and can run on any software, including web-based applications, ERP systems and mainframe systems.
RPA replicates the user’s actions, within the UI, to complete various processes including queries, calculations and maintenance of records and transactions.

Why RPA?

  • Easy to Implement
  • Low code platform
  • No changes to IT infrastructure
  • Managed by business users
  • Quicker ROI

Robotic Process Automation – Use Cases


Decreased Costs:Potential to reduce operational costs by up to two thirds of the human cost
Improved Efficiency:Robots are faster than humans and can be utilized to operate 24/7
Reduced Errors:Eliminate human interventions that can create unintended errors or delays
Employee Satisfaction:Removes many of the unsatisfying tasks we currently ask our human teams to perform

No IT System Changes:Benefits are possible without updating your current systems of record
Customer Satisfaction:Reduced errors improve efficiency and the quality of the customer experience
Security:Reduces internal risks to data and processes
Scalability & Flexibility:Deploy or re-assign more robots where more support is needed

Challenges in Implementing RPA


  • Deloitte’s survey of 400 global firms found that 63 percent of surveyed organizations did not meet delivery deadlines for RPA projects
  • For the ones that succeeded, longer-than-anticipated bot implementations delayed return on investment (ROI)
  • An EY study found 30 to 50 percent of initial RPA projects fail
Area Issues How to Overcome
Stakeholder Buy-in & Expectations
  • Lack of buy-in & engagement
  • Initiative not supported by IT
  • Engage Business, IT, Risk Teams early on
  • Senior management commitment
  • Communicate within internal teams
Process Identification
  • Process not being standard
  • No documentation exists
  • Well defined criteria for process selection
  • “As is” and “To be” process documentation
  • Longer lead time
  • Process changes
  • COE setup
  • “As is” and “To be” process document
  • Engaging the right partner for implementation
Return on Investment
  • Not factoring all the costs involved (Dev, License, IT)
  • Wrong process selection
  • Identification of right process & size
  • Maximize the utilization of bots thru scheduling