UiPath Platform Reviews

We have worked on multiple use cases, but most recently, we have worked on a payroll system. Previously, every month, we had to manually get certain details from HR, and we used to do the pay run for all employees in the organization. Now, we automatically extract the required information from the current system by using UiPath. We then prepare a sheet by using Excel, and the entire Excel sheet is processed by a bot. The final sheet is sent for the payslips for the entire organization, and the entire pay report is sent to the bank for payment details.

Automation reduces dependencies. When I have a process that is done by humans, there are dependencies. For example, I need to make sure that the required number of people are available in different shifts. Any process that is done by a human has to be split into eight to nine hours of work. After every eight hours, I have a replacement happening for the same work. So, multiple people are working in different shifts. In addition, any work through humans can only be done from Monday to Friday, or I have to get the team over the weekend. Making our team work over the weekend requires special permissions or approvals. With automation, I am at ease. I'm not dependent on anybody. UiPath is easily accessible from mobiles for the orchestration part. So, if I have a critical process that I need to execute and get the results, I can do it from my mobile. Even when I'm traveling, I can get real-time statistics. 

Previously, I used to get a request at any time to do the pay run for an employee. If the employee was on a leave on that particular day or was not available, I used to miss my target or deadline. Now, we are not dependent on anybody. We are completely independent. If I get a request, the robot is automatically going to process it automatically. I don't even have to tell the robot to run a process after getting a request. All my rules and validations are taken care of by automation before the deadline. If I'm away from the office, my robot can automatically trigger a process on receiving a request. So, we are able to meet all the deadlines, targets, and standards set by the company within the given timeframe.

It has helped in minimizing our on-premises footprint. We work for multiple zones and across the globe. If I have a UiPath architecture, I can deploy it anywhere. Irrespective of the country or continent or zone, I'm able to use the same deployment or the same architecture at multiple locations. It has reduced my cost of infrastructure and maintenance. The cost of everything has come down. Previously, we used to have servers country-wise and continent-wise, but now, we don't need multiple servers and multiple teams to maintain them. I can do things from a single location with a limited set of resources.

The majority of our processes are in the unattended mode, but we do have certain processes in the attended mode where certain end-users provide me the real-time information. We have designed a process where we give a specific form to the user. When the form is filled by the user, a process is automatically triggered, and the robot starts processing. It gives real-time statuses and information to the end-user in terms of what we are doing, how are we doing the calculations, and how are they going to get the benefit by opting for certain features within our organization. I can run my processes in the attended and unattended mode. So, I'm able to trigger both modes of automation very easily.

I am able to keep my customer data integrated. With humans, a data leak can happen, but in the case of robotics, my data is very secure.

The way the processing happens is also very smooth. For example, if I'm on leave or on a break, and a customer calls at my help desk, I won't be able to respond. Now, we have chatbots or robots running throughout the day. When the executives are not there and anyone calls the customer support team, customers are able to get a resolution. They don't have to keep calling or wait. Automatically, the bot is able to respond to their queries and concerns. We have been able to reduce the response time. My customers are pretty much satisfied with it, and they don't have any complaints. Previously, the satisfaction level of the customers was not that great.

The best part of automation is that we can easily integrate multiple technologies within a single tool. I can do it at ease with all of my data flow. Automation is happening across the globe, not only in my organization. Every time we do automation, we feel that there is something overlapping in every process. If I automate a process for my organization and your organization, 50% of the things would be the same. I can very easily maintain common things in automation tools through common libraries or common components. For the remaining 50% of things, we use different technologies. We are integrating optical character recognition (OCR) technologies for document processing. We are also using multiple machine learning methodologies to do pattern matching. We are using artificial intelligence to give a response that is comparable to a human response. 

We use its AI functionality in our automation program. We get multiple requests, and they can be through telephone, emails, or documents. When a request comes through the telephone, the robot or automation is designed to convert that to text. When a request comes through a document, we are using AI features. The document might not have a proper structure, and a customer can give any set of data in any format. So, we have built a special template or format, and this AI is helping us to extract the document with the most accurate results possible. We are getting an accuracy of 95%. With this, dependency is also gone. A human has to properly go through a document. Then, we have to convert the data to the file and process it. With AI, irrespective of the size of the document, which can be 100 pages or 500 pages, we are able to exactly locate the data that we're looking for, and we are able to extract and then process it through automation. We are able to smoothly integrate multiple things within a single process.

