AutomationCOE Establishment

RPA Center of Excellence Program

The Enterprise has started their RPA Journey but want to setup an RPA COE and Governance Program. Every enterprise conversation we have had regarding RPA includes a question about the coveted “COE” and the discussions are typically broad and varied. “Do we need a COE?”, “How do we set one up?”, “Can you help us set one up?” and so on. The basic functions of a COE fall under the following five broad categories. Vision, Strategy and Governance, Methodology, Service Model, People and Technology. So, to get the basic questions out of the way. “Is the COE Needed?” Well, yes and no. If you are doing a Pilot or a POC, you don’t need one to start them. However, keep in mind that you will need someone to be in-charge of setting up an enterprise program and infrastructure that will need to scale with the sudden influx of automation requests we usually see, once the Proof of Value is visible. You will also need someone to navigate the technical challenges of setting up infrastructure and Bot IDs, VMs, and so on. It may be a good idea to involve the group/person that may be the best candidate to eventually run the CoE up front.

Services

Strategy

Bot Performance Monitoring (Workload, Exceptions, Queues and Bot Platform Monitoring (Infrastructure Monitoring)

Governance

L1 and L2 Support (Usability Support, Triage, Trouble Shooting) and Escalation and coordination of issue resolution with development teams

Methodology

Support deployment of code to production

Duration

Enterprise – 90-120 Days
MBE – 45-60 Days

Deliverables

Opportunity Assessment and Demand Management Methodology

RDLC – Process Automation Delivery Methodology

Organizational Operating Model

Pricing

Accelirate offers a simple pricing for COE establishment

*Please contact us for pricing at [email protected]

Lorem ipsum dolor sit amet, consectetur

The basic functions of a COE fall under the following five broad categories. Vision, Strategy and Governance, Methodology, Service Model, People and Technology.

We have seen many COEs set up and the only ones that were successful in having the enterprise adopt their recommendations were the ones that had delivery capability built into them right from inception and were responsible for delivering real life, business value solutions. Most of these COEs sat within Enterprise Architecture or Shared Service groups. There is nothing more annoying to a business IT manager than a EA group that presents standards in abstract without having practical delivery experience. Seasoned Enterprise Architects always build delivery capability into their COE. A COE must “eat its own dog food”; It will never be able to tell other groups within the enterprise how to do things, unless it has itself has consumed its architecture, governance practices, and delivery methodologies.

Setting up an automation program for the enterprise requires a thorough understanding of not only the challenges that are unique to RPA but also expertise with infrastructure and Dev Ops. The CoE provides various services such as Demand Generation and Management, Process Analysis, Automation Development (Configuration), and ongoing maintenance and support. In order to provide these services efficiently, a successful RPA CoE needs to establish three verticals:

  • DevOps
  • Infrastructure
  • Operations Center