UiPath Platform Reviews

We're using UiPath on the customer side, where we have lots of data and PPs on the customer information. We're trying to put in what the customer is including, and then using machine learning. We created a Python type of UiPath to do machine learning and automatically build that so that items can be automated. That was our POC. That said, we're exploring more, to get into the finance area, where we can take invoicing and general revenues and the closing worksheets and automate those processes.

The biggest improvement has been in the ROI we've seen, which has been $55,000 in six months' time. 

The whole bot process and the way scheduling is done is a very valuable aspect of the solution and it's really cool.

In terms of the ease of building automation using the solution, we’re very near achieving that. It's taking more time than what it's supposed to be taking, however, I don't see any complexity in building the code nicely.

So far, the solution has saved costs for our organization.

I’m not sure if the solution has reduced human error. It’s hard to tell at this point. We’re in the early stages. However, simply by looking at the way it’s built, it will.

The solution has freed up employee time. Once again, it’s too early to say too much, however, we are saving approximately 130 hours per month. This additional time has enabled employees to focus on higher-value work. They don't need to just go to the system to click here and there, they're spending more time with the customer.

The management team is more satisfied as it’s much cleaner, with less human error. Management reporting shows definite improvement. In terms of overall employee satisfaction, employees are still not quite trusting the bot. The bot does something and they will go and still validate that. They don't have a hundred percent trust yet. That's what we are trying to build right now.

We have used UiPath Academy courses. It's taking time due to the fact that we have a consulting partner who's helping us. The majority of the workload is being handled by the consulting partner. We're trying to play just the B role of supporting. We're not doing too much development.

That said, with UiPath Academy, just the ease of accessing the material has been great. It's simple.

The only thing which I see is missing, is it does not have an inbuilt machine learning. You have to teach the bot. The bot is not self-learning.

For example, right now, we are using a description. Based on the fields or the description, we're trying to identify what is the category to be used. I have data for the last five years. The bot should be able to go and learn by itself tasks such as "These are the five things which I need to add," instead of me manually maintaining it.

I've been using the solution for six months.

The solution is stable. I don't see any problems.

The scalability I still need to figure out. Right now, with the licenses we have, I don't think we're going to scale it out to where we want it to be. It's my understanding that it just involves increasing the number of parts or number of processes which we can run. It will probably be scalable, however, we have not tested that, and therefore I cannot say either way.

We have close to 30 users on the solution right now. It's mostly our customers' manager and their team.

We do plan to increase usage in the future.

Technical support is okay. I have not really invested a lot of time in getting support from UiPath, however, I get a response.

We did not previously use a different RPA. We had a CIO who'd used it before and based on their experience, we went to UiPath.

In terms of the initial setup, the system side is straightforward. It's the business side that took us a lot of time to understand the concept.

The deployment itself took three months.

The company is probably going to need to negotiate. It's competitive right now, however, once we scale it out, there's going to be some room for negotiation. Likely, UiPath will be responsive to negotiations.

We did not evaluate other options before choosing UiPath.

We're likely using the most up-to-date version of the solution, however, I don't know the version number.

We don’t use the solution's AI functionality in our automation program yet.

I'd advise potential new users to go slow. Always create the roadmap first. Take smaller pieces and then implement those. Don't wait too long, however. Otherwise, you will lose user interest.

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

We're the shared services divisions to contact centers and handle back-office work. Most of our use cases with UiPath so far have been automating back-office work, taking information from Excel files, and putting them into legacy systems or some mainframe integrations. All of our robots, as of right now, are unattended automation. We haven't really used the attended robots just yet.

The primary benefit so far has been bringing up and updating other processes so that I can move on to other more valuable processes. I no longer need to copy here and paste there. It's taken the robot part of the job out of my hands. 

I have not actually developed anything with it directly. I manage the people who do. The little bit of training that I did, was pretty straightforward. I was using the rapid development tools. If you truly want to build something that's stable and fast, you really have to get in there and at a much deeper level than I got. That said, from what I did, it looked easy.

UiPath has saved the company costs. With the automation we've had so far, we're probably in the 20 to 30 FTE savings range so far.

The solution has reduced human error. It helps in the sense that, if you take a process of humans doing it and give it to a robot that's always following a set of rules when it encounters a certain value, it's always going to handle it a certain way. It's the consistency that the automation provides that has been great.

I’m not sure if the solution has freed up employee time. That's tough to evaluate due to the fact that the FTE that would have been doing this manual process would just mostly get moved to perform more valuable work. It has freed up time by allowing us to allocate those resources to higher-value tasks.

We have used the UiPath Academy courses. They are all good. We've had developers go through the UiPath training. In fact, that's a requirement when developing. They have to at least complete the training. We have at least one developer that's gone through it completely. It's a fundamental starting point to training people on UiPath. We've taken internal people and they train them ourselves.

We also appreciate the fact that the Academy is free to use. Right off the bat, due to the fact the Academy was free, we were able to say, okay, complete the training. You have to complete the training in order to be able to develop. Right away, it became part of our standard. We see the value in it.

The speed could be improved. In some cases, when I have to ask analysts to estimate how much licensing we need, we have to figure out how long it's going to run, and right now we go with the worst-case scenario, that the robots are going to run no faster than the human. That's been our stereotype. We've used other platforms in the past, where I could perform a transaction to some websites in three seconds, however, for UiPath it was 10 seconds. That was even after we did some enhancements to make UiPath as fast as we could. I know it's the internals with the way that the platforms work, however, from our robot's perspective, speed seems to be a barrier.

We started using the solution in late 2019.

The solution is stable. 

I have not had any direct relationship with the support from UiPath. When I do have a technical issue, I'm to engage with an internal team and they are the ones that have the relationship with UiPath support.

