UiPath Platform Reviews

I am a UiPath developer and my role in the company is as an automation developer specialist. I'm working mainly in UiPath Studio, not Studio X, and I also work with Orchestrator. We are using attended automation.

We are automating the processes in our company, for example, in the finance department. One of the ones that are now automated is invoice coding determination, which no longer involves humans. At this time, 80% of our processes are completed by robots. The remaining 20% is approved by humans but I think that this will improve later. 

With respect to the ease of building automations using UiPath, from my experience, when you have a basic knowledge of programming, it is really easy for you to start your journey with the UiPath environment. You can do it without this knowledge but then, you will just need to spend a little more time learning the details.

I really like working in UiPath because the programming allows me to do whatever I want. I can declare any type of variable, I can check the locals, and I can add breakpoints whenever I need to check the states. For me, it's a very professional platform.

I really like that they offer the possibility to work with it from two sides. It can be operated from the full-programming side, as well as from the standpoint where you don't need this knowledge.

UiPath has helped to minimize our on-premises footprint, although I cannot estimate by how much because I am not responsible for that aspect.

UiPath has helped to reduce the cost of our digital transformation because it really speeds up the processes. When we compare the time it takes for a human, with perhaps a one-hour task, and it only takes 30 minutes for the robot to do it, we can see the savings. You just multiply this by the salary and we also see the reduction in cost.

UiPath has definitely reduced the number of issues arising from human error. We can confirm this with 100% certainty because we have compared it to when humans were completing processes on their own. I estimate that the error rate has been reduced by approximately 60%.

In my previous company, we managed to save about 20 FTE after our UiPath implementation. It was about two years of work. Thanks to the ease of access, as well as the fact that our employees did not require programming knowledge, we were able to show it to normal employees and explain the automation. After this, they were not afraid that they will be replaced by robots and instead, understand that they are co-working with them.

The most important part of Studio is the debugging feature. It gives you the ability to watch local variables, as well as highlight elements as it is moving through the process. The results of actions are displayed and indicate whether particular actions are performed successfully or not.

Outside of the company, I am using UiPath's AI functionality and it very much speeds up processes and improves accuracy for reading data. For example, the OCR is much better than Microsoft's solution. With UiPath, I was able to read handwriting samples but with Microsoft, I was unable to do it.

The AI functionality has allowed me to automate more processes in my own projects. It adds flexibility and improves process speed. I don't have to think about boundaries when I decide how to approach a project. 

It lacks something crucial, which is a map of the variables and arguments. When we are using a lot of variables and arguments, sometimes, we get lost. UiPath should create a map that connects different files and shows the connections between them. For example, from file A, we have variable B, and file C contains variable D. However, they are actually the same variable, but it's connected by argument and we don't know it. It is something that we have to remember explicitly. In this case, it would be really helpful for me, as a developer, to have this picture of the net. It would show me what is where and how it's connected to everything.

For the on-premises solution, if we ignore any problems that may occur with the infrastructure, such as the network, then stability is very good and the platform works well.

In my experience with cloud-based deployment, I haven't faced any problems with stability.

Scaling UiPath is really easy. When you get to the point where you have to think about scalability, you use the UiPath Installer to extend the Orchestrator by another node. There is an option for it and you don't have to know much about the network to do it on your own.

I am part of a four-person development team that is working primarily with Studio. We have approximately ten processes at the moment, and it is difficult to estimate how many employees are affected by the automation. 

The technical support is very professional and they work quickly. Usually, we are able to get responses in about two hours. Sometimes, it takes one day, but I have not faced a situation that took longer than two days.

The help from their site is also very professional, and well-described.

Overall, it is really easy to resolve errors.

Prior to UiPath, I used Selenium WebDriver. The problem with this product is that you have to know the Python programming language. You have to know everything inside Python, and there is a lot more typing. In UiPath, you have some clicking, and there is some decent orienting stuff, which you don't have to define. You already have some pieces of code that you can use, and this is a really nice feature.

I have also used Kryon RPA and the problem is that it's based on the OCR. This is something that I would never accept with an RPA tool unless the OCR is fully working. Right now, OCR is not a perfect technology and it causes many issues. UiPath allows us to use selectors, so we are able to track the exact area of the display in the program that we want to access.

The initial setup is quite easy, although we faced a few issues. With the help of the UiPath service desk, we were able to quickly fix our problems. The deployment was completed in a few hours on one machine. This included checking everything to make sure that it was working fine.

We followed the documentation provided by UiPath, as well as their guidelines.

At this time, we are using the on-premises version. In the next few months, we plan to move to the cloud environment, so we are currently planning the transition.

In my previous company, I was responsible for moving to the new version of the UiPath, with the Apollo interface in the Orchestrator. Where I am now, this was already done. So, yeah. I was responsible for this transition. Right now, in this company where I'm working currently, the UiPath setup was already done but I helped with the optimization.

With respect to upgrades, once we knew what had to be done, it took about one hour to complete. Otherwise, there is no maintenance required.

I have calculated ROI for our project and it seems that we will reach our ROI point in approximately two years, which is quite good.

Price-wise, it is not the cheapest one on the market, but it provides the fastest automation and the best training that I have ever seen for RPA, through the UiPath Academy. It's really easy to set up a new developer in this environment. Everything considered, the pricing is very good.

There are no costs in addition to the standard licensing fees.

We are currently evaluating Kryon RPA.

My advice for anyone who is implementing UiPath is to always check the documentation before you try to look for answers on the forum. Another good point is that when you have a problem, there are plenty of people in the UiPath community that can help you in a few minutes. This is the perfect solution, in this case.

From the maintenance side, you have to remember to increase your database with the scaling up of the automation because it can really slow down your process.

The biggest lesson that I have learned from using UiPath is to always create a backup copy of Orchestrator before you update it. This was a very big lesson for us because we had an issue with the installation. It is also really important to back up the related databases.

I would rate this solution an eight out of ten.

We have a cross-platform infrastructure, where two servers are sitting. We have Orchestrator, which we connect to our virtual desktop infrastructure (VDI). In the VDI, we have a UiPath stationed. 

From India, I work for an Australian client. Previously, I worked for a European client. In order to work with the client network, we have a dedicated Wipro laptop. In that Wipro laptop, we log in and connect via the VDI. In that VDI, we have UiPath Studio. Using UiPath Studio, we are doing development for the client and automating functional business processes.

We are extracting data from Salesforce using a particular report that is sent by the business SMEs. We pick exact fields end-to-end, then we put these values into Salesforce. Next, we extract the value and data from Salesforce, putting that into an Excel application. After putting the return to Excel application, we generate a service request for the business and send transaction reports of the bot's performance and accuracy at the end of the day. The business was taking around four to five hours. Our robot takes around eight to nine minutes in order to automate this end-to-end automation.

