What is our primary use case?
We are using the attended, unattended, and Orchestrator components of this solution.
Our primary use case is developing automation around revenue cycle management in the healthcare space.
We run automations in a virtual environment and we are very happy with that ability. It is much more time-consuming when compared to running it directly on the server, but it is very reliable and it is a great way to create automations that you wouldn't otherwise be able to create. Of course, we prefer to go directly to the same environment.
With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a four. In order for me to give it a five, it would have to be such that a user could go in and develop it easily with a point and a click. I think it would be extremely difficult to build a platform that was that simple for the end-user, but I think UiPath has come a long way and is very good at making it easier and easier as we go along.
We have at least ten developers who have gone through the certification training with the UiPath Academy. On a scale of one to five, judging how beneficial it is, I would rate the training four and a half. The training is wonderful. There are certain elements of the training platform that are not keeping up with the product though. Also, some of the things that are in the documentation are not up to date. Being a little outdated, it can be kind of frustrating for the people that are going through it. But, it's a great way for people to get a good understanding of how to use all of the elements of the process.
From the point that we purchased our UiPath license until we had our first robot was approximately three weeks.
How has it helped my organization?
In terms of eliminating human errors, they are one hundred percent gone. When we build the bots we build them right, and there are no more human errors.
With respect to saving time, for the processes that we have built, it saves at least ninety percent of the time that humans were taking. We have to have somebody that monitors the bots. In case they stop, they have to start them up again.
What is most valuable?
We are a development shop for UiPath, so we use the Studio all day long.
We really like the Orchestrator and how I'm able to see what's going on with all of the different automations.
What needs improvement?
On the development side, more documentation on how to structure the setup for different environments would be helpful. Our biggest struggle had to do with questions like:
- Do I need to have fifty monitors to run fifty different bots?
- Do I need to have fifty separate computers around fifty different processes at the same time?
There was no really good documentation to teach us how to do that, so there was a bunch of trial and error involved in figuring it out.
We know that we didn't want on-premises computers, but we didn't have any documentation to explain how to set them up in the cloud. We went through several different iterations before we finally got that right.
Ultimately, it took us about three months before we decided on the structure that we wanted, so better documentation on infrastructure would be very helpful.
For how long have I used the solution?
We have been using this solution for about eighteen months.
What do I think about the stability of the solution?
The product, itself, is generally very stable. On a scale from one to five, I would rate the stability a four. We do have situations where we've run some updates and then ended up with some OCR things breaking on us. But overall, we build automations for our customers and they don't really know that there are any problems whatsoever, because they're generally pretty easy to resolve.
What do I think about the scalability of the solution?
We have approximately twenty people involved in the automation side of the business, but it's growing rapidly.
How are customer service and technical support?
I have not used technical support other than the online forum.
Which solution did I use previously and why did I switch?
This was our first RPA implementation.
How was the initial setup?
The initial setup of this solution is straightforward. It just works. You download it from the cloud and install it on your computer. You might have to update your .NET framework, so make sure that it works. It is very visual and very intuitive, so you're up and running in no time with Studio. With Orchestrator, it takes a little bit of getting used to in terms of matching up Orchestrator with the computers that it's linked to but it took hardly any time for us.
What about the implementation team?
We deployed the solution ourselves.
What was our ROI?
We have seen benefits, but I would say that it took us longer than most because initially, we were building through an RDP connection. We were also connecting to a software platform that is inherently slow. Between these two things, it took a lot of extra work to get it running and recognizing all of the images and stuff like that.
I can say for sure that we've seen savings on efficiency and labor for performing the tasks that we've automated. As a result of that, we've invested a lot more in training developers and building their skills. We're cash negative on the deal, but it's because we believe in the product. For the processes that we are actually doing, we are seeing savings right away, which is why we're investing more in UiPath.
What other advice do I have?
For people who are researching this type of solution, I would suggest that they test all of them out. All of them give you an opportunity to try them. We initially made our decision to go with UiPath after looking at Automation Anywhere and Blue Prism. One of the primary factors that drove us to UiPath was developer feedback. Asking developers what platform they would choose to develop on, all of them said UiPath because it's very flexible and very intuitive. A lot of people are familiar with the .NET framework, so it's easy.
My advice for anybody who is implementing this solution is to first speak with people who have already deployed it in a similar type of target environment. Once you know how to set it up, it's easy. It depends on the infrastructure that you want, or need, for your organization. Otherwise, it's just going to be a bunch of trial and error.
From a cost perspective, the unattended bots are obviously much cheaper than the attended bots. However, to build a bot to automate a process where an unattended bot can run it is also more costly for the end-user. For us, it makes more sense to have attended bots. We also have access to a very low-cost labor pool. Because of that, it's cheaper for me to just have somebody monitoring the bots, running them manually.
Overall, this solution is awesome. I'm very excited about all of the new things. We've been doing automations for about eighteen months, and with the product from that time, to where we are today, many new things have come in. I mentioned the problems that we had with the RDP connection but Computer Vision comes out, and it makes things much easier and much more reliable. Fortunately, all those have now switched over to running directly on the servers where we're running the software, so the need for us has gone way. At the same time, I have used Computer Vision and it's great.
I would rate this solution a ten out of ten.
Start Your UiPath Free Trial
Accelerate your digital transformation now with free access to the UiPath Platform