UiPath Reviews

We leverage UiPath for customer service use cases and process automation to improve employee productivity and reduce time spent on repetitive work. UiPath is mainly used for financial processes like automated invoicing, but we also use the solution for IT processes. 

UiPath is deployed on-prem on a private cloud, and all our BFSI customers are on-prem. BFSI customers tend to use fully on-prem environments. UiPath offers cloud and on-prem versions, but the functionality is the same. A few technical aspects are a little different. 

UiPath makes our employees' jobs easier by eliminating repetitive tasks. The solution has reduced the time spent on these tasks by around 35 to 40 percent. They can use bots and spend more time on more productive work. We've improved process efficiency and employee productivity using automation. 

It's helped us discover better ways to make each process more stable. Our productivity has increased from 20 percent to almost 45 percent. That's what the change we have seen using you about. Using UiPath has reduced human error by 99 percent. I can't say 100 percent because nothing is fully automated. 

UiPath's automation features are all equally valuable, but we use the unattended bots the most. UiPath is easier to handle than most RPA technologies, and it's easy to install, so it's a competitive solution. 

The UiPath community has helped us troubleshoot issues. For example, if a bot isn't working properly, we can go to the forums to find the root cause of the problem. My technical team uses the UiPath Academy to get certifications and gain a better understanding of the product, but I haven't used it. 

We use some of UiPath's AI functionality, which makes it easy for us. Predictive analysis suggests the next logical step and what could be the possible solution for that. It tells you the possibilities and the pros and cons of each step.

The OCR technology has room for improvement. UiPath accurately reads about 85 percent of the fields in a scanned document, but that needs to be somewhere around 90 to 95 percent.

I have worked with UiPath for nearly three to four years.

The uptime for our bots is almost 99.9 percent.

UiPath is highly scalable. We plan to increase our usage because we aren't using it internally. It's something we deploy for our customers, so the usage will increase as our business grows. 

I rate UiPath support 10 out of 10. There are many ways to get support, including the knowledge base, live assistance, UiPath Academy, and UiPath support center. 

Positive

I was not involved with the setup. I sell the licenses, and the technical team handles the deployment. UiPath requires some maintenance, such as platform updates, updating the bots, and adding workloads. 

UiPath has reduced our employees' processing time and our expenses. UiPath has cut costs by about 18 to 20 percent. You can start realizing the ROI within six months to a year.

UiPath is affordable compared to Blue Prism or AutomationEdge. A basic license covers the cost of implementation and recurring fees that depend on the complexity of the processes and workflows. 

I looked at Automation Anywhere and AutomationEdge. UiPath is easier to implement and use. Cost is the primary factor. Indian customers tend to consider the cost of a solution more than the features.

I rate UiPath 10 out of 10. The solution can't give you 100 percent automation for complex processes, but it gives you up to 90 percent. However, once you optimize a bot, you can reuse it for other processes.

Oracle has three broad categories: HCM, PPM, and finance. I have used UiPath to automate mainframe applications. I have automated all types of automation, including ServiceNow processes, PDFs, APIs, and web-based automation.

UiPath has a large number of Java and Python developers. Its modularization of packages for different types of activities and automation is very well done. UiPath also collects suggestions from end users and developers, such as those using the free UiPath software. In fact, UiPath does not release its enterprise edition directly; instead, it releases a free edition for developers to use and provide feedback on the forums. This gives UiPath a significant advantage. Additionally, UiPath has made its tool flexible by building it on the .NET framework but allowing users to also use Java and Python. This gives UiPath another advantage over other tools. I am not sure if other tools offer this type of functionality, but I know that UiPath does because I have used it for a long time.

It can connect systems that don't communicate with each other, enabling us to share data between systems using bots, which is important in the healthcare industry.

The application that was built for our organization is not capable of handling millions of users because it is very old. We must consider the Citrix application, the mainframe applications, and the desktop applications, which are also old. They were not designed to handle millions of customers. For example, CVS Pharmacy has millions of people using its applications on a regular basis. Therefore, we cannot expose that application to customers. We need to build a new client-facing application, but we cannot discard our existing application, which has been in our organization for many years. UiPath helps our applications communicate which improves our patient experience.

It helps our staff easily share data between systems by saving the information in Excel or CSV files and connecting the files to new applications.

We use UiPath to consolidate patient data from multiple sources into a single dashboard, which helps our doctors keep track of patient histories in one place.

The single dashboard helps our patients a lot because we save patient information in the same way for all hospitals including doctors, nurses, and medicines. This means that if we need a doctor nearby, want to change doctors, or are moving to a new city and need medical help, our data can help us find the right resources.

