Setting the Tone with Enterprise Automation using RPA within the Organization
THE PATH TO TAKE
What path can you undertake in setting up at Robotics Process Automation (RPA) practice? Who is involved in this selection process? What are teams involved? Do you go Desktop or VM? At what juncture is IT involved? Do you start slow, with smaller POC’s, and build progressively with higher volume processes, or do you jump in fast with major volumes at stake?
Just Google RPA, and you’ll get thousands of strategies, framework, methods, on pulling it all together to a custom approach for your own team. This article will examine a few simple approaches to using RPA in your organization. We will assume you might’ve selected an RPA vendor, did (suitability analysis, Benefits ROI analysis and designed an RPA roadmap). The approach taken on RPA practice implementation varies from client to client.
Most RPA implementations will be more agile based, smaller volume sets, and mature over time, with huge dividends later on. Using a lower RPA Risk model will complement IT, compliance and audit teams. Other companies will invest heavily in the beginning, as they have researched all potential avenues to take, and are confident with their direction. One must also factor in, who is performing the Analysis, Delivery, and Implementation? Internal or external resourcing, a Hybrid Model of both. The last area in RPA creation is to consider ‘where to start your RPA Center of Excellence (COE)’? Is the COE necessary for success? At what stage do you start to build and iterate excellence within the organization?
SET THE TONE
One major question to ask and answer prior to any project initiation – Is our RPA (COE) Center of Excellence / PMO – Governance framework in place to provide oversight on all projects? The obvious answer should be a resounding YES! Unfortunately, in the current RPA / Business Automation landscape, many companies are not fully prepared in the beginning stages, but that shouldn’t deter any company from venturing into the RPA space. Some companies can adapt quickly, validate process selections, design POCs, develop, test and build in production for deployment. It is also recommended to measure outcomes of RPA results, and performing stage gate reviews/lessons learned to expand the RPA enterprise. The steps below can help your team initiate the RPA program framework:
- RPA Kick-off – discussions with all business owners, align core business teams with a new RPA / BPA model, and discuss which ‘potential’ business processes fall in scope for RPA work
- Confirm key business stakeholders (each business unit area) to be automated, select one lead from each area
- Identify RPA vendors, conduct demo walkthroughs, select the best RPA tool to fit your environment (or work with the Consultant team on site who has experience and will recommend best tools to utilize)
- Identify the Resources and augment with specialized vendors as needed. Usual best practices are to have a combination but depends on each company’s capabilities and needs
- Perform Suitability Analysis – Draft and Sign off – on processes selected
- Establish the Project Plan RACI, time, cost and scope of project deliverables and major milestones. Pre-setup prior to start is vital.
- Testing Environment Initiating the test environment on test cases, strategy and criteria, unit, end to end and regression, etc.
- Create a COE Center of Excellence for the RPA / BPA Business Process Automation practice, working in unison with IT infrastructure, PMO / Governance, Compliance /Audit & Risk and the Executive Committee
- Transition to a strategic Governance Model (Internally) upon your COE being developed to monitor the overall RPA program.
- Establish the Operations Manual to provide ‘day to day’ activities in RPA rollouts with IT, Compliance, PMO, Governance, and consulting teams.
- Post Production Support Maintenance and initializing the Service Level Agreements (SLA’s) between a partner (remote or on-site) to maintain the robot’s performance, gain metric data points, manage the control panel to verify any system exceptions or failures, and backup of data in case of outages