For another use case, there is an application that submits invoices for an insurance client in Australia. Right now, the business is doing this. Whereas, the bot operations reads a file on the hard drive, picks up that file, and puts it into SharePoint where the bot performs some operations. After doing those operations, the bot will report the status, whether it is valid, invalid, or an exception. When we get the file, we develop the application that submits the invoice. After that, we capture the data from the Excel application and submit a request. This is an end-to-end process. This bot only runs after business hours, five days a week, so it doesn't impact the application. With this process, we send daily transaction reports, the success ratio to the client, and present the entire picture to our peers and business holders.

We have set up our own cloud, which is internal. UiPath has a different cloud. Per our governance, we are not allowed to use another cloud. We are using our hosted internal cloud, which is hosted on our internal servers in Australia.

With our rule-based tasks, we pick the processes which involve a higher transaction volume and run many times in a week or month. Next, we analyze how much time the subject-matter experts (SMEs) uses to do their end-to-end journey. We calculate that, then decide the scope of the operation and whether to use an attended bot or unattended bot. We do analysis to determine which parts of the operation can be attended and unattended. Our preference would be the unattended bot, because it handles a lot of volume and is uninterrupted. 

In our analysis, we thoroughly check the scope of the application, whether it is a legacy or new application, and the dynamic nature of the data. Based on this, we define certain rules. Combining these rules, we design a complete end-to-end solution and give a presentation to the business that this is our commitment, e.g., this is the amount of Average Handle Time (AHT) and FTE that the bot will do. FTE means that if four people are doing a task, then it will give me back four FTEs. We then calculate the cost, meaning how much they are paying to that FTE and the cost of the bot. We compare the two and present our case. If the numbers are good, and the business agrees, then we proceed further in our discussions with them. This is the power of analytics.

We don't need that much infrastructure. If an analyst is doing reporting with an Excel sheet, then we can give him a bot and capture what he is doing without paying attention to the infrastructure. From the captured information, we give them a bot that will help them to do their regular task. This process helps them to understand automation while not investing in infrastructure. 

We design end-to-end solutions. We have different roles, teams, and divisions. I am part of the technical department, so I design the solution. I am responsible for analyzing and developing the solution. Once I develop the solution, I monitor the bot for two weeks, which is the "hypercare period". After the business is satisfied that the bot is performing, we give it to the support team. This is how our RPA lifecycle flows. It has around nine stages, including discovery, analysis, design, development, support, presentation, and solution. 

We have developed a bot process called "Padlock". In "Padlock", there is security development. It is very important that the user input his credentials. Per the governance of the process, we are not allowed to store the credentials on the cloud. It is very dynamic and encrypted. We have deployed about 25 robots for this particular process. The robot does its job after the SME. After a certain point, there is a CAPTCHA. The robot helps the SME do things, and they need to input their credentials and click the CAPTCHA, which happens in real-time. They verify all the information, giving them more confidence in their regular processes. We have deployed a large number of bots using this process. This has brought a lot of value because we have saved on a good number of costs when it comes to attended automation. 

I have found Orchestrator is UiPath's most valued feature. It has the ability to automate different applications, such as, mainframe automation and Excel macros. It is so efficient. We can download up to seven days back in just one click, monitoring errors.

It gives you the ability to efficiently monitor the bot.

With the new updates, a lot of analytics have come from AI Center.

Its features help us showcase what the bot has done and efficiently delivered to the business.

They are improving the OCR feature for reading text and images as well as the operations for automating that. They have integrated third-party OCRs, such as, SharePoint, ServiceNow, Salesforce, and mainframe automation.

The advantage of using StudioX is I can see how long the bot will take or what went wrong for any particular use case.

In the future, I would like new services that can utilize robots as a service (RaaS).

Our legacy applications are a bit old, so we get issues sometimes in automating those. However, modern applications are very compatible with the UiPath tool.

We have seen that UiPath doesn't have the capability to identify unknown pop-ups. This needs improvement.

The API needs a lot of improvements because it does not give proper results. There are always some issues with the logs.

When it comes to real-time scenarios, we see in production that Citrix automation always crashes. This integration could bring a lot of value to UiPath. Our business could save a lot of time and money if we could automate Citrix effectively.

All of our code resides in GitHub, which is our central repository for managing the code. There was a performance issue using GitHub with UiPath; it was slow. They have recently upgraded the performance so we are happy with it now.

I have been using UiPath for more than four years.

We always design a stable unattended solution that helps the business.

If fields are scattered, then the bot might get confused. 

Maintenance is handled by our support team. When something crashes, our dedicated support team monitors the bot. If the application crashes in production, the bot will send an application link to the support team and business stakeholders because the bot has faced some downtime in the application and kindly look into that issue.

Because I have automated a lot of enterprise solutions, I would go with the UiPath tool. They are frequently rolling out updates to the software. It is very stable compared to other tools in the market.

Infrastructure is quite important at an enterprise level. There are a lot of mundane and repetitive tasks. Once we have the infrastructure, then we set up best practices and governance. Based on that infrastructure, everything can scale up. Though, if we are going to build a lot of bots on a personal laptop to automate something small, then infrastructure is not as important with that.

We started with two to three bots. Now, we have around 25-plus bots. There are around 300 to 350 using both attended and unattended automation.

I have spoken a number of times with the UiPath product team. Initially, we were not able to use Excel, so we contacted the UiPath team. They provided a solution. They support the product well. I would rate the tech support as seven out of 10.

I have previously used Selenium. We switch because of scope. The Selenium tool was good with bot automation. With UiPath, we can do various automations, like mainframes, ServiceNow, SharePoint, etc. In order to increase implementation of automation from my end, I started with UiPath. I liked it because of its ability to automate applications. Those are the main reasons that I switched from Selenium to UiPath and SoapUI to UiPath.

The initial setup and deployment are pretty straightforward. They provide free training, which is a good thing. We do the training correctly and religiously. Once we are good with the training along with a little programming knowledge that we have acquired over the years, it is easy to adapt and work on UiPath because it is structured and organized. 

Our setup is a mixture. Orchestrator is hosted on a server and the application is installed on a desktop or system.

In order to use UiPath on servers, we need to set up two servers: one in Australia and the second in New Zealand. 

The implementation is not that big of a task. It is very organized.

It has been a huge monetary benefit. Since the bot has been running for two and half years, it has given my organization a lot of business. When I joined Wipro in 2019, there was one guy who was developing the bot. We named the bot, "win-back". As the name suggests, 'win-back' means winning customers back. That was a maintenance bot which possessed a lot of qualities. If a person was physically doing the task, then we might need to spend $90,000 on them. This is the difference. While the robot has some costs, they are not huge when compared to the salary or compensation that we give to an SME. This is how an organization can scale up, because the bot works accurately 24/7 without any maintenance. Also, seeing the bot's accuracy, as well as the volume that it handles, motivates other business holders to go for automation.