UiPath automation has helped our staff save time, especially for invoicing insurance policies in healthcare organizations. UiPath automation has saved millions of dollars and thousands of hours by simplifying the process in both the healthcare and telecommunications industries.

UiPath has streamlined tasks for our healthcare staff, especially data viewing, enabling them to focus on higher-value activities.

We use UiPath's AI and machine learning capabilities to understand documents. The machine learning process has significantly improved the accuracy of the bot's ability to read data from PDF files.

In 2019, UiPath introduced Computer Vision activities for Citrix applications. This was a major turning point for the company, and the functionality was very useful; I had not seen it in any other tools.

The OCR engine is a valuable feature. 

UiPath should lower its prices because many other RPA tools have reduced their prices, and Microsoft is a major competitor because it offers RPA services to its customers.

I have been using UiPath for over five years.

UiPath is generally stable, but there are bugs in UiPath Studio that require fixing or restarting the application.

UiPath is scalable.

The technical support is good.

Positive

I previously used Blue Prism automation, but at the time, the functionality was limited and there were not many features.

The initial deployment is straightforward. We have some design methods. The dispatcher will handle input, the performer will perform the tasks. All processes will be transactional: our first module will create the transaction, the second will execute it, and the third will generate a report.

We use the CI/CD pipeline to deploy our software. After the software passes UAT testing, we need approval from the technical team before deploying it to production.

The implementation was completed in-house.

UiPath is expensive. Automation Anywhere is much cheaper, and it does not have the same AI and machine learning capabilities or features. However, for some industry cases, such as document understanding and computer vision, these features are not required.

I evaluated Automation Anywhere, which was not mature at the time but is now. I also evaluated Power Automate, which has the best price of all RPA tools and is capturing a large market share due to Microsoft's bundles and integrations.

I would rate UiPath a nine out of ten.

We have thousands of people across the organization using the automation.

UiPath itself doesn't require maintenance but the infrastructure does at times.

UiPath offers a 60 to 90 day trial of its features so that users can try the solution before buying. We can also negotiate with UiPath sales to ensure that we see a return on our automation investment within the first year.

We typically solve for any use cases that falls under different business functions within our company. That includes finance, supply chains, services, IT by itself, and a little bit of engineering.

UiPath has improved the way our organization functions. The flexibility with which the business processes get changed is great.

A lot of times we know the method of operation, however, certainly it'll not be the same after a few months, a few years, or longer. Our dependent script or whatever is in place (that is dependent on that business process) has to be adjusted. The flexibility with this tool has enabled us to adjust those workflows quickly and deploy them so that our business can continue using those applications or the workflows that we’ve been using before, even after changes to the underlying system.

The most valuable aspect has been the workflows. They have helped to deal with legacy applications. We have a lot of legacy applications in place, which we cannot get rid of. The processes around these legacy applications are something that cannot be automated in a typical way. The RPA is helping us to automate the business processes that have to work with legacy applications.

The ease of building automation using the solution is great as it is a low-code solution.

I'm able to create workflows. By the time I'm familiar with one process, I'll be able to automate the next one. This is the case especially with tools like task capture; I'm just working through the process. In the end, it will be a skeleton workflow and it can be used for deployment once we are done with the cleaning. It has reduced the development life cycle by about 30%. It’s done this by making use of the features that are enabled by task capture and certain other features within the Studio.

Overall, we’ve seen the solution has saved costs. That is our value realization.

Our first target metric is to bring up the number of processes that we can save. We have a formula to convert inter-dollar values in terms of the user experience we are benefitting from. That’s the user experience that is enabled by automation. Those are direct savings which can be calculated by multiplying the number of dollars that we have spent for one resource per hour. Indirect monetary benefits can also be calculated by looking into the user experience factors and adding them when we do the value realization. In the last four years, we would've saved $3 million.

The human error rate has been reduced. Initially, when we targeted some of the business use cases, they were straightforward. They were linear in nature and there the accuracy had the upper hand 99.9% of the time. The reason is that the process by itself is quite linear. It doesn't have multiple branches or exceptional routes that it has to take to complete a particular transaction. We have good accuracy, however, we have had challenges with the accuracy when the business processes get complex. If there is any human intervention or if the quality of the data is not proper, or if the user errors are low, that is where the accuracy rate used to be low. It's better now.

