UiPath Reviews

Our primary use case is creating automation for day-to-day activities for our internal use, especially for performance management and reporting. Apart from that, we create some automation applications for our clients as they're using UiPath. That's another use case.

We prepare database reports where a lot of product data is consumed. Creating reports or reporting used to take a lot of time and effort for us. UiPath has been very helpful for us in quickening this process and making it efficient.

It enables us to implement end-to-end automation. With our data and reporting tasks, there were a lot of repetitive tasks that needed to be done, which sometimes can be irritating. UiPath has completely taken over this process. So, right from the input of data to the extraction of reports, the complete end-to-end process is covered by UiPath. I don't have any complaints.

With UiPath, our automations are getting better and better. UiPath is driving performance, innovation, and growth across our entire organization. With report automation being our main use case, we saved a lot of hours, and we have also reduced a lot of overhead costs with UiPath. With automated data processing, errors are minimal. The error rate is almost zero, and the time taken is pretty quick. Our efficiency has improved, and that has been a major benefit for us.

We have been using the cloud version of UiPath. So, our on-premises footprint has definitely been reduced.

It has helped us move a lot closer to 100% digital transformation. Our reporting is automated, and we are almost 100% digital now. There is also an overall reduction in the cost and employee time.

It has reduced human error. The error rate is minimal or nearly zero. It's 100% smooth for us. In the past, we would have overlooked or missed certain data points, and during our final report collaboration, a mismatch would happen, but that is completely reduced with UiPath. 

It has freed up a lot of employee time. It has also made our work much more efficient. Earlier, if seven employees were doing a particular task, only three employees are required now to do that task. So, other employees can focus on something else now. 

It has saved about two working days or 16 hours a week. With the amount of data that we work with for reporting, it was a very hectic task for us. We had a lot of data sheets, Excel files, etc. UiPath has saved us two days of manual work per week.

It has saved costs. We were a team of seven who were handling reporting. We were taking reports and consolidating everything, whereas now, only three of us are required to do that. The remaining four can focus on something else. That much time and cost have been saved. This has resulted in us focusing on some other aspects of our business and bringing in more revenue for us. These are some of the overheads that have been completely saved by UiPath.

One feature that is particularly very likable is the My Workspace option under the Orchestrator menu. We can easily arrange and/or segregate all the folders there. The My Workspace option has been a very big positive for me. I've been able to streamline my work and do structured work with this My Workspace option. It's one of my favorite features. Apart from that, I like the integration services offered by UiPath. There is also the Studio option with good features, but I have used Studio very less. It's basically used to design specific automations and applications.

UiPath is very straightforward for creating automation. Especially in the UiPath Orchestrator and UiPath Studio, you can just drag and drop items to create an automation flow. It's that easy. For example, for the reporting automation, I designed the automation flow by using the in-built features. I did not type any command or code. I just picked a feature and dragged and dropped it to create and implement the flow. It was that easy for me.

The UiPath community is very vast, which is a very major plus for us. Whatever doubts we have and whatever knowledge transfer needs to happen can happen pretty quickly with the UiPath community. I find it very useful. Apart from the UiPath community, there is an Academy option where we can take up some courses, and we can do some certifications. That is also very good. I have personally not taken any courses, but I'm aware there are courses because my teammates did the certification courses. So, in terms of value, UiPath is an all-rounder for us because apart from doing automation, we get a whole lot of other things. It's very good.

They can improve the in-app guides and in-app tutorials. One instance where I faced a challenge with UiPath was during the initial week of using UiPath. It can be a little complex to understand at first. The in-app guides or the in-app tutorials could be much more elaborate and detailed. That would have made my entire journey smooth, but that did not happen.

The AI functionality could be improved. We used its AI functionality as a base for our reporting automation. It's not 100% perfect. It's still evolving. We used AI to predict the data modeling and report structure, but it wasn't accurate all the time. It's an evolving functionality, and I hope that it gets corrected over the course of time. The basic functionality is on par with any other software in the market, but it's not helpful for simplifying complex workflows and modules. The AI functionality has also not been helpful in increasing the number of automation, but UiPath, in general, has been very easy to use and helpful for doing more automation.

I have been using UiPath for about eight or nine months.

I haven't faced any issues so far. It has been smooth. I would rate it a 10 out of 10 in terms of stability.

I believe that any automation software, including UiPath, is scalable. It's a cloud-based solution, so it's definitely scalable for us. With UiPath, we have been able to do more automation and reduce our overall manual work. Our manual work now is very limited. It has definitely helped us scale up in terms of revenue, efficiency, and performance.

They're definitely very knowledgeable. Until now, I haven't had any complaints about them. Whenever we have any doubts, we just email them our queries with certain documentation, if needed. They get back to us immediately. They are also patient. It's not like they're in a hurry. They're very patient. They make sure that our query is completely resolved before moving on. I would rate them a 9 out of 10.

Positive

In my previous organization, they used a software called Freshworks. It was for automating our reports and sales processes, but I personally did not like that software because it was a little bit complex for me, and it was also costly. There were very few integrations that were offered in that particular software. We were not able to get the results that we needed. So, we looked into different solutions, and that's when I recommended UiPath to my team.

In terms of performance, UiPath has been very reliable. It's a complete cloud solution. The Freshworks software was not a cloud solution. We used it on-premises, but UiPath is a complete cloud solution for us. It's a very reliable and stable solution. We hardly face any downtime, server errors, or something like that with UiPath. That has been a very noticeable difference for me. Apart from that, in terms of complexity, UiPath is not at all complex. It's a structured solution. You choose A, and you can come to B, and you can come to C. It's very structured, which is something that was lacking in Freshworks.

I was involved in its implementation. It was not a complex process. It just required me to sit with the UiPath team and get it implemented. We did not need an elaborate team or effort. Within 15 to 20 days approximately, we were able to set up everything and get it running completely. The implementation process was very smooth.

Its maintenance is also very easy because it's a cloud-based solution. We just need to keep it updated all the time. That's the only thing. We have employed just one person to take care of the maintenance.

It was a combination of the in-house team and UiPath specialists. Their initial training team was very knowledgeable, and they were very pleasant in addressing all our queries with respect to how to design applications, how to create automation, and things like that.