We automated an internal solution because there were long keywords that led to spelling mistakes, since spelling mistakes don't look good on invoices. Therefore, we input this extracted data to an application, using end-to-end automation. This reduced human errors tremendously. For example, with the "win-back" solution, errors tended to happen because the volume is high. Therefore, we wrote a code that has reduced errors for the "win-back" solution.

Because of the bot's accuracy, it has saved us a lot of time and money, making the life of the subject-matter experts easier. It is a win-win situation. They are making the most of the bot, running it continuously. They don't need to wait for a particular report. For example, people, in our organization, work eight hours then send a status mail, which says, "I have done all these tasks." Instead of having us create the report directly, the bot saves a lot of time. 

The bot marks in the report what is successful and unsuccessful as well as the reason for not being successful, e.g., if it was an application, data, or particular element issue. There are a lot of areas that we call "exceptions". Every day, we are getting all these details in one go. Whereas, a person would be frustrated or bored providing all these figures. That is the cost of human error. If you are not paying attention to a particular task, then errors will happen naturally. 

The bot currently performs four times faster than the SMEs for the tasks that we automated.

After three or six months, we send out a survey to different SMEs in various production areas, asking how the bot is doing. From the survey, we have found that the bot is helping them out a lot. They are very satisfied with it.

The solution has reduced our costs by approximately five percent.

I have seen very high ROI from the processes that we automated. It is very good to invest in automation.

There are three leaders in the market: UiPath, Automation Anywhere, and Blue Prism. UiPath is in-between the two. BluePrism is on the higher end when it comes to pricing. Automation Anywhere is on the lower side when it comes to pricing. When comparing the automation of business processes, analyze the amount of work that your organization will save using automation, particularly compared to the pricing.

You will be compensated for buying the product when you see processes automating.

I also evaluated Automation Anywhere, Blue Prism, and EdgeVerve (which I used in a previous organization).

The trend of the other technologies is moving to the cloud. Other competitors of UiPath, like Automation Anywhere and Blue Prism, have already moved their applications onto the cloud. This brings more robustness to the product, because its performance is significantly increased. It is also very scalable when putting in new features. 

I have attended a lot of UiPath's webinars.

We are in the initial stages of using the AI functionality.

The RPA technology is part of our digital transformation. For example, we are doing digital transformation by automating the Salesforce application.

They roll out an update every three months. With every update, we see a lot of new features. We are always exploring using those features so we can automate the stuff.

Don't rely completely on the UiPath tool to achieve automation. You should have some background and knowledge to understand what can be automated. There isn't a magical algorithm for building robots. You educate the robot on what can be automated.

We always rate a product based on other products. I would rate this product as nine and a half out of 10.

Most of the time, we work with financial services to automate financial transaction monitoring systems. We go through multiple CRM and financial systems, then query the transactions based on the KYC information. We use OCR operations, using UiPath Robot, to fetch information, such as, identification number, passport number, and their tax information. We extract this information, then validate with our financial data or transactions data to ensure that there is no fraud nor anomalies in the system. If there are any suspicious transactions or potential fraud, we do manual investigations. Those manual investigations are redirected from the robot to a human agent, then the human agent verifies the information. If there are any cost validation requests from other systems, such as Salesforce and PeopleSoft, then another bot will be triggered using UiPath Orchestrator. After that, we do the remaining processing. At the end of the processing, we use the UiPath analytics service. That analytics service uses UiPath logs, which helps us to understand how the bot is performing and how many transactions we have validated. From that, we look at how many were successfully processed and how many were manually handled, i.e., exceptions. We identify business exceptions for any transactions during the initial pre-validation stage, such as the user identification number is not valid or input data validation errors. For example, passport information must be an alphanumeric eight digit. If the bot identifies that the value is not eight digits, but four or five digits, then it is an invalid record straightaway. We can see this from the reporting and performance graphs.

We do automation for our HR processes, such as onboarding processes. On any day, there are five or six people who need to be onboarded. This is one of our standard business cases. We have a UiPath robot design using UiPath Studio and then it deploys in Orchestrator. This robot is being used by the HR admin. They can fill in the key information of the user, e.g., name, level, and their package. So, they import all this information, which includes my identity information, mobile number, email, and IDs on an Excel file, possibly along with a few other associates joining tomorrow. Once those entries are made in the Excel file, then the user can trigger a robot. They also need to keep the file in a designated folder. The robot will read the file from the designated folder. Then, one by one, it will read the records or line items from Excel and open an SAP portal. After logging through the SAP Portal, it inputs the required employee information. After that, it will go to Microsoft Azure Active Directory to QA the user, email, and ID. It will then go to PeopleSoft to create an HR record for the salary information, leave information, and the level at which the associate is joining. At the end of this process, it will update the status to, "The associate has been registered successfully." It will then send the updated final report to HR, saying, "The processing has been completed." The bot triggers information with their newly created email ID. They can then access or receive the onboarding information. This is how it works.

Depending on the client's requirements, we use UiPath AI Center and UiPath Apps for custom requirements. Most of the time, we don't need them. There are some times that we do based on the client's requirements.

I am using UiPath Studio, UiPath Orchestrator, and UiPath Robot.

Initially, I used the on-premises deployment model. For the last two years, we have also been using the cloud deployment option, UiPath Cloud, along with the on-premises. This is based on a client's requirements.

We can use the Process Mining tool to identify opportunities. We can then design the robot using UiPath Studio. After designing it, we can deploy it, using UiPath Studio, to Orchestrator. From Orchestrator, we can manage, monitor, and upgrade all the new patches within the UiPath platform.

If we have one place where we can see the end-to-end journey of our automations, then I do not need to manage multiple licenses. I do not need to spend money and expertise hiring multiple people and training them on multiple platforms. Also, when upgrading the systems, if I have a one place where I can manage all my automations at the same time, including UI and background automations, then we can build low-code apps using UiPath Apps. Therefore, I can manage everything within one platform, which is either a UiPath Intelligent Automation platform or UiPath Cloud. This is very important. Because if I have multiple systems, then I need multiple stakeholders to manage, upgrade, and maintain them. So, we do not need to think about all the things that I am using. There is one place where I can manage everything.

It has enabled us to automate more processes overall. In the initial days, we easily automated the low hanging fruit. As our automation journey matured, we needed to automate processes using more complex methods, like AI, machine learning, and advanced OCR functionalities. 

The UiPath package available on UiPath Studio is useful. Compared to other RPA tools, like Automation Anywhere and Blue Prism, we found that this package gives us the opportunity to automate tasks in the shortest amount of time. There are multiple templates available on UiPath Studio. For example, if I need to do multi-setting processing, which means we are going to process multiple records simultaneously, we can use a UiPath Background Process as a template. Using the template, I can run multiple robots on the same system, which will not interact with other systems. It will work in the background. We have found that really valuable. This is not available with other RPA products, such as Automation Anywhere and Blue Prism. This is one of the valuable things that we have found in UiPath.