Due to the fact that all these are role-based bots, if there is something that is getting changed, the bot will fail. Down the line, I can see that, for linear processes, accuracy will be great. However, when it comes to some of the complex processes, that is where we have challenges that we are facing with accuracy and we are continuously fine-tuning the process in such a way so that the accuracy can get better. It's great we can continuously tweak.

The solution does free up employee time and allows for the employees to focus on higher-value work. We have a lot of examples within our organizations where they have to deal with some kind of manually intensive task, such as just reading something from the document and putting that into the financial system.

We normally take up the customization portion that comes directly from customers. Those kinds of customizations have to be updated back into the financial system in order to make sure that they are appropriate. These updates take a while as they have to do with talking to the customer, understanding what changes are needed for a given order, or based on specific correspondence from the customers. With automation, employees can focus on talking to the customer to understand what changes they have to incorporate. And they can offload all the data entry tasks to a robot. This way, they can focus on how they can engage more with users to understand the pain points faced by the customer rather than spending time taking all those inputs and then doing the data entry job. They can be more client-facing.

I’m not sure exactly how much time is saved with automation. I could say that we have around 150 purchase processes that we have automated. We don't trace back how it has replaced a team or member of a team. We always go with the number of hours saved. We go the route of checking and saying “okay, so we have done this, but it needs a constant involvement from them in order to make sure that someone is owning the process.” We still own only the work.

We have started to use the solution's AI functionality in our automation. We started it recently and we have finished the proof of concept on document understanding, which involves AI, of course.

In terms of AI automation, we will be leveraging this tool for all business functions. There is no limit with any of the business folk that we talk to. Whatever the process is, as long as we feel that it is feasible to automate, and there is a value in automating it,  or as long as we feel that we are automating the right processes, we will just take that up into our pipeline.

AI does help us handle complex and involved processes. We include a lot of use cases where the sole core RPA capability would not suffice as a purely role-based automation. We often encounter a lot of use cases where they say, "Hey, this is something where there is no logic in doing it." If there’s analysis or natural language processing, et cetera, we are making use of AI. However, the process isn’t in use yet. We’re just starting.

We have used UiPath’s Academy courses and we are also encouraging our implementation partners to refer to those materials so that they can be approved.

It’s kept us up to speed with the solution. We refer to the Academy daily. Of course, we get help from UiPath whenever we face any hiccups; we normally ask them questions and they're able to sort it out for us. That said, the materials are great for trying to sort out issues or problems on our own.

It's been four years of practice and we've matured with the traditional RPA candidates. We have a strong foundation with what we have showcased to our business folks, and we are good with the healthy background that we are building. However, when it comes to the roadmap of what's next, that is where we are not clear. While we get the concepts, bringing them to reality is looking to be quite a challenge. We are unsure as to if UiPath can actually bring our vision to life.

UiPath is very clear in defining items such as this is what the high automation needs, this is what the process planning needs. We are getting clarity into those concepts and we are able to explain that and take that back into leadership to get other approvals. They are able to understand what UiPath is talking about within these different concepts. Really, it's just figuring out whether we have the right arrangement at this point and if UiPath can get us there.

I've been using the solution for four years.

I'm impressed with the version that we have today. 2019.10 is a version that is quite stable, compared to how we did with 2018. A lot of pieces that are enabled as part of the new version, 2019, are stabilized. We have zero downtime with the tool.

Today, ith X number of bots, if we want to reuse the same solution, and if there is an appetite for consuming those kinds of robotic solutions, of course, buying more bots is going to solve the problem.

If you think in terms of scaling this platform by itself or the other business functions, that is where the discovery piece will come into play. We have to constantly talk to businesses to understand where the opportunities are to scale in the correct manner.

Scalability is possible in terms of reusing existing automations. It's related to the number of bots that we are going to purchase. When it comes to the number of business processes that we are automating, during the discovery process, twe have to engage with our customers and constantly follow up with them. When we understand more about how they're doing business, we're able to locate the kinds of tools that are going to help them.

Currently, we have eight bots in production and 150 processes are automated. I’m not sure how many users are actually on UiPath currently.

We always follow up with our business to build our pipeline. That goes hand in hand with the implementation. We off-load all automation ideas and requirements to the pipeline, to our implementation partners, so that they will be able to implement our vision.

Traditional support for the RPA is great. In terms of the help that we are getting, if we end up with some issues, running operational issues, it could be better if they can propose some fixes. It's not that automation is going to solve every other problem that the underlying system is having. However, we expect some kind of expertise from the tech support when we face issues that are related to the system. We need to understand if there's an ERP error, if it has to do with the underlying system, or if automation has to solve the issue. Often, technical support will say "Okay, so this is your error, go and solve it." Yet, due to the fact that support has seen more issues like this, they should have more insights and they need to be able to share those inputs in a way that is going to help us.

