Automation impact

End-to-End RPA explained
in simple words

Automation impact

End-to-End RPA explained
in simple words

AI2 – Operating model – Part 1

Operating model

AI2 - Operating model - Part 1

Topic: Operating model
GuestFrank Schikora
Recommended for: CoE management, CFO, Team managers, RPA Lead

Operating model - Part 1

About guest: Frank Schikora is a Head of Delivery @ Roboyo and UiPath MVP

(1:35 – 3:05)
Frank Schikora is Head of Delivery at Roboyo and UiPath Most Valuable Professional. He studied Business Informatics (Master) and after started to work in IT Operations where he did first automations. His journey with RPA (and UiPath), however, started at Roboyo. In current position Frank is ensuring the quality of automation delivered to the client while also trying to keep up with the innovation in technology in the end-to-end automation journey.

(3:15 – 6:03)
Before this position Frank worked at the infrastructure side, where he was helping customers to start with their RPA journey. This quickly shifted to the actual project delivery – as an automation engineer, then moved to the role of project manager and project lead, where he got a team of developers. Even though Frank is now focused on the methodology he still delivers projects and writes codes from time to time which is “a good practice to not get out of practice”. 

(9:42 – 12:48)
Frank’s journey to MVP role started with being a pretty active part of the community on the forums, then part of Reboot Your Skills program and developing custom activities on Go. What would Frank recommend to the next MVPs? Deep technical understanding of the product, delivering quality automation and believing in the product. 

(12:50 – 17:09)
The discussion about the operating model is important as it is the core of any project. Wikipedia (2020) defines the operating model as “both abstract and visual presentation of how an organization delivers value to its customers and as well as how the organization actually runs itself”.  According to Frank, the operating model is core guidelines on how to service RPA initiative as it is “the biggest and most influential part of the end to end automation”. The only case when you don’t need to have an operating model is when you have only one or two robots, so really small projects. Easily said, “the operating model is defining who does what, when, and with what purpose.” 

(17:10 – 20:38)
In an ideal world, the operating model is something to start with. Automated processes are showing their effect on business contingency even now in COVID-19 times – “Robots are just lying on the servers doing what they are supposed to do without any effect.” 

(20:40 – 38:53)
Frank’s first experience with the model was at Roboyo when working for a big German bank. It was more sort of setting the governance – which kind of services provide, what to do, what tools work with, strategy and vision, resources. Even though the model has been replicated five or six times since then Frank says that “the approach is a lot different now than it was back then”. Now it is more about end-to-end automation than RPA itself, the focus has shifted from technology to strategy and vision, to collaboration and integration with the ecosystem of the company. This is crucial when you have so many people that you need to cooperate with. Due to this fact and many discussions the operating model “slows you down at first but gives you the power of scaling and speed of implementation and get rid of the headache of maintenance”

(44:53 – 54:32)
If we are to name the essentials of operating model on different levels, according to Frank: 

MUST-HAVE level (Surviving kit)

  1. Methodology
  2. Best practices
  3. Documentation
  4. Internal alignment

The GOLDEN MIDDLE level (80/20 principle)

  1. Methodology
  2. Best practices
  3. Documentation
  4. Internal alignment
  5. Reporting
  6. Demand management
  7. Governance 

ADVANCED level (covering the last 20 percent)

  1. Methodology
  2. Best practices
  3. Documentation
  4. Internal alignment
  5. Reporting
  6. Demand management
  7. Governance
  8. Strategy&Vision 
  9. Support – stable and accessible
  10. RPA Champion / Sponsor (someone to “fight for RPA”)
  11.