We have definitely seen an ROI. Four employees are now not needed to do reporting. We have been able to transfer them to other projects. It has given some returns within four to five months. We have reduced our overall work time by around 30%. We have been able to use that saved time for other things helpful to bring in more sales, automation, etc.

Our inbound revenue is going up. We have seen a 20% increase in our overall revenue after the introduction of UiPath, but I cannot directly pinpoint that to UiPath because there are other factors as well.

I was not involved in the pricing negotiations, but as far as I understand, my team was happy with the pricing. So, I assume that its price is moderate and competitive. It isn't highly-priced.

To anyone looking into getting this solution, I would advise getting UiPath instantly and integrating it with your business to proceed further. If not UiPath, I would definitely recommend trying any other automation solution because that is the need of the hour. We are humans after all. Manual work is prone to error and less efficient. An automation solution can definitely help you scale your business quickly. UiPath is one of the top ones when it comes to automation. It's a tried, tested, and trusted solution. So, I would suggest going with UiPath, but if you have any concerns about it, you can definitely try other solutions.

Considering the UiPath community, UiPath Academy, and UiPath's all-around capabilities, I would rate it a 9 out of 10.

Our use case is mainly for PDF automation for invoicing. Specific data from the invoice needs to be gathered, entered into, and compared within the SAP application we use. We face challenges as the formats of the invoices change and can range in length from a single page to up to 100 pages. 

We've integrated a tool called ABBYY FlexiCapture and ABBYY will help format and be used as the source of input for the UiPath bot. This bot in turn will process each and every necessary customer detail to the SAP application. If everything is correct, and the data meets the parameters, an email will be sent to the customer, attaching the necessary invoice. If there's an exception, we'll be able to look at that too.

There are some other sets of use cases as well, which include SAP or Hyperautomation. However, we also do generic workflows where we have data from multiple domains and will need to build our XML output. The XML output will contain a lot of data (such as the date, time or name of the customer) which will keep changing and is not fixed. I built a bot using UiPath that I host on Orchestrator which can monitor this data.

Another use case is placing job descriptions into an analyzing tool to search for keywords. Depending on the sort of description which we have pasted in, it will throw out a certain set of outputs, such as if the word is feminine, masculine, how many details it contains, how long it's going to take to complete the description, et cetera. This part has been done using an API key, and therefore it's not a normal cut and paste job. 

There are a lot of processes that are, even today, done manually. I can take a simple process in, for example, ServiceNow, where issues are made into tickets and put into queues. Previously, a person would have to pick up the ticket and then assign it to a variety of people, but first, before even doing that, they would have to check in on those team members and figure out who had the most or least workload to be able to address the ticket.

This process is automated now. There's no human intervention in assigning tickets. The bot will monitor the queue and when a person raises a ticket and can monitor which person is working on which ticket number, and who should get the next ticket. The turnaround tie has been reduced by a lot and is also saving us costs when you look at it in relation to the entire project as a whole. 

The most valuable feature is the API.

It's really compatible with other solutions and it got integrated when I was working with ABBYY. There is no dependency. I just need to trigger my bot and that's it. I didn't need to go and separately trigger to work on every part of it. It is really good when we talk about the integration of UiPath with any other tools.

I am currently working through the documentation to help with understanding the solution and it is really great.

From a studio perspective, I really like the feature of debugging.

It’s making automation really feasible and ensures that it takes less time.

The ease of building automation using UiPathis great, even if a person doesn’t have a development background. Just by going to the UiPath Academy and doing the basic certification, any user can start to understand the process and begin automating.

In my first organization, there were two or three developers including me, and our challenge was that we had a lot of projects. We had certain process analysts that would run on different sets of processes. We were able to train them and make sure that they understood the processes and could start developing. We saw a lot of progress in them, and, due to the fact that the tool was really easy to use and didn’t require a lot of coding, they were able to do a lot just by drag and drop functionality.

UiPath enabled us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automation. It really supports the end-to-end deployment of any project or any task and makes it very easy.

The Automation Cloud has helped decrease time to value. If there was no Automation Cloud, we would need to run the bot from the studio all of the time, or we would need to create an upgraded file and trigger it via a third-party application, like VBScript or something like that. It has reduced a lot of time. It also makes deployment really easy. For example, if I am working in a development environment, I publish to the cloud, it will start reflecting in the Orchestrator and I just need to push the package. From the Orchestrator itself, I can trigger that particular package to any other machine. That makes life a lot easier - just publishing the package and testing in any other system and understanding how the UAT is going.

The deployment in production is really easy. I have tested Orchestrator and production Orchestrator and I just need to copy the package from the studio and download the package and push it back to the Studio or Orchestrator production, and the work is done. I don't need to manually copy and paste the packages again and again.

Automation Cloud, in a way, helps decrease UiPath's total cost of ownership by taking care of things such as infrastructure, maintenance, and updates. There’s no need, for example, to host on different servers or a defined cloud. It has definitely reduced a lot of costs due to the fact that, instead of going for a different set of applications for a different set of projects, now we are relying on UiPath for most of our work. Whether it’s invoicing, finance, or an HR process, we can rely on UiPath to automate a particular process instead of going back and forth across multiple tools.

Automation Cloud allows us to also effectively scale up automation. It is very easy to monitor any process which is running correctly, and, with automation, you don't need to have any separate application downloaded into your system. It is just an URL. You just need to have a URL and you just need to enter the URL and you can monitor from any system and easily understand how the process is performing.

On top of that, with Automation Cloud, suppose you have 10 licenses. You can see how many licenses have been consumed by how many processes and what the outcome of the processes was.

Moreover, you can integrate your cloud with other tools and create a dashboard. With a UiPath dashboard you can see, for example, the percentage of success rates, the failure rate, and how many processes have been successfully done or what quality. From the management side, we don't need to go to the logs and check what has run. We can directly look into a dashboard and we'll come to understand how many processes are running successfully and what are the outcomes, and how many licenses have been consumed.

It is important that we can scale automation without having to pay attention to infrastructure. I’d rate the level of importance at an 8.5 out of ten. It is helping a lot.

When we talk about automating a web application or we need to work on a different set of applications, we used to get integrations and we needed to have, for example, a PowerShell scripting application license. Now everything is being replaced by UiPath, or most of it is. It does not require you to have a license for a different set of tools all the time. If you have UiPath it is easy to integrate with any third-party tool and it is easy to automate a web application or desktop application or even code. If I know the coding, I can just do coding right in UiPath itself. Instead of going for multiple tools, for multiple projects, it's just a single tool for multiple projects.