We use the UiPath recorder. For the latest, modern experience, we have a recorder called App Integrations. Using that particular recorder, I can automate tasks with multiple systems without thinking about having manual integrations between multiple browsers by identifying multiple sessions. Sessions can be used by the same recorder during the entire automation cycle. For example, I have two screens, one called PeopleSoft and another one is SAP. I can do a keystroke, mouse click, and then hit the submit button within PeopleSoft. Then, at the same time, I have another window open being used by the robot. I don't want to think about separating two windows, so the recorder takes care of this.

The UiPath recorder has multiple ways of identifying. For example, it uses UI elements, fuzzy logic, and image recognition at the same time. These three methods are used by only one recorder. Whereas, with other platforms, like Blue Prism and Automation Anywhere, I can use only one method at a time, so one command is one method for selecting or identifying objects. Whereas, with the app recorders, I can use three methods using one command. So, if one fails, another one will back up the scenario. Then, if another one also fails, the third one will help us automate. That is the ease of automation, which is a valuable feature that helps us ensure that automation works flawlessly, without having to look at if one of the methods failed.

One of the 2018 projects was built using version 18.2. We then got a report from users that it was not working. Most of the time, it failed on multiple use cases. When we took the process from the owner to repair and troubleshoot, we found that many packages were not being recognized by the new version, which is 2020. So, we had to upgrade to the latest package, then do a repair. It took a good amount of time for us to repair the package. We had to go back to the UAT environment, then do testing and get approval from the UAT. We then had to sign-off and deploy pre-production and post-production Hypercare. So, the automation cycle being repeated by almost 40% is quite costly to the business, but this is rare.

The vendor had already noticed these things were a big pain for us. With the recent versions, 2019 and onwards, the compatibility between the activity and packages is there. Prior to that, there were some issues. The UI automation package was the one that was mostly affected. Many people who were early adopters of UiPath observed or experienced these kinds of issues.

Sometimes, when we are using Remote Desktop automations, we may need to use a different approach along with the AI functionalities. For example, if I need to recognize the object on the screen, which I cannot do using native methods, then along with the AI functionality, I may need to have a backup method, such as the OCL methods along with AI Computer Visions. This ensures that it works robustly and my solutions deliver 100% results without any manual intervention. In such complex scenarios, we are using AI features along with multiple methods for the backing up of the AI features. We have to ensure that if something goes wrong with the AI features then we have another method which will ensure, if A fails, then B will back up our solution's process as expected.

I have been using it for the past six years.

We use UiPath AI Center, UiPath AI Computer Vision functionalities, and Document Understanding. These AI features came into the picture from 2019 onwards. First, we received updates using UiPath Computer Vision functionalities. Then, we received AI Center, which was not stable in its initial days. However, during the first quarter of 2020, we received version 2, which seems to be more stable. From there, we received general availability versions with integrations on UiPath Studio and UiPath StudioX. These work much better, as compared to the initial versions. So far, all the components of UiPath Computer Vision, Document Understanding, and UiPath AI Center work well. 

I appreciate other benefits, such as UiPath community support and UiPath enterprise product support, because if anything goes wrong, we search in Google or the UiPath Forum where we can find the answer. Even if the answer is not available, and I post a question, I am quite certain that within one day that I will get someone to respond to the question. It may be someone from the forum or UiPath. Most of the time, the answers are readily available on the UiPath Forums.

UiPath Forum is the one place where we reach out to research problems, do troubleshooting, or get some help. If we need some help regarding the installations or licensing, we can create a ticket. Typically, we get a response, email notifications, or support calls within four to six hours.

We hire fresh, new graduates that we are going to train. UiPath Academies offers numerous training tutorials and certifications, which helps us to train our newly hired resources who are completely new to RPA and UiPath. So, the training is really useful in terms of video tutorial practice and configuring our multilingual environment. UiPath Academy does support English, Chinese, Malay, and German. So, our associates from multiple offices, who are already working on the global initiative, can learn the same things at the same time. Or, they can get someone from an English background.

I started RPA using UiPath.

Using the tool for the last six years, the initial setup is like having breakfast every day; it is very simple. I can do it much faster than someone new who started two years back or the new guy. I know what to do and how to do it.

Because it is software as a service, the setup and configuration time are very quick. Within an hour or two, we can set up the infrastructure deployment for a starter package. Configurations can be done smoothly. The infrastructure deployment, which typically takes a week's time, can be minimized to an hour. This saves us a lot of time and money for multiple components.

In the initial days of 2016 or 2015, our automation journey was center of excellence (COE) based most of the time. Nowadays, we changed our strategy, and it is more employee involved. So, an employee can go into UiPath Automation Hub and submit their idea. If they have time and are interested, we give them the training to use UiPath StudioX features for automation. If a process is complex based on our assessment, we pick that process and do the automation so the COE and employ-driven automation work hand in hand. 

With a simple process, then the employee can automate it and do the PoC. If they need help, we are more than happy to help them. However, we found when the processes are medium to highly complex, this is something professional developers should be working on. If they are interested, they can contribute and learn, but it's less likely that a business user would be involved in a complex automation process.

UiPath has absolutely reduced human error. Infrastructure setup and maintenance are taken care of by the product owner or vendor. So, there is 100% assurance that nothing wrong will happen in the system because they are the people who built and deployed the product. Whenever we deploy, there may be a chance that something might go wrong or configurations went wrong. For example, I need to configure the Internet information services port. If I incorrectly configured the port or use a different method, there is a high chance that I might need to redirect the port to some other router or native firewall. If I use UiPath Cloud, everything is taken care of by UiPath. I just log into assistance, then allocate the license and configure our users.

For small to medium clients, those clients have an investment of about $100,000. We see around six to eight months in, they get something around 40% to 60% ROI being returned to them. Then, within a year to 18 months, they get a 100% to 120% ROI realized.

When we implement a robotics process automation solution using UiPath, and if the client's budget is limited, we mostly encourage the automation journey to be done using UiPath Cloud. UiPath ensures that it works fluidly, performs all upgrade security patches, and has 99.9% uptime.

In the initial days, UiPath was more competitive in terms of the license pricing as compared to Blue Prism and Automation Anywhere; it was much less. Currently, the pricing is quite standard compared to the other two vendors. 

We can use UiPath Cloud, which helps us to save a lot of money and infrastructure costs, if the automation journey or project is for a small to medium-sized company. However, if it is a big company, then on-premises is preferred. 

I have also used Automation Anywhere and Blue Prism as well as open-source automation platforms, such as TagUI and Selenium.

The main pros to using UiPath are its user interface, user-friendliness, learning platform, and support.

