UiPath Platform Reviews

We use UiPath for automation.

As a consultant, we have been involved in many client projects and deployed UiPath using a hybrid model.

UiPath enables us to implement end-to-end automation.

UiPath's User Community is good.

UiPath helped us reduce our on-premises footprint.

UiPath helped us reduce human error.

UiPath's support for various types of interfaces is the most valuable feature as it aids in automating the end-user systems we want to streamline.

I would like to have the ability to make changes at different stages of the development process without having to start from the beginning each time.

Automating with UiPath is not as easy as it appears in the advertisements.

I have been using UiPath for seven years.

UiPath is stable, but not 100 percent reliable. I would rate its stability an eight out of ten. If we need to restart the project, open the file again, or close down the program and open something else, UiPath does not behave consistently every time.

UiPath is highly scalable.

The initial setup is straightforward. The deployment takes around one month.

I give UiPath a seven out of ten.

Maintenance is required. We need to make changes to the code due to updates in the systems on which the automation is running. There are updates in the IT environments, such as operating systems, and also in the UI part. The newer features in UiPath bring new updates, and its components necessitate modifications to the code.

Our primary UiPath use case is reconciling data and getting data from the web and writing to either Excel or our system. The automations are very reliable. 

Task Capture is quite a helpful feature because it is easy to design a process flow with it. All you have to do is just capture it and then do the manual process. It then gives you the process flow and the process definition document, PDD, so it saves you a lot of time.

The database connectors I found are not fully free and expire after 30 days. That is something I would like looked at for MongoDB specifically. With regards to this, I was working on a project that needed a robot to read data from a MongoDB database. To achieve this, I used the CDATA ODBC driver because I couldn't find a direct Activity to achieve this from Studio. See the link to the CDATA ODBC driver for UiPath here https://www.cdata.com/kb/tech/...

It would also be great to have UiPath Insights included in the free Orchestrator. The Insights module is currently only available for paid licenses. It would be great for developers to have it included in the free version because then we could try it out. 

I have been using UiPath since May 2018, and have recently worked with UiPath Process Mining. I am currently not very actively using this tool because the projects I'm on at the moment are using Power Automate. However, I do look at it once in a while.

UiPath is quite stable. I have not seen any inconsistencies come up because even exception handling is well set up in case of bad themes. Transformational processes are well managed, including exceptions, so that adds to the stability. Also, you can scale out from one bot to tens of thousands, so automation is quite easy with UiPath.

Very scalable

The initial UiPath setup is straightforward. You just go on the cloud, create an account, and you get the Orchestrator right away. From there, you can download the Studio. So once you build the automation, you just publish it from the Studio and you can run it. It's a very seamless process.

There is no need to hire an external team. You can do everything yourself. Also, the forum is quite busy and active. You can get a lot of helpful material there.

I cannot give actual figures, but I have seen a return on investment especially in processing invoices. It used to take us a week to read certain invoices into Excel but now it takes us only a day. So we are saving five Mondays in a week and 30 or 40 a month. 

From what I hear, UiPath's licensing costs are a bit high, but I can't evaluate that information because I haven't actually experienced the cost. We are using a free version at the moment. A good thing about the Community Edition is that they allow you to deploy even as a company as long as revenues are below $5 million I think.

I recommend automating the small processes in the Community Edition. This is the best way to evaluate how scaling would go within your organization. 

It is also important to fully understand what you want to automate. I also recommend trying the Process Mining feature to make sure you are able to pick up areas of automation within the organization's processes before committing to paying for automation. 

We primarily use the solution for interactions with customers. For those coming through the contact center, we are automating responses and actions.

The solution has improved the company in that when a customer needs to come in and have a consultation with an agent, it opens up a video conference to actually see the other end of the product, the full consultation, instead of being described over the phone. It makes the meetings much more effective.

One of the most valuable aspects of the solution is that we are able to automate a process that doesn't have an easy API or integration. It’s an easy way to complete an outcome without having to read another application.

I have seen a reduction in human error. The assumptions that agents were making previously via verbal communication compared to actually physically seeing something are now completely different.

UiPath has freed up employees' time. I don’t have the exact metric in relation to that, however. Also, this additional time has enabled employees to focus on higher-value work. We’re not chasing issues that can be seen physically, instead of trying to gain understanding by going back and forth via calling or email or chat.

It’s my understanding that UiPath has saved our organization money.

I have used UiPath's Academy courses. It has helped a lot in terms of helping users to understand the whole process. It goes under the hood to help users figure out how everything gets applied and then how we can write code as well. It gives a solid direction of what it takes to be a good developer.

There are definitely some changes I would like to see. I’d like to see, for example, more note code for applications. Some of the complexity of the scripting is hard. If note code was there, it would be easy to just scale it.

I've been using the solution for five to six months.

The stability so far has been good. We just have got to make sure that we don't change anything on the back end and adjust it. Right now, it's a critical path that we need to be aware of in needing adjustments. It offers a great interchange.

Scalability is good in terms of adding more RPA processes across the board. There's also a question of, when things change and adjust, how it reacts to those changes. Scalability can cause issues.

Right now, the number of people who use it in the organization is small. There are
maybe three or four engineers. It's used at a high level. There are more in-depth engineers that are involved with it.

Technical support has been pretty good for asking questions and giving responses. I'm not sure anyone would get a perfect ten out of ten, however, they are good. To be perfect, support would always have to have an answer and do all the work for me. 

The solution was chosen when I was brought on board. I'm not sure what was used previously.

That said, I am familiar with other RPA solutions. For example, Blue Prison is more foreign to me, compared to UiPath. Automation Anywhere seems very familiar from what I have seen, however, I don't really have a good understanding of all the theory, technically, except in terms of UiPath.