While I didn't use a different solution previously, the finance team has used Blue Prism before. They implemented Blue Prism and they engaged Blue Prism to automate the processes that they have added for automation. Now, we have aligned on a single platform. It is UiPath now, however, they initially had around 50 processes that they automated using Blue Prism.

We proposed UiPath as the one solution based on Gartner ratings.

The initial setup was quite straightforward as we understand how RPA works and we understand how UiPath is going to help, how UiPath is a tool to help us to automate things. It's quite straightforward in terms of that. Whenever we are doing some kind of initiative, like document understanding or data capture, it is quite straightforward.

However, with process planning, we didn't understand the documentation right away. That is where we used to get help from UiPath.

The pricing was great at the start, and so, down the line, we have been enhancing all these features. We are seeing that, as we are looking for opportunities to grow, the number of robots that we need to purchase and the software cost is going to go up.

UiPath has increased the cost. We feel that it's good, however, based on all the new features, which we are pursuing. That said, we expect that whatever robots that we have purchased or whatever the standard platform that we have from UiPath should continue with the pricing that they had earlier.

There will be an offset, however, when it comes to the existing platform like Orchestrator or robots, and we are expecting that the margin should be less.

Back in 2017, we evaluated three to four products. Blue Prism was already used by the finance team, however, we evaluated WorkFusion, UiPath, and Automation Anywhere.

Of those other three, we evaluated WorkFusion and UiPath extensively.

The two reasons that we went with UiPath were, one, the learning curve, and, two, the community edition of UiPath, which had everything we needed to dig into the solution. Whereas with the other companies, there wasn't that option. With Blue Prism, for example, we had to buy a license in order to check whether the tool was going to work for us. In 2017, we were not sure whether this was going to work or not. At that stage, UiPath was the only company that gave us the entire set of tools to try and it worked really well.

We are customers and end-users.

While we're using the on-premises deployment, we are open to moving to the cloud. There are a lot of cloud solutions that we already use in our organization. However, with UiPath, we have stayed on-prem out of concern for security. We don't have clarity on if a cloud solution is going to work securely.

The other concern is around how we are augmenting the capabilities of core RPA. We know that process mining is going to help us, however, whether process mining is already added into the RPA, do we have any solid use cases that we can start with.

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

We have several use cases. We're a telecommunications company. We use it for anything from order entry, design, activation, and interactions with technicians within our field. We really have an end-to-end solution.

We are using Studio, Orchestrator, and unattended bots.

It is deployed on-premise but on our own cloud.

We had a long-time situation where we were sending technicians to the fields unnecessarily, because they couldn't install the service. So, we worked through a process to wake up devices. We used RPA to implement it. 

With downsizing, we have been able to automate a lot of this space, so we can downsize and still function as a company.

Capitalize on the unattended automation, as there are a lot of different methods to evoke and schedule it. You can email it, trigger it via API bots or Orchestrator. There are a lot of different methods you can use. We don't really do a whole lot of attended. Not that we wouldn't at some point, but unattended is nice because it's out of sight and out of mind. Set it up and let it go.

We are the first company to bring UiPath Academy in-house on the 30th of September. When we signed our licensing agreement, we added it in our own LMS. So, we have that connection and everything else. We love it. We've implemented all of their modules: RPA Starter, all three of the development courses, Solution Architect, Business Analyst, and Build a Bot. It's super exciting. It's one of the best things that we've done. I would rate it a five out of five.

We now have a functionality that is being released for web forms. It's more for attended. I would like to have these web forms exposed in Orchestrator to be able to trigger a bot externally. I know we have partners that provide similar functionality. I would like to have that same functionality where you could deploy a form, but instead of having it pop up on somebody's desktop, they could go through a URL through Orchestrator and trigger the bots via a web interface. This is instead of having to be tied down to an attended bot.

For some of the Insights stuff, we have found that you have to be flexible on measuring your ROI. You have to be able to customize some of that because it's not as cut and dry as you think it is. 

I would look for the audits on the back-end. Performance-wise, make sure that it is still performing. 

I would rate the stability as a four (out of five), but some of it could have been us too. 

An overabundance of logging that we created crashed the SQL Server. We had to adjust and restructure the way we were doing all of our logging to prevent that from happening again. Ever since then, it has pretty much been fine. 

We have had issues with upgrades. However, from a normal day-to-day functionality perspective, it is pretty stable.

