UiPath Reviews

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.

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.

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.

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

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

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.

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

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.

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.

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.

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.

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

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

We have about twelve people working with this solution, from developers to the business side to the IT side.

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.

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. 

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.

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.

We have some processes that haven't been completed flushed out. Right now, there has not been an exact improvement yet.

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.

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.

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.

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.

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.

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).

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

The primary use case is data management.

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.

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. 

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.

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.

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.

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.

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.

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.

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.

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.