We can use the infrastructure and we can also host it. Suppose there are two users who are accessing the same VM over a different time zone. They can rely on the same VM and they can use the same UiPath tool and do not necessarily need to have a separate licensing for it.

UiPath has helped minimize our on-premise footprint. Mostly now, everything is on the cloud instead of on-premise and it is making life easy. For example, suppose a person who is working on-premise, if he logs out, then the other person can log in and cross-verify the work he has done. With the cloud, now the transfer of files is easy. If a person falls sick or something happens that he's unable to make it then the other person who has a login or credentials with him can just directly go in and start working. If a code is being published in the cloud, we can just copy or download the code and cross-verify how it's working.

We do use attended automation. We use it relatively less compared to unattended. However, in certain cases, where the project is too critical and we do need to run all the time, it’s nice to have that option. Attended automation helps scale RPA and benefits our organization by automating specific processes that require human, robot collaboration. There are certain processes where you can't automate end-to-end. We have to rely on a human being occasionally, and it’s nice to have automation we can collaborate on. At the same time, we do largely take advantage of automatons where no human intervention is required.

We use UiPath AI functionality, although not much is being used in any of the projects which I have worked on. I’m just looking forward to it, as I am currently working on documentation understanding before diving in.

UiPath speeds up the cost of digital transformation and has also reduced costs. I started with Blue Prism and then I got my hands on UiPath. Now, I can see the transformation which is happening and I can see the comfort which we have with the tool. I can also see how it’s a lot easier to deploy the tools.

The solution has helped our company reduce human error by a significant amount. For example, when I automated the complete process and I put everything in GPL step by step and automated using UiPath, the best thing that happened is that there was one invoice that got stuck and I could see that the bot didn't process it. The bot has sworn an exception stating that there is a certain set of values that a bot should not process, if it is not matching, the quality is not matching, then the bot cannot process it. When the customer logged into the particular invoice and they saw that, okay, the value which is being mentioned in the invoice is below the threshold critical value. For the first time in over a period of 13 or 14 years, they came across a particular invoice that got stuck with this particular amount, which was below the threshold level. The bot captured something that needed to be dealt with, and the client was so happy it was caught as it saved the company a lot of money - around $1 billion. After catching that threshold, they have monitored all the invoices for the past 13 or 14 years and they came across a lot of differences. It has played a major role in saving a lot of money.

UiPath has freed up employee time. The faster you deploy, the better. We look at months instead of weeks when calculating time. If a ticket, end-to-end, takes 24 hours to resolve, for example, with automation, we’ve managed to reduce that time down to seven to ten hours. It will keep following up and sending emails until there is a resolution, and those reminders are quite helpful in moving the process forward. It’s definitely allowed employees to focus on more important tasks and there’s less time spent on follow-up.

In terms of employee satisfaction, when we are developing something and we have a proper outcome, it makes life easier.

The product has reduced the cost of our automation operations. Not for all the processes, however. If the process is really simple, just like 10 pages or 20 sequences or 10 activities, then the cost is high for a particular license, for a particular process. That said, when you talk about the complex process, where the process takes 48 hours or 90 hours to process a particular activity manually versus what the bot can do in just five to ten minutes, it impacts the cost. Now, a single bot is taking care of that and there is only one person instead of many who monitor the process. Likely, it has reduced costs a lot, roughly 50 or up to 70%. Overall UiPath has saved costs for our organization. Processes that needed five people can now run with just one or two running things with a bot.

When the Orchestrator got upgraded and UiPath didn't get upgraded, we started getting errors regarding the managed packages, the packages were not getting upgraded. There are little things like that where we’ve had trouble. We have just made sure that if the company is upgrading and they have a license to upgrade Orchestrator and the Studio, they do it simultaneously instead of waiting for a week or two weeks or one month. If they have upgraded the Orchestrator, and they have not upgraded the studio, it will impact the developers.

In terms of the upgrading of the on-premise orchestrator, there are organizations that are upgrading their developing environment but they're not upgrading the production environment. Therefore, now, when the bot or the particular package will move from a higher-end environment to lower activities, it is not working well and it needs to get downgraded.

While delivering or providing the license, we need to explain to clients that this particular product, if you are working on a development and production environment, they have to keep them on the same packages or they have to keep your production higher, so that if they move the packages, it won't impact anything.

I've been using the solution for the past five years.

The solution is very stable. I have not faced any difficulties at all. 

Until now, it hasn't scaled a lot. From 2018 to 2021, the tool, the overview, the look and feel of the tool have been scaled a lot. It has scalability, definitely. We haven't scaled it a lot. 

In our organization, we have between 100 and 150 users on the solution.

The vendors are really helpful. Whenever we have a concern regarding any of the issues, including if there is an issue with upgrading, it gets resolved well. For example, when we upgraded the studio and didn't upgrade UiPath’s Orchestrator, there were some issues. The board was not connecting to Orchestrator. We had to raise a ticket to our support team and it got resolved. 

I'd rate them at an eight out of ten, as we've gotten a good response overall.

In the last five years, I have worked in two to three organizations. All of them have started exploring automation tools. I've used Blue Prism as the very first tool, then I got the opportunity to work with UiPath and explore the different sets of opportunities with it. 

At this company, WinAutomation was previously used. That was four years ago.

The initial setup is pretty straightforward. It's not too complex. 

We have a server we implemented the solution on. We installed the certificate to have the application installed with the Orchestrator URL.

The deployment took around two days of full-time work for us. There were multiple servers involved.

The implementation strategy was very simple. We got onto a call with the UiPath team and they had a lot of data with them, including all of the details regarding the applications. We wanted our certificates to get installed and we had our internal team involved as well. Between the two teams, it was working properly and it got installed in less than the expected amount of time. 

We have a team of 25 to 30 people that can handle deployment and maintenance. Maintenance would be, for example, if you have certain packages missing, someone would have to deal with that. Or if something wasn't working as required. Another example of maintenance might be if we are accessing multiple applications, or if we are accessing SAP, and there were tools that the bot accessed, the maintenance team would need to go and check the particular environment on which the bot is going to get deployed.

From the very first organization, I have implemented UiPath end-to-end.

We don't use a third party for deployment now. We have our own team. There's an internal team within our current organization which deploys everything.

