UiPath Platform Reviews

We are a pharmaceutical company, producing insulin, primarily for diabetes. We work with other diseases, as well, but our focus is primarily diabetes.

We have automated many processes, at least 20 RPAs across the company.

Automation can be done in many ways, but UiPath is a more simple approach. There, any layman can learn how to program in UiPath, which is its main benefit.

We need them to improve the scalability, as we are still building up.

We have had stability challenges. However, I don't know whether it is product-related programming-related, or if it is our core systems which are failing. So, we have instabilities, and whether or not it is UiPath, that I don't know.

We still need the power of the scalability. We have a few robots, but we are a big company with 45,000 employees. 20 robots will not change the world.

The product is not big enough yet to eliminate human errors.

The initial setup is complex. Technically, we are still implementing the product, as we are doing it in phases.

There's a difference when you start up, you just need to make something work to prove the concept. Proving the concept, that is easy. You hire in some consultants, build the robot, and it works. Building the organizational scalability is more complex: How to combine process knowledge, programming knowledge, and maintenance knowledge, since these are three different types of skills which are needed. It's not straightforward to do in a global company.

If you are a local company with one site, it's one type of challenge. If you have multiple sites across the globe (more than 200 sites), it's another type of challenge. Thus, we haven't nailed it yet. Right now, at this intermediate stage, there are more stages ahead of us.

We would like to see improvement on the ROI, as we need to free up resources. Too many man-hours are being spent on trivial tasks which could be automated.

RPA appears to be working, as a technology, but it is still too immature to say that it is beneficial as many people portray it to be. It is still in the making, but it is not there yet. Right now, we don't have a solid business case on RPA, as a technology. Maybe, in the future, but it has given us a lot of challenges so far.

When it comes to finance and HR services the product has great potential. Our company is big, so there are a lot of opportunities.

We are doing automation internally for financial processes.

Externally, for our customers, we are developing a shared service center. This is not restrained to any one specific area, like HR or finance. Anything that is manually or taking a lot of human effort, we try to automate (by selling it to our customers).

The Unattended Robots are good and handy. If you have the proper team and environment available, especially a team who is experienced and knows how to develop with a sense of excellence, then a lot of tasks can be done outside office hours. Then, the next day, teams can come in and have the information that they need readily available.

UiPath needs to improve Orchestrator and its back office licenses. For example, three or four people logging in on a license should be able to get in, but they can't, even though its Unattended.

Why can't we just increase the capacity of the VDIs, so we can use capacity that is there?

Stability depends on the type of structure that you are putting in place. I think it is important that you run 16GB, with not more than three or four processors in parallel.

If I need something, I go to my account managers, who are nice people. They respond back quickly and get back with a lot good options, which I like. 

My development team does connect with the technical teams. The feedback, which I receive from them, is very good. There have been instances, which we have highlighted and identified something, then the UiPath technical team accepted it, said whether they would fix it in the next release, then fixed it if needed.

The UiPath Academy is fantastic and amazing. I'm a big promoter of it in my discussions with customers.

When it comes to Studio, it is an easy solution to install. Anyone can go download and install it. Though, I'm not sure if just any company can install it, because you need to have permissions from IT in order to install it on your computer.

When it comes to Orchestrator, you need an approved structure from IT security. There are associated firewalls that have to be installed with your IT partner's help. Then, it is quite straightforward.

UiPath helped us with the installation.

It is not easy to see ROI quickly. 

It is not a cheap solution. There is an annual licensing cost for all the components.

When it comes to back office licenses, why can't we have parallel processors running on one back office license? I understand the commercial aspect, but when you have servers and a node locked license, you should be able to use the license from different instances.

UiPath is quite a customer-centric company.

We are working on trying to optimize some of the current processes which have been selected for review. I have been talking with our business partner to try and find the best way or tool to optimize these processes.

I have only been with the company a month, so I am only aware of a couple of scenarios/cases where it has already been implemented, such as:

• Transferring data from one system.
• Looking data up on the internet from a browser.
• Performing logins and copying data tables, then putting them into Excel. Afterwards, manipulating and putting them into the right system.

These are our best cases, so far.

It is great for automation. It can reduce the time needed for the entire work assignment, freeing up time for something more exciting.

There is a very steep learning curve for business users.

From everything that I have seen, we still have stuff that we need to figure out on the inside:

• How to spin up servers.
• How to get compliant.
• How to create A/B uses for the robots. 

It would help to have some guidelines, which I haven't found yet. It seems like UiPath is trying to keep out of the guidance part, because they want to leave it open for us to interpret how to use the tool. 

I don't even know all the features available yet. I would love to see the roadmap. I love that going forward UiPath is simplifying the roadmap, trying to make it available for development within the business, not only IT.

The stability has been good, so far. I haven't had any complaints.

