UiPath Platform Reviews

We are using Orchestrator for both development and production. We are using attended and unattended bots, and we are using Studio to develop them.

We use this solution for front-office processes, back-office processes, IT processes, and automating anything that we can.

We run our automations inside a virtual environment. We use Citrix and Citrix Server. We have sixty-seven processes that we've automated to run in the virtual environment and its very straightforward. It's deployed out of Orchestrator, and for attended processes, it's as simple as going in, opening a UI robot, and clicking the start button. It's phenomenally easy.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would say that it's a five. It's very easy. I'm a software developer by trade and I was able to automate several processes in a very short time span. In two weeks I can automate an entire process, end-to-end, which is incredibly fast for the ROI.

One of our processes was extremely complex, which was our customer onboarding process. The complexity was, in part, because it is handled by six different departments. The PDD for it was one hundred and forty pages long. One or two we've done were simple automations, and the rest have been medium to high complexity.

My first robot went into production within a month of me being in my position. That included going through all of the UiPath training, getting familiar with our IT systems, and then actually vetting out a process and automating.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. It was very informative and very detailed.

We are using the unattended robots more than we are the attended ones, and we're trying to continue that drive. We understand that there's a need for some processes to run attended, but if we can, we do process optimization to make it work and be unattended.

We have definitely seen savings in time. I can only speak to one particular instance, which is one that I automated. It was taking a product marketing team roughly an entire month to process, so they were always a month in arrear processing invoices for orders. When we developed this quote-to-order process, it saved us something along the lines of seven thousand hours per month for the one group. I was able to shrink down what a team of twelve people was doing in a month's time, to about seven days.

Unattended robots are my favorite because it allows us to completely remove a process from a person's day. The process can be fully automated and scheduled out of Orchestrator to run. Whether it's several times a day or once a month or whatever it may be, that user no longer has to worry about whatever that task was.

I would like to see support for native C# capability. I have a .NET background, so it's easier for me to write in that language.

With respect to the stability, on a scale from one to five, I would rate this solution a four. There are some issues we've run into where we just can't exactly figure out what is causing the problems.

A robot would run through a process two to three dozen times with no issues and then on the very next run, it will stall in the middle of the process. When we tried to debug it, we can actually replicate that stall but clearly, it's not throwing an error. There's no rhyme or reason to why. It just stops and it just kind of hangs. I would say that it may be a stability issue.

The technical support for this solution is great. They're responsive, and always willing to help. We got infrastructure support to help us through an upgrade so I could actually migrate everything from our on-premises server into Azure. I would rate their technical support a ten out of ten.

This solution started as a homegrown operation by one of our satellite offices that downloaded a trial license and started using it. Once our IT department found out, we hired Deloitte to come in and talk us through the whole process. Then, Deloitte left and we started our own kind of homegrown development. The did not actually deploy it with us.

Prior to choosing UiPath, we evaluated Automation Anywhere and Blue Prism. There may have been one more, as well. We are a very large SAP shop, and UiPath was the only one that touted that it was integrated well with SAP. For the most part, it did.

For anybody researching this type of solution, I would suggest that they try this out and they will instantly see the value.

I would rate this solution a ten out of ten.

We are using Orchestrator and Studio and we are using both attended and unattended robots.

We use this solution in the compliance space to manage risk.

We do not run our automations in a virtual environment.

With our first process going into production just last week, we are just new to RPA. The RPA involvement across our organization is very small given our stage of development, with less than ten people. These are both developers and business users.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would say that it's about a three. The software itself is relatively straightforward and easy to use. However, the task of automating processes can be challenging. Each company is going to be different than others. My experience tells me that process automation perhaps is not as straightforward as businesses may think it is.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. I found the training at the UiPath Academy really good and easy to understand. We were able to download trial versions of the software and apply our training to the trial versions. It is very straightforward and easy for .NET developers to actually use the tools. They felt comfortable, and there was nothing new, just a different way of doing what they do.

My company is probably not a good example of judging how long it takes to build your first robot. We implemented the system and did the process at the same time. So, combined, it took several months. Going forward, because we're no longer putting a system into place, I expect that timeframe to shrink significantly.

Given that the processes were just implemented at the end of last week and the beginning of this week, we have not yet seen the benefits in terms of cost-saving, time-saving, or a reduction in human error.

Enhanced capability in the document management space would be a huge benefit to our organization. As part of our business process, we receive a high volume of returned documents. Managing that high volume, in the millions, can be a challenge. If we had inherent, out of the box tools to drive document manage principles, that would be advantageous for our business.

With respect to the stability, on a scale of one to five I would rate this solution a five. We have not incurred any stability challenges as of yet.

We did not use another RPA solution prior to this one.

I think that the industry as a whole is going in this direction. Knowing the industry as well as we do, we thought it product to get involved with RPA.

The initial setup of this solution was straightforward. The underpinning technology is familiar to us.

We performed the implementation ourselves.

I was not involved at this stage, so I am unsure whether other solutions were evaluated.

My advice to other companies who are looking into UiPath is to document how you do what you do. Document your processes first.

I would rate this solution an eight out of ten.

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. 

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.

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.

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.

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.

We have approximately twenty people involved in the automation side of the business, but it's growing rapidly.

I have not used technical support other than the online forum.

This was our first RPA implementation.

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.

We deployed the solution ourselves.

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.

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.

We are using this solution for a POC and Pilot stage for RPA deployment.

Ease of deployment means that business benefits can be developed quickly and easily.

The most valuable feature of this solution is the Studio.

Additional help with ROM and approach would be an improvement.

I use this solution for the automation of Accounts Payable invoices.

This solution has improved business by facilitating increased speed and accuracy.

The most valuable feature of this solution is capturing information.

I have identified two issues that have to be improved:

• It was necessary to use native PDF rather than a scanned PDF document to improve accuracy.
• Templates had to be created for different formats.

Getting data from the SharePoint site and processing the data with business logic, and after this, inserting the data one by one into the QuickBase site. The environment was development, QA, and production. We are working for back office automation so work with Microsoft office products.

UiPath RPA process reduced manual work, improved work efficiency, decreased human mistake and increased scalability by using unattended bots. use orchestration for attended and unattended robots and for centralize control the environments . Handle daily jobs.

The OCR feature is the most valuable for processing PDFs, images and the Citrix environment.

LINQ and Lambda expressions should be included fully.

The primary use case is for a medical claims process automation using UiPath RPA.

• Streamlined the medical claims process. It reduced errors by 30 percent.
• Improved user productivity by 50 percent.
• Turnaround time for claims payment has been reduced from 120 days to 30 days.

It is easy to manage the robotics environment with Orchestrator, including scheduling and reporting.

Optical character recognition for hand written documents could be improved.

We are checking products in search of a better RPA solution for our landscape.

This solution has increased productivity in our organization.

The most valuable feature is its ease of use.

Better alignment of workflows for development is needed.