The initial setup started off as straightforward, however, it can easily get complex. For example, not knowing the other applications and what it takes to interact with them will make things a bit more complicated. Also, the APIs versus actually scripting information, especially when you're talking databases or backend reports, et cetera, gets complicated.

Our deployment took three months.

The CTO and development team were involved in the process of implementation.

We deployed the solution ourselves, internally.

We have yet to see an ROI, as we just started using the product.

The pricing, in comparison to others in the market, is fair. 

We don't scale that big. If we scaled larger, we might have different opinions about pricing. 

We have the solution on the cloud. It hasn't affected our footprint too much as we haven't really integrated too much at this point.

We use a mix of attended and unattended automation, however, for the most part, it's attended.

I would advise companies to train as many people as they can through the training portal and provide simple boxes and procedures to execute on things that are scalable components.

I'd rate the solution at a seven out of ten. A perfect ten can't happen. However, I'd rate it at a seven due to the fact that it's got the possibility of the cloud, which is great. While I don't have a problem with scalability, there's an issue around how much more it is going to cost. There's a question around scaling and ROI and if it is worth it. 

We primarily use UiPath for outsourcing. Customers call us when they need extra people to fill positions, on a temporary or permanent basis, similar to a temp agency.

The biggest use case that is running right now is that we get job openings or requests from a lot of different third-party brokerages, customers, clients, vendors, et cetera. They all arrive through different platforms. We get an email saying there's a request, please check it out and let us know if you have someone to fulfill the position, and the request is implemented through UiPath. It's automated. We've created all of the mailbox folders based on the sender and the subject, so we know which customer or which broker it is. Then, we make the email follow a link to the information for the job opening or the inquiry and we put it into our Salesforce system.

There are a couple of smaller use cases as well, where we have task operations that have to be done weekly or daily. Mostly it's reading emails or reading schedules and making changes in files.

The automation of job inquiries has a lot of sufficiency on how we operate as we used to have multiple people need to be available throughout the day to manually check if an email with an inquiry came in, and that would require them to drop work and open the email, check it out and maybe take action immediately. Now that the robot is running and taking care of the need for filtering through all the results for them, employees can stay focused on the other tasks that they have. They don't have to keep an eye on a second monitor every time and drop everything they're doing to read an email only to decide what is relevant or not.

I understand work has to be tested. It hasn't impacted the entire company yet as I've been here a little short of a year now and we haven't made that big of an impact just yet. 

The most valuable aspect of UiPath is the community in terms of the way they open up their platform to the community and make it freely available for people to try and to practice. The amount of feedback from that community makes it very easy for us to get into UiPath and if you're trying something that you've never done before, you at least have some insights. There's almost always someone who has done it before or who has asked the question. I would say the community is one of the biggest extra treats for UiPath. 

From a technical perspective, I like the learning curve in the Studio and in the orchestrator - or the Cloud Platform as they call it now - due to the fact that it's easy to get into. It's easy to grasp the basics and to get started. You can scale up as fast and as far as you'd like or need to for your customer. It can do everything. You don't have to learn everything in advance to be able to work with it. It makes it really approachable.

Building automation can be really easy. The biggest challenge is to find the easy use cases as the use cases in the company can get quite complicated quite fast. That said, using the recorder in the Studio and then converting that to work in a mobile office is quite easy. I started in 2016 or 2017, and between then and now there's been a lot of changes. It's always been easy for developer-minded people to get started. However, now with the introduction of StudioX, it is even more focused on the different users and they have a different entry point for them. What I like about UiPath is that the training is really comprehensive. You can almost just record what you do by hand and then StudioX will translate that into a robot and then you can fine-tune it to make it more robust. Smaller costs can be easier steps. Just press record, do what you do, and then you're able to work with teams. 

Scaling automation without having to pay attention to infrastructure does make my job a lot easier for now. What I do see in companies is when they've taken the first steps and they start to scale up, a lot of them have policies or ways of working in place where they want to stick to the ways that they know. A lot of time I see customers will, in the end, do it by themselves anyway, so they use all of the upscaling functions that are available as they want to do it the way that they always did. 

UiPath enables us to implement end-to-end automation starting with process analysis, then robot building, and finally monitoring of automation. However, while it does facilitate end-to-end automation, it does take a lot of the development and running and monitoring of the robots on itself. That is something that is facilitated really well by UiPath. The process discovery and the analysis is rather newish within UiPath. Maybe it's not as well integrated into the community platform.

At this time, UiPath has helped to minimize our on-premises footprint as it is a cloud-based solution. It's important that the on-premise footprint has been minimized as it makes it easier for us being a small company. We have 160 people working for us in the Netherlands and then a couple in the Caribbean. Bringing new technology in like robotic process automation and then asking from the IT department to get me free service and results of my configuring and have all the discussions about what goes where, how the security works, how to find the work, who gets access, et cetera is easy. This is due to the fact that UiPath is offered on a cloud basis and I don't have to do all that on-site work, which allows me to get to building and talking about RPA quicker. 

The fact that the vendor handles infrastructure, maintenance, and updates saves time for our IT department. It helps us to implement a lot faster. The client companies can have a reliable cloud solution to help them do at least the first steps to get them acquainted with the product. It makes it a lot easier. It helps me a lot, and it helps our customers in starting out as well.

UiPath has decreased the time to value in that since it's cloud-based, I can deliver faster than I would be able to do on-prem. If we have an idea, or if we want to scale up, we can do so faster in the cloud solution than I could on-prem.

