What is our primary use case?
We develop and deploy use cases in the area of the cloud. We have deployed over 100 use cases. Most of our use cases are related to SAP applications, web applications, and mainframe applications.
One use case example is related to mainframe applications. The bot monitors mainframe applications 24/7. If there are any new jobs, they are identified, then the bot changes the status of the job to differentiate it.
Previously, we are using the 2016 version of Orchestrator, then we upgraded to the 2018 version of Orchestrator. Some clients are deploying the 2020 version. It depends on the client. We suggest using a version back to clients, i.e., the 2019 version.
We automate retail, sales, and agricultural services.
How has it helped my organization?
There are a bunch of candidates being monitored 24x7. Automation Cloud monitors these jobs, and whenever new docs come into the application, it will then change the status manually based upon certain conditions. Once we deploy the automation into the production, our manpower has been reduced so there are only one or two people needed for the backup. The rest will be taken care of by the automation itself. So, there has been a drastic reduction in our workforce.
What is most valuable?
We schedule different jobs using Orchestrator only. We have a separate team who takes care of jobs that we apply in Orchestrator. So, if there are any failures, it will automatically send email alerts to us.
Within Orchestrator, there is a tab where we can restrict roles from the admin level to the user level. Developers give only access to the jobs. Whereas, admins have a roles option to restrict access.
What needs improvement?
There are still some areas that need improvements. Currently, the tool is not 100 percent accurate with hand written notes and image based automation. It is also tedious using it with Word applications.
We are doing automation to take care of all our processes, but we still need support people 24/7 to monitor these jobs. So, human intervention is still there. We have two people monitoring these automations 24/7 because there are still some challenges with the automation.
For how long have I used the solution?
I have been working with it for two and a half years.
What do I think about the stability of the solution?
When new bots are developed, we definitely see some errors in the first few days, which are usually connector issues. Once the bot is moved to production and has a lot of enhancements and patches to the automations, we make sure that the automation is running smoothly. So, during the initial stages, it won't be very stable, but after a few enhancements to adjust to the automation as time goes, then it will become stable.
Once we deploy and release the automation into production, we will monitor production to see if there are any new challenges, different scenarios, or bugs that we need to fix. We have monitored the automation after deployment for around six to seven months, and the automation went smoothly without any issues. Because the automation is performing pretty well, we have deployed it to more of our workforce and their different jobs.
What do I think about the scalability of the solution?
We have separate, dedicated test data in three different environments. Orchestrator has a database and email server, so everything is in Orchestrator. Apart from the servers, products, and services, everything has a separate operations team, which has eight to 10 members, who take care of everything.
Which solution did I use previously and why did I switch?
Previously, they used on-premises services for the bots. Then, they asked us to migrate more than 20 bots from on-premises to our AWS environment. So, we have created a dedicated AWS environment for them.
How was the initial setup?
The deployment process goes this way:
- Developers develop the use case in a development environment.
- Once that is done, then they will move the code to the non-cloud environment.
- They will test the code if the automation is running fine or not. If automation is running fine, they will show the data which is running fine as a code to the client.
- Once they have the desired output, then we will move to the production environment.
- The operations team will then deploy that process.
The first time, it is a bit tricky. Going to production, it will take around 20 to 30 minutes to deploy the first time. If there is already existing automation, we only need a patch to implement it in production, then it will take roughly five to 10 minutes to apply.
The process of testing and deploying code takes roughly one to four nights maximum.
What about the implementation team?
For deploying UiPath, we need at least three to four RPA developers. In general, one person can deploy at any time. The other two to three people are just there on support calls.
Post-production, we have an operations team of eight to 10 members who take care of the automation.
What was our ROI?
There are some automations that save us thousands of hours monthly. These are automations that we run 24/7 as well as some automations that we run every five minutes for installing backups. Depending upon the amount of time the automation is standing, we will manage the capabilities of the server.
To some extent, it has reduced the operations:
- The automation is sending an email whenever there will be an error. Automatically, it is not going to the user. The user just needs to verify their emails.
- Whenever an error is noticed in the code, the automation will fit the address and email the operations team members.
In these ways, it has helped to reduce operation costs, but not completely.
What's my experience with pricing, setup cost, and licensing?
There are three types of licenses: unattended, attended, and developer.
Which other solutions did I evaluate?
We also use Automation Anywhere (version 10) and Blue Prism automation tools, but I think most clients prefer UiPath. There are more activities available in UiPath versus the Automation Anywhere version that we use. For example, UiPath has database-related activities, but Automation Anywhere, version 10, does not have this feature. I have tried using mainframe appliances in UiPath and Automation Anywhere, and I found that UiPath is more flexible and has more options available.
What other advice do I have?
The solution is single sign-on, so the authentication is done for us, because it is difficult to remember all our passwords.
We have a ServiceNow ticketing tool for reporting issues related to UiPath.
UiPath is very good for developing web-based applications, especially for SAP and the web. For these two applications, you can go with UiPath without any doubts.
I would rate this solution as an eight (out of 10).
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Which version of this solution are you currently using?
Start Your UiPath Free Trial
Accelerate your digital transformation now with free access to the UiPath Platform