We have been using the UiPath Apps feature for the last four or five months, so it is relatively new for us. Most of our technical people are experimenting with UiPath Apps. We have planned training sessions for business users to upskill them.

If you are starting or in your initial days, I advise you to use the UiPath community version. Try first to do a PoC with the community version, trying out the automation in UiPath Cloud for free. Once you realize that this is something good as well as understand the value of it, then you can start with the initial package. If you think that you can start big from the beginning, then go for on-premises and start a large-scale transformation. However, I would advise doing a PoC first with proper guidance from UiPath and selecting a proper implementation consulting partner who has good experience or a solid past track record of doing automation, RPA, the RPA automation journey, and the transformation journey, as a whole. Not just UiPath automations or building robots, but also transforming their project and processes as well as doing Lean Six Sigma, which is a crucial part of the transformation journey. So, you should consider all these factors for a successful automation journey.

Compared to the top three tools, I rate this solution 10 out of 10.

We have licenses for 15 robots and they are running internal processes. We develop them using UiPath Studio and we only use unattended automation.

Our primary use case, which is 70% of what we have automated, is related to our booking system. Instead of having 10 agents who handle the booking or creating the reservations, the work is done by the robots. Sometimes, bookings are very simple where you have just airfare or the hotel, but in our case, it's quite complex. We call it dynamic packaging, which will have a flight component, you can have a hotel component, different attractions, meal options, a rental car, and more. Instead of entering all of the options manually, which can take up to 10 minutes or 15 minutes just to create a single booking. It is similar when we perform other tasks, such as making a payment. These things are normally done in our target system. I have created robots and workflows in UiPath that are triggered by the database, and they complete these tasks automatically. We have 15 robots conducting the job.

The second use case replaces the agent when once we get all information from the outside system using a .NET application and store it in the database, it creates parameters for the robots to make a booking or reservation at Universal Studios for attractions.

The third use case covers all of Europe and it is a completely automated car booking system. 

Basically, our use cases are all about travel and booking systems for Universal Studios, general dynamic packaging, and car rentals.

UiPath has definitely improved the way our organization functions. It normally takes one agent approximately six hours to create reservations in the booking system manually, and now the job is left to RPA with UiPath workflows. It saves between 40% and 50% of the agent's time, leaving them time to work on something different.

The accuracy of tasks has been improved because everything is data-driven, and there is no problem that comes from human error. The system is almost bulletproof; if you send garbage in then you get garbage out but definitely, there are no human mistakes. For example, instead of entering the name of the customer, it comes straight from the database. The same is true for options like the times of picking up and dropping off your car. The only problem that we have is not related to RPA; it's the case where the target system is not responsive. For example, if you're moving from one screen to another and the system doesn't respond, then we are notified via an alert. 

The improved accuracy and shorter time to complete tasks, freeing up resources for other jobs, translate to money saved. Given that our processes are complex, the automation of them takes a load off of our end-users. In some cases, they have to perform data entry in several different systems. For example, in order to make a booking, they have to use three different systems with three different interfaces.

With RPA, in general, there is also a fear that jobs will be lost but when you're always swamped at work, including overtime, night shifts, and working on weekends, RPA is a big help. 

UiPath has helped to reduce our hardware footprint by between 20% and 30%. We now have only 15 virtual machines running instead of 15 physical desktops. The amount of hardware required to operate the business is directly correlated to the number of human operators and the software that is running.

UiPath has saved us significantly in terms of costs, primarily because of the manpower we used to have for the booking reservation system. It frees up resources for the agents, IT staff, and people from various departments. For example, we have group reservation systems for car booking, flight booking, and others. UiPath has made an impact in all of these places and the cost saving is very beneficial. In the first year, we saved over $100,000 on the booking systems. After the initial project in the first year, two or three more systems were built, for a savings of $300,000 annually before COVID.

In terms of the time we are saving, it is quite low these days because of the COVID-19 travel restrictions. Pre-COVID, we were saving approximately 80 hours per day. The reclaimed time for our employees is now available for them to work on higher-value work. The savings is not only from the data entry but for troubleshooting errors, which no longer needs to be done.

We have offices in Montreal, Vancouver, and Toronto, and the majority of agents are stationed in Montreal. I am working in the Toronto location, so I cannot comment on the majority in terms of how employee satisfaction has improved. What I have heard from the executive management is that more people are happy because they are able to better focus on what they want to do. This is especially true because they do not have to spend many hours troubleshooting trivial issues. Instead, they are concentrating on higher-value work.

We are using approximately 70% of all of the activities that are available in UiPath. These include web scraping and data entry, where the information is stored in a database. We also perform database queries.

The biggest benefit that we have from UiPath comes from using the API.

The features that we use most often are database communication, scraping, and PDF functions. The only features that we don't use are those related to Excel, for spreadsheets.

For smaller projects, we are only passing parameters from .NET applications but in the newer projects, we are using features such as database communication and data scraping.

The ease of building automations is great. When I talk about UiPath, I am usually referring to Studio, which has a very intuitive and easy-to-use interface, yet it is very powerful. This is something that has improved with the help of forums and tutorials. In 2016, it was more difficult because there were really no forums so we had to contact the head office in Bucharest, Romania when we needed help. Getting a demo had to be done in the very early hours and there was lots of communication back and forth. It was a struggle to find solutions, although to be fair, they've been very helpful. These days, it is very easy to use because there are numerous examples, and UiPath Academy is available, along with other resources.

We have been using the UiPath Apps feature and it has helped with the ease and time required for creating automation. Everything has improved over the past several years, as in the past, there were no examples or tutorials available. There was no manual and it was very technical. At the time, you definitely needed programming knowledge in order to handle some of the scenarios. It was at times like this that we relied on support from Bucharest.

Even today, there are only a couple of programmers in the company who develop the bots. Even with the Apps feature, I don't think that the end-users are ready, although this may be because of the way that our organization is structured. Everything is given to the IT department because our scenarios are very complex, and not a simple case of data entry or something like that. With such complex solutions, it is definitely too difficult for our end-users.

There are a few areas that need to be improved, one of which we have already raised with the salesperson and technical team.

The first area that needs improvement is backward compatibility. If you have a newer version of the UiPath Studio or any product, then quite often, if you're a year behind or so, you cannot compile the whole project. This means that you have to rebuild system modules. It's not like a Microsoft product that is always backward compatible. For us, that is a huge obstacle because sometimes, we have to rewrite entire workflows. In our case, this is a massive undertaking that will take three or four months to complete. This is the main issue for us and it doesn't happen with minor release updates, but with major ones, we have to rewrite the entire project because it doesn't compile.

The licensing should be more flexible and more affordable.

We used to be able to integrate with .NET applications, where all of the business rules reside, and then invoke robots or workflows from there. Now, that capability has been removed, so we have to use Orchestrator. Converting our projects requires a lot of work because we have to move all of the business logic to the UiPath workflow. It is not an ideal situation for us because keeping the business logic inside our .NET applications is more flexible and more scalable.