Its AI functionality has enabled us to automate more processes. It takes a human 23 minutes to process a 500-page document. With AI features, it hardly takes 7 minutes to process the same document. There is a great reduction in the time taken to do the same task, which is a huge benefit. With AI, I can look for, find, and extract specific information in a particular document, and then I'm able to process the information at ease. I can have documents in different formats. For example, each insurance customer or service provider can have different formats. A human would have to scan through multiple pages to reach the conclusion that this is the right data. AI can easily process different formats, whereas a human being has to be trained for different formats. Humans might also understand something and forget something, but that's not the case with AI or automation tools. They always remember the instructions given to them, which has drastically helped us in making our processes more accurate.

It has contributed to end-to-end automation in our organization. End-to-end automation helps us in completing things in a shorter span of time and utilizing resources in a better way. Previously, for every step of a process, we used to have a different team. We had a separate team for the following:

• Requirement gathering
• Answering the queries for the customers
• Responding to the queries by the ticketing system
• Responding to emails
• Processing particular processes at the backend
• Supporting the infrastructure in real-time

Now, all these things are done by robotics. I only need a few people to maintain my infrastructure. 

We use the UiPath Apps feature, and it has definitely helped us. If there is something that is not available within our team, we can directly use all the apps and features given by UiPath. We don't have to dedicatedly set up a team to design that app. If I have to design a new app or a chatbot for my customers, I can easily integrate the UiPath Apps feature instead of recruiting people, training them, and expecting them to give me the output. UiPath provides help and documentation, and if I require any licenses or support, UiPath's team is always available to assist us.

The UiPath Apps feature has increased the number of automations that we can create. It reduces the time to create automations. We can easily create automation. For a small process, we're able to roll out one automated process every 21 days. We are able to roll out an automated and complex end-to-end process every three or five months to our customers. Previously, it used to take us at least six months to one year to roll out the new features or new functionality to customers, but now, the time has drastically come down. 

It speeds up or reduces the cost of digital transformation. Every time we automate, we are able to speed up automation. We are able to do more things, and more people are working on automation. By using new features that UiPath is bringing and the learnings from my past experience, we are able to automate very quickly. Four and a half years ago, a process used to take four months. Now, it only takes 25 days for me. They have added many features, and I don't have to sit and design those features. They are constantly providing new features in their quarterly releases, and I can simply make the best use of them and implement them in my process.

Previously, I needed people in different shifts, and every human being might not have the same speed or enthusiasm. Humans also need breaks. A robot works throughout the day, and it has a consistent processing speed, so we are able to process more and more. I can plan a target with my robot, and I am able to achieve that. If I'm adding new customers, I just have to integrate one or two more licenses, which is very easy. I can easily create or configure a new robot and start processing. With humans, I have to train them again and again, whereas with automation, once a process is ready, I can use it in multiple robots. I can use it for 25, 50, or 100 robots very easily. I can scale my process rate very fast.

Previously, we were able to process 5,000 customer requests in a month. By using automation, we are able to do the same amount of work within 10 days or even within a week. If we add more human resources, it increases the cost for my organization, whereas, with robotics, I can configure 10 robots or 100 robots. It doesn't increase the cost a lot for my organization, and I can process everything that I want. I don't have any backlog.

It has freed up the time of our employees. This additional time has enabled employees to focus on higher-value work. I am utilizing resources in a much better way, and I am able to give them the work that is interesting for them or is relevant to their growth. When people in my team started working, they found the job interesting. After working for more than two to three years on the same thing, they don't feel that they're doing something new or learning something new. By using automation for a lot of things, I am able to train my team on the new things or technology that they are interested in or want to work with. I am also able to give the work that they're looking for. It is bringing more satisfaction, not only from the customers' perspective but also from my team's perspective. I am able to keep the same resources in my organization for a longer period of time because they're very happy. They are not dissatisfied with the organization.

It has definitely reduced human error. Our accuracy is 99.2%. With humans, our accuracy was 96%, and by using robotics, we have brought the accuracy to 99.2%.