The product lowers the overall total cost of ownership by taking care of things such as infrastructure, maintenance, and updates, however, I'm not sure what would happen if we scale up.

The automation Cloud Platform has definitely helped reduce the time it takes to create automation. It brings a lot of things together. It's easy to use for clients and customers. It makes it easy to bring different disciplines together, so I don't need to think about how to reuse my code, or how to explain to the customer, and I don't need to share the processes to be able to release, run, and monitor and to get reports on the results. 

UiPath has reduced human error. There are fewer errors and the processes are less error-prone and once the technology has proven itself within the company, within the customers, people start to trust the robots to do what they do. Employees don't need to check the work that had been done as they know that if the robot reported that it was done correctly, then it was done correctly. In that way, it has saved a lot of time by not having to check anything. 

It has also freed up employee time. It's a three-person team and it saved them a couple of hours a week doing the work that they used to do. It saved them a lot more focus as they didn't have to monitor the email inbox all the time. They were able to apply more focus to the other things that they were doing. That said, it's hard to quantify the gains. However, overall, it has made them happy. That's one guarantee. They absolutely love that they gave the mundane work away to the robot because it was bothering them to be monitoring an email inbox all the time. It's given them the time to focus on cases that match the right people to the right inquiries or openings. I don't have any metrics on it, however, anecdotally, they tell me that it helped them to do the rest of their work better as they could apply more focus to more important tasks and placements are better attended to. There's much more focus and attention and better matches being made.

The solution has saved costs for our organization.

I'm trying not to sound negative about it as I like them a lot, however, the process mining and the process mining features stem further away from the development of the robots and the monitoring. The development, run, and monitoring are really closely knit, or really close together, and then process discovery is starting to get there. It's on its way, however, I don't see that it's as closely connected as the other three parts.

The automation operations have not brought down any company costs. Automation operations have gotten more expensive due to the fact that we added UiPath to them. That said, you do get gains at a different branch of the company. We didn't replace anything with UiPath. We weren't able to skip a step or program or tool, which makes it an added cost.

More documentation would be helpful, as they change rather quickly. There are two yearly stable releases and then a couple of community releases and data releases in between. Sometimes not all documentation is changed as quickly as the features are. Sometimes you can find something in the documentation that is not the answer, or not available in the product anymore. That's simply a side effect of how fast they develop the product. 

Sometimes it's not entirely clear what features are, for example, available in their community edition, or in the on-prem, or in the cloud. The difference between the on-prem and the cloud has become clearer in the past few weeks, however.

I've been using the solution for three years now. 

I started out at my previous company with systems integration. We started out with discovering robotic operations, discovering the tools, and suppliers. We chose UiPath and one of the competitors, as we found them to have the best suit with our customers. That was the end of 2016. That's when I started doing training in UiPath and started doing some custom integrations.

Now, I switched to a new job at a different company where they want to start an RPA practice as well and they chose UiPath solely for RPA.

From the operations standpoint, the stability of the cloud it's very good. I haven't had any issues with stability. The Studio will crash at random times. I've identified two scenarios where I'm able to make the Studio crash every time by just doing the same actions.

However, other than that, the automation was really stable, and I haven't had any issues or incidents. In Studio, I'd say it is good enough, however, there is some room for growth there.

Scaling automation without having to pay attention to infrastructure is a bit pro for UiPath as I'm starting an RPA practice. We don't have a lot of infrastructure engineers to build the project yet. Therefore, a lot of the time, with new customers as well, it will be a bit of a one-man show. Yet, what we can do is communicate to the platform and then make sure the infrastructure is there and then implement the platform and build a business analysis basically in an un-built realm. I have to do a lot of things by myself, so the fact that UiPath brings in the Cloud Platform and the Studio and it's all integrated and you can scale up without having to have too much. You need to know something about infrastructure to understand what it does for you, however, you don't have to do it all by hand. I don't need like three or four DP-trained individuals to be able to scale up or scale out. It's helped me get further faster.

Once you build the infrastructure and you know what you're doing and you know where you want to go with your platform and scaling, it's rather easy.

The only people really using it at this time are me and six trainees. There are a couple of ops people as well that are able to log in. We might have a total of ten people on the solution.

It's not being used too extensively now, however, that's for a large part due to the fact that most of my colleagues are working with our customers, so there are not too many internal processes or tasks. However, we do have plans to increase its priority as the tasks that we do have are at some points largely repetitive. We do a lot of operations and maintenance for our customers as well in different fields, so we are mainly looking at that for further automation opportunities.

Technical support has been pretty good. 

I get a quick response and it's usually constructive. I manage to fix my own problems a lot of the time using the community forums and information from there. I haven't had too much interaction with UiPath tech support.

We did not previously use a different solution. 

I personally implemented the solution at my company. 

We currently have it running, so some internal processes. And, we're looking to expand that into the customer landscape.

The setup is simple. They deliver it in a cloud environment, I didn't need to do any installs or make any arrangements.

You need to make an account and get started and watch a couple of training videos that will help you through it. The adding of the robots is very well documented in the forum, in the community, and in the training sessions. They have made it really easy to get started and to get the information you need to take the first step.

The deployment question is a tough one as I started out at this company while already having a communicators subscription on my own account. Therefore, I started out using that one and then gradually shifted toward using more automated resources. I don't have a clear overview of how much time it took to deploy. It might have been a couple of weeks overall, however, I was doing different things at the same time, and I never took a metric of how much time it took. I'd say starting out if the prerequisites are in place at the company, it could be a matter of days.