I don't have any details in regards to the pricing.

We did POCs in the past with WinAutomation and we also looked at Automation Anywhere. At the time, we were looking to deploy more on the cloud, which is why we went with UiPath instead.

I am just an end-user of the product.

I'm not sure if the version we are on now is the latest. It likely isn't. We are in StudioPro currently.

I'm not sure about the infrastructure side of things, in relation to the cloud, as I'm more on the side of developing and deploying the project. We have an internal team that looks into cloud deployment and other stuff. While we were working on and purchasing the license from UiPath, the very first instance, then definitely the team got integrated with the UiPath team, however, after that, the internal team is capable of handling the end-to-end part of it.

We don't use UiPath as a SaaS solution and we do not yet use UiPath apps.

In the process of UiPath, speeding up and reducing the cost of digital transformation, I have never required expensive or complex application upgrades or IT application support, however, we have a different set of teams that work on the licensing part and the management side of it. They likely worked with UiPath to get their issues resolved. I do not have much knowledge regarding this.

A person who's starting on UiPath can also up-skill himself with the tool as well as it is easy to learn. 

The best part about UiPath is that they provide a trial version. Any organization or any individual or any business looking for automation solutions can give it a try. There are a lot of things which you can explore and you have a lot of integration. If we have a module that is already running, which has been designed in almost any language, you can just integrate that in UiPath and keep that running.

It is reducing a lot of dependencies on other tools and it's making sure that our lives get easier from the deployment and monitoring perspective. From the licensing and the cost perspective, there are a lot of items that are really helpful. In terms of integration with third-party tools, they have a lot of packages which are available on the internet. You can download the packages and integrate it with any other tool. It really makes UiPath a better solution for organizations compared to any other tool.

The biggest lesson I have learned from  UiPath is that if a single step of the solution is not working, you have to keep trying. There are other ways of doing things. You have options. There are a lot of ways by which a user can understand and explore.

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

UiPath was used in-house in my first company for automating processes. We had deployed it on-premise. In my current company, we are giving UiPath automation as a service. We help companies with automation. We set up UiPath from scratch and help them achieve their automation goals or strategies. As a service, we have done on-premises and cloud deployments.

From a service perspective, we deal with a lot of clients who are predominantly in the oil and gas sector and energy sector. They have SAP systems for their ERP, and their use cases mostly revolve around automating SAP processes such as invoice automation, joint venture reconciliation, balance sheet reconciliation, and intercompany netting. So, the use cases usually revolve around the finance tasks, but sometimes, we have also seen use cases related to the supply chain and planned maintenance, such as purchase order closures, work order closures, and comparison of the work order plan with the deviations. 

In terms of the version, we always have the latest version. I've also used 19.4 and 20.4 on-premise versions.

UiPath enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring all of our automation. They have created a platform to handle everything from process analysis to deployment. If you just had UiPath Studio, you would have to procure something for your attended or unattended robots. You would also need a tool to capture the process or task itself. Similarly, you would need a tool to collect the ideas from subject matter experts. If you don't have a platform that covers end-to-end automation, it becomes very challenging, and you'll have to find ways to procure those applications. With UiPath, you don't have that headache.

It has reduced human error and saved time. These two are probably the best things that we achieved from automation. We recently did a deployment for a customer who had purchase orders and other stagnant stuff from 2011 onwards. These purchase orders were not closed even though they have been receipted and invoiced completely. We did robotic process automation to takes care of these purchase orders. It is a recurring job that takes care of all POs that were created in the last one year and closes them automatically. It used to take 5 to 10 minutes for the customer to close one purchase order and recheck everything. There were probably 22,000 to 23,000 purchase orders every year. The business benefit that the customer got was close to 1,200 hours in a year, which is a massive saving.

It has freed up employees' time. It has definitely reduced the time for our clients. The time saved varies based on the project. It has saved the time of associates in completing their tasks, and they can focus on a lot of other things. In one of the use cases, an employee was spending 10 hours every month to complete a process, which is 120 hours in a year, whereas the robot takes just one hour every month. So, the robot takes 12 hours as compared to 120 hours taken by a human, which is one-tenth of their effort. It has reduced around 90% of their time for this project. For the purchase order closure project, the robot has saved close to 1,200 hours in a year. That's a huge saving.

There are other use cases where savings were not huge in terms of the efforts or hours, but the robot was very much compliant with a company's processes. It eliminated any sort of human errors that could have occurred. For instance, balance sheet reconciliations always had some sort of issues and were prone to errors. The robot completely eliminated all those issues.

We use attended and unattended automation. We have a couple of robots on the finance team's laptops, and they trigger the process as and when required, such as for month-end clearing, which is a process where the end-users have to do some kind of clearing task in the SAP system. They can trigger it as and when required. This attended automation has helped in scaling RPA benefits. The overall benefit was in terms of the efficiency with which the robot gave them the mismatches. At the end of the day, it is giving the end-user satisfaction. They don't have to repeatedly do the same steps for every company code and intercompany code. It has definitely saved a lot of time for the end-user and provided satisfaction with the process.

With cloud offerings, UiPath handles infrastructure maintenance and updates, which saves our time as well as our clients' time. The clients do not want to worry about the infrastructure and other such aspects. We are generally the ones who provide services to the clients and deal with these things. When they use the automation cloud, it is definitely time-saving because we don't have to install patches and other things. If there is a new service that they introduced, such as data service, we don't have to install anything new on the automation cloud. It is all taken care of pre-default. We just have to enable it or disable it as per our need. That definitely saves some time for us.

Their automation cloud offering helps in decreasing time-to-value. It definitely reduces time as compared to on-premise because all that you need to do is procure an automation cloud and the licenses for the UiPath team and enable them. With the on-premises setup, there is an overhead of installation of orchestrator on the virtual machine. In this aspect, an automation cloud is better than installing everything on-premise for the client and setting up the orchestrator and things like that. The automation cloud doesn't have any other thing that reduces your time. Other solutions, such as Blue Prism, provide the same benefit when you use a cloud-based orchestrator.

It has a lot of features, but the ones that I'm really interested in and focused on are the Automation Hub and the Task Capture tool that they have created. Automation Hub helps you in gathering a lot of ideas, and Task Capture helps subject matter experts in capturing the step-by-step processes. It helps them build their SOPs or a document system wherever it is not already available. 