The scalability seems good. 

I haven't been through to customer support yet. I use our internal tech support (in-house). We have some knowledge, and they have been working in this area for quite some time.

I love UiPath Academy. While it is dull and I can't do more than an hour or two at a time in sequence, I think it is great. It's available to everyone, which is awesome.

The implementation for virtual environments went fine for the cases I've seen. We are using Citrix for some of them and virtual machines for the Unattended Robots, which seems to have been flawless.

We used consultants at some point.

It has saved us time. We are still doing the business cases to determine return of investment.

We expect to see ROI and performance benefits. I would rate the performance benefits as a ten out of ten.

I have nothing to do with licensing.

We are using multiple solutions for RPA within the whole region. UiPath is doing something right with its open community, sharing and involving users, then providing a platform for us to share our findings and snippets. That's the way to go and why I would recommend UiPath.

We have a huge strategy on digitalization, so automation technology is very important. It's a common goal: Optimizing and putting stuff into categories, which can be optimized. 

While I believe it has been helpful in the elimination of reducing human error since it is doing the same task every time, I'm fairly certain we didn't have many error previously.

I am a developer, and I find the product pretty easy to understand since I understand the logic of data containers and data types. However, I have been speaking with a lot of our business partners on the business side, and they are finding it hard to use.

The primary use case is business services (finance).

When we would have a huge backlog, we would hire short-term employees for some of our cases. Now, we don't have to do that anymore.

It is easy to use, automate, and scale.

UiPath should make the solution part of customer's everyday (more user-friendly).

I would like to see the following additional features going forward:

• Advanced scheduling
• Easier implementation of the robots
• Better analytics
• Easier non-technical overview of the process.

The stability is pretty good.

Our Citrix environment works, but it is quite unstable. It takes a lot of processing time because it is unstable. We have to do a lot of checks and so on.

The scalability is pretty good.

I have not had to use the customer support.

The UiPath Academy is fine. I would like it if the videos were more written out for reading purposes, since I have been developing in UiPath for some years before taking the Academy. Having to watch all the videos was a bit slow and time consuming.

The company was not using an another RPA solution previously.

The implementation went really well. The initial setup was straightforward, but when you start to scale, you have to figure out how to do it.

Our Citrix environment works, but it is quite unstable. It takes a lot of processing time because it is unstable. We have to do a lot of checks and so on. 

I was a consultant doing implementations for many years before taking an implementation with this company.

We have seen ROI. It has saved our organization time.

It has eliminated human errors. There are now more processes where we do checks and controls than we would do with an actual human, because it takes no time for a robot to do the checks. 

We are only using Unattended Robots. Though, I can really see a use case for Attended Robots, especially with these cases where there are a lot of errors. The user could help the robot and we can process the case, instead of having in error.

It is really easy to use and get started with, but if you want to build up more complex processes, you need to have a bit of a development background to make it easier to understand anyone other than yourself.

We are looking at processes and automatization and are at the very beginning of our journey. We have been looking at finalizing the job and making the use cases in insurance assistance.

When we finish a job, we remove articles from it which are not being used. That was a manual process, and the guy who was doing it wasn't really adding any value to the company. Now, they only have to look for the exceptions, and everything else is automated.

• The automatization part
• The OCR technology: Having it automated and putting it into other systems.

I would like UiPath to be more intuitive, so people like me could use it.

Usability is its room for improvement.

Until the solution is more stable, the robots need to be Unattended.

The system is quite stable. However, we need more experience in coding it to make it even more stable.

The scalability is huge.

We have one guy doing the troubleshooting who likes to try different alternatives for locating answers, like YouTube or calling support.

The technical support has been very helpful. Whenever our guy has a problem, he first goes to the phone for a resolution. This is really the reason for choosing UiPath, because everybody else was so closed off, and it was hard to obtain knowledge.

We did not have a previous solution. This type of solution is quite new for us.

We decided to purchase this type of solution to reduce our backlog with insurers.

If you have the right person, the setup can be straightforward.

We had some issues in the beginning because some of our applications cannot run on Citrix. Having the robot run alongside it and going into the computer, then into Windows was difficult, at first. It has been working now that some of stability issues have been fixed. When it is not stable, things take too long.

We started with a consultant. We had some specific tasks that we wanted him to make the robots do. However, when we got started, we changed the approach to do it ourselves with him teaching us. We started with four people doing the training, then ended up with one person being capable.

We saw ROI in the first month that the first robot was implemented. Because we had people leaving when the robot was ready to start, it was ready to do their jobs right away. I would rate the ROI benefits as a nine out of ten.

It has helped us to eliminate human errors.

It has saved a lot of time for our organization.

We looked at three different vendors, but chose UiPath because of its easy access to knowledge and information.