It has also reduced the costs of our automation operations. In the initial year, we saved 10% of the day-to-day operational cost that we had when we were doing things manually. In the second year, it was 30%, and it has increased in the subsequent years. So far, almost 60% turnaround in the business profit has been reported.

It has saved costs for our organization. Previously, for a process, I had to train, for example, 100 people and keep them in multiple shifts. I also had to give them multiple facilities to be a part of the organization, whereas with robotics, I only have to design the process once, and I can use it in any number of bots, such as 10, 25, or 50. It also helps in scaling at no extra cost.

By using automation, we need fewer people for support operations. If the customer queries are taken care of by chatbots, my data and patterns are being analyzed by using AI and ML, and the scanning of the documents is taken care of by OCR, I need very few people for support operations. I need only 10% of people for providing support around the clock.

We are using the entire automation process most commonly. We are also doing scheduling. Our processes are running on a fixed date, so we are also using schedulers or timers. 

We are also using AI technology. We have AI Fabric, and we are doing the entire extraction part of the document through UiPath, which is very helpful. We're able to do everything within this single tool, and we are not dependent on other tools. We don't have to license more tools from the market and go to multiple tools to do the same work. Within this single tool, we have every feature that we need for our organization. 

It is a very simple tool to work with for anybody. Simplicity is the best in UiPath. It also has the best community support. If we are looking for any solution, we can directly reach out to UiPath at any point in time. 

The new features or functionalities that come with UiPath upgrades don't work perfectly in the initial days. Their new releases are not stable. We always find some set of issues. I have to work with the UiPath team for a week or so to resolve the issues, and then I'm able to use it. The stabilization should be there. We expect UiPath to reduce the number of errors before rolling out new features to end-users or customers.

In addition, many times, the apps or activities that we use within UiPath for designing are no longer compatible when a new upgrade happens or the version is changed. We want UiPath to look into it.

I have been using UiPath for almost four and a half years. 

It is one of the very stable tools. We don't see any breakdowns happening within the tool. 

We only have to design the process once, and we can use it in any number of bots. It helps in scaling at no extra cost. After we design a process, we can reuse it in subsequent designs. I just have to work on the things that are not already designed. So, there is a 10% to 30% reduction in the new processes that we design. Scalability improves with each and every design.

There is a user base of 100,000 users who are benefiting from automation at the moment. With manual processing, if I had a team of 1,000 people, then with automation, I would need 50 people to automate all processes. I would have four to five solution consultants or solution architects and around 15 to 20 developers and testers. There would also be people who are doing the business implementation, giving guidance to the customers, and doing the production rollout and handover preparation for the customers. 

Our usage is increasing. With every new process that we design, we are able to integrate more and more. Previously, we only used to integrate with OCR, and now, we are also using chatbots, AI, and ML. So, our processes are increasing, and we are definitely expanding.

The support that we get from UiPath is one of the best. We are a direct channel partner for the product. Every time UiPath comes up with new features or functionalities, they come and demonstrate that feature and help us to understand them so that we can help our customers with their implementations. We get direct support and the licensing, pricing, and certification benefits from UiPath.

It was pretty straightforward for us. We were able to build the entire infrastructure within a week. This includes getting licenses, doing the installation, and configuring the robots. We found the UiPath documentation very helpful while doing the installation and configuration. 

If I design a process today, I can deploy a process to production within 30 minutes of time. It is very quick. In terms of the implementation strategy, we go to the customer and understand their pain points. We then identify the processes that can be automated and tell them about the benefits and the timeframe for implementing a particular process to their server. We also tell them when will they start seeing the result and how they can achieve what they need by using multiple integrations of the tool. They don't have to spend multiple licenses on different tools. Everything can be done within a single tool.

We use a tool called TFS. With a single click, I can deploy my process from development to QA. In the same way, I can move my process from QA to UAT, and then with one more click, I can move it from UAT to production.

As solution architects, our role is to help the design team understand the design that has to be built. They take care of the design and testing. For the production rollout, we have an infrastructure team. We also sit with the business team to make them understand the process, how robotics works on a day-to-day basis, and what are the things that they have to monitor. Whenever we design a process, we make sure that all the complexities are handled. We are also handling all the compliance, and the integration is done smoothly. After a process is designed and approved by our business team, our accuracy stands at 99%.