Tasks such as setting up an account, getting some service, et cetera, if you know what you're doing and you know what to ask a few questions before starting, it's a couple of minutes or hours. That said, in reality, there are always things you forget or things that they didn't do, so it always takes a little extra time.  

My implementation strategy was basically to figure it out as I went, which is not the best strategy, however, it was the best we could do due to the fact that the company didn't really know what they wanted to do with RPA. I was figuring out my own place in the company and then their wishes with robotics with RPA. There were a lot of things at the same time, so there was not a closed strategy other than to start up quickly, as soon as possible, get feedback, and then try again.

For now, I alone handle deployment and maintenance tasks. That will be the case until our trainees finish training.

We did not use a third-party service such as an integrator or a consultant.

We have not yet seen an ROI and have no concrete plans for any in the near future.

While I have one or two sheets from old presentations that have pricing information, they are over a half year old. I have no current insights. I wasn't included in discussions between the company and UiPath in relation to licensing. 

The company might have looked at other options. However, they did this before I was hired. Ultimately, they did want to choose UiPath, and I was hired based on my experience with the product. They chose UiPath at that time as they were working together with Oracle and that company has always been very Oracle-minded.

I use the community Studio and the Cloud Platform. I take the cloud from UiPath. I'm not sure where they host their solutions. I use the automation cloud from UiPath.

End-to-end coverage is not too important to my work at this time. Maybe if they were more closely integrated, I would be able to offer it more easily to my customers. However, now, due to the fact that I often go in at the first interaction with a customer or at a company, I have to introduce the concept of RPA, I have to introduce the product of UiPath, and I have to introduce or orchestrate the Cloud Platform and Studio. What I've seen is that that's enough for the first steps, usually, the company will have a pretty clear vision of what they want to start out with in terms of automation. However, introducing the process mining capabilities would add an extra step to the start-up that we have to do and what they want to see is faster results in the early phase. It's short the time from when I come in to initiate the first value, so they can appreciate the value and start the business cases and go from there. Maybe, once they are a couple of steps further on and they have a couple of automations, then they go look at the process of task mining as they have the infrastructure, they understand what the process automation is about, and then they start to see the value process or task mining. Therefore, the end-to-end factor, for my job, for now, is not too important as I don't truly use the end-to-end approach. I do the start by myself with the customer and then we go from there. Then, in the next phase, I will build them practices and they will start to automate the beginning of the process discovery as well. There is not something that I have initially do. Once companies start beyond that first phase and the first steps, then process discovery and process mining can be really important in automation. In a later stage, it becomes more important. However, in my case, I work a lot in the early phases and haven't seen too much of the process discovery products in that phase.

Attended automation hasn't really helped us scale RPA benefits as we are a rather small company and there's only a small group that works with the product, and therefore, we haven't been able to use the assistance in the same way a larger organization such as a bank or insurance company might use it.

We don't use the staff solution yet and we have not taken advantage of the AI functionality. While I have played with AI, I haven't had any use cases to implement the AI sensor.

Overall, I am quite satisfied with the product.

I'd advise new users to start by doing instead of only reading. Start small, like finding small processes or if you're an individual, look at your own work. Find something you could do and automate that as it gives you the best appreciation of the value. Try it out in your own environment and just explore how it goes as that gives you the best insights. For me, when I started, it was a great feeling to watch your screen and watch your cursor follow the screen without doing anything. 

Keep asking questions when talking to users. When translating the biggest use case into other processes, spend more and more time talking to the users and going through the processes, and defining and understanding what happens. Otherwise, it's going to cost you a lot of extra time figuring out why you've got all these weird exceptions that you didn't expect. Everyone always talks about how easy robotic process automation is. However, only once you understand your processes from a user's perspective, you'll run into a wall. It's never standardized. It's never the same. I need to warn my customers more frequently about this pitfall, due to the fact that, yes ultimately, it's very fast, but it only is once you know exactly what you want to automate and that's why most of the time it's time-consuming.

I'd rate the solution at a nine out of ten.

I'm using the product primarily for building automation projects for shared services users. It's for internal customers. It's a shared services center for finance, HR, IT, and all processes like that.

UiPath enables you to implement end-to-end automation starting with process analysis, then robot building, and finally the monitoring of automation.

I use UiPath mainly for building a robot. I always use unattended bots. However, I also use it for task capture. I use the Task Capture feature a lot. It's pretty much a game-changer since Task Capture has become available, as creating documentation takes a lot less time than before. As for UiPath, I'm using it for building a solution and then testing using not only UiPath but also Orchestrator. In the end, we also use some document templates from UiPath. It's pretty much present all the way through the life of a project.

UiPath has sped up or reduced the cost of digital transformation in our organization.

For me as a professional developer, this is an obvious fact, however, people can notice that the robot can do their job a lot faster and they can concentrate on completely different things. They don't have to do simple tasks, repetitive tasks, and that's when they realize that this transformation is happening. Some people did not believe that it would happen so fast, yet, by using UiPath, we can prove to user that a process can be transformed into an automated one in a really short time.

It's reduced human errors in our company as well. I can use an example as a VAT declaration. That's one error that would cause some financial consequence for our business. After creating an automated project process, it is impossible for a declaration to be submitted with an error. It's basically eliminated typos or human errors in the case of VAT declarations and financial consequences.

The solution has freed up employee time. It's difficult to estimate how much as there are a lot of projects and I'm not the only developer on. However, thanks to my bots, we could free up, so far in half a year in this company, two FTEs, two full-time employees. Obviously, it doesn't mean that these people were let off. They are doing their job, however, they've just got different tasks, more complex tasks to do.

Mostly I'm using Studio. This is my main tool for work, and, for Studio, I can say that this is my favorite out of all the automation platforms. 

