Integrate RPA Bots into your existing tool chain

Micro Focus Expert
Micro Focus Expert
3 0 4,588

RPA tools (Robotic Process Automation) are great solutions for automating boring, expensive, and repetitive workflows. RPA is designed to follow a pattern of user interactions and can free up valuable human resources by allowing software to perform repetitive tasks related to business processes. RPA tools provide the possibility for organizations to build a virtual workforce that works around the clock and continuously performs tasks without any human intervention.

Basically, RPA tools consist of 3 basic components: Designer, Orchestrator and Robot.

rpa.3.png

The Designer (also Studio) is used to create and design automated processes.

The Orchestrator is the brain of a RPA solution. It coordinates the execution of the automated processes based on user input or periodically. It also takes care of the management of the robots, which are part of the topology of an RPA platform. 

The Robot is software robots that actually execute and run the automated process.

Common misunderstanding

When we talk about integrating RPA into the existing set of tools, we mostly refer to the workflows and processes we aim to automate using RPA. This usually starts by identifying the workflows and processes where a high amount of human effort and time is involved by executing repeatable tasks. These tasks are mostly performed on the frontend of software, such as SAP, Outlook, Microsoft Dynamics, Salesforce, etc. This kind of integration is referring to the recognition capabilities of an RPA tool and not of being integrated into an existing toolset.  

rpaspp.png

The need to integrate

Let us assume, we have an ITSM process, where employees open an internal ticket or service request when they need to order a new phone, laptop, or any other asset required to do the job. Today this is completely manual. Once the ticket is created and approved, someone needs to place an order of the asset and interact manually with the ordering system. In order to integrate and benefit from RPA, the ITSM tool should be able to execute an automated Bot from the RPA platform as part of the ITSM workflow. rpaprocessint.png

Once RPA is integrated into an ITSM workflow, the user will need to submit the ordering request/ticket. Once the request/ticket is accepted, the manager/approver will approve or decline the request. If the request is declined, the ticket is updated as usual as part of the ITSM workflow. In case of approval, RPA bot(s) will be triggered, which will extract the employee information from the ITSM ticket such as job level, location & cost center and order the asset required by the employee. This will consist of activities to login to the asset ordering tool place the order based on the job level of the employee. Once the order is placed, the billing need to be mapped to the correct cost location, as well as the correct employee location needs to be added as a delivery address. Once completed, a confirmation email is sent to the employee and his manager. After this, the ITSM workflow is set to the next phase.

rpawf.png

RPA is not only for business (users)

To integrate fully automated bot(s) as part of your existing toolchain, it should be possible to access and execute the bots using an open interface (such as REST API, SDK, etc.) on the RPA platform (usually on the orchestrator). This is crucial to be able to integrate and scale RPA within an organization. When RPA tools are evaluated and implemented, they are not integrated into any of the existing toolchains, such as ITSM, DevOps, IT Operations, Asset Management, Development EcoSystem, etc. This is a mistake as RPA implementation gain on maturity, this aspect becomes more important to the overall automation initiatives.

rpam1.png

RPA at the enterprise level

On the long term, RPA will not only be used to automate business processes and increase productivity – on the contrary: Existing toolchains will require the need to integrate and consume their own bots as part of accelerating automation and improvement. Therefor a cross consumption is unavoidable.

The following diagram shows an example of how RPA evolves and integrates into the different toolchains.

For example, ITSM processes will manage, consume and integrate their bots into the ITSM workflow as needed, the same goes for DevOps (preparation and post activities), IT Operations, Business, CRM, etc.

rpam3.png

This allows for a flexible consumption of RPA across departments and teams and will not be isolated anymore. Share, reuse, and collaboration will increase to productivity for RPA and build an automation community within an organization to support all aspects of automation (Test automation, RPA, Service, IT Process, etc.).

Conclusion

The reason many organizations are failing adopting RPA solution is the fact that often it is evaluated as a point solution focusing on automation aspects only. When it comes to scaling bots by integrating into existing toolsets, it starts to get complicated as the initial evaluation was made for a specific department and not completely valid for the enterprise need.

Micro Focus Robotic Process Automation gives you the power to build, secure, and scale automated processes, from legacy to modern, across the enterprise. Combining UI and API operations to centrally orchestrate the work of robots, Micro Focus RPA liberates human brainpower and ignites enterprise productivity. It provides an open REST API to integrate automated bots into your existing toolchain, independently from the toolsets in place.

Check out this related article

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.