The Uipath Document Understanding framework is also very nice in comparison to Abbyy and similar sorts of OCR technologies. 

In terms of the ease of use, I would rate UiPath very high. If you have some kind of coding background in C#, .Net, or VBA, the development in UiPath is very easy. You can customize it as per a customer's requirements. It has an easy-to-use Studio where you can build complex automation. On the Citizen Developer side, people without much technical knowledge and coding expertise can also automate their basic processes. We have done some training internally within our management, and they found StudioX very easy to use for their developments. 

Licensing is one area where UiPath could do better and can be more competitive. It is a little expensive. Their bundling of products is a bit confusing. For instance, if we want the UiPath Apps license, it is bundled with Action Center, so you also have to procure the Action Center license. These bundles are not tailored as per our company's requirements. If we reach out to the UiPath partners who deal with the accounts, they usually take your request into consideration and see what best they can do, but it is still not easily customizable.

I've been using UiPath since the beginning of 2018. It has been three and a half years.

It has been reliable. We haven't had any reliability issues as such. Only the automation that we create could have inherent issues based on how a developer develops it. All of the out-of-the-box functionalities available in UiPath work as expected.

We have seen customers starting with PoCs and scaling up to have running production bots. There are around seven to eight bots per client, which is good. From a scalability perspective, UiPath enables you to scale things quickly. We could quickly procure all things and deploy an attended or an unattended robot from a PoC to production. So, its scalability is very high.

We have used their support. Most of the time, we reach out to the usual support logins that they have given. We also have a partner whom we keep in the loop if there is something very urgent. The support team has its own defined SLAs. If it is a priority one case, they get back within 24 hours or something like that.

We've always got a resolution for our issues, and they've always been helpful in that regard. They have got some technical guys who joined us over the phone and helped us solve some of the issues.

I have used Blue Prism and Automation Anywhere at the PoC level and the initial setup level. I've not developed any enterprise-level robot using these. So, I'm not qualified to tell the differences between these solutions.

When new clients ask us to implement UiPath for them, the implementation is almost always straightforward. We know whether they have a cloud of their own, and what they need to procure. We have that very neatly outlined, and UiPath has also given us step-by-step instructions that are readily available on their documentation portal. So, if you want to install anything, everything is very well documented. It is very easy to follow the steps and install it.

If you have everything in hand, it would take a couple of days. If your virtual machine is ready, we just have to install the orchestrator. We also have to install Studio on the machines of the developers. It definitely takes a couple of days.

Its price is on the higher side as compared to the other players in the market. They are tying up with a lot of other products such as Druid, but they are independently also very expensive. That's what the customers say when we start giving them options of UiPath.

Apart from the FKUs or the licensing that UiPath provides, if you are implementing an on-premise kind of solution for a client, you have to look at all the things that would be required, such as the virtual machines and the user IDs that the robot might use. We mostly deal with SAP, and if you are using SAP, the robot would have to log into the SAP system to get some data. So, the username that you would create within SAP is also licensed. There are a lot of other costs and related things that you need to focus on. There are a lot of things around UiPath that you need to deal with.

I would also advise using best practices while implementing the solution. Every developer has his or her own way of developing automation. A lot of times, we have seen a gap in the understanding and the kind of deliveries that teams do. So, it is very helpful to understand the skills and capabilities of a developer and see how that could impact the final deliveries from an automation perspective.

We provide solutions depending on our customers' use cases. For on-premise or cloud deployment, we follow the same sort of process and project plan. There is no huge difference in whether we use cloud automation or on-premise automation. At the end of the day, a robot has to do what is expected as per the objectives.

We don't use UiPath's AI functionality in our automation program. So far, we haven't seen any use case where we had to use any sort of intelligence or incorporate any sort of machine learning. We haven't had a necessity for that.

We are going to use UiPath apps in a new project that is coming up. We haven't used it so far. We did a PoC to see if we can connect the cloud apps to an on-premise orchestrator and if it is feasible, but that's about it. It is going to be implemented soon.

I would rate UiPath a nine out of 10.

We are using Studio, Orchestrator, and mostly the unattended bots.

Our primary use for this solution is to give time back to the employees.

We do not run our automations in a virtual environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. It's drag-and-drop, and all of the activities are there.

On a scale of one to five, judging how beneficial it is, I would rate the training a four. All of this information there is self-explanatory and it works. 

From the point where we started using the demo version, it was a couple of months until our first robot was ready.

This solution has probably helped to eliminate human errors.

I can definitely say that this solution has saved the organization time. With all of the processes together, we have saved one full-time equivalent person. 

The most valuable feature of this solution is the unattended automation.

This solution is easy to use and it saves you time.

In future releases, we would like to see more drag-and-drop, and more out of the box AI.

With respect to the stability, on a scale from one to five, I would rate this solution a four. We had some issues where we needed to get in contact with the support, and sometimes, UiPath crashes on our servers.

We have about eight people in our automation group.

Most of the time, the technical support for this solution is very good.

One one occasion, it was not very good. We had a problem with a new version. When we updated to 18.2, the robots stopped working after some time. We had a lot of emails that included session logs. I made it quite clear that it was really important because we were in the beginning phase and the robots had to run. In the end, I fixed the problem by downloading the next version, 18.3. When we asked whether the problem was version-specific, they never got back to us, which isn't very good.

We did not use another RPA solution before this one.

From the external consultants, we got the idea that RPA has the possibility to save us time and money, so we decided to do it.

The initial setup of this solution is straightforward. Orchestrator is easy to understand. You can connect the virtual machines to it and then run the robots.

In the beginning, we used a consultant from Roboyou to assist us with the process. Our experience with them was good.

We recognize ROI in terms of performance benefits as soon as a process is automated and an employee can do something else that is more meaningful. It is not a benefit listed on a spreadsheet, but the employees are happier.

Our licensing fees for this solution are €68,000 (approximately $75,000 USD) yearly.

Two years ago, we evaluated Automation Anywhere and Blue Prism, in addition to UiPath. UiPath was the best overall solution then, and it still is now. It has a big community, and you can download the demo versions to start testing immediately.

This solution saves us time in all areas. We don't keep track of exactly what we have saved in terms of time, but we can say that we have more customer experience. If somebody has a mundane task and wants it automated then we do it.