We did use a cloud solution previously. We switched to UiPath on-premises as UiPath's on-prem deployment was more aligned with our security constraints. 

We've had multiple projects. Some have been very complex and others have been perfect. It's dependent on the projects that we're using it for. Some were a little bit more complex.

It's my understanding that, while the company likely did look at other options, I was not engaged in those meetings. While I recall some high-level conversations, they didn't say which ones we were actively evaluating.

I'm not sure which version of the solution we're using. 

I have not used the AI functionality in my automation program yet.

In terms of functionality, UiPath does quite well. The fact that it's not net-based gives it a lot of flexibility to use it in a non-standard way. For example, we were building a robot interface with an Oracle database, and we could either build a robot to open up an access database with blank tables and pull it down. Or we, due to the fact that it did not have access to the net, could grab an in-memory data set and cycle through that. I liked that flexibility and the fact that we had options.

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

We have around more than 300 bots that are active right now. All the automation we have is based, basically, on Oracle and Oracle ERP. We have other automation as well, however, for now, I am focusing only on Oracle-based automation.

We have so many other use cases that we want to implement within our organization. We try to look at how we can save time for our employees so that they can spend their time on other valuable things, and not waste their time on unnecessary time-consuming tasks. 

Our employees use Oracle ERP, so they have to process so many invoices at one time and it takes a lot of time to consume a single invoice. I'd estimate it would take at least 5 to 10 minutes. But with the automation, we can process one invoice within a minute, or maybe less in some situations. It saves a lot of time - likely hundreds of hours for each employee. It saves manpower for the company and saves you valuable time for the employees. They don't have to do the same things again and again and waste their time on that.

For example, if they have to download an invoice and process that for some reason. They have to go to some ERP tool, log it onto that first, type in the information, and then download the invoice. It takes a lot of time. They don't have to do this once or twice, it's hundreds of times due to the fact that they're not for the same couple of invoices. Therefore, this is one of the best use cases that we have for now. We are still looking for other future use cases, but for now, this is the one we have.

UiPath is saving employees hours of time and has also been able to dedicate their free time to more valuable tasks.

The most valuable feature of UiPath is the time-saving employees get. It's definitely sometimes complicated for the developers when they are automating. However, from a business point of view, I would say this is one of the best tools that every organization should have, to help save time and work hours.

Sometimes if you are doing the same task, again and again, we do make mistakes. Automating those tasks removes that human error. Also, with those types of tasks, a human gets annoyed very, very soon if they keep doing one thing again and again. With the help of robots, we can fix it. There is no error with the bot. The only error would be if there is an exception if something is wrong. That said, from a business point of view, when I'm working on a bot, I make sure that it is not throwing any errors and making sure that there are no mistakes. From a development point of view, we can always fix that, however, we don't want our bot to have an error on the production level.

The ease of use and building automation using UiPath is pretty straightforward. It's not complicated. Even a person who is non-technical can become a citizen developer and use StudioX to automate some of the tasks that they think are time-consuming for them. Otherwise, from a developer's point of view, I don't find it complicated. Initially, when a user is learning and at the initial stages of learning RPA, it's definitely complicated, however, once you get used to it, it's pretty straightforward. I love working as an RPA developer.

UiPath has saved costs for our company. I don't have any metrics on the spot, however, I would say it's a big amount of saving. Our organization is very happy that we are using UiPath. We have a few complications right now, however, in a few months we'll fix everything. By next year, when everything is all settled down within our team, then we can start looking at exact metrics in terms of cost savings.

Our teams have used the UiPath Academy courses. I have been using UiPath Academy for a long time. I tend to keep on checking what's new at the Academy. If something new is there, I always try to learn it as soon as possible. If somebody were to ask me "How can we learn UiPath?" The first answer I’d give them is, "Just go to UiPath Academy and follow the learning path over there." That's what I always recommend to any new person.

UiPath Academy courses have positively affected the process of getting employees up to speed in UiPath. It’s helping employees and companies to learn, and I would say it's a one-stop place for anything related to RPA. You don't have to go to other places. You will find everything at UiPath Academy. Sometimes it doesn't have too much detail on the advanced level of things. However, it provides enough information that you learn by experience. If you need more information, you also have access to the UiPath Forum for that.

The biggest value of the courses is that they definitely save time for someone who wants to learn. I don't have to read a book and I don't have to go to any other place or learn from multiple sources. Everything is in one place and I can just follow the learning path and it's a good education in the tool.

Sometimes we don't see what processes can be automated. When we think that, "Okay, we can do that. It's not so time-consuming," however, we can figure it out with the help of UiPath apps and we likely will use them in the future to automate even more.

In terms of improvements, to be honest, I don't have anything I'd want to be added right now. If I have any problems, UiPath is always there. It's easy to find everything. I don't think anything can be improved. It's going very well. It's working for us.

They could always continue to add new features, however, I don't have anything specific in mind right now.

We have been on UiPath for almost more than a year now within our organization.

I'm satisfied with the stability of UiPath. It's good.

UiPath is always there if you want to scale over UiPath-related items. It is scalable.

In terms of who uses the solution, on my team, it's only me who is an RRP developer. That said, every person in the team knows what UiPath is, and they are joining bots onto the system on a daily basis if they have something to do. In the finance department, there are almost 40 to 50 people using UiPath. It might be more. We have more than 300 bots active right now, and I'm not working on all the bots. We definitely have other developers and other people who are working on it in other divisions within the company. 

We also do have plans to create more bots. We are going to use the UiPath apps in the future to see what kind of automation we can do there as well. for example, the Task Capture is a good tool. We haven't used that yet, however, sometime in the future, I would love to set it up for everyone on my finance team and run that application in the backend so that we can see what processes might be automated.