I like the fact that you can use and customize activities from the marketplace. The fact that even though the built-in activity sometimes cannot cope with some tasks, you can still find solutions outside of UiPath, internal kinds of built-in functions. You can use the third-party package marketplace. 

I like the way it handles debugging as it's very comfortable and it keeps the project under control. 

I'm also using Orchestrator. The newer version of Orchestrator is really very user-friendly and it's easy to manage projects there.

For basic automation, it's very easy to learn and it's easy to use. It's intuitive for basic functions. However, for more complicated automation, it gets more complicated. This is expected. The more advanced the project, the more advanced the skills you need. That said, as a basic product for simple automation, it's very easy to use.

The solution is user-friendly and has great training materials available.

I use the solution for automating my own work sometimes. I work at building small robots to make work go faster. For example, I'll create a robot that will help to create documentation. For example, analyzing arguments and workflows inside a project and outputting them in a DXC file or things like that. It's small ad hoc automation that makes life easier.

At the moment, I'm pretty satisfied with it. Thinking about UiPath, I can't see any downsides and the downsides are in like companies' infrastructure.

At this point, debugging, for me, is lacking the ability to edit on the go. It lacks the ability to stop the process on a breakpoint and being able to edit or even go a step back. At the moment when I'm debugging I'm only able to stop the process, check the locals etc. It is not possible to change anything in the code, go step back and try the changed code. You have to start the debugging process from the beginning. It is just slightly annoying and it was there since I started with version 2016. It's not a showstopper at all, just adds some time to development. I'm not even sure it could be done technically, it's just a wish.

I've been using the solution for about four years at this point. I've used it for a while. 

There are occasional errors happening, which cause the software to freeze up. However, this is not more than once every two weeks and I'm always able to recover the project. I would say it's stable. Regarding working automation, I also have no problems as the errors that we have on ready robots never result from UiPath's issues. They result more often from infrastructure issues or robot problems.

Regarding UiPath scalability, it's great. It's one of the biggest advantages. Over the years, you're able to build a library of modules that sometimes make your work a lot faster. You can use a few modules and you will have 70% of the project done. Every module that you work on, which is new and can be reusable, is very easy to make into libraries and to reuse.

In my organization, closest to me, there are only about five or six people on the solution. However, we also use external contractors and consultants who use UiPath and there are even UiPath MVPs there. That said, in my company, it's only developers, operators, and a project manager.

We have plans to employ more developers and to increase usage. 

We have an RPA department, which is using it and it's cooperating with all other departments in terms of creating automation. We have specialists that are specializing in using UiPath for automation. We create automation projects for every department that requires it. The people who are using UiPath are using it pretty much full-time. It's a full-time development. We are planning to increase the size of the development team as the projects are flowing and the backlog is growing. From the business side of our company, the satisfaction is high. The demand is growing.

The solution has exceeded my expectations over the last few months and technical support overall has been great. The way they approach customer service and help us through issues has been great.

The initial setup is pretty straightforward. I'm not a system admin or anything like that and I was able to set up UiPath on the server. It's pretty good.

How long it takes depends on the database that I'm working on. That said, last time it was not even the one full working day. It depends on how much data you have to back up. Usually, it's a few hours.

While I'm not the correct person to ask about ROI, I can say that UiPath has reduced the cost of our automation operations by making it 30% faster. 

I don't know the exact prices, however, I know that compared to other companies, other solutions, it's the best value for money, at least in our country.

I tried Automation Anywhere and also Blue Prism. At that time, there were only these three available for us. That was four years ago.

We are customers and end-users of the solution.

We use the enterprise edition of the solution.

At the moment we are not using the newest version. It's 2019.

It was not my choice to use UiPath. At the beginning of my automation career, it was chosen for me. However, I was able to test other automation software and give my feedback to the employer and UiPath was the winner for me. At that time I was a finance worker. I was not a developer, a professional developer yet. For me, it was the user-friendliness and the way that you could very easily start your adventure with it, and then learn as you go. I have to say that the training packages for UiPath were very good and are enough to make you start working with it.

In my experience, I would say that it is the best platform for people who are willing to learn to automate. Also, if you want to use automation software, you have to consider hiring someone who has experience in it. Even though UiPath is so user-friendly and so intuitive, you still need to have a professional who has some experience.

It's very important to educate people to make them aware of what the RPA is. To be honest, from my experience, humans are the weakest link here, and people who are submitting, for example, input data for robots, cause the most problems. It is important to invest in the education of people and to raise awareness about RPA. 

I'd rate the solution at a ten out of ten.

I am currently involved in healthcare-related projects and wholesale/retail-related projects. Previously, I was involved with banking and financial services, healthcare, and retail.

My current company is using a combination of the UiPath tool and SAP automation.

In my previous company, I used the UiPath tool for many projects.

It has a very easy drag and drop process and logic base setup. Previous projects were taking a lot of time. However, when we used UiPath on the same projects, instead of a process/task taking a day, it was now taking anywhere from 10 minutes to five hours.

There is almost no human involvement. For example, in banks, a bank manager will receive so many loan applications. We create some bots to check the requirements after validation and do the follow-up work. The manager is only checking boxes for the final approval request.

In the banking sector, I am using AI Center and creating some workflows. Some machine learning is needed to create these workflows in AI Center. This gives us a 94% accuracy, which is good accuracy.

Document Understanding is a good feature. It is a combination of artificial intelligence and machine learning. We have created some workflows using Document Understanding. We are using its machine learning to do some language analysis, semantic analysis, and invoice processing. UiPath currently provides some language conversions, such as German to Russia and Russian to German. However, it does not offer Russian to German, English to German, German to English, Russian to English, and English to Russian as well as some non-trainable languages.

