Your benefits will come from analysis of your as-is processes, and how these can be improved using automation. But for a few general thoughts:
Look for use cases like:
- Using UiPath to do an “integration”, e.g. other app puts a transaction on the orchestrator with webservice, robot goes and types it into the existing mainframe applications
- Taking some access away from people, get them to request something with approval in workflow, get the robot to do the entry into terminal. Some mainframe applications are way too powerful and have limited logging and controls.
- Collating data out of terminal programs into other reports
- Repetitive checking/simple business rules - we have a UiPath process that reviews a set of mainframe programs for details on a customer account, and then applies a set of business rules. Exceptions are pushed out to people to manage.
With most of these, there just hasn’t been a business case to do the difficult work to replace the mainframe application or build a normal integration. RPA puts all these back on the table due to it’s low cost, speed to build with technical analysts rather than true developers and maintains the investment that has been made in the mainframe in reliability, controls in the existing programs, etc.
With UiPath, I have had alot of success using Rocket BlueZone as the terminal client to connect to our mainframe. There is a 30 day trial on the Rocket site. Make sure to install the 32 Bit version (64 doesn’t work with UiPath).