UiPath support is amazing. We talk with someone on a weekly basis. They suggested we use UiPath technical support as we were having a few technical support issues with UiPath and we couldn't figure it out. When I submitted a ticket at UiPath, they were able to answer within a few hours. At maximum, we would get a response in one day. Not more than that.

They also answer with a solution, and the solution always works. I'm very satisfied with them. We don't have to search on the forum and do our own research. We just submit a ticket and once they get back to us, implement the suggested method and after that, it's all good. I'm really, really satisfied with UiPath's level of technical support.

It's my understanding the company did not use a different RPA tool before UiPath.

That said, there are so many automation tools and I do know a few. There's Blue Prism, Automation Anywhere, and Microsoft has their Power Automate. I'm not familiar with all of them as my focus is only on UiPath for now. I haven't used others. I wouldn't be able to compare them. UiPath does seem to be one step ahead, however, as others do not have a free learning academy the way UiPath has. They do not offer a free trial version initially either. That is the best thing UiPath has done from a business point of view.

I was not present for the initial setup of UiPath.

While I do not have an exact ROI metric, it's my understanding that we have saved way more than the solution costs.

For example, if we are spending, for example, $300,000 on the licenses in a year, and we are definitely saving more than $1 million, or maybe more than that. due to the number of hours that we are saving, it's a huge amount of savings we're receiving. 

The pricing is worth it. It's definitely expensive, however, I wouldn't say it's overpriced. The services that we are getting from those licenses help us to save way more than what we are spending.

My managers were telling me that they were comparing which tool to use before choosing UiPath. While I'm not sure what they were looking at, they said they liked UiPath from the first day and that's why they're sticking with UiPath now.

Maybe in the future, we might switch to the cloud, however, for now, we have an on-prem deployment. We're using the most recent version of the product.

We do not use UiPath's AI functionality in our organization yet. We are not using all the UiPath apps right now.

My advice to potential new users is that the first thing that they should do is they should go to the Academy just to get familiar with the tool and how they can use it. Then, move through to the next steps.

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

Our primary use cases are in our financial department. We had a bit of a downturn, but we still had work that needed to be completed. So we developed several automations to manage a lot of the financial work and a lot of our payment processing systems. We expanded that out to include more of our traders' work processes, just because we saw there were a lot of workloads coming in and a lot of repetitive work. So we used UiPath to eliminate a lot of that for our commercial traders, then we did the same thing for our operations and production teams so that they have their own automated processes.

We plan on scaling it and using it in more functions.

Our biggest metrics are in our financial org, they have more of a cost avoidance where we don't have to backfill those positions. It's around $2 million a year because we don't have to bring in personnel to complete the processes.

It has helped solve certain human errors but that's an unintended bonus because we're automating a process as it is that a machine is going to repeat. We don't really have a person to do it.

UiPath has helped to free up employee time. The additional time enabled us to focus on higher-value work. By removing a lot of the repetitive work, it's given them the ability to do more analytics and to dive into the data science realms of their job to do more data-driven analysis of what they're doing.

The ability to do citizen development is the most valuable feature. That initiative has helped us to expand it because that gives folks that are closer to the business the ability to develop their own solutions that are tailored to what they need to do, as opposed to waiting for someone in IT to contact them to build it out. Or to wait for a business analyst to provide some type of value metric, but they can actually go and build it themselves.

My job is to actually be the evangelist to these groups. I'd say we've been pretty successful. My developers are working with the citizen developers who help to guide them and to teach them how to build their own automations for their business process.

It's pretty easy to build automation. The no-code process has really driven the adoption by the business people so that they don't have to skill up and learn how to code anything. They only need to know how to click a button and build it out. That's the best component.

We used the UiPath Academy course. It's our training regimen for our business users. We have to introduce them first to the platform and understand how to work through the platform. It's a pretty straightforward and easy course. With our citizen development program, we also have the Academy where they can either do hands-on learning or use the Academy to get some video training as well.

The biggest value of the Academy is the ease of being able to access the training. 

Governance has room for improvement but that's more of a cultural thing. It depends on your company. We have the reference architecture that we have in place, but it's easy for someone to say, "Okay, I need to make an adjustment here outside of that reference architecture." Because it's so easy for them to do that, they leave the company now that a non-compliant bot is out there running a production process, we need to be able to rank that in. There needs to be footwork that we have to do as an organization for my team as opposed to a true problem with the platform.

We have been using UiPath for around five years now. It's the on-prem version, but we have it deployed in the cloud in our Azure tenant. We started on-prem then we migrated it about three years ago.

It's pretty stable. It's more of the architecture and how it runs because it has to leverage VDIs and as Microsoft releases an update, we have to be watching that process because it'll make the box really brittle. Any change to the UI anywhere will break and that's where we have to step in and fix it.

Every corner of the business except for folks out in the field uses UiPath. It's around 200 people or so.

We've had a little bit of back and forth whenever we have an issue and some of the solutions we got back were pretty boilerplate-type answers. We had an issue with a Microsoft update. They said, "Well, could you potentially reach out to Microsoft and have them let you know." 

They're just going to release the update. We need to be a little bit more proactive on the software side. Our account executive took care of it for us. He stepped in and enabled us to not have that response again. 

I wasn't there for the initial setup but I heard about it. It was complex, but that was more of a cultural thing.

The deployment took around a year to get that through planning, discovery, and implementation.

Our biggest return is our cost avoidance and not having to backfill personnel.

I think the pricing is comparable. It's fair pricing for the size that we're deploying.

My advice would be to make sure that you have a really good understanding and a really good culture in your company that understands and wants to get on board with automation because it will require that type of mindset of understanding what you're doing before you do it.

I would rate it a seven out of ten. 