Dive in, start working with it, and get experience along the way. Just working with it, you will get a lot of great ideas.

Our automation technology is at its beginning stages. There is huge potential for us with it. We need to start looking at our HR processes.

We have someone on our team who has just start to use the RPA training in the UiPath Academy.

The handling of different types of insurance tasks.

It has mainly taken the load off of employees. We had a huge amount of tasks which weren't being done. It provides our employees time to do their other work, since we automated very manual things. 

We are currently using automation technology at a small level, as we just got started with UiPath and its technology. 

Its ability to remove manual tasks.

I would like better stability and possibly some tools to determine why robots are failing.

The stability is not great. UiPath is okay, but when it interacts with our programs, it often fails. It is difficult to determine why it fails. We are utilizing a lot of time trying to figure out why it is unstable.

The implementation time was very long due to instability.

The scalability is good.

The customer support was slow at the start. After a while, they come up to speed, then everything was okay.

The initial setup was easy because it was logical, but afterwards, it was harder to make UiPath function. While it is simple to set up and get started on. To make it stable, that takes a lot of hard work.

We use it in Citrix. The implementation was easy. We just installed on some VM servers.

We did try Blue Prism in another part of the organization, while using UiPath in our part of the organization. We decided to stay with just UiPath.

Since it was two different parts of the company, so you can't compare the decision. It was a decision made by management.

Because we are spending so much time on debugging, it has not saved us time yet.

We just use Unattended Robots, not Attended Robots.

I am not using the UiPath Academy because I do not put in the robots. I make sure that they run in the background. I do know some of my colleagues are looking at using the Academy, but they have to find time for it.

We are working on changing all the administrations tasks at the college. For example, with travel refunds to the students, students currently have to go from their homes to the school before they can be refunded their expenses. We want to make a robot which does that instead of the people doing it. I'm using a measurement tool for distance to calculate the measurement from student's homes to the school. Then, this should calculate the amount the student should be refunded.

The product is easy to learn and begin using. When you are just getting starting, you can get deep dive and start using PowerShell and other tools.

It is easy to use and understand. You can learn it by yourself.

The reporting task needs improvement. The reporting is boring.

The product has been stable, so far. It is rare that it goes down.

The product will be able to grow with us.

I don't really use the support, because the product is that easy to use.

I have used the UiPath Academy, and it is great. The videos and questions are good in it.

It was easy to get started with PwC's help. It took a week.

We received help from PwC with the setup. They do most of the financing stuff with UiPath.

It has helped us eliminate human errors. People from the school doing the entry do not always follow the rules, and the robots are following the rules.

It is saving us time through compliance.

We also evaluated Blue Prism, Kofax Kapow, and Automation Anywhere.

The biggest deciding factor to go with UiPath was its community.

We have a lot of maps worldwide which order some stuff from my department, and this is the compiled path. This goes into our database, then it comes to us. 

It uses data that we have already in the company, which is just sitting there waiting to get picked. You just have to tell a robot that a human does this, now you do it. We have so many processes which could be done like this. Right now, it's just scratching the surface. We are really exciting about it.

The product is very intuitive and easy to use, and I am not a developer.

The product is stable with no downtime.

The product can scale and meet our needs going forward.

I haven't used UiPath's technical support.

The UiPath Academy is good. I started there and learned how to use the tools.

The initial setup was very complex. We had the data, but we had to streamline it. You can build a robot in 30 minutes, but the robot needs to get the data correctly. This was hard to do because the laboratory in the U.S. uses the system one way, then the Chinese lab does it another way, so we have to streamline those before we can use the robots. 

Therefore, I should have looked at the data beforehand, since it took too long to get the data to be recognized correctly. We have learned from that experience.

The product has saved us on time.

We are mostly using it for HR processes. We have two departments: Accounting and HR/Payroll. However, we mostly use it for payroll and travel.

We are only using Unattended Robots. We need to start talking about Attended Robots more.

We moved IT to a business unit, so the business now knows more about IT than before.

The automation technology at our organization is not so mature.

The platform is open, and we can connect it to other technologies. We connect it to SAP using the SAP Connector. We are also using intelligent OCR technology to read receipts.

While the product is easy to use, it is not easy for all business people to use. It needs to be improved to be like Excel, since everybody should have an RPA tool. So, it needs to be easier to use.

It can be stable, if you build it stable. However, you have to know the tools or activities which make it stable.

It can be scaled. We have it scaled for all our customers. 

We are a shared service center. We have scaled to run task by task, which we find easy to scale.

Working with the customer support is easy.

There is a lot in the UiPath Academy. It should be divided into smaller tasks and smaller certificates. 40 hours is a whole week, which is a lot, and most people need more time than 40 hours to complete the Academy. As a baseline, the training is helpful, but not anymore than that.

We did not use a solution prior to UiPath.

