According to the Capgemini Research Institute, large organizations will achieve savings of almost $500 billion dollars in aggregate by 2022 using intelligent process automation (IPA). The most mature of the current crop of IPA tools are software robots, commonly referred to as robotic process automation (RPA) products. We are now seeing the rapid adoption of RPA to streamline and scale a range of front- and back-office activities. While large financial institutions were among the first to aggressively embrace RPA, the trend we are seeing now spans across industries. But the rapid acquisition of these tools is often accompanied by challenges. The key issues manifest themselves with questions that we, as one of the larger RPA integrators globally, hear on a regular basis:
- “We’ve done some proof-of-concepts, but how do we ‘industrialize’ RPA to deliver benefits faster?”
- “Now that we’ve put some bots into production, what’s a good support model look like?”
- “Before the business lines develop dozens of bots, what kind of governance processes should we establish?”
What are the Core Capabilities of an RPA COE?To drive these capabilities, we see best-in-class RPA COEs supplying five key services:
- Governance: establish the policies, procedures, and standards for bot qualification, development and deployment to meet audit, regulatory, information security, and compliance requirements;
- Technology: select the right automation tools and then organize the maintenance and support of these tools. Drive the integration of RPA into the fabric of IT Service Management (ITSM), including change management and the configuration management database (CMDB);
- Processes: execute and monitor the complete lifecycle of RPA in the enterprise, from evaluating automation opportunities to deploying bots into production environments with a scalable support structure;
- People and Culture: analyze and effect the changes to human roles by RPA, from organizational change management (OCM) to redefined job descriptions and even altered org structures;
- Organization: define the organizational structure of the COE itself, including the definition of a RACI chart to define the roles and responsibilities for all aspects of RPA;
Alternative Organizational Structures for RPA COEsBecause RPA innovation can be business-led, we see three basic structures used to support an enterprise-wide automation effort.
- The COE as a support function for the business: this model provides a loosely governed operating model, most suitable for less regulated industries (e.g., consumer packaged goods, industrial manufacturing, etc.). In this scenario, the lines of business establish their own COE guidelines and structures, which can aid speed and flexibility but may hamper scalability.
- The COE as a central RPA provider: this model provides a shared service comprised of business and IT members who manage all aspects of RPA intake, delivery and support. This option supports high scalability but can require more significant discussions with business and IT stakeholders to establish the framework for a true shared service.
- The COE in IT as enabler for business: on the opposite side of the spectrum from the first option is a COE closely managed by IT. While it’s usually easier to get executive support for this model, it can hamper enterprise scalability in some cases.