UiPath Platform Reviews

We automate processes across a number of different agencies. We automate whatever use case they determine. We tend to focus on the financial management side, but we have other areas that we've delved into such as HR and general data pulls for executive dashboards.

Oddly enough, a lot of our clients have not focused on work where there are people actively doing the process already. They've chosen to focus their efforts on processes for which they haven't had the manpower. It has been a little bit of a challenge in that the use cases tend to be coupled with a lot of process-development stuff. We have to figure out what the process is before we can even begin to automate it.

But over time, we plan on trying to shift that focus back to areas where they have a large number of people doing a process all the time and getting them to shift those people into doing the complex processes where there isn't a structure already determined.

The differentiation between unattended and attended bots is valuable, as well as being able to do portions of a process that are unattended coupled with portions that are attended. We can get human interaction, all within the same product.

The product is easy to use and definitely exceeded my expectations in that context. I have an IT enterprise architecture background with some computer programming experience. This was very easy to grasp.

The additional plugins and different partner programs have been a huge help.

My only complaint is that I hate VB.NET. If I had to pick a language, it would not be VB.NET. That whole .NET framework is just overly complicated. But I can understand why it's necessary for the use case of RPA.

We haven't had any problems with the stability. In comparison, we do use Blue Prism and that solution often runs into memory issues. That's one thing that we have not had to deal with, with UiPath.

I haven't had a lot of chances to test out the scalability firsthand, but the documentation is all there and it makes sense. It seems relatively simple, which is a big help. Once again, this is in contrast to Blue Prism whose documentation is not good. It's very confusing to figure out how you take it from a single-bot use case to multiple bots and more.

It's an easy setup. It's a single install which is pretty simple. Connecting to Orchestrator does get a little complex in some cases. It is what you make of it. Certainly, installing Studio on a single desktop for proof of concept is easy. It takes five minutes. When you start to get into enterprise-level setups, where everything's a different server and everything has to be connected, that's necessarily complex.

Blue Prism definitely has a simpler licensing structure, but I feel like that's almost a shot in the foot at certain points. It also gets kind of deceptive. There's a crossover point at which, if you're scaling up to a high number of bots, UiPath path definitely does come out cheaper. But the initial implementation has a higher cost.

We've been working on RPA, in general, for about two years. We're at different points in the process for different clients. We have some that have grasped onto it quite quickly and others that are still in the proof-of-concept/pilot realm, and we're trying to push it past that. We've been doing it for a fair amount of time, given the relatively young age of RPA as a whole.

I've done a number of different training sessions through the UiPath RPA Academy. The introductory ones are fine, but I really found a lot of value from the ones that focus on solution architecture, the courses that were more on the general infrastructure of how you would implement UiPath.

I would give the solution a solid eight. The first big thing with software is, if you're not running into bug issues all the time, that's an easy five right there. If it's easier to use, that's a six or seven. And it's just been consistently good. I haven't really run into any areas where I've had any trouble. The only real issue is that, from a consulting perspective, I can't really go out there and say, "We're going to use UiPath," all the time. We really have to leave it up to the client.

The primary use case of this solution is to generate a report by scraping data, filtering it and combining the data for input to another system.

UiPath has improved our organization; the primary difference introduced by the application of the UiPath tool is the speed of processing and accuracy in the data processing.

The most valuable feature is the unattended robot, it adds a lot of value. Besides, there are certain situations where attended robots are employed to perform specific tasks.

Making improvements in the processing speed would be a good idea. I have experienced that sometimes during the development of robots, it becomes prolonged and unresponsive. Also, sometimes errors pop out of nowhere for already working simulations. This is not a significant limitation, but it would be nice if these instances can be eradicated. 

We use it for customer-facing and internal processes.

The most valuable feature is its time savings.

The product is easy to use and has exceed our expectations. We have a mixture of technical and non-technical people.

They need to improve features around legacy systems.

We currently lack in experience. Hopefully, after another year, we will be more experienced with the product.

UiPath has been stable all the way through. We have not experienced any issues.

It scales very well.

The technical support has been good to work with for the few cases that we had to raise.

The initial setup was pretty straightforward. Including the Orchestrator, the setup took one to two months.

We have seen ROI. It has eliminated human errors and saved time for other teams at the company.

We looked at Blue Prism and two other vendors. Based on our comparison, UiPath was the better solution with better licensing.

My team uses the UiPath Academy and find it good and helpful.

Automation in our business is a new thing.

We use it to automate administrative functions, like finance and HR tasks. We are also automating a lot of things in our SAP systems, e.g. updating prices. 

We use it for a lot of small tasks, like downloading something from an particular internal website (e.g., SharePoint in Office 365) and uploading it back, or for doing modifications, then loading them back.

We use it in a very large way across the company. Last year, we implemented approximately 22 processes and saved close to 80,000 hours total. This year, we have already saved close to 6000 hours. 

You don't need to know coding, as it's pretty straightforward. The graphical user interface is easy to use. It is drag and drop. You do need to understand the basics of what's happening, what you're doing, and how the technical things work. However, after a short bit of training, you can start doing stuff, and the more you learn, the better you become. 

There are so many workarounds. It allows you to do complicated things in such an easy way. UiPath has provided so many APIs that make it easy to interact with other databases or applications without even going into them. If I want to download something from a website, then I don't need to necessarily go into it, I can use the API function, which is very cool.

With Excel applications, it is not able to handle a lot of pop ups. It should be able to do this automatically. We just change the format of the file from XLSX to XLS, but it should be able to handle this automatically. Instead, when something pops up, it gets stuck there. This type of thing are small, but still the process gets stuck. I would like to see better integration of applications to avoid these issues.

We are also making a lot of manual changes in SAP. We are looking for a solution where we don't have to make manual corrections every time, similar to what UiPath did with some SharePoint websites.

Less than one year.

The product is definitely reliable. It gets the job done. The difference is in how you design it. When you start as a developer, you tend to always take the longest route as part of the learning process. Once you get used to the product, you realize something can be done in two steps instead of five.

A lot of people rely on what I design, so if it doesn't work, I immediately get a call that 50 people are waiting for something. This happens, but rarely, as it works perfectly.

Whenever we get stuck on something and are not able to proceed, then we get in touch with UiPath, who will help us out. Their technical support staff is pretty good. These things really help the user out.

Initially, I used the UiPath Academy when I didn't know anything. At that time, I went through the basic training, then I had to leave the academy to focus on automating our company standard products, like SAP.

I have been working with this solution for 11 months. I did not know about this solution before working as an RPA Developer. Now, you can challenge me on anything UiPath related, and I will find a solution. It is so easy to learn new things. It has good usability.

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.