We primarily use the solution for automation of the back office. When speaking about our customers and use cases, I wouldn't highlight one specifically, however, mainly, we are using UiPath to build a center of excellence. The aim is to automate a majority of the processes in the company, and that includes Order-to-Cash, HR, supply chain, and even IT, among others. We are not approaching needs for one or another specific process. We want to automate the enterprise end to end.

There are many great features in UiPath that our clients consider valuable. I definitely like Studio. The Studio's a very powerful product, which helps very easily to build automations. Nowadays, there's also a StudioX for citizen developers, which doesn't require coding.

Orchestrator, which helps users monitor and schedule robots, manage assets, credentials, et cetera, is also very useful.

The third feature worth mentioning, I would say, is Insights. It is reporting and dashboards. Once the robots are running, it is quite valuable to see how those robots are performing. You can see KPIs and other aspects of both robots and processes.

Worth mentioning is the Automation app, which helps to manage the automation initiative end to end, especially building the pipeline and collecting the ideas.

It is quite easy to build automations with UiPath, especially now that they are segregated depending on seniority, meaning that you have the regular Studio and Studio Pro, which are truly for developers, however, you also have StudioX, which is more for people without a previous coding background. That makes it quite easy to use. People with a business background find it quite easy to pick a tool up and use it in daily automation. They didn't have any previous experience with programming or making macros or whatever else, and still, they have no problem with UiPath.

UiPath enables users to build end-to-end automation, and this is what we are doing on a daily basis. UiPath enables mainly our clients (through us) to build end-to-end automation in their processes. When I mean end to end, I mean that we help them to automate the chain of processes and do not focus on the single practice itself.

End to end coverage within UiPath is a great advantage and offers great possibilities. It is really important to have the ability to do end to end. Though it is not applicable all the time, it still is a nice option to have and use when needed.

Very soon after starting the RPA journey, customers realize much more important benefits than time-saving itself and FTE saving or FTE reduction. There are things that happen, like quality improvement. Whenever the work is done by robots, it is running in a much more stable manner and without any human mistakes and errors. It is also sustainable, predictable work, meaning that robots do not get sick or have a bad day, or face conflicts with each other, et cetera. They just do their work. They also can’t get viruses, such as COVID which means that we don’t have to worry about losing staff.

We have a customer speech workload that was growing dramatically in relation to COVID and having processes already automated, it was very easy to sustain and even upscale the delivery. The customer experience is better as well. It is not only important to spend less time or fewer resources in delivering the service to the customer, it is also important that the customer gets a quick response. Overall, the customer experience can be much improved when using robots in the processes.

In terms of the Automation Cloud offering, UiPath handles infrastructure maintenance and updates to save time for our client's IT department. Having UiPath in a cloud enables enterprises and customers to focus more on the automation initiative itself, instead of managing all the hardware and dealing with all their hardware problems and having more or giving more time to the IT department. Instead, you can use everything out of the box from day one and focus on bringing benefits to your end customer or end employee.

The Automation Cloud offering has helped to decrease time to value from UiPath. I would say that Automation Cloud increases time to value dramatically in the sense that you can start from day one. Literally day one, you can go and start automating the processes without bothering with all the infrastructure topics. The time required to deliver the first benefits is reduced dramatically.

Automation Cloud’s offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure maintenance and updates. It helps to reduce the cost of infrastructure maintenance, especially in the early stages of the projects, as well as on small and medium projects (for the long term). Not all customers or enterprises have strong IT departments or strong infrastructure in-house nowadays. Even large enterprises are moving more and more towards cloud services, even though they have strong IT infrastructure teams in place.

Automation Cloud is able to scale well due to the fact that we can, in a matter of minutes, or, in the worst case, hours, double the capacity. I would say that it positively and dramatically affects the scaling factor.

UiPath is a SaaS offering. It enables our customers to really quickly adapt and start using the technology almost from day one. It is very easy to start developing. It is very easy to start.

We are using UiPath Apps for our customers. However, this feature has not yet helped to reduce the workload on our IT department, or on our client's IT department by enabling end-users to create apps. Mainly, we are still involved as a service provider in the creation of the apps for the end-users. That said, where it brings added value is it reduces the limitations or the need to have an additional user interface, as you can create this app or user interface directly in UiPath to have an even better user, employee, or even customer interaction.

UiPath apps definitely increased the number of automations created. You can take more into the scope, what wasn't there before, with just attended or unattended automation, considering the fact that you can build a better user interface or any user interface from the very beginning. Before, there were only simple message boxes and prompts. Now, you can build really nice forms to interact with your end-users. It helps to accelerate initiatives.

Our teams have used UiPath’s Academy courses. Every team member of our company went through UiPath Academy. We always start with and actively involve UiPath academy.

UiPath Academy courses are a part of our standard onboarding procedure in the company, especially if we onboard junior developers. The very first thing we direct them to is UiPath Academy. Everyone starts with a basic foundation and goes through to a diploma and certification, and only then will we build on top of that more specifics about our standards, of our delivery approach, et cetera. I would say that UiPath Academy is a core and basic start for each and every employee in the company. Based on that education, we will later elaborate on different topics.

The biggest value I see behind UiPath Academy is its simplicity in terms of delivering the information. Even if you don't have any previous development experience and coding experience, all the explanations, videos, practical tasks, and reading material is formed in a way that is really easy to understand. The biggest value I see is its ability to bring people up to speed from really different levels, including very, very junior people with no previous experience in coding, programming, or the creation of robots.

UiPath's user community is excellent. Being an MVP, for me, the community has huge value in the whole end-to-end journey of RPA. Meaning that, at the very beginning, whenever you need to learn new things, you can always find a lot of useful hints in the forum and in the community. Later, when you already have delivered some solutions, you might face some problems. Luckily, very likely, you are not the first person to face those problems. There is always someone who already has had this problem and may have even raised it in a forum or on YouTube, et cetera. Even when you are already deep in delivery, sooner or later, there will be a point where you reach out for help to the community. The community, therefore, plays a crucial role for developers and automation specialists - be it business analysts, developer architects, et cetera. Having a strong community is definitely one of the most important factors that sets UiPath apart.