In terms of maintenance, it doesn't require expensive or complex application upgrades or IT application support. UiPath is pretty simple. The basic infrastructure works in most of the servers, and we don't need frequent upgrades and maintenance. It is very easy to maintain.

We have seen an ROI. In the initial year, we saved 10% of the day-to-day operational cost. In the second year, it was 30%, and it has increased in the subsequent years. So far, almost 60% increase in the business profit has been reported.

There is no additional cost apart from the standard licensing. There is a one-time cost for the infrastructure setup.

We did evaluate multiple RPA tools such as Automation Anywhere and Blue Prism. In terms of the ease of designing, the ease of use, and from the cost perspective, we found UiPath to be the best tool for our customers.

Anyone who wants to automate processes should understand the process, its complexity, and the volume of the processing or the number of transactions to be processed. You should do proper analysis before you select the tool and licenses.

UiPath provides a lot of benefits and reduces the cost for an organization. It is one of the best tools in the market. The support that we get from UiPath is one of the best, and most of the features provided by UiPath are simply amazing.

Initially, people are hesitant to use automation because they don't know what automation can do. Anybody who uses the technology in the right way will get lots of benefits from any technology. Your implementation strategy has to be proper. You should check the feasibility of using a particular technology with existing processes in the organization and the benefits you can get.

It helps us in reducing the time, and we are also able to bring more business to the company. By making my processes digital, I'm bringing more revenue to my company. We visit a customer's site and try to find out the processes and pain points. After that, we analyze the entire solution within UiPath and tell the customer about the best solution and what would be the reduction in time as compared to the normal process.

I would rate UiPath a nine 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.

Currently, we use UiPath in multiple types of use cases and build innovations for our clients to improve their system operations. We don't plan to implement AI in our automations in the near future. We're interested in that market, but it's a long journey, and it's a little advanced for us right now.

UiPath is helping our organization with its environmental, social, and governance automation space. Though it's currently at a beginner stage, it is progressing, and we expect to see improvements. UiPath has helped us free up staff for other projects. We have engaged our employees in working with UiPath through presentations. 

UiPath's integration features are highly valuable to us. We are able to achieve a lot with them.

For the moment, I don't see any explicit areas for improvement. However, having UiPath come up with unique features or advancements would be beneficial.

I have used UiPath for five years.

I don't see any drawbacks because our content is not down over time. We keep it updated consistently.

As our environment has grown, I haven’t encountered any specific issues or limitations.

I rate UiPath support nine out of 10. It's great, but sometimes we see delays. We ask a question, and they have to get back to us later with an answer. Otherwise, I don't see any drawbacks.

Positive

We previously tried out another automation app, but it didn't meet our expectations for handling exceptions and managing complex workflows.

Deploying UiPath was straightforward.

UiPath is the best tool, but the price is challenging from a management perspective. The cost-benefit equation might not work out favorably for some smaller organizations.

I rate UiPath 10 out of 10.

We use UiPath for claims processing, enrollment, and interpreting what's on documents, and then we use the data that's in them for different purposes. I'm sure there are many other use cases. We're still brainstorming and giving our leaders some ideas. Frontline employees also have process improvement ideas.

UiPath has improved efficiency, turnaround time, and accuracy while eliminating repetitive tasks. 

With generative AI, we can take on even more complex tasks. We've seen a return in claims and enrollment, which has freed up time and resources. There are lots of other possibilities. Our frontline people have seen how it can supplement and focus on more important tasks, and business leaders like seeing the resources freed for various reasons. The growth potential is immense, and we're only in the early stages. 

UiPath is a low-code solution that allows us to build automations fairly quickly and see the results promptly.

Overall, UiPath is relatively straightforward, but there are opportunities to simplify activities. Sometimes, I've hit roadblocks while developing RPA jobs and found it difficult to find the answer. I can usually resolve a problem through a support ticket or an online search. 

We have used UiPath for about a year and a half.

I rate UiPath support eight out of 10. UiPath support is good, but sometimes they give generic users. Maybe I need to take the initiative and give a little more information and context

Positive

There has been a return on investment, though I'm unsure of the specific amount. We've already saved time and thousands of dollars.