Right now, we have about 150 developers. Then, we have engineers and process analysts.

We have 400 automations on average and 1000 in the pipeline.

It's been fantastic. It doesn't matter what time of day or anything else. We get top-notch service.

It has been about our contacts and support team. They look at us, and say, "You guys want to do what?" Then, they stand behind us and help us get it done.

We had merging companies coming together with a lot of integration going on. With integration, there are multiple teams, processes, and systems. To keep up for our reduced expenses, we had to do it. This was another tool in the toolbox for us: automation.

It took us eight weeks from initial purchase to the first bot to be put into production. It took about two weeks for assessment and documentation, then another six weeks to develop and deploy it. The bot that we developed was complex. It wasn't super simple. We've done simpler, but that time frame was about average for us.

We did the deployment ourselves, but we had the premium support. So, we did have some support from UiPath. However, everything that we did, we did on our own.

ROI was almost instant. We measured everything from deployment. We measured our successes. We do audits once a month. ROI was pretty much from deployment. We don't audit anything in the first 30 days because there is a lot of settling in, some bumps, and, "Oh, we missed this step." For the most part, within 30 days, we were realizing and managing expectations on benefits.

We're really only measuring handling time right now, which is defined by our business clients. They define what handling time we are trying to define, then the measure of success. That's what we measure ourselves on.

We're probably in the tens of thousands of hours that we have saved, easily.

Because we have so many agents, that's why we went unattended. Attended was very expensive for us because it's a per person license. Where we can take entire workflows, do the triggering and scheduling, etc. We never have to have any human interaction with unattended.

We have a cost model for operating expense savings. It is usually about $100,000 to $125,000 and takes us six weeks to develop and implement. That's development, testing, and implementation. We do code reviews on everything. That does not include all the documentation, assessment, etc.

We just signed a very large perpetual agreement. So, we had 125 Studios and 1200 unattended licenses. We paid $3.7 million. Then, we paid maintenance costs for the next three years, which was 15 percent of that.

We evaluated Automation Anywhere, Blue Prism, Pega, and UiPath.

Scalability was probably the number one that we went with UiPath. Scalability, the ease of use of the software, and the existing functionality that was there were the main reasons. There is a lot more out-of-the-box in terms of embedded functions that were there at the time when we did our analysis. It seemed like UiPath was really on the cutting edge. They were more proactively implementing good features, where others that we were talking with seemed like they were behind in that perspective. 

We'd rather stay on the cutting edge with technology instead of having to wait for our partner to get caught up.

Obviously, there are cheaper options than UiPath.

I'm really excited about the new stuff. There is great new stuff. We wish we would've had this stuff a year ago because we had to build some of it in-house. We are really excited about the Explorer and process mining.

I would rate the ease of use of the platform for automating our company’s processes as a three and a half to four out of five (where five is the easiest). It depends on the skill set of the developer. If you are a developer with a .NET background, then it will be a lot easier for more of the customization. For the technology overall, it is easy to automate our processes.

We run our automations in the virtual environments, like Citrix. We struggled a bit with Citrix at first, because our infrastructure and systems are somewhat antiquated.

Nobody is perfect. I would rate UiPath as a nine (out of 10).

Our UiPath automations primarily focus on web applications but also include tasks like extracting data from Excel for queuing, automating transactional processes and desktop applications, and even populating CRM and ERP systems with data extracted from PDFs.

The recording feature allows us to capture a manual process as a starting point for automation. We can then customize the recording based on the specific transaction, including how often variables need to be initialized and whether data needs to be passed between workflows. This way, the recording serves as a foundation to automate the core functionality and build new processes within the framework.

UiPath offers end-to-end automation for many applications, but I encountered challenges with NetSuite, an ERP web app. The connection kept failing due to NetSuite's slow loading times. While UiPath has built-in connectors for these situations, the lag prevented interaction with the NetSuite interface entirely.

The UiPath user community is a large and active resource for users of all levels. With community pages dedicated to specific countries, users can easily find information relevant to their needs. The community fosters knowledge sharing and learning, allowing users to stay up-to-date on the latest UiPath features. Beyond traditional documentation, users can access demos and connect with motivated developers to enhance their skills.

UiPath, a market leader in automation solutions, comes with a higher price tag due to its wider range of features. However, the return on investment takes time as initial costs cover development team setup and licenses. It can take between six months to a year to determine if the number of automated processes justifies the cost savings for our customers.

UiPath reduces our physical infrastructure needs by eliminating server management, maintenance, and database backups that are handled by the cloud provider. On-premises deployments require a disaster recovery plan for database backups and regular data maintenance to prevent performance issues, which are burdens eliminated by cloud-based UiPath. 