When I was taking some UiPath Academy courses, I noticed that they gave us more complex tasks. There were expert-level examples, but the junior examples are missing. Furthermore, they give you high-end, very technical guides, but there are not really any examples. This means that you really have to dig and use the forums and ask people questions. Essentially, you have to try and find the solutions by yourself.

In general, if you have very large and complex solutions as we do, the overall workflow layout could be improved because navigating through the network components can be very inconvenient. You can still see the high-level of the workflow, but not a detailed one. It may take you several minutes to get to the component you were looking for. In terms of navigation, the mapping solution could definitely be improved. There are always workarounds. What you can do in this case is use the flow charts with the sequencing module to break it down to a more general view. This makes it faster to get to the module that you want to improve or fix.

I am a Senior Lead Developer in my company, and I have been using UiPath since 2016. I was one of the very early UiPath users.

Stability-wise, we haven't really found any issues lately.

In the earlier versions, from 2016 and 2017, there were some issues that were never resolved by the UiPath team. The newer versions, especially while performing web scraping, are much more stable. Once it was deployed, we haven't seen any issues with the .NET applications.

Instability in our use case is the result of the target system; for example, the one that is operated by Universal Studios. If they are unresponsive for perhaps 20 or 30 seconds and the robot is expecting to see a certain screen, especially when it normally only takes two or three seconds to move from one screen to the other after submitting a request, it is going to cause a problem. However, that's not the fault of UiPath or RPA in general, but a fault of the source or target system.

I estimate that with all things considered, UiPath is 99.9% stable.

UiPath is very scalable. We are a mid-sized company with approximately 200 to 250 employees.

There are three or four of us who have hands-on experience with the product, and there are between 100 and 110 end-users. This includes four or five departments spread across three different locations. Our end-users are primarily business users.

Our goal is to increase our usage of UiPath but we are currently downsizing due to the COVID situation. We have some projects in mind, but we have to wait to see what happens with the travel industry. With approximately 50% of our employees laid off, no progress will be made. However, down the road when we get back on track, we plan to use other areas of the system. That will include manipulating spreadsheets, data entry, interoperability with other systems, and interfacing with it.

The technical support is definitely good, although there were some issues that never got resolved. The situation is that we are based in Canada and our salesperson from Toronto organizes the meeting with the technical staff from New York in the US. There were times when they couldn't help us because the majority of them had been with UiPath for two to three years. They didn't understand how things were working back in 2016, '17, or '18, well enough. Ultimately, they never found a person who could help us and to me, that is not really acceptable in terms of finding a workaround or the fastest approach to resolve the backward compatibility and .NET Integration.

What we needed was somebody with five or six years of experience and they could simply not find one.

We had some basic automation running prior to UiPath, but it was native SQL and .NET applications. An example is that we were using scaping options available in Microsoft applications, but it wasn't really RPA. UiPath has definitely helped us to reduce the costs of our automation operations. Everything is now run from one application, and you can use the workflows to collaborate between databases, spreadsheets, and booking reservations. Basically, it's end-to-end in terms of the development lifecycle because originally, our tasks were only partly automated.

If you consider automated testing solutions then we were using Selenium for things such as load-testing, in a previous company. I had no experience with a full RPA solution before UiPath in 2016.

In our early stages of automation, the task would start and then only get to a certain point before a different application had to pick it up. We had a scheduler that was responsible for this. The scheduler would see the partly completed task, then take it and put it somewhere else for a third application to take over. Now, all of this is done using the UiPath API.

Specifically, in terms of overhead operations, UiPath has saved us approximately 80 hours a day, which translates to between $4,000 and $5,000 per day, just in one department. If you multiply this by 30 days then it is a lot of money. Given that it is a ballpark figure for just a single department, it could be even more.

Back when we first installed UiPath, it was complex. But now, it is much easier because they have grown. It is much easier than it was five years ago, although, at the same time, we haven't had many issues in the process of implementing and rolling out our solutions.

Our deployment is on-premises and entirely private.

These days, it takes less than a day to deploy. In 2016, it took us almost a week for much simpler deployments because there was no proper documentation. Fortunately, at the time, we got lots of help from the technical staff in Romania.

When we first started with UiPath, it was not even close to what it's today. It was much difficult to create a strategy because it more or less was a black box. We purchased the product and there was only UiPath Studio, nothing else. There was virtually no documentation and more or less, everything was left to us, our team, to develop this strategy.

Implementing it was more of a trial and error process than it is today. Finally, we did it. We moved our automations from the development environment to the staging environment, and then finally into the production environment. Now, it's pretty stable. At the time, however, it was pretty cumbersome and difficult because there was no proper documentation or guidance from UiPath. Nowadays, it's pretty simple.

There are three of us in the company who are responsible for deployment and maintenance. We also handle the monitoring, implementation, troubleshooting, and updating of the product and robots.

We also have an infrastructure team that is outsourced from a company in Toronto, Canada, called Carbon60. Our experience with them has been a little shaky, but we are handling it okay. They could not really help us as much with the initial setup of UiPath because they did not have experience with RPA. We gave them the specs required for our infrastructure, and they set it up. Overall, approximately 90% of the setup was our responsibility.

Compared to four or five years ago, the licensing in terms of price is less flexible and less affordable. Recently, because of the COVID situation, we need 15 robots. Ideally, we could use five robots and Orchestrator instead, and pay the difference, but the vendor refused to take this offer.

We are currently using the Community Version of Orchestrator for training purposes.

When we started looking at UiPath, they had less than 100 customers in the world. We had been looking at three different options that included UiPath, Blue Prism, and one other one. In our case, we were using a legacy application that was Java applet-based, and the other products were not able to handle that well.

From what I recall, back in 2016, UiPath was the only option that supported Java applet-based automation. We needed the functionality because one of our internal applications was not web-based, but Java applet-based, and depended on it. It did not work immediately and there were some workarounds, but with some help from the UiPath technical staff, we were able to handle it. This is the main reason that we ultimately chose UiPath.

Essentially, UiPath was the only option that was able to handle Java applet automation. With that covering the front end, we automated the whole process.

In the future, because UiPath was not able to handle the legacy projects that we developed in RPA, we might consider another product like Blue Prism. We would assess potential solutions based on backward compatibility.

We have been thinking about using the Orchestrator with the cloud option, but because of the current world situation, especially because we are in the travel industry, our income has been significantly reduced. At this point, we are more or less in survival mode, so we decided to stay as-is.

We were also supposed to get Orchestrator, the latest web developer, and a production license but we gave up because we cannot afford it at the moment. Travel may be idle right now but post-COVID, which hopefully is next year or by end of this year, we're going to get the official Orchestrator license.