Document Understanding has been one of the best features for invoice processing. For example, companies require some keywords in invoices. While normal frameworks take much of time, we upload the invoices using Document Understanding, then determine the keywords required for cross referencing. The cross reference is very fast. It will capture the amount and put that in an Excel format. This is a very good feature.

A valuable feature of UiPath has been the REFramework. In banking, we need to log in to the website with a user ID and password. Once, we did that wrong and the workflow stopped. Using REFramework, there is exception handling. Stability depends on the correct configuration of error handling, so this is the best feature. 

It has some Citrix recording options.

The AI Center feature has been very good. It supports many machine learning languages and skills. It speeds execution and provides a good savings on time.

I like the certifications offered by UiPath Academy.

I would like UiPath to give free trial licenses for more features, like AI Center. UiPath currently offers two licenses for the trial version. However, if I need to practice in AI Center, then I need four to six licenses.

I have been using UiPath since 2018.

The stability is very good.

There are no limitations for Windows.

We have over 500 activities in UiPath right now.

I haven't used the technical support so much. My colleagues use it sometimes, depending on their problem. The speed of their response depends on the type of plan, normal or enterprise, that needs support. I would rate them as 10 out of 10.

There is also social media support through Twitter and LinkedIn.

The user community is very good. I am a member. If a developer has any doubts when working on a project, then a lot of people in the community are ready to give immediate answers.

Positive

We have faced challenges when installing market-related data. We need to dig deep when we are installing it with Orchestrator and/or VMware. All the documentation is available, but it needs to be prepared in advance. Whereas, we work in real-time.

I have been involved with many client installations for UiPath and Orchestrator. We do standalone installations for single node and multi-node systems, like Linux. Linux is not fully supported, as compared to Windows. UiPath deploys well on Windows.

My previous company had good ROI using UiPath compared to other tools.

UiPath Academy is free of cost.

The UiPath Community Edition is enough to implement any complex workflows.

The price for attended robots is good.

Some features are very costly, like Document Understanding. That is why in India many customers are not using the Document Understanding license. This is a premium feature and its licensing costs are high compared to other tools.

Compared to other tools, UiPath provides a good, rich environment.

I am using AutomationEdge, which is similar to UiPath, but a small tool. It provides the same features as UiPath, but it is not as popular a tool. The UiPath Academy videos are very good and better than those offered by AutomationEdge. While AutomationEdge also has a free learning course, you must watch their videos from start to finish. UiPath has no restrictions on its learning, which is good and the best option. For example, when you are an advanced learner, you want to go to advanced training courses. However, AutomationEdge makes you start from scratch, even as an advanced user of RPA.

Some processes are faster in AutomationEdge than in UiPath for insurance-related organizations.

I am also using Automation Anywhere, which is a popular tool in comparison to UiPath. However, feature-wise, UiPath is easier to use because Automation Anywhere requires complicated coding knowledge, though some of their features are very good. While UiPath requires some coding knowledge, it is not as high level as Automation Anywhere.

UiPath is the number one tool in my opinion. I would recommend choosing UiPath for someone looking to purchase an automation tool for the first time.

UiPath has very good accuracy. I would overall rate this solution as 10 out of 10.

I am an RPA developer and I am using UiPath to create both attended and unattended bots.

I develop bots that run doing overnight tasks and we can check the results in the morning.

UiPath allows us to scale without having to worry about the infrastructure. It is simple to scale any of the automations that you develop. 

UiPath makes it easy to build automations. It is very user-friendly and they provide all of the courses in the UiPath Academy. We can learn starting with the basics, and it is really simple. One person needs between two weeks and one month to learn it.

This solution provides us with the ability to do end-to-end automation, starting with the discovery phase and process mining. After that, we move to the building page where we have Studio X, and then we can deploy the automation on the cloud.

UiPath has helped us to scale RPA benefits by automating the backup of all of the projects running in the organization. This bot runs every night and reduces our workload for one employee by eight hours, or one day each week. 

UiPath handles all of the infrastructure updates and maintenance, which is really good.

The cloud offering has helped us to see time to value quicker. It has helped us in many ways, including with the automation of repeated tasks. One example is that I created a bot for myself that is responsible for filtering all of the spam emails from my inbox on a daily basis, and then removing them. The first step is the identification and the second step is removing them. This saves me time.

The automation cloud has helped us to reduce the total cost of ownership because we can manage everything through Orchestrator.

UiPath has definitely reduced the percentage of human errors that we have in our processes. In our system, all of the bots follow our best practices so there is a very small chance of error. The reduction in error rate depends on the process. For example, the OCR is not very accurate so the errors are higher but if the process involves an API or SQL queries then it is very good.

This product has helped to reduce the cost of our automation operations. There is more of an upfront cost but it is one-time, and then we start saving.

The best feature is the good community support that is provided in the UiPath forum.

I like that it is a cloud version and runs on Citrix. I used the cloud offering to deploy my bots and manage my Orchestrators.

It would be very helpful for us if they provided more business use cases and helped us to learn them.

We have been using UiPath for almost two years.

There are times when you need to shut down the automation and restart it. Other than that, it is very stable.

I am the only one developing the bots but I am currently training some other people who are just learning it.

To this point, we have not had to scale any of our projects. Our usage of it depends on the project and where we can use automation.

When other features and updates are released, we normally visit the forum to help understand them. I have never used technical support.

I have also tried using Automation Anywhere.

Each solution has different types of bots that are available. One of the differences is that with UiPath, you have Orchestrator to help you manage them.