I honed my skills through UiPath Academy courses. Their learning portal proved valuable for exploring new features and pursuing certifications.

UiPath is a helpful tool for digital transformation, but its applications vary depending on an organization's needs. While many companies focus on automating tasks with PDFs like purchase orders or legal documents, UiPath can also handle images and perform sentiment analysis. Processing large, complex documents can be challenging manually, but UiPath can convert them into digital formats and quickly extract the necessary information, saving significant time. For example, a telecommunications client used UiPath to classify images from cell towers, while another client in the legal field used it to analyze contracts and identify key details like timelines and disputes. This eliminates the need for manual processing of large volumes of documents.

UiPath helps minimize human errors by automating tasks. It even allows us to create extensions in plain English. For instance, instead of writing complex code to find a phone number in a document, we could say "Fetch phone number" and UiPath would generate the necessary code for us. This makes automation development more accessible, even for those without extensive coding knowledge.

UiPath helped our clients save money by automating tasks. This meant they could reduce the number of employees needed. For example, a repetitive four-hour daily task could be eliminated. In a large call center with 100 employees, automation might reduce staffing to 20, saving the company the cost of 80 FTEs. This approach has been used in many industries, including airlines where manual searches in contact centers were significantly reduced.

The most valuable features of UiPath are the user-friendly UI and manageable learning curve. Their Academy offers valuable courses, and they keep users informed with clear communication and updated documentation whenever new features are released. 

I've submitted feedback to UiPath, including a suggestion to improve the slow mainframe connection currently limited to a 300ms timeout. Focusing on the connector would be a user-preferred approach, allowing interaction with applications like ServiceNow, SAP, or Salesforce and future ones like Dynamics 365 or ERPs through activities instead of custom code. This reduces development time and reliance on technical expertise simplifies maintenance for future teams, and provides a user-friendly, reusable component.

I have been using UiPath for eight years.

I would rate the stability of UiPath eight out of ten.

I would rate the scalability of UiPath seven out of ten.

I've encountered various issues with UiPath products, including activity connection problems that worked fine during development but not in production, occasional defects, and personal knowledge gaps. Sometimes these were bugs addressed in later patches or releases. To find solutions, I'd first search the UiPath forum for answers shared by other developers. If unsuccessful, I'd submit technical support tickets based on our UiPath service level. Responses came quickly, and for premium support, we could directly contact our technical account managers for immediate issue resolution.

We can expect an email response after submitting our ticket. Response times for standard support subscriptions range from one to two days, with issue resolution taking up to four days. Premium support offers immediate response and prioritizes issues based on the number of affected machines and their importance in our workflow.

Neutral

UiPath deployment is very manageable. With their cloud option, they handle everything and provide a URL for easy access. Even on-premise deployments are straightforward thanks to UiPath's clear documentation. While some IT team coordination is needed for on-premise security and Active Directory integration, the process is generally simple and can be done within a few days. Overall, cloud deployment is the easiest option, but on-premise is also achievable with good IT support.

UiPath deployment on the cloud is fast, but additional setup is needed for large organizations. While integrating with our existing IT directory keeps user creation a few hours, creating separate environments, machines, licenses, and folders can take a few days depending on the complexity of environments, machines, libraries, and use cases.

One admin person is sufficient for deployment from our end.

I evaluated Power Automate but UiPath has more features.

I would rate Uipath seven out of ten. UiPath's process mining feature, while desired by many users, appears to be limited in its current functionality. Since many haven't implemented it yet. UiPath still needs to refine this area.

UiPath does not require maintenance from our end when it is deployed in the cloud.

My current retail organization uses UiPath for finance-related activities like invoice generation. We also use the solution for pulling documents from any stored devices for customers. We save customer files like licenses, invoices, and other tax-related documents in the box. If customers want to use such files for any purpose, we need to extract them from the box environment. A bot will check for that particular customer-specific file, download it, and save it in client-shared locations.

Transactional details regarding whether a customer has delayed an EMI or paid the EMI on time will be updated in the system. A bot we defined using UiPath will do it around the clock without any human effort.

The most valuable feature of UiPath is the complete queue system-based framework because it is robust for all clients. If something goes wrong, we can define how many retries we can do for a particular request. In the next attempt, it can be achieved in a proper way.

The end users can expect the results without any manual intervention. This framework is very user-friendly, convenient for the developers or system integrators, and satisfies the client compared to other frameworks.

