Automation Center of Excellence
This guide is an overview for Automation CoEs on how to use OfficeAutomata's Dashboard to accelerate their automation initiatives and build an automation pipeline.
An automation center of excellence is an internal team or a third party System Integrator that streamlines automation output, provides structure, and helps scale automation through the enterprise. An Automation CoE team usually consists of an automation manager, business analysts and RPA developers.
0. Define and Measure Processes through Data Collection
The first step in automating anything is collecting data. Normally, a Business Analyst would spend two to nine weeks manually observing and documenting employee workflows but the Dashboard does most of this work on its own.
The Dashboard Defines Processes by:
- Determining what are your organization's tasks and processes
- What are the respective steps in each task and process
- Finding the start and stop points of each task and process
The Dashboard Measures Processes for:
- How often it is done
- When it is done
1. View the Automation Scorecard under the Home Navigation tab.
Because the Dashboard Defines and Measures automatically, all that the business analyst or automation manager needs to do is view the Dashboard and make data driven decisions based on what tasks or processes to automate first.
The Home - Scorecard is a good place to start looking for top automation candidates.
A task or process's Automation Potential is a function of the average amount of process steps plus the average number of logic events divided by the standard deviation of the variations.
2. Automation CoE reviews and selects high automatability processes based on cost to organization.
Under the Task Summary or Process Summary an Automation CoE can view all tasks or processes. They should sort by Cost and Automatability for most impactful improvements. An Automation Potential score of 40 or above means that a task or process is a good automation candidate.
3. RPA Developers analyze detailed task and process data and PDD information to scope development efforts
After tasks or processes have been designated as automation candidates by automation manager, RPA developers and business analysts need to dig into the task details and PDDs for that candidate. The Task Map and Table will be the most relevant places to inspect for estimating development effort.
Most automation developers want to automate the top 20% of processes from an organization. This is based on how easy they would be automate compared to their impact on the organization.
4. RPA Developers extract automation data to develop bots
After it has been determined the a task or process has a high Automation Potential that lines up with a low development cost and effort, then the candidate needs to be exported into the right automation framework. This can be found under the Process Exports or Task Exports in the Process Details or Task Details.
Automation data can be Exported to:
Depending on the automation platform, OfficeAutomata can export the necessary data and process maps in several different formats.
5. RPA Developers put bots into production and monitor bots for errors
After the workflow details have been exported, the RPA developers use their RPA tools to put a bot into production. When a bot is live, the OfficeAutomata's activity tracking treats it like any other user and all of it's events are tracked. RPA developers can monitor the bot's Audit Trail for errors.
6. Automation CoEs compare before/after automation data to get full ROI
After a bot has been in service for a period of time, the Automation CoE can use the Analytics - Annals to compare the task before and after it was automated. Hopefully, they will see either a decrease in duration or in cost. A business analyst may need to review analytics of robotic workforce or bot tracking to calculate an exact ROI.
For more information about how OfficeAutomata's Dashboard supports Automation Providers please contact us or visit the other training guides.
Non-Disclosure Disclaimer: This document and the information contained herein is confidential; This document is provided for information purposes only for the exclusive use of the recipients to whom it is addressed and the contents hereof are subject to change without notice. Whilst the information contained herein has been prepared in good faith, it is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Office Automata specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Any reproduction, retransmission, republication, translation, or other use of, all or part of this document is expressly prohibited, unless prior written permission has been granted by Office Automata. Office Automata, the Office Automata logo and other all other Office Automata trademarks, logos and service marks used in this document are the trademarks or service marks of Office Automata and its affiliates. All other marks contained herein are the property of their respective owners. Office Automata has intellectual property rights relating to technology that is described in this document.