Generally speaking, UiPath is easier to understand.

The initial setup is not complex. It is easy to deploy and the actual setup of UiPath is not very difficult. It is a matter of downloading the Studio and creating an account in the Orchestrator. Then, you can start working.

My IT team was responsible for the initial setup. Only one person was needed to complete it.

I take care of all of the maintenance.

I am using the Community Edition and am not familiar with the cost of the paid editions.

We do not yet use the AI functionality but I know that it is there.

I have watched some videos on the UiPath apps feature, which lets us create automations in a low-code/no-code fashion. We have not used it yet but this is something that we'll be exploring in the future.

The biggest lesson that I learned from using this solution is that they have a very good community forum, where you can share ideas and learn from other RPA developers.

My advice for anybody who is implementing this product is to start by taking the fundamental UiPath courses from the UiPath Academy. This will help to understand RPA and UiPath.

In summary, this is a good product and I'm quite satisfied with all of the functionality that it provides.

I would rate this solution a nine out of ten.

We used to maintain a lot of Excel sheets for lead generation and other activities. UiPath helped us to automate those processes and clear our workloads so that we could focus on other main tasks.

It saved a lot of time on tasks that could be quite redundant. Fetching data and maintaining the machines and regularly updating them. That's the only thing that I was using it for. Using UiPath saved me about 10 to 12 hours on a weekly basis.

It allowed me to delegate mundane tasks to personal automations and to focus on more important tasks. By not having to do tasks that don't add value or skills, I could focus on tasks that were more important and that added value to my skills or targets. That brings much more satisfaction.

Also, the ability for employees to delegate mundane tasks to personal automations meant that we did not have to hire a person dedicated to doing those particular tasks. We could use the tool to do those tasks. It helped save those costs. On that front it helped in business operations.

UiPath was quite useful in terms of getting data from thousands of webpages online and arranging it in a predefined format. You can easily create robots and define operations in UiPath.

I come from a non-technical background. You need a little bit of technical knowledge to use it. We had a demonstration of how to use the platform, but it's easy to use. It helps in automating tasks which otherwise you would have to do manually.

The desktop Assistant tool provides a personal automation launchpad so that you can easily access and run automations. That's important because you don't have to go to someone every time you face a problem, or every time you have to run an automation process. It helps make you independent so that you can do your own tasks.

Other things I like about it include:

• Its dashboard is quite easy to use and you don’t need to have a programming background to understand it.
• You can record screens in Excel and download it from the cloud.
• You can also get quite a load of data from the web and use it for your processes without any manual effort.
  

For me, it was quite an effective tool because I hadn't used any automation tool previously. It was quite new for me and it took time to adjust to it and understand it. At times, some processes took longer with the tool, initially. But when you do them on a regular basis, you understand it better and it takes much less time. Setting up the systems could be difficult initially. It would be better if it were more user-friendly for non-technical users.

I used UiPath for less than one year.

It's quite stable and reliable. We had no issues.

I wasn't involved in the initial setup of UiPath in our organization, but I think it took less than a month to deploy it. It's also an ongoing process after deployment. There are a lot of things that need to be done.

About 10 to 15 people were using it in our organization. The users were mainly in IT where they were using it for central management and other automation purposes.

The fact that we didn't have to hire a resource specifically for doing certain tasks is how the ROI could be calculated. It also saved time for the existing employees.

There is a trial version available. You can go for the trial version first and then buy it and scale it per your needs. Try this tool. Go for it. It's definitely worth a try. If yours is a large organization, try the Community Edition first to get the hang of it. After that, move on to its Enterprise version.

What I learned from using UiPath is that there are tools available in the market that can essentially make your life a lot easier. You don't have to worry about doing certain tasks, maintaining them, continuously updating them. Their backups are always available, even if you lose something. They are always easily accessible on any device.

We use it for financial use cases: purchase-to-pay processes, reconciliation processes, vendor payment, and merchant payments. This is just in finance. Then, we have retail order processing, order creation, PO generation, delivery note generation, and all those things in retail. We even have banking processes as well, such as a payments portal. We use it in most of the fields.

We don't use cloud licenses. Most of our licenses are on-prem.

We use both attended and unattended automation in UiPath.

We are partnered with UiPath. Sometimes, UiPath refers customers to us, bringing us business. We also give them business.

We have a third-party order processing portal, which keeps on changing its UI very often and has elements that keep on shuffling between the metadata. What we had in this case was the script running was shuffling the elements, and we are disabled that thing. Then, we used the selector technology instead. Selector technology is very important for all our UI-based processes. We rely on it. 

We used the AI Fabric functionality in one of our projects. We had to categorize users' reviews based on the sentiment scores. Everything was already available, including the model. So, we just have to click on all those things from UiPath now.

The new features that they are adding in, these are very different from other RPA tools in the market:

• AI Fabric
• Integration with different data models
• You can do all the data processing, data mining, etc., in the back-end UiPath. 
• You don't need a separate tool for data mining or other cognitive abilities. You can do all the cognitive abilities in UiPath. 
• UiPath Apps, which they're bringing in just now, is a really good thing. It has a good user interface.

Most RPA tools do not directly have these features. Also, we don't have to rely on other tools in order to develop these things. We can directly develop and integrate them with UiPath on one platform. So, we don't have to struggle within multiple platforms.

UiPath Apps is available only on Community. So, this was a best case scenario for us. It was pretty good. The only thing is that it has to be more advanced. Now, it is very basic. I would like more integration with the UI elements. It should be more user-friendly, especially if we go for any other application development. For example, in other UI development platforms, you can easily drag and drop to develop in a UI. However, it is a very initial phase for UiPath Apps, and maybe in the future, they might improve this.