I'm not actively involved in other communities, and therefore wouldn't be able to compare UiPath to other similar communities. I can only say that the UiPath community is very supportive and very active in responding to any queries. The way it’s organized, it’s inspiring the next generation of forum members to help others and pay forward with insights based on the help they receive. UiPath’s community is really responsible and supportive.

In terms of reducing human error, at the very beginning, almost every company when starting the RPA and automation in Germany thinks of FTE saving as the main benefit. However, very quickly they recognize how huge the value is behind the quality improvements that happen after automation. It is quite obvious that robots are not doing human-like mistakes that may be caused by, for example, not paying attention or not getting enough sleep et cetera. Robots also cannot get bored. Very often, and whenever you have to process 1,000 or 10,000 records in more or less the same manner, it just becomes super repetitive. A mistake can appear in manual work as humans can lose focus on redundant tasks. This is not so when robots are involved.

In terms of time savings and error reduction, usually in our initiatives, we can see not higher than 5% of error rates when executed by robots. Even in those cases, I wouldn't say they are errors and more likely exceptions, which are documented and later handed over with specific explanations. A good KPI for our robots is to have less than a 5% exception rate. Related to this is that, by improving quality, we still save a lot of time as it can reduce the number of reworks which we might have afterward. For example, in one of the projects we were delivering, it reduced by eight times the amount of reworks or fixes, which the customer needed to process due to human-directed errors. Mistakes and fixes, therefore, were reduced by eight times.

What I would improve in UiPath, or I would just say, keep on improving, is the other products in end-to-end automation. UiPath started with Studio and Orchestrator as a core product, and still, we are actively co-operating UiPath and suggesting improvements for the other products. 

One of the products where I would definitely see a need for improvement would be a Task Capture. It is already good, however, there are many aspects and many ideas, which, for example, our business analysts have, which can be improved.

I've been using UiPath since 2016. It is already over five years. I'm familiar with the product.

Both on-prem and cloud solutions are very stable. The cloud is stable thanks to the UiPath team and on-prem, in our case, is stable thanks to our customer IT infrastructure team. Between the product itself and the infrastructure, be it Azure Cloud or on-site infrastructure, the stability is good. If there's any instability, it could be related to the people involved in using it as I've had a good experience with both cloud and on-premises stability.

The scalability of UiPath is one of the main competitive advantages, compared to other products. The software and the solution give you the opportunity to stably run it and scale it. With stable operations, you can focus on the new automation instead of maintaining already existing solutions. UiPath is very good at scaling in a friendly way and has good support that can help too.

I'd rate the solution at an eight out of ten. I never give ten, just to keep the motivation to improve high. I still believe that there are areas of improvement, though I really rate UiPath's support very high. The response time can always be shorter, the specification on solving problems can always be better, et cetera. Overall, I am extremely happy with the support UiPath provides in over 95% of the cases. For the remaining 5%, we still received the needed support, it only takes another iteration to move through another team and have a look at the problem.

Comparing the initial setup on cloud versus on-premise, the cloud configuration is much easier. This is one of the purposes of the cloud solution. It's meant to be easy to deploy and easy to scale. Documentation for the cloud is definitely straightforward. In terms of on-premise deployments, it is also quite straightforward, especially at the start, however, the complexity grows with the demands and requirements from the customer. If we have to get into the area of high availability and more of a complex server setup, it takes some effort to establish everything.

The simplest deployment on the cloud would take a matter of 15 minutes or maybe even as little as five. After five minutes you are ready to go and can use Studio and the cloud Orchestrator. It is very fast. You still need to have your admin rights available on your PC, however, that's the only prerequisite. 

For deploying on-prem, it's nearly the same for a simple deployment. If you only want to use the Studio and attend the job, it is very easy to configure in a matter of 15 minutes. Whenever you get into Orchestration, it will require more complex setups. It might take one or two days to set up, depending on how good of an infrastructure team you have to onboard.

The strategy in implementation remains the same no matter which deployment. In the end, you still have the same setup of products, be it Studio, Orchestrator, Task Capture, or whatever else. You have the same configuration of the products. It is only on the backend that is slightly different as it is hosted in another place. You don't really recognize the difference between cloud and on-prem hosted services.

At the very beginning, when we started the RPA journey, we were always tasked with understanding and looking at the potential return of investments. Therefore, we don't start automating the process before understanding the savings. For each and every process which we automate, we start with understanding what it will bring to the end customer. Even if we see minimal savings in the processes, we automate these. The biggest processes which we were automating were saving more than 20 FTEs (Full Time Equivalents). We are speaking to just about one process.

For us, FTE saving and time-saving are the same thing. It’s just different units of measure. You can measure it in people equivalent or in an hours per year equivalent.

The good thing about UiPath is that they are very active when it comes to listening to feedback. Every release incorporates some of this feedback into the product life cycle.

We are using both UiPath's Automation Cloud offering and the on-premise solution. We have customers, which need on-premise as well as customers which are running it in the cloud. On-premise, we have clients using different versions, however, it's my understanding that we are using version 2020.10.

I would definitely recommend, when starting the RPA journey, to start to use UiPath. Think about RPA as a robot factory, as a strategic thing, however, do not focus on one or another process. Think big and aim for automating all the manual processes in the corporation and from day one, and work to adjust all your procedures and infrastructure, the way that you've been able to get to this point. Do not get stuck at some point and feel you need to rework anything. Rather, change your standards in order to scale. In fact, aim for scalability from day one.