My solution for anybody researching RPA solutions is to try UiPath. When you want to start, it is easy to register and get going.

This is a good solution and it saves us time, but there is always a path for improvement.

I would rate this solution an eight out of ten.

It is looking externally at how we can enable the government to identify efficiencies and improve effectiveness. The other is, internally, how can we drive efficiencies within HR and finance, with everything that a big corporation can do. 

1. How do we help the government realize these benefits? 
   
2. How do we help our internal workforce benefit?

It is two different things, and they are similar, but they're not the same thing.

A lot of people externally are worried about the elimination of jobs, but at the same time, they still want that efficiency, and they are looking for it. We want to drive the effectiveness of the workforce, whomever we're working with. 

There are plenty of automation opportunities out there: DoD, the federal government, and commercial space. There are all sorts of stuff that we can do. Internally, we feel the same way. There are lot of things that we can do to make ourselves run more efficiently. If we are preaching to the government that they need to be using this, it's beneficial for us to say, "This is what we have done as a company."

Our company is 25,000 people across the globe. There are certain opportunities for us to include automation in what we do every day. We are doing it now by instituting RPA, specifically, and the tools that the UiPath bring to the table. It will be a game changer for us, if we can get it done at scale.

Automation is growing at our company. A lot of what we do is focused on AI. Going from zero to AI is a Herculean task. It's extremely difficult. However, there are many steps in-between zero and AI that we can do now to help realize the benefit to the company or the federal government, such as the benefits of the efficiencies that we can identify. That intermediate, non-threatening first step can be RPA, which ultimately will lead to enabling AI, but is not AI. 

Within our company, we are looking to identify what those pre-AI steps are, with the goal in mind that we know that the federal government is asking for AI. What we do in the interim is a type of level set, where you can build an algorithm, AI, or machine learning algorithm. This ultimately is what they want, but what they need right now is to aggregate their data in a structured way to be able to feed into those algorithms. That's step one. This is the first step to getting all your data right. It's not easy, because you have to take people out of the mindset of AI.

A lot of times, in the government, people say, "I'm wearing two hats." It's an idiom. The question I have in response is, "What if we could take one of those hats away?" We can take one of those responsibilities that someone finds cumbersome, or annoying, and remove that from their task list. We have them tell us the steps of their process, so we can automate it, if not pieces, but all of it. That is our starting point with a lot of people, "We can take this off your plate," which is definitely exciting for a lot of people. It scares some people too, but we're working on that.

The most valuable features are the unattended bots. Initially, we are going to be looking at a number of attended bots in a pilot phase for our HR internal operations personnel. We are going to come in and try to remove tasks from their daily lives, such as ten minute tasks brought down to five seconds, or we could just completely eliminate them, making them unattended.

The training and certification online is very helpful.

The software is easy to use, as a drag and drop function. Even if it wasn't, the type of support that we get from the people who work for UiPath is paramount to the capability of the tool. The ease of use has exceeded our expectations.

The Academy Live that I took was only a half a day course. There needs to be diverse set of courses for those introduced to RPA for the first time. There are different people who show up to this course: 

• The developer who is interested in automation and automating different facets of the tasks that they have, either at work or for their clients. 
• Business managers who want to know more about what RPA can do for my business or company. They want the operational and strategic level versus the tactical level of how do I get automation to do the thing I want it to do?

The course was only a half a day, and although we were able to provide two automations and build two bots, it would be helpful if that was extended to include the RPA story and pitch. E.g., What's the story that we need to tell in order to get people to say, "How do I get into the pilot phase now."

I would like to have the course do an introduction, "Welcome to the course. This is what RPA is. Now, let us build your first bot." 

The sales elements of why RPA should be there too:

• What is the value proposition that RPA brings to the table.
• Here is the expected ROI for a menial task, saving an hour a week equals this in the long term. Even if you can cut a 25 minute task out of somebody's daily routine, this is the benefit in the long term.
  

That wasn't there as much. I wasn't really expecting it to be there, but in the long term, if there are a number of different types of training courses which are offered, people will have different breadths of understandings of RPA can really do, e.g., it needs a hardcore developing training and a capture manager. It needs to explain what sort of things a capture manager needs to know. Maybe not necessarily how to develop the architecture for it, but what does that even mean? For example, how easy is it for me to get Orchestrator onto a server? How do I become a reseller of the software? These are the capture manager responsibilities, and it would be helpful if they were explained. While this is probably more of a day two of a training rather than day one. 

I would like to see a UiPath user group to discuss issues. I am unaware of all the activities and features, and this would help. Right now, there is just the user's guide and UiPath GO! It would be great if this feedback went back to the UiPath development team. We should also be notified of new features through an alerting system on UiPath GO!

With our focus on the federal government, they're looking at dozens of bots: Scaling of five instances of Studio, 10 bots of Orchestrator, and three unattended bots. That is far easier to scale than in the commercial world, where they are asking for 1000 instances of Studio and 500 unattended bots, touching 100 different processes. We haven't had that experience yet.

The current staff at UiPath won't let you fail (the customer support and customer success managers). They are not going to leave you hanging.

They are an honest broker. They told us when things aren't going to work. They've been upfront and transparent about everything with us.

Our developers have found that it is relatively straightforward. With any installation issues that have come up, we have always had somebody just be able to pick up the phone and call.

ROI depends on the complexity the project. Unattended bots tend to see ROI immediately, where attended bots take longer. The savings starts as soon as a bot is deployed.

Getting licenses has been relatively easy.

We have all the prices for the software. Every project is up for a negotiation on how it's going to be done. A lot of times, with the federal government, it will be necessary to put it on contract. When we are bidding for something, we need to know, how many bots are we talking about? The tricky part is when the government is unsure what they actually want. A lot of times when contracts or proposals are put on the street, the government wants something that can support 100 bots. That's not really helpful given that the price points for unattended and attended are different. So, clarification is often necessary when we're asking, what ratio of attended to unattended are you really asking for?

There is some initial sticker shock from a lot of people regarding cost, until you show them what the actual benefit is. Initially, people are just going, "Why?" So, the retort for that is, "Look how much you will save, time, and budget-wise with one bot. If one bot costs X, this is how much it will save you over one year. This alleviates the "Oh my gosh" face, when it's 1200 dollars for a bot. 