Originally, we were using .NET applications, which is the technology that has driven the business. It's huge, and with the newer versions of UiPath, it is no longer possible because we have to use Orchestrator. At this time, we are more or less working on a workaround and it's a massive project that is probably going to take six or seven months to complete.

We are not using the AI functionality yet, although it is something that we're planning to look into, eventually.

The biggest lesson that I have learned from using UiPath is how much time was consumed by our manual processes. Definitely, we have freed up resources for our business team. In terms of accuracy, there are no human errors anymore. Consequently, we can free up between 30% and 40% of our agents' time in terms of analysis and billing. In summary, the biggest thing that I have learned is that using RPA is about improving accuracy and reliability.

My advice for anybody who is implementing UiPath is to start with the training. These days, especially younger developers, people are very keen to jump on developing RPA and they're doing this stuff without using Academy or other training. Rather than do that, I suggest people get familiar with the product and use the training material first. Use the examples that are provided because the UiPath Academy is amazing in terms of that.

In summary, this product has a very intuitive and powerful interface. There are very good examples and scenarios on the UiPath Academy website, and technical support is very helpful. You can also find lots of good examples in the community forums. There used to be only one OCR option, and now there are two different flavors of OCR, which is definitely one of the pros. However, the major cons are backward compatibility and licensing in terms of flexibility and affordability. We also lost some of the functionality for .NET integration, which was a problem for us because the capabilities are simply gone.

I would rate this solution an eight out of ten.

I have worked on multiple use cases with UiPath dealing with SAP, SharePoint, or a web application. We had to extract the data and do some automation of data processing. We were taking data from one environment, such as from an Excel sheet, and processing it. These were the use cases for which we used UiPath extensively.

In addition to app integration, there were use cases related to various frameworks such as REframework and State Machines. We used the REframework at the enterprise level to be able to handle exceptions and bot failures and make automation healthy, robust, and steady.

We have also done automation for a healthcare department for claim processing.

UiPath saves the execution time of processes running in the production. If a process was taking three to four hours previously, with UiPath automation, it can be completed within an hour with better exception handling capability and less dependency. It saves 50% time.

UiPath is capable of handling the complexities involved in taking data from different environments. It is also capable of exception handling. If any application has limited functionality, we can use UiPath for automation with that particular application. With advanced selectors and linked queries, we can get the data from the application or interact with the application.

UiPath Document Understanding has helped to reduce the data entry work and physical copies of documents.

UiPath enables us to implement end-to-end automation. For every organization, it is very important that automation is robust enough.

UiPath can help minimize your on-premises footprint. It depends on whether you plan to deploy your automation on the cloud or on-prem. On-prem has various challenges and restrictions, but it also has benefits.

UiPath speeds up digital transformation without requiring expensive or complex application upgrades, or IT application support. App integrations are advanced and robust. It is plug-and-play. You can integrate with Excel, Outlook, SharePoint, SAP, and various databases. There are pre-loaded activities. You can integrate with GitLab or GitHub. It has inbuilt activities for enterprise-level applications.

UiPath reduces human errors, but it also depends upon the process. It depends on how much interaction is required and what exception rates are there. When everything has been identified, it can reduce errors by more than 70%.

The first feature that I like is the exception-handling capability. The second feature is the REframework provided by them, and the third feature would be the Orchestrator functions. There is also the feasibility provided to monitor the ports and deploy the code. There is monitoring, retrieving, and all those things. We can use the web or mobile application. These are the key features of UiPath.

For handling complex scenarios, REframework is good. It has good exception handling and in-built mechanisms.

The certification can be made more affordable.

In terms of features, we get regular updates, and AI has recently been integrated. As of now, I do not have an area of improvement. They have already improved the functionality of Orchestrator. As compared to two or three years ago, Orchestrator now offers different functionalities and services. There is a difference, and it has improved.

I have been using UiPath for more than three years.

It is stable. Our organization has licenses because we cannot upgrade the application in sync with the Community version. The enterprise has to stick to one version for a certain period or whatever tenure has been mentioned in the license. The Community version is the playground for UiPath. They upgrade it, and all the beta version updates are there. They come to know how things are going and what are the responses and challenges.

It is scalable. It is used in multiple departments. The size of the organizations that use UiPath varies. They could be MNCs or startups.

Their support is good. After procuring the licenses, when there is an issue, there is a dedicated support team. They respond well.

The UiPath Community is vast. It provides an opportunity to get help from others. They provide good support, and the MVPs are actively engaged in responding to the queries that people are posting when facing any challenge. We can find relevant information by searching with keywords. It is good.

UiPath Academy has been useful in learning about new topics and new versions.

Neutral

I am quite new to Automation Anywhere, but a better exception-handling mechanism and the ability to interact with various applications make UiPath more unique. The drag-and-drop interface is attractive to people who are not very technical. The user experience is more intuitive.

We have on-premises and cloud deployments. The deployment part takes about a week because we have to prepare the production environment. A week is good enough for the deployment.

The number of people involved in the deployment varies. Support teams are there. Developers are also there. There are also people from the change management team.

Like any other software, it requires maintenance.

I would recommend UiPath to others. Overall, I would rate UiPath a nine out of ten. It is robust and scalable, but there is always scope for improvement.

We use it to automate repetitive processes. We are also using it to manage people and costs.

I have used it for automation in telecommunication, HR, and finance. I have also done two projects for IT. It is a combination. I have worked on all these different projects.

UiPath helps with cost savings and staff savings. We can use manpower for high-value tasks rather than for repetitive tasks.

UiPath helps with end-to-end automation. I have created end-to-end automation through UiPath. It is a high priority for our company. I have not yet worked on the AI functionality.

UiPath reduces human error. If it is a repetitive task, then bots cannot go wrong. They have already been coded with whatever is required, so human errors are generally not there, but there can be scenarios that have not been covered, and they can result in exceptions. We have to work on them and update the bots so that we do not get the same issues.

UiPath improves accuracy. The teams for whom we have done automation are happy. There are no errors. It improves their efficiency. Bots can work 24/7 or at whatever time they want. There is no dependency on time, which is not the case with humans.

The time savings vary from project to project. On average, if a human takes three hours for a task, a bot would take about ten minutes. UiPath reduces the costs, but I do not have the metrics.

UiPath is very user-friendly. There is ease of use. People can understand it very quickly.

It is very easy to use.  It is very good. There are many people who are uploading learning sessions on YouTube, which are free. It is good to learn from there as well. There are many sources to learn and explore it. There is also a community of UiPath users.

UiPath Academy has complete courses for developers and business analysts. A business analyst can follow the course path created for business analysts, and a developer can follow the course path created for developers.

I have been working with UiPath for the last four years.

It is a stable solution. However, if your applications are changing, you will have to do some manipulations in the code. Now they have a feature where you can keep your UI things in your config or in the assets, which is helpful. It is easy.

