Selection of technology and proof of concept (PoC)
The preparation to RPA implementation mostly means verifying the possibilities of this technology in the case of a particular organization and answering the question of whether robots will stay with us for longer. That is why the team is so important — during the pilot implementation or PoC, it will select the platform and indicate business processes that will the subject of automation.
Business representatives in the team should prove their knowledge and understanding of the business processes and ways of accomplishing tasks of which the business processes are comprised. It is their job to assess the assets that will be involved in the planned project and approximated volumes of transactions.
During that stage, the task of the IT people is to verify the safety of considered RPA platforms (proper certificates, ways of storing keys, authentication, and authorization), as well as compliance with architecture standards of the IT systems in the organization. Besides, the representatives of the IT department support the people who build robots by sharing knowledge about the technology and the operation of business applications on which digital employees (that is, robots) will work.
The selection of people involved in building the first robots depends on the adopted strategy of automation.
- In the case of insourcing, the specialists who combine knowledge about automated business processes with both basic computer skills (Word, Excel, www) as well as the basics of programming (variables, loops, program control) will prove themselves. They do not have to be developers. Before the PoC stage, it is worth running a course on the the basic use the utilized RPA platform for them.
- In the case of outsourcing, the IT involvement may be limited to issues related to providing the vendor with access to the system and appropriate permissions. However, it is essential to supply the vendor with detailed information about the carried-out process.
In the following part, we will focus on planning the work in insourced or combined model of building robots (a client and a provider of robot creation services), as well as creating the RPA Center of Competence. The project team should consist of people with analytical skills and can-do approach, open to new ideas and technologies, because these are the natural candidates to create the RPA Center of Competence (CoE/CoC).
The stage of selecting processes and building robots
The robots built in the PoC stage or pilotage are usually less complicated than those with which we deal at later stages of RPA technology implementation and operation. Therefore, in the selection of further processes for automation, comprehensive knowledge of the organization and nature of work in particular departments is essential. It allows a faster and — most importantly — more effective selection of further processes and tasks subject to robotization. Thanks to this, it is much easier to avoid pitfalls of robot implementation when tactical tasks are carried out, and combine the tasks into longer processes. Components of automation platforms, such as UiPath Apps, are helpful in this.
Moreover, the increasing complexity and scale of the processes covered by the implementation as well as the use of robots in the production environment lead to the necessity of conducting tests as in the case of every other software platform implementation and update. Therefore, it is important to implement standards similar to those used by teams that build software. The contribution made by the people delegated from IT seems to be essential for actions such as defining standards of robot creation (components naming, exceptions handling, the optimal approach to processing big volumes of data) or robot operation validation.
Maintaining robots in a production environment
A well-performed PoC stage should be completed with a decision about choosing particular RPA technology and preparing a list of processes planned for automation in the nearest future, including the first process (or processes) ready to be implemented to the production environment.
As during other implementations, in the case of RPA the first days or weeks of solution use decide whether it is a success. Over this period, the possibility of difficulties is the highest. It is necessary to assign (and train) someone who will monitor robots working in the production environment. The role is so significant that the knowledge of people in this position should be no less than the knowledge of RPA developers, or they should have constant contact with people involved in creating the robot code. At the beginning of an organization’s adventure with the RPA technology, these two roles can be played by a single person. However, as when the number of automated processes increases, it is no longer possible since robots can work without a break 24 hours a day, seven days a week!
The first days of robot operation in a production environment will also most likely help in detecting business cases not considered during the analysis before the implementation. Close cooperation of the person that supervises robots, the RPA developer, and the business representative will make it possible to verify the automation and prepare a business case to complete the code of the robot so that it handles new tasks.
RPA Center of Competence activity
The implementation of the RPA technology, its growing importance in the organization, and the appearance of other forms of process automation result in the need of establishing a competence cell for them: CoC/CoE (Center of Competence/Center of Excellence). It is a team that not only watches over the maintenance of already existing solutions but also looks for new technologies and possibilities of their application to improve the effectiveness of the whole organization. The establishment of this team helps in improving information flow and sorting out procedures regarding both internal company policy as well as industry regulations.
We can distinguish the following roles within the Center of Competence:
- RPA Project/Program Manager, Manager of the RPA Center of Competence is responsible for the contact with the sponsor in the organization and performance of work starting from building the team to passing robots to operation; very often, they play the role of an automation ambassador (Change Manager) in the organization.
- RPA Solution Architect defines the technical standards for building RPA solutions and the cooperates with the infrastructure team (representatives of this team can join RPA Center of Competence).
- RPA Developer designs, implements, and tests robots and their components; in the case of smaller teams, the developer may also play the role of a process analyst (if they have proper predispositions).
- RPA Supervisor is responsible for planning robot launches and the business processes carried out by them; in the case of smaller teams, the supervisor can also play the role of the first line support for users.
As you can see, RPA implementation comes with creating new job positions and often whole new structures in the organization. These actions undoubtedly mean cost for the company so it should be considered at the beginning of a project. However, it is worth thinking of it as an investment that will let the company to obtain measurable benefits and open new possibilities of professional development for the employees.
Do you agree with such an approach? Are you thinking of automating first processes in your organization?
- RPA Consultant
A manager with over 15 years of experience in software and technology consulting. A graduate of the Warsaw University of Technology and the Warsaw School of Economics experienced in managing big teams (over 50 FTE) in international programs and projects. He has cooperated with clients from the financial, manufacturing, and telecommunication industries in Europe and the Middle East. At Craftware, he is responsible for consulting and development of RPA services.