I'd rate the solution at a ten out of ten. We are a happy partner of UiPath and we have had many successful implementations with our customers. I can confidently say, after five years of experience using UiPath, that I've been happy with it. I still believe that there is always space for improvement. However, I really do have an appreciation for the tools. They're making a really good product and they should keep on improving at the same great pace. We plan to keep on using this product to deliver the same great services to our customers.

Currently, we are using it for reading emails. We download the attachments that we get in emails. After downloading those Excel sheets attachments, we process the data based on a few rules. The processed data is input into the SAP application. In the SAP application, based on the business rules, we process the data and commit.

It is very user-friendly in terms of building automation. We don't need to be experts in coding. We can learn it easily and build complex business tools in UiPath. We don't need prior coding experience.

It reduces the cost of digital transformation. Every day, we get 10 Excel sheets, and somebody has to sit and read the Excel sheet and load the data manually into the SAP application. Three to four employees are required for the same job, but if we automate this process, it can be done in a minute. It is easy, and we save time and cost.

It reduces the time taken for a task. If we are manually filling timesheets, we need to open the website, fill the timesheet, and submit it. It can take 10 minutes. With automation, it will take just a minute.

Orchestrator is very useful for deployment and publishing, maintaining queues, and running jobs.

In UiPath, REFramework is useful for different use cases with predefined code templates. There are well-established steps. There is a step for code marginalization. Similarly, there are separate steps for initialization and processing. For closing an application process, a step is there. So, it is very well modularized for getting the transaction data. If there is one exception or anything wrong happens with an application, it will log the exception in the orchestrator and send an email. It can also close your applications and end data processing. So, everything is well organized and separated, and we can log the exceptions separately in the queues as business exceptions or application exceptions. We can have the complete report of a particular queue.

For document understanding, there are so many features. I haven't used them practically, but to read a PDF, there are patterns and semi patterns. A wait option is also there for somebody to come and correct it. It can wait until somebody comes and corrects it, and then it will do the processing. So, all of the features are very useful in UiPath.

In exception handling, wherever exception occurs, the out arguments are not being passed. It would be good if there is a way to pass the out arguments. 

Sometimes, when an element is not there, UiPath gets stuck, and it doesn't even throw an exception. It stays stuck for hours until we go and check the logs. When this happens, we have to kill it. It happens in some cases, so an improvement is needed there.

I have been using this solution for three and a half years.

Other than the issues related to the exception handling and UiPath getting stuck, it is very stable.

It can scale well, but we don't really have a need to scale it. Currently, we are automating 15 projects. We are planning to use other functionalities of UiPath to automate extra things.

Currently, we have 1,000 people who use this solution. They are consultants, developers, and business analysts. A business analyst takes care of making design documents and solution documents. The RPA developers develop the code and test it. After that, for deployment, someone is there to take care of all technical things. After that, the support team is there to look after the deployment.

I didn't call UiPath support, but I know about them from my friend. We had called them for some issues, and they answered those very well. I would rate them a nine out of 10.

I have worked only on UiPath.

Its initial setup is straightforward. It is not that complex. We need to install UiPath Studio, and then we connect it to Orchestrator for getting logs, etc. It doesn't take more than an hour.

I took the help of my colleagues.

I'm not sure about licensing and pricing, but the pricing for their certification is a little bit more. Previously, we could do it for no price.

I would definitely recommend it to my colleagues and others. It is very user-friendly.

In terms of reducing human error, it is not up to the mark. It detects human errors, but it waits until we place the correct files for processing. For example, when comparing files, a human can detect two almost-similar addresses as the same, but a UiPath bot cannot do that. So, in some cases, it won't work as humans. It cannot decide. It works on predefined rules.

Considering its areas of improvement and the cost of certification, I would rate UiPath a nine out of 10.

I've created an app for conversions and exchange rates. Every day I need the exchange rate of a certain currency and I use the API free exchange and UiPath.

It's also used for the reconciliation of invoices.

I've used it for the creation of an onboarding bot for employees to be onboarded onto a website with a remote system. I used AWS and a virtual machine and created a Google Form from there, and used UiPath's computer vision to do onboarding activities and extract data from files. PDF files can then be entered into the remote system. UiPath can be used to fill the forms.

It can be used for web extraction tasks as well, for example, for booking flights, where you can extract the flight details for particular search criteria and place them into an Excel sheet.

It can also be used to extract data from invoices in order to populate an Excel sheet, for a portable format. I've created a process that used documents as a learning model and extracted the invoices, using logic to output the transactions. 

Another use case I tried was extracting data from Amazon based on exact data. The same can be done on Linkedin using the Linkedin API. I'm fine-tuning and extracting data, putting the outputs on Google Sheets.

I've experimented with many use cases and automated many processes. 

It's low code/no code which makes it very easy to work with. 

Building automation using UiPath is easy. If I see a video or some instructions, I can do it. Things are doable. You learn. If there are use cases or there is information online, you can replicate the process.

Adding activities is easy. All of these partners are integrated into UiPath now - including AWS and G-suite. You have activities already built right into UiPath and they are working to make everything as low-cost as possible.

Then you have OCRs which offer the Document Understanding. I can do a PDF extraction using just OCR in a normal way.

I love the Document Understanding. You can see whether a document is valid or not. You can accept or reject. I came up with a .NET background. I used to write so many lines of code for doing a certain thing. Here, you have a for a loop. You don’t need so much code.

I remember when I used to work for a UK client, a gas utility, and at that time we used a read-through data driver, and got the Excel data, and again validated everything. However, for that, we used to write around two, three pages of code. Now, using UiPath, you just do a real Excel activity and you get the entire sheet. Automation has made our lives easier.

I can scale automation without having to pay attention to infrastructure. Now, since the cloud has come into the picture, everyone is going to the cloud and everything is easier but with the new cloud partners like Google, AWS, Azure, and Oracle. A company may not have its own on-premise orchestrator.

