In order to increase its economic efficiency, the main target of RPA providers is to facilitate the two most costly stages of RPA deployment, design & development and maintenance. To this end, in the maturation process various solutions will be pursued, such as the simplification of RPA programming (in accordance with the no-code RPA tendency), or the development of self-learning and cognitive automation.
Leveraging Natural Language Processing (NLP), Optical Character Recognition (OCR) and machine learning will broaden the category of automatable processes. The RPA application areas will expand beyond support functions to more complex operations such as end-to-end customer service with chatbots, performance of KYC checks over handwritten customer input or scanned documents. For instance, a Forrester report predicts that throughout 2019, up to a fifth of service desk operations will be eliminated by integrating RPA, chatbot technologies and cognitive systems.
With this trend towards RPA becoming more intelligent, sophisticated, and more widely applicable, it will most likely also be used to improve the performance levels of IT departments, despite professionals’ skepticism that it be nothing more than Macros. We thus argue that robotic process automation will change IT operations as it matures over 2019.
But what do we actually talk about when we talk about IT automation? To put it briefly, it refers to the use of software tools to manage the IT tasks in a business environment with minimal intervention from the part of IT administrators. In what follows, we’ll put some flesh on the bones of this generic description by introducing 8 concrete RPA use cases for IT.
Real world use cases of IT automation
Use of RPA to change IT operations amounts to increasing process quality, reducing service delivery time and Mean Time to Restore, enhancing the productivity of IT resources, and, as a consequence of all of the above, ensuring an overall improvement of operational efficiency. In the list below, you can find both back- and front-end processes.
1. Backup and patch management.
These are routine, repetitive tasks that require meticulous handling without necessarily leaving employees who perform them manually with a sense of fulfillment or job satisfaction (on the contrary!). However, your business cannot do without them. So this is a typical kind of process that can be removed from employees’ shoulders and assigned to RPA technology.
2. Password resets.
Requests for password resets are repeatable, have a typical and consistent structure, and few exceptions. Consequently, the process is a prime candidate for automation. All that’s needed is to provide software robots with specific templates (request, acknowledgment, etc.), and with access to the IT service management (ITSM) tool for active directory activities.
The next step is to set apart urgent from non-urgent requests, and allow bots to deal with the latter category. By logging into the Citrix app, bots can simply change the password, send the new one to the user, and change the request status to "solved". UiPath provides an informative case study about the whys and wherefores of automating password reset requests. Their result was a reduction of handling time to 12 minutes per request, which means that the company was able to save 1 FTE per month.
3. User management.
Leveraging bots in the IT department to handle activities like account creation, email address creation, etc. crosses over the benefits into the HR unit. Upon collecting user profile information for account creation, software robots equipped with access to email exchanges and the ITSM tool, can use that information structured in accordance with the HR templates and generate a service request.
Similarly to (2) above, bots first pass on the exceptions to the global service desk staff and validate the non-urgent requests. They can then handle the creation of a new user account based on the End of Day report. They set up an exchange account, provide the default access credentials, notify the HR about resolving the request, and change its status to "solved". Finally, when the service desk decides that everything works as it should, they close the case.