The initial setup was not straightforward. With some of the technical infrastructure that we deployed in 2017, we were an early adopter, so there wasn't a lot of product experience. We made a lot of mistakes with it.

We used a consultant for purchasing the licenses and deployment. While we still use them for licenses, we now do everything in-house.

We don't have a money saving initiative. Our goal is to do more with less, e.g., we have taken on more cases without scaling up with people.

We have eliminated human errors and saved our organization time.

We did a PoC of UiPath with our main processes, and it showed good results. 

We did try Blue Prism before during ramp up. They were quite similar at that point, but UiPath seemed like a more open platform with the better possibility of using the best technology available and integrating with it, instead of having an all-in-one system.

We are in the public sector, so we had a public bid, and there were only two.

Just do it. Start with a PoC and do the trial. It's easy for a technical person to look into it. Every person that can do programming can learn RPA in a short amount of time.

It is an open platform where you can do a lot of stuff.

We don't use Citrix. We run the application on virtual machines. The implementation was good. 

The primary use case is to have a platform which allows us to scale rapidly without adding a lot of human labor. We are looking to go global without being dependent on recruiting heavily on back office functions.

We combine this RPA solution with predictive analytics. We are in the hairdressing industry, so we predict the amount of haircuts that we get every month in advance. Based on that prediction, we set up our work shifts based on it. We do that predictably, then we use UiPath RPA to fill in the work schedules for each employee in advance and measure it, since it is really important for us to get an accurate number of shifts based on predictive analytics.

It is fairly easy to use. We are using it with a lot of integrations with separate tools to get the flow of data going.

Valuable features include rapid development and the scale of solution. The most valuable feature would be accuracy: The ability to perform the same job accurately and consistently.

We use UiPath only in virtual environments. If it came out of the box like a software as a service, it would be a whole lot better, especially in our case. All our internal systems are cloud-based systems, so we have no dependencies or legacies in terms of installed software in any way. We could be completely in the cloud all the way through.

I would like to see direct integration with the Google BigQuery platform. 

I would also like an Orchestrator self-service desk.

The stability is as good as the developer makes it.

The scalability looks pretty solid. We haven't been working with it too long, or long enough to see it really scale yet. 

Orchestrator should have better scalability with a better payment model in terms of number of processes that you want to use. Instead, you have one product which covers this size with this fixed price. You're getting a box of options, but you can't really scale it.

We have not really used the support. We did spend a bit of time on the community forum, but that's about it. The community forum is pretty good. This is one thing which differentiates UiPath from the pack: It has a community and access to information.

We did not use a previous solution. We went straight to UiPath right from the get go. 

I have worked with automation before. We saw a rapid gain in terms of automation where we couldn't automate in any other way. 

The initial setup was a bit complex. It could be better, especially with Orchestrator. 

Orchestrator should be a separate solution, straight out. Just sign up and have a heavy solution for it. Instead, we spent a lot of paid consulting hours setting it up on our Google Cloud platform and virtual server in the cloud. That was just wasting money for our organization. It should be its own software as a service. 

We used PwC for the deployment, who was very good.

We've been in production for about two months, and we have seen tremendous ROI. The accuracy of the job was far more valuable than the man-hours spent.

It has helped to eliminate human error by a huge amount.

While it has saved us time, we're a small staff business, so there's not a whole lot of time to save.

Licensing costs are high, but still well within a positive return on investment.

We like the hybrid model, but it would be very costly for us to have one Attended Robot for each person in the organization. Although, it would be nice to have, we don't do many mundane, repetitive tasks in entire our organization. We actually have UiPath to do all the work that we don't do, which means we can think about it differently from the start. If we can consolidate all those tasks on Unattended Robots from the start, then we save on licensing money, which we try to keep as tight as possible.

The main cost driver is developing and maintaining the software. Ensure that you don't spend unnecessary time implementing something you don't know. Get someone who knows it to get it up and running. Let that be the basis of your tech choice. I like UiPath roadmap, and the roadmap of the product should also be very important.

Getting the ROI, which we expected within one month, would be impossible to do with another tool.

We did not look at other solutions. I am managing the system, not developing it. I am a self-service manager for the operations, and I only knew UiPath. Therefore, the cost of implementing something that I didn't know would be higher than the cost of implementing something I did know. Plus, it works for work we need.

The automation technology at our organization is pretty good. We use a set of combination batch/cron jobs for a Google Cloud platform together with some AI automation tools, like Dialogflow, in combination with the RPA tools, like UiPath.

It is a very good product and very much stable. I love working with it. Though, it still has some limitations when it comes to integrations and development. Sometimes, you find yourself in a situation where have to add a bunch of code to make it work faster, or you will be stuck with it dragging and dropping. While this works in most cases, for the 20 percent where you want to add code, it does becomes annoying.