Earlier, you needed three servers for production, testing, and development. Since UiPath has both cloud orchestrated and on-premise, it's easier for organizations to use less physical space. For smaller organizations, they can go to the cloud. For larger they can have their on-premise orchestrator. It’s flexible.

UiPath enables me to implement end-to-end automation starting with process analysis and then robot building and finally monitoring of automation. There are many process mining tasks, capture tasks, mining, et cetera. More things have to be automated - such as deploying, managing, and enhancing for continual improvement. It has all the components.

For a beginner, end-to-end coverage may not be essential. When we talk about automation, we should know what can be automated so that we ease our lives and that doesn't mean we have to remove the resources. You don’t have to involve the employees. You just need to simplify the task so that there is continual improvement. Users should consider not only, how to automate but what needs to be automated. If it is automated, how it can be improved gradually and what are the returns? Sometimes that doesn’t necessarily mean you need end-to-end. You just need simplicity.

I do use the attended automation. For some processes, I use the attended automation for testing purposes. I use the attended if I'm using UiPath assistant, otherwise, it's normally background processes that are unattended.

Attended automation will be for Document Understanding when I'm training a robot, for example, for what is the format or validating the time I'm using attended one. If I'm asking a user for particular search criteria, or for currency exchange it's mixed but mostly unattended.

Both attended and unattended work together - the human as well as the robot. However, it depends on the scenario. Unattended means you are not dependent on any human resources.

The orchestrated cloud, which is a SaaS, it's quite helpful. If I just want to install UiPath studio in my system and I'm least bothered about what environment it should be, what infrastructure should be, where I'm going to deploy, it is quite useful and quite easy when there is a SaaS option available.

I’ve used the AI functionality for sentiment analysis such as getting reviews from the websites about a particular product or service.

UiPath offers great object detection where you have a magistrate and you can detect whether you want to detect the people. If you want to extract how many people are there in that image, for example, during a social distancing sort of event, that can be used for object detection. I've used object detection for images in terms of extracting a number of people.

I’ve trained the system to read different types of invoice formats. I've used the email or Document Understanding that can read separate invoices, receipts, utilities, et cetera. I’ve used the solution to create processes for invoice reconciliation.

The AI functionality is quite easy to use. For tollgates, for example, when they charge for tolls, the solution can be utilized for seeing the number plate, and through the image, get the data, extract the number of data from the numbers plate, use the driver information from the number plate of the car, et cetera. It becomes a very easy AI model. Without any type of knowledge in AI, you can use those out-of-the-box functionalities.

The more training you do with machine learning, the better results you get in the end.

I use the automation cloud feature.

We are not bothered about any patches or any work that has to be done to maintain the infrastructure; the vendor does it.

The automation cloud offering has helped decrease time to value, however, since I have not deployed real-time projects, I cannot give exact numbers on the decrease. That said, from my experience, I feel that it is true.

It’s my understanding that the automation cloud offering helps to decrease UiPath's overall cost of ownership, however, at this time, I just use the free version.

The solution enables you to be better and better with cloud features that are quite accessible.

In terms of UiPath Apps, I have used them, however, just for my own purposes, for my own training purposes, as I was learning. It is easy to use and pretty much drag and drop. For the basic things, the user can do a lot with minimal training. You can do everything with low code and less coding knowledge as well. A person may not be technically sound, however, even with minimum knowledge, they can create apps using UiPath apps. That's the interesting part of UiPath apps.

UiPath reduces the cost of digital transformation. It does not require expensive or complex application upgrades or IT support.

UiPath has reduced human error. For example, let's say I'm filling a form using a document. Typos, errors, spelling mismatches, et cetera, are reduced when it is handled by automation. When we automate this process, the robot minimizes the error since a human is not involved in this case of data entry. It will extract whatever data there is in that document and it will fill in the form. Similarly, for calculating Excel data, we can avoid calculation errors.

More videos are required. There are basic videos that can help you learn about the product, however, there need to be more in-depth videos to help you through certain tasks. For example, I was trying to use an API for conversion. I was doing it for a single transaction, one by one. There can be cases where it will not go for a simple conversion or simple transaction, and it will be a bulk action. In that case, I may need to upload a file. I was searching for an upload control however, I could not find anything to assist me.  It would have been helpful to find some sort of instructional video for this task. The file upload, where you upload a file and select a file so that you can extract data all those things based on that file is a commonly used feature - and yet, that was missing. 

UiPath apps may be able to increase the number of automation I can create while reducing the time it takes to create them. However, they need to elaborate on the process. I need more articles on that. From the point of view of the person developing the automation, I need more details on writing the correct code or doing the automation, which I hope will be coming in the next releases.

They require an improvement in the IEP. I don't know whether it's a bug or something. I find that, with drag and drop, you have to drag it in a particular fashion. 

When they add new features, they should offer some in-depth sessions on them to help people get comfortable with the changes. 

It would always be helpful to have new partnerships between UiPath and different cloud vendors. 

I started using the solution in February of this year.

I am on a gap year. I used to work for an IT company, and I have taken a gap. To re-skill myself I started learning UiPath. 

The stability is quite good. You have other options, such as Automation Anywhere and Blue Prism. UiPath will be like coming out with new revisions in the coming years that will continue to compete with those.

Even now, it's quite stable and quite reliable, even if the changes which are coming, in the much of the deployment, are felt good. There are frequent revisions. I have no experience in other automation, however, from what I've seen, even as it changes, it's stable.

Scalability is quite good. It has alliances with different cloud vendors so that you can scale your robots. You can have different instances, different new virtual machines, and in the cloud. You're not concerned about what to install and you just pay as you use. The cloud vendors make it very scalable. 