I would like to see more clarity in the solution's AI functionality. I have not completely implemented AI for our client. I'm trying to understand the areas in which AI will be more usable for my client.

The OCR is the only area where I expect a little flexibility and improvement. If you try to extract scanned documents or photos using any native or Google OCR, you won't get 100% accuracy.

I have been using UiPath for more than five years.

UiPath is a stable solution.

UiPath is a scalable solution. UiPath is deployed in one location with around 5,000 end users using the solution.

I also have more than four years of experience with the Blue Prism tool.

The only major difference between UiPath and Blue Prism is that UiPath is deployed in the cloud, and now Blue Prism is trying to be deployed in the cloud. Other than that, I did not observe any differences between the two solutions. Both are good products in the market, and customers are happy with both solutions.

UiPath's initial setup is easy.

Around two people are needed for the solution's deployment and maintenance.

Our customers have seen a return on investment with UiPath and are happy with the licenses, pricing, etc. They haven't raised any concerns so far, and they're increasing the licenses based on the processes we are deploying.

I'm a system integrator and one of the lead developers of UiPath for the end customers.

I use UiPath in the banking and retail industry.

UiPath is deployed on the Oracle cloud.

I would recommend UiPath to other users. The users need to configure the environment in a better way. If an organization wants to utilize only four or six bots, it needs to plan ahead and consider how big it plans to grow in the next five years. Planning in advance would clarify how the organization needs to configure the environment and what challenges it needs to handle. That's a better way to start using UiPath as an RPA tool.

Even before the deployment, we gave an estimation to the end clients regarding what to expect after deploying the solution. We told them about the things they will be very comfortable with and the time interval they will take to know things. They are comfortable and 100% satisfied with the solution.

Overall, I rate UiPath a nine out of ten.

We use UiPath to automate back-office tasks.

UiPath helped us with compliance-related tasks. These tasks involve reviewing various systems and taking screenshots to get proof of compliance. It's a costly process that can be mostly automated. The employee doesn't need to collect all the proofs; they just have to check if they are correct. For example, they must verify that the referenced time stamp is correct. 

They can focus on quality instead of doing all of the manual work, which requires a lot of time and effort from the specialist doing that auditing job. Automation frees up the auditor to do more critical tasks. A bot can handle repetitive, menial jobs. 

If you have some tasks that must be done at the start of the day, you can configure the bot to run first thing in the morning to retrieve all the details you need. You can get the report and start working on it. It's hard to estimate how much time it frees up because it varies from client to client, but if you plan well and use UiPath strategically, it can cut the time in half.  

UiPath enables us to do complex end-to-end automation for multiple systems. Some of our automated processes take input from the ERM software and enter data into various applications. UiPath can sit and listen to any SAP solution, depending on the requirements, and report to the business user, who can validate it. 

The user community is amazing. UiPath put a lot of effort into fostering a community, and now it is so mature that we can find a solution for 90 percent of our problems in the forum. 

UiPath has a small physical footprint. It's not like a typical enterprise application that requires multiple servers. You can run various automations on a field workstation. Numerous processes can be automated on a single machine. 

The UiPath Academy courses are helpful. It's a great way to learn queries and new techniques. I got my initial training from UiPath Academy, and we use it to onboard junior staff fresh out of college. We first direct them to the UiPath courses and follow up with one-on-one training. 

UiPath reduces the cost of digital transformation. For example, you can automate the process of extracting information from devices. If you aren't confident that the automation is accurate, send it to a human staffer to verify and make corrections. You can put a human in the loop if necessary. It may still require some labor, but it takes much of the burden off your employees. 

It reduces human error if you have fool-proof automation developed. If you have good rules that fit, it works smoothly without any help. With the proper ruleset, you can eliminate errors 100 percent. 

UiPath is a complete RPA product suite with machine learning packages and out-of-the-box processes. I'm a developer, so I primarily interact with UiPath Studio. It has a large set of activities ready to use, reducing the time we spend developing bots. The Orchestrator interface is thoughtful and easy to use. In Orchestrator, you can deploy processes and choose from various triggering options.   

Building simple automations is easy if you have a little technical knowledge. It takes more expertise to create complex automations. UiPath has a different product line for non-technical users, but it has some limitations. 

The more advanced developers use UiPath Studio, which allows you to enrich processes with Python and JavaScript. From a developer's perspective, it's almost a perfect 10.

UiPath could gain a lot more customers if they lowered the price a little and improved the license model with some more affordable tiers. 

I have been using UiPath for nearly six years. 