Getting clients, and our own people internally, to recognize that this is an investment in efficiency to drive effectiveness. If you can do that, and you can get past any initial sticker shock, thinking strategically and long term, then you've got them. But if they say, "Look, my budget this year is only 10,000 dollars. Why would I put that into bots?" That becomes a different type of discussion. It's mostly focused on, you're thinking about today. We need you to be thinking about three years from now.

If you look around at the other software systems, we have chose to go with UiPath because of the ease of the interface and also the customer support that we get from their people. There are a lot of tools out there. The reason why we have gone with UiPath is because of the relationships that we have built and the type of success that we are going to get working with their account leads.

We looked at Blue Prism, Automation Anywhere, and briefly at a couple of the start ups. However, we figured that they didn't have the ATOs that we needed to go within the federal space. There are a lot of people who say they can do this, or they say that they have an offering that can do this. In many cases, that is absolutely true. We wanted to be with a company that we feel is up and coming and will be around in the next decade. We want to use software that is going to be recognized by the federal government as number one, or at least very close.

Be prepared, because you are going to be asked a hundred question. This product takes a team. Your senior management needs to want this product and sign onto training. You will need developers capable of using the UiPath software.

UiPath is not just a technology business. It really comes down to a people business. The people and culture that UiPath provides us leads us to use their software more often.

The NextGen workforce is not going to be cutting and pasting for eight hours a day. That is not a function that a human should be doing anyway. Therefore, we treat RPA as a digital assistant, because who would not want a digital assistant.

People are finding ways to automate the reporting functions that Workday can really provide. This is not at an individual level. At the individual level, you can go in and check your benefits and check your 401K. However, at a macro level, we need people to run Workday reports pretty much daily, and that gets updated in the systems that we have. Therefore, our HR and finance people are all working with Workday, as people of incorporate these big management systems, trying to find new ways to automate them.

It is now on us and our team to be able to implement automation with the Workday, and have it work more efficiently. That will be our next challenge moving forward, automating Workday.

I have used UiPath for very few projects. My go-to tool when it comes to automation is Power Automate. The reason for that is that I work in the Microsoft 365 environment, so Power Automate is better connected than UiPath.

With UiPath, I helped some organizations in my company automate tasks like data entry into systems such as SAP. 

I like UiPath. I enjoy working on UiPath. It has a lot of different features to control, especially related to desktop flows. I helped some organizations in my company automate tasks like data entry into systems such as SAP. They had Excel files, and all that data needed to be input on standard screens in SAP. It was taking a fair amount of time to do it by hand. We created a flow that transfers all that data, interacting with the screens in SAP, and uploads that information where another alternative, like an API or mass upload tool, was not available.

It is pretty easy to build automation in UiPath. We could easily implement end-to-end automation. I was consulting a group within my company. I was helping them build the flow. For them, it was a game changer because they would have spent several man-hours trying to transfer all that data into SAP, creating all those SAP items. After that, they were not only able to complete the task at hand; they were also able to replicate and create more automations on their own because they knew how UiPath works. They learned a little bit more and were able to continue to expand the other processes they had.

We were able to realize its benefits quickly. It took us a couple of weeks to finalize the flow, but once it was built, we were able to start seeing the benefits. It definitely saved time.

I like the way that I can reference specific objects on the screen, like a specific text box, and add a value to it. The capability that UiPath has to recognize elements on the screen is what I found most useful at that time.

UiPath has a lot of courses for easy learning. There were several courses that I offered to the organization I was helping. I myself went through several online resources that UiPath offers to figure out things.

UiPath should be less sensitive to changes in the existing UI of the system we are trying to manipulate. If it was more intelligent in adapting to changes in the user interface and the tools we are trying to manipulate, it would be beneficial. If the UI changes or a label is changed, sometimes the whole flow breaks. Identifying where the flow breaks requires going into edit mode and making modifications. It might be quite extensive work with the new, updated UI.

I have been using UiPath here and there for at least two years. It is a part of the solutions that my company offers, but I have not used UiPath as much as Power Automate.

It performs well. I do not see any issues there.

I use Power Automate on a daily basis. 

It was easy. It took us about a few weeks for ideation, selecting UiPath as a tool, getting everything set up, building the flow, and testing.

In terms of maintenance, users continually review and upgrade their flows. They can reuse the existing flows to create new ones.

I am not familiar with the pricing. I worked for an organization where the UiPath was available, so I do not know what the pricing is.

It was through an internal community that I connected with the organization for which I did the automation, and that is a great advantage. They were looking for people to help create automation. I was curious about UiPath, and I wanted to learn. I raised my hand to build that for them. An external community or a learning community is something that has proven its value by creating synergies between people who do not know and people who already know a little bit, allowing them to get together and grow.

In my opinion, RPA solutions are alternatives to digital transformation. Digital transformation is a big project. When you do not have access to those big budgets or the structure to get into new capabilities on an existing system or implement a future system, that is when you go to RPA to supplement the digital transformation. If the use case is not eligible for the big capital investment or the big project investment, you go through the route of RPA.

I would rate UiPath a nine out of ten.

For two years, I have focused on automating workflows related to processing documents in formats like PDF, Excel, and CSV. Using the document understanding feature, we have handled forecast orders and purchase order invoices. 

If you use input files like Excel, PDF, and CSV, we can automate file validation, such as checking data accuracy, format compliance, or missing information. It's integrated with Boomi, so after the files are validated, they're sent to Boomi for further processing. 

Boomi provides us with the RTF file, and we use UiPath to validate its contents and correctness. It automates the process of converting the RTF file into an Excel file. Another process is remittance, where we can get files from clients, validate them, and submit them to the credit managers for correction.

UiPath reduces human error by eliminating manual work and intervention. Some human intervention is still necessary, but it has been reduced. Realizing UiPath's benefits takes some time because you may have some issues after the initial deployment. The UiPath Academy was helpful. I took some courses and achieved developer certificates. I'm still learning. 

It hasn't saved time in my work because I'm still spending a lot of time learning the software. It was new, so learning and implementing those things in my work takes time.

My favorite feature is Document Understanding. I haven't used most of the new features, such as AI-enhanced document processing and process mining. The document understanding feature is especially valuable because I can use it to extract and process invoice data efficiently. It enables the quick and accurate handling of structured and unstructured data. 

The flexibility to work with templates and machine learning models for document extraction has been helpful when dealing with various invoice formats and forecast orders. Data extraction from PDF has been smooth, especially with UiPath's capability to handle scanned documents using OCR and AI-based models. 

