What is our primary use case?
Here are two use cases: one involves a customer with an insurance domain. They had multiple underwriting claims, loss prevention, members, or teams, and they were doing manual filing of the documents or correspondence. We automated the document filing system using UiPath. We had users send the documents to a particular email box with a particular subject line. Then, we had the UiPath robot automatically read those email subject lines and automatically file into SharePoint online.
The second use case involves creating new policies in an underwriting system or renewing the older policies in the system automatically. The robot will read the Excel file in a particular structure and will create new policies or renew the existing policies in the underwriting system automatically, building on certain key business rules. The successes or exceptions will be reported to the business.
How has it helped my organization?
By automating the document filing system for our customer with an insurance domain, we were able to save them eight to nine years of individual-person-effort with regard to filing. We have saved them almost 1800- to 2000-person days of work.
Also, there was a team that used to key in the data for delegated underwriting authorities to create the policies or renew the policies. However, with the success rate we have achieved with UiPath, we have been able to bring down those efforts as well so that our customer can utilize that team in other valuable activities.
What is most valuable?
UiPath has a low code or development.
Also, the Orchestrator module is very effective because it allows me to schedule the jobs in a particular manner without interrupting any processes so that it can automatically handle it.
The UiPath libraries or classes in which the flows are maintained are very effective. UiPath has a very meaningful or powerful parameter-driven approach such as the flows approach. So, you can customize the flows as required, and you can use that for further business processes as well.
A rich use of libraries and reusable assets can be created in UiPath, which is quite significant.
What needs improvement?
One key aspect is how UiPath in itself can provide certain views of where an exception has occurred. If UiPath can identify where it has gone wrong and try to identify the bottleneck value, which are more machine learning in AI, it would be great.
If they can strengthen that core area as well as in the business processes side, not as a separate module but within the current RPM module itself, it will be really helpful. If they can bring AI and ML algorithms within it, it will be great.
For how long have I used the solution?
I've been working with UiPath Process Mining for almost three years.
We have a hybrid cloud process.
What do I think about the stability of the solution?
If you have implemented it correctly with detailed requirements, refinement, and correct processes and standards, then it will be very stable.
Our processes are running for the last few years in a very stable manner without any major concerns or failures in production. This has increased our credibility with our customers as well regarding the stability of UiPath Process Mining.
What do I think about the scalability of the solution?
UiPath Process Mining is scalable, but it is key that you identify the right use cases to implement STEM. If you have to convert a lot of complex manual interventions into an automated process, then things may be really difficult to scale. However, if you have a process that is very rule-driven, then it would be quite scalable. So, the scalability depends on the complexity of the business process.
How are customer service and support?
We received adequate support, but sometimes the turn around time to get into a particular root cause was high. So, I would rate technical support at eight out of ten on a scale from one to ten.
How was the initial setup?
Deployment is very quick in the case of RPA, and it takes less than five minutes. It's very effective.
We have certain standardized checklists, guidelines, and best practices, which we recommend all the team members go through at the start of the project. They follow STEM. Similarly, we take care of STEM during deployment checklists and then book preparation as well, so that the deployments are quite quick and easy for the release management team.
What about the implementation team?
We implemented it through an in-house team.
What's my experience with pricing, setup cost, and licensing?
There is a standard licensing fee, which is charged for the products, but it is very module-driven and depends on your utilization or your team size. Compared to that of other providers, the cost is average or below average. So, from a pricing perspective, it's not very high.
For example, let's say you are developing a new process that has to be a fully automated process without any manual intervention. You will then need to buy a robot, a studio, which you have to use for development, and an Orchestrator to deploy that bot. You will also need one non-production license for your test environment.
So, there will be three to four different products that you have to plug together and buy as a package, but each will have its own individual licensing cost. When you have to scale, you can scale as many licenses as you need to for development and for running the bots in production.
Which other solutions did I evaluate?
We evaluated Blue Prism and Automation Anywhere.
What other advice do I have?
There are two key things: one is to collaborate with the right UiPath partner. The second is to identify the right toolkit that will help you to get the ROI, especially when you want quick benefits or want to build confidence with the business.
I recommend that you have all use cases backlogged and then discuss these items with the stakeholders, business process owners, and business stakeholders. Then, get everything vetted by an implementation partner. Also, discuss with UiPath if required and then implement the processes.
On a scale from one to ten, I would rate UiPath Process Mining at nine.
Disclosure: I am a real user, and this review is based on my own experience and opinions.