I do not interact with them directly. There is a team that communicates with their support. 

I know Automation Anywhere, and I have also done a certification on it about four years ago, but I did not work on it. I am not familiar with the features currently in Automation Anywhere, so I cannot compare it with UiPath. I have more experience with UiPath because we got more UiPath projects. We were going to work on a project with Automation Anywhere, but that did not happen.

I have also worked on UiPath Document Understanding, but most of my experience is with general automation.

I have set it up from scratch in one of the companies. It was not that hard. It was easy to set everything up. I was doing it for the first time, so it was a little bit confusing, but it was good. There were forums and YouTube videos. The UiPath team is also available if you need help with installation and what to use. It was good.

After the code is ready, the bot deployment takes 10 to 15 minutes. Three years ago, it used to take us an hour.

I have not worked extensively with any other tool. My experience with UiPath is good, and I would rate it an eight out of ten. I am satisfied with UiPath.

The process is for background checks. There are all kinds of checks such as academic, criminal, and work as well. We receive all the volume through the queues. We are using the citizen developer, StudioX, to get the cases and understand what are the fields and what are the requirements for each one of the cases. The bot will process them accordingly. For example, for each university or academic, there is a different process around the world.

The industry we use it for is HR. What we do with the backgrounds is providing a confirmation to our clients that people have the qualifications that they say they have. It is for data accuracy and consistency within the HR and talent acquisition departments.

Our AI-powered automation initiative has not yet changed what our organization is able to achieve because the project is still a pilot. We are still working a little bit on the environment. We are working through VDI, so it is not straightforward. We cannot just install or put UiPath to work. So far, we have not seen all the results, but we are looking forward to that in the next quarter.

UiPath would definitely free up time or resources for other tasks. We are a team of six people. We are estimating that two of them will be free for new projects. There is about 30% of resource savings.

Our usage is very simple. We have been getting the text, parsing it, and trying to categorize and analyze it. We are not using it fully, but the OCR is very important. This is a package from StudioX. With OCR, we will implement document reviews to make sure that whatever the applicant puts in the form is consistent with the document provided. For example, in academics, it will be your bachelor's or master's certificate.

The value proposition of implementing UiPath is that if we use UiPath and the RPA functionality, instead of passing the process to a BPO, we will start understanding the process and automating it as much as possible. We will have hybrid workflows between humans and robots. We will create capacity. We will have the same number of workers but increased capacity. We will start having conversations with our stakeholders on how to reinvest all of this capacity that has been liberated.

We have had some issues with StudioX. In terms of features, for now, I am pretty happy with UiPath. The requirements of the process to be automated are covered with the basic functionality. It is not exactly UiPath, but for security reasons, we are not able to download packages and use the functionality provided by the community with their developments. It is not on the side of UiPath. 

I was certified as a Citizen three years ago. That is the time frame that I have been using it.

Recently, there was a software update of StudioX. We had some bugs. I would rate it a five out of ten in terms of stability.

We are working on moving to the cloud, so scalability will be good.

We have internal support. I do not speak with the vendor. Our internal support system is pretty consistent. They have quick response times.

From my perspective, I do not think we have been using any other solution. We have been with UiPath for about eight years. I cannot confirm the number, but I know that we have been partners for a long time.

We also use AutoHotkey which is something similar but not a replacement. It is a software solution that allows you to reprogram your keyboard and put some functionality in there to automate some of the things, but it is not a replacement.

I was not involved in its deployment. It is on-prem right now. We are migrating the company to the GCP, so there may be some restraints in regard to that. Everything is currently on-prem, but we are working on going to the cloud.

The ROI would be in regard to the capacity. We estimate two FTEs to be free from this project.

We have not yet used UiPath's AI Center and many other features. We are using StudioX, so we are still in the citizen developer mode. We are not using the full functionality with Studio and all that. We have an RPA COE. They have much more complex processes and projects, but we have not used it for that. This UiPath convention has brought a lot of ideas in terms of how to start leveraging it more.

We have also not used UiPath Process Mining and Task Mining. I am working with one of my colleagues who is like a bridge between operations and IT.  We are working together to see how we can better use the technology to improve processes. I have to go team by team, understand the process, and go deeper to see where we can start using this technology. We will have a roadmap of where we need to go.

Overall, I would rate UiPath an eight out of ten.

We use UiPath for marketing, accounting, and sales.

The solution has helped us save time. 

I like the automation capabilities. I particularly like Autopilot and documentation.

We don't currently use AI Center or process mining, but we want to learn more about these features.

The support team could be more responsive and helpful.

I have been using UiPath for one year. 

I would give the stability of UiPath a six out of ten. I've experienced some issues with it in the past.

I would rate the scalability a six out of ten.

I have had to contact the support team on a few occasions. It was a good experience. But the solution could be better with its support team.

Positive

We switched to UiPath because it's a better fit for enterprise companies like ours.

It might not be a good fit for smaller companies. It's a bit expensive for small companies, but it's worth the money for larger companies.

Overall, I would rate the solution an eight out of ten. 

UiPath is an RPA solution that is very easy to use and local. It's a good choice for companies that are new to RPA or have limited resources for training.

We primarily use UiPath for RCM and it can handle most tasks effectively, especially when dealing with data extraction from PDF files. There might be more complex scenarios where AI could be more suitable, although the implementation might be challenging. We are in the process of evaluating these AI-powered use cases.

We have found UiPath to be quite valuable as we actively deploy and use bots, which have become a significant asset to our operations. 

We were able to achieve the savings. It has freed up around ten thousand hours of time and resources for other tasks.

Improving financial and recording operations through the use of charts would be advantageous.

I have been using UiPath for approximately two years.

The stability is excellent.

Scalability is impressive, and it only requires the appropriate licensing.

The support is quite commendable, and they are very prompt in addressing issues. I would rate it eight out of ten.

Positive

The initial setup is straightforward.

ROI is significant when the use case results in substantial cost savings, but it's important to note that not all use cases deliver such hard savings.

The cost is on the higher side.

My recommendation is to thoroughly assess use cases and choose the right tools to prevent possible setbacks. Overall, I would rate it nine out of ten.

We use the solution to pull documents from audit systems, download documents from document management systems, and grab data from financial management systems. 

I like UiPath's framework. It offers a modern design experience, which makes it easy to do different activities. 

The solution is expensive. 

I have been using the product for four years. 

The product is stable. 

UiPath is scalable. 

UiPath's support is great. 

Positive

UiPath's deployment within our environment is complex. However, we have online resources available. 

We have seen ROI with the tool's use. 

The tool's pricing depends on its use. It is expensive. 

Our business objective was to improve manual processes and increase efficiency. 

Task Capture helps to build documentation. 

UiPath has freed up our resources' time. 

I rate it a ten out of ten.