The taxonomy manager lets you define the structure and categorize data from multiple document types. AI center integration allows continuous improvement in document extraction accuracy by training models based on historical data. I have utilized AI and machine learning models in UiPath specifically for processing complex PDF and Excel documents. 

UiPath's AI capabilities, such as pre-trained invoices and receipts models, have effectively extracted structured and unstructured documents. For example, when processing purchase orders, the AI model identified key fields, such as invoice numbers, dates, line items, and currency details, with high accuracy. I have found the machine learning models to be especially useful when working with documents that have different formats. In some cases, additional training or validation was required to fine-tune the models for complex or irregular documents. Overall, AI models and document understanding are my favorite features.

UiPath is highly user-friendly because it has drag-and-drop functionality to design and develop complex workflows without much coding knowledge. This has been particularly beneficial when working with different document formats. UiPath's built-in tools and integration capabilities simplify the automation process, leading to greater efficiency.

We have end-to-end automation and integration with other applications. For example, we have portal automation that's end-to-end. We use it to log in to the website and sign in to different accounts. It enters the CAPTCHA, downloads the files, and logs out. It can complete the automation without human intervention. 

UiPath has many resources online. We use its academy and online documentation. If we face any challenges, we can find an answer on the forum or one of these resources. I've never had a problem finding solutions to problems. They have the best resources.

I would love more integration with Third-Party applications. Expanding the library of pre-built, plug-and-play connectors to include more industry-specific applications.

I have worked with UiPath for two years. 

I've never experienced lagging or crashing with UiPath. The app has never given me trouble. 

Installing the community version of UiPath was easy and only took five to ten minutes. 

I am using the free community version. The enterprise version is obviously a little expensive. 

I'm using UiPath on an automation project for my company in the banking domain. The use cases are for things like insurance claims and debit card transactions. We use it for our clients' requirements and also internally to address any of our company's needs for UI automation. 

When we started the client's project, they had a simple process, but they were dealing with a large volume of data. Most organizations primarily rely on Excel as their main solution, and they're doing processes through that. They wanted to automate Excel processes that they had been doing manually. UiPath improves productivity and saves time. For example, I developed a bot for processing insurance claims in UiPath. It involved checking documents and comparing them to the information in the databases. The process would take around 40 minutes to perform manually. We reduced that to eight or nine minutes per process through automation. It greatly increased the volume we could handle, producing a lot of value for the organization.

As we developed more automations for Excel, their manual work decreased, so they gave us more requirements. I've developed about 15 separate processes for the banking project I'm working on. Each process has its own way of doing it. We have developed network solutions. UiPath has contributed so much to the development of automation in our company. Our clients are pleased because they can boost their revenue by introducing bots.

UiPath has helped us reduce our on-premise footprint. The development cycle depends on whether it's a major or minor process. We start development, test, and deploy. After that, a support team will maintain the process, and we will not be involved again. We have multiple people working on a particular project, and it changes with every sprint of a cycle.  

UiPath Academy has lots of videos and other resources. While we can go to YouTube or some other source to learn about UiPath, we don't get a comprehensive understanding of the solution or the latest features. We can only get this through UiPath, and everything we need is in the courses. You can take a foundational course to learn the basics and get a certification that is valid everywhere from the advanced developer courses. Every company expects its UiPath developers to have this certification. 

UiPath's AI functionality is useful if we're working with unstructured data. For example, if we have a PDF where the data we want to extract is not separated, we can use AI to define the data for automation. I have done some practice use cases for learning purposes, but I haven't used AI in a project.

The solution helps to speed up digital transformation. I'm not sure about other countries, but many banks in India are still doing things manually and not using UI automation. This is a revolution in banking technology because bots are doing everything, and they don't need a lot of people to do the tasks.

UiPath can reduce human error, but a developer needs to understand the process completely that the bot will perform and provide all the conditions for how to perform things. After the client approves a project, we create a bot, and it will function based on the solution documentation. The UiPath bot will perform whatever conditions I give it. About 80 percent of the solutions we develop will complete the process without human intervention, and the remaining 20 percent of automations require some manual effort.

The solution frees up employee time because UiPath doesn't require much coding knowledge. If we can find a working solution for many purposes, we can download it. We don't need to spend time developing as many processes. 

I like UiPath's coding engine. We don't need to know much code. Most of the activities in UiPath are drag and drop. It's easy to build automations in UiPath. If we need support also, that doesn't require much effort. The UiPath tool gives us a structured framework. That is used in almost every project I work on. It made our development process effortless. We've completed a lot of projects with the help of the framework. 

The UiPath community enables users to share knowledge and bots that they've developed. If I have a bot installed in our machines, it doesn't require much effort for other users to run it. The user experience is seamless and user-friendly. Everything is ported on the back end, and it works as expected everywhere. If we have any doubt about a topic, we can post a question on the user community forum, and people from around the world will offer solutions in minutes. It takes very little time to get the solution. 

We only use the UiPath Community for support. It would be nice if a team of developers or a support person were available to help us work internally on our project. That would be helpful.

I have used UiPath since 2020.

UiPath is stable. All of my colleagues in other companies feel that this is highly stable compared to other tools.

UiPath is scalable.

I rate UiPath eight out of 10. We primarily get support from the UiPath Community, but sometimes their solutions work differently when we take it to our machine sometimes we have this capability. 

Positive

I also learned Automation Anywhere at the same time, but I found that the UiPath interface was easier for beginners to learn. 

We use UiPath as a cloud service. You create packages that are deployed through Orchestrator. Any machine with access to Orchestrator can just download the package and run it. The deployment is straightforward if we have the necessary access. We need to add a package to Orchestrator and download it. It doesn't require much time. 

We have a team of people. Every deployment includes developers, a support team, and an engineering team that will deploy the code to the production machine. The support team will ensure the bot is running properly after deployment, while the developer is the one who creates the package. UiPath doesn't require much maintenance aside from upgrading the bots with packages from UiPath. 

The pricing model is based on the number of processes. My colleagues tell me that UiPath's pricing is pretty normal compared to other solutions. 

I rate UiPath nine out of 10. I would recommend it to anyone who is interested in RPA. It's easy to learn and implement. You will not be disappointed. I still have a lot to learn. There are so many capabilities.