We just raised a $30M Series A: Read our story

UiPath OverviewUNIXBusinessApplication

UiPath is #1 ranked solution in best RPA tools. IT Central Station users give UiPath an average rating of 8 out of 10. UiPath is most commonly compared to Microsoft Power Automate:UiPath vs Microsoft Power Automate. UiPath is popular among the large enterprise segment, accounting for 61% of users researching this solution on IT Central Station. The top industry researching this solution are professionals from a computer software company, accounting for 28% of all views.
What is UiPath?

UiPath is leading the “automation first” era – championing a robot for every person and enabling robots to learn new skills through AI and machine learning. Through free and open training, UiPath is led by a commitment to bring digital era skills to millions of people around the world, thereby improving business productivity and efficiency, employee engagement and customer experience.  The company’s hyperautomation platform combines the #1 Robotic Process Automation (RPA) solution with a full suite of capabilities that enable every organization to scale digital business operations at unprecedented speed. The company has already automated millions of repetitive, mind-numbing tasks for businesses and government organizations all over the world including approximately 50% of the Fortune 500.

UiPath was recently recognized as the top company on Deloitte’s Technology Fast 500, a ranking of the fastest public and private technology companies in North America, was recently featured in CNBC Disruptor 50, and #3 on the 2019 Forbes Cloud 100.

UiPath Buyer's Guide

Download the UiPath Buyer's Guide including reviews and more. Updated: November 2021

UiPath Customers

Airbus, Bank of America, Berkshire Hathaway, Chevron, CVS Health, DHL, General Electric, Google, Lufthansa, NASA, NTT, Orange, Philips, Singtel, Spotify, The Home Depot, Toyota, Uber, United Airlines, UnitedHealth Group, Wells Fargo

UiPath Video

Archived UiPath Reviews (more than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
YAWANTWI-ADJEI
Data Visualization Specialist at Data Catalyst
Real User
Top 5
Automated data scraping and entry helps to shorten customer service time

What is our primary use case?

My primary use case is data scraping and entry for an insurance firm.

How has it helped my organization?

This solution has gives us shortened customer service time. It is easy to use and a lively community is always ready to help resolve an issue.

What is most valuable?

The most valuable features are PDF, Excel automation, and web scraping. The Try-Catch feature is awesome.

What needs improvement?

The emailing and integration with self-service BI systems are areas that need improvement.

For how long have I used the solution?

I have been using UiPath for eight months.

What is our primary use case?

My primary use case is data scraping and entry for an insurance firm.

How has it helped my organization?

This solution has gives us shortened customer service time. It is easy to use and a lively community is always ready to help resolve an issue.

What is most valuable?

The most valuable features are PDF, Excel automation, and web scraping.

The Try-Catch feature is awesome.

What needs improvement?

The emailing and integration with self-service BI systems are areas that need improvement.

For how long have I used the solution?

I have been using UiPath for eight months.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PG
Robotics & Process Efficiency Manager at Ageas
User
A powerful and easy-to-use solution for fast process automation

What is our primary use case?

Our primary use is RPA in insurance.

How has it helped my organization?

This solution has given us the fast automation of processes.

What is most valuable?

The most valuable features of this solution are that it is powerful and easy to use.

What needs improvement?

The operations need to be improved.

For how long have I used the solution?

I have been using this solution for two years.

What is our primary use case?

Our primary use is RPA in insurance.

How has it helped my organization?

This solution has given us the fast automation of processes.

What is most valuable?

The most valuable features of this solution are that it is powerful and easy to use.

What needs improvement?

The operations need to be improved.

For how long have I used the solution?

I have been using this solution for two years.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about UiPath. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
554,529 professionals have used our research since 2012.
HT
RPA Developer at a tech services company with 1,001-5,000 employees
Real User
Academy training and session recording help you get started right away

Pros and Cons

  • "The most valuable feature of this solution is the training that is available."
  • "I would like to see more features included in the AI Fabric."

What is our primary use case?

I am a developer so I primarily use Studio. Once the bots are developed they go to Orchestrator.

We have a combination of different use cases. Sometimes it deals with Outlook, the Microsoft Office Suite, or certain integrated web applications. You build a solution to integrate all of the applications that are part of the same process.

We do not run our automations in a virtual environment at the moment, but we are currently evaluating how we can do this.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. The majority of the simple tasks are done through recording, which saves on our development time. You just record the things that you want to achieve and then customize to get it going.

Since I was new to the product, I used the training. I took the developer training, as well as business analyst training. On a scale of one to five, judging how beneficial it is, I would rate the training a five. It's truly very beneficial because you can just touch base with the actual tool and get it done.

From the point that we purchased our UiPath license until we had our first robot was approximately six weeks. This was a complex use case and it worked well, so it was a good proof of value.

How has it helped my organization?

Prior to using this solution, everything was running well, though users were facing challenges because they were spending a significant amount of their time correcting things that were misrepresented or not done correctly by some other part of the team. The consultant is supposed to correct or manage all of the changes, and it was not only taking a long time but not on their to-do list for the day. It is this extra time that this solution is being used to address.

In the pilot project, we have seen proof of value. However, it is not in production yet, so it is too early to see how much time this solution will save us. The people whose jobs will be affected are looking forward to this solution because we are expecting to cut their mundane tasks from eight hours a day to two or three hours a day.

In terms of eliminating human errors, I don't think that we have seen any difference.

What is most valuable?

The most valuable feature of this solution is the training that is available. You can just access the resources.

There is a Community Edition of this solution, which is a plus. Some other vendors do not offer this or have just started offering it. Accessibility is the biggest thing.

What needs improvement?

I would like to see more features included in the AI Fabric. This is the biggest thing that I am looking forward to.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four. There are certain features that are incomplete and they are still working on, such as computer vision. 

What do I think about the scalability of the solution?

We currently have about five people involved in the RPA team. It's the kickoff stage for us, and more like a COE.

Which solution did I use previously and why did I switch?

We did not use another RPA solution before this one.

We decided to invest because necessity is the mother of innovation. We were seeing our consultants spending too much time in processing certain areas of the business, and we wanted to find ways to make their lives easier and improve the processing.

What about the implementation team?

We had Roboyo assist us, and our experience with them has been pretty good so far. On a scale from one to five, I would rate them a five.

What was our ROI?

This is just a pilot project so ROI is not really in the grid. We hope to have a good ROI on the solutions that are deployed using UiPath.

What other advice do I have?

I look forward to trying the better features that will be released in upcoming versions.

My advice for anybody who is implementing this solution is to not only automate the process but redesign the process. If you have steps one through ten then you don't simply automate them "as-is". First, improvise your process and then try to automate that. It will save time and money.

This is a good solution and I am looking forward to the new AI features.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
MB
RPA Operations Lead at a energy/utilities company with 11-50 employees
Real User
Offers valuable training and has dramatically reduced processing time

Pros and Cons

  • "Compared to other solutions, training is very valuable. You can easily access the resources. There is a community edition which is a plus and something that other tools don't offer. Accessibility is the best feature."
  • "It interacts with so many products that the robot itself becomes unstable."

What is our primary use case?

I am a developer so I primarily use Studio most of the time, and when the bots go live, they move to Orchestrator.

We have a combination of different use cases. Sometimes it is dealing with Outlook or the Microsoft Office Suite. The idea is to build a solution that integrates all of the applications that are part of the same process.

We are not currently running our processes in a virtual environment but we are currently evaluating how we could make it work.

How has it helped my organization?

Everything was running well but the users had some challenges because they had to spend a lot of their day correcting the things that were misrepresented or not done correctly by another part of the team. The consultants had to manage the changes which were taking a lot of time but weren't on their to-do list for their day. UiPath is helping us save that time. 

It hasn't really helped to eliminate human errors. The processing time is dramatically reduced. It makes it easier for consultants to make things right. If they spent eight hours doing a task, it now takes them two. 

What is most valuable?

Compared to other solutions, training is very valuable. You can easily access the resources. There is a community edition which is a plus and something that other tools don't offer. Accessibility is the best feature. 

I would rate the solution's ease of use as a five out of five. The majority of tasks are done through the recording which saves development time. You just record the things you want to achieve, customize it, and get it going. This reduces development time. 

I have been using RPA training since I was new to the product. I did the developer training. I would rate it a five out of five. It’s very beneficial. You can just touch base with the actual tool and get it done.

It hasn't really reduced human errors but it has reduced the processing time. It's easier to make things right.

What needs improvement?

I would like to see more of the AI Fabric domain feature. 

What do I think about the stability of the solution?

It interacts with so many products that the robot itself becomes unstable.

I would rate the stability as four-ish out of five. There are some features that they are still working on. There will be better features in the upcoming versions.

What do I think about the scalability of the solution?

We have around five users. We're in the kick-off stage so not many people are involved. 

How are customer service and technical support?

I have not needed to contact technical support. 

Which solution did I use previously and why did I switch?

We knew we needed to invest in a new solution because necessity is the mother of invention. We saw our consultants spending too much time processing areas of the business, so we knew we needed to evaluate new processes to make their lives easier. 

We chose UiPath because of the accessibility. It's easily available and widely used. 

How was the initial setup?

It took us around six weeks from when we purchased our first license to having our first Robot in production. It was not a complex process.

What about the implementation team?

We used Roboyo for the implementation. We had a good experience with them. I would give them a five out of five. 

What was our ROI?

ROI is not on the grid right now. We hope to have a good ROI. It's a proof of value and it's not in production yet. 

What other advice do I have?

With the existing features, I would rate UiPath an eight or nine out of ten. Once the new features come in, I would give it a ten. They keep improvising. 

I would recommend not only automating the process but redesigning the process. It's not just about automating steps one to ten, you need to improvise your process and then try to automate that. Automating the steps as is won't really help and you can end up spending the same amount of time and money. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
AR
Senior Manager at a financial services firm with 10,001+ employees
Real User
Intuitive and logical solution that has some of the best training available

Pros and Cons

  • "We're able to handle some of our tax and HR processes, the volumes of the documents or new hires at a tremendous speed compared to how we used to do it manually in the past."
  • "I think in the Studio, as in building automations, it takes a lot of clicks and there's a lot of options and I think sometimes there's just too much. It should be more simplified on the user interface."

What is our primary use case?

We use Studio and Orchestrator. I personally use unattended bots but we're releasing one of the largest attended implementations right now.  

For the most part, it's still in the back office, finance, and accounting, that's typically where we've been starting. That's where for me, as an inexperienced developer, is easier for me to get started.

How has it helped my organization?

We're able to handle some of our tax and HR processes, the volumes of the documents or new hires at a tremendous speed compared to how we used to do it manually in the past.

What is most valuable?

I like the layout and design of the Studio using the RPA framework. It makes sense to me. It's very easy to get started. I've been a fan of the current debugger. I know that UiPath is releasing an updating debugger but I think that's been very intuitive for me as well.

I would rate the ease of use of the platform for automating my company’s processes a four out of five because, for me, there's still a lot of clicks and keystrokes I need to do for development. I know that UiPath is releasing StudioX, which is something that is needed, for people like me who aren't super technical.

I would rate UiPath Academy RPA training a five out of five. It's one of the best. Compared to its competitors, it's intuitive and it's robust.

It's everything that UiPath is moving forward towards, intelligent, machine learning, and AI. I embrace the fact that the direction it's going especially for me personally.

What needs improvement?

I think in the Studio, as in building automations, it takes a lot of clicks and there's a lot of options and I think sometimes there's just too much. It should be more simplified on the user interface.

What do I think about the scalability of the solution?

As far as our practice, we have over 150 consultants in the States and over 350 in India. We also have a team in Europe. Overall, we have over 3,000 RPA consultants. UiPath is probably close to about a third that would be UiPath competent.

How are customer service and technical support?

I haven't had to contact their technical support. I go through my SMEs. 

Which solution did I use previously and why did I switch?

We're always challenging ourselves to be more efficient and effective in the workforce. We also recognized that some of our businesses needed to do things better, faster and cheaper. RPA was a natural solution. For us, as a large organization, we want to learn about all of the top competitor solutions. UiPath is in the top-ranked quadrant regularly so it is an obvious choice.

Because of the market demands of Automation Anywhere, Blue Prism and UiPath, we had to invest in learning all three equally. I don't know the exact reason we went with UiPath, I can ask our clients. 

How was the initial setup?

The implementation process was easier than the competitors.

What was our ROI?

We have seen a 100% ROI. We do automation to deliver a faster ROI than traditional software. As a firm, we saved over 2 million dollars a year now from using RPA.

What other advice do I have?

Regarding both attended and unattended bots, I think there are places for both and it comes back to the purpose of what you're automating. I think attended is going to be great for the casual users of applications. It's a lot of the call centers and even some of the system developers. The unattended are places where you can really find those scaling volumes and processes. Typically back-office functions are unattended.

I would rate it a nine out of ten. There's always room for improvement. For me, it's very intuitive and logical. I grew up with a little bit more of a technical background so for me, it fits in well with my needs.

I would encourage someone considering this solution to use UiPath, especially if they're automated and especially with UiPath's new one-click cloud solution. It's so fast for them to get started. I would encourage them to be up and running in the same database to try it out.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
HB
Chief Health Informatics Officer at a government with 10,001+ employees
Real User
Has the ability to schedule tasks and Orchestrator centrally manages our bots

Pros and Cons

  • "The product helps achieve efficiency that will create ROI and the training and support are very good."
  • "Incorporating more in the way of machine learning and AI would extend the capabilities of the product."

What is our primary use case?

We use Orchestrator, Studio, and of course the bots for indexing documents received from outside providers.

How has it helped my organization?

The best example of the way this product has improved how our organization functions is by the increase in efficiency it has helped us achieve.

What is most valuable?

The most valuable features are the ability to schedule tasks and using Orchestrator to centrally manage our bots.

What needs improvement?

Areas of this solution that have room for improvement are a couple of activities that have issues. We would like to incorporate machine learning so that we can do some of the quality checks that we do automatically instead of relying 100% on manual quality review by humans.

Additional features that we would like to see included in the next release are those they seem to already have planned. I am very intrigued by the AI capabilities that we saw in demonstrations. Having that capability would be absolutely fantastic.

What do I think about the stability of the solution?

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of UiPath platform as about a four. There are two activities that we use that fail about 5% of the time. UiPath is fixing that — as far as we understand — and so we should get a solution very soon.

What do I think about the scalability of the solution?

We currently have just two people in our organization involved in the automation program. That could potentially expand under the right circumstances.

How are customer service and technical support?

Our team has had the opportunity to use the UiPath Academy RPA training. On a scale from one to five where one is the least beneficial and five is very beneficial, I would rate the UiPath Academy in training our team as a five-out-of-five. We literally started at ground zero with UiPath software, and, without the training, I don't think we would know exactly what it can do.

I also think the source support and technical support for this solution are both very good.

How was the initial setup?

From the time we purchased our UK UiPath license until we had your first robot in production was really before purchase. We had a proof of concept opportunity prior to purchasing the product, so we could make sure it worked for our purposes.

The initial setup process was straightforward. We started with just Studio, and not Orchestrator. Our deployment was just a simple matter of installing Studio. It was very simple to install.

What was our ROI?

We have not seen a return on investment in a way that we can account for exactly because we have not done that evaluation. At this point, we have projected some ROI numbers but we don't have the final ROI. I think it did not take long to see the ROI as it didn't take months. It probably just took a few days to see a difference.

The performance benefits we have seen at this stage of our deployment is in the form of increased productivity. So, in our development processes, we have at least doubled the performance of the process we have automated.

The solution also helped to eliminate human errors. I really don't know the percentages we have not done that evaluation, but I know it does eliminate them as it is evident in the results.

On top of that, the solution saves our organization time which is also evident in the fact that the staff members who are using the bots can double their performance.

What other advice do I have?

On a scale from one to five with one being the most difficult and five being very easy, I would rate the interface of the UiPath platform as a four-out-of-five. I chose that rating only because our legacy software is a bit difficult to automate. The selectors end up not always being accurate.

On a scale from one to ten where one is the worst and ten is the best, I would rate the product overall as a nine. I don't think I have enough understanding to give it a ten. However, it seems from our investigation of other platforms, that UiPath is one of the easiest RPA systems to learn and use.

My advice to anyone considering RPA as a solution is to do your homework upfront. Learn what the platforms can do before you just pick one and start trying to automate.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
KF
Health Systems Specialist at a government with 10,001+ employees
Real User
Doubles productivity in records processing with high industry compliance

Pros and Cons

  • "An example of how this product has improved the way our organization functions is that it has doubled the number of records that we process per hour."
  • "We have had some problems with processing errors, but these are largely due to our legacy system and UiPath is working to help resolve the issue."

What is our primary use case?

We are using Studio, the Orchestrator, and both unattended and attended bots. We are using the product primarily to index and process patient records into patient charts when records come in from outside sources.

How has it helped my organization?

An example of how this product has improved the way our organization functions is that it has doubled the number of records that we process per hour.

What is most valuable?

The most valuable feature for us is the unattended bots. They are valuable because records come in automatically from the vendor with a cover sheet, and that cover sheet has a QR (Quick Response) code. An unattended bot will take the record, and based on the code can index it and upload it to the patient's record with no human intervention.

What do I think about the stability of the solution?

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of the UiPath platform as three right now. There are some nuances in it that are throwing some error codes when reading the QR codes. But we are in the process of working with UiPath to get that issue corrected.

What do I think about the scalability of the solution?

Right now we have about five people in our organization involved in the automation program. We can expand that as necessary.

How are customer service and technical support?

Our team used UiPath Academy RPA training. Two of the individuals on the team have gotten their certifications.

On a scale from one to five where one is the least beneficial and five is the most beneficial, I would rate the UiPath Academy as a four. The team really liked it. The two people that have certification are our two main developers. They had been doing their academy in concurrence with our deployment while they are still working on the project. They both said the academy has been very helpful.

We also have a customer support person dedicated to us. They call them Customer Success Managers. We use them and then we have also had to reach out to the home office in Romania. They are working on a solution for us right now. The service, on the whole, is very good.

Which solution did I use previously and why did I switch?

I was part of the decision process in choosing UiPath as our RPA solution. We had not previously been using another solution but knew that we needed to invest in one because we looked at our employees' overtime records. We were paying for overtime and did not see the need to just for scanning and indexing. A bot can run 24/7, so the bot takes care of processes that can be automated instead.

How was the initial setup?

The initial setup process was complicated because of us and the requirements of our organization. It was not because of UiPath. But even with those complications, from the time we purchased the UiPath license until we had our first robot in production took only about three months.

What about the implementation team?

We did not use an integrator, reseller, or consultant for the deployment. We used internal staff and the UiPath engineers helped us along.

On a scale from one to five where one is very bad and five is excellent. I would rate our experience with UiPath as a five. They have been very responsive and have given us engineering support at no cost. They seemingly did that just to ensure that we were successful.

What was our ROI?

We are starting to see a return on investment. It has only taken us about a month to realize that. Basically, we have seen a performance benefit. Where it was taking a human about an hour to do ten records, we have estimated that we are going to be able to up that count to about 80 records an hour. One of the humans that is doing the manual part of it has already said that the product has helped double their workflow. The solution has also helped to eliminate human error by approximately 85%. I would say that it is going to save us at least 40 hours a week right now. I also think that is a conservative estimate.

What's my experience with pricing, setup cost, and licensing?

For our licensing cost with this solution we have invested $90,000 right now, but that is to cover several facilities. The UiPath solution is not expensive considering that.

Which other solutions did I evaluate?

UiPath was the only RPA solution we looked at. They are TRM (Technology Reference Model) approved and they appeared to have the best platform.

What other advice do I have?

On a scale from one to five where one is very difficult and five is very easy, I would rate the ease-of-use of the platform for automating our company's processes as a four. The UiPath product has fit our model the best. Number one, because in the VA (Veterans Affairs) hospitals the RPA solution has to be TRM approved and not all RPA solutions are. They have also been very helpful because we have a little bit of a unique system. There are some nuances in an older system that we are still using that can not be changed at the moment. They have helped us work around those issues and they have provided the technical support that we needed.

On a scale from one to ten where one is the worst and ten is the best. I would rate the product overall as a nine. From everything that I've heard from the staff, the ease-of-use and the effectiveness of it are really good.

If I were to give advice to a colleague at another company who is researching RPAs, I would tell them to go with UiPath because of the product and the culture of the company. I think the culture of the company is one of the reasons that you are going to ensure that you will be successful.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Jeremy Rank
Application Support Engineer at Centene Corporation
Real User
Unattended robots completely take tasks out of the user's hands so users don't have to spend time doing mundane things

Pros and Cons

  • "Unattended robots completely take tasks out of the user's hands reducing error and unnecessary effort on mundane tasks."
  • "While it is still the best, the usability for end-users without programming experience can be improved."

What is our primary use case?

We use Orchestrator, Studio, and Robot to work with automation in our finance department.

How has it helped my organization?

The product improves how our organization functions by automating tasks so users aren't having to spend time doing mundane things.

What is most valuable?

The most valuable feature is the unattended robots as they completely take tasks out of the user's hands.

What needs improvement?

In the next release of the solution, I'd like to see process mining to analyze business processes through event logs. It would help the end-users determine what processes need to or can be automated.

As for areas of the solution that have room for improvement, the usability for the end-users could improve so that they will be better able to program on their own. Coupled with process mining capabilities, that could remove the need to involve programmers or IT in the automation of simple tasks. The cloud platform could be improved so we would be able to deploy through that with sufficient security.

What do I think about the stability of the solution?

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of the platform as a four. It is a four because I haven't seen any outages yet but we may need more experience with the product to be sure it is totally stable when we are completely live.

What do I think about the scalability of the solution?

We have about four people are in our organization who are currently involved in our automation program and I can see that expanding as the company improves ease-of-use.

How are customer service and technical support?

Our team has used UiPath Academy RPA training. On a scale from one to five where one is the least beneficial and five is the most beneficial, I would rate the UiPath Academy RPA training as a five. It is very good and very detailed.

We have also used customer support and it is good. When I called in they were helpful with answering questions that I had and they responded quickly. Usually, we had one person assigned to us that kind of helped us implement and who was familiar with our needs. This helped in several cases.

Which solution did I use previously and why did I switch?

I was involved in the decision process to move to UiPath. We knew that we needed an RPA solution to take care of repetitive tasks that could be automated and we had been using solutions in other departments. We went through an RFP (Request for Proposal) process when the finance senior leadership wanted to see what RPA was about and how it could help in their processing. UiPath was one of three products that made it to the next stage of evaluations for this use case.

We did simultaneously use a different solution, which was Pega. UiPath was actually already being used in the company but the idea was to expand into the finance processes.

How was the initial setup?

The initial setup process was straightforward. The complexity that we met with was because of the requirements of our own company. The setup, as far as the installation, was straightforward and simple. From the time we purchased the UiPath license until we had our first robot in production was about three months.

What about the implementation team?

We did use a consultant for the deployment. The company was PwC (PricewaterhouseCoopers International Limited). On a scale from one to five where one is very bad and five is excellent. I would rate our experience with PwC as a three. They are not rated higher in our case because they didn't provide us with the best resources. They sent a younger team that seemed not to have really ever used UiPath.

What was our ROI?

We have only projected a total for return on investment and performance benefits from the solution through testing and past performance as we are not fully live yet. It will probably take six months to see the actual ROI when we know more about the performance benefits of full deployment. The solution has already helped to eliminate human error by about 25% and has saved our organization approximately 2,000 hours.

What's my experience with pricing, setup cost, and licensing?

As far as pricing, I don't know what the company spends on the license. I do know about the robots. I think the attended robot is a little bit too pricey. With the unattended robots, we can put them on virtual machines — not really Citrix but regular virtual machines which are a little bit cheaper.

Which other solutions did I evaluate?

The vendors who were on our shortlist were UiPath, Pega, Automation Anywhere and Blue Prism. We chose UiPath because we already had the product in-house and we had already gone through all the security checks for the company requirements.

What other advice do I have?

On a scale from one to five where one is very difficult and five is very easy. I would rate the ease of use of the platform as a three-out-of-five. I give it that rating rather than going a bit higher because it is a little bit difficult for the regular users to automate. In some cases, you have to be more of a programmer to automate successfully. Even so, it is better than other RPA tools.

On a scale from one to ten where one is the worst and ten is the best, I would rate the product over-all as an eight. It gets the job done, but there is still a lot of room for growth in the capabilities so that is why I think that eight is a justifiable rating.

The advice I would give to a colleague at another company who is researching RPA solutions is to read up on what RPA is and what it can do for your company. That is where I would start. Then try to go to as many meetups or conferences as you can to find out more about the products and how they are being used.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
AW
Business Analyst at a renewables & environment company with 1,001-5,000 employees
Real User
Reduces the need for manual intervention which has saved us time and increased ROI

Pros and Cons

  • "Its intuitiveness is great. This solution is very user-friendly. There is almost no need to have programming knowledge."
  • "The initial setup was in between simple and complex."

What is our primary use case?

We use this solution for our business purposes. We use it from the back end all the way to the front end. That's where we are looking to use this, although we haven't fully implemented it yet. We are exploring more processes to use it for.

How has it helped my organization?

Mainly, this solution has reduced the need for manual intervention. That's the main thing. It has saved us time. We can now increase our ROI.

We run a few automations in a virtual environment, but not all of them. I've been using some other automation tools, like QTP/UFT.

I would rate the ease of use of the platform for automating our company's processes as four out of five.

What is most valuable?

Its intuitiveness is great. This solution is very user-friendly. There is almost no need to have programming knowledge.

The solution has helped us eliminate human errors, by about 40%. It also saves us time.

What do I think about the stability of the solution?

The solution is fairly stable. I would rate it as four of five for stability.

What do I think about the scalability of the solution?

So far, we have almost 50 people in our organization involved in our automation program.

How was the initial setup?

The initial setup was in between simple and complex. As even my colleague was fairly new at that time, he came across a few challenges. However, he could overcome them and now I'm in three of the processes that are in products.

It took about three months from the time we purchased a UiPath license until our first robot was in production.

What about the implementation team?

We used a consultant. I would rate them as four out of five.

What was our ROI?

We have definitely seen a performance benefit. Now that it is in the production processes, we are able to see ROI, in terms of saving time on repetitive tasks and the manual effort saved. That's our return on investment.

What other advice do I have?

I would rate this solution as eight out of ten because it has saved us a lot of manual intervention, as well as time and money. We may have not yet explored the full horizon of what this solution can do for us.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
GunjanSharma
RPA Lead at Slalom Consulting
Real User
Human and robot interaction happen seamlessly with Attended bots

Pros and Cons

  • "They've got the bolt on the market, so even with the new launches that happen with some of the new tools that came in, I think Connect really speaks to an overall automation strategy. I think that sets it apart."
  • "I talked to the product team. They are very passionate about this. In my opinion, all the different components that they have now released should be integrated under a single umbrella, available through a single landing page. That way, everything integrates with each other and they are able to communicate data back and forth. To me, that would be the ultimate solution."

What is our primary use case?

We're a consultant, so we help customers use this solution to develop automation and help set up COE. We provide the means for an entire organization to build its use cases. That's how we use Orchestrator both attended and unattended.

How has it helped my organization?

The solution has helped eliminate human errors. The amount varies by specific use case, but it is sometimes 50% to 60%.

It has also saved organizations time. Internally, we're not at a stage where we've measured it. I would say right now it's not that great, but maybe 15 or 20 hours per person.

What is most valuable?

Orchestrator's value really comes from scheduling and jobs, where robots can trigger other robots. I can't speak to the new versions yet, but they all seem great. Attended is where the human and robot interaction can happen seamlessly. With unattended, some of the processes that were earlier so mundane are all being done without any human interaction, so that provides true end-to-end uninterrupted automation.

I would rate the ease of use for this solution as five out of five.

The UiPath Academy RPA training is awesome. It's top of the line, so I would also say that it should get a five out of five rating.

What needs improvement?

I talked to the product team. They are very passionate about this. In my opinion, all the different components that they have now released should be integrated under a single umbrella, available through a single landing page. That way, everything integrates with each other and they are able to communicate data back and forth. To me, that would be the ultimate solution.

I get it. There is a roadmap and it's a journey. Still, I would like to get to a place where everything integrates with each other. Now that we have all these different means that can help us enable a customer in their journey, making sure that they're integrated would truly add value. That removes the overhead of combining data from all these different sources.

What do I think about the stability of the solution?

I would rate its stability as five out of five. With any tool, there have been occasions when a job did not trigger or aborted, but that's been very rare in my experience.

What do I think about the scalability of the solution?

I would say we have more than 20 users. There may even be around 50 users, if not more.

How was the initial setup?

It was very easy to install this solution.

It does not take long from the time one purchases the UiPath license until they have a real bot in production. We do this mostly for our customers, but also for our own internal use case. We were able to get it done and up and running in weeks.

What was our ROI?

We have absolutely seen an ROI. The time to get an ROI varies from case to case. 

What's my experience with pricing, setup cost, and licensing?

Attended is fairly cheap. Anytime you bring in Orchestrator, that starts to become a little more expensive. I'm a little concerned about all the new SKUs that are coming in and the products associated with them. I am really interested in finding out if someone wanted a full product suite, what kind of money are they looking at annually.

What other advice do I have?

I would rate UiPath as ten out of ten. I've done implementations across tools, so I'm familiar with some of the other market leaders too. Honestly, though, UiPath is very good at keeping up with the times. It's easy to implement. Its ease of use and how quickly you can get set up and going stands out, in my view. They've got the bolt on the market, so even with the new launches that happen with some of the new tools that came in, I think Connect really speaks to an overall automation strategy. I think that sets it apart.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
KY
Consultant at a financial services firm with 501-1,000 employees
Consultant
Good scheduler, queues, and activities help us to save time on manual processes

Pros and Cons

  • "The most valuable features are the scheduler, queues, and activities."
  • "More Excel activities should be included."

What is our primary use case?

I use Studio, Orchestrator, attended and unattended robots.

My primary use for this solution is back-office automation in a banking environment.

We run automations in a virtual environment, both for development and production. The robots are implemented in a development environment first, which is connected to Citrix. Once the process automation is finalized, including deployment and UAT has passed, we move the same file from the development Orchestrator to the production Orchestrator in the production environment. Production is also in Citrix.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a three. We have legacy Oracle applications and I'm finding it difficult to find selectors for the older, legacy systems.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. Some of the lessons are really easy, whereas others are more difficult, but you need to finish everything, otherwise you cannot go further. This is what I didn't like about it.

It took approximately one month to implement our first robot. Prior to purchasing the license, we implemented our PoC using the Community Edition. That took three weeks. After that, my company bought the license and it took about a week to put into production.

How has it helped my organization?

With respect to saving time, we save a lot of manual hours by using automation. I would estimate that we save eighty hours per month, on average.

In some of our processes, it took an hour to run them and the resource used to have to watch them manually. They are now automated and running in unattended mode, and the resource is finding other activities to do. There are more than one hundred of these types of processes.

In terms of eliminating human errors, I would say that we have a ninety-five percent reduction in our rate of errors.

What is most valuable?

The most valuable features are the scheduler, queues, and activities. The activities are there for applications like Excel, Word, and Outlook.

What needs improvement?

More Excel activities should be included. We do have basic Excel activities, but we don't have ones to do things like add colors or formulas. For these types of operations, we always use custom objects and have to write custom code or pay for them.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four.

My automation is one hundred percent working in my dev environment; however, the same package is not working with one hundred percent success in the production environment. It's a ninety-eight percent success rate, because sometimes there is a network issue, like slowness, and it's breaking my automation.

What do I think about the scalability of the solution?

We have eleven people working in our automation group including process architects, developers, and testers.

How are customer service and technical support?

I would rate our experience with technical support a five out of five. Whenever I needed help on the infrastructure, or with development, they immediately responded and tried to solve the problem. In cases where it was not solvable, they would jump on a call and look at through our code to help us out.

Which solution did I use previously and why did I switch?

Prior to using this solution, we used both Blue Prism and Automation Anywhere.

When it comes to deciding the suitability for automation and the choice of vendor, we consider the results of the process mining. We evaluate how many hours and how much money will be saved. We also consider how frequently the automation will be run, such as quarterly, monthly, or even daily.

One of our clients did not like the support from Blue Prism, which is why we jumped onto UiPath and implemented it.

How was the initial setup?

The initial setup of this solution is complex. We began immediately with a setup for high availability, but somehow we messed it up. We did not have the proper documentation and ended up getting help from UiPath.

They helped us, but overall, I would say that it is not straightforward.

What about the implementation team?

We implemented this solution in-house with support from UiPath.

What was our ROI?

We have not yet seen ROI from this solution.

What's my experience with pricing, setup cost, and licensing?

The licensing fees for this solution are $8,000 USD annually.

What other advice do I have?

Everybody says that this solution is easy to implement, but I do not find it that easy. It may be true for very simple processes, but not for more complex ones. For that, we need to have some kind of development and analytical skills. 

That said, from a code developer's point of view, I haven't found any difficulties with this solution. My advice for anybody who is considering this type of solution is to try UiPath.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Victor Sirianni
Business Intelligence & Automation Manager at a manufacturing company with 1,001-5,000 employees
Real User
UiPath allows us to not only automate but to also do new things that would have previously required an army to develop and execute.

Pros and Cons

  • "his solution has allowed us to tackle tasks that could not possibly be done by humans."
  • "The initial setup process seemed very complicated."

What is our primary use case?

We currently use an on-premise Orchestrator instance along with VDIs for Studio development, testing, and production Robots. We use UiPath in a few different ways: for repetitive high volume and or high complexity time-intensive tasks, for tasks with high error rates and or low error tolerance, and as a component in larger digital workstreams requiring the interaction of multiple systems and workers.

How has it helped my organization?

We are able to roll out customized sales reports for every appointment for all 400 of our sales agents, which is something that was not even feasible before. It could not possibly be done by humans alone without hiring an army.

What needs improvement?

We have been patching together a number of different solutions to try and create a more holistic automation solution. The newly announced features such as Long Processes, AI Fabric, and improved attended dashboard will go a long way in solving those needs.

For how long have I used the solution?

Eight Months

What do I think about the stability of the solution?

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of UiPath platform as a three. We had a lot of trouble initially, most of which was our own fault. Migrating all development, testing, and production, to identical virtual machines to ensure parity helped tremendously with stability and reliability. We still have to be very careful with selectors though and have learned to not trust the default capture particularly with Java-based applications.

What do I think about the scalability of the solution?


How are customer service and technical support?

I'd say the customer support is nothing short of excellent. We've had access to both technical and business experts as needed, and have regular conversations regarding challenges, successes, and the path to full-enterprise deployment.

On a scale from one to five where one is the least beneficial and five is the most beneficial, I would rate the UiPath Academy RPA training for our team as a four. It's no substitute for programming experience and computer science knowledge, but one of our Accounting Analysts and a Process Engineer each completed the first course and within a couple of weeks were producing basic automations. It's a fantastic entry point both for non-technical and technical users to learn about RPA and get up and building fast.

Which solution did I use previously and why did I switch?

Previously I've used Automation Anywhere and switched when changing companies.

How was the initial setup?


What about the implementation team?

Our infrastructure team handled implementation with considerable help from UiPath. On a scale from one to five where one is very bad and five is excellent, I would rate our experience with UiPath as a five. The service was excellent.

What was our ROI?

It took us about four months to see a return on our investment. In the last six months, we have saved about a hundred thousand dollars and we have freed up about five FTE (Full-Time Employees) of capacity.

What's my experience with pricing, setup cost, and licensing?

Plan to scale from the start! We initially deployed with a single-node on-premise configuration to test everything out and validate the business case. Six-months later and we now have to stand-up a new environment that is critical-process-capable (multi-site/cloud, load balancing, log monitoring, failover, etc) and has the capacity to handle the number of robots and users needed as we roll out enterprise-wide. It would have been more cost-effective and much easier on the infrastructure team to plan it all out ahead of time.

Which other solutions did I evaluate?

We evaluated BluePrisim, Automation Anywhere, and UiPath. Our Process Engineers and citizen developers really liked the flowchart-esque UI and the business leaders were impressed by UiPath's ability to build a PoC for one of our worst processes in just two days.

What other advice do I have?

On a scale from one to five where one is very difficult and five is very easy, I would rate the ease of use as a three. The flow is ideal for process-minded people and analysts, so they are able to navigate the UI and start building quickly. Our more advanced developers occasionally opine about the lack of an editor like interface and the need to click through a lot of UI elements to access more technical elements. Overall though, we feel it strikes a good middle ground, particularly when compared to other major competitors.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
FS
Senior Consultant at Vindelici
Consultant
Empowered users to change the way they were working which helped them save time

Pros and Cons

  • "Orchestrator lets you start a credential stair, so you can get the credentials in a safe way. Before this, they were afraid that credentials would be stored somewhere and people could see them. I think it's really important for our customers that you can do that in Orchestrator. The scheduling feature is also valuable of course."
  • "It's really hard for me to get all the machine learning and AI parts. I think maybe that's going to get a little bit easier for me to understand how to really use it in the company. I don't really know what to do with it at the moment. I think that is something that could be improved."

What is our primary use case?

I'm working for one project where we're trying to automate processes for a logistics company, specifically in their back-office accounting processes.

We're using Studio, Orchestrator and the bots. In other words, we're using the whole platform.

How has it helped my organization?

When we were implementing it, we were empowering people. In this company, everybody has their own work and they were really in their own area. Then we started this project and they got empowered to change the way they were working. UiPath is so open that everybody can take part in it.

That was one thing that changed right away. Another thing was the way they think about processes and where there are possibilities to automate has really changed. Before, they never thought about automating all these processes but we told them there is a possibility. Now, when they're having strategy meetings, they have dedicated time slots where they're just talking about processes that could be automated. The whole mindset is changing now.

We have a virtual environment that we use.

We haven't touched the processes where there would be human errors that much. We started with the really basic ones that are so easy that people don't make errors there. We will get to the more complex processes, but we haven't yet.

The solution has definitely saved time.

What is most valuable?

Orchestrator lets you start a credential stair, so you can get the credentials in a safe way. Before this, they were afraid that credentials would be stored somewhere and people could see them. I think it's really important for our customers that you can do that in Orchestrator. The scheduling feature is also valuable of course.

In terms of ease of use, I would rate this solution as four out of five. I think it's very easy, but our customers are sometimes not so technical. When they come from the business side, it's somehow hard for them to understand.

I would give the RPA Academy training program five out of five. Without it, I don't think I could have started implementing this solution. I did the developer program just for a general understanding of how everything works: how Orchestrator works and how it all works together. For me, it was really important to do the training then. It was very good, so I really liked it.

What needs improvement?

It's really hard for me to get all the machine learning and AI parts. I think maybe that's going to get a little bit easier for me to understand how to really use it in the company. I don't really know what to do with it at the moment. I think that is something that could be improved.

I tested the live sessions and we saw some parts of StudioX. There were some things that were so easy there. I think it would be good if they would put it also in Studio, for example. The carts they have are in color. We try to get people in the company, even if they're not technical, to implement the bots or processes by themselves. I think some parts they changed in StudioX could be really helpful in Studio skills.

What do I think about the stability of the solution?

I would rate their stability as three to four out of five, but I would say that's probably because we don't know how to use it best. That is why we sometimes have issues that something's not working.

What do I think about the scalability of the solution?

We are a consultancy firm but the customer that we are working with has about five people in the core team that are working with this solution.

How are customer service and technical support?

Both customer support and technical support are very good. I think the chief from my customer and the UiPath technical team had many phone calls because the virtual machine didn't work at first. They were in contact and I think two days later it was working.

Which solution did I use previously and why did I switch?

I can only speak for my client, who is undergoing a huge digital transformation. They're a small German company and they just know if they don't change something other companies will get ahead. In Germany, there are many family-owned firms and the owner just saw the need to change. We told them about RPA and they got very excited. We showed them the first pilot bot and they were set.

We chose UiPath, for the same reasons you can read on the internet. If you look at the Gartner and Forrester reports, I think they all say UiPath. Also, it's just so easy to get started. You just download the community edition and you're starting. Then you do the Academy and you actually know how to do it. It's very easy and very fast. All the statistics say it's the best.

How was the initial setup?

In terms of the setup, because we were using the community edition first, and then we licensed it afterward, we had the first bot running in about a month.

What was our ROI?

We have seen ROI and performance benefits. We are still at the beginning but we can definitely see it. I think we could see after about a week that we had processes that the company didn't have to do anymore and so they had more time. 

What's my experience with pricing, setup cost, and licensing?

So far, our first customer started with just Orchestrator and an unattended bot, along with a couple of studio licenses. I don't know the cost. Maybe $25,000 for the year.

I would definitely say it's worth the money.

Which other solutions did I evaluate?

We did a little research obviously. We looked at Automation Anywhere and Blue Prism, but that's it. We didn't really look too deep. We just saw UiPath and said, "Okay, I think that's a fit for us." And then we went for it.

What other advice do I have?

I would rate this solution as eight out of ten because of what I see from the stage we're in now. There are things that can improve and they are all working on improvement. I still think that at its current state, it's really beneficial for a lot of companies.

I would recommend UiPath. I like the company and I like their products.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Wayne Ahrens
Technology & Innovation Consultant at a engineering company with 5,001-10,000 employees
Real User
Has the ability to take data out of wherever we have it and translate it into customer-owned Citrix environments

Pros and Cons

  • "Having something that is very flexible like Studio X will make it possible to change with our environments very quickly, very easily, very nimbly, and to deploy and redeploy as needed."
  • "There is currently room for improvement in the area of ease-of-use."

What is our primary use case?

Currently, we're using Studio and soon to be using Orchestrator. We have not actually deployed any bots yet, but we have looked into both Orchestrator and bots. We have just looked at the solution set of that on why do we need to deploy in the future.

Our primary use will vary from department to department. We have what we call 11 global practices. These range across different platforms, but the underlying theme of that is we want to automate different items which might be finance or accounting or HR or whatever. But where I think it will be most useful is in our core business where I'm looking to apply it to engineering project management.

What is most valuable?

The most valuable feature for us has been the ability to take data out of where we have it — Excel sheets or wherever it may be — and translate it into customer-owned Citrix environments. Our primary core is engineering. A lot of our business requires us to take data what we have developed as part of the design process and relay that into work orders or other process triggers, ordering triggers, or material ordering, or different things for our clients. Allowing us to interface local data with Citrix environments is going to be a big deal.

What needs improvement?

I'm not exactly sure what I want to see enhanced yet. I know that we do a lot of small processes. Depending on how good Studio X is and how easy that is to build and manage we could potentially do a lot of small little things inside of various design tools like Excel, Word, and Outlook and to be able to kick out the workflows from that.

We like to do a lot of the design side locally for Excel, whether that be in a BBA or an add-in type environment. Being able to manage and deploy or build those will be helpful. Maybe we won't call them bots, maybe we call them processes that are centrally managed. In addition to the Microsoft stack, we use many other vendors like AutoCAD, Bentley MicroStation, Revit Inventor, BIM 360 and Autodesk Forge. To us, the CAD world is where we can see a lot of time savings and benefit ROI on a solution. That would be our next horizon.

I think this solution has room for improvement in the area of ease-of-use. It does require a little bit of coding background to be able to get in and really build out the solution. After I get in and look at Studio X a little more, I may change my opinion on that.

What do I think about the scalability of the solution?

We have six people working in the organization involved in our automation program. We are pretty confident that can scale easily.

What other advice do I have?

Since we have not deployed to production yet, we are not sure which direction we'll be going in. We were looking on-premises but the software as a service cloud deployment will likely be a hit with our IT department. We plan to run our automation in virtual environments through a Citrix interface but not in Citrix.

On a scale from one to five where one is very difficult and five is very easy, I would rate the ease of the use of the platform as a three or four for now. I saw some things today I'd like to dig into a little farther, and I think that that Studio X would make it a whole lot easier for citizen developers to get in and do small tasks. Rebuilding tasks for accounting and finance where there are fairly rigid rules will be great. In the engineering world, our interfacing with the clients sometimes changes on a weekly basis. So having something that is very flexible like Studio X will make it possible to flex and change with those environments very quickly, very easily, very nimbly, and to deploy and redeploy. So if Studio X is what I hope it is, that rating may be closer to a five than not.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
YZ
Associate Director at a government with 10,001+ employees
Real User
Attended bots help eliminate human error and duplication in data entry tasks

Pros and Cons

  • "Together, the aggregated features add value to the day-to-day operations of the business."
  • "I would like to see more options in terms of configuration."

What is our primary use case?

We are using UiPath Studio, Orchestrator, and attended bots.

We are automating 12 shared services processes. They are from the finance, HR, and procurement areas. These processes are run at a high frequency and are required to be captured on two different platforms. We have implemented this solution to stop entry clerks from having to do the same job twice, on two different platforms.

We run automations in a virtual environment and it is successful. The implementation was fast and we realized the benefits quickly. Currently, we have deployed three processes and we are going to roll out more processes in patches.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. Some of these processes have difficult exceptions that had to be handled, which is why we opted for the attended robots.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. The training is rich in content and the material, products, and methodologies are explained well. The concept of automation can be very easily digested by anyone, even if they are non-technical.

From the point that we purchased our UiPath license until we had our first robot was approximately a month and a half. I was not the person doing the configuration, but I managed the process through interaction with the technical team. It was a straightforward and easy process.

How has it helped my organization?

We have realized performance benefits through the use of this solution. We were able to decrease the processing time of one of the processes from 15 minutes, under certain assumptions, to one minute and four seconds.

One of the calculations that we have done to determine the time we have saved is for one type of process. It used to take 7,000 person-days each year but now takes only 160 person-days a year.

Using this solution has eliminated a lot of human errors. It is now done based on preset values, activities, and rules. Exceptions are properly handled and the robot will take the information from the source system, which is fundamentally correct all of the time. The robot only needs to capture the data as it is from the source, and copy it to the destination, and this eliminates the errors. When humans are in the middle of the process, mistakes can happen.

What is most valuable?

The design capability in Studio is great.

The way that you can monitor the robots within Orchestrator is helpful.

Together, the aggregated features add value to the day-to-day operations of the business.

What needs improvement?

I would like to see more options in terms of configuration.

More information should be made available on the AI Fabric features, and how it can be used as part of a larger ecosystem.

Unattended robots could be cheaper.

What do I think about the stability of the solution?

So far, we have not noticed any crashes or any issues with the platform itself.

What do I think about the scalability of the solution?

In total with the partner that we are working with, we have 12 team members.

Which solution did I use previously and why did I switch?

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

RPA was on the strategic roadmap for the transformation of the organization. When we came across this plan for the shared service teams and operations, we started to build a use case and try to see how RPA can help us. Basically, it's a strategic thing for my organization and we will continue scaling it up to other business areas.

What about the implementation team?

We had assistance from a local partner in Saudi Arabia. I would rate our experience with them five out of five. They have the right capabilities and the right knowledge. They were committed and dedicated to the successful completion of this project.

Which other solutions did I evaluate?

We did not evaluate other options before choosing this solution. The capabilities of the platform are good, as is their presence in the market. They have a very qualified team that gives you all the possible support, can answer your questions, collaborate with you, and ensure that you are on the right path to completing your automation projects. They try as much as possible to make your story a success.

They handled the PoC for us, and we implemented the full solution as soon as it was successful.

What other advice do I have?

The time freed up for our employees allows us to enhance and scale up their competencies and capabilities.

This solution is very good. The team is effective and they are constantly focusing on the product's roadmap and enhancements. As a platform in the ecosystem, this is a promising product for anyone who is considering automation projects in any organization.

My advice to anybody who is researching this type of solution is to have a look at UiPath. Take an in-depth look at their fabulous knowledge base that is available on the product.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
BP
IT Manager at a mining and metals company with 10,001+ employees
Real User
Studio is very valuable for our developers because it gives a nice visual way of developing the robots

Pros and Cons

  • "The product saves time and effort so employees are spared wasting time on mundane tasks."
  • "Even with drag-and-drop the product is a little difficult to use unless you are a programmer."

What is our primary use case?

We don't have a single primary use case. We use the Orchestrator studio to deploy attended and unattended robots to relieve the workforce of the mundane tasks that they currently do.

What is most valuable?

I don't think there is one most valuable feature. From my viewpoint, Orchestrator is great because I'm able to manage and control the robots and licensing. Obviously Studio is very valuable for our developers because it gives a nice visual way of developing the robots. Of course, the robots themselves do all the work. It is really a package that has to be put together.

What needs improvement?

The Insight product coming out in the next release looks interesting as a management tool, but I haven't dug into it enough to fully appreciate it.

Obviously, the Studio can always be improved. Even though you can drag-and-drop, it's still cumbersome unless you are a programmer. I think the Studio X is going to help tremendously for the citizen developers. I think that is going to be a big benefit in simplifying the interface.

For how long have I used the solution?

We have been using the product for more than six months.

What do I think about the scalability of the solution?

There are currently four-and-a-half people in the organization involved in the automation project and I think we'll have no problem scaling that up as necessary.

How are customer service and technical support?

We have used UiPath Academy. In fact, we've actually referred our citizen developers there.

On a scale of one to five where one is the least beneficial and five is very beneficial, I would rate the UiPath Academy about a four. It is specifically for developers, so there is a complexity level there that can take a little bit for say the average user who isn't an expert to get through, but for somebody who's already done development, it's good.

We actually signed up as a premium support member and took out a contract back about four months ago. Christopher Wilkins is our liaison and he's phenomenal. Absolutely any time I called Christopher, he has gone out of his way to help us. He's our success manager.

How was the initial setup?

From the time of purchase to deployment took about six months total. We did a quick prototype that I had spent two months to get it up and running and then it took me six months to clean it up.

I thought that the implementation was complicated but that was because they did the prototype and then handed it off and I had to come in and take the prototype and actually make it work in production.

We run the automation in a virtual environment. It was a bit painful to get it all working. We actually use Citrix VDI (Virtual Desktop Infrastructure) environment and the problem with that is it uses a storefront. When you log in, it doesn't know which server you're accessing. UiPath had problems with that, so we had to ditch that attempt. What we're doing is we're using the VDI image just to read and chart virtual machines every four months and using those for our UiPath.

What about the implementation team?

We did use a third party. Our experience with them was good and bad. The young man that came in from the Netherlands was extremely bright, but he was all over the place. So he thought he knew how certain things would work and in reality, they did not. So it was painful because instead of having a methodical way of working through the issues, he was jumping about too much and it didn't go very smoothly.

What was our ROI?

We don't really have exact numbers for the return on investment right now because we are too early into the process. We are still trying to get the whole organization comfortable with the concept. But you can see the processes have helped reduce human error in the finance area. It has also saved our organization time. Anytime you don't have a person doing the manual work, they can go on to do better things with their time.

What other advice do I have?

I inherited a bit of a mess. On a scale from one to five where one is very difficult and five is very easy, I would rate the ease of use of the platform for automation as about a three. Most of the problem is with the processes themselves having not been streamlined. So if there is a bad process in place and we still have to automate it, it will still be a bad process.

On the other hand, we do experience performance benefits using the solution. For mundane processes, the people who no longer have to do them because they are automated are extremely happy about that. The benefits were almost immediate. If we had somebody wasting three to four hours producing a single report that we can have a robot do, it's an immediate benefit.

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a nine or ten. I think the product is tremendous. We're still early in the process. As we get into AI, I think it's going to be a tremendous benefit.

My advice to anyone looking into this as a solution is to let somebody else do the deployment. You really have to make sure you understand the infrastructure required to properly scale up the solution. Make sure that you have senior management on board with the concept and then work hard to get citizen champions out there as soon as you can.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
AM
Transformation Manager at a computer software company with 10,001+ employees
Real User
Reduces human efforts so we can put effort into other quality work

Pros and Cons

  • "We're just starting to use UiPath now, but the automation process which reduces human intervention is the one we like most."
  • "I would like to see them improve the validation part of the data categorization."

What is our primary use case?

We use this solution mainly for data validation.

To start with, we are using Studio for many of our processes.

How has it helped my organization?

It reduces human efforts so our employees can put effort into other quality work.

I'm a manager, so we have UiPath for the team and my clients. I am a mediator. We are using Citrix for our VDI environment. We are going to implement the VDI.

Our client already has the UiPath Academy set up. It has been very beneficial in training our team, with its live involvement features, etc. It is good.

The solution has helped us eliminate human error. I would say, as it's now in its initial phase, this is somewhere around 80% to 90%.

It has also saved time for us.

What is most valuable?

We're just starting to use UiPath now but the automation process which reduces human intervention is the one we like most.

It's also very easy to use. I'm not directly involved in the program side. We have a team. I am the intermediator between our two teams. Those guys prepare the documentation and solution.

What needs improvement?

I would like to see them improve the validation part of the data categorization.

What do I think about the stability of the solution?

I would rate the stability of this product as five out of five. The team that works on this told me that once they come up with a use case, they can immediately implement it in UiPath. They have an idea and then can put that feature into practice. This can reduce many efforts.

What do I think about the scalability of the solution?

We have about 500 people in our organization that are involved in the automation program.

Which solution did I use previously and why did I switch?

We knew we had to invest in a new solution because when there are two categories of data, it is very useful to implement them with UiPath. We previously did this manually, as in with Excel and similar tools.

How was the initial setup?

The initial setup is straightforward.

Which other solutions did I evaluate?

Every customer in our current scenario is looking to move to digital. They want to make their manuals digital. UiPath is one of the best solutions in the current market industry. That is why we chose UiPath. It is easy to use, plus it gives a lot of benefits to our clients and our own organization as well.

What other advice do I have?

I would say that for the people who are using UiPath without any automation knowledge, the tool will be very useful. Apart from the UiPath platform, there are a lot of videos on YouTube. People can see a session from start to end. That will be useful.

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
RR
Architect at a wholesaler/distributor with 5,001-10,000 employees
Real User
Easy to use for non-technical business users, but the OCR capabilities need to be improved

Pros and Cons

  • "The most valuable feature is Studio, which is a very powerful tool."
  • "I am looking forward to new cognitive and artificial intelligence capabilities."

What is our primary use case?

We use Studio, attended robots, and Orchestrator.

Our primary use case is automating support services for accounts payable and accounts receivable. We are still implementing and our robots are not live in a production environment yet. For the time being, we are using attended robots but we are looking into unattended robots as well.

We run automations in a virtual environment using VMware, and the implementation was straightforward. It was easy to set up.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. You don't need any programming skills to be able to leverage the tools. We have used other tools such as Blue Prism and Automation Anywhere, and this solution was easier than those.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. It is very simple and can be easily demonstrated.

From the point that we purchased our UiPath license until we had our first robot was approximately six months. 

How has it helped my organization?

In terms of eliminating human errors, this is the expectation once our robots are live in production.

Once our robots are live, we expect to see a fifty percent reduction in time for certain tasks. It will save thousands of hours.

What is most valuable?

We leverage all of the components in this solution.

The most valuable feature is Studio, which is a very powerful tool.

What needs improvement?

I am looking forward to new cognitive and artificial intelligence capabilities.

I would like to see voice recognition and better OCR capabilities. Today, we have to leverage other tools for this, so we are hoping that UiPath matures in this area.

What do I think about the stability of the solution?

This product is very stable, but we have some issues with security.

What do I think about the scalability of the solution?

We have about five people working on automation in our organization.

How are customer service and technical support?

We have a CSM and they are awesome. On a scale of one to five, I would rate our support from the CSM a five.

Which solution did I use previously and why did I switch?

Before using this solution, we used to leverage our internal tools.

How was the initial setup?

The initial setup of this application was straightforward. It was easy, and like other applications that use a Windows installer.

What about the implementation team?

We used an integrator to assist us with deployment. I would rate them a three out of five.

What was our ROI?

We have not seen any ROI because our bots are not yet live. However, we have done a calculation and expect fifty percent savings in time.

What's my experience with pricing, setup cost, and licensing?

The licensing fees for this solution are approximately $100,000 USD annually.

Which other solutions did I evaluate?

Before choosing this solution we evaluated Blue Prism and Automation Anywhere. UiPath seemed to be the easiest one to implement.

Blue Prism seemed to be too technical for some of our business users, while Automation Anywhere did not have attractive pricing.

What other advice do I have?

This is definitely a solution that I would recommend. From my experience, this is a technology that is easy to leverage among users that do not have a technical background.

This is a good solution, but there are still gaps and the product could be more mature. The OCR capabilities definitely need to be improved.

I would rate this solution a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
RM
Process Consultant at a energy/utilities company with 10,001+ employees
Consultant
Good training helped us get started, but the Insights feature needs improvement

Pros and Cons

  • "The most valuable feature of Orchestrator is that it gives you the ability to control everything from a centralized location."
  • "When it comes to scoring, you receive a score after the intake and a score after you build it, but you should also get a score after you build it."

What is our primary use case?

We are using Orchestrator and unattended robots.

We use this solution for automating financial tasks. Some of our use cases including reconciling amounts, such as those related to invoicing.

We run some of our automations in a virtual environment. We have been running into roadblocks with Citrix, so we run them on virtual desktops.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. Building automation using a standard set of rules is not a problem. It can become problematic depending on the data and the types of tasks.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. We are using it to gain experience with the platform.

From the point that we purchased our UiPath license until we had our first robot was probably three or four months. The first robots that we created were for account reconciliation, and the implementation was straightforward.

How has it helped my organization?

At the least, this solution is making us rethink the way our processes work. Putting automations in place not only helps to save time, but it gets people thinking about where else we can use automation.

This solution is improving our employee experience, giving them time to do other things. From a resource perspective, we are staffed the same way, but our employees are able to make better use of their time. In total, we have saved thousands of hours.

In terms of eliminating human errors, we have seen an improvement of approximately twenty percent.

What is most valuable?

The most valuable feature of Orchestrator is that it gives you the ability to control everything from a centralized location. You can have access to everything that is running.

For unattended bots, the best feature is the value that you get from not needing to have somebody there to do the job. It's a time-saving benefit.

What needs improvement?

Several areas of this solution need improvement including insights, the dashboarding of results, and process mining.

When it comes to scoring, you receive a score after the intake and a score after you build it, but you should also get a score after you build it.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four. The system is generally pretty stable. Some of the things that cause instability are outside of UiPath, or the robots interact with them.

What do I think about the scalability of the solution?

There are between fifteen and twenty people involved with the automation program in our organization.

How are customer service and technical support?

We have used support and they are ok.

What about the implementation team?

We hired LTI to assist us with the implementation. Our experience with them was not good. They had a few really capable people, but not the whole team. They were learning along the way.

What was our ROI?

We began to realize ROI after six months.

What other advice do I have?

This is a good solution, and the availability of training helped us to get started.

Definitely, the Insights component needs to be improved.

My advice to anybody who is implementing this solution is that the solution can be great, but it will only be as great as the design of your processes. You have to make sure that everything is done right to get the best results.

I would rate this solution a seven out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
LS
Analyst at a energy/utilities company with 11-50 employees
Real User
Good technical and community support, and makes tasks easier for our employees

Pros and Cons

  • "The most valuable feature of Studio is the ease of use for developers who do not have a technical background."
  • "I would like to see anything that can increase the reliability of the processes."

What is our primary use case?

We are using Studio and Orchestrator.

We use this solution for financial analysis, accounting, invoice processing, and other menial tasks.

We run automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. The ease of use comes from many things including the user interface and the coding.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. I feel that you can have people who are directly thrown into the training, but sometimes it is difficult for people to pick up on topics that are not related to the processes that they are dealing with.

From the point that we purchased our UiPath license until we had our first robot was approximately two weeks. The implementation was straightforward both on the setup and the development side.

How has it helped my organization?

This solution has a big impact on what we do. It gives us a bigger impact on a decreased employee base.

I can't say exactly how much time we have saved across the company, but I can speak to my own processes. We save about one hundred a twenty hours per week. This savings comes in part because it is making people's jobs easier.

In terms of eliminating human errors, our error rate has improved since automation. I would estimate we have twenty-five percent fewer errors.

What is most valuable?

The most valuable feature of Studio is the ease of use for developers who do not have a technical background.

The user interface is good.

What needs improvement?

I would like to see anything that can increase the reliability of the processes. It can be a really challenging task and there is certainly room for improvement.

I would like to see more selectors included in the next release of this solution.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four. It's fairly stable and it's making good improvements. In some cases when you get an upgrade package, you can lose functionality that previously worked with some processes.

What do I think about the scalability of the solution?

We have about six people involved in our automation program.

How are customer service and technical support?

The technical support for this solution is good, but seeing the functionality break that worked in previous versions can be frustrating.

What about the implementation team?

For my processes, everything was done in-house.

What was our ROI?

We have seen ROI with this solution. We began to see some in about a month, but a lot more after two months and greater.

What other advice do I have?

My advice to anybody who is considering this solution is simply to do it. Dive right in. Gather as much information as you can about the processes, then use the community in place to help.

This is a good solution, but there is always room for improvement.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
CL
IT Analyst at a printing company with 10,001+ employees
Real User
Saves us time and helps eliminate errors in repetitive manual processes

Pros and Cons

  • "Using this solution has allowed us to enter a lot of customer data into our system in a much quicker and more efficient manner."
  • "In the training, between steps two and three, there is a pretty big leap in terms of how difficult the material is."

What is our primary use case?

We are using Studio and Orchestrator.

Our primary use case is automating data processing for clients translating into other systems.

We do not run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a three. I think that the technology that we use in the printing industry is a little more difficult to automate.

I am currently involved in the UiPath Academy training. We have third-party contractors who have been doing the development, and I am the first internal employee who will be developing. I find that the training is good in the first step, and also in the second step where we're learning about Orchestrator. However, when it moves to the third step and they are talking about the framework, I think that it is a pretty big leap and that is where I'm struggling. This is the section that I am in right now.

There was one project that was completed before I started, at my understanding is that from the point that we purchased our UiPath license until we had our first robot was less than six months. For my project, it has taken two months.

How has it helped my organization?

Using this solution has allowed us to enter a lot of customer data into our system in a much quicker and more efficient manner.

In terms of eliminating human errors, this solution has definitely helped. I would estimate an eighty percent reduction in the number of errors.

With respect to saving time, automation has taken a process that used to take two or three days to perform, down to several minutes.

What is most valuable?

The most valuable feature for us right now is being able to automate our process applications.

What needs improvement?

In the training, between steps two and three, there is a pretty big leap in terms of how difficult the material is. Moving right from the basics into the framework is causing me to struggle a little bit, and I think that there is room for improvement here.

What do I think about the stability of the solution?

With respect to the stability from a bot perspective, on a scale from one to five, I would rate this solution a four. It has been pretty stable for us.

What do I think about the scalability of the solution?

We have less than fifty people involved in our RPA program at this time.

What about the implementation team?

We have contractors who are doing our development right now. On a scale of one to five, I would rate our experience with them a three. They seem to be struggling with the PDD.

What was our ROI?

In the project that I worked on, we have definitely seen ROI. We replaced a process that was being done manually, so we began to see returns immediately.

What other advice do I have?

For the way in which we are using this solution, the features have been working very well. Our company is very young in this so we are still learning. We will get a lot out of this solution.

If you have a lot of manual and repetitive tasks in your company then this is definitely a great solution for you. That said, I know that things can always improve.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
MK
Business Transformation Advisor at a energy/utilities company with 1,001-5,000 employees
Real User
Helps us save time and eliminate errors with repetitive tasks

Pros and Cons

  • "The most valuable feature is that you can save time when you have to run the same process over and over again with little variation."
  • "It is sometimes difficult to work with the exceptions, which can cause us a delay."

What is our primary use case?

We use Studio, Orchestrator, and robots.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a two. It's been going for about six months now, and we are still having challenges here and there.

On a scale of one to five, judging how beneficial it is, I would rate the training a three. The material is on the technical side, and not being a technical person, it makes it pretty challenging to get through. 

From the point that we purchased our UiPath license until we had our first robot was approximately three months.

How has it helped my organization?

With respect to saving time, we have saved about fifteen hundred hours so far.

In terms of eliminating human errors, we have seen a reduction but I'm not sure by what percentage.

What is most valuable?

The most valuable feature is that you can save time when you have to run the same process over and over again with little variation. 

What needs improvement?

It is sometimes difficult to work with the exceptions, which can cause us a delay. We have a lot to learn.

I would like to see more options that we can quickly select to help improve the robots.

For how long have I used the solution?

We have been using this solution for about six months.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four. Most of the time it is working pretty well, but there have been a couple of blips along the way.

What do I think about the scalability of the solution?

We have approximately twenty people who use this solution in our organization.

What about the implementation team?

We hired a consultant to help us with the implementation. I would rate our experience with them at three out of five. It was successful, but we had to redo some of the stuff that was originally done.

What was our ROI?

We have seen ROI but it is pretty far off right now. After about three months, we began to see ROI. I'd say that it is probably going to be about two years before we break even.

What other advice do I have?

We are excited about the new features that were recently announced.

My advice to anybody who is implementing this solution is to hire a consultant who is familiar with the process. It is such a new technology that getting assistance would be helpful.

I would rate this solution a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
WB
Senior Systems Analyst at a pharma/biotech company with 10,001+ employees
Real User
Robots work on-demand to complete tasks quicker, but there is a learning curve

Pros and Cons

  • "The robots that I have developed can take a process that is normally very complicated and simplify it."
  • "The licensing process is complicated and needs to be improved."

What is our primary use case?

I primary use Studio, but I also use Orchestrator.

I develop robots for reducing tasks for our business users.

We run some of our automations in the Citrix virtual environment. We have found that the Citrix environment tends to present challenges, so it can take a little longer.

With a year and a half of experience, I am still learning with this platform. I find that the ease by which processes can be automated is not as much of an issue with the platform, but rather how it behaves with other applications that the robot controls. The learning curve is mostly how the robot behaves in maybe a Citrix environment, or in how it behaves with the applications that it's controlling. Sometimes they have their own little quirks that you have to learn.

I got started with this solution by using the Academy training. On a scale of one to five, judging how beneficial it is, I would rate the training a three. It is easier to get started because you are learning by experimenting.

From the point that we purchased our UiPath license until we had our first robot was approximately seven or eight weeks. 

How has it helped my organization?

Some of the robots handle high-volume processing, where people would take months but the robots are doing it in weeks. We have probably saved two hundred hours so far, using robots. Timing is a big issue. The tasks can be completed quicker because robots can do it on-demand, rather than having to schedule a person's time. I would say that for the tasks, they are saving forty to fifty percent of the time by using the robot.

Not all of the tasks we have automated were existing in-house processes. In some cases, after using the platform, we thought about ways to create automated tasks that were never being done before.

Human errors have been reduced, if not eliminated by using the solution. When users have to complete a task in a timely fashion they sometimes miss one of the steps, but this is solved using the robots.

What is most valuable?

The robots that I have developed can take a process that is normally very complicated and simplify it. 

What needs improvement?

The licensing process is complicated and needs to be improved.

For how long have I used the solution?

I have been using this solution for a year and a half.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four. The tool itself is quite stable and I haven't had any real issues with it. The issues that I have had tend to be with Citrix or the environment that the robots are running in, and not the platform itself.

What do I think about the scalability of the solution?

In the US, we have two developers who are working with this solution.

How was the initial setup?

The installation was straightforward but activating the license was slightly complicated. I'm not sure if it was a UiPath issue or something at the company.

What was our ROI?

We are definitely seeing performance benefits for users and the turnaround time for tests that we have to do.

What other advice do I have?

I have seen a demo with Studio X and it should help with the coding so that we can go live quicker than we do.

Using RPA has given us another tool to offer with respect to business solutions. Automation is something that we're actively looking for places to make use of.

This is a good solution, but there is a learning curve. One you are familiar with it, this solution works well and it is fun to work with.

I would rate this solution a seven out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
AF
Process System Administrator at Rich products
Real User
Good training and helpful activities in Studio are helping to restore value-added time for our employees

Pros and Cons

  • "The most valuable features of Studio are all of the activities that UiPath and their partners have developed."
  • "If there was a little more flexibility with the selectors, and they were a little bit more adaptive, I think it would be helpful."

What is our primary use case?

We are using Studio and the attended robots, but we haven't implemented Orchestrator yet.

Our primary use is to automate tasks within the accounts receivable, accounts payable, and trade settlement realm that we work in. We're also getting into some more internal audit automation.

We run automations in Windows Virtual Machines. It was a long process for us to get started, getting our IS to buy into letting us set up this environment and get started with it.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a two or three. They offer upfront training, the UiPath Academy, and that makes it easier but you still need to have a technical mindset to understand it, as it is now.

We have all used the Academy. On a scale of one to five, judging how beneficial it is, I would rate the training a five. It's a great experience and very beneficial.

From the point that we purchased our UiPath license until we had our first robot was approximately six months. It took us a while because we had a bunch of other projects in front of getting our first automation. The process was hard, although it was not complicated. The approval process involved going through a security review. 

How has it helped my organization?

We have not found that our automations have saved us money, yet. However, it's giving people back the time so that they can do more value-added work.

With respect to saving time, we have just measured the out rate. We're probably saving thirty hours a week with what we have going now, so almost one FTE.

This solution has absolutely helped reduce or eliminate human errors, although I cannot estimate by how much at this time.

Using this solution has definitely increased the confidence and communication that we have between departments because we're saving a lot of department time, and they can focus on their value-added tasks. With this, they're a lot more willing to work with us, and they're happier employees.

What is most valuable?

The most valuable features of Studio are all of the activities that UiPath and their partners have developed.

What needs improvement?

The biggest problem that we have when working with this solution is the selectors. If there was a little more flexibility with the selectors, and they were a little bit more adaptive, I think it would be helpful.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution four and a half to five. We haven't had any problems.

What do I think about the scalability of the solution?

Currently, we have twelve automations running.

In our organization, we have three people directly doing automation and design work. There are probably six or seven more than are trying to get the larger enterprise into UiPath and get their departments set up with it.

How are customer service and technical support?

The technical support for this solution is excellent. They got back to me really quickly and provided the solutions that I needed. It was very helpful.

Which solution did I use previously and why did I switch?

We were not using another RPA solution prior to this one. In deciding to invest in this technology, we recognized that people were doing a lot of tedious processes and that we can make better use of their time.

What about the implementation team?

Huron Consulting assisted us with the implementation and deployment, and they were very helpful. On a scale from one to five, I would rate them a five.

What was our ROI?

We have been asked to start measuring for tracking ROI but have not yet begun. However, I can say informally that we have seen performance benefits. People are very happy with the things we've automated so far and they're just glad to be relieved of some of that tedious work.

What's my experience with pricing, setup cost, and licensing?

Right now we only have a couple of Studio licenses and a couple of bots, so we're at about $8,000 USD per year. We're hoping to ramp that up pretty soon.

Which other solutions did I evaluate?

We evaluated Blue Prism and Automation Anywhere before choosing this solution.

One of the major reasons that we chose UiPath was because they gave a free trial at the time when we were looking at it, and none of the other vendors did. Then they also have the UiPath Academy, which allowed us to look at it first and then learn how to use it before we actually had to make an investment.

What other advice do I have?

From a cost perspective, the unattended robots are going to be of more benefit because they can run twenty-four hours a day. At the same time, the attended robots are pretty affordable. I think we're coming up with more use cases where people have it on their desktop and want to be able to run it on demand. We have definitely benefited from both types of robots.

We are looking forward to some of the new features that are going to be released. One of them is in the UI, where you can document what your processes have and figure out if any have the potential for automation. That is going to be very helpful.

My advice for anybody who is implementing this solution is to first speak with a partner. If someone is new and hasn't been in this space before, it's going to be kind of confusing and they're going to need somebody to guide them it setting it up.

This is a really great product and there's a lot of potential for it.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
EE
Monitor Technology at Equifax Inc.
Real User
Drag-and-drop configuration can automate processes and save time, effort and money

Pros and Cons

  • "The ease of configuring new processes via drag-and-drop is invaluable."
  • "The machine learning and artificial intelligence components need to be enhanced and become more efficient."

What is our primary use case?

We have robots and we have Orchestrator and we are exploring the new analytics model over the next few months. Right now, our primary use is mostly operational processes and deploying apps for the global operations team. We have multiple automation processes in place for them already.

How has it helped my organization?

The product has improved the way our organization functions in a lot of ways. Mostly, I would say it improves our processing efficiency. When you have one person working eight to five to take care of tasks and can replace that, instead, with a bot that can work 24 hours a day to onboard customers or entering information to a form, that drives a lot of value for the organization. With that benefit and decreasing human error as well, that turns into a lot of value for a global organization like us.

What is most valuable?

The most valuable feature in UiPath is different from one process that we build to the next. I would say that the ease of configuring new processes may be one of the most consistently valuable features for our robot production. Creating a process is just a drag-and-drop solution most of the time. With this automated feature for process creation, it is very easy to make what we need, and that ease-of-use is valuable.

What needs improvement?

There are a few areas where the product can be improved for our use. Invoice processing, for us, is a major use case. I saw some examples in our research that mentioned machine learning models and how to implement that in the new, upcoming version. It seems that the machine learning would solve some of our current issues in processing. That is one feature that I would like to see and experiment with when it is released. I want to explore that to see not only what it can do, but how efficient it is and how it affects the performance of invoice processing models. The other feature we are interested in that is promised to be in the next release is the VDI (Virtual Desktop Infrastructure) desktop. 

Those two features, for us, are critical. But we also need them to be fast and efficient for us to be able to use it in practice. Otherwise, we are going to continue struggling with the solutions we already have. The solutions are kind of already there in UiPath, and I think they need to work hard on the performance of anything they release. This is especially true for those two solutions. For us to have a good business case for deploying them for use, we need them to be efficient.

A feature that we tried to use that clearly has room for improvement is the UiPath Computer Vision component. We have tried to use that but it was not efficient enough for our planned applications. It was a little disappointing. It needs to be improved in performance and in the design of the machine learning models. It is pretty easy to use for people considering the technology. I just don't think it is quite to the point where it should be.

For how long have I used the solution?

We have been using UiPath for about a year-and-a-half

What do I think about the stability of the solution?

On a scale from one to five with one being the least stable and five being the most, I would rate the stability of UiPath as pretty stable. For us, it has really been a five.

What do I think about the scalability of the solution?

We have 35 employees involved in the automation program doing configuration. We also have three platform administrators and a bunch of automation champions right now — there are quite a few of the latter.

How are customer service and technical support?

Customer support, in general, is pretty good. They are very responsive. We have one dedicated support person in New York and we always get support right away. But there are other facets to UiPath technical support.

The classroom and Academy training are both easy to use and beneficial. On a scale of one to five where five is the best, I would rate these resources as a five-out-of-five. It was and is beneficial and it is available to help the staff get oriented to the product and resolve production issues.

We have 35 configurators. Of those 35, I will say that only five or ten of them were formally and personally trained by a trainer at our site in Costa Rica. The rest — and really most of the configurators — have been trained only using the UIPath Academy suite. So, with some senior resources available and the Academy, you can establish a team of proficient configurators in a very short time.

Which solution did I use previously and why did I switch?

The reason why we choose UiPath was because they let us play with the tool before we bought into it. We were looking at many vendors for an RPA solution, but the other vendors wanted us to pay first before they would let us explore the products and what they could do. With UiPath we were able to play first without paying and that's something that was attractive and showed that the company was forward-thinking and confident. We explored the product and saw that it was something that could help us to solve some of our problems. So that is why we identified it as a solution and eventually selected it as the product that was going to cover our processing needs.

How was the initial setup?

The initial setup was pretty easy because we had the assistance of UiPath experts on-site. They helped us with the first deployment. They did a lot to help make it pretty easy. It might be more accurate to say it was not easy, but that because of them it went smoothly. That's what their group was there to do: sort out modeling problems pretty quickly and get the product to production.

What about the implementation team?

We used a consultant and our experience with them on a scale from one to five where five is the best, I would say they were a five-out-of-five. They knew what they were doing and were excellent in promoting the deployment. We have no complaints about their services or the result.

What was our ROI?

We have automated a lot of things and realized about a million-dollar return on investment in about a year-and-a-half. There is still a lot more to do in our company. We are big, so we have a lot of opportunities for automation and we are expected to be producing even more benefits than we already have. But a million-dollar return on investment is pretty good and is only the beginning of what we will eventually realize.

What's my experience with pricing, setup cost, and licensing?

Right now we have around 200 licenses in terms of the bots we have in production. I know the cost is about $200,000 or $300,000 per year. I am not sure about additional costs.

From what I understand UiPath is cheap when you compare the costs to other vendors in the same market. In any case, the price seems to be good in comparison to the actual benefit. We also have some type of special agreement for pricing discounts because we are one of the early adopters who engaged with UiPath for use of the product. I feel we have some very special treatment and the price, for us, is reasonable and convenient.

What other advice do I have?

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as an eight out of ten. The reason why it is an eight and not a ten is because there are some specific considerations — especially in performance and machine learning — that we believe has a lot of room for improvement. They are starting to introduce the functionality, they are doing a good thing in introducing it, but there could be a lot of improvement.

If I would make a recommendation for people considering automation options, I would say that they should take advantage of manufacturers that let you play with their product to evaluate if a particular solution is convenient for you. This is the reason why UiPath became the more convenient option for our company when we were looking to start with process automation.

For us, the virtual implementation has been working well because we have deployed everything that we automated in our Citrix environment. Now the new question is how easy it will be to interact with target applications through our VDI desktop. Resolving that to this point has been pretty tough for us and it is actually one of our constraints in making processes work efficiently.

Robotic processing has helped to eliminate human errors and reducing human error is definitely one of the basic benefits that those moving into robotics should expect — if they are approaching automation correctly.

The solution also saved our organization time. For example, we had the one case where we had to onboard around 2 million customers. What that would take in terms of manual hours is about a month and a half. Instead, using RPAs, we were able to complete the task in one week. That is just one example. We have multiple examples in three years of automation. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Murali Kothapalli
Senior Analyst at Salt River Project
Real User
Works well with Excel, easy to learn, saves us time, and points out human errors

Pros and Cons

  • "The ability that this solution has to work with Excel is really good."
  • "Creating a trigger that is based on either the arrival of a file or the arrival of an email is a common scenario and it should be built into the platform so that I don't have to code for it every time."

What is our primary use case?

We use Studio, Orchestrator, attended and unattended robots.

We use this solution to solve the things that people don't want to do. They spend a lot of time and there is a high potential to make manual errors. Quality suffers because it takes too long and users can get fatigued. There are the things that we are targeting and we have already seen some of the benefits.

We do not run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. It is easy, but there are some improvements that can be made.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. It is my lifeline. 

From the point that we purchased our UiPath license until we had our first robot was approximately six to eight months. I felt that the process was complicated, in part because of UiPath but also partly because of internal things.

Internally, in order to get set up, the entire infrastructure needs to be in place. All of the servers have to be set up and you need the right permissions because the bots need their own security. You have to explain to people that this is going to be a service account, and you have to explain the need for it. These are all internal, but necessary issues.

How has it helped my organization?

This solution has saved our organization time. I would estimate that the bots save us four weeks every month.

In terms of eliminating human errors, this solution absolutely helps in that regard. The bots don't make any mistakes. Rather, they point out the mistakes that have been made by humans so far.

What is most valuable?

The ability that this solution has to work with Excel is really good.

The SAP feature looks helpful and we are going to explore that functionality in our next project. 

What needs improvement?

We don't like the attended bot experience, where it requires the user to be hands-off. We installed it on the user's machine, and the user should not touch the mouse or keyboard because the moment they do, it crashes. It takes over the machine and cannot work in the background. For this reason, it is difficult to work out scenarios that are purely attended. 

For example, we have a process that downloads two files and then does some massaging of the data. Now, the data needs to be looked at by the user. An email is sent and the files are deposited into a common folder, and the user will address the task when they have time. After the user manipulates some of the data or makes decisions, it can proceed to the next step.

They drop the modified files into the common folder, but the bot doesn't react because there is no feature in Orchestrator to trigger based on the arrival of a new file. Instead, we have to put in a call to check periodically, whether it be five minutes, fifteen minutes or some other interval. This is something that we don't find desirable.

Creating a trigger that is based on either the arrival of a file or the arrival of an email is a common scenario and it should be built into the platform so that I don't have to code for it every time. As it is now, there are only two ways to trigger a bot.

Orchestrator does not have a good filtering mechanism to look for jobs, and the table view needs to be improved.

From the UiPath side, one thing that irritates me is that you cannot find the downloads to upgrade to the new version. I'm a paid customer and I log in with my credentials, but I cannot download it. I need to create a ticket, tell them who I am, and I have to give them a long list of things that I don't remember. They will address the ticket maybe today or tomorrow, and then finally I get a response. When I use other tools like Microsoft and SAP, as a customer or subscriber of the tool, I just download the latest versions and install them on my servers. When I have a mandate to do work, I want to be able to do it. However, when I can't download the file and have to wait for a ticket to be answered, this wastes my time.

The integration with Elasticsearch and Kibana is a struggle. They are not UiPath products, but they are recommended by UiPath. Some documentation is provided, but it is an Orchestrator installer package the just installs itself. I had to do a lot of experimentation on Windows machines because the configuration is different for Linux machines, and this gave me some trouble. There is a lot of information about this in the UiPath forums and I spent a lot of time on it.

Right now, I have a set of configuration data that I put into an Excel file. The users can change the file and my app will run using the configuration variables. A problem occurs if the Excel file is not closed properly because there are locking issues. This is a pain because the bot crashes when opening a locked file. There is something in Orchestrator called Assets, but it is kind of limited. It only accepts text and a credential. It would be nice if it had a simple database table, say to be able to create a couple of columns that I want to set up for a bot-related task. Rather than a single piece of text, there is a whole table of information. My users will be able to edit it, based on the permission that I assign. Then the bot will look at it and work according to what is specified. This would be a great feature to have.

I would like to see the Studio web-based so that we don't have to install it on everybody's desktop. 

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a five. I have never had any problems with the platform itself. I haven't had to restart the servers or anything like that.

What do I think about the scalability of the solution?

We have three people in the organization who work with the bots.

Which solution did I use previously and why did I switch?

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

In deciding whether and RPA would benefit us, we followed the guidelines that UiPath provided, which is a twelve-step validation process. If processes are unchanging, there is a lot of manual work, there is the potential for errors, and it's simple to automate, etc, then RPA may be suitable. Based on this assessment, we made the investment in RPA.

What about the implementation team?

Our own team was responsible for the implementation.

What was our ROI?

We have recognized ROI through savings in employee hours. For our PoC, with two projects, we saved one full-time employee.

It took us one year to see ROI, although I don't think that we have saved any money yet because of the development time. If we negate the development cost then it might be $60,000 USD, as a developer's salary, but we're not there yet. One of the things that I am trying to do is motivate people to look at more processes that we can automate because right now, my bots are sleeping and I want to put them to work.

What's my experience with pricing, setup cost, and licensing?

Our licensing fees are approximately $140,000 USD annually, which includes all of the bots, Orchestrator, and the Studio.

Which other solutions did I evaluate?

In our company, there is another group that had already implemented UiPath, and they have had good success. We followed their lead, but in addition, we reviewed other sources such as the Gartner ranking. The features set was also considered during the evaluation.

What other advice do I have?

I feel that the cost of the bot is worth it, provided that we make use of it. The unattended bot is cheaper, but it is useless for us right now because there is no use case. We think that Studio X might change that, and I've heard that the Studio X license includes the attended bot. So, if we swap the attended bot license that we currently have then we could take them away and then get the Studio X license, and that will motivate more people to make their own automations.

No organization has unlimited resources, but the business is changing around us and we are always tasked with new things to do. In that aspect, you have to make room for innovation, and you have to automate.

UiPath has shown tremendous gains with this solution. They're sitting on the shoulders of Microsoft .NET, and they've shown some initiative on what you can do with a generic platform. They offer free training and a Community Edition for people to experiment with, and it can do wonders for the world. We have seen that happening and I love that.

This is a company that is listening to customers' feedback and I think that they should keep doing that.

My advice for anybody who is considering this solution is to start by watching all of the videos. Go through the UiPath Academy and get a feel of what it can do. Read all of the case studies and see what other people have done. You will get a feeling for the ROI. Then download the Community Edition and play with it to see for yourself what gain you can get from this tool. Finally, start small and just keep adding to it.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
SO
Head of Automation at a retailer with 1,001-5,000 employees
Real User
Easy to use and allows building a solution onto any legacy system

Pros and Cons

  • "Orchestrator has a lot of good features including the configuration, the queues, the transaction reporting, the logs, and accessibility."
  • "I would like to see more support for the cloud in Australia."

What is our primary use case?

We are using Orchestrator and robots.

Our primary use for this solution is Accounts Payable invoice automation.

We run automations in the virtual environment provided by the Amazon service. Our implementation has been finicky at times. The latest release is a lot more stable, but I've had a two-week production outage where DLLs weren't registered and someone from Vegas had to log in for eight hours to our servers. They had to uninstall and reinstall the solution, as well as all of the different apps. I lost a bit of faith in the solution with that incident.

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. It's pretty easy to use, but it wouldn't be a five because it isn't doing everything for me. Things still need to be done.

I have not taken the Academy training but my team has. On a scale of one to five, judging how beneficial it is, I would rate the training a four.

From the point that we purchased our UiPath license until we had our first robot was approximately two weeks. The process was pretty straightforward.

How has it helped my organization?

With respect to saving time, the last company I worked with was trying to save one thousand FTE. So far, they are already at sixty FTE, and in Australia, we're at ten FTE.

This solution has helped us to reduce human errors, although it has created other errors.

What is most valuable?

Orchestrator has a lot of good features including the configuration, the queues, the transaction reporting, the logs, and accessibility.

This technology gives you the ability to build a solution using any legacy system.

What needs improvement?

I would like to see more support for the cloud in Australia.

A tool that better identifies the processes, watches the computer and works it out for me, would be an improvement.

For how long have I used the solution?

I have been using this solution since 2016.

What do I think about the stability of the solution?

The stability of this solution has improved since we started using it. Now that I have done an upgrade, it seems to be a lot better.

I was running High-Density on the 2016.2 or 2016.3 version, and I had a lot of problems. I couldn't determine whether they were just UiPath issues or it could be partly attributed to the client app. What we noticed was that if you log in as Console, you have far fewer issues than if you run High-Density.

These days, I would rate the stability a four out of five. 

What do I think about the scalability of the solution?

We had between fifty and a hundred people working in the automation program in the old company.

How are customer service and technical support?

I have only used technical support once and my experience with them was not good. That was during our two-week outage.

What about the implementation team?

We used Blackbook.ai to assist us with our implementation and our experience with them was awesome. 

What was our ROI?

We have seen ROI from this solution in terms of money saved. Just in Australia, we have saved a million dollars. In India, we have saved maybe five million dollars.

What's my experience with pricing, setup cost, and licensing?

At the last company I worked with, the annual licensing fees were $700,000 USD.

From a cost perspective, I have an issue with the price of the bots. At the company that I was with previously, we were paying $3,600 USD per bot. With the new company that I am at, because we're new and we don't have the size, we are paying $8,000 USD per bot.

Which other solutions did I evaluate?

It was 2016 when I evaluated this solution, and it had a small market share at the time.

Everything I had read about Blue Prism said that it was too heavy, too old school, and had too much development ramp-up time. I looked at Automation Anywhere and UiPath. Automation Anywhere had a good price point, especially for a PoC. However, in between Blackbook.ai and what I saw out of UiPath, I felt that UiPath was the better option.

What other advice do I have?

This solution is pretty good. It's an enabler. There is a lot of investment and a lot of new things. My advice to anybody who is implementing this solution is to make sure that it is set up to scale correctly.

What I would like to see is everything as a SaaS, completely, bots included, and I want it hosted in Australia.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PN
RPA Developer at Lsc communication
Real User
Easy to learn and use, good customer support, the macros are helpful, and we save a lot of money

Pros and Cons

  • "The most valuable feature in Studio are the macros."
  • "When we deploy code into Orchestrator, sometimes there are macro activities that worked in Studio but do not work correctly in production."

What is our primary use case?

We are using Studio and Orchestrator, and we purchased an unattended bot.

Our UiPath is integrated with Kibana, which is a free tool.

Our primary use of this solution is to automate manual processes. We have approximately eighty use cases to automate.

The RPA team includes two developers, a manger, and two BPOs.

We run automations in a virtual environment, but I am not familiar with the details.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. We just drag and drop. If you want to write something we use "Type Into". If you want to click, we use the corresponding click application. For me, it's very easy, and we also have tutorials available on the UiPath website. That is something that is very useful for everyone who wants to learn, and even a non-programmer can start learning to become a developer.

The Academy RPA training was very beneficial and I would rate it a five out of five. You cannot skip one step. There are ten sections and you cannot skip any of them. It means that until you pass a certain test, it will not allow you to go to the next lesson. This restricts people from jumping directly into another section. I really like the training and it is very easy. The tutorials are not very lengthy, they are simple, and the way they are explained is relatable. The practice tests that were conducted at the end were really helpful.

We partnered with IVy to create our first two pilot bots, and from the point that we purchased our UiPath license until we had our first robot was approximately six months. It was very easy because they helped us.

How has it helped my organization?

This solution obviously helps us when it comes to eliminating human errors. I cannot estimate the percentage, but our company is manual process-intensive. We have a lot of manual processes like invoicing, where we have a process with the business team. They pull out an invoice number and a purchase order number from a PDF, and the source PDF is not structured. When it was being done manually, they had encountered issues entering data into one of their applications. This is one place where human errors have been reduced.

Using this solution has saved us time. For example, we have a huge process and I have heard that it saves us millions of dollars every year. Each human takes forty hours to complete the task, whereas it takes the unattended bot between ten and fifteen minutes.

Any savings in time for humans gives them time to work on something else.

What is most valuable?

The most valuable feature in Studio is the macros. They are very useful but at the same time, it depends on how we write them.

UiPath is very easy to learn.

What needs improvement?

When we deploy code into Orchestrator, sometimes there are macro activities that worked in Studio but do not work correctly in production. For example, I have implemented a Text Reading Activity that worked fine in Studio, but after deploying the code into Orchestrator it does not read the text exactly. I was able to create a workaround by using a split function in the code. It was reading the text fine because the data is being read using split functions, but this is something that I would like to see fixed.

I would like to see more AI and natural language processing.

Having chatbots available would be a helpful inclusion in a future release of this solution.

How are customer service and technical support?

Customer support and technical support are very nice. I would rate them a ten out of ten.

Which solution did I use previously and why did I switch?

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

What about the implementation team?

We partnered with IVy to assist us with the implementation. They helped us with two pilot bots. One of them was not up to the mark, so our CEO decided to have it reprogrammed. I would rate them a four out of five.

We have our own IT team that looks after connecting the servers with Orchestrator.

What was our ROI?

I am not updated regularly about how much money this solution saves us, but I have recently heard that we saved $400,000 USD in six months.

Which other solutions did I evaluate?

After our CEO decided to invest in RPA, we chose UiPath because it is easy to learn.

I have heard of Blue Prism and Automation Anywhere, but I have not learned them or worked with them.

What other advice do I have?

We are looking forward to the new tools, and when they launch, we are definitely going to use them.

My advice to anybody who is implementing this solution is to speak with UiPath. Many people do not know how to start. The basic things they should have are a proper PDD (Process design document) and a recording of the manual process. These two things are essential. It is also very important to hire the right partner if you do not have your own developers because some of them are not up to the mark.

This solution is simple and easy to implement. I know there are lots of new features coming and every year they are providing good solutions with every release. There is always something new that minimized errors in previous versions.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
LJ
Automation Delivery Lead at a pharma/biotech company with 10,001+ employees
Real User
Good training, helps to reduce errors, and the technical support is good

Pros and Cons

  • "The most valuable feature is Studio, which allows developers to specifically focus on development."
  • "I would like to see some use cases and additional information on the process mining and the OCR features that are being released."

What is our primary use case?

We are using Studio, Orchestrator, attended and unattended robots.

Our primary use for this solution started with automating processes in finance, procurement, and HR. Now, we are researching various directions in logistics.

We do not run our automations in a virtual environment. This is something that we are trying to avoid.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. I'm an IT-based person, and for IT people it is easy to learn. UiPath claims that it is easy to learn and it's for everybody, but it's not true. For business people, it is hard to learn and hard to understand how to code to make things work. They need a lot of help with things like exception handling. If somebody lacks technical or programming skills then it makes it much more difficult to use. Although UiPath is getting closer to business users, there are still some basic skills that they need to have to make it work.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. When I get new hires it doesn't matter whether they have previous experience in RPA or development, they have to go through all of the basic training from the Academy. This includes the Orchestrator and I've been recommending SAP training because we are experiencing growth in the use of SAP. Going to my team, this is the base, and then we have created our internal framework and standards that also require training. Some people may already have experience with UiPath or Blue Prism, but they still need to take the training from the Academy.

Before I arrived at the company, there were already some automations running. However, fifteen months ago we shut down a couple of robots because they were failing terribly. From that time, it took us five months to create the first robot.

How has it helped my organization?

We have a project that combines UiPath with OCR and our integration tool. This allows us to automate processes we use in different projects that are coming from different vendors in different countries. Apart from gathering the information, we are template invoicing. The robots take invoice information and post the results into our SAP and other systems. It is much faster than our original process. This has been implemented in Spain, and we are now releasing it to other countries, one by one.

Using this solution is not just about saving time or reducing the number of staff. It is also for improving stability and decreasing the number of errors that we have. In Spain, where we were implementing a pilot project for purchase orders, we saw a decrease in the number of human errors. When they started, there was an error rate of ten percent. After three months in production, the error rate decreased to five or six percent, and after six months it was one or two percent. Also, even though there was still an error rate, it was consistent and it is something that we can account for.

In terms of money savings, we are talking about hundreds of thousands of dollars annually.

What is most valuable?

The most valuable feature is Studio, which allows developers to specifically focus on development. Orchestrator allows us to connect those things together.

What needs improvement?

I would like to see some use cases and additional information on the process mining and the OCR features that are being released. There are other products that offer OCR features, and at this point, it is hard for me to determine the benefit of using UiPath for OCR rather than integrating it with another solution. This is not just from a business perspective, but from a development perspective as well. For example, I would like to see how you can connect UiPath to all of the applications to collect the logs and the data. Then, how we can put that information together. If there is a thirty-minute delay then how do you identify whether it was because the person went to lunch, or rather that they were working and thinking.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a three.

The stability of this solution really depends on the developer or the execution. It's not always a UiPath issue. If the process is unstable, it's the issue of the business case and not the actual execution of any development. So it really depends on how you use the platform and how you understand it. We will use a more stable technology, such as alerting through an API, before we go to the UI path.

What do I think about the scalability of the solution?

We have about one hundred licenses for production and four Orchestrators.

How are customer service and technical support?

Both customer support and technical support are really good. Whenever I have a question, whether it is business, Studio, or Orchestrator related, I usually get an answer. We have our own customer success manager who helps us on a daily basis. I also have connections to the lab and to the production team so I can ask questions there as well.

Which solution did I use previously and why did I switch?

At this company, they did not have an RPA solution in place before this one.

Personally, I have also used Automation Anywhere and Blue Prism. From my perspective, it's about how you use the tool, and not about which tool you use. Personally, I don't like Automation Anywhere, and I used to be a Blue Prism guy.

I feel that Blue Prism is easier to learn because you can do things in terms of processes or objects. Logically, it is easier. In UiPath there are more options, but it's also harder to learn because you need to create a logical structure on your own. It doesn't show you how to do that in an easier way. UiPath has more connections and more inbuilt stuff than Blue Prism, but on the other hand, the navigation between the types of variables is slightly different. It's not a disadvantage, but it is something that takes time to learn.

I find that Automation Anywhere is not that user-friendly. For example, in Blue Prism you have loops that you can put a component into. In Automation Anywhere, you have to copy all of those stages, one-by-one. You cannot create a loop, which is basic.

What was our ROI?

We have not been tracking ROI yet, although we are working on it. It is difficult to calculate because to collect the information for each process it requires a logging system. Each project will require a specific logging system so that we can collect the same information to compare and evaluate it. We have to consider our development costs, maintenance costs, licensing costs, etc. At this point, we do not have enough people to work on this, so it is a work in progress.

Which other solutions did I evaluate?

They ran a selection process here and my understanding is that Blue Prism was not able to provide a free Studio license, unlike the policy they now have in place. This is the reason that UiPath was selected. 

What other advice do I have?

The majority of our use cases are unattended, and that is the way that you should go. We do use attended bots as digital assistants, where you have small automations that are triggered by the users on their own to direct the robot. These are two separate products.

My advice to anybody who is researching this solution is not to be scared to use it. Play with it as much as possible and see if it brings value. There are different applications that can bring more value in certain cases.

Overall, this is a good solution, but there are always ways to improve a product.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
NK
Operations Support Sr Manager at Etisalat UAE
Real User
Unattended robots save us time, provide good value, and the training is good

Pros and Cons

  • "The unattended, back-office robots are the most beneficial feature."
  • "The Form Builder for back-end robots needs to be a web portal instead of a full desktop application."

What is our primary use case?

We use Studio, the Orchestrator, and we have attended and unattended robots.

Our primary use case is automating back-office processes from the corporate side. One example is the automation for ticket closure for some of the customer complaints. We also use it to fill information gaps between systems. Instead of having information run through standard APIs, we have it copied over from one system to another.

We run automations in a virtual environment, and the implementation was pretty easy and quick.

We used the Community Edition before purchasing our license. From the point that we purchased our UiPath license until we had our first robot was approximately one week. We found it to be very easy and very fast. We, as a Contact Center, usually face a lot of problems when we suggest any requirements. When we started with RPA, it took approximately one month for a very complex process to be automated.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. It is very easy. You can use the UI, or you can use APIs for the connection. In the end, you can do it.

On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In two or three weeks, an RPA developer can do everything.

How has it helped my organization?

In the Contact Center, the key issue is the handling time. RPA has helped us to decrease our time, and eventually, it will help to decrease the headcount.

For one of our processes, it reduced the time it takes from five minutes to somewhere between forty and fifty seconds. That saves a lot of time.

In terms of eliminating human errors, there has not been much difference because we have very strict processes and strict steps for them, so human error was minimal, to begin with. Our success is in the reduction of time to complete them.

What is most valuable?

The unattended, back-office robots are the most beneficial feature.

What needs improvement?

The Form Builder for back-end robots needs to be a web portal instead of a full desktop application. 

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution between three and four. For exception handling, it means that a senior RPA developer has to understand the reasons behind the process. If they have not been exposed to it then it is easier to perform some simple fixes and continue the process.

What do I think about the scalability of the solution?

We have implemented eighteen processes so far, they are they used in several departments. In total, we have approximately four thousand people who are using this solution.

From a scalability point of view, we're not that confident that we can have the robots running twenty-four hours a day with a huge transaction. Being a telecom operator, we have a lot of transactions and the stability of the unattended robots needs some enhancement.

How are customer service and technical support?

I think that both customer support and technical support are very good. When we have any questions or any issues, we are connected immediately. 

Which solution did I use previously and why did I switch?

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

We learned about RPA because one of the contractors was working on an RPA PoC at our company, and we were convinced that it could help us a lot. The IT people were invited to see the technology and from there, they decided to implement it with our in-house IT group.

How was the initial setup?

The initial setup of this solution is straightforward. We used the Community Edition and it is very easy to use. 

What about the implementation team?

We performed the implementation on our own.

What was our ROI?

We realized ROI in approximately six months. Our cost savings come from savings in agents.

What's my experience with pricing, setup cost, and licensing?

From a cost perspective, unattended robots are better. They run twenty-four hours a day and do not require running on a client machine. The attended robots are not as cost-effective.

Which other solutions did I evaluate?

We did evaluate one other RPA solution before choosing this one. Our main reasons for choosing UiPath were the price and the ease of development. The Community Edition is very useful, and we are easily able to find RPA developers working in UiPath. This is different than with some of the competing products.

What other advice do I have?

My advice for anybody researching this solution is that it is easy to download and it has a big community. A PoC can be done easily, and you can decide from there whether this solution is suitable.

This is a good solution, but the stability of the unattended robots needs to be improved.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
SP
IT Manager at a mining and metals company with 10,001+ employees
Real User
Orchestrator is easy to use and safely stores system credentials

Pros and Cons

  • "The most valuable feature in Orchestrator is that it stores the credentials in a safe way."
  • "I have trouble understanding the machine learning and AI components, so I would like it to be easier to understand how and what to do with them."

What is our primary use case?

We are using Studio, Orchestrator, and bots.

We are a consulting company that is working with one of our clients to automate back-office accounting processes for a logistics company. There are five people in the core team who are working on the implementation.

We run automations in a virtual environment, but I was not responsible for the implementation.

With respect to how easy it is to automate the company's processes, on a scale of one to five, I would rate it four. It's very easy, but it is difficult to explain to our customers who are not as technical. In other words, it is difficult for people who are coming from the business side.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. Without it, I don't think that I could have started the implementation. I completed the developer program just for a general understanding of how everything works, including the Orchestrator and how it all works together. For me, the training was really important. It was very good and I really liked it.

We were working with the Community Edition at first, but from the point that we purchased our UiPath license until we had our first robot was approximately one month.

How has it helped my organization?

In terms of eliminating human errors, we expect to see this benefit later. Until this point, we haven't touched the processes where there could be human errors. We just started with the really basic ones, which are so easy that people don't make errors there, and neither do the bots. We plan to get to the more complicated processes next.

With respect to saving time, I can say that this solution has helped, but at this point, I don't know by how much.

While we were implementing this solution, we were empowering people. This solution changed the way people are working because it is so open and everybody can take part in it. It caused them to think about their processes in a different way, with automation in mind and possibilities for the future. Now, when they're having strategy meetings, they have dedicated time slots where they're just talking about processes that could be automated, so the whole mindset is changing now.

What is most valuable?

The most valuable feature in Orchestrator is that it stores the credentials in a safe way. Our clients were afraid that the credentials would be stored where somebody could see them and being able to schedule bots with the credentials available is very important for them. 

What needs improvement?

We would like to see Studio made a little easier so that our non-technical customers can also implement the bots. For example, some of the features from the upcoming Studio X should be put into the original Studio, as well.

I have trouble understanding the machine learning and AI components, so I would like it to be easier to understand how and what to do with them.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution between three and four. Sometimes there are issues where something is not working, although there are probably times where it happens because we don't know how to use the solution in the best way.

How are customer service and technical support?

Both the customer support and technical support for this solution are very good.

The technical support has been very helpful. Our team has had many calls with UiPath regarding the virtual machine, which did not work at first. Within two days it was working.

Which solution did I use previously and why did I switch?

Our clients did not use another RPA solution before this one.

They are undergoing a digital transformation and wanted to give themselves and edge so that the other companies will not get ahead. They just saw the need to change and we told them about RPA and they got very excited. We showed them the first pilot bot and they were ready to implement it.

What about the implementation team?

Our in-house IT department handled the initial setup.

What was our ROI?

We have seen ROI and performance benefits from using this solution. While I do not have specifics in terms of money or time saved, I think that we could see the benefits after a week. There were processes that the client no longer needed to do, so they had more time available for other things.

What's my experience with pricing, setup cost, and licensing?

For our first customer, we started with Orchestrator, an unattended bot, and a couple of Studio licenses, all of which cost $25,000 USD for the year. It is definitely worth the money.

Which other solutions did I evaluate?

We had researched Automation Anywhere and Blue Prism, but we didn't look too deeply.

The choice for UiPath was made based on what we read on the Internet, including the Gartner Report. It was very easy to get started after first downloading the Community Edition and then taking the Academy to learn how to do it. It is easy, fast, and the statistics say that it is the best.

What other advice do I have?

Right now, this is a good solution that I would recommend. It is really beneficial for a lot of companies. At the same time, there are things that can improve and they are working on them.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PM
RPA Architect at AXA Equitable
Real User
Way ahead in terms of providing features, customer support, ease of use, and in the development of robots

What is our primary use case?

We use all three of the UiPath components which include: Studio, Roboyo, and Orchestrator. There are a bunch of use cases that we explored for the POC (Proof of Concept) to be sure the product fits with our expectations for automation. For example, one use case is reconciliation processes for insurance group retirement and LOB (Law on Occupational Benefits) plans. We built it, tested it, and now that is one of the primary things we use the product for.

How has it helped my organization?

This solution has improved the way our organization functions in several ways. It has helped to eliminate human errors. It already saves 20 hours per month for reconciliation and LOB. It helped clients schedule their transactions before the end of the month. All of that automates tasks and makes financial processing faster in the insurance industry. That works out great for us.

What is most valuable?

The most valuable features provide solutions for when I am using OCR (Optical Character Recognition) technology. It easily integrates with Google OCR, Microsoft OCR, and ABBYY OCR. We are using that integration feature to incorporate OCR mostly for reading scans. To interact with Google OCR, Microsoft OCR, or ABBYY OCR, you don't need to implement a separate component but you can just — in a blink of an eye — integrate those peripheral solutions into the UiPath Studio and use them in your automated processes.

If we can integrate other features that are not part of UiPath, it makes it far more useful in automation. In this case, UiPath is not building out an actual OCR component but they are just giving you an option to incorporate the other OCRs. That is very valuable.

What needs improvement?

In the next release of the solution, I would like to see the ability to grant permission to users at the job level. Some jobs or processes may need to belong to only one person. Right now, I believe we don't have that feature in UiPath and we can't assign a job to a user. We can give permissions on a tenant level, or we can give permissions on the environment level, but not at the job or process level. 

I would like to see the ability in UiPath to be able to assign each job or each process to a particular user and give that user some specific access and privilege. For example, maybe they should only be able to run or stop a particular job or a particular process, but they can not do anything else. That makes a lot of sense because all users may not need to see all the processes in Orchestrator in one instance or have access to administrative features. The same goes for a tenant or even in an environment. If UiPath can make that happen at the user-level or process-level for a robot, that helps a lot to enable customized bots.

What do I think about the stability of the solution?

On a scale from one to five where five is the best and one the worst, I would rate the stability of the UiPath platform at a four-out-of-five. The stability is a four instead of a five because the stability is not completely dependent on only UiPath. Underlying obligations play a part too. Sometimes when I am writing applications, I'm not up on how to handle every exception. That is not possible because a developer does not know all the scenarios an application can become involved with. In that scenario, the product can lag. But, otherwise, it is really a very good solution that is dependable and stable.

What do I think about the scalability of the solution?

Approximately five people in our organization are involved in our automation program working in the CoE (Center of Excellence). There are four developers and there are 200 users including business users. So, you can say there are around 250 people currently involved in this. I don't think scalability is an issue.

How are customer service and technical support?

We did have the opportunity to use UiPath Academy RPA training. On a scale from one to five where five is the most beneficial, I would rate the training as a four-out-of-five. It is good for basic understanding. We have usually had UiPath foundation training for all of our developers. Really, I think you can say that we have not put fully utilized it.

Other parts of technical support we have only used very minimally. For example, we have not used premium support or licensed support levels. Sometimes we called customer support on tickets to integrate with mainframe obligations the first time or some more involved issues. But that type of situation was unusual. We have barely used the customer support because most of the information is available in Academy, in the portals, or the user forums. A few times when we left a ticket, it was not even necessary for us to get back to technical support because we resolved the issue on our own.

Which solution did I use previously and why did I switch?

We knew that we had an opportunity to invest in a new solution when we heard about RPA three years back. UiPath and WorkFusion came to us at the same time and saying, "We have a solution to improve your work processes."

We spent some time evaluating which tool was right for us by doing a study inside our organization to determine how much manual work could be automated. With some analysis, we found out that there is a huge opportunity for implementing this type of RPA solution in AXA (global insurance, not an acronym) as it is a large organization with a lot of repeated processes.

Because there was a lot of manual work, people in our organization had to work for more hours at times to properly complete a job. Sometimes they had to stay overnight and work additional hours on weekends to complete processing on time. To avoid that we requested that operations consider our proposal for automation.

We showed operations where we could automate repeatable and mundane tasks. The response was very positive and they realized we need to implement these solutions to help us to buy some time for employees to properly do their work and reduce labor intensity.

Our previous solution was either no solution at all except for manual labor or some experience we had with one tool called OpenSpan. OpenSpan did not have a proper management console and was difficult to use so it mostly remained unimplemented. When we introduced the potential solution for seriously pursuing RPA to reducing the workload, that is when we started looking at UiPath.

How was the initial setup?

The set up for the product is straightforward. It is seamless. In fact, you just need to know the server where it will reside. There is material available in UiPath guides and the UiPath forum where you can just follow along step-by-step and install your Orchestrator. So it is very straightforward. 

From the time we purchased the UiPath license until we had our first robot in production is not exactly clear. We had developed a POC, which was ready to be put into production and then we bought a license. After we bought the license, we just put it into production and it had already been built.

What about the implementation team?

We did the entire implementation ourselves with some contact with UiPath.

What was our ROI?

We are not yet really realizing a return on investment as our deployment continues to be in progress. How much money we have saved is what we are hoping to eventually count in the ROI. In terms of the calculations that we started last year, we asked that the KPI (Key Performance Indicator) points look at time-saving and not really the dollar saving. The time saving you can say approximately 20 hours per month, which we have achieved consistently up until now. We have achieved something but we are expecting that to grow a lot.

The solution has also helped to eliminate human errors. I cannot say exactly what that percentage is —  say even 20% or something like that. There are a couple of instances before we automated the reconciliation process last month — before we actually put the bot into production — where people were getting the wrong details by mistake. I would say we have reduced the human error because those situations are being handled by the bot and they will not be repeated now. 

What's my experience with pricing, setup cost, and licensing?

We license the product on a yearly basis and it costs us around $80,000. We are a very large organization. We have unattended bots and there is a pricing structure surrounding that but I'm not involved in the licensing terms.

Which other solutions did I evaluate?

What made us choose UiPath to automate our processes was evaluating the capabilities of competition and deciding on the best solution for us. We compared UiPath, WorkFusion and other products — and even other types of tools — in terms of infrastructure, setup, how easily it could be scaled, etcetera. UiPath stood out a little as it had the capability to invoke virtual machines automatically without any human intervention. A lot of other tools didn't have that capability at that point. But the time we had to come down to a decision, UiPath had features that were not available in any of the other tools. With other research into the company and product, we saw that UiPath listened to the customers' needs and was often upgrading. Now all the competition has seen them as the leader and they have tried to incorporate features UiPath had already deployed.

That initial difference we saw between UiPath and the other tools we compared was the reason we took this direction. We believed UiPath and we decided that this was our theater for RPA. Now, if we see some enhancements that need to be made in the product, we just communicate to UiPath and we know they will look at the idea and maybe implement it. UiPath has the capability of adding features immediately. They are releasing around 10 or more versions in a year with important new features. 

What other advice do I have?

We do use a virtual environment such as Citrix when it is appropriate and that works out pretty well. The obvious advantage is there is no dependency on a physical machine being available and they are available 24/7 from anywhere. I am actually comfortable developing anything and everything in Citrix via virtual machines.

On a scale from one to five where one is very difficult and five is very easy, I would rate the ease-of-use of the platform as a five. Ease of use is one other thing that I like a lot about UiPath.

Going a step further, on a scale from one to ten, I would rate this product overall as a ten compared to other RPA solutions. In comparison to its nearest competitor — Blue Prism — UiPath is way ahead in terms of providing features, giving customer support, ease of use, ease of access to our personal history, and surely in the development of robots.

Everybody can understand easily what exactly the product is doing and can become familiar with it quickly. With other competitors, there is a huge infrastructure to set up. Some of the products make it so each bot needs a control room. Those products are not centralized, which makes them more confusing to use.

People have to manage on their own how they are going to build all their RPA management solutions. When you are using UiPath, you just get Orchestrator instead of multiple robots and control panels, then you just scale whenever you want.

I definitely recommend UiPath for simplicity and ease-of-use. If somebody was getting an RPA solution, the advice I would give them is to definitely go for it. Setting up RPAs eliminates human error in tasks and lightens workloads for menial jobs. This lets people focus on more innovative work and it can lead to further integration. What I would think is the natural path for UiPath is that it can integrate the AI in the future. Right now, people think that this is already cognitive or AI integrated, but there is a very long way to go in the future for it to become truly like artificial intelligence.

So, what I am saying is I would take it as a first step towards the AI. I would definitely recommend people use it so that in future when AI comes in, you can just grab an AI solution from UiPath and improve your implementations further.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Karil Quintana
RPA Develepor at Equinix, Inc.
Real User
Has flexible coding, good stability and solid support but it needs better scheduling options

What is our primary use case?

We use only unattended robots with Studio and Orchestrator. Our primary use for the bots is in finance, so we only do finance use cases like AP (Accounts Payable) invoice retrieval.

How has it helped my organization?

The solution has improved the way our organization functions because no one has to sit for hours just spending time retrieving documents. The staff just picks up the documents they need in the morning, start their analysis right away.

What is most valuable?

What I find the most valuable about UiPath is flexibility in adding code. That ability is the most important feature for me and what I do.

What needs improvement?

In the next release of this solution, I would like to see better scheduling options. Because of the schedule limitations, you can only schedule one process at a time. There are situations where I might want to build five processes that need to work together. As I can only schedule one at a time, it isn't currently possible.

What do I think about the stability of the solution?

On a scale of one to five where one is unstable and five is very stable, I would rate the stability of the UiPath platform as a five. There are not many issues at all. On other platforms that we use, we always seem to encounter small things that cause problems. For example, with other solutions, we have had problems processing things like resolution and there is always an issue. But with UiPath, I can control almost everything from the robot and get it working.

What do I think about the scalability of the solution?

There are ten people in our organization involved in our automation program and I think it can be scaled at any time.

How are customer service and technical support?

While we don't use technical support directly, our team has used UiPath Academy RPA training to become more familiar with the product. On a scale from one to five where one is the least beneficial and five is the best, I would rate the Academy experience as a five. We've also used the forum. In all, between the implementation help, the Academy and the resources, I would rate the support as a nine-out-of-ten.

How was the initial setup?

From the time we purchased the UiPath license until we had our first robot in production took only about one month, and that was without previous experience with the product. The initial set up of the product was straightforward, so it was all pretty efficient.

What about the implementation team?

We did not need to use an integrator, reseller, or consultant. We did the entire implementation all in house. The only exception is that we did get some help from UiPath by working with them directly. 

What was our ROI?

We have experienced some return on investment and performance benefits, and it only took about one month to see it. There is one monthly process we use and in just one run — the first time we ran it — something that took two people two days was done in two hours. So, what took 16 hours to do analysis on before has been cut down to two hours. It is hard to say how much money that saved as we just changed the allocation of resources. The solution also helped to eliminate human errors which are even harder to account for.

Which other solutions did I evaluate?

We chose to try UiPath because we wanted to test the SQL capabilities that it has. I don't know that I would say we evaluated other options before choosing it as a solution. We currently work with both Blue Prism and UiPath at the same time. 

What other advice do I have?

On a scale from one to five where one is very difficult and five is easy, I would rate the ease of use of the platform as a seven. I think that especially business users who don't have more of a technical background can get lost in all the different features that are available.

For this solution, we could totally deploy with attended robots, but our business just isn't ready for that yet. I think, with the adoption of Studio X that we might be in that position, but not right now.

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a seven overall. The scheduling feature just isn't there yet to allow more flexibility in programming and use, but the development is much faster and the flexibility better than much of the competition. The introduction of open-source changes the game for RPA solutions.

The advice I would give to a colleague at another company who is researching this solution or a similar one would be to clearly evaluate the use case. Don't just breeze through and assume you need automation. Take a good look at what you actually need to do, make sure the solution fits, and make sure the targeted processes are processes that should be automated.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
MB
Product Manager at a financial services firm with 201-500 employees
Real User
Saves the organization time, and enables the reallocation of resources but reporting needs more development

Pros and Cons

  • "Customer support is a bright spot and helps give users confidence in the solution."
  • "We are having some on-going stability issues."

What is our primary use case?

We use Studio, Orchestrator, Studio and Orchestrator right now for RPA development for automating pretty much anything that rules-based processes can accomplish that are mundane and take time. 

How has it helped my organization?

UiPath has improved our organization simply through the ability to automate. Creating rules-based processes and making them automated can allow us to make better use of people's time. Now people are not working weekends and overtime. People are working their regular hours and doing their regular jobs.

What is most valuable?

I would say the most valuable feature in the solution is Orchestrator in conjunction with the customer service piece which is also very valuable. The ability to troubleshoot whether it is infrastructure support or a development support issue, having somebody to reach out and provide feedback is very beneficial.

What needs improvement?

One additional feature that I would like to see included in the next release of this solution — and actually looking forward to — is more development in the reporting. The Insight piece that was announced was very good to hear about. We are excited about that and looking forward to it just so we do not have to develop our own reporting infrastructure. Instead, we can leverage UiPath's Insight platform to do reporting, deliver reports, measure production errors, and further simplify how we gather and assess information. As far as room for improvement, I would say that is my biggest missing piece.

What do I think about the stability of the solution?

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of UiPath platform as a three. Right now, we are having some connectivity issues, between Orchestrator and our environment. We have been working with our infrastructure support team and UiPath infrastructure report team to figure out what's going on. We are working through the issues and I'm very impressed with the support that we have been given, but we have got to figure out what the issues are and solve them.

What do I think about the scalability of the solution?

We have approximately 15 people in our organization involved in the automation program and I don't think it would be difficult to scale that usage up.

How are customer service and technical support?

I would say that overall I'm very pleased with the customer and technical support from UiPath. They have been very responsive. If there is any need or if there is an issue, they are good at getting to work on finding a solution. They also provide additional resources.

Our team used UiPath Academy's RPA training and on a scale from one to five, where one is the least beneficial and five is the best, I would say the training is probably a four-out-of-five. The feedback that I've gotten from others that attended is that it is very informative and they are good training courses. The tests are challenging enough that it makes participants involved so that they are prepared for the next course. So mostly the RPA training is a positive experience.

Which solution did I use previously and why did I switch?

We did previously use a different solution, but it was a proprietary vendor solution — one of our servicing vendors created it. They were not able to deliver solutions of service packs within an expected timeline. We had to identify different short-term and long-term needs and decided to invest in a new solution. We had to identify a way to bridge some of those gaps in the interim until we could get those upgrades on that platform.

We ended up choosing UiPath automated processes on the recommendation of Accelerate who we were using as a consultant.

How was the initial setup?

I would say the initial setup was straightforward and it wasn't too complicated. From the time we purchased the UiPath license until our first bot introduction I think it was only about two months. The installation itself was easy too. We were able to install it on-premises, get all the licenses running, get all our basic needs set up so we could do development, and put a bot into production. It was not a long onboarding process before we started seeing results. 

What about the implementation team?

We did use the assistance of a consultant for the deployment. That would be Accelerate. Our experience with them was okay. On a scale from one through five I would say they scored a three-out-of-five. The delivery was not quite what we expected and did not meet our timeline. We set out with a goal and we fell short of that goal, and we're working with them to help us have a good forward-thinking plan. Delivery was not fully met, so we weren't too happy with that. But otherwise, they were right there.

What was our ROI?

We have seen a return on investment and some performance benefits. For example, we were able to pretty much completely automate one process that had two FTEs (Full-time Employees) who were spending 40 hours a week completing a process. Using UiPath we were able to almost completely automate that process and bring that workload down to 10%. So now the bot does 90% of the work and they just handle Excel. 

I think I could say we'll save approximately $400,000. Somewhere around there. But it isn't just financial savings. The solution helps to eliminate human errors, saves the organization time, and allows the reallocation of resources. I would say, based on the use cases that we have, we have saved roughly 60% of our effort on automated processes. So the users are now managing business exceptions that they may have and are handling things on a higher level.

Which other solutions did I evaluate?

I don't know if we had additional options on a shortlist because I wasn't involved in that part of the selection process. I was brought in a little bit later. But there are obviously a host of different vendors that have different solutions that Accelerate would have been aware of. We went through a vetting process and identified Accelerate as our number one choice as a consultant. From there, UiPath was the vendor they suggested, so that's how we got connected with UiPath.

What other advice do I have?

We run our automation in a virtual environment. The implementation is good. We are having a few issues. I don't know if it's directly related to the virtual environment, but we are having some connectivity problems which affect stability. Otherwise, we're good.

On a scale from one to five where one is very difficult and five is easy, I would rate the ease of use as a four. It is a four and not a five for the simple fact that the product does not really achieve the level of simplicity I expect. I'm not a technical person. Most non-technical people can — if you're kind of familiar with the different workflow options and sequences — go in and develop some things you need to accomplish for automation with this tool. I would say that for more complicated pieces, you need a more technical background. The focus on making it easy for non-technical users is very important and they could do a better job of it in my opinion.

On a scale from one to ten, where one is the worst and ten is the best, I would rate this product at probably a seven out of ten. That leaves a lot of areas for improvement. On the other hand, I'm pretty pleased with the product and what UiPath has delivered.

The advice I would to a colleague at another company who is researching this solution is that with UiPath, customer support is a driver. Anybody can deliver a product, but it's what kind of system or service you provide to back it up that can matter as much or more. My experience has been great with UiPath and their ability to provide excellent support matters a great deal to my customer experience.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Brian Schall
Project Manager at MidAmerican Energy Holdings Company
Real User
Gives us the ability to have an agile development group to do automation without relying on IT but we've had issues with stability

Pros and Cons

  • "The ability to automate processes allows the opportunity to allocate resources differently."
  • "The bots do not seem stable and we spend a lot of time fixing things that break."

What is our primary use case?

I'd say our finance applications, like accounts payable, have been our biggest use cases for this solution. 

What is most valuable?

I would say just the ability to be able to go outside of the IT department in our organization to get things done and have a sort of agile group to do automation. It is difficult to get IT involved in this type of thing in our organization. So being able to have our own agile group is beneficial for us.

Another thing that is valuable is that I think it's just saved a lot of our finance and customer service people a lot of manual time on processes. We are just able to involve a lot more value-added work.

What needs improvement?

I really liked the insights dashboard. I guess that there is an additional fee for that. Being able to see your return on investment in real-time is definitely beneficial. We spend a lot of time manually calculating how many hours we saved and that would make it a lot easier. The improvement I want is already there. I have to look into implementing it.

The area of the solution that has room for improvement is the stability of the bots. It just seems like we have spent a lot of time trying to fix bots that are down and whether that is our coding or the product. I think there must be a better way to diagnose the issues and avoid them.

What do I think about the stability of the solution?

On a scale from one to five, five being the most stable, I would rate the stability of the UiPath platform as a three. We've had a lot of issues with bot stability. I don't know if it is how we go about development or if it is the platform itself, but we spend too much time trying to fix all the bots that seem to be breaking.

How are customer service and technical support?

I have not used technical support personally but our IT group has. Everything I have heard about the customer services group has been positive.

I have used the UiPath Academy RPA training. On a scale from one to five where one is the least beneficial and five is the most, I would rate the UiPath Academy as a four out of five. I'm not an IT person, so would have given it a five if I was. Parts of the training may have been more advanced than I expected.

Which solution did I use previously and why did I switch?

We had a lot of archaic processes in our company — a lot of paper-based processes — so we knew we needed a better solution. That meant we had to work through a lot of processes and re-engineer what we were doing. We knew that we needed to move in the direction of automation because the processes were just not sustainable. We had processes but we did not actually have an automation solution until we started using UiPath.

How was the initial setup?

The initial setup for the product was something I found to be a bit complicated. At least the first couple were pretty complicated. It was just that we were all new to the technology and we didn't really know necessarily what we were doing. It is getting better. From the time we purchased the UiPath license until we had your first robot in production, I think we took about three months.

What about the implementation team?

We did you use an integrator. It was EY Technologies (Ernest & Young). They helped us out a lot and our experience with them was good.

What was our ROI?

We have certainly seen a return on investment. As far as how many months it took to see real value, I think we just crossed that threshold. So it was about twelve months in total. We have probably saved — just at our platform — around $100,000. The solution has also helped to eliminate human errors with a couple of the bots that we've deployed for sure. It has also saved our organization time. If I had to estimate, I'd say probably 8,000 hours a year so far.

Which other solutions did I evaluate?

We looked at Blue Prism, Automation Anywhere, and UiPath. We kind of landed on UiPath because it just seemed like it was a little easier to navigate than the other ones from a user experience.

What other advice do I have?

Currently, we do not run any of our bots in a virtual environment and we use only untended bots so far. Either of those situations could change at any time. We have a couple of processes that we are looking at for attended processes, but we haven't implemented any yet.

We have about five people involved directly in the initiative. On a scale from one to five where one is very difficult and five is very easy, I would rate the ease of use the platform for automating as a four. It is a four because I would say it takes a little time to kind of get up and rolling for a developer, but it is not too bad.

On a scale from one to ten where one is the worst and ten is the best, I would rate this product a seven. We have just had some issues with keeping bots up and running. I feel like the issue is the learning curve.

The advice I would give to a colleague at another company who is researching this solution is to just do it. Make sure you know what processes you are going to want to automate. If you need to do standardized anything in the processes, do that on the front end in the planning stages versus kind of chasing your tail on the back end.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
KS
Senior Consultant at a financial services firm with 10,001+ employees
Real User
Attended robots guide our users saving them time, minimizing training, and reducing errors

Pros and Cons

  • "We did not have to do a lot of customization because the standard UiPath activities fit our needs."
  • "I find it difficult to set up the Orchestrator and it should be more user-friendly for non-technical people."

What is our primary use case?

We primarily use the Studio, which is for developing the robots, and we deploy to Orchestrator.

We went through a large SAP transformation and we had a lot of issues getting the users to accept the new systems. They were issues related to the adoption of new systems. We decided to build these attended bots in order to guide the users through the system. Essentially, it is navigation or guidance assistance. By helping the users with proper data entry and design, flowing in a logical sequence that is easy for the user to follow, it minimizes end-user training.

Running our automations in a virtual environment is something that we had tried during our PoC. Currently, we have attended bots deployed in more than twenty thousand laptops, and eventually, we're planning to have more than eighty thousand deployments. Because of the large scale, initially, we were having a lot of challenges because of things that go on with the users' machines. We wanted to explore Citrix because there is just one virtual environment that every user logs on to, and then run the processes from there. Unfortunately, it did not work for us. We were seeing a lot of issues and felt that it was much more stable deploying individually to each laptop, instead of using Citrix.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. There is always room for improvement.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. The material is very sequential and logical. You don't get lost because you just follow the modules from beginner to intermediate to advanced. You cover everything from end-to-end, and it is very structured.

From the point that we purchased our UiPath license until we had our first robot was approximately one year. This included our pilot project, then the development and the UAT. When we went live in production there were three thousand users. 

How has it helped my organization?

This solution saves our users time. For example, on a standard SAP system where a user has no training, and you tell them to go and finish performing a transaction, it will take them between thirty and forty minutes. Now, with these attended bots, it is almost reduced to half. They can finish the same transaction with minimum training in probably fifteen minutes.

This solution has definitely reduced human errors. We have cleaned up the transaction screens and we help the user to focus on what is needed. We give them the right instructions to make sure that they enter the right information.

This solution is mainly used for navigation, position making, and reducing errors. It means that we have a quicker time to finish any transaction. We are a financial organization, so obviously, for us, it's important to record every sale that we make and every client that we have. It has significantly helped our client servers to reduce the time that they spend on these systems to finish a particular transaction.

What is most valuable?

The most valuable feature of this solution is the ease of using it. This includes the way the activities are set up, and how easy it is to solve problems by searching with Google if we're stuck.

We did not have to do a lot of customization because the standard UiPath activities fit our needs. This is a big point for us because we end up customizing most of the products that we use just to satisfy our own business needs. In the case of Studio, we didn't have to create a lot of custom activities.

What needs improvement?

I find it difficult to set up the Orchestrator and it should be more user-friendly for non-technical people. I understand how we create packages and push them, but I find the maintenance hard to follow. As it is now, I have to contact our IT department, which takes two to three days. In the meantime, we just have to wait.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four. In terms of attended automation, we did have a lot of issues. We have requested lots of product enhancements, which then came through the pipeline. Initially, we did see a lot of issues and they had to make some changes to cater to our needs. Also, we have some more requests that have been put in the pipeline to make it a bit easier for us.

What do I think about the scalability of the solution?

We have about twenty people working with RPA in our organization. At this time we have automations running on more than twenty thousand laptops.

How are customer service and technical support?

The technical support for this solution is very good. They're very responsive.

We have had people working on-site at UiPath too, and they have been hands-on trying to see what we are solving. They have given us very good and very relevant suggestions, which has been helpful for us. 

Which solution did I use previously and why did I switch?

We did not use another RPA prior to this solution.

We knew that we needed to invest in this solution based on user feedback. When we launched our new SAP system, everybody kept complaining about how difficult it was to use. There is a lot of training involved, but it's not like you can remember the training. We replaced fourteen hundred systems and put them into a single instance, so even if you are trained for weeks it is hard to remember all of it.

Basically, we needed something that was easier and helps us navigate through the systems so that we can complete our transactions. This solution does just that. It guides the user, waits for the user to give the right input based on what is expected, and then takes the user to the next relevant screen so that they can perform the transaction.

How was the initial setup?

The initial setup has been complicated for us. After we went live in production, one of the issues we saw, but didn't realize initially, was that even though the tray was not open, by default though, if the bot is pushed onto a user's machine then it will be connected to the Orchestrator. Even though the user is not running the process, the bot always stayed connected. That was causing a large load on the Orchestrator and we didn't realize it until we started increasing from three thousand to twenty thousand users. That's when we were seeing a lot of timeouts. The production connection kept dropping and we were not able to figure out why. UiPath helped us to restructure the whole SQL database and the way we established the connections.

What was our ROI?

We have not yet seen ROI, although I think it's too early because we only went live two or three months ago. The big expansion in users was just this week, so it is too early for us to say.

We do know that we have been receiving very positive feedback so far. The users with machines where these bots are deployed have been saying it is very easy to use and there is minimal training required. It's out there, on the desktop or laptop, and they just have to launch by clicking the play button and the process starts. 

Which other solutions did I evaluate?

When we started this project, we explored Blue Prism and Automation Anywhere. I don't think that they were able to give us what we were looking for in terms of attended automation. When we looked at UiPath we found that it could satisfy all of our business requirements, which is why we chose this solution over the others.

What other advice do I have?

I am really excited about the new Studio X. Ours is a consulting firm where not everybody is tech-savvy, but everyone wants to get their hands into automation. UiPath is saying that it is going to be very easy. Even for people without a technical background at all, they will be able to build their own process and bot. I'm looking forward to seeing how our users are going to make use of that within the UI.

This solution is easy to use and adopt in an existing environment. The best part for us is that even though some features were lacking, the turnaround time to have them implemented was amazing. We have always coordinated with our UiPath partner to tell them what it is that we need. When we have requested features, we have found that in the next release they are added. We found this unique among vendors.

My advice to anyone who is researching this type of solution is to definitely go for it. There are a lot of materials out there which will help them make the decision. Our own journey showed that it was easy for us to use, learn, adopt, and finally deploy.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Storm Pracht
RPA Developer at Security benefit
Real User
Annotation is very easy to do and it helps to make things clear to understand during development

Pros and Cons

  • "The product helps us establish and maintain best practices while simplifying workflows."
  • "The IDE could use some improvement, but most improvements that come to mind have already been announced for release."

What is our primary use case?

We are in the finance industry, so we use Studio and Orchestrator to automate a lot of Excels and making reports.

How has it helped my organization?

The product has given us the opportunity to automate processes for our industry and specifically for our business. We have set up best practices. So we know what description needs to be at the top in the code. We just start there, read what's going on. Automation just makes everything simple and standardized while reducing human error.

What is most valuable?

I don't know all of the features so the scope of my view is a little limited as to what may be best or most valuable overall. For me, the ease of use is definitely valuable. Assembly of processes is just drag-and-drop and that simplifies a lot of things. Annotation is also very easy to do and it helps to make things clear to understand during development. I can go look at someone else's code and within an hour understand what it's doing without having to consult the other developer. On a scale from one to five where one is very difficult and five is great, I would rate the ease of use of the platform a four. 

What needs improvement?

Even though there are things I'd like to see, I also know that most or all of them are already being announced for new releases. As a developer, I would probably say the most important thing I would like to see is that the IDE (Integrated Development Environment) a little bit more fleshed out. It could use more debugging capabilities, for example. But again, we've been seeing that they're adding stuff like that. It will be getting in there and playing with it when it is released to make sure that it has got all the stuff I want and I might be able to be more specific after that as to what still needs to be added.

What do I think about the stability of the solution?

On a scale from one to five where five means the product is very stable, I would rate the stability of the UiPath platform a five. It works and nothing breaks that is directly related to the product itself.

How are customer service and technical support?

The technical support, communities, and resources are all pretty good. We use the forums and I like the forums a lot. It's crazy how many people actually spend time on it and reply. You get your answer pretty quickly. The guys are really open to work with, so if we need help we just reach out and we get all the help we need.

We also use the UiPath Academy. On a scale from one to five where one is the least beneficial, I would rate the Academy as probably four out of five. It is easy to use. You go in there and you know what training you are looking for and what you need to take. Most of the training is in-depth enough so that when you complete it, you really have a good grip on what's going on. It eliminates barriers to getting the information you need when you need it.

How was the initial setup?

The initial setup and implementation happened before my time at the company.

What was our ROI?

A lot of our return on investment has to do with time savings. It is definitely amazing to see processes that could take eight days before actually run in ten minutes. Just because of automation. It eliminates Hangouts and just makes the whole process and the people involved in the processes more efficient. As far as how much gets saved exactly, it depends on the complexity of the project and what it resolves. We have to invest in our BA (Business Analyst) work so all together it may take a couple of months for anyone project to pay off.

What other advice do I have?

We use the solution on-premises right now, but I think we are going to move to the cloud because of the advantages. We also do not run our automation in a virtual environment, such as Citrix either. Our bots run on a physical server, but there may be reasons in the future to explore virtual environments for that purpose. 

The approximate number of people in our organization involved in the automation initiative, strictly considering developers would be my team of six. It is harder to say how many are using the bot solutions who are not directly involved in the development.

We currently tend to stick more with attended bots which just helps take a measure of human error out of the way. A lot of problems that we had in the past have come from users not updating their personal machines. That can obviously cause things to break. We try to make bots unattended if we can, but it isn't always practical to deploy in that model.

In any case, the solution has definitely saved our organization time and reduces human error either way.

On a scale from one to ten where one is the worst and ten is the best, I would rate the product as a nine or ten. Beyond just the product, there are tons of resources that we have available. Finding things other people have already made is an additional benefit. There's no point in reinventing the wheel if something's already been built.

My advice to people considering the solution is pretty simple. Buy it.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Nathan Boeke
Principal Robotic Configuration Specialist at Allianz life
Real User
Studio saves the QA team a lot of time setting up separate environments, test data, etc.

What is our primary use case?

We use UiPath Studio, Orchestrator and Robots, all unattended currently. Our primary use case is one-off for mediation projects because we're trying to set up our infrastructure. Once the infrastructure is set up, we plan on creating a federated model throughout our entire organization.

How has it helped my organization?

Right now, our remediation teams do a lot of large one-time projects where they have to have policies for scaling up and scaling down the volume of full-time employees. I know we have avoided that situation in at least three cases now where they have not had to hire or remove people because they have been able to automate the remediation process.

What is most valuable?

The most valuable features for me in Studio can be anything that helps me test or debug. It saves me a lot of time and it saves our QA team a lot of time setting up separate environments, test data, and things like that.

The most valuable thing in Orchestrator is just how easy it is and the fact that it's cloud-based. It is also useful in that it allows non-technical users to get information about their projects. For example, they can find out if independent components are up and functioning; if something is down they can find out what went wrong.

What needs improvement?

In the next release of the solution, my biggest hope would be getting more accessibility to test data processing information. I was told that this feature was coming already. Being able to see what my variables and my arguments look like when things are being passed and making the processes very clear to my customers when we are doing test cases for UAT (User Acceptance Testing). That would be invaluable. It would help the customer to see and understand the data flow more easily without having to go through training or being very tech-savvy.

I think Studio has a little more room for improvement and could use a few more features. They just announced Studio X and Studio 2 which actually addressed many of the issues I hope to see resolved, but that is assuming that they come through in development and do what they say they are going to do.

What do I think about the stability of the solution?

On a scale from one to five, where one is not stable and five is very stable, I would rate the stability of the UiPath platform as a four-and-a-half. I've only seen one or two buggy behaviors, so I think that qualifies as extremely stable.

What do I think about the scalability of the solution?

In our organization, there are five full-time people involved in the automation program. We can drag people in from different departments in the business on a case-by-case basis when necessary for resolving issues with automating.

How are customer service and technical support?

Before we started, all of us were involved in using UiPath Academy RPA training and learning through it. On a scale from one to five where one is the least beneficial and five is the most, the Academy is something I would give a three. I say that because I don't think they went into enough detail. I understand that they didn't because they are trying to save time for non-technical people, but I love knowing everything and I would love to see more detail in their presentations or have options to do so.

Customer support overall is very responsive and they say a lot of helpful things, but I'm often able to find the same information and answers on the forums. It would be nice at times to be able to talk to someone from support over the phone. I can describe my problems without having to send dozens of emails back and forth in order to get an answer. It just isn't terribly efficient.

Which solution did I use previously and why did I switch?

The decision to automate and the product selection for the solution were completed before I was brought on as part of the team. I was actually brought on as an expert from another company in order to help them stabilize their deployment. The product vendors which were on the short-list actually include some vendors which the company has licenses for in addition to UiPath, like Blue Prism. They are exploring multiple options because we are a global entity. They want to offer the option to entities to choose whatever partner they prefer to go with.

How was the initial setup?

The approach to the initial setup which was selected was a complicated process. I don't know much more than it took a long time, it wasn't very successful and that's why they brought me on.

What about the implementation team?

They did the entire implementation in-house.

What was our ROI?

We have seen some return on investment to a certain extent, but a lot of it's coming from one-time processes and not from recurring processes. In other words, the ROI is already there, but it is from one-time processes we've deployed. These are processes that we would run a bunch of items through one time and the circumstances are not repeatable the next year or even the next week.

I'm not sure about the exact numbers, but I know that the cost of our department has been saved roughly four times over. Again, a lot of those savings are from one-time events that won't be recurring in the following year so they can't really be seen as predicting the future results.

The solution has helped to eliminate human errors in some cases and that also has value. In addition, there is the benefit of saving the employees time. Right now I believe that we have approximated that we saved somewhere between 40,000 and 45,000 human hours. That resource can be re-allocated.

What other advice do I have?

Part of our deployment is in a virtual environment and part of it is not. The implementation is actually still in progress. We are in the phase of setting up our infrastructure and trying to automate some POCs (Proof of Concepts) and some early successes to show the financial benefits of RPA to the C-suite (C-level executives such as the CEO and CFO).

On a scale from one to five where one is very difficult and five is very easy, I would rate the ease of use of the platform as a four. I think the product is fairly intuitive. Because I come from a tech background though, I feel like it is going to be a little easier for me to understand than some other people who don't have that same background. The only reason I don't give it a five is because the integration between Orchestrator, Robots, and Studio does require a little bit of intimate knowledge to be able to connect them all and make sure that they stay connected.

We have not used attended robots yet, so I'm not sure how cost-effective they are because we don't have any data on that. We use unattended bots and they seem to be effective solutions, but I don't know what they pay for them.

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a nine. The only reason I'm not going to give it a ten is that I have struggled with certain errors and stability issues. Whether that is our fault or a general bug in the actual software is yet to be seen. I have a few open tickets, but I've really liked this software overall.

Advice that I would give to a colleague at another company researching this or similar solutions would be that they look at their organization and see if they are really ready for deploying RPA solutions. A lot of RPA solutions are sold with the promise that anyone can build solutions with the products and the bots are going to deploy quickly. I don't think quick deployment is deceiving, but I do think that trying to implement a solution that does move so quickly like this into an organization that doesn't move quickly can create friction.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
CO
RPA Manager at a government with 10,001+ employees
Real User
Recording tools enable the capture of user actions on the screen and then the recordings can be converted into workflow sequences

What is our primary use case?

Our primary use for this product is to automate processes that we are capable of automating at our tier-one level human resources center.

How has it helped my organization?

This product has improved the way the organization functions by helping us go through a digital transformation. RPA is able to bridge a lot of the gaps that we had in our processes and processing what we had before we moved to this platform as a solution. With a little effort, I was able to bridge those gaps and automate a lot of processes that were manual and less efficient prior to involving the product.

What is most valuable?

The most valuable features for us are the recording tools. They allow the capture of user actions on the screen and then the recordings can be converted into workflow sequences. The activities are very simple to use and easy to put together in order to automate the processes. Once we get Orchestrator, that feature will probably be the most valuable, but we are currently not able to put it into production.

What needs improvement?

As far as additional features, there doesn't seem to be anything outstanding that I can think of right now. Maybe some off-the-shelf "How To" features could be installed with Studio so that you can search for how to do something and pull it up directly in the Academy or on-screen without leaving the product.

There could be room for improvement in the ticketing feature. It's kind of hard to find that feature sometimes.

What do I think about the stability of the solution?

On a scale from one to five, where one is the least stable and five is the most stable, I would rate the stability of UiPath as a five. It is very stable. We have never had any issues with regards to UiPath. The actual problems seem to be network issues and our environment.

What do I think about the scalability of the solution?

We started out sort of small in the beginning and we've invested more in buying licenses and functionality. The scalability in that way seems very good.

How are customer service and technical support?

My experience with customer service has been very good. They make a few different types of resources available and it is usually pretty easy to find what you are looking for. For example, I have used the RPA Academy. It is pretty easy and it was very beneficial. I haven't really opted for using customer support or technical support much. I've been able to just call, text, or email somebody and get a solution.

Which solution did I use previously and why did I switch?

There were really no automated processes when I first came on to work at this organization. When we made the decision to go in this direction, we made a comparison of products to solve the automation issue. What made us choose UiPath to automate our processes was price, availability, ease of use and customer services. They were also willing to be the quickest to work with us as well. It seemed to be the best mix of all these.

We knew we needed to invest in a new solution because, where I'm working, we had 600 or 700 processes that I knew could benefit from automation. As an industry and in total, we probably have thousands of processes that could benefit from and be improved by automation. Coming into the company and seeing how things were done just made it obvious that automation was missing but necessary. Government processes need to be automated to be more efficient because of the volume and the potential for human error.

How was the initial setup?

I would describe our initial setup as complicated because of our industry. We never worked with software like this prior to implementing UiPath. Just to get permissions to use the product on our network was one obstacle. It wasn't always easy to get to ATO (Authority to Operate) and get the capabilities and rights to do certain things on the network like to have the product interact with certain programs that have sensitive information. It's kind of complicated, but that is a whole new path within our industry whenever introducing new technology.

From the time of purchase of the UiPath license until adding our first robot in production was a few months. We purchased a license in February and got a robot into production in May. Most of that time spent was because working on the project is not even my full-time job. I have a whole different responsibility in the organization. So, I was doing a lot of developing in my free time. It probably would have only taken a month or so if I was doing it full time.

What about the implementation team?

We did not use an integrator, reseller or consultant. I did everything in-house.

What was our ROI?

We have seen a return on investment and performance benefits. The ability to notice a difference was almost immediate for certain things and in certain programs. I know that I've calculated that we saved $1.47 million through the automation we have already set in place. The solution also helped eliminate human errors which are more difficult to approximate as a dollar value or percentage.

Basically, using the product has allowed us to take between four to six full-time employees from doing very mundane transactional processes to doing more value-added work. That shift alone reduces human error because the human mind is not made to do this kind of transactional work over hours and days at a time.

This solution saves our organization time on an ongoing basis. I would say it saves a minute to three minutes per transaction per thousands of transactions. It certainly has value in more than one way.

What's my experience with pricing, setup cost, and licensing?

We license the use of the product on a yearly basis. The licensing we bought costs $7000 in 2019 for what we have in production. That is the cost of the license plus Studio.

From a cost perspective, I believe that unattended robots can save even more time and more money than attended robots. The only reason we haven't gotten unattended processes into production yet is simply that we haven't got the authority to operate Orchestrator on our network server. The cost is not an issue given our budget, we need to be able to justify how secure it is.

Which other solutions did I evaluate?

The vendors who were on our shortlist were UiPath, Automation Anywhere and Blue Prism. All of them seemed to be good solutions.

What other advice do I have?

We are currently running some of our automation in a virtual environment. The implementation performance is all right. Our system environments are pretty out of date and a bit technologically behind. Sometimes that fact will hold things up. I am the only one in the organization involved in the automation program. I'm the only developer and the only person who uses UiPath directly, but it affects thousands or even tens of thousands of people.

On a scale from one to five, one being the most difficult and five being the easiest, I would rate the ease of use of the platform as a five. Personally, I had no developer experience. I never heard of RPAs or UiPath a year ago. I was able to learn it and figure it out using the Academy, YouTube and the forum. Coming to it cold and doing it part-time, that really doesn't seem like a long time.

On a scale from one to ten, where one is the worst and ten is the best, I would rate this product as a ten overall. It has been completely helpful in achieving the goals we set for it and the technical help and customer service I've gotten have been good. Most of the issues we have encountered with the product are because of the way we operate and not because of UiPath. The support from UiPath provided everything we have ever asked for and needed.

The advice I would give to a colleague at another company who is researching this or a similar automation solution is to just do it. It really creates the opportunity to make things more efficient.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
MP
Senior RPA and AI at Bertelsmann
Real User
Savings in time and money helps us compete with services offered by lower-cost countries

Pros and Cons

  • "The most valuable feature of unattended robots is that they are always available."
  • "We would like to see improvements in Studio such as syntax highlighting and documentation functionality for audit purposes."

What is our primary use case?

We are using Orchestrator, attended robots, and unattended robots.

Our primary use case for this solution is in the financial industry.

We do not yet run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. The whole interface needs some TLC because it can be a bit tricky.

We have used the UiPath training and it has improved a lot since we first tried it. When I used it a while ago, it had its problems. I think it came due to the fact that it was not developed by native English speakers. For example, they had questions that were simply wrong. It has improved a lot and now it is beneficial. I think that the biggest challenge is for them to stay up to date.

From the point that we purchased our UiPath license until we had our first robot was approximately four and a half months.

How has it helped my organization?

This solution has saved us time, but more importantly, it has saved us money by not paying certain fees or certain penalties. With respect to saving money, the last amount that I saw was six figures. Legally, I am not allowed to say more.

Being in the finance business and having certain audits, this solution helps to make sure that we have validations and checks in place to help us to do our processing quicker. Also, with invoices, normally when you pay them by a certain date you get a certain discount. So, we've managed to significantly increase the savings we get just from having invoices processed earlier or on time.

In terms of eliminating human errors, we have one process where we've eliminated errors completely. The average is that we eliminate errors by fifty to sixty percent.

What is most valuable?

The most valuable feature in Orchestrator is the scalability.

The most valuable feature of unattended robots is that they are always available.

What needs improvement?

They have added a lot of new features over the past months, and things are a little more complicated. In the interface, sometimes you just have the screen full of windows and figuring out what goes where can be a bit tricky.

We would like to see improvements in Studio such as syntax highlighting and documentation functionality for audit purposes. That would be great.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four. There are a couple of things that break the robots, and it has to do with the technology itself. The user interface and other components are prone to error, and it's not one hundred percent automation. This is something that you take into consideration when you do RPA. They have also had a couple of updates over the past years where they made significant changes that basically broke the robots.

What do I think about the scalability of the solution?

We have more than a hundred people involved with RPA.

How are customer service and technical support?

So far, I have only used the ticketing through email support, and it is sometimes frustrating. I've only just learned that there is telephone support. It is hard for me to rate customer service because I was looking for telephone support, thinking that it was not available.

In general, there is room for improvement support-wise.

Which solution did I use previously and why did I switch?

We are in an industry that is heavily targetted by low-cost countries, so in order for us to stay competitive, we had to do something. When we did our research, the two obvious solutions were RPA and AI.

When we started, it was with Blue Prism, and we learned from the issues we had. When we were looking at what we could do as an AI, UiPath started to emerge and started to become a big player. We then looked at capabilities and the licensing model, and at the time there were two vendors that had pretty similar capabilities.

These two were Automation Anywhere and UiPath. Automation Anywhere had a very high initial investment requirement and UiPath didn't, which is why we stayed with UiPath. I believe that you had to buy at least a hundred licenses for Automation Anywhere, whereas with UiPath you can buy one or two.

It looks like we made the right choice.

How was the initial setup?

The initial setup of UiPath was straightforward. The approvals on our side slowed things down. If it were not for that then we could have been up and running in six weeks.

What about the implementation team?

We implemented the solution ourselves.

What was our ROI?

We only automate processes where we expect to see ROI within twelve months. As such, most of our processes have an ROI between six and twelve months.

Which other solutions did I evaluate?

We evaluated Blue Prism and Automation Anywhere before choosing this solution.

What other advice do I have?

We are in the process of moving this solution to the cloud.

From a cost perspective, it is very hard to get ROI with an attended robot. The price is too high.

My advice to anybody who is researching this solution is not to overthink it. RPA is a technology that you learn by doing it.

This is a very strong product. I think that there is a lot of good investment and a lot of good attention out there. This is the best or one of the two best tools out there. They are listening to what the market wants and just need to be careful not to get greedy. That said, there is always a little bit of space for improvement.

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Patrick Graf Von Hardenberg
Senior IT Project Manager at Otto group
Real User
Orchestrator is easy to understand, and Unattended robots save our organization time

Pros and Cons

  • "This solution saves us time in all areas."
  • "In future releases, we would like to see more drag-and-drop, and more out of the box AI."

What is our primary use case?

We are using Studio, Orchestrator, and mostly the unattended bots.

Our primary use for this solution is to give time back to the employees.

We do not run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. It's drag-and-drop, and all of the activities are there.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. All of this information there is self-explanatory and it works. 

From the point where we started using the demo version, it was a couple of months until our first robot was ready.

How has it helped my organization?

This solution has probably helped to eliminate human errors.

I can definitely say that this solution has saved the organization time. With all of the processes together, we have saved one full-time equivalent person. 

What is most valuable?

The most valuable feature of this solution is the unattended automation.

This solution is easy to use and it saves you time.

What needs improvement?

In future releases, we would like to see more drag-and-drop, and more out of the box AI.

For how long have I used the solution?

We have been using this solution for about two years.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four. We had some issues where we needed to get in contact with the support, and sometimes, UiPath crashes on our servers.

What do I think about the scalability of the solution?

We have about eight people in our automation group.

How are customer service and technical support?

Most of the time, the technical support for this solution is very good.

One one occasion, it was not very good. We had a problem with a new version. When we updated to 18.2, the robots stopped working after some time. We had a lot of emails that included session logs. I made it quite clear that it was really important because we were in the beginning phase and the robots had to run. In the end, I fixed the problem by downloading the next version, 18.3. When we asked whether the problem was version-specific, they never got back to us, which isn't very good.

Which solution did I use previously and why did I switch?

We did not use another RPA solution before this one.

From the external consultants, we got the idea that RPA has the possibility to save us time and money, so we decided to do it.

How was the initial setup?

The initial setup of this solution is straightforward. Orchestrator is easy to understand. You can connect the virtual machines to it and then run the robots.

What about the implementation team?

In the beginning, we used a consultant from Roboyou to assist us with the process. Our experience with them was good.

What was our ROI?

We recognize ROI in terms of performance benefits as soon as a process is automated and an employee can do something else that is more meaningful. It is not a benefit listed on a spreadsheet, but the employees are happier.

What's my experience with pricing, setup cost, and licensing?

Our licensing fees for this solution are €68,000 (approximately $75,000 USD) yearly.

Which other solutions did I evaluate?

Two years ago, we evaluated Automation Anywhere and Blue Prism, in addition to UiPath. UiPath was the best overall solution then, and it still is now. It has a big community, and you can download the demo versions to start testing immediately.

What other advice do I have?

This solution saves us time in all areas. We don't keep track of exactly what we have saved in terms of time, but we can say that we have more customer experience. If somebody has a mundane task and wants it automated then we do it.

My solution for anybody researching RPA solutions is to try UiPath. When you want to start, it is easy to register and get going.

This is a good solution and it saves us time, but there is always a path for improvement.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
NR
Solution Architect at a engineering company with 10,001+ employees
Real User
Studio is very easy to learn, and Orchestrator makes it easy to manage the platform

Pros and Cons

  • "It is really easy for people to learn the basics and the learning curve is not steep."
  • "Orchestrator needs to have better integration to include business users."

What is our primary use case?

We use all of the products in the UiPath platform.

We have use cases ranging from back-office to manufacturing, which include large project management, accounts payable, accounts receivable, and treasury management. Most of the areas in the company have processes that we have automated.

We run our automations in the Citrix virtual environment, although we are unhappy with Citrix. It is pretty bad, and it's very difficult to keep up the performance. AVS or Azure do not offer a good service yet, but we are looking for alternatives with respect to the virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. We have been using UiPath for quite a long time, and we have seen this evolving. It has been getting better over the last few years.

On a scale of one to five, judging how beneficial it is, I would rate the training between three and four. The training is good, but the content doesn't have the depth required for people to go ahead and do something if they're not technical. It's still pretty high-level.

From the point that we purchased our UiPath license until we had our first robot was three to four weeks. The process is getting better, but when we started in 2016 and UiPath was small, it was good but needed refinement. I would have rated it three out of five back then.

How has it helped my organization?

Using this solution is enabling us to move the drive for digital transformation to the core. We can now take automation to a level it has never been to.

In terms of eliminating human errors, we have seen benefits. With humans performing, the accuracy was at approximately ninety percent. Our accuracy with automation is now close to one hundred percent.

With respect to saving time, we have seen FTE savings but the numbers are confidential.

What is most valuable?

The most valuable feature of Studio is the ease of use. It is really easy for people to learn the basics and the learning curve is not steep.

Orchestrator makes it very easy to manage the platform.

What needs improvement?

Orchestrator needs to have better integration to include business users.

For how long have I used the solution?

We have been using this solution since 2016.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution between four and five. Stability has been getting better. For example, Studio used to have a lot of bugs when you were developing and when you were capturing the screens. Now it's been getting better, but there is still room to improve.

Orchestrator used to lag quite a bit when there were a high number of transactions, and there is still room to improve.

What do I think about the scalability of the solution?

We have at least a few hundred people involved in our automation program.

How are customer service and technical support?

The technical support for this solution is pretty good. Whenever we had trouble they were always there.

Which solution did I use previously and why did I switch?

We did not use another RPA prior to this one. We were looking at improving the efficiency of processes and bringing some innovative solutions to automating tasks and processes. This is when we decided to try RPA. 

What about the implementation team?

We implemented this solution on our own.

What was our ROI?

We have seen ROI but I cannot share the specifics.

Which other solutions did I evaluate?

We did a very extensive vendor review. We had all of the major providers of RPA solutions in 2016, and UiPath was the one that came through in terms of fulfilling all of the criteria.

What other advice do I have?

Looking ahead at the features that are being released this year, they seem to be what we have been looking for.

My advice for anybody researching this type of solution is to choose wisely. There are a lot of products out there, but few of them actually work.

This is a good solution and they are releasing some features that I am looking forward to, but there is still room to improve. 

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Thomas Mathews
President at Onq technologies
Real User
Saves time and eliminates errors, but industry-specific training and information would be helpful

Pros and Cons

  • "The most valuable feature of this solution is the ease of deployment."
  • "More industry-specific training and information would be highly valuable to us."

What is our primary use case?

We use the entire UiPath suite for healthcare revenue cycle management.

Our automations are not run in a virtual 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.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. The information about the automation processes was really useful. At the same time, I would suggest including more industry-specific training and knowledge sharing.

From the point that we purchased our UiPath license until we had our first robot was approximately one month. I felt that the process was straightforward. It was very intuitive. Most of the resources were available to us and we've got it up and running with no problem.

How has it helped my organization?

We have clients for which we provide people to perform various processes. Parts of those processes are exceptions that could not be done by these people but were very time-consuming. We have automated those exceptions so that now, we don't have a percentage of our staff evaluating those exceptions every day. They now run flawlessly one hundred percent of the time. Our clients are happier and we're happier.

In terms of eliminating human errors, UiPath is excellent at that. We have one hundred percent accuracy on all of our automation.

This solution saves us time and it saves our clients time. I would estimate the savings at ten percent where automation is deployed. Some of the automations run slowly but they run around the clock.

What is most valuable?

The most valuable feature of this solution is the ease of deployment.

What needs improvement?

More industry-specific training and information would be highly valuable to us. We're a healthcare company, and it would be helpful to know where and how automation is being deployed within a healthcare environment. For example, what have we done that we could share with people, and what are they doing that they could share with us?

What do I think about the stability of the solution?

The UiPath platform is stable, but it is dependent on other platforms.

For example, we may be extracting data from or populating data in a customer billing system. That billing system might go down and someone needs to wake up the bots after that happens. It is not the fault of UiPath but it is part of the process.

What do I think about the scalability of the solution?

This solution is easy to scale.

We have approximately thirty people involved in our automation program.

Which solution did I use previously and why did I switch?

We were not using an RPA solution before UiPath contacted us.

What about the implementation team?

We handled the implementation in-house.

What was our ROI?

We are very close to seeing ROI, although not quite yet.

Which other solutions did I evaluate?

We looked at some different technologies that were out there and it seemed that UiPath was ready. These included Blue Prism, Automation Anywhere, and one other one. We felt like UiPath was a solid solution that was pretty easy to use and could scale easily and quickly as well.

What other advice do I have?

This is a fantastic solution and we love it, but we definitely see some room for improvement, mainly around interoperability and leveraging intelligent or cognitive RPA and educating their client base around that stuff.

My advice to anybody researching this type of solution is to familiarize yourself with the concepts and all of the market participants, and then choose the one that works best for you.

I would rate this solution a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Jeff Martin
AVP Customer Experience at Encova Ins
Real User
Super simple solution that has made our organization more efficient

Pros and Cons

  • "With the robotics and management of Orchestrator, we are able to kick things off. We are starting to get more out of the scheduling of these and into more on demand triggered events, such as a RESTful service calls and things of that nature."
  • "While the UiPath Academy is simple and you get a decent understanding of what's there, you still have to dedicate on an awful lot of time doing the automations to become proficient at them."

What is our primary use case?

The primary use case is around manual conversion of data from one system to another. These are big processes right now.

We are using Studio, Orchestrator and the robots.

How has it helped my organization?

Our organization is more efficient. The people that you're automating processes from are happy they are getting done. They are excited and like to be a part of the process. It's also new technology. It's innovative. and people enjoy being around that.

We don't have a baseline metric for the elimination of human errors. So, we don't know how many errors a human actually makes doing some of the conversion data entry processes. We assume they are about 90 percent accurate and UiPath is 100 percent accurate.

We have saved 18,000 hours so far this year.

What is most valuable?

With the robotics and management of Orchestrator, we are able to kick things off. We are starting to get more out of the scheduling of these and into more on demand triggered events, such as a RESTful service calls and things of that nature.

The ease of using the platform for automating your company's processes is a five out of five. It is super simple. Everyone who we have in our robotics team had no experience with automation or robotics previously. They went online took the classes from UiPath. They started with the Community Edition, just to play with it themselves, then they were probably experts within a couple of months.

What needs improvement?

Everyone has used the UiPath Academy training. I would rate it around a three or four out of five. While it's simple and you get a decent understanding of what's there, you still have to dedicate on an awful lot of time doing the automations to become proficient at them.

While it looks like it is being addressed, getting the unattended robots to every person's machine in the company and executing on their machines needs improvement.

What do I think about the stability of the solution?

I would rate the stability as a five out of five. it hasn't gone down yet.

What do I think about the scalability of the solution?

We have a team of four people involved in our automation program.

How are customer service and technical support?

I have only used the technical support to fix a licensing discrepancy. They were okay.

Which solution did I use previously and why did I switch?

Everybody said, "We had to do more with less," from the C-suite on down. RPA is the only way that you can do that which seemed viable. So, we tried it out.

We were previously using VM. 

How was the initial setup?

The initial setup is straightforward. With our proof of concept, it took us two to three weeks to develop it, then another week to make it production ready. When we deployed it into production, we had the license. We installed the robot and had it running through Windows Scheduler before we had Orchestrator, and it just worked

We started with a proof of concept, had it running in production, and bought the license that day.

What about the implementation team?

We did have a systems integrator who helped us. Overall, for the initial implementation, I would rate them a five out of five. They came in, and it was great.

What was our ROI?

We have been able to achieve our ROIs on pretty much every process that we have done. You see it almost initially, as soon as the process starts running. However, until we get the actual feedback of, "Yes, I can tell this is saving us time and effort." It takes about a month for the business unit to really recognize it.

We haven't technically saved money because we haven't gotten rid of anybody, so our CFO will not let us claim money. However, we do calculate time given back. Right now, I believe for this year, we've been given back 18,000 hours so far.

What's my experience with pricing, setup cost, and licensing?

Our licensing costs are around $40,000 a year.

Which other solutions did I evaluate?

We looked at the big three: Automation Anywhere, Blue Prism, and UiPath. Then, we chose UiPath because of cost and ease of use. The training was there. It was so quick and easy to pick up.

What other advice do I have?

I would recommend UiPath. It's easy to use and learn. It just works and doesn't break. It's cost-effective.

We run our automations in virtual environments, such as Citrix. Orchestrator sits in VMware along with unattended robots. It kicks everything off behind the scenes. Most processes are set on a time schedule.

We prefer unattended bots. We're moving into that real-time trigger, but still like to run unattended to give some form of user interface for the user to call them.

I would definitely rate it a 10 out of 10 because of what it delivers and allows, along with the benefits. You can also see on their strategy on the roadmap, it's just expanding and getting better.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
DM
Consultant at a consultancy with 201-500 employees
Consultant
Saves people time to be able to look at high-value tasks

Pros and Cons

  • "Studio is the most valuable feature from the aspect of developing a bot. It is very nice from the drag and drop perspective. It is very easy to follow and has low guidance from the technical aspect."
  • "I would like to have cloud in the next release. It's one of those things that allows customers to be able to have an easier access point."

What is our primary use case?

Our most prevalent use case is invoice processing.

We are using Studio, Orchestrator, attended bots, and unattended bots.

How has it helped my organization?

It comes down to saving people time to be able to look at high-value tasks.

The solution has helped us eliminate human error with 100 percent testing and accuracy. This is only where there are exceptions, which generally tends to be under five percent of the time.

The solution has saved us time. It does depends on the specific process. For one specifically, it took a week out of each month, then we were able to process the same reconciliation process within minutes.

What is most valuable?

Studio is the most valuable feature from the aspect of developing a bot. It is very nice from the drag and drop perspective. It is very easy to follow and has low guidance from the technical aspect.

What needs improvement?

I would like to have cloud in the next release. It's one of those things that allows customers to be able to have an easier access point.

There are still areas for improvement for some of the drag and drop features and moving more to a bit of a lower code perspective.

What do I think about the stability of the solution?

I would rate stability as a five out of five. Compared to competitors where we've had instances where either exceptions are kicked out or the workflow breaks, UiPath does not encounter those issues.

What do I think about the scalability of the solution?

About 50 people in our organization are involved in our automation program.

How are customer service and technical support?

The technical support is very good. They are very good partners.

The experience overall has been really great with UiPath. The culture and individuals at the company really help make the project easy to do.

Which solution did I use previously and why did I switch?

We had a very manual process that needed to be addressed because it was taking up way too much time of employees' efforts.

How was the initial setup?

The initial setup was straightforward. Going through the certification process, it enables you with the tools to be able to implement at an easy level for low-hanging use cases.

It took about a month from the time we purchase our UiPath license until our first bot was live.

What about the implementation team?

We used a consultant for the deployment. I would rate our experience with them as a five out of five. 

I would rate ease of use as a four out of five. We had a bunch of people that do implementations from a development aspect for our use cases. The solution has been very easy to be able to implement for our specific use cases, given the capabilities of the platform.

What was our ROI?

We have seen ROI from this solution. We saw it almost immediately in regard to performance benefits around accuracy, timeliness, and the ability to do 100 percent testing.

Which other solutions did I evaluate?

We also evaluated Blue Prism and Automation Anywhere. We chose UiPath because of stability of the platform, ease of use, and the deployment factors are much easier with UiPath.

We have used UiPath Academy for RPA training. I would rate it as a five out of five. Compared to competitors, the UiPath Academy offers a very easy path to certification. The way that the curriculum is laid out, it is very nice and easy to follow.

What other advice do I have?

Do your due diligence.

We have probably use attended bots more heavily. They're very nice and everybody has a good experience with them working alongside actual humans.

I would rate the overall product an eight out of ten. There are additional features that probably could be rolled out. I think there are on the roadmap.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Daniel Hartzler
Digital Workforce Analyst at a energy/utilities company with 10,001+ employees
Real User
Gives you a technology or ability to build a solution on any legacy system

Pros and Cons

  • "It gives you a technology or ability to build a solution on any legacy system."
  • "VM was on the service for high density. It is finicky at times. The latest release is a lot more stable. However, I've had a two week production outage where DLLs weren't registered and someone from Vegas had to login for eight hours onto the fraud service to work it out. Even though they uninstalled and re-installed it, all the different apps still wasn't working. So, I have lost a bit of faith in it to be honest."

What is our primary use case?

Our primary use case is IP invoice automation.

We are currently using Orchestrator and bots.

How has it helped my organization?

It gives you a technology or ability to build a solution on any legacy system.

What is most valuable?

I love Orchestrator: 

  • The configuration part
  • The amount of keys
  • Transaction reporting
  • Logs
  • Accessibility on the iPhone.

What needs improvement?

VM was on the service for high density. It is finicky at times. The latest release is a lot more stable. However, I've had a two week production outage where DLLs weren't registered and someone from Vegas had to login for eight hours onto the fraud service to work it out. Even though they uninstalled and re-installed it, all the different apps still wasn't working. So, I  have lost a bit of faith in it to be honest.

I would like to have cloud stuff back in Australia and hosted there. I want everything in SaaS, bots included.

While it has eliminated human errors, it has created other errors.

I would like something that better identifies the processes. If it could watch the computer, then work it out for me, that would be good.

For how long have I used the solution?

I have been using it since 2016.

What do I think about the stability of the solution?

Now that I've done an upgrade, it seems to be a lot better. Because I was running high density on the 2016.2 or 2016.3. I had a lot of problems, but I couldn't work out whether or not it was just UiPath or our client app that was timing out. But, we noticed that if you login as console, you have far less issues than if you run high density.

These days, the stability is a four out of five. Back in the day, it wasn't.

What do I think about the scalability of the solution?

In my old organization, 50 to 100 people were involved.

I have a bit of a different issue because at my old company that I just left, I was only paying $3,600 USD per bot. I turned up at my new company, and because of our size, we are paying $8,000 per bot.  

How are customer service and technical support?

The support is not good. I had a two week production outage.

Which solution did I use previously and why did I switch?

There was a business problem, and we needed to work at how to solve it. The partner was a big driver in this process.

How was the initial setup?

The initial setup was pretty straightforward.

It took two weeks from the time we purchased our UiPath license until we had our first robot in production.

What about the implementation team?

We used Blackbook.ai, and our experience with them was awesome.

What was our ROI?

We have seen ROI. The last company that I work for was trying to get 1000 FTEs out the door, and I think that they are already at 60. In Australia, at my current company, we are already at 10 FTEs. Just in Australia, we have save a million dollars, and maybe five million in India.

The reduction of 10 FTEs has saved us time.

What's my experience with pricing, setup cost, and licensing?

At the last place that I worked, it was $700,000 USD.

Which other solutions did I evaluate?

Everything that I read about Blue Prism suggest that it is too heavy and takes too much development to ramp up.

I looked at Automation Anywhere for the price point, especially for a PoC. Between Blackbook.ai and what I saw already with UiPath, I just thought UiPath was the better option.

What other advice do I have?

Scout it out. I am going to try to work with this company a different way than what I did than last time, e.g., federated.

I would rate the overall product as a nine out of 10. It's an enabler. It seems pretty good. There is a lot of investment and new things.

I would rate the ease of use of the platform as a four out of five. It is pretty easy to use but it is not doing everything for me. I still have to do stuff.

I would rate the UiPath Academy as a four out of five.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
WC
Solution Architect Support Manager at a financial services firm with 5,001-10,000 employees
Real User
Orchestrator enables us to monitor the bots, "orchestrate" them, and we can deliver that tool to customers so they can manage their bots

Pros and Cons

  • "The best thing about UiPath is that it is fairly easy to understand and learn how to use it."
  • "There are a lot of things that can be done to the product to make it better but they are minor and the product continues to improve with every release."

What is our primary use case?

We have a bunch of uses for the product so it is hard to judge which is the most important. We started working with data structures for websites and then moved into more complex automation like speech detection and making more cognitive decisions based on rules. Our automation using bots is essentially on the verge of using artificial intelligence.

How has it helped my organization?

There are a lot of ways this product has improved our organization. Even a simple project can bring us a lot of recognition. One example is retrieving passwords on Amazon. Imagine that you have a user who forgets their password. Amazon lets you reset your password but there are a lot of steps. In the background, Amazon is validating that you are the person that you are saying that you are with a lot of manual steps. We automated that with a bot and other tools and the customer experience skyrocketed. We reduced the processing by five minutes just for that service. Not only did we apply that solution for one country, but we also applied it to seven different countries. It was a success story.

What is most valuable?

What I think is the best thing about UiPath is that it is fairly easy to understand and learn how to use it. One of the most valuable things about the product is the improvement they are making with the tools. They are offering around thirteen new products now. With these additions, there is a lot of value-added enhancement that we can provide via the automation to augment what we already have implemented.

The studio's Orchestrator is the tool that we use in order to create the scripts for the bot. It is what enables us to deliver automation. Having these new technologies within the studio is what enables us to be more creative. With the Orchestrator we can monitor the bots, we can "orchestrate" them, and we can deliver that tool to customers so that they can manage their bots. It is really like digital workforce management. If we created a bot for a business, usually it would just do its job and the customer would not see what the bots are really doing. With this tool, the client has that opportunity to see what the bots are doing. 

The bots automate the work that otherwise would have to be done with other interventions and resources, so reallocation of resources and focus is the most valuable thing overall.

What needs improvement?

There are a lot of things that can be done to the product to make it better. The feature list that I develop between releases is often covered new releases of the product. That is good. But there are still a lot of enhancements that I would like to have within the Orchestrator and the queues. For example, how we manage the queues is an important thing.

I would like to see the ability to have other ways to look for one transaction within the queue. If I am looking for a single transaction, it would be good to have a filter that you can use to specify a detail, like just looking for a reference name that starts with a particular letter — but not the entire reference, but wildcards. Those are the kind of things that can be enhanced and make a big difference. Maybe they are not on the roadmap for the company when it comes to upgrades at this point because those are tiny things within the tools. But even those tiny little things can make a lot of difference in the functionality of the tools.

What do I think about the stability of the solution?

On a scale of one to five where five is the best and one is the worst, I would rate the stability of this platform a five. The stability of the platform is very good. During the four years that we have been working with UiPath, we have not encountered any issues with stability because of the platform. There are always issues with the environment and that can affect stability and performance, but with the platform itself, there are no issues.

What do I think about the scalability of the solution?

Within the RPA suite, we have around 40 people working with the product. But we also have to consider that we usually engage people from other places to contribute to every single project. There are a lot more users than are working with us within the project and within our immediate company team. The peripheral people are going to be people from security, people from IT, people with specific business backgrounds, etcetera. The number of users and the product itself are scalable.

How are customer service and technical support?

The technical support is actually pretty good. We worked a lot with our CSM (Customer Service Management). They are always doing a great job to find someone to help us out when we have issues. They get the right person for the right issue. For now, if I had to rate it from one to five where five is the best, it is going to be a five.

Which solution did I use previously and why did I switch?

At the beginning, we would try to automate tasks using spreadsheets where we had calculations. We had macros and things of that sort to automate small tasks. The next step in moving to a new era was to turn to RPAs. There were a lot of things that we needed to implement through this new technology. So we did have another solution before for some types of automation but it wasn't really a dedicated system for automation and it wasn't capable of this scale.

How was the initial setup?

We have a turn-around time of four to six weeks. In order to go to implementation and production, it depends on the complexity of the project. A normal project that is not that complex will obviously take less time. We have to take into consideration the time that we have in assessment, in the evaluation of the project, and in development, and only after that do we do testing to put it into production.

There are, of course, always challenges, but not all of them come because of the UiPath platform. There's a lot of things that are an issue because of the environment or the target applications that we're using. It is often more because of that than the platform itself.

What about the implementation team?

We have in-house developers, we have a QA team, and we have a training and communication team specifically for the RPA suite. We also have managers for the teams, the support team, and solution architects. We do our own implementations and assist others in doing theirs.

What was our ROI?

We usually try to calculate return on investment within a year or two depending on the project. But we start to look at the benefits from the first month we put the product into production. Not really the ROI exactly, but the benefits. What I mean by benefit is if the automation is achieving the goals it was intended to achieve. Once we pass through the cost of implementation, license cost and any additional expenditure of resources, then we look into ROI.

We have seen a lot of benefits in a variety of ways depending on the projects. Most of what we have been seeing is capacity creation. There are a lot of things that can be introduced to automate processes. If there is work that can't be handled by a team and they are not going to meet SLA (Service Level Agreement), creating bots and putting bots into their team to take over redundant tasks is letting the team use resources differently. It creates additional capacity so the team can focus on more important things — like quality or process. That enables the business unit to accomplish their tasks while raising quality. The bot can always be depended on to do a specific task in the same way. If we have the right steps and if we have the right process to execute, the output from the bot is going to be right. That is another incredible benefit. Of course and for example, giving the customer a response in one hour instead of five hours enhances the customer experience. Proper use of automation can do all of these things.

Bots can also be used in eliminating human errors. Being cautious in estimating that, it could be as much as a 60% to 80% reduction. It will be reducing human error, but there is always some level of error in processing.

The percentage of time saved using UiPath bots depends on the projects, but most processes can save teams 85% of the time they would spend on tasks that can be automated. Some other automated tasks we have the efficiency go up to 90 or 95%. That is pretty good and a great way to allow for the reallocation of resources.

What's my experience with pricing, setup cost, and licensing?

The cost depends on how many licenses we have and how we use the bots. We have a rate for attended bots and a rate for unattended bots. The price itself depends on the project and the number of licenses required. The prices, in general, are good — actually they are the best — but they could always be cheaper. Right now there is no one that is cheaper. The cost is in line with what we thought that it should be.

Which other solutions did I evaluate?

In 2016, we started to evaluate vendors. We went through Automation Anywhere and a lot of the competing products. We decided to go with UiPath not only because of the cost and the model that they have, but also the relationship that they have with customers. They actually care for you. They are always looking to provide you with the newest and best technologies. They try to make you use it in the best ways and they try to make you test out new features and provide feedback. If you need it and you realize that it's really good, then they help you make it happen. That is the best thing. They are being humble even though they are growing a lot. It is what actually made us go through UiPath.

What other advice do I have?

We are using the entire UiPath tool. We are using the studios, we are using the orchestrator, we are using the bots. That is both unattended and attended bots.

We have two different environments. One is on-prem within Costa Rica data center and then we have another in the U.S. that is on an internal cloud and we use VDI (Virtual Desktop Infrastructure) and Citrix.

The virtual environment is actually pretty functional. There are some pros and cons. The pro is that it enables you to add virtual machines if you need them. The con might be that sometimes you need to enable connections that are not enabled. You might have to go through firewalls, go through network issues, etcetera. With that, it is a little bit more complex to build out automation sometimes. You have to go through configuration hurdles when you encounter them.

On a scale of one to five with five being very easy and one being very hard, I would rate the ease of use of the platform as a five. It is a five because when comparing it with the other RPA (Robotic Process Automation) platforms, it is easier to navigate within the studio and it is more comprehensive. There is a saying in usability that if you need to take more than five clicks in order to find what you're looking for, it is not easy. Finding what you want in one or two clicks is what makes a product easy to use.

We use UiPath Academy RPA training all the time. Every new employee or intern that we employ in our company goes through the RPA academy training first. That is kind of the bible for us. On a scale of one to five, five being very beneficial and one being not beneficial at all, I would rate the academy as a five. 

My advice for anyone considering this solution is very simple: It is worth it, go ahead and give it a try. You will like it. Try to experience everything within UiPath and go through every single feature that they have and can provide currently before you commit to it. The company's support will back you up and they will make sure that you find what you are looking for.

On a scale of one to ten, where ten is the best and one is the worst, I would rate the product as an eight. To get a ten, a product should be perfect. Nothing is perfect. It is not a nine because it is just a cautious rating. In technology, we always say that for every question there is an answer that says "depending on...[something]". Depending on what you're looking at, it is going to be an eight or it's going to be a nine. It should never be a ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Terry Yoo
Sr Finance BI Manager at Vulcan
Real User
Good pre-sales support, and the savings in time allows our users to work on more value-added activities

Pros and Cons

  • "The most valuable feature is automating processes and tasks, giving users time for more value-added activities."
  • "I would like a better ability to connect and integrate with other software systems."

What is our primary use case?

We're starting within our finance group, so a lot of different processes in our finance group are being automated. Our main project was for our tax department, extracting data from PDFs and putting them into Excel.

We have two people involved with RPA in our company.

We just purchased this solution last week so we're still installing everything. We did automate four processes with the community edition. The length of time in development varied by the process. The longer ones required help from UiPath. They came on-site for the PoC, so that helped us out. Some other easy ones we just did ourselves within a couple of days.

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 is a four. But with Studio X, I think it will probably be a five. I say four because as you get more complicated with your processes, you need to learn how to code and there's a brunt learning curve. A lot of people will get turned off by that. So, I made some good sessions with Studio X, it's all drag and drop, mostly, so that's perfect for the business users.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. We are actually in the process of taking it right now. It's good that they have something like that available. There are not that many who have aced it.

How has it helped my organization?

So far we haven't gone too far, but I expect that people will be a lot happier because they won't be doing the jobs that they don't like doing. They'll have more time to learn and up-skill technologies like this, which can help further their careers rather than just learning, or not learning by copying and pasting.

What is most valuable?

The most valuable feature is automating processes and tasks, giving users time for more value-added activities. This results in cost savings.

The free community edition allowed us to test out the technology before investing in it.

What needs improvement?

I would like a better ability to connect and integrate with other software systems. An example would be integration with data and business intelligence tools. I don't think they have a native connector yet. So, just something that a user can connect, and have RPA in the middle, would be helpful.

I would also like to see an easier UI for the user. It may have already been taken care of with Studio X, but I think if they keep improving that, it's going to get a lot of people interested because users are attracted to it.

For how long have I used the solution?

We were just using community edition for about six months.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a five. I mean we haven't used it too much so we haven't really pushed the boundaries, but for the stuff we've, done I would say it is stable.

How are customer service and technical support?

Their sales and pre-sales support is very good. They've been very willing to come onsite and help us out and help with our pilot as well.

Which solution did I use previously and why did I switch?

We got introduced by RPA from PWC. They came and talked at one of our finance summits.

How was the initial setup?

The paid version, I'm still learning how to use, how to connect everything together. There is still a little learning period for that as well. Learning how Orchestrator works, how the licensing works and things like that, were necessary after using the community edition.

What about the implementation team?

UiPath helped us with our PoC and they were great. I mean they came for free and through just a pilot or a proof of concept. We could actually see if the technology works for a use case.

What was our ROI?

Before we start anything we evaluate the process and we take down how many hours it saves, the costs, and ROI. In our main project, it took someone approximately three hundred hours a year to do all that data extraction, data input, and that also came along with errors because someone could fat-finger the value.

Then, through the PoC, they're able to turn around within two days. A bot can basically do that entire process and do it error-free as well.

It is a savings of three-hundred hours, and the cost savings is a multiplier of hourly pay.

We also use it as an ETL tool sometimes, so instead of paying for an API connection, we can use RPA. Simply just to run a simple report of the system.

I don't have any other software vendors to compare it to, but I would say if you're fully utilizing it then there's definitely an ROI in it. Obviously, if you have only one process running five minutes a day with the bot, it's not worth it. For us, what we did was we built enough use cases before we bought that enterprise license to make the ROI on it. We've got eight or ten and then we realized that we can cover that license cost easily with ROI before we purchased it.

Ultimately, we realized ROI within six months.

What's my experience with pricing, setup cost, and licensing?

We got purchased the basic minimum package and it was around $35,000 USD, annually.

Which other solutions did I evaluate?

We tested out Kryon RPA, and we looked but did not test Automation Anywhere and Blue Prism. Those two were out of our price range, and at that time, neither of them had a free community edition, so we couldn't test out the technology.

UiPath sort of fit our company well because it was priced reasonably, and they also had a free version so we could test out the technology. Ultimately, we chose UiPath because of the price. It was not as expensive as Blue Prism or Automation Anywhere. It has a free community version where you can test new technology, which was huge. They also have a local office next to us so we can get their help pretty easily.

What other advice do I have?

They have announced features in the next release, and I think that they are all the things that users would want. There are easier ways to document processes and a better and more user-friendly UI. A lot of people just got turned off by having to learn code. So that was a lot easier, and then being able to track all your RPA projects and the ROI on them saves time. Doing them manually is time-consuming. Fortunately, we're a small company because I couldn't imagine if you're trying to implement this for a bigger company.

My advice for anybody who is researching this solution is to, first of all, do their own research on the ratings and independent research. Secondly, I would just say a lot of them now have free community editions, so there's nothing holding you back from testing out the technology and seeing if it works. I think Blue Prism is the only one that doesn't have it now. That's a really high cost and a barrier to seeing if the technology works. Just going and validating the software and doing a simple automation task is important. All of those vendors have free training so you can just go step-by-step and learn something. I think that's the biggest thing someone can do, and then obviously finding enough processes within your company as well.

This is a good solution but there is always room for improvement.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
UK
Robotic and Intelligent Automation Lead at a consultancy with 10,001+ employees
Real User
A user-friendly solution with good training and is easy for people with C# experience

Pros and Cons

  • "The most valuable feature of this solution is that it is user-friendly."
  • "I would like to see more machine learning features and capabilities for more accurate OCR."

What is our primary use case?

I have used UiPath Orchestrator, and we have created both attended and unattended robots for our clients.

We have been using the new AI and OCR technologies with UiPath, and we are currently trying to implement the Citrix log capability that was recently introduced.

We are not running our automations in a virtual environment. When we automate any Citrix-based application, it's all email-based. There is a Citrix receiver and we communicate with that, which helps automate Citrix applications much faster.

Most of the clients I had seen have been running in virtual environments, although I have seen some of our clients running on the desktop. We have also seen hybrid scenarios.

One thing is that virtual environments can be standardized pretty quickly. So, that's an advantage. Normally, the companies, which are leaning towards more cloud now, will be happy with this. So, I think that is one factor. As you move virtual machines to the cloud you can migrate your bots to the cloud faster.

I have worked on various different domains including the public sector, commercial, healthcare, energy, utility, and federal. These are the different customers for which we are implementing solutions. Now, the customers are moving towards AI and natural language processing. They are more into chatbots, how they can use artificial intelligence, making use of data science, and putting more machine learning on board.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it two and a half. I'd say it is about marketing. You can develop anything. There are very small processes that you can develop with having minimal experience. However, when you start implementing complex processes, I would say you need to be a background developer.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. All of my team members have been using UiPath Academy for training and certification. It's not just with the U.S., but outside the U.S. as well.

From the point that a UiPath license is purchased until the first robot is ready totally depends upon what use case we are implementing. There are different methodologies that people use. Some build the bot without exceptions and it can go to production. Like a very simple process can go to production in two to three weeks. A more complex bot will take eight to ten weeks, and depending upon the process, it can go longer. I have seen tasks when a human is performing the job and it takes him around twenty minutes per transaction. But, when the bot comes in, it actually completed that same transaction in five minutes. But, to develop that five minutes of processing, it was understanding system availability and testing. Then you have to do load testing. It takes ten weeks or so.

Our clients decide to implement RPA for several reasons. The first reason, of course, is to have work completed faster. Second, when there is a workload, you can work on it more efficiently and with fewer people. Consider an open enrollment in October, where the open enrollment starts at 10:00 AM and there are a lot of transactions flowing in. Now you have to hire a human and train them. With the bot, we can just scale up instead. Finally, the bots are errorless.

How has it helped my organization?

In terms of eliminating human errors, it is a one hundred percent reduction. When you implement bots, it's error-free, as long as you have implemented it properly. The robot does not get tired, so the error rate is actually zero.

I would say, more important than saving money, it's more about business growth and client satisfaction. Our clients all serve someone, so it's more about customer satisfaction. The employees benefit because sometimes they have to do repetitive jobs, and they get bored with them. So, they can use automation and apply their brains somewhere fruitful.

Overall, automation is always improving customer satisfaction. Response time is improved, errors are reduced, and productivity increases because work is being done around the clock.

What is most valuable?

The most valuable feature of this solution is that it is user-friendly. I was a coding developer, so I know how to write code, and I've also used other RPA tools. This solution is workflow-driven, where you can easily relay what you had written. If someone has to read the code, it is very readable.

Second, I've always been a Microsoft technology guy, and they have provided the facility where we can implement any of the C# code into it. We have .NET code, and that's why I like it. We say it's a tool, but I would say it can also be leveraged as a custom coding tool. We can actually do whatever custom code you want.

What needs improvement?

I would like to see more machine learning features and capabilities for more accurate OCR.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a five. It's stable. The thing is, with the software, we have a few glitches here and there, but what I like is that we have the right support. When we actually reach out to verify, we get a faster response and also a faster solution. The responses are effective and fast.

How are customer service and technical support?

The responses are effective and fast.

Which solution did I use previously and why did I switch?

I have seen some cases where there is backend automation, but it was a series of processes. With this solution, they combine all of it into one. There were few human-interactive automations. Rather, it was batch-job processing of databases, etc.

How was the initial setup?

The complexity of the initial setup depends upon the client.

There is admin access and a whole lot involved. There are safety concerns from client to client with their security policies, and it may take time. I have hardly seen any clients where it's easy to set up, within a week or two. It takes longer because of the client's own security policies. You have to get a lot of clearance because there is a lot of admin access that UiPath needs. If I had to rate the setup, I would give it three out of five.

A dedicated person is required to maintain this solution. The same way humans get sick and need doctors, the bots get sick and you need a maintenance person.

What was our ROI?

I would estimate that our clients see ROI, on average, in one year. It depends on what they are trying to save. If it is FTE then eventually you'll be getting everything. If you are trying to have a faster experience, it totally depends. There is a development cost and a tool cost that have to be considered. It also depends on the complexity of the processes and how long they take to code.

Which other solutions did I evaluate?

We have clients who use almost all of the RPA solutions. The most common ones are Automation Anywhere, Blue Prism, and WorkFusion. We don't recommend. We advise. We can implement regardless of the solution.

The choice is dependent on various factors. What we have seen is that most companies have a technology stack. Some have a Java shop, while others have a Microsoft shop, or others will use a different technology stack again. People tend to choose what best matches their technology.

What other advice do I have?

When we started initially, most of the business users were afraid that the bot was going to take their job. That is not the case. The bot is actually helping them with their substantive, day-to-day work, by handing the repetitive work. So, after seeing the benefits, I've seen a lot of users now leaning towards bots, and they are very happy with RPA.

I am looking forward to the new version where they have implemented libraries. One thing they have done is merged the media packages into one. 

From a cost perspective, there is a difference between attended and unattended bots. I have implemented both, but most of the plans are moving towards unattended. The unattended bots come at a higher cost. For an attended bot, it is being used while the user is at the machine, and is more like an interactive bot. While there is a huge difference in cost, I still prefer unattended bots. I see less benefit in using attended bots and say that I would use unattended eighty percent of the time.

When I'm implementing an unattended bot, I am actually putting it on a machine. I can run as many unattended bots as I need on that one machine. I can do this with attended bots, but the thing is, you need user interactions. Now think in this way, if the user is not there, the attended bot is waiting for that user. Secondly, I see some of the use cases that are really helpful and suitable for attended, but I would rather go with unattended because it's going to show that I don't need a physical machine and it will be more efficient.

My advice to anybody who is considering this solution is to start with the UiPath Academy and do the training. Then, look through some videos, implement a process or two and see how comfortable you are. At this point, you can move forward with it. I would say that it is pretty easy to understand.

This is a good solution, but I'm a hardcore custom developer. I still want that flexibility in my hand to do whatever I can do. With a tool, there are always limitations in terms of policy and rules.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
HM
Process Architect at a insurance company with 201-500 employees
Real User
Has quick performance benefits and takes away redundant tasks

Pros and Cons

  • "As we are mostly using unintended robots right now, the main value we see is the ability for the solution to take away the redundant tasks. That's the key value. But there's tremendous potential in the attended or hybrid model. The value I see there is allowing people to automate partially or at a time. And whether that's something that we've identified clearly now or something that we look at in the future, I think that lives in the attended or hybrid piece. It would be nice to just see what more we could do and what more value we could add to the business there."
  • "As far as stability is concerned, I'm not sure what people who have deployments of hundreds or thousands of bots are seeing in terms of stability. We're small. For a small implementation, we've had a few hiccups and a few concerns where I would say, how can we triage more quickly, or how can we understand what we've caused more quickly?"

What is our primary use case?

We primarily use the solution for insurance processes where we have redundant activity and we have pain points for our customers. It allows the employees to do more insightful work.

What is most valuable?

As we are mostly using unintended robots right now, the main value we see is the ability for the solution to take away the redundant tasks. That's the key value. But there's tremendous potential in the attended or hybrid model. The value I see there is allowing people to automate partially or at a time. Whether that's something that we've identified clearly now or something that we look at in the future, I think that lives in the attended or hybrid piece. It would be nice to just see what more we could do and what more value we could add to the business there.

On a scale of one to five, I would validate the ease of use to maintain our processes almost at five now that the solution has introduced Studio X. Studio X has the potential of empowering people to prototype and then pass along more qualified information. It's a game-changer.

Right now just being able to capture process, even without Studio X, let's say we video it or we capture it by way of a traditional Vizio diagram, enables asking work instructions, etc. It allows us to capture and standardize what people are doing as well as take steps toward optimizing processes in general. It's all good stuff.

I wouldn't know without looking at the actual metrics, but I would say in general our pay projects probably cut time by factors. Simply because people do things more slowly, more inefficiently. They're interrupting where the bot is not. That's the reason why we love it so much. The potentials of cost and time savings and the possibility of really having people get some of their time back is great.

What do I think about the scalability of the solution?

We haven't had any problems that make the solution look unstable. I'd give stability a rating of four out of five.

As far as stability is concerned, I'm not sure what people who have deployments of hundreds or thousands of bots are seeing in terms of stability. We're small. For a small implementation, we've had a few hiccups and a few concerns where I would say, how can we triage more quickly, or how can we understand what we've caused more quickly? How can we implement strategies for redundancy and business continuity management? What guidance is there from the company on that and how can we be very transparent to our customers to be clean, concise and clear about that? 

How are customer service and technical support?

I've talked to a lot of the technical support team. They all know that we're really happy with their responsiveness. We were really happy with the product and we're really happy with them. Just continuing to get the guidance, meeting with them, considering strategies and having them support us has been great. 

Which solution did I use previously and why did I switch?

In this day and age, RPA is the appropriate tool for certain issues where a lot of times I think a lot of firms, not just ours probably go, "Hey, we don't need a longterm solution that will last forever, but we do need something that's going to automate this process and is going to take this pain point away from the business and this appeases that need." I'm not sure if that's specific to any one certain company; that's just the way that people approach it.

I'm not quite sure the exact reason why our company chose to automate. It was decided before I joined the team.

How was the initial setup?

Implementations from process assessment through actually bringing something to production takes about three months. We'd like to be at six weeks like everyone else. But right now, we're at about three months.

It'll be more straightforward in the future now that we have tools like explore apps and insights. 

The complexity of the project informs the complexity of the implementation. We are an IT services company. We have a very standardized kind of approach to testing and bringing things to production, so I don't think that's terribly complex. It's kind of business as usual. We recently brought a project to 10 productions that had three parts to it. We staggered the implementation that typically might be more complex than what other people are doing. The complexity of the project introduces complexity to the implementation, which is fairly straightforward.

What about the implementation team?

We have a partner that assisted with implementation.

What was our ROI?

The performance benefits are usually pretty quick. The process assessment that we do that hopefully determines the processes that we would pick, allows us to see ROI fairly soon. I'm not sure what the timeline is on that exactly.

Which other solutions did I evaluate?

I'm sure our process probably looks like a lot of other companies. We go and look at not only one solution but also its competitors. We look at the top of any certain field and make a decision based on what fits the need the best. 

What other advice do I have?

My understanding is the solution is deployed on-premises.

We also run our deployments in a virtual environment and we have the potential to do hybrid things as we have more processes that are in the pipeline that we must review to see what our roadmap looks like going forward in the future. Our experience with automation within virtual environments so far has been fine.

In terms of the UiPath RPA Training Academy, I've taken a few courses. I've also done Academy live and watched tutorial videos. The UI path engineers and customer service managers, as well as some of the directors that are local to our area, have been very helpful in providing this information. I fully intend to continue to do that and as long as it's available. If I were to rate the training materials, I would say the training materials are probably a five out of five rating. There's a lot of information there.

I would suggest others give the solution a good hard look to see if it works for them. Hopefully, for others, it will be a successful product and a useful tool.

Overall, I'd rate the solution eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Suresh Babu
CRO at Imaginea Technologies
Real User
The moment a machine takes over, there are fewer errors

Pros and Cons

  • "The democratization, automation, and attended automation, all of these are pretty good features. Those are all good value add to what it was there previously."
  • "Sometimes in their partner communication, they aren't consistent. This maybe is related to the fact they are growing as a company."

What is our primary use case?

We play significantly in the BFSI and healthcare space. A lot of use cases have been related to BFSI. Insurance is much bigger, with claims and underwriting, policy admin, health benefits, and so on so forth. There are also good use cases on the functional level, HR and finance, and that cuts across industries. 

How has it helped my organization?

As an example, looking at fatality insurance for pets, clients had a high volume of documents come in, claims in all different forms, and they had to apply logic eligibility. There's a simple rule of whether you allow or disallow. If they don't allow the claim, then there's a comp process. By a sheer ability to read whichever way the document comes in, clients are able to load the system and quickly get the eligibility. 

This dramatically improves their claims operation by a big margin. Whenever there is some complexity in one, then we do an exception. We crunched the time so well and made the process so cost-effective it has given the client a huge benefit.

What is most valuable?

The democratization, automation, and attended automation, all of these are pretty good features. Those are all good value add to what it was there previously. 

The moment a machine takes over, there are fewer errors. That is inherent. When you say value, that is the cost-benefit. 

What needs improvement?

We have seen a lot of benefits on the backend, but then the algorithm is constrained, which can't transform because of the older technology. 

Sometimes in their partner communication, they aren't consistent. This maybe is related to the fact they are growing as a company.

What do I think about the stability of the solution?

The solution is fairly stable. 

How was the initial setup?

The initial setup is always complex. Clients don't know the hardware, the licensing, or how it works. Any large organization will always have an initial hurdle. 

We have roughly around 164-165 trained RPA credentials on the engineering side, all on UiPath.

You do have complexity when it comes to maintenance, as you get to 50, 100 bots. 

What was our ROI?

As an example, one of the customers for whom we did an early bird, we estimated we could save this one division of their company $44 million. They only may have to invest about $4 million. There's $44.5 million for about 12 months. That's what we think we could save. 

The adoption of RPA has definitely been increasing and we know that all of that has been largely in the back office. In the back office, it's easier to check ROI. We've actually gone beyond ROI because ROI is a very simple statement, so we start showing clients value.

How long it takes to achieve ROI actually depends upon the client's way of implementing it. For example, some people will wait to take away the manual effort while they will stand by. Because what if it doesn't work? What if it fails? What if then my backlog increases dramatically? So, it is really up to them. If it is simple task automation, we can do it in about four or six weeks. In eight to 10 weeks they'll see the benefit. 

What other advice do I have?

We're using all components of UiPath: attended, unattended robotics, and Orchestrator Studio. We have a very wide customer base and our clients use all of them.

Cloud adoption is increasing. Deployment models are a little bit more a logistic question than anything else because companies who want on-site are a little bit more conscious of security, but they take a normal amount of time, just to figure out the infrastructure. If we moved clients to the cloud, we can make it easier to implement. With email on the cloud, they have a huge set of processes. The larger the company, the larger the processing. With the cloud, it becomes faster. 

I've got a deep partnership with UiPath. I would absolutely rate them high. I'd give them a ten out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Richard Denton
Director at RPA Box
Real User
Enables less mundane work to be done, there are fewer errors, better compliance, and better visibility

Pros and Cons

  • "The solution is quick and easy to implement. It's fairly easy, and it means clients don't have to get IT involved."
  • "They should expand on workflow type items and take another step up from the long-running workflows to offer more visibility of business processes within Orchestrator."

What is our primary use case?

The solution is primarily used for invoice processing in combination with intelligent data captures. It's used for anything to do with lots of finance processes. Typically they go into lots of HR processes as well. They're the two main business functions that we work in.

What is most valuable?

Orchestrator has valuable scheduling and being able to run things on demand and dynamically as well allocating the transaction, and the studio are good features. Nothing stands out in particular. Everything's kind of equal, it just depends on the task you need to complete.

With an unattended robot, you can schedule it and have it running autonomously.

The solution is quick and easy to implement. It's fairly easy, and it means clients don't have to get IT involved. If you get IT involved in anything there's always blockers and there are always other priorities. 

What needs improvement?

They should expand on workflow type items and take another step up from the long-running workflows to offer more visibility of business processes within Orchestrator.

The solution needs a better integration team, different versions of Orchestrator, and to make it easier to identify problems with versions, as well as to be able to fix those kinds of problems. It's hard if you don't keep up to date all the time as well, for example, to go from 2018 to 2019 versions. It's quite a big jump considering activities and things like that.

For how long have I used the solution?

less mundane work being done, fewer errors, better compliance, better visibility

What do I think about the stability of the solution?

I'd rate the stability five out of five.


How are customer service and technical support?

When we were using technical support we were typically going directly to some people we knew in UiPath because we knew them very well. We haven't had that many instances that we needed to use the help though.

How was the initial setup?

In terms of ease of setup, I would rate the solution four out of five. From an IT perspective, it's pretty simple, but from a non-technical perspective, I think people will struggle.

They've brought us Studio X which is starting to increase that to a five out of five. From a business user perspective a lot of the sales teams will sell it as a very easy to mend product which isn't particularly helpful because when you go into a customer environment and you have to build via a complex process and then integrate it with IT and all of the business systems then obviously it's not a five minute job. It's not overly complicated but can take three to four weeks for some processes to be implemented successfully.

From the time the UiPath license is purchased to implementing it virtually takes about three weeks.

What was our ROI?

ROI depends on the process. Some customers are using their people badly and they literally have a person doing the job of processing invoices all day long. It's very quick to realize their ROI because it's a 30-40 thousand pound salary that they get to replace very, very quickly. More commonly, on a big project, it takes 6 to 12 months to get to an ROI. Even if you are just breaking even, in a year or two you'll start to get an ROI.

What's my experience with pricing, setup cost, and licensing?

There's information online. There's actually a section where you can go through training online for licensing. There's some documentation available as well from the UiPath sales team. You can just ask them.

I've already struggled with licensing a little bit. It's never been super clear because you have the notion of a mode lock and concurrent users and things like that depending on whether you want it on one machine or whether you want the licenses to be able to float around different users. The wording around it can be improved. They communicate in a simpler way.

Which other solutions did I evaluate?

Usually, the client looks at UiPath, Automation Anywhere, Blue Prism, and sometimes other smaller competitors but that's quite rare.

What other advice do I have?

We use Orchestrator, Studio, and unattended and attended robotics. We typically use more unattended than attended generally. Increasingly we're using attended robots. We use Orchestrator but at 1:1 per client, and Studio for development.

For the larger clients, they still go on-prem, but mid-tier customers start to use the cloud solution.

We try to encourage clients not to run automation within virtual environments like Citrix. UiPath does work through Citrix but it's only if clients really don't have control of that environment. We have done it, but where possible we always ask clients to install either the robot on the local machine or to install the major Citrix extension. By running within virtual premises everything's a little bit more or less stable so you have to add more checks, which means the development time takes a bit longer; and the data coming out is a little bit less reliable. But with the Citrix extension, everything has become a lot easier.

I used a web tool for the UiPath Academy RPA training. I did a lot of the training before there was an Academy, and then when it came out I did the certification. We always put our team through every stage of the training. I'd rate the Academy four out of five. It's easy to follow and get through. The only thing that's lacking a little bit is, it's just that you can't do 2 weeks worth of training and then become an expert. Another thing is that there is a further certification which is an advanced developer certificate which needs product experience as well, and for me, there's not been enough distinction between the 2-week online training vs that proper diploma. There's always some confusion, when people say, "Oh yeah, we've got this", many people say it doesn't mean as much as it could, or other software companies have a better distinction between levels of certification experience. They need to offer a solution architect type certification for someone who knows the infrastructure really well and can prove it. There needs to be a proper qualification for that.

In terms of reducing human error with the solution, I've always been an advocate of the software benefit that comes out of automation. AFT savings are great but I think a lot the other benefits include less mundane work being done, fewer errors, better compliance, better visibility. One of the things that hasn't been exploited that well is the additional data that you get from automation. Where humans previously were just doing a job, for example, we automate a lot of processes.

I'd rate the solution ten out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
JB
Sr Digital Transformation Consultant at a tech services company with 501-1,000 employees
Consultant
The UiPath Academy is very intuitive and easy to use

Pros and Cons

  • "We have saved steps and time from people doing their jobs because they're not doing all this crazy validation anymore."
  • "There is potential there for some workflow capability. I know this would be going beyond RPA at that point, but having one platform that does a lot of things would be nice. Because as it stands, when you need to do a workflow or approval process, you need to send this out somewhere else. There are things the bot can do, but I can see some of that functionality already showing up though with the tasks and apps. However, I would like to see more."

What is our primary use case?

We have two customers. One is in the insurance industry. We are implementing it within our own company to automate HR and finance processes: back office. This is the same thing with the customer: back office. That's the focus.

We are using Studio, Orchestrator, and attended bots. We are not using unattended bots yet.

How has it helped my organization?

For one of our clients, their intent is to create a bot because one of their key folks was retiring. This person had a lot of knowledge of the processes and how things happen. So, the idea was to create a bot that helps. They want it to do 25 percent of most of the work, and this person would just validate instead of training somebody new to do the job. Their idea was to not hire for that position anymore. Instead, if the person is just doing validation, 25 percent of that load is then spread across their current staff.

What is most valuable?

It is easy to use. That is definitely one thing that attracts people. 

I really like the feature that you get to record actions. I wish that feature was a bit more advanced where I could build more automation. Sometimes, you have to stop the robot because the robot doesn't get the level of detail that I am expecting to see in the automation. Then, you have to stop the bot, and stop or break the recording. While it's nice in creating a first sort of brush off your automation, I wish it would just go a step further.

I really like the new products that were announced here. The apps have a lot of potential. I'm interested in learning more about that in the next few months. The same thing with StudioX. Although, it would be interesting to see if they're more business-friendly or not. While UiPath is advertised as a low code platform, you can't put it in the hands of a business user. They have no idea what some of the features are. Some things, they need to have extensive training and be tech savvy in several things before they can go there.

Several of us took training using the UiPath Academy. I thought the UiPath Academy was very intuitive and easy to use. I would give it a five out of five rating.

What needs improvement?

When you are tech savvy and been trained, it is a four out of five for ease of use. Having that automation recording feature operate better and capture more of the automation that you're trying to build would make it a five. 

With the new products that were announced, UiPath closed a few of the gaps. I can see how they could expand the products into other areas. There is potential there for some workflow capability. I know this would be going beyond RPA at that point, but having one platform that does a lot of things would be nice. Because as it stands, when you need to do a workflow or approval process, you need to send this out somewhere else. There are things the bot can do, but I can see some of that functionality already showing up though with the tasks and apps. However, I would like to see more. That would be good.

Moving bots to the cloud would be the next good step. The new product has Orchestrator in the cloud. I think moving to bots to the cloud could also be next along with having Studio in the cloud where you can do everything in the cloud: Deploy and run your bots from the cloud.

What do I think about the stability of the solution?

It is pretty stable. I would rate it a five out of five.

How are customer service and technical support?

I haven't used the technical support.

Which solution did I use previously and why did I switch?

We learned about this stuff about two years and a half ago. We started exploring it, then we decided to take the plunge and try it out. That's how it came about.

How was the initial setup?

The initial setup was pretty straightforward. 

It took us about four months from the initial purchase of UiPath to putting the robots in production. With our first deployment, we made a lot of mistakes. For us, it was like the first time you do something, you don't know exactly what you're doing, you just do it. Then, the second time, you're like, "Oh, now, I can go back and do other things differently." With us, it was very much like that. We learned sort of on the job.

What about the implementation team?

We did the installation ourselves. 

I didn't do it, but I know that the people that did the installation didn't have any issues with it. They didn't need to open a ticket in particular or anything like that. This tells me that it was fairly easy. 

What was our ROI?

We have saved steps and time from people doing their jobs because they're not doing all this crazy validation anymore.

Which other solutions did I evaluate?

We evaluated the top three. UiPath at the time was number three, Blue Prism was number number two, and Automation Anywhere was number one. So, we weighed them out.

I liked some of the functionality from Automation Anywhere. The recording feature of Automation Anywhere was much better and easier to use than UiPath. Although, I haven't seen the new Studio. In 2019, maybe they changed some things in there. Regardless, the Automation Anywhere tool seemed easier to use. But, in terms of partnership, they were not a good fit for the values of the company. Those things all go into account when trying to partner with somebody. That's why we decided to go with UiPath.

Some of the features in the software looked the same between Automation Anywhere and UiPath. Blue Prism seems very hard to use. That one we kind of killed on the spot. Between like Automation Anywhere and UiPath, it was more about how the company's vision, and where things were headed. All of that sort of helped. So, we were at that point that we were not really looking at the software anymore. We were looking at other things. That's how we ended up here.

What other advice do I have?

With the new additions that were announced yesterday, I'd probably give it an eight (out of 10). I still would like to see some other features, which I know UiPath would start crossing into BPM a bit when you start talking workflows and things like that. However, that would be a good next step given their market share, customers outreach, and beyond API and some partners that they have today.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Camilo Gutierrez
RPA Leader and Business Analyst at Ecopetrol
Real User
Orchestrator helps us to have an overview and control of the company as we scale up

Pros and Cons

  • "In terms of ease of use, I would rate the solution five out of five. It's really intuitive and any people that have the basics of coding can handle it."
  • "It could use an easy integration with SAP. Most of the processes of our company are in SAP. Sometimes it's kind of tricky to automate over it."

What is our primary use case?

We primarily use the solution for the financial processes. 

How has it helped my organization?

In our company, we are freeing up 14,000 hours per month.

What is most valuable?

All of the UiPath's components, meaning Studio, Orchestrator, and Unattended Robotics, are really important for us because they offer really clean processes. The one that generates more value for us is the Orchestrator because we are planning to really scale up the factory. It helps us to have an overview and control. With the insights that they announced recently, I hope we have really great control over it in the company.

In terms of ease of use, I would rate the solution five out of five. It's really intuitive and any people that have the basics of coding can handle it. 

What needs improvement?

In the next release, they need enterprise connect. That's something we were wondering about. 

The solution could maybe use more artificial intelligence components or stuff we can start to use in the AI field. 

It could use an easy integration with SAP. Most of the processes of our company are in SAP. Sometimes it's kind of tricky to automate it.

What do I think about the stability of the solution?

I'd rate the stability four out of five. We haven't presented problems but sometimes with the UiPath robot, the robot attended license breaks.

How are customer service and technical support?

We have reached out to technical support. We are in Columbia so sometimes there are slow responses because they don't have too much capacity to attend to us in Latin America. It could be better.

How was the initial setup?

Our time to market in implementing our first robot was four months because it was new for everyone in the company. We started too many processes at the same time and we were preparing everything around the company. It was slow. It was four or five months.

The initial setup was easy. We didn't have any problems.

What about the implementation team?

We implemented the solution ourselves. Our IT department and our robotics architect handled it. We also had UiPath help us with the set up as well.

I'd rate their assistance five out of five. They helped us a lot.

What's my experience with pricing, setup cost, and licensing?

Unattended robot costs are high.

For our company, we have money to buy the solution and we have a huge contract with UiPath, but for companies that are smaller, the costs are too high. For example, a company that is not too big, because they have to pay in dollars, may suffer because conversion rates are high.

Which other solutions did I evaluate?

When we started we started with UiPath and Blue Prism. We made 14 processes with each and we decided to stay with UiPath. Mostly because of the IT architecture. We really like the Orchestrator, for example. It was like a huge consideration we had because Blue Prism is like a closed book and we didn't like it too much.

What other advice do I have?

We utilize the full UiPath package. We are all on the cloud using the Microsoft Azure platform. 

We also use it within the virtual environment. It has been tough implementing it. Sometimes it doesn't identify the selectors or the images. It has a higher risk of failure. It's risky to have a centralized process.

We plan on automating the drilling process, the upstream and midstream process of the company, and the transportation of oil and gas for the company. Those are the main areas for us that we are aiming to automate. We started with back processes such as financial processes, logistic processes, and HR processes because they are not the core. As we continue learning about it, we will focus on the back-office processes.

A prerequisite for us in the company is to go through the UiPath RPA Training Academy. They have many courses, including foundations and advanced certifications. I'd rate the Training Academy four out of five. If they didn't explain too many things that would be great. They do basic stuff that will help people have a different mindset about it. They need more of an overview. Use cases, examples and more explanations about the activities in the UiPath would be useful. 

I'd rate the solution nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
AY
CTO at OOO “DMS”
Real User
Helps to eliminate human errors and helps to save us time

Pros and Cons

  • "All of the features are valuable. I think the best feature for Russian government customers is security. Security in Orchestration for requiring credentials. Our customer are usually serious about security."
  • "I would like to see more AI features with data classification and computer reason. I think it would be great to have more features in full monitoring robots."

What is our primary use case?

We use all of the UiPath products: UiPath Studio, Orchestrator, attended robots, and unattended. Primarily, we use them for financial liquidation. Our customers frequently use it for different cases. Some use it with chatbots.

Sometimes, our customers run automations in a virtual environment. In terms of implementing UiPath within a virtual environment, UiPath staff are working on the cost. Currently we have UiPath with a Citrix client and you need to go to the Citrix virtual station to activate. It's more difficult to implement as a user.

Our customers' organizations have involved about 15 to 20 people in their automation programs.

How has it helped my organization?

I would rate its ease of use as about four out of five. It's not so easy, but it's also not difficult. We have a great UiPath Academy and it's really useful and helpful. Sometimes we need to do difficult operations and use other frameworks, through activities in UiPath. I think this mechanism is very nice, but in implementation, the customers are pretty close. Sometimes we must do it.

This solution helps to eliminate human errors. The amount depends on the process and the customer. Even unattended robots don't provide 100% automation. Sometimes a robot interrupts and waits for a human to make a decision. There is a process when unattended robots do fewer steps and after ten interruptions are waiting for a human to go on. I would say there is about a 70% reduction in human errors when using an unattended robot.

UiPath also helps save time. One unattended robot works 24 hours a day because a robot doesn't get ill or need to sleep.

What is most valuable?

All of the features are valuable. I think the best feature for Russian government customers is security. Security in Orchestration for requiring credentials. Our customers are usually serious about security.

What needs improvement?

I would like to see more AI features with data classification and computer reason. I think it would be great to have more features in full monitoring robots.

What do I think about the stability of the solution?

I would rate their stability as four out of five.

In cases of high scalability when we have one process and many of us use that process, we sometimes have problems. When one process uses about 24 robots for 24 hours, we have problems with it. I think when many robots work at the same time, something goes wrong in orchestrating tasks between robots.

How are customer service and technical support?

I am happy with the support. For me, it's okay.

How was the initial setup?

The initial setup can sometimes be complicated, depending first of all on the environment, as well as the implementation strategy of the company. Too many processes or only one PoC could lead to a more difficult implementation. Sometimes, customers try to automate a lot of the big processes. When we try to automate the complete process, we understand with the customers how many FTEs you can get from it. Everything depends on the customer's requirements.

It takes about six months from the purchase of a UiPath license until our customers have their first robot in production.

Which other solutions did I evaluate?

UiPath is a data mining solution. Our company tries to explain why RPAs are useful.

I don't know which other solutions our customers evaluate. Kofax might be one. Sometimes we work with a customer to make a decision about which platform to choose. Sometimes we do a PoC for Blue Prism. In the Russian market, there are two major vendors that are competing against each other: Blue Prism and UiPath. Usually, customers go through a PoC to choose the best vendor. UiPath wins because you can automate more processes with it.

What other advice do I have?

I would rate UiPath as nine out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
JL
Automation Lead at a manufacturing company with 10,001+ employees
Real User
Good training and a forward-thinking platform, Unattended bots save us time and eliminate errors

Pros and Cons

  • "The Orchestrator management tools are growing a lot and are constantly improving."
  • "The technical support is a bit of a weak point for this solution, and ideally, they can improve turnaround time so that we don't have to figure things out ourselves as often."

What is our primary use case?

We are using unattended bots, Orchestrator, and Studio.

We use this solution for doing a variety of things. It includes a lot of back-office finance and accounting, tax, and a little bit on our operations side. We're also using it for some test automation within our IT group, so helping to test our points of sale, and some of our data transfers as well.

Orchestrator runs on a dedicated server, but our bots all run on virtual dedicated machines in our data center. There were some challenges in setting everything up to run in a virtual environment. We implemented a couple of years ago, so I think that it has improved by now, although it was challenging.

Part of it was on our end, where our people were not familiar with it. The challenges included picking the right type of VM to run on, having the right kind of setup, and having the environment configured correctly. We needed this to allow the RPA team to have enough control over the day-to-day maintenance, and not have bottlenecks with the technical side. Managing things when we had issues or needed to add something new was also a challenge.

The documentation was kind of broad and didn't go into the detail that we wanted it to, although I have seen that get better, so that is really good. I'm sure if we were trying to implement it today, it would probably be a lot smoother with the tools that they've come up with.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a four. I think there are still a few things they could do and it looks like they are working towards that. It still requires a good bit of training and ramping up for someone brand new to it, especially without a programming background, to jump in and start building. I think they can continue to refine that and they definitely are moving in the right direction. It's a little bit of a technical hurdle to overcome to be able to build not only just basic automations but enterprise-scale automations and automations that are reliable and can check up on themselves. I think they can work some more of that into the actual tool because we've had to do a lot of figuring out how to build best practices and how to program it directly, and the best way to be able to allow us to support it cleanly through the lifecycle. It is good, but there are some things they can add in to truly make it a five. My standards are pretty high, but I'm sure they'll get there.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. We are big fans of it. I typically don't get the luxury of hiring people with technical backgrounds. We usually have people coming out of school or people transferring from other departments who are interested in RPA. So, the Academy tools have been a lifesaver for us and they've been very good, especially for the RPA developer track. It is very detailed and we can really get someone through that training and feel like they're at least able to perform the basic functions of the tool pretty well. From there it is up to us in terms of getting them familiar with our best practices and how we program things and get some hands-on training with the more senior RPA developer to learn some further tips and tricks. Overall, I'm very pleased with the Academy offerings and they're one of the best I've seen from many of them.

From the point that we purchased our UiPath license until we had our first robot was perhaps a month or two. It did not take long, and that included time for training. When we started off, we bought the software, went through the training as a team, and then started building a few small things. We probably had the first one in production within two months of buying the software.

How has it helped my organization?

We have seen a lot of improvements to our organization.

We have one that was a really high-visibility project, where it was kind of a data entry thing that all of our retail managers were spending time on. The data was fed through to a vendor that we franchise through, and they were spending an hour or two a week across hundreds of locations.

We took that into the back office and got data feeds for all the data they were putting in, and then had a bot go through to the current system of reporting, and enter that data for every single store location. We were able to free up those managers with a bunch of time. It was about 5,500 hours a year.

In terms of eliminating human errors, I can say that it has happened but it is difficult to approximate by how much. This is in part because we have a wide variety of software of processes that we've implemented. So, in some, it's definitely higher than others. On the whole, it's been good and it's been helpful, for sure.

What is most valuable?

A lot of the value from this solution comes from Studio and the activities. They really enable us to make things happen accurately, with the clicks and the types they support. Of all the automation tools I've tried or used, they seem to be the most accurate and most consistent.

The Orchestrator management tools are growing a lot and are constantly improving.

What needs improvement?

I would like to see more interconnectedness of everything, including making the APIs a little easier to use, and having bots be able to call other bots and get them to start things. Having all of this a little more seamless would be really helpful.

I would like to see more seamless AI functionality built in to allow teams without data scientists or strong data people to be able to build and deploy simple models that will help enhance their bots further and let them do more.

The technical support is a bit of a weak point for this solution, and ideally, they can improve turnaround time so that we don't have to figure things out ourselves as often.

For how long have I used the solution?

We have been using this solution for a couple of years.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a four.

We've had some issues with stability, and I've talked to a lot of other companies who've had maybe more issues than us. It concerns ongoing support and the issues with bots not performing as expected or doing unexpected things as well. The problem is running into unexpected issues that can result from things that are not very readily apparent on the surface. This can be caused by underlying configuration differences in Windows, or patches that have happened, that sort of thing. It's still a challenge to manage and we often have bots that don't seem to have the issues when we are troubleshooting.

Sometimes it is our fault because we're not programming in enough breaks or logging enough to really track what's going on. It seems very dependent on the underlying operating system and things like update states of office applications. Occasionally, it'll just get stuck or hung up and we can't really figure out why, and that's frustrating. It definitely takes people time to go in and resolve those issues and figure it out.

It just seems like there's a lot of times where we just rerun the bot and then it works fine. I find it odd that it would stop at one point and then you just rerun it again and it works. A lot of those are, I will admit, due to input data issues or the system going down, or a website not being available or loading too slowly when it checks. However, I would like to see them continue to focus on stability as a platform, to avoid those as much as possible any issue.

What do I think about the scalability of the solution?

My team that I work with directly is probably about ten people in total. There are a couple of other teams who are working more on test automation that are kind of separate and that's probably a total of about five other people right now, and we're looking to expand to another couple of teams. That will probably be about five more people within the next year, and then my team is growing. We're looking to add a few more people next year as well.

I am the automation lead, and the users are RPA developers and business analysts.

How are customer service and technical support?

When it comes to the technical support for this solution, I feel that it may be a little bit of a weak point. When we reached out to customer support, we haven't gotten a ton of help, or it takes them quite a while to dig through the issue. It is understandable because they're going through someone else's code essentially, to try to resolve an issue. So, usually, we end up relying on internal people, more senior developers.

Sometimes it's just a matter of rerunning it or changing some input parameters and then trying it again, which is not the cleanest troubleshooting by any means. The problem is we felt like we had to, given the slow turnaround time on their support desk. We've kind of had to have the internal ability to figure things out.

Overall, I would rate their technical support a three out of five.

I know that they're a growing company and that they have a lot of new people. It seems like we've maybe had some bad luck in terms of the people that we've been in contact with when we've reached out. Perhaps they were new and maybe not fully understanding. There have been times we've reached out to support where we feel like we know the system better than they do, and that's frustrating. Again, that's why we've had to focus on internal knowledge building, which is a strength of theirs, through the training offered.

We do have a CSM assigned to us who I work with and he's somewhat spotty at times. I think he has a lot on his plate. So, at times we have questions that take a while to get answered.

Which solution did I use previously and why did I switch?

We did a proof of concept that was driven by a consulting company and it was not a success. After that, we decided to implement an in-house solution using UiPath and from there it was successful.

We began with RPA because our management was interested in the potential and in trying it out. Even though the PoC failed, I think there was a promise with the software that we were able to see, so we made the purchase and dove into it. Obviously, it has been successful.

How was the initial setup?

Installing the software itself, the Studio, most of the elements of the licensing and that sort of thing, were all very straightforward, which is great. I would say that the technical side, regarding the virtual machines, took a while in terms of setting up accounts and getting all the VM stuff figured out. All of that took a little bit longer than we expected before we had a stable platform. I think that there could've been some more resources available there, which I think they've partially fixed by now.

What was our ROI?

We were calculating our savings and our estimate is that in a little under a year, perhaps as little as six months, we probably earned back the amounts that we had paid for the platform for a year. Even into the journey, we felt like we had broken even and were making more money on top of that. ROI was very fast.

What's my experience with pricing, setup cost, and licensing?

I can estimate our licensing costs are approximately $100,000 USD per year.

Which other solutions did I evaluate?

In addition to UiPath, we evaluated Automation Anywhere and Blue Prism.

My main reason for selecting UiPath, I think, was the strategy of focusing on a very open platform and allowing anyone to try out the trial, and allowing anyone to register for the Academy. I'm really focusing on democratizing RPA and making it available to everyone. It was a big focus for me because the other two had very closed-off systems and while they were able to give us demos, we didn't really get as good of a feel for how the software works as we did with UiPath where we could just download it and try it.

Also, we just had very good experiences with the salespeople and the people who demoed the product. They were very positive and very excited about RPA, and kind of matched what we were looking for. We felt like it was a much better fit for us, focusing on easy to use automation, not as much on code security like Blue Prism, and Automation Anywhere didn't seem to have a clear strategy for what they wanted to do moving forward.

Ultimately, UiPath has been a successful choice, and I feel that they have continued to grow their lead on the competition.

What other advice do I have?

I really liked a lot of the things I see coming in terms of the future improvements for Orchestrator. I think it's going to continue to grow into a true kind of Cloud Platform for end-to-end automation, whereas right now, it's a little more focused just on building things in Studio, and then managing monitoring them in Orchestrator. So, I'm excited about some of the further integration with the dashboards and everything for managing how it works.

Upcoming is better management of projects from end to end. I've built a lot of things myself to keep up with that. But having UiPath support, a lot of that, a little bit better, it's improved. This is including the focus on the process mining and the design phase, and it's often a bottleneck of not having enough time to go through and really thoroughly map out and document the processes.

I am interested in trying the specific Studio for test automation. I think UiPath has a big advantage in that space with their RPA software. It really solves an issue that a lot of other test automation platforms have, which is not being as consistent as they could be, or being too hard or too complicated to program correctly.

From a cost perspective, we have definitely got our money's worth on the unattended bots, which is what we have been focused on. We have bought a few attended bots to try them and this next year, we will be looking for good use cases. It requires a little more integration and using the API. We're looking at leveraging more attended bots, and we may end up buying more, but we're still evaluating how to use them. Unattended bots felt like the clearest advantage for us to implement, and we were successful in starting with those.

We were an early adopter of this solution in our region, so I often speak with people who are researching this solution. I tell them that UiPath is a really great platform and it's growing. It's moving in a really great direction, and I recommend people to take it in-house. Find a small team of people who are really passionate and interested in learning it, and then start small. Start with a few small things to get your feet under you, build an operating model that will support scaling, and then slowly scale it out over time. That's what we have done, and it has been successful for us.

Overall, I am very happy with UiPath, but I do have a few small quibbles. On the whole, it's been very successful and I'm very happy.

I would rate this solution a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
DB
Sr Manager Operational Support at a comms service provider with 10,001+ employees
Real User
It has saved us tens of thousands of hours and the ROI was almost instant

Pros and Cons

  • "We are the first company to bring UiPath Academy in-house on the 30th of September. When we signed our licensing agreement, we added it in our own LMS. So, we have that connection and everything else. We love it. We've implemented all of their modules: RPA Starter, all three of the development courses, Solution Architect, Business Analyst, and Build a Bot. It's super exciting. It's one of the best things that we've done. I would rate it a five out of five."
  • "We now have a functionality that is being released for web forms. It's more for attended. I would like to have these web forms exposed in Orchestrator to be able to trigger a bot externally. I know we have partners that provide similar functionality. I would like to have that same functionality where you could deploy a form, but instead of having it pop up on somebody's desktop, they could go through a URL through Orchestrator and trigger the bots via a web interface. This is instead of having to be tied down to an attended bot."

What is our primary use case?

We have several use cases. We're a telecommunications company. We use it for anything from order entry, design, activation, and interactions with technicians within our field. We really have an end-to-end solution.

We are using Studio, Orchestrator, and unattended bots.

It is deployed on-premise but on our own cloud.

How has it helped my organization?

We had a long-time situation where we were sending technicians to the fields unnecessarily, because they couldn't install the service. So, we worked through a process to wake up devices. We used RPA to implement it. 

With downsizing, we have been able to automate a lot of this space, so we can downsize and still function as a company.

What is most valuable?

Capitalize on the unattended automation, as there are a lot of different methods to evoke and schedule it. You can email it, trigger it via API bots or Orchestrator. There are a lot of different methods you can use. We don't really do a whole lot of attended. Not that we wouldn't at some point, but unattended is nice because it's out of sight and out of mind. Set it up and let it go.

We are the first company to bring UiPath Academy in-house on the 30th of September. When we signed our licensing agreement, we added it in our own LMS. So, we have that connection and everything else. We love it. We've implemented all of their modules: RPA Starter, all three of the development courses, Solution Architect, Business Analyst, and Build a Bot. It's super exciting. It's one of the best things that we've done. I would rate it a five out of five.

What needs improvement?

We now have a functionality that is being released for web forms. It's more for attended. I would like to have these web forms exposed in Orchestrator to be able to trigger a bot externally. I know we have partners that provide similar functionality. I would like to have that same functionality where you could deploy a form, but instead of having it pop up on somebody's desktop, they could go through a URL through Orchestrator and trigger the bots via a web interface. This is instead of having to be tied down to an attended bot.

For some of the Insights stuff, we have found that you have to be flexible on measuring your ROI. You have to be able to customize some of that because it's not as cut and dry as you think it is. 

I would look for the audits on the back-end. Performance-wise, make sure that it is still performing. 

What do I think about the stability of the solution?

I would rate the stability as a four (out of five), but some of it could have been us too. 

An overabundance of logging that we created crashed the SQL Server. We had to adjust and restructure the way we were doing all of our logging to prevent that from happening again. Ever since then, it has pretty much been fine. 

We have had issues with upgrades. However, from a normal day-to-day functionality perspective, it is pretty stable.

What do I think about the scalability of the solution?

Right now, we have about 150 developers. Then, we have engineers and process analysts.

We have 400 automations on average and 1000 in the pipeline.

How are customer service and technical support?

It's been fantastic. It doesn't matter what time of day or anything else. We get top-notch service.

It has been about our contacts and support team. They look at us, and say, "You guys want to do what?" Then, they stand behind us and help us get it done.

Which solution did I use previously and why did I switch?

We had merging companies coming together with a lot of integration going on. With integration, there are multiple teams, processes, and systems. To keep up for our reduced expenses, we had to do it. This was another tool in the toolbox for us: automation.

How was the initial setup?

It took us eight weeks from initial purchase to the first bot to be put into production. It took about two weeks for assessment and documentation, then another six weeks to develop and deploy it. The bot that we developed was complex. It wasn't super simple. We've done simpler, but that time frame was about average for us.

What about the implementation team?

We did the deployment ourselves, but we had the premium support. So, we did have some support from UiPath. However, everything that we did, we did on our own.

What was our ROI?

ROI was almost instant. We measured everything from deployment. We measured our successes. We do audits once a month. ROI was pretty much from deployment. We don't audit anything in the first 30 days because there is a lot of settling in, some bumps, and, "Oh, we missed this step." For the most part, within 30 days, we were realizing and managing expectations on benefits.

We're really only measuring handling time right now, which is defined by our business clients. They define what handling time we are trying to define, then the measure of success. That's what we measure ourselves on.

We're probably in the tens of thousands of hours that we have saved, easily.

What's my experience with pricing, setup cost, and licensing?

Because we have so many agents, that's why we went unattended. Attended was very expensive for us because it's a per person license. Where we can take entire workflows, do the triggering and scheduling, etc. We never have to have any human interaction with unattended.

We have a cost model for operating expense savings. It is usually about $100,000 to $125,000 and takes us six weeks to develop and implement. That's development, testing, and implementation. We do code reviews on everything. That does not include all the documentation, assessment, etc.

We just signed a very large perpetual agreement. So, we had 125 Studios and 1200 unattended licenses. We paid $3.7 million. Then, we paid maintenance costs for the next three years, which was 15 percent of that.

Which other solutions did I evaluate?

We evaluated Automation Anywhere, Blue Prism, Pega, and UiPath.

Scalability was probably the number one that we went with UiPath. Scalability, the ease of use of the software, and the existing functionality that was there were the main reasons. There is a lot more out-of-the-box in terms of embedded functions that were there at the time when we did our analysis. It seemed like UiPath was really on the cutting edge. They were more proactively implementing good features, where others that we were talking with seemed like they were behind in that perspective. 

We'd rather stay on the cutting edge with technology instead of having to wait for our partner to get caught up.

Obviously, there are cheaper options than UiPath.

What other advice do I have?

I'm really excited about the new stuff. There is great new stuff. We wish we would've had this stuff a year ago because we had to build some of it in-house. We are really excited about the Explorer and process mining.

I would rate the ease of use of the platform for automating our company’s processes as a three and a half to four out of five (where five is the easiest). It depends on the skill set of the developer. If you are a developer with a .NET background, then it will be a lot easier for more of the customization. For the technology overall, it is easy to automate our processes.

We run our automations in the virtual environments, like Citrix. We struggled a bit with Citrix at first, because our infrastructure and systems are somewhat antiquated.

Nobody is perfect. I would rate UiPath as a nine (out of 10).

Which deployment model are you using for this solution?

On-premises

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Lisa Bruecher
Manager at Vindelici Advisors GmbH
Real User
Bots help eliminate human error and better reallocate resources

Pros and Cons

  • "The client is eliminating human errors as they are eliminating some of the accrual processes from SAP, where a lot of mistakes can be made. If the bot is not making mistakes, then they are eliminating errors by 100 percent, but this depends on whether the bot is efficient or error-free."
  • "Studio is a bit overwhelming in the beginning. They could get add some details, but not so many, into the foundation training. I've seen StudioX and loved the colors. Please get the colors into Studio. I loved the flow and that you got all these activities and colors too. It was so much easier. It was visually easier to understand where to click. It was really user-friendly."

What is our primary use case?

Our client's companies have extensive issues with SAP and getting information out of it. They have another technical ERP system with an in-memory database where they don't get the information out of it, then have to add it manually to SAP. That will be probably the first big use case for automation. So, we will get a bot reading it on the database from the Citrix environment and probably moving it to SAP.

The client will probably have it on-premise. They tend to be really risk adverse in terms of Cloud solutions. We have tried to get them to use the cloud more because it's just easier.

We are using Studio Orchestrator, and unattended bots. I have programmed attended bots before.

How has it helped my organization?

The client is eliminating human errors as they are eliminating some of the accrual processes from SAP, where a lot of mistakes can be made. If the bot is not making mistakes, then they are eliminating errors by 100 percent, but this depends on whether the bot is efficient or error-free.

What is most valuable?

You need an understanding of how to code, use the variables and arguments, etc. That was why I was excited for StudioX. I tried it earlier, and it was amazing. This is actually what they were missing. Studio is great because you can do so much stuff.

What needs improvement?

On a scale of one to five (where five is beneficial), I would rate the UiPath Academy as a four. There is some stuff that they could do better. I sampled the advanced, which is really difficult because it's just PDF. I had to use some YouTube videos to understand the framework that you need to pass for developer. They could do more videos on that.

They have three parts. The first is the foundation, and they are a lot of videos. The third part of it (advanced), there are no videos except one. That's only those PDF files, which you have to look and read through. I was like, "Okay, I probably can't do it." Then, I fell upon some community YouTube videos from other developers who just demonstrated it. This would be great if UiPath offered that, because I found out later that the developers made mistakes in their videos.

In the foundation, they get into much detail in the beginning. You're overloaded with information. You have to go through videos like three times to get it correctly. They could remove some stuff out of there. Those quizzes are really frustrating too. They are too detailed. If you sat with Uipath, you think it's really easy. However, it's not so much, if you get into those details.

Studio is a bit overwhelming in the beginning. They could get add some details, but not so many, into the foundation training. I've seen StudioX and loved the colors. Please get the colors into Studio. I loved the flow and that you got all these activities and colors too. It was so much easier. It was visually easier to understand where to click. It was really user-friendly.

I would rate the ease of use of the platform for automating our company’s processes as a four out of five (with five being very easy). I would rate it as a four because it didn't work in the beginning to get my bots active. I had to get into a lot of videos to get them running. I didn't understand how it needed to be designed or coded.

The Orchestrator training was much better, but I still somehow missed some details which I needed. However, it's not just do it, then it's done. You need some time to get into it. Though, it's much easier than Studio.

The integration with Outlook is not that good yet.

What do I think about the stability of the solution?

I would rate stability as a four (out of five). I had some cases where Orchestrator didn't work in it. We couldn't login and the platform was slow.

What do I think about the scalability of the solution?

We are still small and just starting out. We have five developers/solution architects involved in automation projects. We have done our certificate through UiPath Academy.

How are customer service and technical support?

Support is pretty good. It's responsive.

Which solution did I use previously and why did I switch?

Our client was having some problems. They got a framework running on a scale: 

  • Which processes should be automated?
  • What are the easiest processes to automate and more difficult?

How was the initial setup?

For our first client project, it took us five months from the time that UiPath license was purchased until we implemented the first bot. 

The initial setup was straightforward. They identified several easier flows, and it was like learning with the client together. I know they are phasing out some more complex issues where you have to get into the details of HTML coding and stuff like that to get some stuff done. That is where UiPath gets difficult, because it's just coding and tech.

What was our ROI?

Our client saw ROI after one month. They realized after we showed them the first process that three people would be free to do other stuff. They got to sort of afraid of what they would do with those three people, and those people were afraid, which was a big issue. 

We invented RPI and pizza. We all came to those pizza Fridays and showed them that they don't have to be afraid. They benefited from it more than not, and no one would lose their jobs.

Which other solutions did I evaluate?

We told the client UiPath is best. We looked for the biggest player in the market and decided UiPath was the platform.

We target medium-size companies and have long-term relationships with them. They trust in our opinion. We told them our reasons that we think UiPath is the best.

UiPath is biggest player in the market. They have this platform economy going. I'm really excited to hear that they bought the process goals. There's a lot of potential there, if they integrate process automation with process mining. That is a big thing for me.

We looked into other RPA tools, like Blue Prism. We decided it's harder to learn and implement.

What other advice do I have?

I would rate the solution an eight (out of 10). They need to thrive to get better.

If you have some tech experienced people, then UiPath is the better solution because it's easier to learn and implement.

Disclosure: My company has a business relationship with this vendor other than being a customer:
NH
Lead Process Analyst at ACT
Real User
The bots help us utilize our staff better

Pros and Cons

  • "It has a really good turnaround time for our operations department to start working on claims, because all the information has already been pulled upfront with the bots. Instead of having to go into an account and request medical records or a certain type of document, it's normally already been pulled on the front-end as soon as the account loads because we run everything through the bots."
  • "The implementations or integrations through Citrix are really good. The only problem that we are coming across is just maintenance. If the Citrix platform gets updated and we're not notified, it breaks. So, we have to reconfigure our bot to the new updates. Unfortunately, that's just the name of the game, and that would be true if we were pulling them manually versus a bot."

What is our primary use case?

Right now, the primary use case is document retrieval from our client system. We are a healthcare billing company, so we have to pull things like medical records and different documents from hospital stays. So, we used the robots to pull those versus an FTE.

We have both unintended and attended robotics that we use. We haven't really delved into Studio a lot yet. That's going to be part of our staging and going into the next phase. We built all of our basic bots, so now we're going into the more complex bots.

We are on-premise. We were looking at moving to the cloud, so that will be something in our next steps.

How has it helped my organization?

It has a really good turnaround time for our operations department to start working on claims, because all the information has already been pulled upfront with the bots. Instead of having to go into an account and request medical records or a certain type of document, it's normally already been pulled on the front-end as soon as the account loads because we run everything through the bots.

What is most valuable?

The most valuable feature right now is we have been able to utilize our staff better with the bots. We can put them on more high priority items. That was the one thing that everyone was afraid of: The bots would replace them. What we did is retrain them to do other tasks that we needed, as that was more of a priority for us.

What needs improvement?

We do deal somewhat with Citrix. It depends on the client and how the bot has to be set up. We have some clients who do run through Citrix, then we have some who use a VPN tunnel to get in. So, we have it on both.

The implementations or integrations through Citrix are really good. The only problem that we are coming across is just maintenance. If the Citrix platform gets updated and we're not notified, it breaks. So, we have to reconfigure our bot to the new updates. Unfortunately, that's just the name of the game, and that would be true if we were pulling them manually versus a bot. We would still run into that with the Citrix platforms.

What do I think about the stability of the solution?

I would rate stability as a five (out of five). We have not actually had any issues with UiPath. Most of our issues have been with just platforms changing, breaking, and the regular maintenance.

What do I think about the scalability of the solution?

We have about 40 bots right now with 30 ready to be made.

Our team is really small. We have roughly six people who are working with the developers and actually running the bots. We're the only department using the solution. Our department was asked to lead this on, so we've been very fortunate to be able to lead it and be able to help our own department first. Now, we're starting to look at other areas of the company to deploy RPA.

How are customer service and technical support?

We have not used UiPath technical support.

How was the initial setup?

The initial setup was a little complex, but that was because we really didn't even know what we were getting into. We were told by upper management (our CFO) that automation was the next frontier and we had to go that route. We were sort of the pioneers going through this for our company,

It probably took about six to eight weeks for us to talk with development and for them to get the context of what we wanted. It took them about five weeks to actually build the bot. Then, once they built the bot, it was in production. Of course, we had to go back and do some maintenance because it did not work first time. After we got the hang of it, it's been great.

What about the implementation team?

We got some consulting from UiPath. We do use their developers. Other than that, we do not go through a third-party. We did everything else ourselves.

Our experience with UiPath services was good. There were some bumps along the way. It's just trying to understand the process and RPA from what we've seen.

What was our ROI?

It took us about six months to really see what the bots could do. We then started tracking financial savings and how it's helping the company. We set out a bit differently. Our CFO came out, and said, "Automation is where we're going," but on top of that, "This is X amount of money that you have to save in the process."

We have spent the last 18 months tracking how much we are spending and how much we're saving. We hit the goal with no problems because we were able to shift staff. We did eliminate some staff, but this solution really brought out the skill level of our employees. Those employees with the higher skills were able to transfer to more important projects.

Within the first year, we saved a little over $600,000. That totaled to almost 19 FTEs which we ended up saving.

Which other solutions did I evaluate?

We haven't used any other vendors.

What other advice do I have?

We are on spreadsheets and data. I keep saying we're stuck in 1996. It's been nice to have the vision of being able to be in the 21st century and really be able to use the bots the way we want to use them.

We have not taken part in the UiPath training. That's something that we talked about right before this conference. We really need to start utilizing more of the training that's offered. We want to turn some of our soft coders into people who can really code for us, not always relying on developers to do all of our work. That's definitely something that we're implementing soon.

I would rate it at least a four (out of five) for ease of use. We don't deal so much with UiPath, but from what we do deal with outside of developers, we have not had any problems. It has been very user-friendly, for those of us that don't know coding. We are able to look at things, sort of fix things, etc.

I rated them a four for ease of use, not a five, because we want to see what UiPath can do. We have a lot on the table. We have 30 bots ready to go. A lot of it's more screen scraping, which will be more complex. So, we want to see really if UiPath can do what they say the solution can do. We want to test its scalability.

I definitely would say UiPath is the way, especially with everything that they're coming out with now. It helps you understand more about RPA instead of just being thrown into things. It helps you understand all that on a smaller level. It is what everyone else has said here at the conference too, "Start with a small project. Don't go out with a big thing because it's not going to work." Luckily, we did start small, and we've just grown from there. Those would be my suggestions.

I would rate the solution a 10 out of 10.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
SV
Manager Applications Development at Mercury General Corporation
Real User
Good training and stability, and the unattended bots save us a lot of time

Pros and Cons

  • "The most valuable feature of this solution is the unattended robots because I can schedule my jobs and it can run on its own."
  • "We sometimes struggle trying to figure out what kind of a bot we need to use for what kind of work, and it would be nice to have more clarity on this."

What is our primary use case?

We are using attended and unattended bots. The attended ones are very low profile. We are also using Orchestrator.

Our primary use case for this solution is to automate underwriting processes.

We do not run our automations in a virtual environment, yet.

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. I think that we still struggle sometimes with what kind of a bot we need to use for what kind of work. It may be a lack of understanding on our side. We need to have more clarity on this.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. This is what I have heard from my team members. I did enroll in the training but I didn't make much progress. That said, I have heard good things about it.

From the point that we purchased our UiPath license until we had our first robot was approximately a six-month transition.

How has it helped my organization?

In terms of eliminating human errors, I would say that this solution has done so to a certain extent. The stuff that we are automating was quite simple to begin with. As such, there was not a lot of room for error because we have multiple verification steps. I cannot estimate a percentage for the reduction of human error.

I would say that we have a time-savings of approximately fifty percent.

What is most valuable?

The most valuable feature of this solution is the unattended robots because I can schedule my jobs and it can run on its own. I don't need to pay much attention, except in the case of an exception. That is the only time that I need to deal with it.

What needs improvement?

We sometimes struggle trying to figure out what kind of a bot we need to use for what kind of work, and it would be nice to have more clarity on this.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a five. It is quite stable.

What do I think about the scalability of the solution?

We have a team of ten developers who work with this solution.

Which solution did I use previously and why did I switch?

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

We got involved in automation because it makes us more efficient and we save money. These are a few of the important things that we are always looking for.

What about the implementation team?

The implementation of this solution was done in-house.

What was our ROI?

We have seen ROI because a lot of the work is now automated, so the people who used to do these tasks, the monotonous work, are now doing better things. I would say that we saw ROI in five to six months.

What's my experience with pricing, setup cost, and licensing?

The licensing costs for the unattended bots are a little too expensive. If it were lower then I think we could use it more effectively.

What other advice do I have?

We are excited about the upcoming features with artificial intelligence and document understand capabilities. I think that those are features that would come in quite handy for us.

My advice for anybody considering this solution is to take a look from the grand scale to see which use cases are the prominent ones. Do not look at all of the tiny details because sometimes we can make a use case very complex. The end result is less valuable. Look for the high-level stuff that can be quickly automated, then come down to the final stuff later.

I would rate this solution a ten out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
SM
Sr Consultant at a marketing services firm with 1-10 employees
Consultant
Saves significant time on manual, mundane, and repetitive processes for our clients

Pros and Cons

  • "The most valuable aspect is the different capabilities and features that can be applied to different processes."
  • "I would like to have a guidebook of examples that help me to determine the feasibility of specific use cases, based on the tools and the features that are out there."

What is our primary use case?

We are using Orchestrator, Studio, attended and unattended robots.

I am on the business analyst side, so I do not have much experience with Orchestrator.

We are using this solution to automate processes for our clients. They typically have mundane processes or something that's super repetitive, that we're able to quickly automate for them and see that return. We did do an attended bot with them as well, to improve their call center.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would say it's a four. This is a rating from the business side, as opposed to the development side. We understand what the features are, and when new releases come out we have an understanding of what's feasible. I am not rating it a five because sometimes we do not know whether a use case is feasible or not. It means that I may have to speak to one of the developers to see whether it can be done with the tools and the features that are out there.

We host the UiPath Academy RPA training every other month for our clients. I have not taken the full course, but on a scale from one to five, I would rate it a five. This is based on the number of people who sign up for it and look forward to attending it, just to learn the basics of RPA.

In terms of how long it takes from purchasing a UiPath license until having the first robot, the average is probably four weeks. It depends on the complexity of the process. 

How has it helped my organization?

We have helped our customers to reduce some of their manual work, but they also benefit by freeing up their time to use elsewhere. Some of the processes we have automated have people spending hours locked up trying to finish.

It is also that we are improving areas such as the production line, or even automating some of their dashboard reporting to get more accurate information a lot quicker. We've been able to help cut that down but then also provide accurate data, and faster as well.

With respect to saving time, this fiscal year we were at seventy thousand hours saved across the enterprise. That is significant and has been across different departments and different regions, as well.

In terms of eliminating human errors, we do not have an exact calculation. We do get a lot of good feedback about the bot's performance doing well.

What is most valuable?

The most valuable aspect is the different capabilities and features that can be applied to different processes. I don't consider one particular feature more valuable than the others because they are all relevant to what the need is.

What needs improvement?

I would like to have a guidebook of examples that help me to determine the feasibility of specific use cases, based on the tools and the features that are out there.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a five. I haven't had much in the way of negative experience with it.

What do I think about the scalability of the solution?

There are approximately two thousand people working on RPA across the firm. On my current project, we are a team of about sixteen people at our client's site.

Which solution did I use previously and why did I switch?

I cannot say for a specific client, but I do know that our clients are constantly looking for what's out there. Whether it is from banking, automotive, or retail, they want to know what they can do to improve their firm or their company. RPA has been on the rise in the last three years, so I would say they want to be able to get hours back and save time so that they can allocate resources elsewhere. They are always looking for a tool out there that'll save them money and time.

What was our ROI?

In regards to ROI, we track it upfront. We have asked for the information to assess if a candidate process is a good use case. Then we track it in our dashboard throughout the year just to ensure that we are actually calculating the hours correctly. We'll then follow up to make sure that they are seeing those changes and they are receiving those hours saved. We have found that over the year, they are seeing a return on investment.

We track data in terms of money savings that the tool provides. I don't have the dollar amounts, but I can say that there are some processes where we have saved $50,000 USD just on a single process. It really varies on the complexity of the process and the time it would take to complete without automation.

Which other solutions did I evaluate?

I have worked with other tools and I see them as pretty similar.

My experience is with Blue Prism and Automation Anywhere. I'm not developing, so I don't have any details on the tool itself. My preference for UiPath is based on what seems to be the goal, and what is easier to understand. It rolls out more features and newer features, faster.

What other advice do I have?

I am looking forward to trying the new UiPath Connect feature. I have seen the demo and it seems like that would be helpful for my role, specifically being on the business side. It is able to assess the use cases and determine what percentage they are RPA-able. I think that it will be super helpful.

My advice to anybody who is researching this solution is to try UiPath Academy Live first before they invest in the tool. This will allow them to get a better understanding of how it works, and get familiar with the services provided.

Sometimes I have questions. If I didn't have any questions then I would rate this solution a ten out of ten.

Overall, I would rate this solution a nine out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
CP
Application Developer at a wholesaler/distributor with 5,001-10,000 employees
Real User
Easy development for a .NET programmer, unattended robots save our teams a lot of time

Pros and Cons

  • "Unattended robots are my favorite because it allows us to completely remove a process from a person's day."
  • "I would like to see support for native C# capability."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

What do I think about the stability of the solution?

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.

How are customer service and technical support?

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.

What about the implementation team?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
BB
Manager Operational Services at a energy/utilities company with 501-1,000 employees
Real User
Good training, straightforward to install, and easy to use

Pros and Cons

  • "The software itself is relatively straightforward and easy to use."
  • "Enhanced capability in the document management space would be a huge benefit to our organization."

What is our primary use case?

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.

How has it helped my organization?

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.

What needs improvement?

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.

For how long have I used the solution?

We put our first process into production last week.

What do I think about the stability of the solution?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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

What about the implementation team?

We performed the implementation ourselves.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Kaitlyn Kapp
Software Engineer at Security Benefit
Real User
Running unattended processes and receiving daily reports has helped us become more efficient

Pros and Cons

  • "I think the most valuable feature is being able to run processes in an unattended way where we can schedule them, and then have the report sent to the process owner's inbox in the morning."
  • "I would like to see a biweekly scheduling option in Orchestrator."

What is our primary use case?

We are using attended and unattended robots, Orchestrator, and Studio.

We are in the financial services industry. A lot of what we do is background data processing, and we use the unattended robots for a lot of it. We do have some attended robots as well, but most of our processes are unattended.

I am a developer, so I primarily use Studio. I write the instructions for our Orchestrator Application Manager to do everything we need in Orchestrator. 

We are currently operating an on-premises deployment, but we're in the pilot group for Cloud, so as soon as we get a date on that we'll probably be migrating.

One of the primary processes that we've automated is reporting. Prior to automation, our users were only able to run a few of the reports, a few times a week. Now, we're running every single report that there is to run, which is probably four or five times what they were able to do, every single day. Every morning they receive a summary of that work, so they're able to just get on and look at it, rather than during the close of the day. In financial services, the close of the day is crunch time. We work really hard to make sure that everything is done within a set about of time because there is a domino effect. One person has to be done before the next person can finish, and they're not having to dig back and try to figure out when these issues happened. We're providing it to them upfront. We can say exactly what happened, which account they need to look at, and on what date. This means that we're ahead of the issues, rather than trying to backtrack and find them.

We are not currently running in a Citrix environment, but the only reason we're not is that our sister company hosts our Citrix environment, so we can't install any of the services that make those environments much easier to utilize. For example, we can't install the computer vision component because we don't own it, so they won't let us.

Our team is really small, there's only six of us on the actual RPA team. However, we work really hard with the business to get buy-in in every department. We're trying to roll out at least one automation in every single department. Our company's goals for the next year, I believe, every associate of the company is supposed to have proposed a task that they are doing, whether it's daily, monthly, yearly, whatever, that could be automated. Then our team will ingest that, prioritize that, and work through it. But, we're really trying really hard to get our whole company involved, and we're getting ready to kick off this campaign to try and get more attention to it and to try and get people using it. We want it to be more than just a buzzword. We want it to be something that everybody's talking about regularly, and using, and excited about.

When it comes to getting people interested, I think it's probably a combination of education and sharing the experience of those projects that we have rolled out. When people are really seeing that with the projects that we've rolled out, our close is shortening, they become interested. What we say is happening, or will happen when we're rolling these automations out, is happening. Getting that to be shared from process owner to their team, to the teams that they're working with, it acts like word of mouth for those that are affected. We don't like it to just all come from us, the technical team. We don't want to simply tell them that it's going to do something. We want others to talk about what it has done for them and suggest they should take advantage of that too.

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 five. We don't struggle with it.

I took the UiPath academy training, and I love it. We are looking at an unrelated tool right now, and we found no comparison between their training and the UiPath Academy. We were spoiled with UiPath Academy, and we didn't really realize how good that training really is.

The thing that I love about the developer training; the level one, level two, level three... level one really does walk you through it. It gives you, literally the walkthrough, so when you don't understand, you can go back, you can look at, and see exactly how to do it. But by the time you're in level three, it's not doing that anymore. The requirements are a little bit looser, you have to figure out how to interpret the words or the requirements, and it becomes more challenging, but I think that that's important, because, by the time that you're actually working real projects, it's not a walkthrough anymore. You have to figure it out on your own.

From the point that we purchased our UiPath license until we had our first robot was approximately three months. It did take us a little while, but we knew that we purchased our licenses before we were really ready to hit the ground running. We function out of such a small team, and we were still working with UiPath trying to figure out which partner we wanted to bring in for consultants because we wanted somebody with experience. We didn't want someone who just finished the training just run in and try, and I think we learned a lot working with that consultant.

We did work with a second consulting group, Machina Automation, and we loved working with them. They're great. They're just so supportive, and they really want to make sure things are right. It's never just sending them the requirements and pounding it out to get it into production. We work with them really deeply to try and make sure that they understand the process, we understand the requirements, they express their concerns to us, we express our concerns to them, and we work together. It's not like we just send them the documents and they send it back as a project. The whole way through we touch base with them every single morning. They're always asking what more they can do and how they can help. They ask if we're happy with what we received.

We do time card reviews, so the time that they spend with us we're actually able to go back and validate, based on that, what they've said they did, that indeed it is what they did. We had received some scrum and sprint training from them. We've had actual developer consultants, we've had mentoring hours for our developers. So we've had a lot from them, and they've been able to help us with everything. Anything we ask, they try to accommodate us. For example, we asked if they had any experience with Kibana. They did not but said that they would find somebody who does.

How has it helped my organization?

With respect to saving time, I don't actually track that because I am a developer, but I know that our goal for next year is twenty thousand hours. That's the big goal that we're working towards. With one of our processes, I think we're going to hit about thirteen thousand hours if we can just get that one process done. That's a statement review. We sent out tens of thousands of statements, so we'll be able to review every single one of those. This would be a huge saving in time.

I think right now we have about one hundred and thirty-six processes in production, and a lot of what we've done so far is in the finance section of the business. As such, a lot of those are only run on a quarterly, or monthly basis. We have some annual processes, and we have very few daily processes, but those daily processes add up over time.

In addition to the hours that we have saved, one of the big things we're working on is accuracy, control, and staff avoidance. Staff avoidance is the work that couldn't have been done otherwise because we would have had to hire someone to take on all of the work. So, we're able to do more than what our current staff is capable of doing. We add that into our time savings.

But, more than that, we really do focus on accuracy and timeliness. We're able to speed things up. We're able to ensure that things are exactly as expected. We spent a lot of time in the early stages of our planning, really trying to optimize our processes, so we get our original documentation, we take it, and our team works with the business to optimize that. After we get sign-off and we've optimized the manual process and got it documented and signed off, then we do a developer review and discuss ways that it can be made easier. Then we do a review for development and optimize it. Finally, once we get that signed off, we actually start our development.

We spend a lot of time on the front end of the process, making sure that everything is accurate and reliable, and we're going to be able to deliver faster as expected, and it's going to be able to handle all of these different errors or use cases. Following this process has worked well for us, so far.

What is most valuable?

I think the most valuable feature is being able to run processes in an unattended way where we can schedule them, and then have the report sent to the process owner's inbox in the morning. The is great for us, and we use it a lot. It saves the users a lot of time, and we're able to do a lot more for a user than they were ever able to do on their own.

What needs improvement?

I would like to see a biweekly scheduling option in Orchestrator. We've actually built into our automations a roundabout way to process every two weeks but it would be really nice to front end a biweekly schedule. Being in the financial services industry, we do have a lot of projects that run on weird schedules. We've kept some of our automations attended just because they're ad-hoc. They might need to re-run them. We don't want to have to wait for Orchestrator managers to kick those processes off. But, outside of that, there is no need for this one to be an attended robot. It's a perfect candidate for unattended automation, just the scheduling is the problem.

For how long have I used the solution?

We have been using this solution for just over a year.

What do I think about the stability of the solution?

With respect to the stability, on a scale of one to five, I would rate this solution a five. We haven't ever had any issues with it.

Which solution did I use previously and why did I switch?

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

When I first started at the company as an intern for my department, it was only myself and my boss, who's now our COE manager. The very first thing that we did was meet with all of the different functional departments of the company, and we explained to them what RPA is. We explained the types of processes that it can help take off your desk and asked for ideas from each department about what could be done to help them.

We took that, and we built this huge backlog of perhaps three hundred different items, prioritized them, and worked with others to explain that it was needed. At this point, we did PoCs with UiPath and Automation Anywhere.

How was the initial setup?

I found the initial setup to be straightforward. They had me sit in on it and I don't work infrastructure, so there were some things that kind of went over my head. They did a lot of planning. After some help from UiPath, it went really fast.

What about the implementation team?

UiPath helped us with the implementation. We worked with them to really figure out what our infrastructure needed to look like. 

Which other solutions did I evaluate?

We evaluated both Automation Anywhere and Blue Prism in addition to this solution. We ruled out Blue Prism pretty quickly. Our sister company uses Automation Anywhere, but we liked UiPath, primarily for the reason of our experience working with them and the sales team. To me, it was so much more than just working with the sales team, they're our friends now. We still talk to them and we have relationships with these people. We actually just ran into one of our developers for our PoC. It's a culture you want to be a part of.

In comparing with Automation Anywhere, one of the big reasons we went with UiPath was the support that we received. Any question we had was immediately answered. If they didn't know the answer, then they would search to find the right people in the company who did. I think that that's more valuable than just saying that they'll find us an answer. You always got the feeling that they were going to follow through, just by the conversations that we have had with them. I think that really sold us, a lot.

Also, watching the road maps for both companies at the time, initially it seemed like Automation Anywhere was ahead, and that UiPath was catching up. Then, when UiPath started releasing what they were going to be doing, as opposed to only what they were working on right now, we realized they were really going to be moving ahead. I think that kind of sold us too. Just watching what's on the road map, and how it fits in with what we see our company doing in the next few years, they aligned really well. I think that was the point where my boss really realized that it's going to be a good fit for us.

What other advice do I have?

When I was in business school, they taught us that the things that users like the most are the things they didn't know they needed. I think UiPath does a great job of anticipating the users' needs, and they meet them before we knew that it was what we needed. I am excited about the next release.

I recently had a discussion with my father, who works for one of the energy companies in my state. He works at the IT level but on the infrastructure side. When I explained to him our savings in terms of hours that we have had since adopting RPA, he was very excited and is now heading their RPA initiative.

RPA is making a difference and it's really changing the way the workforce works.

My biggest advice for anybody considering this solution is to get their quality improvement, and Six Sigma teams involved because I think it makes a huge difference in terms of understanding processes. When you can get your processes understood, you can get people on board early, at every level.

I think it's really important to have proponents for automation, just in general. You want to have the automation mindset at every single level. Of course, it's important to have your C-level bought in, but it's important to have the people who are doing the work bought in too. If you don't get their buy-in, it's going to be much more difficult because a lot of the work that you're automating is at their levels. You're working with them on a day to day basis to understand their process, to understand all of the rules behind what they're doing. So, buy-in, and process understanding, that's just critical. You can't move fast without those two things.

We have nothing bad to say about UiPath. We have regular communication with them and all of the concerns we have are always addressed. They're addressed quickly and they're addressed well. They really listen to what the customers want.

I would rate this solution a ten out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Shashi Singh
Director of Shared Services Automation and AI at Virign Media Business
Real User
Scheduling features prioritize work and queuing systems to make sure they're at the right points in time

Pros and Cons

  • "The main value within Orchestrator is definitely the scheduling aspect. That includes the way you can prioritize work and use queuing systems to make sure they're at the right points in time, as well as whether they'd be long term related, especially if we're looking at finance."
  • "One of the issues is with the acquisition of new types of software and new companies. It's important to introduce process documentation and make sure that it's not just making it look like UiPath products, but making it feel and act like one to us. They need to make sure it's embedded and the integration is seamless. They should just keep improving how easy it is to use. I think it's very good already, but there's always room for improvement."

What is our primary use case?

We use UiPath primarily to drive efficiency within the company and introduce a new technology, which is only going to become more popular and more prevalent in the industry in the next few years.

At the moment, we use Orchestrator, Studio, and unattended robots.

We invested in an RPA solution because competitors were doing it. They do it because it's the next wave of this industry, the fourth industrial revolution. Everyone's saying that you can't escape it. It's also because our company, in the shared services department, is thinking about how to challenge our existing models. Traditionally, you chose whether to take the processes onboard or streamline them offshore, but robotics and automation are a competitive alternative to outsourcing. It's very easy. We are challenging the status quo and making sure we're evaluating all our options effectively.

How has it helped my organization?

We had a process that was very manual and repetitive and took a team of 14 people, all keying in manually. Now, we've managed to automate it and save 14 employees worth of effort, which amounts to around 14,000 hours to date.

We run our automations in a virtual environment as well. We do Citrix environments when we're working with our offshore partner. We do it on Citrix when working locally. Both work well. I know UiPath has developed a lot on the Citrix platform lately, so it's getting better and easier to do.

Within my immediate team, I have eight people and we can also involve the other operational teams. Including everyone who's related to automation across IT and ops and us, you're probably looking about 20 or 30 people.

What is most valuable?

The main value within Orchestrator is definitely the scheduling aspect. That includes the way you can prioritize work and use queuing systems to make sure they're at the right points in time, as well as whether they'd be long term related, especially if we're looking at finance.

In terms of Studio, it's just getting easier to use. Studio X is basically the embodiment of that. Even at this point in time with the current Studio version, anyone could pick this up and run with it to develop simpler automations.

The best feature about unattended robots is that they do exactly what you ask them to do. They are as reliable as the code that you provide them with. I think as long as you've got the right governance in place, such as IDs you have created, and you looped in the right teams, the robots are just the shell that will do exactly what you ask them to do.

What needs improvement?

I'd rate the ease of use of automating our processes at three and a half out of five at this point in time. That is because we've been on a journey over the past year or so and it's not been smooth sailing. There have been issues. I'm not saying that UiPath's support hasn't been great. It has been, but there is still a lot of work to do. It's still a relatively new product in terms of the grander scene of the industry. There's still a lot of work to do there to make sure that the integrations with existing software providers as well as new ones and API connectivities are as they should be. Often, you'll find yourselves using the workarounds in order to address issues that they haven't quite solved yet. I know that's constantly being improved, but that is the journey that we've been on.

One of the issues is with the acquisition of new types of software and new companies. It's important to introduce process documentation and make sure that it's not just making it look like UiPath products, but making it feel and act like one to us. They need to make sure it's embedded and the integration is seamless. They should just keep improving how easy it is to use. I think it's very good already, but there's always room for improvement.

What do I think about the stability of the solution?

I would rate the product's stability as three and a half, based on our experience. This relates directly back to where we've had challenges. Some of the integration with more mainstream products, like Excel, for example, has been questionable at times. It's just striking that balance between the fact that we want it to be democratized and easy to use by everyone, while we don't want to be in a position where we're forced out of the route to use macros necessarily within Excel. We want the UiPath software to be just as quick and easy to use as that more technical solution. Otherwise, we lose the benefit of having it. It shouldn't be technically inhibited.

How are customer service and technical support?

I think their support offerings are good. They're very responsive. I think the challenge that they face though, is that they don't always have the answer. They don't always know what the real root cause is. Unfortunately, that's where the real crap piece comes in, which is both a blessing and a curse. It gives me some way of getting around it but it doesn't give me confidence that the issue will be addressed.

How was the initial setup?

It probably took us about nine months to deploy, from the initial UiPath license to implementing the first robot in production. The reason for that is the learning curve of the team as well as the education across the operational teams to bring them up to speed and make sure that everyone's on the same journey. We were also working very closely with IT to make sure that we've got the right infrastructure in place, as well as support models, governance frameworks, etc. Without it, you can't really get anything done. It's a new technology and it was a new concept for everyone. Needing a robot ID, for example, was something that was never discussed before. Lengthy conversations had to be had to make sure that we weren't putting anything at risk with data privacy, for example.

The setup was both straightforward and complex, really. Some bits we're quite straightforward, but other parts were more complex. Especially the infrastructure we're still dealing with now one year on still has some complexities. We're still thinking about credential management versus the use of virtual machines and whether we should be using high density or not. There is also the matter of all the different types of offerings. There's a matrix that you have to abide by and I don't think UiPath is even aware of all the conflicts between the different options. That's something that we're still working through right now, but I'm sure they're going to address it.

What about the implementation team?

We outsourced the implementation.

What was our ROI?

The performance benefits usually you would see instantly. We had a realization that there were some process changes that we probably needed to make, which we hadn't done prior to going live. I think it took us probably three months before we really saw the benefit coming through.

What's my experience with pricing, setup cost, and licensing?

It's the same as what you would see on any of their list prices. There is also a corporate discount because of scale. Overall, we think it was a competitive price offering. They were the cheapest out of the three, so that's why we went with them.

Which other solutions did I evaluate?

We looked across the big three: Blue Prism, Automation Anywhere, and UiPath. We did have a few others we considered, such as Kofax and Pegasystems. However, they're not dedicated RPA tools. That narrows you down immediately to probably select one of the top three dedicated RPA providers.

UiPath is a very unique example of being very technology-based from its history, but also its culture is very different to the other two. They're trying to be humble. UiPath has a different background and cultural fit, which is very much like our company. That was definitely one of the reasons we chose them. The other reason was the views. We just find it easier to use. The strategy, especially at the point in time when it was announced where the product was headed, was very much that they're trying to push this out to a robot for every person. We want everyone to be able to access it, too.

What other advice do I have?

Do what you would normally do with any vendor. Check out the competition and see what is right for your company. I'll be shocked if you don't think that UiPath is the best because there's a reason why it's at the top of the Gartner reports all over the shop. It's got great user feedback on places like IT Central Station and other review boards. There is absolutely a reason for that. Also, assess the other values that you place importance on. It's not all about costs. Cultural fit was a massive deal for us. What would you envision your company looking like with the uptake of automation? Is it a cultural thing? Is it purely about efficiency or do you want everyone to be up-skilled for what the workforce in the future will look like? That means that actually having everyone being able to access the tools is very important.

I would rate UiPath as eight out of ten.

I have used the UiPath Academy RPA training, although not completed it. I am a bit busy doing a few of the bits, but a lot of my team have completed level one and some completed level three. I have one member of my team who just completed all the training available online. He's done every single module that you have available, including obviously the RPA Advanced Developers training. I think there is a wealth of knowledge there. It's incredible, but it's the same training material that's used internally for UiPath as well as other companies. I think as long as they stay on top of it and make sure that it never gets overlooked, it's a great resource for anyone to get, in order to up-skill in the new technology. If they constantly talk about the democratization of RPA, this is fundamental to that.

The training has helped my team get up to speed, apply best practices, and make sure that we're not wasting time. We were trying to work it out for ourselves in a bit of a haphazard manner. It also forces standardization, of course. Anyone else who decides to get qualified can use it. If you're thinking about doing attended automations, I think it's the right way to do it. Everyone has the same set of standards and rules to build off of.

I would rate the training as four and a half out of five because there's always room for improvement. However, I think it's very thorough and they've covered all the aspects, both technical and not technical. It is very impressive.

I think there are different perks to using one type of robot as opposed to another. The unattended robot cost is higher, therefore the need to make sure the utilization rate is high is paramount to getting your value out of it. I think that makes it challenging but worthwhile. There are different types of processes you will end up pushing towards with an unattended automation profile, whereas an attended profile, which we're starting to move into now, leads to other types of automation opportunities. Attended robots are cheaper, which means it is easier to achieve ROI, but you can almost expect less utilization because it won't be people's full-time jobs. They won't get back all the time and there will be licenses to honor which are being consumed. That has to be baked into the business case. I think you will end up with a portfolio of both. The big opportunities probably sit within an unattended fashion.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Larry Hinds
Systems Administrator at Allied Solutions
Real User
Unattended robots save us a lot of time, and Orchestrator makes it very easy to see what is going on

Pros and Cons

  • "I like Orchestrator and how easy it is to manipulate and get your data, to see what's going on."
  • "One of the things we're struggling with it how to project how many robots we need to do these processes, so better documentation or assistance in this regard would be useful."

What is our primary use case?

We use unattended robots and the Orchestrator module. I am most familiar with the Orchestrator. We are very new to this solution and just getting into it.

We are a financial insurance company and we do VoW, Verify on Web. We have a bunch of different insurance carriers.

We run automations in a virtual environment, VMware, and I haven't seen any problems with it.

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 five. For my part of it, this solution seems very useful. I have limited exposure to it because I do more of the installation, the configs, etc. I don't really work with the workloads, although I see what is being worked with. We have our in-house developers who are doing the integration into our in-house programs, so I watch what they do and it just seems that it's very easy to pick up on.

I have not used the UiPath Academy, although I think that the developers have. I did not get any feedback from them about it.

I was not involved at the time, but I think that from the point that we purchased our UiPath license until we had our first robot was approximately three to four months.

How has it helped my organization?

In terms of eliminating human errors, I would say that we have a twenty-five percent reduction in the number of them. However, it is hard for me to say because I'm not that clear with it prior to the incorporation of the robots.

With respect to saving time, because of the commitment to the development and the installation and the bringing things onboard, at this point, we have not saved time. In daily operations, we do save time. I would say that we save between twenty and forty hours a day.

Our organization has improved because of the time savings. We've got robots now taking ten seconds to do what people were taking four to six minutes to do. It's a whole department of people that are now free to do other things.

What is most valuable?

I like Orchestrator and how easy it is to manipulate and get your data, to see what's going on. My job is to make sure that the system is running, so it's very easy to go to the Orchestrator through the dashboards. If it's not running, you'll see through the logs what's not running and what has caused the problem. At that point, normally, I escalate it to whoever needs to work on it.

The company likes this solution because of scalability.

What needs improvement?

One of the things we're struggling with it how to project how many robots we need to do these processes, so better documentation or assistance in this regard would be useful.

What do I think about the stability of the solution?

With respect to the stability, on a scale of one to five, I would rate this solution a four. I cannot give it five, yet, because I have just not had enough exposure to it.

What do I think about the scalability of the solution?

We have about twelve people working with this solution, from developers to the business side to the IT side.

Which solution did I use previously and why did I switch?

The idea of RPA was brought back down to me from our VP of IT, but I'm not sure where he got it from.

What was our ROI?

We have already seen a workload that has been moved off of our employees. It was within the first two months of the bot being developed. It is not my place to say the amount, but I can say that it is substantial and six digits. 

What other advice do I have?

From a cost perspective, the unattended bots are going to be a major saving for us. We have a lot of mundane, routine tasks that need to be done. I have not done very much with the attended bots, so I'm not sure how we might benefit from using them.

My advice to anybody who is implementing this solution is that knowing what it is you want to automate is the most important thing. We were kind of blind walking in on that. We had one process we looked at and now it's throughout our company. People have all kinds of ideas about what we can do with automation.

I would rate this solution an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
RA
Assistant VP of Robotics at Open Logix
Real User
Good scheduling, easy to follow code, improves efficiency, and has a good ROI

Pros and Cons

  • "The Orchestrator is great because you schedule it, and that's it, you don't have to worry about it."
  • "We had some issues with instability for which we were never able to determine the root cause."

What is our primary use case?

We are using the unattended robots and Orchestrator modules of UiPath.

We have built close to fifty processes in the three years that we have been a client. Our primary use case, the one the gives us the biggest relief, is the processing of premium border rows. The robot will pick up Excel files with between four hundred and a thousand rows of data, and then does the data entry into our policy issuance system.

All of our automation runs in a virtual environment and we do not have any problems. At the start, of course, there were a few bumps in the road, but we got it figured out and now have no issues at all using the VM.

When we began working with automation, I was the leader and I had three BAs and three developers offshore. When our company decentralized, we created three other robotics divisions. There are now twenty-eight of us including the project manager, the BAs, the testers, and our developers. People are spread across four different divisions within the corporation.

With respect to how easy it is to automate our company's processes, I will consider the individual components. With the Orchestrator, on a scale of one to five, that's easy, it's a five. It is very evident how to use it. The Studio, I am not a developer but I got six developers up and running on it in a very short period of time. It has a very short learning curve, so on a scale of one to five, I would rate it a four.

My rating of four is because I know that we had some challenges with using the recorder. Things would shift and there were a couple of things that had worked and then stopped working. We found a little instability, and it was hard for us to know whether it was us, or the application, or the studio. Ultimately, we were not able to get a final answer on the root cause of those problems.

We are no longer experiencing these problems. When we upgraded, a lot of that went away. Also, when we went to Orchestrator, a lot of that went away. Exactly as UiPath had told us when we went to them with the issue, they gave us some solutions and once we implemented them, the issue was corrected.

I did not attend the UiPath Academy, but my Business Analysts took the BA course and my offshore developers all took the Academy. On a scale of one to five, judging how beneficial it is, I would rate the training a five easily. Before the Academy came around, they were kind of self-taught. When they took the Academy, it closed some of their gaps.

When we started with this solution, we did a PoC with the help of a UiPath developer. In two weeks we built a PoC for a bank reconciliation, which was pretty fast. That helped us decide whether we wanted to go with the product, and of course, we did. After that, we took the code, which really didn't have a lot of bells and whistles in it, and we gave it to one of our developers to really soup it up and make it more robust. That took them about a month to do.

How has it helped my organization?

Orchestrator has given us a huge boost in terms of efficiency.

In addition to the resource-creating benefit that we get from this solution, it has given people the opportunity to move away from those mundane jobs and into something more challenging. Rather than sitting there doing data entry, they're able to move up, re-skill themselves, and add value to themselves as well as the organization.

We have been able to eliminate one hundred percent of human errors. We found that the robot was better than the human because when the human was doing some of the processes, they were supposed to be checking into another system. While testing our robot, we found that the robot's state was different from this other system that it's supposed to check against. We thought that the robot was wrong; however, we found out that the humans were eliminating that step. They were cutting corners. This stage of our development raised a flag to inefficiency on the human side.

In terms of the time that this solution saved, it equates to the equivalent of four full-time employees a year. At two thousand hours per year times four, that's a savings of eight thousand hours.

What is most valuable?

The Orchestrator is great because you schedule it, and that's it, you don't have to worry about it. It will tell you what passed and what failed if it had any issues. We don't have that dependency on someone needed to schedule tasks.

The code in Studio is easy to follow. I am not a developer, but I am able to read the code. When we have problems, the developer will display the script and I'm able to read it and follow it. Several times, I have been able to see where there was an error and the developer was able to fix it. It looks like it's easy to code.

What needs improvement?

We had some issues with instability for which we were never able to determine the root cause.

For how long have I used the solution?

We have been using this solution for three years.

What do I think about the stability of the solution?

On a scale of one to five, I would rate the stability of this solution a five.

How are customer service and technical support?

A UiPath consultant assisted us with our PoC, and the experience was incredible. They were really wonderful.

The technical support for this solution is excellent. They're very responsive and we never wait more than twenty-four hours for an answer. The developers have more contact with support than I do.

Which solution did I use previously and why did I switch?

We did not use another RPA solution prior to this one. Our former CFO went to a meeting where they were talking about robotics, and when he returned from the meeting we had a discussion about it. I was working in Internal Audit at the time, and with his prompting, I left Internal Audit to head up the robotics process. From there, it just took off.

What about the implementation team?

The initial setup of this solution was straightforward. To me, it just made sense.

What was our ROI?

In our first year, the development was a little bumpy, which is to be expected. I would say that it was fourteen to fifteen months before we hit a smooth path. Even with that, things go smoothly for a while until you start doing more challenging and more complex things, then you're back to a crazy path, then you correct yourself and things go smoothly again.

One of the issues is bad user requirements. Simply put, we don't know what we don't know, and we're dependent on the business to tell us. Even if you ask the same question in a variety of ways, if the business can't articulate it or tell you about it, then we can't build for it. Getting the right user requirements was our biggest challenge.

After that, we were trying to build for everything, instead of just building for the straight path. Trying to build in all of the exceptions and allow room for an imperfect world is what took us down. We've since learned that we're going to build for the straight path, and then look at the exceptions as we start to gather data on them. When we find exceptions that occur at a high frequency then we'll build for that. Failing is fine, and it is expected, as long as you can learn from it. Our approach is based on what we have learned from our mistakes.

From just one of our four divisions, A&H, we saved approximately $390,000 USD. You can multiply that to include the other three divisions (Estimate: $1.5 Million Dollars).

This past July, I completed a cost-benefit analysis and we determined that in the three-plus years that we have been using UiPath, we created the capacity to the equivalent of four full-time employees and have cost-avoidance in that we didn't have to hire five other employees. This is where the value is helping us utilize resources better.

Overall, we are giving ourselves a two year ROI.

Which other solutions did I evaluate?

We did not evaluate options from other vendors.

We went to Swiss RE because they offered to show us what they were doing. We saw their process and we were impressed by it, and it was a pretty nominal cost to buy the package. We thought, instead of wasting time, which could take months, and management wanted us to hit the ground running, we would try it. If we didn't like it then it wasn't a big loss of money. So, we totally circumvented the traditional route of purchasing and we are happy that we made the right decision.

What other advice do I have?

From what I have seen recently, I'm excited to try the Community and start building my own robots because it just looks like it's gotten a lot easier.

I am looking forward to one of the upcoming options, the dashboard. It will give us the productivity of the robot, which is something that I do myself right now. I record everything on each robot that runs and we keep metrics on it. These include how long it took to run, how many transactions it processed, and what the error rate is. Then I have to figure out ROI. So, the dashboard is huge and at the top of my list of things that I want to see.

We have a process for obtaining the right requirements for someone to follow. We go and observe the business and we record the process. That way, when we have to sit down and write the requirements, we can refer to the video and don't have to keep going back to the business because that is going to annoy them. We include the video when we send it to our developers and that way they have a visual for it, as well. When we put together formal documentation we show screen prints of where to click. After doing it a couple of times, one of our developers had this great idea to make things configurable so that we're not hardcoding a lot of stuff in there. With that configuration file, we just keep improving.

From a cost perspective, I can't speak to the advantages of attended robots because we do not have any. When I look up the pre-automation cost of doing a process versus post-automation, we give ourselves a two year ROI. We're not going to automate everything immediately, so we give ourselves a two year ROI and if it's going to be a positive ROI, we'll go with it. Of course, based on what it is, we'll prioritize. If it's a nominal ROI it will probably go to the bottom of our pipeline, but that's what we do when trying to evaluate initiatives.

My advice to anybody who is researching this type of solution is to try UiPath. Use the free version. I have a friend who does this as well, and I encouraged him to use the free download and do something simple. After it worked, they would up going with the product. With respect to the cost, you're going to recognize the savings immediately for the cost of the tool.

We are very pleased with this product.

I would rate this solution a ten out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Jack McBride
CEO at OnQ
Real User
Easy to develop automations that save us time on manual processes, making us more efficient

Pros and Cons

  • "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."

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
FP
Process Specialist at Biffa Waste Services
Real User
Easy to deploy and has a helpful Studio

What is our primary use case?

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

How has it helped my organization?

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

What is most valuable?

The most valuable feature of this solution is the Studio.

What needs improvement?

Additional help with ROM and approach would be an improvement.

For how long have I used the solution?

We have been using this solution for six months.

What is our primary use case?

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

How has it helped my organization?

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

What is most valuable?

The most valuable feature of this solution is the Studio.

What needs improvement?

Additional help with ROM and approach would be an improvement.

For how long have I used the solution?

We have been using this solution for six months.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
reviewer1180599
User
Real User
Increased speed and accuracy for invoicing, but the accuracy depended on using native PDFs

What is our primary use case?

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

How has it helped my organization?

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

What is most valuable?

The most valuable feature of this solution is capturing information.

What needs improvement?

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.

For how long have I used the solution?

I have been using this solution for six months.

What is our primary use case?

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

How has it helped my organization?

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

What is most valuable?

The most valuable feature of this solution is capturing information.

What needs improvement?

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.

For how long have I used the solution?

I have been using this solution for six months.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
reviewer1053186
User
Real User
The OCR feature is the most valuable for processing PDFs, images and the Citrix environment

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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

What needs improvement?

LINQ and Lambda expressions…

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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

What needs improvement?

LINQ and Lambda expressions should be included fully.

For how long have I used the solution?

I was using from last 2+ years
Disclosure: I am a real user, and this review is based on my own experience and opinions.
ITCS user
Head Consultant at Delosevrve Technologies Ltd
Real User
Turnaround time for claims payment has been reduced

What is our primary use case?

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

How has it helped my organization?

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.

What is most valuable?

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

What needs improvement?

Optical character recognition for hand written documents could be improved.

For how long have I used the solution?

15 months.

What is our primary use case?

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

How has it helped my organization?

  • 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.

What is most valuable?

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

What needs improvement?

Optical character recognition for hand written documents could be improved.

For how long have I used the solution?

15 months.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
it_user1142991
Senior Technical Consultant at Brillio
Real User
Easy to use and has increased our productivity

What is our primary use case?

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

How has it helped my organization?

This solution has increased productivity in our organization.

What is most valuable?

The most valuable feature is its ease of use.

What needs improvement?

Better alignment of workflows for development is needed.

For how long have I used the solution?

Evaluation period.

What is our primary use case?

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

How has it helped my organization?

This solution has increased productivity in our organization.

What is most valuable?

The most valuable feature is its ease of use.

What needs improvement?

Better alignment of workflows for development is needed.

For how long have I used the solution?

Evaluation period.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Pravinraj Vincent, PSM
Technology Specialist at Cognizant
Real User
Easy to automate for people without any programming knowledge
UiPath is the best tool for Robotics process Automation(RPA) compared to other tools because for people who don't have any knowledge of programming can automate simple processes easily. It needs to be improved in the workflow debug. Currently it does not allow to modify the values in the variables. It would be better if it is allowed. I would like to see this in the future releases.

UiPath is the best tool for Robotics process Automation(RPA) compared to other tools because for people who don't have any knowledge of programming can automate simple processes easily.

It needs to be improved in the workflow debug. Currently it does not allow to modify the values in the variables. It would be better if it is allowed. I would like to see this in the future releases.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Birinder Singh
Founder | RPA Solution Architect at Auxiliobits Technologies
Real User
A feature-rich solution with strong community support

Pros and Cons

  • "The OCR feature is very handy to extract structured and semi-structured data from documents."
  • "Extending the UiPath studio in terms of UI and functionality would improve this solution."

What is our primary use case?

We use this solution for automating manufacturing processes from invoice processing to accounts payables. All of these use cases are solved using UiPath. For insurance sectors, reconciliation is another process that is automated using UiPath. I have been using UiPath at various enterprise levels.

How has it helped my organization?

We provide professional services around RPA and UiPath, and we have certified developers in-house. I have helped many organizations to set up their Center Of Excellence in a hybrid model, wherein the stakeholders and developers are shared in-house and with our company.

What is most valuable?

UiPath is rich in features. The OCR feature is very handy to extract structured and semi-structured data from documents. A rich set of activities and an open platform is pretty helpful in creating solutions out of the box. The community forum is quite helpful in solving issues when they appear.

What needs improvement?

I would want UiPath to build as many activities as possible. The new machine learning activities in the UiPath AI fabric is something I am looking up to. There are many focused sets of activities and the ability to build custom activities is a great feature and can be made richer.

Extending the UiPath studio in terms of UI and functionality would improve this solution. This relates to adding hooks to the workflow/activity execution and extending the UiPath Studio UI with more functionality like a handy tool for activities with icons etc.

The orchestrator also can have set of APIs to work with.

For how long have I used the solution?

One year.

Which solution did I use previously and why did I switch?

We did not use another solution prior to this one.

What's my experience with pricing, setup cost, and licensing?

This solution has a very competitive and flexible pricing scheme that depends on the process complexity.

Which other solutions did I evaluate?

I evaluated AutomationEdge and Thoughtonomy.

Disclosure: My company has a business relationship with this vendor other than being a customer: Auxiliobits Technologies www.auxiliobits.com is a Business Partner of UiPath and have been involved in RPA projects.
Saif Ul Islam Khan
Sr Managing Consultant at Abacus Consulting
Consultant
Leaderboard
There is no coding required to implement a complex business process

Pros and Cons

  • "There is no coding at all required to implement a complex business process. If you have some programming background, it will help you. However, if you are a business user, you can still develop simple processes."
  • "The automated recording helps quite a bit. You record a complete business process along with human interactions to the desktop or web application. You can easily manipulate them. Once you are done, you have a complete recording of the interactions, which you can use to tweak your requirements."
  • "Tech support takes time replying to queries. It should be improved."
  • "You can't write small snippets of code. If you want to do a single code snippet, this is not available by default."

What is our primary use case?

UiPath is best at its core and with the help of plugins from UiPath and community you get solutions to a lot of problems out of the box. I have tried couple of more platforms, but the easiness, diversity and flexibility that UiPath provides is unparalleled. 

In the recent top 50 enterprise application at g2crowd, UiPath is at 18th place and topmost in the automation platforms. 

I have done quite a lot of different real-time projects with UiPath. In one big project, there was a lot of loan applications from scanned documents. We used Abbyy Flexicapture for reading OCR and ICR text and we read it very accurately. It really boosted the moral and now we are automating the whole CAD department of the bank. 

Now we are looking forward to more complex processes and try using the ML and AI into it.

How has it helped my organization?

RPA is our bread and butter. We have implemented projects in the telecom and financial industries. 

A good example was when we implemented a network process in the telecom sector. The time for that process was seven minutes, then by implementing the RPA, we drastically reduced it to 40 seconds. The process involved worked on four different applications. Each application required a secure login, and the speed was due to the websites being hosted on the Internet. It did not require any internet connection when we implemented RPA on-premise, and used complete network and system resources.

What is most valuable?

  • The ease of the processes
  • There is no coding at all required to implement a complex business process. If you have some programming background, it will help you. However, if you are a business user, you can still develop simple processes.
  • The automated recording helps quite a bit. You record a complete business process along with human interactions to the desktop or web application. You can easily manipulate them. Once you are done, you have a complete recording of the interactions, which you can use to tweak your requirements.

What needs improvement?

You can't write small snippets of code. If you want to do a single code snippet, this is not available by default. For example, if I want to do some date conversions, and that date conversion requires different variables to be available in the context, but they are not there. A small snippet of code change should be available out-of-the-box. This will help me in the long run. I can create activity out of it. Support for a little bit of in-line script should be there.

For how long have I used the solution?

One to three years.

What do I think about the stability of the solution?

There aren't stability issues, though it should have better RAM and cores. When it's overloaded you get considerable problems.

What do I think about the scalability of the solution?

Scalability is one bit which should be properly planned at the time of license and planning. For tight budget projects, you have to be very precise in the runtime execution requirements otherwise, you might face issues.  

How are customer service and technical support?

Tech support takes time replying to queries. The more you go to the community, the more likely you will get replies. Therefore, tech support should be improved.

How was the initial setup?

The initial setup was very straightforward. We were up and running in approximately 15 minutes. UiPath is the best of breed in the market for setup.

What's my experience with pricing, setup cost, and licensing?

Licensing is one of the big issues when I have been doing some pre-sale activities. One robot price licensing is quite high with UiPath. They should provide some discounts to partners so we can spread the product easily in countries, like Pakistan and other areas in the Middle East. Licensing should be reduced and price should be cut down a bit.

Which other solutions did I evaluate?

We also evaluated Blue Prism. We went UiPath due to the community support.

What other advice do I have?

It has a lot of community support with a lot of help available. It is a very mature tool.

The academy for UiPath is very good place to start with UiPath. It is easy and the learning curve is quite low.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Kalyan Appana
User
Real User
Easy to centralize task automation and management

Pros and Cons

  • "The UiPath Orchestrator is one source to easily manage all bots."
  • "I would like to see all a full-featured version for mobile devices."

What is our primary use case?

Our primary use case is to develop automation projects, like automating Excel activities for repetitive tasks and operations on files. We also automate operations on Citrix. With UiPath we can easily manage all of the projects in a single page (i.e. in orchestrator).

How has it helped my organization?

We have used this product to implement automation for several things, including:

  • UI automation that updates a project's status based on conditions
  • Gathering data from web sites
  • Excel functions related to HR operations
  • File checks, to determine the validity
  • Python and .NET scripts to connect to different databases

What is most valuable?

The most valuable features are Activities, Orchestrator, and UiPath Go!

The UiPath Orchestrator is one source to easily manage all bots.

What needs improvement?

I would like to see all a full-featured version for mobile devices.

In some Activities, there are inconsistencies between versions where the most recent does not have support for throwing the same kinds of errors.

For how long have I used the solution?

One year.

What do I think about the stability of the solution?

What do I think about the scalability of the solution?

How are customer service and technical support?

The support from the community, as well as from UiPath themselves, is awesome. Also, users have the advantage of training videos and material, including free certifications.

Which solution did I use previously and why did I switch?

We did not use another solution prior to this one.

What's my experience with pricing, setup cost, and licensing?

This solution is priced less compared with other products.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Jaideep Gangui
Co-Founder and Oracle Fusion Middleware Architect at Fusion Applied
Real User
It has good Academy content and an open platform, which is easy to download and start using

Pros and Cons

  • "The eagerness of UiPath engineers and their salespeople to help us along the process has helped us align ourselves more with UiPath."
  • "The initial setup is quite easy. We have worked with some other RPA tools, but they took us quite awhile to get setup. With UiPath, it was relatively easier to get started."
  • "I would like to see higher end AI type features natively in UiPath. Some native integration over time would help."
  • "UiPath could use more OCR use cases to help with those features."

What is our primary use case?

The primary use case is invoicing and billing. The first thing that we used it for was some content migration from one video hosting provider to another. We later on moved to invoicing and billing, which included time sheets, management, and feeding data into our accounting system.

What is most valuable?

The features that we use the most for our use case include reading PDFs, email integration, and web and desktop automation talking to other desktop software.

We have generally found it easy to use, but we also develop some extensions. We are actually a software development shop, so we have developed extensions to the core UiPath platform. They have made it pretty easy to do that.

What needs improvement?

UiPath could use more OCR use cases to help with those features.

I would like to see higher end AI type features natively in UiPath. Some native integration over time would help.

For how long have I used the solution?

I started with this solution a couple years back.

What do I think about the stability of the solution?

We found it to be quite stable.

What do I think about the scalability of the solution?

We have a relatively small use case. Most people have entered the market on a small scale. The maturity will come in, maybe over this year, as people start to scale up. 

I expect some issues will surface when it starts scaling up. However, that happens with any software. 

How are customer service and technical support?

The eagerness of UiPath engineers and their salespeople to help us along the process has helped us align ourselves more with UiPath.

Support is good, helpful, and eager to help.

Which solution did I use previously and why did I switch?

The UiPath Academy is great. It was one of the reasons which made us choose the tool, and align ourselves with it. It was easy to get the software, and train on it. If you're doing professional work, you don't want to have untrained people work on it. This will not lead to success.

As a software development shop, we value training quite a lot. They made it easy to help our developers come up to speed with the software and get certified.

How was the initial setup?

The initial setup is quite easy. We have worked with some other RPA tools, but they took us quite awhile to get setup. With UiPath, it was relatively easier to get started.

What was our ROI?

We have seen ROI by it saving some hours for us. We are a small company. We use the tool mostly because we want to learn about the software. We also save some hours, but we do it to learn and help other customers who are doing it at much higher volumes. The savings for us is relatively lesser than the savings for a larger customer.

ROI is a bit tricky. Customers need to implement simpler use cases: Get ROI from the tool, learn it, and re-implement it. This is just the nature of how RPA works. I see a lot of opportunities for it.

When customers start scaling up their use of RPA and have learnt how to use it, that is when the real ROI will start trickling in. When you start off, it will take some effort to get it right. Once you developed some maturity with the process, and you're scaling up a lot of use cases, and you have one bot doing a lot of different things and being able to share a lot of processes with a few bots, that's when you will start seeing good ROI.

This tool gives opportunities for people to be productive in other areas, which is hard to measure sometimes. The first step is to get them there, then determine where you can go from there. ROI is a very long term thing. The product lets people focus their skills on what they are good at, which is a type of ROI.

Which other solutions did I evaluate?

UiPath made it easy to learn their software. When we looked at a variety of RPA tools initially, UiPath was the easiest to get started with. It has good Academy content and an open platform, which is easy to download and start using (the Community Edition).

We have been looking at other RPA solutions, but we like UiPath quite a lot.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
MC
Tech Lead in RPA Offerings at Perspecta
Real User
The initial setup is simple. Once you install Studio, you can do the development within minutes.

Pros and Cons

  • "Screen scraping credentials of whatever features that it has. The robot can log into the system, scrape the data, and enter the data into the system. This eliminates a lot of the manual work that the team had to do, which has improved the performance. Our teams used to do a lot of data entry, and this repetitive work has been reduced. The same resource can now work on some high-end work."
  • "Stability looks good except that we see that when we run the bot sometimes somewhere in the middle it fails. It will recovers, but I don't know why and can't answer to my customers why. I don't know if something can be done to eliminate the failing piece. I don't know whether it is a stability issue, but it should be handled in future."

What is our primary use case?

We are using it for financial applications in the financial sector. We also have a couple of bigger federal customers who started RPA development on their own, then needed our help. 

Internally, the RPA offerings team is developing more resources, so we can support all our customers. This involves a lot Pegasystems, ERP, and homegrown systems.

How has it helped my organization?

We are really seeing that RPA in the production, where people are using it, they are getting benefit.

What is most valuable?

Screen scraping credentials of whatever features that it has. The robot can log into the system, scrape the data, and enter the data into the system. This eliminates a lot of the manual work that the team had to do, which has improved the performance. Our teams used to do a lot of data entry, and this repetitive work has been reduced. The same resource can now work on some high-end work.

The ease of the use is good and exceeded my expectations. The implementation became easier and more standardized. Also, our development time has been reduced. Using ReFrameWork, we saw that the code become organized very nicely by UiPath and the implementation became easier and more standardized with more prebuilt components, which reduced development time. If you load the ReFrameWork nicely, you can do things faster and more standardized.

What needs improvement?

I have found there to be setup issues with Chrome. Right now, I am using IE.

I am looking for more batching processing because of the ODI framework. While they have a process where they log everything into Orchestrator, then they process it. However, when I have 50,000 to 100,000 records being batch loaded and processed one-by-one Orchestrator, I am apprehensive about it.

What do I think about the stability of the solution?

Stability looks good except that we see that when we run the bot sometimes somewhere in the middle it fails. It will recovers, but I don't know why and can't answer to my customers why. I don't know if something can be done to eliminate the failing piece. I don't know whether it is a stability issue, but it should be handled in future. Other than that, stability looks great.

What do I think about the scalability of the solution?

If you start using Orchestrator, and you put your Orchestrator on a very high-end machine, it can handle thousands of bots. I don't see any issues with running multiple processes on a single bot, then connecting it to Orchestrator.

How are customer service and technical support?

Before using UiPath Academy, we used the customer support to answer our initial questions.

Which solution did I use previously and why did I switch?

This automation is not exactly like other automation that we used to do. This is a different type of automation where we are not disrupting the existing codes. We are providing all these features to the customer.

How was the initial setup?

The initial setup is simple. Once you install Studio, you can do the development within minutes.

What was our ROI?

Once the bot is programmed, it eliminates human error. It doesn't make any mistakes if you have programmed it correctly.

Which other solutions did I evaluate?

Right now, we are not working with other vendors.

What other advice do I have?

I would recommend UiPath and its bots.

Most of our work is with unattended bots. People are more keen to work with unattended bots because they just want to schedule it somewhere in the night and let the bot run, then come in the morning and have it ready.

Everyone in our organization has used the UiPath Academy. We are certified in it. There are three levels of training, which we had to go through before the final certification. The Academy is very good and well-organized. We went through it step-by-step.

One of team members developed a bot in a Citrix environment for a project, and it looked great. From his machine, he connected to Citrix, logged into the application, did some data scraping, and built an Excel file, then provided the data.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
KamranKhan
VP Strategy at Interimage
Real User
The ease of use and implementation together are a huge value-add and time saver to any organization

Pros and Cons

  • "It took us only about two days of man-hours to build it out. Thus, it is easily implemented, programmed, and deployed. The ease of use and implementation together are a huge value-add and time saver to any organization."
  • "I would like more defined processes for around use cases. This might be helpful, as it is more general at the moment."

What is our primary use case?

Our primary use case for it right now is in human resources. We are using it as a recruiting capability where we receive resumes in from recruiters, one in particular. Then, we're looking at the emails, pulling data off the resumes, and loading it into a database. We are also identifying resumes which might need some additional clarification. This saves a lot of time, so somebody doesn't have to go through each email, evaluate them, and pull the resumes down.

Our customers are the DoD, mostly, and some civilian agencies.

What is most valuable?

  • The ability to integrate easily within our IT environment.
  • The ease in which we are able to program and tie it into our various applications.

What needs improvement?

I would like more defined processes for around use cases. This might be helpful, as it is more general at the moment.

What do I think about the stability of the solution?

We have not experienced a whole lot of issues with UiPath at all internally. 

In some of the pilots that we are developing for our partners or for our customers, we haven't seen any major big issues or bugs.

What do I think about the scalability of the solution?

We are still in the initial phases of deploying different bots, one bot at a time. Once we get into the Orchestrator area, we are looking at more of shared, multiple Unattended bot deployments. Then, we will have a better feel for it.

How are customer service and technical support?

The support has been excellent and very helpful. We have received a lot of great information and assistance from the UiPath engineers and partner alliance people, who has been very helpful and responsive.

How was the initial setup?

It took us only about two days of man-hours to build it out. Thus, it is easily implemented, programmed, and deployed. The ease of use and implementation together are a huge value-add and time saver to any organization. 

The ease of use did exceed our expectations. We heard it was easy. We had been trained up and had certified people. However, this was our first endeavor, in terms of deploying it internally, and it went extremely well. 

What was our ROI?

We have seen a huge benefit time-wise, in terms of the repetitive type of activities that we do. Now, we have automated those and can do the more hardcore analysis of the resumes. In the human resources area, it would take 27 minutes to process 20 emails. With UiPath, we are doing it in about two minutes, which is a huge time savings.

What's my experience with pricing, setup cost, and licensing?

Given how cheap it is to initially buy the product, the licensing methodology that they have in terms of renewing every year is appropriate. Later on, if they start charging more early on, for deployment, buying the license, and deploying it initially, then having a lower maintenance fee might be more appropriate. Now, with the scale they are at, it is an appropriate way to do the licensing.

Which other solutions did I evaluate?

We are a partner. We are totally onboard with UiPath. We did not look into different partners to use as a product internally.

It is the market leader, particularly in the federal government. It is getting the widest use right now.

What other advice do I have?

The product is extremely helpful. In terms of usability, capability, and functionality, it's one of the best products that we have used in terms of being easily implementable and cost-effective.

We find that all the materials out there for partner use are extremely effective and organized extremely well. They are very detailed and helpful.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Richard Autry
Consultant RPA Developer at a tech company with 10,001+ employees
Consultant
The integration with third-party vendors built into the product speeds up our development

Pros and Cons

  • "Ease of use and speed of development are the most valuable features."
  • "Some of the transitions from the forum to submitting a ticket are a little clunky. If a ticket could be submitted on my behalf on the forum, then have me boot over to where the ticket is, that is fine. Just kicking me out of the forum, then having me submit a ticket seems counterintuitive to me."

What is our primary use case?

Internally, we use UiPath to automate financial transactions, specifically for invoice processing.

Externally, on the client side, we use automation in the financial space, primarily. There are various use cases from generic file uploads to transaction processing that we implement for our clients.

How has it helped my organization?

We have some processes that haven't been completed flushed out. Right now, there has not been an exact improvement yet.

What is most valuable?

Ease of use and speed of development are the most valuable features. 

The overall integration with Microsoft stack and a few other third party vendors, like Google, are very useful to us. Having these built into the product speeds up our development, so we don't have to code a bunch of connectors on our own.

What needs improvement?

I would like to see some sort of better implementation of the Python modules. Right now, any error code that Python throws up turns into a generic error that is difficult to track down. I would want to see some sort of integration that at least lets me debug the issue.

Its pretty difficult to do source control through the typical Git functions because of the nature of the UiPath and the visual element. Some sort of method to bring source control home for us would be very helpful. A way to systematically track which actions or activities were added and subtracted from a given process before adding to a repository would be very helpful to us right now. Our team of developers is growing, so control has become somewhat of an issue for us.

For how long have I used the solution?

We are still very much in a prototyping phase and don't have full development.

What do I think about the stability of the solution?

Ease of use has definitely exceeded expectations. Initially coming in, UiPath had some features that needed to be implemented that weren't quite there yet. Now, we are on 2018.4 and all of the features that we desperately needed are there. Thus, ease of use has been pretty great.

What do I think about the scalability of the solution?

We have looked into scalability a lot. So far, we haven't done anything that involves a 100 bot. However, the scalability seems pretty easy. Scaling up to just five bots running in parallel has been very easy.

If we are going to build up the environment, we would run on virtual machines. We would connect through Remote Desktop Services, not through Citrix.

How are customer service and technical support?

The technical support has been fairly good. I like that they pick up on interactions in the forum. However, some of the transitions from the forum to submitting a ticket are a little clunky. If a ticket could be submitted on my behalf on the forum, then have me boot over to where the ticket is, that is fine. Just kicking me out of the forum, then having me submit a ticket seems counterintuitive to me.

Which solution did I use previously and why did I switch?

As a company and for our client, we see any sort of legacy system or too many individual systems as somehow needing to be integrated. This is the bread and butter for RPA, and where we started our conversation (and our clients' conversations).

How was the initial setup?

The complexity of the initial setup depends on who you are. First time implementing, it seems a little complex. If you know how to develop UiPath, it is more straightforward. I had to walk somebody through the implementation setup of the environment because they had a lot of questions about where they were going. For software development is not that complex, it is pretty straightforward.

Having some understanding of database management and services is helpful, so you understand the inner workings of UiPath.

What was our ROI?

It has definitely eliminated human error in our internal process, somewhere between full production, deployment and testing. There were definitely some error prone tasks that we eliminated. If I had to give a ball park, maybe 10 to 20 percent of the process was error prone, which we were able to resolve with UiPath.

For time savings: What used to be a 15 minute task, now it takes the bot two minutes for the bot to run through, for example.

What's my experience with pricing, setup cost, and licensing?

Generally, we push unattended. We think the cost savings is better with unattended. As far as ROI, when you are talking about returning man-hours or moving people off work, unattended does that efficiently. Attended doesn't always save much time. Thus, we push unattended for cost.

Which other solutions did I evaluate?

We have seen general platform survey before implementing RPA of the different market vendors.

Personally, I looked at other platforms, and it is hard to transition from UiPath. It does have ease of use that now I am used to.

What other advice do I have?

If you are starting with development, start with the UiPath Academy. For the end user or client, start conversations about security and prevention now, while you get trained up on development.

Internally, there is not a lot of automation in place. We are using a good robotic process automation software to bridge that gap right now and get us further down the automation road. 

We use the UiPath Academy for new hires. The new training programs, both the previous and current versions, with the UiPath Academy work out for us. I have the previous videos, then the current new slide deck idea. It is pretty streamlined and high level, but it is good for getting new people started.

Also, I used Academy just last week. I used it for security because I had some knowledge gaps on security with UiPath.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Thomas McEvoy
Lead Associate at Booz Allen Hamilton Holding
Real User
Unattended bots see ROI immediately since they remove workers from the tasks completely

Pros and Cons

  • "The most valuable features are the unattended bots. Initially, we are going to be looking at a number of attended bots in a pilot phase for our HR internal operations personnel. We are going to come in and try to remove tasks from their daily lives, such as ten minute tasks brought down to five seconds, or we could just completely eliminate them, making them unattended."
  • "I would like to see a UiPath user group to discuss issues. I am unaware of all the activities and features, and this would help. Right now, there is just the user's guide and UiPath GO! It would be great if this feedback went back to the UiPath development team. We should also be notified of new features through an alerting system on UiPath GO!"

What is our primary use case?

It is looking externally at how we can enable the government to identify efficiencies and improve effectiveness. The other is, internally, how can we drive efficiencies within HR and finance, with everything that a big corporation can do. 

  1. How do we help the government realize these benefits? 
  2. How do we help our internal workforce benefit?

It is two different things, and they are similar, but they're not the same thing.

A lot of people externally are worried about the elimination of jobs, but at the same time, they still want that efficiency, and they are looking for it. We want to drive the effectiveness of the workforce, whomever we're working with. 

There are plenty of automation opportunities out there: DoD, the federal government, and commercial space. There are all sorts of stuff that we can do. Internally, we feel the same way. There are lot of things that we can do to make ourselves run more efficiently. If we are preaching to the government that they need to be using this, it's beneficial for us to say, "This is what we have done as a company."

Our company is 25,000 people across the globe. There are certain opportunities for us to include automation in what we do every day. We are doing it now by instituting RPA, specifically, and the tools that the UiPath bring to the table. It will be a game changer for us, if we can get it done at scale.

Automation is growing at our company. A lot of what we do is focused on AI. Going from zero to AI is a Herculean task. It's extremely difficult. However, there are many steps in-between zero and AI that we can do now to help realize the benefit to the company or the federal government, such as the benefits of the efficiencies that we can identify. That intermediate, non-threatening first step can be RPA, which ultimately will lead to enabling AI, but is not AI. 

Within our company, we are looking to identify what those pre-AI steps are, with the goal in mind that we know that the federal government is asking for AI. What we do in the interim is a type of level set, where you can build an algorithm, AI, or machine learning algorithm. This ultimately is what they want, but what they need right now is to aggregate their data in a structured way to be able to feed into those algorithms. That's step one. This is the first step to getting all your data right. It's not easy, because you have to take people out of the mindset of AI.

How has it helped my organization?

A lot of times, in the government, people say, "I'm wearing two hats." It's an idiom. The question I have in response is, "What if we could take one of those hats away?" We can take one of those responsibilities that someone finds cumbersome, or annoying, and remove that from their task list. We have them tell us the steps of their process, so we can automate it, if not pieces, but all of it. That is our starting point with a lot of people, "We can take this off your plate," which is definitely exciting for a lot of people. It scares some people too, but we're working on that.

What is most valuable?

The most valuable features are the unattended bots. Initially, we are going to be looking at a number of attended bots in a pilot phase for our HR internal operations personnel. We are going to come in and try to remove tasks from their daily lives, such as ten minute tasks brought down to five seconds, or we could just completely eliminate them, making them unattended.

The training and certification online is very helpful.

The software is easy to use, as a drag and drop function. Even if it wasn't, the type of support that we get from the people who work for UiPath is paramount to the capability of the tool. The ease of use has exceeded our expectations.

What needs improvement?

The Academy Live that I took was only a half a day course. There needs to be diverse set of courses for those introduced to RPA for the first time. There are different people who show up to this course: 

  • The developer who is interested in automation and automating different facets of the tasks that they have, either at work or for their clients. 
  • Business managers who want to know more about what RPA can do for my business or company. They want the operational and strategic level versus the tactical level of how do I get automation to do the thing I want it to do?

The course was only a half a day, and although we were able to provide two automations and build two bots, it would be helpful if that was extended to include the RPA story and pitch. E.g., What's the story that we need to tell in order to get people to say, "How do I get into the pilot phase now."

I would like to have the course do an introduction, "Welcome to the course. This is what RPA is. Now, let us build your first bot." 

The sales elements of why RPA should be there too:

  • What is the value proposition that RPA brings to the table.
  • Here is the expected ROI for a menial task, saving an hour a week equals this in the long term. Even if you can cut a 25 minute task out of somebody's daily routine, this is the benefit in the long term.

That wasn't there as much. I wasn't really expecting it to be there, but in the long term, if there are a number of different types of training courses which are offered, people will have different breadths of understandings of RPA can really do, e.g., it needs a hardcore developing training and a capture manager. It needs to explain what sort of things a capture manager needs to know. Maybe not necessarily how to develop the architecture for it, but what does that even mean? For example, how easy is it for me to get Orchestrator onto a server? How do I become a reseller of the software? These are the capture manager responsibilities, and it would be helpful if they were explained. While this is probably more of a day two of a training rather than day one. 

I would like to see a UiPath user group to discuss issues. I am unaware of all the activities and features, and this would help. Right now, there is just the user's guide and UiPath GO! It would be great if this feedback went back to the UiPath development team. We should also be notified of new features through an alerting system on UiPath GO!

What do I think about the scalability of the solution?

With our focus on the federal government, they're looking at dozens of bots: Scaling of five instances of Studio, 10 bots of Orchestrator, and three unattended bots. That is far easier to scale than in the commercial world, where they are asking for 1000 instances of Studio and 500 unattended bots, touching 100 different processes. We haven't had that experience yet.

How are customer service and technical support?

The current staff at UiPath won't let you fail (the customer support and customer success managers). They are not going to leave you hanging.

They are an honest broker. They told us when things aren't going to work. They've been upfront and transparent about everything with us.

How was the initial setup?

Our developers have found that it is relatively straightforward. With any installation issues that have come up, we have always had somebody just be able to pick up the phone and call.

What was our ROI?

ROI depends on the complexity the project. Unattended bots tend to see ROI immediately, where attended bots take longer. The savings starts as soon as a bot is deployed.

What's my experience with pricing, setup cost, and licensing?

Getting licenses has been relatively easy.

We have all the prices for the software. Every project is up for a negotiation on how it's going to be done. A lot of times, with the federal government, it will be necessary to put it on contract. When we are bidding for something, we need to know, how many bots are we talking about? The tricky part is when the government is unsure what they actually want. A lot of times when contracts or proposals are put on the street, the government wants something that can support 100 bots. That's not really helpful given that the price points for unattended and attended are different. So, clarification is often necessary when we're asking, what ratio of attended to unattended are you really asking for?

There is some initial sticker shock from a lot of people regarding cost, until you show them what the actual benefit is. Initially, people are just going, "Why?" So, the retort for that is, "Look how much you will save, time, and budget-wise with one bot. If one bot costs X, this is how much it will save you over one year. This alleviates the "Oh my gosh" face, when it's 1200 dollars for a bot. 

Getting clients, and our own people internally, to recognize that this is an investment in efficiency to drive effectiveness. If you can do that, and you can get past any initial sticker shock, thinking strategically and long term, then you've got them. But if they say, "Look, my budget this year is only 10,000 dollars. Why would I put that into bots?" That becomes a different type of discussion. It's mostly focused on, you're thinking about today. We need you to be thinking about three years from now.

Which other solutions did I evaluate?

If you look around at the other software systems, we have chose to go with UiPath because of the ease of the interface and also the customer support that we get from their people. There are a lot of tools out there. The reason why we have gone with UiPath is because of the relationships that we have built and the type of success that we are going to get working with their account leads.

We looked at Blue Prism, Automation Anywhere, and briefly at a couple of the start ups. However, we figured that they didn't have the ATOs that we needed to go within the federal space. There are a lot of people who say they can do this, or they say that they have an offering that can do this. In many cases, that is absolutely true. We wanted to be with a company that we feel is up and coming and will be around in the next decade. We want to use software that is going to be recognized by the federal government as number one, or at least very close.

What other advice do I have?

Be prepared, because you are going to be asked a hundred question. This product takes a team. Your senior management needs to want this product and sign onto training. You will need developers capable of using the UiPath software.

UiPath is not just a technology business. It really comes down to a people business. The people and culture that UiPath provides us leads us to use their software more often.

The NextGen workforce is not going to be cutting and pasting for eight hours a day. That is not a function that a human should be doing anyway. Therefore, we treat RPA as a digital assistant, because who would not want a digital assistant.

People are finding ways to automate the reporting functions that Workday can really provide. This is not at an individual level. At the individual level, you can go in and check your benefits and check your 401K. However, at a macro level, we need people to run Workday reports pretty much daily, and that gets updated in the systems that we have. Therefore, our HR and finance people are all working with Workday, as people of incorporate these big management systems, trying to find new ways to automate them.

It is now on us and our team to be able to implement automation with the Workday, and have it work more efficiently. That will be our next challenge moving forward, automating Workday.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
MA
Web Developer at USDA
Real User
User friendly and can batch process a lot of the hands-on manual work that nobody wants to do

Pros and Cons

  • "It's accessible, but also has enough features for more hands-on developers to be able to do what they need to do. From the two that I've seen, it was the more user-friendly one."
  • "When you're nesting certain workflows, it can get a little complicated as you start getting deeper."

What is our primary use case?

At Forest Service, we have a massive onboarding season. Because our primary mission is to combat forest fires, we have a huge intake of firefighters that we hire every season. Because of that, there's a lot of onboarding material that needs to be processed through HR, literally tens of thousands of people in such a short amount of time. I can see, potentially, RPA being able to help with some of the manual work that we do.

It's probably the best bang for our buck, but there are certainly other use cases potentially. That is the area that I'm more familiar with, though.

How has it helped my organization?

UiPath can batch process a lot of the hands-on manual work that nobody wants to do. I think that's probably its best value. That said, it does kind of highlight the need for standardized processes, which can be challenging at times, specifically in our space. Just having formalized documentation about what the end-to-end process should be is key. Once that's standardized, then it's a lot easier to leverage UiPath for automation.

What is most valuable?

Having looked at other RPA software, I think UiPath is the most user-friendly. At the same time, it's robust enough to customize and get into the source code. It's accessible, but also has enough features for more hands-on developers to be able to do what they need to do. From the two that I've seen, it was the more user-friendly one.

I have used UiPath's Academy for some of the foundational level training, not the more advanced ones. I think I had some feedback at the time. It's been a few months since I've taken it. Overall it was pretty good.

What needs improvement?

I feel like it's pretty good as it is. One thing I would change is when you're nesting certain workflows, it can get a little complicated as you start getting deeper. For example, if you have multiple blocks that need to live inside each other, and you're using a library to drag stuff or just insert it, it can be very challenging from a visual level to see what level it's in or how deeply nested it is. It's hard to roll it up into a parent level display. So, that's a little confusing sometimes. I guess, if there's any way to improve that, I think that would be helpful.

I think UiPath uses VBScript. If there were some kind of library of common things that developers could use, that would be helpful, but it's not a big deal. You can just Google that stuff. Making something like that accessible would be nice, but I don't think it's crucial.

What do I think about the scalability of the solution?

The big question on my end is just how to scale and keep things stabilized. This is such a new technology for us, that there's a lot of questions around it. I think, being able to answer that would be helpful. I don't really know the answer.

How are customer service and technical support?

I don't know about technical support. We were talking to a developer that was helping us at the time just to walk us through. Our experience with the developer was good. They have a very knowledgeable staff. They're very eager to help us figure stuff out. All in all, it was a positive experience.

How was the initial setup?

The setup, at least from the local side, makes sense. This could be just more of my experience since my expertise in UiPath is not as high as it could be. I'm not super familiar with how Orchestrator is deployed and managed, in terms of multiple bots and scheduling, but that's probably a limitation more on my end then with UiPath.

What about the implementation team?

We are currently in the research stage. It's more like proof of concept work. Right now, it's really about convincing people that this is a technology to look at and pay attention to. We are trying to convince the people with the authority that this is a good way to invest.

I have local test environments that I've used personally. At Forest Service, they're very visually oriented. If you talk to them about it, they won't get it. They need to see it to believe it. So, I've been trying to do that locally in my own environment. I have been building use cases that I think are parallel to what we're trying to do, to demonstrate the value.

Which other solutions did I evaluate?

We looked at a couple of alternatives. Automation Anywhere was one of them. I haven't looked at the other ones, since we chose UiPath pretty early on, having heard about them previously. We also considered some others like Pega and a few others.

What other advice do I have?

Automation technology is non-existent in our company currently, but definitely something that should be leveraged for. I think there's a lot of value in being able to free up people from doing small repetitive tasks and just be more strategic focused. The challenge, really, is just convincing people that they're not going to lose their jobs. We need to show them that we're freeing up their time to be more valuable. The challenge is just educating people about what it actually is.

I would rate this solution as eight out of ten. I think it's going a lot of places. It's definitely more advanced than some of the other ones that I've seen. UiPath is probably the best one that we've seen so far.

My advice is to make sure you have your processes documented before you try to fix something that can't be fixed through robotic process automation. At a fundamental level, your organization needs to be ready for it. It's not a magic bullet to fix stuff that's confusing at your organization level. But, if you have it straight and documented and you're doing high volume amounts of it then you should use this to free up people's time and make them do better work. I think it would be useful.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
LB
Developer at a financial services firm with 5,001-10,000 employees
Real User
Enables people to do more value-added work and has accommodating technical support

Pros and Cons

  • "UiPath allows people to do more value-added work. I found that we were able to take a person well versed in access programming and convert them to be an RPA developer with relative ease."
  • "It was more difficult to use than we originally thought it was going to be. It's not as simple as drag and drop."

What is our primary use case?

We use UiPath to log into a system, run a report, extract the information from the report, and send emails to hundreds of people, all in just seconds.

How has it helped my organization?

We have a requirement when someone leaves the agency that you have to remove access immediately but that wasn't always done. This allows us the ability to take the daily report when people leave and send notifications to the right people to remove system access.

What is most valuable?

UiPath allows people to do more value-added work. I found that we were able to take a person well versed in access programming and convert them to be an RPA developer with relative ease.

The UiPath Academy RPA training is phenomenal. Just the fact that they offer that information is a huge selling point for them. I continually share links to the site and I encourage people to go out. I tell them to take the training if they want to learn more. I started the technical training, but I kind of oversee the program, so I didn't have to learn all of it. Nevertheless, just the awareness of what RPA is and those intro-functional courses were very informative.

What needs improvement?

It was more difficult to use than we originally thought it was going to be. It's not as simple as drag and drop. You really have to have a background in IT development type of work. I suppose you could make simple automations but we definitely found it to be more complex, especially the supporting infrastructure beneath it.

I think where the improvement needs to occur is within the federal government to put out the policy that it has been determined to be a safe product that can be put on any DoD network. That would be huge, but right now that decision isn't out there and every agency has to go out and make its own determination. Some CIOs are more risk-averse than others. That would be one thing, but obviously, UiPath doesn't have a way to influence that.

What do I think about the scalability of the solution?

We don't know about the scalability until we get in there. From everything I've read and heard, I think it will be scalable and should fulfill our needs.

How are customer service and technical support?

Technical support has been very accommodating. In fact, they'll be on site to help us overcome some of the challenges we've had without having third-party integration support. We've been struggling on our own, but UiPath has been there and has even agreed to come onsite to help work through some of these issues.

Which solution did I use previously and why did I switch?

We have automations everywhere through the agency. There were a lot of presentations being held. Senior leaders started to get wind of this and other organizations were sharing their successes and that kind of piqued our interest to assign somebody to explore it.

How was the initial setup?

The initial setup was complex. I've just seen the emails that go back and forth and I think if we had a third-party integrator, it would have resolved a lot of our questions. The security aspects have been our biggest challenge and concern.

What was our ROI?

We absolutely have a return on our investment. It gets difficult to really quantify what the ROI is when you start looking at that. Just the ability for technicians to do more value-added work is hard to put a price on. We have a system that stores a lot of documents. Our pilot bot was just to log into that system and download the documents for audit purposes. Now we can literally let the bot run for 12 hours pulling all the documents and those people can do more important things.

The pilot bot we set up to send those emails, equated to about 350 hours a year. The audit bot is almost endless because if we can share those bots with our customers and the customers can do the same thing and achieve those same benefits, you're getting into millions of potential dollar savings.

This solution has definitely helped to eliminate human errors, as well.

What's my experience with pricing, setup cost, and licensing?

It would be nice if you could just buy the product instead of having the annual rate license renewals. I assume that's how UiPath makes its money. It's expensive, but I guess we'll have to do the business case to see what the ROI truly is.

Which other solutions did I evaluate?

Automation Anywhere and Blue Prism were really the main competitors. The UiPath Academy, for one, was a big selling point. Other than that, just having conversations with other government agencies that have used UiPath and have succeeded in that development helped us make the decision to choose UiPath.

What other advice do I have?

We have hundreds and hundreds of IT technical specialists. We have very sensitive information that must be protected, which is IT's primary focus.

I would rate UiPath as nine out of ten, not a ten just because of the pricing.

My advice to someone starting out with UiPath is to get third-party integrator support.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
KevinBrown
Project Delivery Manager at Deloitte
Real User
Consolidates information and eliminates redundant manual tasks

Pros and Cons

  • "I think there's some scalability to UiPath that's going to make everything pretty convenient and easy to use."
  • "I would like a new feature like some sort of generic interface or input where other UiPath users can examine our product or our situations and help us fix them."

What is our primary use case?

We are using UiPath primarily for process automation. We are trying to consolidate information, eliminate redundant manual tasks, and save some money.

What is most valuable?

I'm developing my first bot, so I can't answer that yet. I've just got my UiPath certification, been thrust into a project which I'm pretty excited about. I don't know what our client is going to ask as of yet. Obviously, those parameters are probably going to change weekly, if not daily. I think there's some scalability to UiPath that's going to make everything pretty convenient and easy to use.

The tool is very simple, even for a layman like myself without a coding background. It's a gateway to the process automation industry. I think this is really the simplest and easiest way to do it.

I used the UiPath Academy and got a certification. It was very easy to use, they are very patient, but it's not automatic. They are very diverse and applications are necessary. The steps just take you all the way through. If you reach a stopping point, you can literally just start over. Then you can try again with another series of questions, some more accessibilities, or different paths towards the same outcome. I loved it. I thought it was pretty simple and pretty easy to use. It's very non-stressful.

Regarding automation, we serve the federal government here, so I'm working for a very specific division in my company. We're serving the client, so I don't even know how new and exciting this is going to be. This is going to be huge. I think we're right on the cusp of all of it. The sky's the limit.

What needs improvement?

Due to the sensitivity of my project, I would like a new feature like some sort of generic interface or input where other UiPath users can examine our product or our situations and help us fix them. Some sort of official UiPath community within, where everyone can kind of help each other out.

What do I think about the stability of the solution?

The stability is fine. The only factor we have is a finicky customer. We need to help them with their choices, changes, reversals, augmentations, but it seems to be pretty simple and intuitive so far.

How was the initial setup?

Our initial setup was pretty straightforward. We used it on a secure client-server, so there was no change from what I'd learned on my own and what I had to use in the work environment. It was pretty simple.

What was our ROI?

In as far as learning the product, it is almost free in its efficiency in teaching people like myself how to use it. With regards to the client, it's a little early yet, but they project incredible savings. One thing I should say about UiPath and process automation is that it's not an attempt to eliminate jobs. This is a huge misconception and stigma. It's an attempt to make working more efficient. In that respect, I think it'll save everyone a lot of money if they're willing to try it and implement it.

Which other solutions did I evaluate?

I've heard about some alternatives, but I haven't used them yet. UiPath is my first entrance into this. I really don't see the need to use anything else. The client likes it as well, so if they're happy with it, I have absolutely no desire to investigate anything else.

What other advice do I have?

I would rate this solution as a solid nine out of ten, just because I haven't used it very long. I'm probably going to give it a ten. I don't know what else UiPath can do for me, and I'm sure there's more.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Manisha Katram
Developer at Octo Consulting Group
Real User
Mitigates risks and eliminates tedious IT tasks

Pros and Cons

  • "It helps mitigate the risks. With traditional native active directory delegation, it becomes real messy, real fast. You lose oversight on who has access where. We are an acquisition merger company, so we let go of certain companies and onboard new ones. With native delegations, you lose track on who has access where. With Active Roles, we can always see who has access and what they can do in a very granular way."
  • "Active Roles works with policies and access templates, as well as workflows, which are really powerful. While it comes with a lot of example policies and access templates, there are zero built-in workflows."

What is our primary use case?

We primarily use it for delegating access permissions to help desks, for example. We use it to automate certain things, like onboarding new users, or deprovisioning leaving users. When we add somebody to a group, it triggers some kind of automation workflow. Lastly, we use it to sanitize data entry, so to make sure that capital first letter in the street name is used, certain zip codes aren't allowed, others are, etc., so data is controlled.

How has it helped my organization?

It helps mitigate the risks. With traditional native active directory delegation, it becomes real messy, real fast. You lose oversight on who has access where. We are an acquisition merger company, so we let go of certain companies and onboard new ones. With native delegations, you lose track of who has access where. With Active Roles, we can always see who has access and what they can do in a very granular way. You can modify the street name but you can't modify the city for example. Or you can modify the picture, but not the names and so that granularity is not available normally.

This product has eliminated a lot of tedious IT tasks, especially when people leave. There are about 10 or 15 actions that Active Roles does, scripted, in the same way, each time. It used to literally be a list of things that the admin would do, like: hide the mailbox, disable user, remove the groups, etc. Also, the auditing history that it keeps is very handy for us. We have a change record of what's been done to a user, who did it, and when they did it, which really helps us out.

We really needed this kind of product for its Active Directory delegation. We could not allow everyone to have native access to our Active Directory. The delegation bit was really the trigger. Automation is also a major reason we use UiPath. There was just so much room for human error that we wanted to script activities rather than rely on the admins to know what to do. This is especially important now that we are outsourcing many activities and dealing with a changing audience. In order to make sure that everybody does the same thing at the same time, tools like these make sure that you do everything in a structured manner.

What is most valuable?

The value for us is that it resembles the native tools that most people have grown accustomed to. Most people come from another company where they may not have used Active Roles. Active Roles resembles traditional tools like Microsoft's, which is really good because it eases the way people interact with the tool.

AD and AAD management features are really good. They're better than native tools; they offer an added value. They show more fields than traditional tools, such as password age and status of things that you normally wouldn't see. We still have the mailbox and user information all on one screen, whereas in native tools, you need two tools to show that information.

What needs improvement?

Active Roles works with policies and access templates, as well as workflows, which are really powerful. While it comes with a lot of example policies and access templates, there are zero built-in workflows. I would personally love for it to come with 10 to 20 sample workflows that achieve a certain task but are not enabled by default. In that case, I would be able to just look at those to see how it's done. I could clone them, copy them, and modify them to how I want them. Then I would be good to go, rather than having to reinvent things from scratch.

For how long have I used the solution?

We've been using UiPath for about 10 or 15 years.

What do I think about the stability of the solution?

The solution is very stable. Even if components lose connectivity, or the database dies, as soon as it comes back up, it just reconnects and goes.

What do I think about the scalability of the solution?

It covers all we would like to do. It's scalable; you can make it replicate databases. We don't use a lot of those features, but it is very scalable.

How was the initial setup?

It needed a bit of getting used to, in terms of where you set what, but once you get the hang of it, it's really straightforward.

What was our ROI?

I think we're just paying for mitigating risks. There is the risk of leaving all authorized access behind and the risk of having Active Directory pollution. With that comes a risk of people getting access that they shouldn't have or having multiple accounts for the same thing. There's no money or value added from using the solution, but there is risk management. That is really what you pay for.

Which other solutions did I evaluate?

We did consider using the Microsoft solution because it's free and built-in, and that's what everybody does. However, when you grow beyond a certain ping, or scope, you find out that it just does not cut it anymore. We also considered using other tools, but at the time, I think Active Roles was very much alone in this world. I have to admit, now there are other vendors available, which I don't have any personal experience with, but on paper, they seem to do a bit of the same thing. At the time, though, there was simply nothing else that could even come close.

What other advice do I have?

I would rate UiPath as nine out of ten. There's always room for improvement. This is definitely, really up there.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Conrad Tyson
Data Analyst at BAE Systems
Real User
It has a simple user interface where you don't have to write code

Pros and Cons

  • "It has a simple user interface."
  • "The initial setup was pretty straightforward."
  • "I would like a better way to find the little things that aren't simply named."
  • "It could be a little more aesthetically pleasing."

What is our primary use case?

I personally do a lot of process automation and data visualization. I work with a lot of people in procurement and finance to pull data from a lot of different systems, consolidating it, and creating reports, then presenting it. What I do a lot of is taking that consolidated data and creating automated reports with Microsoft Power BI and visualization tools. A lot of where people get hung up is pulling the data and the amount of time it takes to do that. So, people want to be able to automate their processes, as well as have my reports.

When I heard about UiPath, it addresses the initial problem of having to constantly pull data, get updates, consolidate the data, then model it in Excel or other sources, like databases. Being able to speed up that process, then connect it to automated reports, can fully lay out that entire pathway. 

What is most valuable?

It has a simple user interface. We used to have the training onsite Friday and Thursday, and while I personally have a computer science and web development background, a majority of the people there were finance and were procurement who didn't have any technical background. Yet, they are able to learn it because of the GUI and hotkeys, because it is just enter, drag this there, and do that. 

You don't have to write any code. You simply click function, open an Excel file,  and open web browser, then you just grab and drag it. This makes it easy to understand what you have to do and where you have to put fields.

What needs improvement?

It could be a little more aesthetically pleasing. 

I would like it easier to find things. How it works now: 

  1. You look up all the different built-in functions that they have. Most are pretty straightforward. It is click in an open access web browser.
  2. If you don't know the name of what you are looking for, but if you want to be able to do something, then you have to scroll down the page and click it, if it's found.

I would like a better way to find the little things that aren't simply named.

For how long have I used the solution?

I have only been working with it for a few days.

What do I think about the stability of the solution?

I haven't found any problems specifically using the tool. I have only had a few errors, but that is because of personal mess ups when I'm creating processes and a field is messed up or a variable is incorrect. I haven't had any crashes or faults with the free Community Edition and the bot that it has come with.

How are customer service and technical support?

I have talked with the UiPath training staff who came to our site and worked with them. They helped us out with any problems that we had learning things.

I haven't communicated directly with any of their support team members.

How was the initial setup?

The initial setup was pretty straightforward. It was easy for us, and we are government contractors. We had to get all the approvals, but once that was done, it was very simple to get it installed and set up. Then, you just have the desktop client right there. 

I assume going through any of the training on the UiPath Academy that you would have an understanding of how to work through installation issues.

What was our ROI?

I see the potential for ROI and how much time it can save me on cutting down weekly and monthly reporting. It will probably save me five hours a week and another 15 hours a month.

What other advice do I have?

It is a tool, which does what you need it to do.

I went through two non-technical training course to get an understanding of using robotic process automation because I didn't know much about it before I started using the tool. That set me up well before the UiPath Academy to get an understanding of robotic process automation and where it's been going, because I didn't have much knowledge beforehand. However, I plan to go through the Academy training courses. I've heard that it's what UiPath uses internally to get ready for certifications.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Kenneth Suen
Strategy and Analytics Consultant at Deloitte
Consultant
It created time savings for my process, but I would like it to handle understanding natural language going forward

Pros and Cons

  • "Being able to understand that your path is structured as a process flow, you are still able to declare variables, and ensure the background logic is sound. You are also able to really visualize what the process needs to do and the paths that it needs to take: true, false, etc. So, it has been very useful in terms of crafting it."
  • "Looking to go from structured to unstructured data, then UiPath needs to be able to handle understanding natural language and scanning of documents which are not well-written or visible, in terms scanning quality. These are probably the easiest target areas to improve on first."

What is our primary use case?

RPA overall is about routine, mundane, structured tasks. We use a number of them at my client's work in terms of how do we do back office reporting for general deliverables, contract compliance, etc. 

We had a few different reports that we had to do every month. We have to hand-jam them into a very poorly-formatted database which had weird drop-downs. Instead of entering them manually, and spending a day or month just punching in titles and numbers, we compile it onto an Excel sheet and have a bot run and dump all that information. 

All I have to do is tweak what information has changed from month to month. This has made my life a lot easier.

What is most valuable?

When I was first introduced to UiPath, I stated that I am very adamantly not a coder. I hate code, lines, and missing that semicolon somewhere in there. Being able to understand that your path is structured as a process flow, you are still able to declare variables, and ensure the background logic is sound. You are also able to really visualize what the process needs to do and the paths that it needs to take: true, false, etc. So, it has been very useful in terms of crafting it.

What needs improvement?

To exceed the expectations, it needs to be easy to debug, not only easy to craft. You need to be able to make it truly do what you want it to do. As a user, you have an idea of what you want it to do. However, when you hit run, it doesn't always do it, then you have to figure out why. That ends up being the majority of your development time. UiPath does pose a bit of a challenge in terms of easy to understand errors, where it's getting stuck, or what was the logic behind the process that we were trying to do from a UiPath standpoint. Making improvements to these would help out a more in terms of being able to make it more user-friendly.

Looking to go from structured to unstructured data, then UiPath needs to be able to handle understanding natural language and scanning of documents which are not well-written or visible, in terms scanning quality. These are probably the easiest target areas to improve on first.

What do I think about the stability of the solution?

If I'm using it as an attended bot, it's pretty stable. When you discussing unattended bots, anything could go wrong in the entire stack. We have found times, if I run UiPath for a week, and it needs to simply loop a PowerPoint presentation, come back in a week, then sometimes the PowerPoint will be dead. It is harder to understand if it was UiPath's fault or if it was because the device decided to do a random Windows update and restart itself. It could be a litany reasons, but even then, I can't be 100% confident that the unattended bot is going to run forever.

How was the initial setup?

It would have been hard to set up without some basic training and basic use cases to practice through first. After some familiarity with the product, it is not hard to set up.

What was our ROI?

We have seen ROI across the board.

It has limited human errors within the confines of how bots were constructed on what we needed them to do.

My specific process that I use it on went from a day to about 15 minutes (time savings).

Which other solutions did I evaluate?

All the RPA tools are good for different things. For my very simple process, I didn't go with Automation Anywhere because setting up the Orchestrator and turning on the server is a pain. I have had any experience dealing with Blue Prism.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Edward Burrows
Robotic Process Automation Program Manager at U.S. General Services Administration
Real User
Enables us to automate manual tasks, reduce labor hours, and shift people to higher value work

Pros and Cons

  • "We were able to automate a lot of data entry into our financial system. We've automated spreadsheet manipulation in the area of financial management."
  • "I'd like to see the ability to operate in a non-persistent environment. Other than that, I'd like to see more intelligence being built in. We aren't using any intelligence yet, but we'd like to."

What is our primary use case?

We use UiPath primarily for our financial operations.

We use this solution in a virtual environment called VMware Horizon. It has allowed us to get started without investing a lot, which was good for us. We need to go to the enterprise solution using Orchestrator as soon as possible. That said, I wouldn't do it differently, because if we were counting on the enterprise environment to get started, we wouldn't have deployed anything in the past year. Because we had this virtual environment, we've been able to deploy 16 bots so far.

How has it helped my organization?

We were able to automate a lot of data entry into our financial system. We've automated spreadsheet manipulation in the area of financial management.

We knew that our process was very inefficient, so we had to invest in a solution like UiPath. We hadn't used any other solution before UiPath. Our processes are manual and error-prone and we have mid-level people who are highly skilled who are doing this non-skilled labor, which is a problem for the workforce.

What is most valuable?

The most value we got from UiPath is the ability to automate manual tasks, reduce labor hours, and shift people to higher value work.

We found the solution easy to use. We wanted to train our staff who were not IT and we were able to do that. People who worked in financial operations were able to learn the software and have successfully developed bots.

What needs improvement?

We used UiPath Academy RPA training to train 14 people. It was good. I think UiPath needs to do a better job of setting expectations and defining the skill level required. That wasn't very clear to us. We couldn't get a good answer. Therefore, it was trial and error. We were told that people just have to be motivated, but learned that that is not enough.  The trainees need to have some demonstrated technical ability.  We found that some people dropped out because it was too difficult for them. Other people picked it up very well because they had somewhat of a technical background. That would be my message for UiPath, to give better guidance on qualifications in the background needed for training.

One does not need IT coding to learn this, but something within business operations that's somewhat technical. For example, writing Microsoft Excel macros, writing business objects reports, and SQL queries. People who can do those things, they can use UiPath.

I'd like to see the ability to operate in a non-persistent environment. Other than that, I'd like to see more intelligence being built in. We aren't using any intelligence yet, but we'd like to.

What do I think about the stability of the solution?

It's stable. We haven't really had technical issues.

What do I think about the scalability of the solution?

It's scalable. We're not scalable now because we aren't using the Orchestrator software yet. We have successfully tested Orchestrator and will begin using it for production soon, giving us greater scalability.

How are customer service and technical support?

We really haven't had to use technical support much. Most of our issues had to do with configuration and the environment, more than the software itself. It's just been one configuration issue related to this software, so far - operation in a non-persistent environment.  I was told there's an enhancement coming, but I don't think we have the enhancement yet.  However, we will not have this issue when we migrate to our enterprise platform with Orchestrator. 

The level of support we received from their technical support was good.

How was the initial setup?

The initial setup was medium complexity. We were using a virtual desktop environment and had to configure it for the software. It took a few months.

What about the implementation team?

We used an integrator to deploy UiPath. Our experience with them was good.

What was our ROI?

We have definitely seen a return on our investment. It took less than a year to see a positive ROI because we had a very small investment to begin with.

This solution has absolutely helped us to eliminate human errors. Most manual processes have 1% to 3% errors, some much higher.  One of our processes has a 25% error rate.  The bots eliminate those errors. 

This solution also saves many hours of manual work. We have measured the number of labor hours automated to be 25,000 hours a year, so far.

What's my experience with pricing, setup cost, and licensing?

We pay $3,000 per license, annually. We're using attended robots, but we will move to unattended as quickly as possible.

Which other solutions did I evaluate?

We chose UiPath because we simply followed NASA's lead. We wanted to move quickly and we talked to NASA. 

What other advice do I have?

We're driving hard to automate as quickly as possible. Traditional IT is not able to automate all the manual work. A lot of manual work unavoidably accumulates between and around core systems.  RPA needs to be part of IT strategy to automate this residual work.  

I would rate UiPath a nine out of ten. The only reason it isn't a ten is because it lacks the ability to work in a non-persistent environment. Effectively when you log in, you have to download the software every time.  However, this is also due to our choices in configuring the environment.  


Disclosure: I am a real user, and this review is based on my own experience and opinions.
JH
Director at a consultancy with 1,001-5,000 employees
Real User
There are pre-built activities which let you build stuff quickly

Pros and Cons

  • "There are pre-built activities, which let you build stuff quickly. It is a functionality where you can record, as a baseline, what a process looks like. Then, you can iterate off of that to build the bot and make it more stable. That is pretty nice because it saves you time."
  • "Some of the documentation that UiPath has around the technical specifications, from a security perspective, are very factual and comprehensive, but they don't have an audience, like CIOs who need to approve this solution. Therefore, the documentation is one area where I might smooth the process out a bit, since the audience is different from the way the documentation is written as technical specifications."

What is our primary use case?

One of the main use cases is stringing together different applications, like a financial system to a database for data manipulation or data extraction. Then, all sorts of little things are added onto that from a process prospective.

How has it helped my organization?

From a process perspective, every single implementation that we have done has saved time: Anywhere from 50 to 90 percent of eliminating the process time. There was an example where there was an analyst who was doing a manual comparison process of a bunch of different systems. The use case was that the bot just goes and checks a bunch of systems, then compares everything. They only have to manage the exception, but it almost entirely eliminated the time capacity.

What is most valuable?

There are pre-built activities, which let you build stuff quickly. It is a functionality where you can record, as a baseline, what a process looks like. Then, you can iterate off of that to build the bot and make it more stable. That is pretty nice because it saves you time.

It also lets you display something very quickly, so you can see exactly how it's going to work.

What needs improvement?

The product has met expectations in terms of ease of use. There is a lot of stuff going on underneath. In the Studio view, there is a right-hand side where there is a lot of configurable components of activities which are built. Some of those are exposed, and some are not. From a stability standpoint, it would be interesting if more of that was power user available.

Some of the documentation that UiPath has around the technical specifications, from a security perspective, are very factual and comprehensive, but they don't have an audience, like CIOs who need to approve this solution. Therefore, the documentation is one area where I might smooth the process out a bit, since the audience is different from the way the documentation is written as technical specifications.

In a Citrix environment, you can't directly connect to a lot of the applications that you can on a desktop environment, or in a server environment, where it is not a virtual machine and going through a pipe. However, that's just a technical restriction.

I would like it if UiPath could watch someone do a process, then builds the bot, but not in a recorder fashion. I want it to watch someone during their day and observe the processes that they do, then provide an informed assessment of what parts of that could be automated. This is because some people do stuff that they don't even realize could be automated, like an interpretation of people's tasks. Technically, that would be hard to do, but it would make a killer application. This make it a product to install on every single person's computer at a desktop level, or every environment, wherever the process is taking place.

There is some learning curve to using even the initial capabilities. While there are a lot of great tools to help you get up to speed and learn how to do it, I almost think there are two types of tracks which are only being addressed by a single product: 

  1. People who are technical and know the stuff which going on behind the scenes. When they use it, they want to have more access and more ways that they can tweak it. 
  2. People who have no coding experience, or low coding experience. In this case, it's great, but slightly limited, in terms of the activities which are pre-built and those are very extensive.

It would be nice to have a medium between the two or power user concepts, where you can open up all of the back-end. I do know you can do this in UiPath to access the code and take advantage of APIs, when you get into some of the really complex implementations beyond just send an emails and copying and pasting data from one thing to the other, which takes up a lot of people's time. There are additional things behind the scenes that would be great to have access to with UiPath.

What do I think about the stability of the solution?

It seems very stable. Like in a desktop environment, I can't think of any issues.

What do I think about the scalability of the solution?

For scalability, it requires additional skews to orchestrate everything. While it is an area where I've had less experience, that is the key component to making it scale.

Automation technology at our customers' companies is in its early phases. They are beyond the pilot, but not at scale, which is pretty common.

A lot of the agencies that we work with, where they are doing a pilot, do one-offs and growing exponentially (one to two to three bots). They just keep using it, then reinvesting it. The bot process is pretty quick: We are doing sprints for them in six to 12 weeks, and they are done. 

How are customer service and technical support?

As a partner, we have a lot of great people at UiPath who we can call and ask about things. 

They've been helpful with understanding what the timeline is for new stuff, like integration and new activity sets. 

From a partnership perspective, like in delivery, they've been really helpful.

Which solution did I use previously and why did I switch?

Having a free Community Edition makes a difference. As long as you can get it installed, then there is no barrier to playing around with it and seeing what it can do.

How was the initial setup?

The simplicity or complexity of the installation depends on the environment and the CIO's willingness to install it, especially in the Federal space.

What was our ROI?

It takes no more than six months to get to an ROI that is at least recouping the costs. Time and again, we are just seeing those cost savings get rolled back into doing the next project. It's like a self-funding, revolving process.

UiPath help our customers to eliminate human errors.

What's my experience with pricing, setup cost, and licensing?

I would like to have transparency in pricing. We're creating more functional robotic process automation use cases all over the place. I'm never really clear on what the pricing model is, the skews, and how much of an investment can be made in letting new agencies do any of the following:

  • Start to do pilots versus proofs of concept.
  • Pricing per bot in production versus Orchestrator costs. 
  • Fixed cost versus licensing cost per user. 
  • Have access to Studio.

Which other solutions did I evaluate?

Our customer also evaluate Blue Prism and Automation Anywhere.

What other advice do I have?

It is a really slick product. Just play around with it. It's doable for all skill levels.

The UiPath Academy RPA training is good and easy to use. There is a lot of content there in terms of going from a very basic understanding to being able to do developments. It was one of the first RPA training courses, from anywhere, that I took. I thought it was really good. I has a lot of use cases to practice on.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
BryanGraham
AI Chief Technologist at BRMi
Real User
It is easy to set up and install compared to its competitors

Pros and Cons

  • "It has a core tool set of things in use to quickly put together an automation, whether it's interacting with an application or website. It gives you the tool kit that you need to quickly put something together. Very often, we can create something in a very short time frame, like in less than a day, and show it to someone. Then, they can see the immediate value of the solution."
  • "Going forward, I would like to see more stability in the robots. When I create a robot, then I want it to work for quite some period of time. I've had some situations, where things will update, change, and the robot is broken. Part of this is making a more stable implementation easier."

What is our primary use case?

We are trying to focus on using UiPath for our mission. A lot of people use RPA for things that happen everywhere, such as in financial or HR. We are a bit different. We are trying to focus on things which will improve what our customer are doing.

For example, one of our customers is a bank. Therefore, we are focusing on improving their relationship with the bank's customers by using RPA. While there are use cases everywhere, we are focusing on trying a company better and more streamlined at their core.

How has it helped my organization?

The robot (in the bank example) focuses on improving the way a customer interacts with the bank. The robot facilitates the monthly interaction that customer the bank by providing information to the bank, processing information much more quickly, helping the customer and bank at the same time. The bank doesn't need to spend a lot of time or resources looking at the information coming in. The robot can process the incoming information, validate it, and do lot of the work which had been done before. It is a win-win on both sides of the relationship.

We are seeing RPA use cases everywhere. Pretty much every one of our customers has some type of RPA that we are talking about as turning into a pilot or have already moved forward with as an RPA solution.

One example is we created a robot to use with DocuSign, which is fairly industry standard.

What is most valuable?

It has a core tool set of things in use to quickly put together an automation, whether it's interacting with an application or website. It gives you the tool kit that you need to quickly put something together. Very often, we can create something in a very short time frame, like in less than a day, and show it to someone. Then, they can see the immediate value of the solution.

UiPath was easy to use when I first came into it. Though, I have a software developer background, so a lot of the concepts were very easy for me.

UiPath has a whole bunch of online courses in the UiPath Academy. These are very helpful on understanding the capabilities of the tool and some of the nuisances of it. 

What needs improvement?

It takes a bit of thought to find the right thing that fits into RPA at this point. However, with the things that we are branching into with natural language processing and imaging things, there will be more possibilities and opportunities.

UiPath should continue to grow and integrate with things that we can interact with, particularly with other enterprise solutions out there. They should continue to have out-of-the-box things that we can just take and work with.

For how long have I used the solution?

I first got involved with it in the last year or so.

What do I think about the stability of the solution?

I have seen a lot of improvement in the stability and scalability in UiPath over the last year or so. There have continued to be new releases with new updates, along with new technologies that help. Therefore, the maturity of the product has gone a long way in getting to a stable, scalable product.

Going forward, I would like to see more stability in the robots. When I create a robot, then I want it to work for quite some period of time. I've had some situations, where things will update, change, and the robot is broken. Part of this is making a more stable implementation easier.

What do I think about the scalability of the solution?

We have put together a couple installations using Orchestrator. We haven't had the need for huge scalability yet, but it seems that the platform is there and has the capability for it.

One of our customers is a very large financial institution that has a lot of automation, because they have millions of customers. Then, some of them are smaller who are just trying to put their toes in. Even at our very large customers, there are still opportunities for improved, additional automation. However, the maturity across our customers is very diverse.

How are customer service and technical support?

UiPath has always been there to answer the questions that we have or help staff when we need it.

Which solution did I use previously and why did I switch?

Our customers ask us about the solution because of the government mandates.

How was the initial setup?

Compared to the other RPA platforms, like Automation Anywhere and Blue Prism, UiPath is much easier to set up. This is the value that a lot of our customers have seen, because it is so easy to set up, you can set up and install something on your own computer, use it, then run with it, and finally, play with it.

That is a huge advantage: You don't have to set up a large infrastructure just to do RPA now. Of course, Orchestrator is a little bit more complicated, but then I've had a much easier time setting up Orchestrator than I have had with some of the other leading RPA products previously mentioned.

What was our ROI?

The biggest thing for a lot of our customers is ROI. It takes about a year to see ROI, but it does vary based on use case.

One of the use cases that we are looking at is for a large government agency. They are taking people out of doing reports and putting them back in the field. In a cost constraint environment that we are in, this is critically important.

Some of the things that we've done have cut down tasks that took four hours to 30 seconds. So, there is a lot of benefit. Our customer are experiencing very large benefits from automation.

What's my experience with pricing, setup cost, and licensing?

Go download it, install it, and play with it. You can't do this with any of the other platforms.

Which other solutions did I evaluate?

There is an easier level of entry for UiPath.

What other advice do I have?

While you can easily automate with RPA, the tasks someone does repetitively and is likely to make mistakes, thus eliminating human errors on a lot of things, but at the same time automation is only as good as you make it. So, humans are creating the robots at this point, and obviously there is still a possibility for errors. However, in processing workload, you will definitely cut down on the errors happening there.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
SG
Program Manager at a government with 51-200 employees
Real User
We have direct access to read and write data in our applications, but the security and integration need improvement

Pros and Cons

  • "The most valuable feature of UiPath is they have direct access to read and write data in their applications, so we don't need to build a back-end interface."
  • "We still have to test the final product. UiPath's recommendation is build another bot to validate the other bot's work. That is the scary part: If you make a mistake creating the bot, how can you recover from that mistake?"

What is our primary use case?

I work for the financial management office. We do a lot of manual processes. Our use case right now is that we look at all of our financial business processes, break them down, and identify the subprocesses that we can use UiPath to automate. This is very manually, so we try to find some efficiencies which have the most the value for our organization.

What is most valuable?

The most valuable feature of UiPath is we have direct access to read and write data in our applications, so we don't need to build a back-end interface.

What needs improvement?

The security needs improvement, especially in regards to managing the credentials.

I would also like to see better integration with Microsoft products.

We still have to test the final product. UiPath's recommendation is build another bot to validate the other bot's work. That is the scary part: If you make a mistake creating the bot, how can you recover from that mistake?

A lot of Elastic is not working, which is why the solution is not integrated.

While the commercial solution is successful, the government solution needs improvement. Government has so many regulation and requirements that still need to be address by the product.

For how long have I used the solution?

We are still in the process of building our first bot.

What do I think about the stability of the solution?

It's a bit choppy, so people need to find workarounds.

We haven't deployed our first bot yet, so we are unable to gauge bot stability.

What do I think about the scalability of the solution?

We tried to set it up in the virtual environment because we want to leverage a lot of the Microsoft features. They need to include all the API features going forward to make the virtual environment effective.

How are customer service and technical support?

We are working closely with the UiPath technical team because we are pioneering putting this infrastructure on the cloud. 

The technical support team is responsive.

There is a big community.

Which solution did I use previously and why did I switch?

We rely on our partner to identify a solution and give us a recommendation.

How was the initial setup?

We set it up in Studio and Orchestrator. We are also ready to put the bot on our Amazon Cloud environment.

What about the implementation team?

We had contractors, a consultancy company, help us build the system. They are a really good team, who also help deploy the solution for government agencies (DHS and DoD).

Which other solutions did I evaluate?

There are a couple options on market, like Automation Anywhere. UiPath is one of the leaders, so we picked UiPath.

Automation Anywhere is not on the DHS approved vendor list, so we couldn't pick them, as the approval process would take longer for them than UiPath.

What other advice do I have?

Use UiPath in a more process-driven way, instead of BI-driven way.

We put everything on Amazon Cloud, even our development is cloud-based.

We haven't had a change to use UiPath Academy for RPA training yet.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
JM
Strategy and Analytics Consultant at a financial services firm with 10,001+ employees
Consultant
One of the easiest things about the product is you click one link, it downloads, then you are done

Pros and Cons

  • "The object cloning in UiPath is a lot more consistent than Automation Anywhere. The consistency with which it captures the information that it's supposed to in order to do the rest of the process is probably the most useful component of the tool package."
  • "Navigating the directory of objects needs improvement. I would like to be able to put in keywords that would allow me to figure out what command will allow me to do the task that I am trying to do."

What is our primary use case?

The primary use case is data management.

What is most valuable?

The object cloning in UiPath is a lot more consistent than Automation Anywhere. The consistency with which it captures the information that it's supposed to in order to do the rest of the process is probably the most useful component of the tool package.

What needs improvement?

  1. Navigating the directory of objects needs improvement. I would like a better way of finding the command which allows you do the thing that you're trying to do. This would help. For example, there was this one command that I was wrongly using for months. Then, someone told me, "You can do that by just using this one command instead of three jerry-rigged together." Therefore, I would like to be able to put in keywords that would allow me to figure out what command will allow me to do the task that I am trying to do.
  2. The testing could be a bit easier. There are error handling steps in the platform tool, but it's not super robust. It's very user friendly from a development perspective. However, from a testing perspective, it is unclear what I am looking at. Maybe, they could add more commenting. 

What do I think about the stability of the solution?

When the complexity increases, the bug related issues go up. There are limitations to utilizing RPA software, in general, where sometimes you have business leaders who think something is a good process. Then, they ignore the technical advice to not move forward, or choose to. Thus, you're left in a situation where you're trying to automate a process that isn't great for automation.

How was the initial setup?

One of the easiest things about UiPath is you click one link, it downloads, then you are done. With Automation Anywhere, we have a whole days worth of setting up that needs to be done. This is another component that UiPath is leading the industry in.

What about the implementation team?

UiPath works best when there is a strong understanding of the capabilities and limitations of RPA. I have seen it work best when you have an experienced practitioner who has seen what an implementation looks like. Therefore, they know the right questions to ask as you are determining which process to automate. It is better to have skilled developers, who are more technically capability, to develop solutions using the tools which come with the package to make sure it is working correctly. 

There is the upfront work of talking to clients. There is a middle part of developing it, then the maintenance and operations post-implementation. You have to manage the bot after it's built, and it works best when you have someone who comes in and knows all three of the step components are equally important to a quality end product.

What was our ROI?

The ROI on all of our RPA use cases is from a throughput perspective. Processing time improvement is anywhere between 70 percent faster to 300 to 400 percent faster. For the right processes, there is even up to 7X to 10X improvement from a throughput perspective, even though it works through the UI. 

The most impressive use case that I've heard of was about saving a year's worth of FTE time in a month's worth of development, testing, and deployment, then doing the processing.

Which other solutions did I evaluate?

I have used all of the major RPA platforms: primarily Automation Anywhere, UiPath, and Kofax.

UiPath is the most open in getting people to use their software. I think they understand that the most successful relationships in sales come from people playing with the solution.

I started out as an Automation Anywhere person and will always be better at Automation Anywhere because of my affinity with it. Where Automation Anywhere might have UiPath beat is the speed at which you can automate simple processes, like being able to create and automate simple processes. Automation Anywhere is a better point of departure because the way you look at the script in it, there is almost like a sentence that you can read. Being able to understand what a process is supposed to do, you can just replicate the steps in your head. A non-technical person can open this web browser, type here, and press enter.

With UiPath, it's more from a process perspective, which is more useful if you're looking at automating a process. Instead of something simple, like for training, we'll have people look up the weather in five, ten, or a 100 cities. From that perspective, it's easier to start up than Automation Anywhere. 

UiPath makes up for its steeper learning curve by being a more reliable product. 

If you are looking on the spectrum of which is most to least technical and most to least scalable, UiPath is a happy medium compared to Kofax, Automation Anywhere, and Blue Prism. UiPath is less technical and not so hard, but it's also scalable, so it's a happy medium.

What other advice do I have?

UiPath Academy is by far the best online training resource. From an online content training perspective, their videos and training modules are leading the industry.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
JF
Manager of IT and Development at Gecu
Real User
Automates repetitive tasks that eliminate human error

Pros and Cons

  • "The automation of repetitive tasks that eliminate human error is a valuable feature."
  • "I would like to see some integration, or ease of integration, with APIs, so we can automate stuff faster. E.g., we go through a co-op, which is a card processor, and they have a very powerful API."

What is our primary use case?

We have multiple primary use cases for UiPath. We have already implemented three, but I foresee many use cases in the future. For example, I am working on one which will automate the gathering of information to comply with subpoenas.

What is most valuable?

The automation of repetitive tasks that eliminate human error. 

The speed: It is so fast when it replaces a human, you become much more efficient.

What needs improvement?

I would like to see some integration, or ease of integration, with APIs, so we can automate stuff faster. E.g., we go through a co-op, which is a card processor, and they have a very powerful API.

For how long have I used the solution?

So far, we have been using it for six months.

What do I think about the stability of the solution?

I haven't had any issues with the architecture at all.

What do I think about the scalability of the solution?

We are starting small and have three bots.

I'm already engaging in conversations with UiPath consultants to ensure that I have the right structure. I know I will need Orchestrator soon as we continue to develop more.

Which solution did I use previously and why did I switch?

I introduced automation with UiPath. This was our first introduction into what is robotic process automation.

How was the initial setup?

The setup is straightforward. We did the complete setup in a week, which includes the server, the virtual machine that it would be running on, and a developing environment, because I wanted that to be separate from our production environment. This is for a small environment. I am expecting the bigger environment to take us longer.

What was our ROI?

For our service test department, we created a bot to automate the reset of pins and passwords for our users. This was the number one call for our service desk. The bot now takes care of it, and we freed resources. Now, we don't have any calls to that service desk team, and they are doing other things.

What other advice do I have?

It was easier to use than I expected. We started with a very small bot. It took us three to four weeks to develop, then put in production.

My staff is using the UiPath Academy. I manage the development department. My staff has gone through the Academy's training, and it's awesome. It's a great resource, because now that I'm hiring more people, I'm having them go through it. Then, I onboard them on what is it that we need them to do.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
EG
Automation Engineer at a consultancy with 1,001-5,000 employees
Real User
Allows me to drag and drop pre-built functions to speed up bot creation

Pros and Cons

  • "The number-one valuable feature is the ease of use. I come from a development background where I wrote a lot of code. The fact that you have these activities with pre-built functionality is great. You can drag them in and use them as shortcuts to get to an end result faster than if you had to do it in a programming language."
  • "There is some room for improvement in the area of error handling. I had to create a custom approach to error handling. If there were some sort of activity or workflow that could be easily dropped in to help support that, it would be good. Error handling and logging, as well as process logging would be a big help."

What is our primary use case?

In general, we use it for automating monotonous, manual processes which a lot of our clients have. We also use it for internal employees in our company.

How has it helped my organization?

We had a use case where there were a lot of documents that had to processed to give access to certain systems. With UiPath, we were able to really streamline that. Instead of having an end-user go through these documents manually, do reconciliation, and send emails back and forth, we were able to automate that solution from beginning to end, with very little human interaction. In the end, over the entire process, it saved hours out of their day, when you compound how many times they run this. It has really freed them up to do other more important tasks. That was my first foray into the client side, and seeing how happy they were to have this bot was great. At first, they were skeptical, but once they saw what it allowed them to do and what it's capable of, they were really happy with the software and what we were able to develop for them.

In this use case, UiPath reduced human error by 100 percent because we completely removed the human element from the data reconciliation for those documents. Through automation, along with some fine-tuning, we were able to get the data reconciled between the two files with 100 percent accuracy, and inputted into the system. Not every use case is going to be that straightforward, but in this use case we were able to get that result, which was wonderful.

What is most valuable?

The number-one valuable feature is the ease of use. I come from a development background where I wrote a lot of code. The fact that you have these activities with pre-built functionality is great. You can drag them in and use them as shortcuts to get to an end result faster than if you had to do it in a programming language. UiPath exceeded my expectations in this area.

Also, the training that's available through the UiPath RPA Academy, as well as the community - the forums, where you can ask questions - both are helpful. The community is a good way to see what others are doing and learn tips and tricks for the platform. That's very useful in comparison to other companies that do RPA but don't have robust training.

What needs improvement?

A lot of the features that I had been asking for have actually been released. We were using an older version of UiPath and we were having issues with Computer Vision and the OCR engine with UiPath. But now that we see that there's a whole Computer Vision activity suite available, I'm excited to use that. I haven't gotten to get my hands on it yet.

But in terms of additional features, I can't think of anything that I would request. I see that they have the AI functionality, as well as the Computer Vision. They have a lot available that I haven't even been able to get my hands on yet. I think once I get some more time to explore the tool and exhaust its capabilities I can look for additions from there.

There is some room for improvement in the area of error handling. I had to create a custom approach to error handling. If there were some sort of activity or workflow that could be easily dropped in to help support that, it would be good. Error handling and logging, as well as process logging, would be a big help.

What do I think about the scalability of the solution?

I can't speak about its scalability too much because we haven't gotten there, even as far as using Orchestrator. Most of the automations that we have done have been one-offs which are done locally on someone's laptop.

But from what I've read in the training and what I've seen in the demos, it seems like a very robust platform that can definitely scale, when designed properly. I'm looking forward to the next phase of the development journeys that we have, where we are actually doing things to scale and thinking long-term about how we can share bots across an entire enterprise. It does appear that they have a pretty robust toolset.

How are customer service and technical support?

I have had to reach out a few times to support, especially when I started and was trying to find my way around the tools and some issues that I was having. The response was great. I was able to get on a video call and actually show my use case and show the kinds of issues I was having and they were able to walk me through the process and suggest ideas about how I could approach them. My overall experience with technical support has been very good.

Which solution did I use previously and why did I switch?

Our company is always looking at the latest digital trends and what we can do to offer our clients new solutions which keep them at the forefront of IT. We were aware of RPA and it was just a case of narrowing down which solution was the best to deliver to the clients.

How was the initial setup?

The initial setup is straightforward. I've used other tools where there are components that you have to install prior to installing the software. You have to create a database and things like that. Whereas, with UiPath, it was a very light install. You just have an executable. It is able to install the components that it needs on its own. There was no other configuration that I had to do on top of that to get rolling. That's a major plus to me and, especially, to our clients. If we don't have to spend as much time getting them configured and set up, it's better for them.

What about the implementation team?

We did the installs ourselves. We have a test lab that we built. We set up an Orchestrator lab so we can get more familiar with the tool. That was all done in-house as part of our training to get familiar with the tools. Essentially, if we want to sell this capability to clients, we want to at least have some knowle