A few years ago, UiPath wasn't stable, but it matured a lot since then. 

UiPath has built-in features that help you scale your automation, and you can deploy automation on multiple machines simultaneously. 

I rate UiPath support a nine out of ten. Their support is decent. I get a fast response when I have questions. I haven't had any issues with them.

Positive

I used Blue Prism and Automation Anywhere for learning purposes. UiPath is easier to use and has a more extensive user community. UiPath's constant improvement is outpacing other platforms. 

Deploying UiPath is straightforward. It requires some maintenance in terms of modifying and updating your existing processes. You can reduce the overhead maintenance if you have a good developer interface in place. The maintenance is minimal compared to the benefits. 

A good consultant can help you implement automation and maximize your returns. Automation implementation can range from fifteen days to six months. You'll see a return in as little as one month. For that to happen, you need to implement it strategically. We see a 10-20 percent return, depending on the process.

I rate UiPath a nine out of ten. 

We currently have 150 bots in production. It is used the most where there are repetitive, cumbersome tasks. Where we do need to have somewhat of a decision made, we put it into a decision tree. This is our primary use case. 

We are looking into other use cases, such as:

• How do we use it as a platform for pretotyping?
• How do we use it as a platform to drive forward machine learning and artificial intelligence usage in our company? 

We have automated assignments where we previously used employees. The outcome of this has been a greater customer experience achievement. We simply are solving tasks faster, and at the same time, we have been scaling down employees. 

We have started to do tasks more often and faster than we have ever done them before. For instance, some of the things in finance, we only did that once per quarter. Now, we have started doing them once a week. This gives us greater insight into those areas. 

The most important outcome here is the amount of insight which you receive when you put power to a process. It gives you the insight that you wouldn't have had when you had 20 employees working. With two bots doing the work, you suddenly get a data foundation that you didn't have before. Then, you can build upon the bots, instead of thinking you know what is happening.

The platform is object-orientated. You can create and reuse objects, which is a great feature. 

UiPath has decided that people who are great at what they do can be invited into the platform and utilize services on the platform. This is another great feature, and one of the reasons that we initially chose the product as our platform.

The solution is easy to use. When you put it together with the UiPath Academy, it's easy to get it going and understand. The drag and drop feature makes it simple and easy to use. The UiPath Academy is great and helpful.

We tried utilizing the virtual environment, but we had some issues in that area. It's one of the areas that we haven't revisited over the last half year because our volume is that high for us. Thus, it is one of those things that we have sort of left on the side for now, but I do hear there is some great stuff coming with it.

We haven't had instability issues.

It can scale.

The customer and technical support are great. We have received fast, sufficient responses. There is easy access. 

We did not have a previous RPA solution.

We were in a place where we needed to do something differently. At the time, RPA was something different. So, we needed to sort of examine, "Could this help us?"

The initial setup was straightforward.

We saw ROI in eight or nine weeks, so it was fairly fast. We have seen a lot of performance benefits, which I would rate as a ten out of ten.

The solution has helped to eliminate many human errors.

Our licensing costs are roughly 1.1 million Danish krones a year. 

We see some elements in the license model that we're trying to figure out how to utilize. There have been some elements in the license model where UiPath has helped us solve them commercially, and having a license model which is more focused on scalability would be a great feature.

If UiPath really wants to put Attended Robots out to everyone, there will be a cost issue. We have some that we are testing now and what their effect will be. However, these are the robots where the license model needs to change before we go full throttle in that direction.

We also looked at Blue Prism and Automation Anywhere. We selected UiPath based on its object-oriented approach.

There is something off in UiPath's licensing model. Their competitors have started targeting us now because they know that we have a lot of bots. They have different types of licensing models, and say, "Because you are having so many jobs with so many job bots, you can save money on the platform by using us instead." 

Play with it and have a playful nature. Acknowledge that you don't know what you're doing with it, then just acknowledge that you're going to make mistakes. The only difference between being good or great at this solution is your ability to learn from your mistakes, because you will be making mistakes. Also, you will be overpromising when working with this solution.

For automation technology, in general, the system landscape is quite wide. We are just starting to put RPA on the shelf for automation. We are pushing a machine-first approach. RPA is the sort of tool on the shelf now helping us become a more efficient customer-oriented company. It is a tool in the landscape with plenty of existing tools, but this is the one that is the most easily accessible for the business people.

We built ourselves some automated documentation, and it was fairly easy to copy. One of the things that people start doing is documenting what they're doing in an organization and updating the documents, then freely sharing them. We would like some sort of automated documentation, as this would be helpful.