I rate UiPath eight out of 10.

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 are using this product to develop automation in the billing section of our website. We are integrating bots so that they can do the basic listing and then our salesperson can take it from there.

The biggest improvement has been in cost. We have been operating it for about eight months for about $8,000. Earlier, it was taking us somewhere around $30,000 to $40,000, so that is a big improvement.

The other part has been accuracy. Before, when we had employees for the same process, there were some minor errors, as well as some time issues. But with this system, I believe the accuracy has been at par, although there are several times when we have had to reframe or do some minor modifications in the AI to make the model work for a new set or variety of clients.

The reduction in human error means we get more leads into the hands of the right salespeople who can work on them. Fewer errors means time savings.

With time, the AI automation has improved. Specifically talking about the kind of business that we do, which is putting things into the right sections so that the right people are taking the right leads, even in some complex cases, we have seen accurate results from automation. AI is doing its job.

AI has also enabled us to automate more processes. Earlier, we had different sets of protocols for differentiating among the different kinds of inbound information we were receiving. Since deploying this automation, we have automated a large chunk of the reception. The accuracy has been maintained and the time has been reduced significantly. We are able to convert the leads in a way that gives us more to work with from the leads we get.

The automation-creation process is quite easy and the accuracy is quite good. That last aspect is critically important because we have used RPA to replace one of our employees and we are taking on a lot of responsibility. The most important thing that we require is accuracy and we have been getting that so far.

The end-to-end coverage is important because each and every part of the input we are receiving from our customers—and they're highly valued customers—is information that goes into our software via automation, and we do not want to miss out on any types of leads.

The UiPath Academy courses have been great at giving an overview of the solution and allowing employees to learn things at their own pace. Other users out there also helped our technical staff, so they have added value. The biggest benefit was that at the time our technical staff was getting used to the product, they felt that there was a scarcity of people who knew about how to execute things. Having this UiPath course was a little helpful because it gave them the initial confidence they needed to start doing things, whether it was right or wrong, and they kept getting feedback and improving.

The only concern is it's a bit tough to understand the first time, and you have to invest in the technical improvement of your team in general.

About 6 Months.

There's no need to worry about the stability.

The only concern is as we move towards scaling it. What happens if the system goes off? Although it's not a big concern, we have been getting reassurance from UiPath that they have a solid backup of everything.

With RPA, scaling is not an issue at all. Once a bot has been trained to do a specific thing using ML, multiple bots can be added for the same automation process, as many times as we want. Scaling is not a concern.

We have not used technical support.

Positive

In terms of our decision to go ahead with this product, although we had received a recommendation that we should be moving forward with it, we were severely concerned about whether doing things over and over would take us the same amount of time, in terms of the technical ability and the workforce, or whether it would be easier. After having a technical call with UiPath, we quickly knew that it would be easier. That was a crucial part of our decision.

The initial setup was easy, but making the AI understand, and using the machine learning algorithms in it, took a long time. It took more than we expected it would take. The UiPath team had us understand that it would be functional after one or two months, but it eventually ended up taking about four months. That was more time than we expected, but the initial setup was easy and straightforward.

We used a consulting firm. There were three meetings over the duration of the two-month contract. The advices we received we about our model selection with regards to pricing and data storage capability.

We have been using it for eight months. For the first four months, I do not believe we were saving time because we had to intervene a lot of times with help from the vendor as well. But from that moment onwards, once the integration was operating smoothly, we started saving time.

We do a regular analysis each month and we have been seeing constant growth. A month is a good amount of time to see the progress of a newly implemented solution.

Previously, we were not using automation operations. I believe we have now reduced costs significantly, which justifies the cost we are paying for the service.

Pricing is good if your venture is looking for growth in 1-10 million size of customer domain.

yeah we got in touch with the IBM team for their automation tool.

Building automation takes some time. The first time, it took us a month, but after that, it was easier. The next time we build an automation, it's a kind of reciprocal of what we did the previous time. The first time involved some help from other resources, but from that time and onwards it has been going well.

The innovation did not happen as fast as we thought it would for the first half. We had to recruit some IT guys to our technical team so that our entire team could become familiar with the process. The innovation potential is there. It helps to get very familiarized with the solution. But for the first few months, the innovation part was delayed. The technical level required to handle it smoothly was not there on our team.