Once I am employed, I do plan to increase usage.

I use the forum for any queries. I didn't face user technical problems for any robots that I am using. I have not been in direct contact with technical support.

The initial setup is straightforward. 

You just go to UiPath.com and register with your user ID or any email ID. From there, you install the UiPath Studio and you set your workflows. Once you publish, you get it in your orchestrator, attach the process, create a job. And then you run it. 

It's quite easy to create a workflow, publish it, and deploy it in the orchestrator. Next, you have to tag the correct robot, the correct machine, and the correct sponsor. In any environment you want.

For small processes, the deployment would hardly take a few minutes to deploy.

Maintenance is light for the cloud instances and really does not need much. The cloud vendors do the work, however, users need to pay for the services which they use.

I handled the initial setup myself. I did not need an integrator or consultant. 

I can't speak to the exact pricing of the product as I am using a free version of it right now. I'm not paying any licensing fees to UiPath.

I shouldn't say you need licenses for many things for today, however, for working on Visual Studio, if you want to automate something, you need a license, which costs you around 5,000 to 6,000 Rupees. If you want to do some extra Microsoft office activities. You need the maximum office license, which is 70,000 Rupees. That said, with UiPath, you need not have Microsoft Office installed. You can still read the data and extract the data in an Excel format. You can then share the data from those automation activities with no third-party license cost and no software licenses.

UiPath can help save costs in an organization. There are so many legacy systems wherein you have so much data migration, and many things which are done manually can be automated and you can save resources while doing something new. 

I'm just an end-user. 

My first experience with automation was, "Okay, which product to learn?". After all the reviews and reading, I decided to start with UiPath. My previous background was .NET web development. I was a full-stack web developer with seven-plus years of experience and I found that I really like when a product is built on a .NET framework. I realized that "Okay, it's better to do something, learn something and I have a background of the platform so let's start from there".

When I started using this product, I found the academy was quite open, and in the forum, there were people who were training as well. I found that while I may not get 100% of the answers I need, 85% to 90% of the time the answer is there if you search. 

Many people do not know RP automation, and it's great that they have these free resources - which is rare for such a product. Each region has a chapter where people working in this area come and share their knowledge and experiences.

Currently, I'm using the 2019 version of the solution. It's not the latest, however, it's not much older. I'm using the enterprise as well, which is free for 60 days. I started using UiPath apps as well. I'm learning so I use the cloud orchestrator to deploy my processors. 

I'd rate the solution at an eight out of ten.

My use case is to automate a bunch of office processes. It helps my team and finance organization save time and money.

There's a monthly upload process in my order management team. Every month, this team uploads a bunch of files to SAP. Now they don't need to do that because the bot does that for them at a given time period. The team members need to just upload a file to SharePoint and then the bot will pick it up.

It reduced human error. It saves us time redoing work and allows our humans to do other stuff.

It has freed up a couple of hours in a month. If you scale it, I'd say there are some processes that are daily. It has been at least 2,000 hours so far. This additional time enabled employees to focus on higher-value work. Bots can be tricky to debug. So, sometimes employees get frustrated there but overall they're happy it's there in the first place.

UiPath reduced the cost of our automation operations. Right now it's breaking even, but over time there'll be more. It has also reduced overall costs. 

The Studio and Orchestrator are pretty valuable. They seem to have a lot of connectivity and usability. It's pretty easy for people without a coding background to use it.

It's pretty easy to build automation using UiPath. It's a little hard for some activities because there's not enough support. There's not a lot of adoption with that activity, but the ones that are commonly used have pretty good support.

Its end-to-end coverage is important to us. If we have it all on one platform, we don't have to bounce around other software. But, we ended up doing a little bit of both.

Capturing ROI needs improvement. I would also like for it to have more logging mechanisms in Orchestrator.

I have been using UiPath for about two years now. 

It's stable now. 

We mainly use Unattended Automation but it has helped to scale RPA benefits by automating departments for the very few Attended Automations we have. It's important to me because my job pretty much depends on this software. Changing from this product to another RPA product is going to be extremely costly and time-consuming.

It is scalable. We have about 30 users on it now that are entry-level/senior associate-level people.

It requires four developers to maintain. 

We plan to increase usage in the long term. But right not we still have enough capacity in our existing Orchestrator.

I would rate their tech support a six out of ten. Most of them don't work in U.S. time and they're not always very responsive. Sometimes they give an answer that is pretty generic and can be found in the online article, even though I referenced the article already.

We also use Automation Anywhere. 

The initial setup was not too hard and not too easy. Some documentation wasn't very clear, and for basic features it handled it pretty well. But, if you wanted to go more granular and customize your deployment, it would be a little hard to find out the answer.

The deployment took about a month. We involved the UiPath support to help us implement it and upgrade our systems. Other than that, we got our PAM software lead that uses CyberArk to configure the Orchestrator with us.

We have seen ROI. I don't know the max number of hours but I'd say we've saved around 2,000 hours so far.

I think pricing could be better. I think it should be more visible.

The license system with Studio licenses seemed a bit redundant and not necessary.

We looked at other solutions but went with UiPath because of the cost. Another reason was that we have more developers that are specialized in UiPath, as well as management, who seemed to like UiPath more.

I still have to pay attention to the infrastructure a little bit because it's still On-premises. I'm using the On-premises products more so, but the support has been pretty decent. And then, there are community forums to look up how to debug some stuff.

The upfront cost is always going to be more than trying to keep it to the human process, but over time we'll realize more return.

My advice would be get UiPath support to do this for you and involve all your IT firewall security team.

You need to know more about security and cybersecurity in order to fully deploy your automations. Some of that is kind of missing in the Academy where they focus mainly on building automations, but not really securing it.

I would rate UiPath an eight out of ten.