We have used the Picture in Picture functionality for a few attended automations, where the user is monitoring or we are installing a new interface. Sometimes, in my experience, Picture In Picture is a bit buggy. It takes over your control, then the controls get mixed. That is one of few issues that I have found. Other than that, Picture In Picture works pretty well.

I had an instance when UiPath crashed on my computer. Then, the code that I was working on also crashed. This was a very crucial process for us, but we apparently didn't have a backup. UiPath also didn't have any way to recover that code. This was something which I found very strange, because ideally the source company should have a mainframe where they can recover a code. Or, if I give them a corrupted damage file, then they could easily recover that code. 

The stability is pretty good when we follow the best practices, i.e., whatever is in the REFramework. 

Scalability is something that we are still figuring out. RPA is something which we cannot do for everything, because there is a small gap between profit and the cost.

The support has been pretty good so far. The response time could improve, then it would be much better. However, once we get a ticket assigned to a technical person, then it is pretty straightforward. They are very fast, know their job, and know how to resolve the issue.

The on-prem setup is straightforward. There is very detailed documentation. We always get support from UiPath, so it is not difficult. I have never faced any issues, but I have only deployed on a small scale.

The timeline of the project depends on the project's complexity. Usually, the due diligence and everything else takes about two or three weeks. Then, the design takes another one or two weeks before we start with the development, depending on the inputs.

I get involved with small client setups.

There is a client-facing team of around 25 people who do due diligence and design work. There is also our back-end/technical delivery team, which includes mostly developers, a product project manager, project owner, and developer lead, who are there mostly for their technical abilities, not for their design abilities. 

The price of Orchestrator is pretty high in general as well as compared to other solutions, because Automation Anywhere does not charge for its Control Room.

We can develop our own packages and integrate them, which is pretty good. Other tools don't have that.

There are a lot of cons with Automation Anywhere, which we are using. They deployed a new version, 2019, which is very buggy, and they are still working on that. I don't know how or why they released it to the public. They did so much testing, but it is still buggy.

Power Automate (previously Softomotive) needs to improve on its UI. The ease of use is not there with this solution.

Go for it. It is a pretty good tool, which is straightforward and easy to use. They have training in place. Even if you are new to it, you can go ahead and learn to do it. 

They are bringing in new things. You can automate, integrate, and test things. It is even used for mobile testing. It is pretty good in that case. For most of people's use cases, UiPath will suffice for their use cases.

I would rate the solution as an eight (out of 10). 

RPA - Novigo Automation Framework Solutions - Setup an Automation Factory Model.

Automation Focus has been Productivity, Quality, Cost, Process Optimization, and compliance.

Focused on delivering Process Automation for Oracle EBS ERP application for various departments including IT, Finance, Operations, Engineering, Sales .etc 

1. Manufacturing: Master data maintenance & monitoring Inventory transactions, BOM error fix & transfer, WIP issue & complacent
2. Finance: Financial closing, IC transaction, security & FA master & transactions, Master data, duplicate check, auto-CM creation & auto-payment, Customer Master, running letter, print errors & auto-receipts
3. Supply Chain: Sales order Integration with the portal, shipment, RMA, digital shipping & backorder, item cost update & inventory interface, procurement, receiving & monitoring
4. System Admin: Access provisioning, - Creating responsibility, Monitoring pending transaction & analyzer.

RPA Automation has accelerated heavily within the organization. 

It started with task automation and ended up with process automation.

• Increased Operational excellence - With multiple FTE savings every month.
• Lowered operational cost with a minimum saving of 780+ Man hours every month.
• Overall $1 million annual savings through improved process efficiency.
• Increased Shipping Order execution velocity by 2x times -At least 10,000 orders in every 4 days.
• Amplified shipping process efficiency and employee productivity by 100% - with one click execution.
• ABCDi (AnyBody Can Do it) technique enables Zero dependencies on SME requirement to perform the task and Zero dollars spend on training the Shipping operators.
• Prevents human error, increases data accuracy, standardization, and quality of data for the shipping process.
• Excellent ROI with investment cost recovered in 1.25 months timeline and an Annualized ROI for 5 years is 68.50%
• Built from LTI Novigo Automation Framework, it provides the agility and speed required to customize and deploy the solution quickly.

• Attended Bots have been star cases as it totally removes dependencies of user literacy to know the application. 
• ABCDi (AnyBody Can Do it) technique enables Zero dependencies on SME requirement to perform the task and Zero dollars spend on training the Shipping operators.
• With Novigo Automation Framework, the implementation lifecycle is accelerated by about 25%-to-32%, while drastically reducing the implementation services cost. Identification of possible use cases along with efforts required, time involved, and cost savings can be easily envisioned by using NAF.

• RPA AI capabilities - UiPath is leading in this area.
• UiPath should focus more on recommendations of process automation based on ERP Applications like Oracle, SAP etc. They should also provide a list of possible RPA cases as per departments, processes and based on various industry domains. 
• More on RPA Governance features to be provided out of the box. 
• RPA Capabilities with IVR Channels to address voice commands will be a game changer for Customer call center cases.                                                                               

We have been using UiPath for two years.

Excellent in stability. 

Easily scalable in a few minutes.

No.

UiPath Cloud Orchestrator setup is pretty must straightforward, we manage to do a complete setup in a matter of a few hours time.

We deployed it in-house - SI - LTI.

>30% ROI  - we recovery of overall investments recovered in seven months' time.

UiPath is very cost-effective.

Yes, we have evaluated all top RPA products like Automation Anywhere and Blue Prism.