I am working for a client. I am using on-premises UiPath Orchestrator. I have installed UiPath Studio and deployed some processes for automation. 

I have used it for SAP automation, Excel automation, and web automation. I have not yet used the AI functionality. I might use it in the future.

Manual tasks are reduced, and in less time, I can complete a task. 

UiPath has sped up our digital transformation by 20%.

UiPath has reduced human error. With automation, correct values get entered, and there is a reduction in human error. There is a 10% reduction.

UiPath has saved us money because there is a reduction in manpower. It has saved about 20% on costs.

In terms of time savings, for Excel automation, the backend activities are much faster, whereas web automation takes time because it requires loading the screen and capturing the elements. For Excel automation, the backend activities take 30% to 40% less time.

UiPath Orchestrator is very user-friendly and easy to understand.

The interface is very good. In the latest one, they have added many more activities, which has made it even easier to do automation.

While doing web automation, I am facing a selector issue. In the web portal, we need to capture a screen element. For capturing the screen element, when I run the job the next time, it fails because the limit is not recognized. It is very difficult to make the selector stable. It is not easy.

I have been using UiPath for more than two years.

At times, when I restart the system, the deployed robots take time to connect to the UiPath Orchestrator. Overall, I would rate UiPath a nine out of ten in terms of stability.

It is scalable. We can use it in different companies or industries, such as hospitality or finance. I would rate UiPath a nine out of ten in terms of scalability.

It is deployed at one location, and we have four to five users of UiPath.

I am satisfied with their support. Whenever I raise a ticket, they provide the required support. 

UiPath has a user community, but I did not use it much. I used the UiPath documentation.

I have also used UiPath Academy and completed three courses. I have done the foundation course, the advanced course, and the continuous learning course. I am satisfied with the UiPath Academy courses.

Positive

I have also used Automation Anywhere. Compared to Automation Anywhere, UiPath is more user-friendly. In Automation Anywhere, we have to do lots of things, whereas in UiPath, we have to do fewer things, which makes it easier to do automation. Also, capturing the screen is much harder in Automation Anywhere. It is easier in UiPath.

The deployment of UiPath Orchestrator only takes one day. 

In terms of maintenance, it only requires yearly license renewal and making sure it is up to date.

We have two people who are involved in the UiPath deployment. 

Overall, I would rate UiPath a nine out of ten.

UiPath provides a platform for building, managing, scheduling, and monitoring automated processes. We use it for various processes, such as cost analysis, repairing permissions, and manipulating Excel data. 

UiPath enables us to build end-to-end automations, improving efficiency, enhancing customer service, and creating a human focus. The solution helps us reduce human error. UiPath saves us time because it's flexible and makes deploying processes easy. 

It's easy to build automations in UiPath. It has a simple drag-and-drop interface.

UiPath has an active user community covering a variety of applications and use cases. The forum acts as a central hub for community members to ask questions, share knowledge, and seek help with different issues.  

UiPath has added more artificial intelligence to the full version of the product. There are many options for developers to integrate AI capabilities like natural language processing and optical character recognition.

UiPath should expand its coding options and reduce its dependency on third-party resources. There should also be more flexible licenses for smaller businesses. It's hard for small companies to estimate the cost of adding users in their final budgets. UiPath could also improve error handling and capture a little more information about the execution of your processes. 

I have used UiPath for the last four or five years. 

UiPath is robust and always available. 

I have used Automation Anywhere. The solutions are similar. UiPath has advantages in scheduling and analytics, but Automation Anywhere supports all the LoadRunner requirements. 

Deploying UiPath is straightforward. The installation can take from a few hours to a day, depending on the project. You need to implement the architecture, create a data server, and integrate it with the solution.

I rate UiPath nine out of 10. It helps to learn a little coding in languages like SQL and Python. You should also take time to learn the platform with hands-on experience, instructor-led training, and online resources.  You can start with a foundational UiPath course if you're new to the platform and learn about the fundamentals of RPA processes. Then, you can create a simple automation project to reinforce what you've learned. I also recommend joining the UiPath community and asking questions on the forum. Once you have the basics down, you can try some of the more advanced programs on UiPath Academy.