UiPath Reviews

We have a use case that involves an invoice billing process, where vendors from an external organization submit their details for the invoice. This automation works as expected, independently of anything else. It is also a good example of how we were able to scale RPA benefits in the company with the automation of a specific process that requires human-robot collaboration.

Our internal tools include the database where all of this information is stored, and we have a second automation that is used by the billers in our organization to tally the data that includes details such as what each vendor has submitted to get their payments.

We built a third automation in UiPath, which basically compares these first two. But, due to the complexity and the nature of the tally that has to occur, we require some human input in between certain steps.

For these particular steps, we have developed a four-bot configuration. These are four separate bots that run and a couple of them have an attended automation part, where a human can intervene. It's a verification step, where the human can decide whether or not something is okay. Specifically, the bot compares two fields and if they match, then it's great, but if not, it triggers a request to a human user for manual verification. If they approve then it is marked as a successful verification.

Because we use technologies like OCR, there are details that cannot always be interpreted properly. This is where we need an additional check, which is the reason that we have humans in the loop as part of the process.

We have saved a lot of time by using UiPath. We have also improved a lot in terms of accuracy and reducing errors in a lot of projects. In fact, in one of the projects, we automated the entire job, which involves coaching people on what has to be done end-to-end, by the robots. It was built on UiPath and on this project, we had a savings of more than €100,000 euros. That was a big saving for us, and it's continuing right now.

More importantly, a lot of the clients had complained about the end-user, which is outside of the organization, with respect to the accuracy of the data. There were errors. When we deployed robots based on UiPath, the accuracy has vastly improved and the clients are very happy with the results. They no longer have to keep coming back to our billers and telling them that things were not done properly. The robot functions like it has been programmed every single time. So, it's been perfect for that purpose as well. The customer trusts us more because of our deployments in robots.

UiPath definitely allows employees to delegate mundane tasks to their personal automations, saving them time. A major reason for a lot of our automation cases is because most people are not 100% involved in certain tasks. For example, if you spend two hours on a particular process, and then over the next four or five hours, you're supposed to be working on more complicated processes, but what happens during the first two hours is that things get complicated and the day is ruined dealing with small tasks. Now, suppose that the two-hour allotment for the smaller process is automated using UiPath, the person is free to dedicatedly perform more important functions. In the entirety of our automation effort, this has been a primary driver for all of the new use cases. It's a huge plus for us.

With respect to employee satisfaction, it has been a mixed result for us. In certain cases, it's been a huge boon because there was a heavy workload on the employees and UiPath really helped them cope with it. This was especially true during COVID when the workload increased exponentially, and people could not go into the office. However, there were times in the past when people were no longer required because UiPath was doing their jobs perfectly, making them redundant. As they were no longer required, they left the company.

So, we have had both scenarios, but moving forward, instead of telling people that they're no longer required, we have retasked them to other projects. Essentially, we have reabsorbed them and in turn, have simplified the hiring process. In this regard, we have adjusted.

The new UiPath assistant is very good.

The customizable forms that UiPath has recently launched allow us to give the user an exact input that they can provide. Being able to customize this is extremely helpful for us because we have other attended automation processes, and they can each be tailored to the needs of the business.

We use the selector technology for automating processes with dynamic interfaces on a daily basis in almost all of our projects. Our extensive use of this feature includes all of the different kinds of selectors that UiPath allows. We have the flexibility to modify these selectors as per our need. This functionality gives UiPath a big edge over its competitors and I know this because I've personally used products by other vendors. The selection-making process is much simpler with UiPath, with improved accuracy and reliability.

This feature is important because a lot of the processes are Citrix-based or remote desktop applications. Because the robot would not have a direct connection to the application, we have to use Citrix technology. All of the applications are different in nature, so having the flexibility to switch between different kinds of selectors and select our activities allows us to build the perfect solution for remote applications. Even the performance, in my experience, has been the best, especially for Citrix-based automations or remote desktop-based automations.

There are a few features that could be improved, and one of them is good integration with the Microsoft ecosystem. For example, Microsoft launched Power Apps as its platform, and even though its capabilities are not as good as UiPath, it has the advantage of being so well-integrated with Excel Online, Word, and everything else. We don't have to perform a lot of development work, and it's pre-approved in our organization. Applications like SharePoint are another example of pre-approved solutions. But with UiPath, we have to prove that it's a secure process. Simply put, a stronger collaboration between Microsoft and UiPath in a lot of areas would be helpful because it would ease the development process for us.

Another example is with the Automation Hub. At this time, Automation Hub does not allow you a direct login process or single sign-on option using Azure Active Directory. This means that you're limited to going through either Gmail or something else. This is true for the on-premises solution, not the cloud one. Although we had decided to purchase the Automation Hub license, this lack of functionality held things up because we did not want to manually go in to update all of the new users again and again. We wanted the information to be picked directly from Active Directory whenever a user wanted to sign up for it.

I have been using UiPath Attended Automation for approximately three and a half years.

In the past, stability has been great. However, more recently I have been facing some issues, and I'm hoping for some resolution. For example, we recently upgraded to the new orchestrator in Studio, and we had to upgrade a few packages also, In particular, the UiPath automation packages.

Some of our GUI activities, which are not fully backward compatible, have been facing some issues. Consequently, some of our bots have been impacted. We have already raised the issue and we are in discussion to find a resolution. This was the first time we actually faced an issue in terms of reliability with UiPath.

Our past experience has been very good, and I cannot say that we have any complaints regarding the reliability of UiPath solutions.

Scalability-wise, it is very good. It is easily scalable and we have a lot of options for expanding and configuring as per our requirements. It is also customizable.

We have a team of between 20 and 30 people, which includes approximately 10 developers, 5 team leads, two architects, two production managers, and one overall manager. We have some contractual workers, as well.

We have approximately 35 automations that are in production right now. From a process perspective, we have pretty much worked on all verticals including finance, healthcare, internal IT processes that needed automation, and more. An example is ServiceNow, where jobs like creating user accounts, deploying new machines, and other administrative tasks have also been automated. HR processes, including onboarding, have been automated.

It is a very large organization, and there are lots of processes, so I expect that our usage will grow.

The technical support is excellent in our experience. Whenever we have had a problem, they've always been there to support us and help us with the problem. I don't have any complaints, as they've always made the effort. Even if things have taken longer than we had hoped or expected, they've always come back with the best resolution they can offer.

I have worked with Blue Prism and in my experience, UiPath does a much better job, both in terms of dev and listening to the community. For example, Blue Prism is a very closed community and very limited. They have improved, I would say, based on the success of UiPath, but it's not very open-source or open-natured.

The biggest advantage that I have noticed is with Citrix-based automations or remote desktop automations. There are cases where Blue Prism did not work, but UiPath was very good. I did not have to spend too much time with UiPath before it worked perfectly. The reliability was also great.

More importantly, UiPath listens to the customers as well as the developer community, and in turn, they implement features that make their lives easier. They constantly reach out for feedback and it's a good process because it helps to know that the customer is happy. If I am speaking about myself, I'm happy that if I have a need, or I'm facing some challenges, I put it in the pipeline for UiPath and within six months, I will see that feature live in production.

We started with a disaster recovery scenario, where we have one live production orchestrator, as well as one backup orchestrator and a load balancer installed. This is a high availability disaster recovery (HADR) configuration, where all of our live bots are on the main orchestrator. In the case that the live orchestrator goes down, we have the backup orchestrator kick in.

The overall deployment and installation process was simple. However, we did face some issues with the Redis part. Configuring Redis was one of our pain points, and we reached out to UiPath about it.

Although it was resolved, it took a lot of time and effort, from our end as well. That was the only experience that stood out as a problem for us. But overall, it was a smooth process.

It took about a week to set everything up, although we had constraints from our own internal infrastructure team. The delay was not related to UiPath issues.

The licensing is close to optimum; however, there is room for improvement in both the cost and flexibility of the licenses. It isn't the best pricing in the market but it's pretty close.

For developing our attended automation, we began by coding the bot to our requirements, and then made modifications to it for attended automation.

My advice for anybody who is considering UiPath is to be sure of what your needs are regarding an RPA product. If you're looking for something very small-scale, very easy, then there are a lot of options. But if you're looking for a long-term, feature-rich solution, which has access to third-party integrations, then choose UiPath.

You will require a development team, at least to some level. UiPath is now simpler with the Studio X products, but in the past, it was a bit more challenging to dive deep into UiPath directly. It required some training but now, things have definitely improved.

One of the major lessons that I have learned from using UiPath is to make sure that everything is documented well. There is a lot that needs to be tested before bots are put into production because a lot of things that work on your local machine may not work on another. It can vary from machine to machine and where something works on one, a change in environment for another may cause it to fail. This means that you should change from machine to machine during the testing phase.

Overall, I feel as if now UiPath is on the right path with its competitors. It is a very good long-term solution.

I would rate UiPath a nine out of ten.

We use all of the UiPath products: UiPath Studio, Orchestrator, attended robots, and unattended. Primarily, we use them for financial liquidation. Our customers frequently use it for different cases. Some use it with chatbots.

Sometimes, our customers run automations in a virtual environment. In terms of implementing UiPath within a virtual environment, UiPath staff are working on the cost. Currently we have UiPath with a Citrix client and you need to go to the Citrix virtual station to activate. It's more difficult to implement as a user.

Our customers' organizations have involved about 15 to 20 people in their automation programs.

I would rate its ease of use as about four out of five. It's not so easy, but it's also not difficult. We have a great UiPath Academy and it's really useful and helpful. Sometimes we need to do difficult operations and use other frameworks, through activities in UiPath. I think this mechanism is very nice, but in implementation, the customers are pretty close. Sometimes we must do it.

This solution helps to eliminate human errors. The amount depends on the process and the customer. Even unattended robots don't provide 100% automation. Sometimes a robot interrupts and waits for a human to make a decision. There is a process when unattended robots do fewer steps and after ten interruptions are waiting for a human to go on. I would say there is about a 70% reduction in human errors when using an unattended robot.

UiPath also helps save time. One unattended robot works 24 hours a day because a robot doesn't get ill or need to sleep.

All of the features are valuable. I think the best feature for Russian government customers is security. Security in Orchestration for requiring credentials. Our customers are usually serious about security.

I would like to see more AI features with data classification and computer reason. I think it would be great to have more features in full monitoring robots.

I would rate their stability as four out of five.

In cases of high scalability when we have one process and many of us use that process, we sometimes have problems. When one process uses about 24 robots for 24 hours, we have problems with it. I think when many robots work at the same time, something goes wrong in orchestrating tasks between robots.

I am happy with the support. For me, it's okay.

The initial setup can sometimes be complicated, depending first of all on the environment, as well as the implementation strategy of the company. Too many processes or only one PoC could lead to a more difficult implementation. Sometimes, customers try to automate a lot of the big processes. When we try to automate the complete process, we understand with the customers how many FTEs you can get from it. Everything depends on the customer's requirements.

It takes about six months from the purchase of a UiPath license until our customers have their first robot in production.

UiPath is a data mining solution. Our company tries to explain why RPAs are useful.

I don't know which other solutions our customers evaluate. Kofax might be one. Sometimes we work with a customer to make a decision about which platform to choose. Sometimes we do a PoC for Blue Prism. In the Russian market, there are two major vendors that are competing against each other: Blue Prism and UiPath. Usually, customers go through a PoC to choose the best vendor. UiPath wins because you can automate more processes with it.

I would rate UiPath as nine out of ten.

We are using the unattended robots and Orchestrator modules of UiPath.

We have built close to fifty processes in the three years that we have been a client. Our primary use case, the one the gives us the biggest relief, is the processing of premium border rows. The robot will pick up Excel files with between four hundred and a thousand rows of data, and then does the data entry into our policy issuance system.

All of our automation runs in a virtual environment and we do not have any problems. At the start, of course, there were a few bumps in the road, but we got it figured out and now have no issues at all using the VM.

When we began working with automation, I was the leader and I had three BAs and three developers offshore. When our company decentralized, we created three other robotics divisions. There are now twenty-eight of us including the project manager, the BAs, the testers, and our developers. People are spread across four different divisions within the corporation.

With respect to how easy it is to automate our company's processes, I will consider the individual components. With the Orchestrator, on a scale of one to five, that's easy, it's a five. It is very evident how to use it. The Studio, I am not a developer but I got six developers up and running on it in a very short period of time. It has a very short learning curve, so on a scale of one to five, I would rate it a four.

My rating of four is because I know that we had some challenges with using the recorder. Things would shift and there were a couple of things that had worked and then stopped working. We found a little instability, and it was hard for us to know whether it was us, or the application, or the studio. Ultimately, we were not able to get a final answer on the root cause of those problems.

We are no longer experiencing these problems. When we upgraded, a lot of that went away. Also, when we went to Orchestrator, a lot of that went away. Exactly as UiPath had told us when we went to them with the issue, they gave us some solutions and once we implemented them, the issue was corrected.

I did not attend the UiPath Academy, but my Business Analysts took the BA course and my offshore developers all took the Academy. On a scale of one to five, judging how beneficial it is, I would rate the training a five easily. Before the Academy came around, they were kind of self-taught. When they took the Academy, it closed some of their gaps.

When we started with this solution, we did a PoC with the help of a UiPath developer. In two weeks we built a PoC for a bank reconciliation, which was pretty fast. That helped us decide whether we wanted to go with the product, and of course, we did. After that, we took the code, which really didn't have a lot of bells and whistles in it, and we gave it to one of our developers to really soup it up and make it more robust. That took them about a month to do.

Orchestrator has given us a huge boost in terms of efficiency.

In addition to the resource-creating benefit that we get from this solution, it has given people the opportunity to move away from those mundane jobs and into something more challenging. Rather than sitting there doing data entry, they're able to move up, re-skill themselves, and add value to themselves as well as the organization.

We have been able to eliminate one hundred percent of human errors. We found that the robot was better than the human because when the human was doing some of the processes, they were supposed to be checking into another system. While testing our robot, we found that the robot's state was different from this other system that it's supposed to check against. We thought that the robot was wrong; however, we found out that the humans were eliminating that step. They were cutting corners. This stage of our development raised a flag to inefficiency on the human side.

In terms of the time that this solution saved, it equates to the equivalent of four full-time employees a year. At two thousand hours per year times four, that's a savings of eight thousand hours.

The Orchestrator is great because you schedule it, and that's it, you don't have to worry about it. It will tell you what passed and what failed if it had any issues. We don't have that dependency on someone needed to schedule tasks.

The code in Studio is easy to follow. I am not a developer, but I am able to read the code. When we have problems, the developer will display the script and I'm able to read it and follow it. Several times, I have been able to see where there was an error and the developer was able to fix it. It looks like it's easy to code.

We had some issues with instability for which we were never able to determine the root cause.

On a scale of one to five, I would rate the stability of this solution a five.

A UiPath consultant assisted us with our PoC, and the experience was incredible. They were really wonderful.

The technical support for this solution is excellent. They're very responsive and we never wait more than twenty-four hours for an answer. The developers have more contact with support than I do.

We did not use another RPA solution prior to this one. Our former CFO went to a meeting where they were talking about robotics, and when he returned from the meeting we had a discussion about it. I was working in Internal Audit at the time, and with his prompting, I left Internal Audit to head up the robotics process. From there, it just took off.

The initial setup of this solution was straightforward. To me, it just made sense.

In our first year, the development was a little bumpy, which is to be expected. I would say that it was fourteen to fifteen months before we hit a smooth path. Even with that, things go smoothly for a while until you start doing more challenging and more complex things, then you're back to a crazy path, then you correct yourself and things go smoothly again.

One of the issues is bad user requirements. Simply put, we don't know what we don't know, and we're dependent on the business to tell us. Even if you ask the same question in a variety of ways, if the business can't articulate it or tell you about it, then we can't build for it. Getting the right user requirements was our biggest challenge.

After that, we were trying to build for everything, instead of just building for the straight path. Trying to build in all of the exceptions and allow room for an imperfect world is what took us down. We've since learned that we're going to build for the straight path, and then look at the exceptions as we start to gather data on them. When we find exceptions that occur at a high frequency then we'll build for that. Failing is fine, and it is expected, as long as you can learn from it. Our approach is based on what we have learned from our mistakes.

From just one of our four divisions, A&H, we saved approximately $390,000 USD. You can multiply that to include the other three divisions (Estimate: $1.5 Million Dollars).

This past July, I completed a cost-benefit analysis and we determined that in the three-plus years that we have been using UiPath, we created the capacity to the equivalent of four full-time employees and have cost-avoidance in that we didn't have to hire five other employees. This is where the value is helping us utilize resources better.

Overall, we are giving ourselves a two year ROI.

We did not evaluate options from other vendors.

We went to Swiss RE because they offered to show us what they were doing. We saw their process and we were impressed by it, and it was a pretty nominal cost to buy the package. We thought, instead of wasting time, which could take months, and management wanted us to hit the ground running, we would try it. If we didn't like it then it wasn't a big loss of money. So, we totally circumvented the traditional route of purchasing and we are happy that we made the right decision.

From what I have seen recently, I'm excited to try the Community and start building my own robots because it just looks like it's gotten a lot easier.

I am looking forward to one of the upcoming options, the dashboard. It will give us the productivity of the robot, which is something that I do myself right now. I record everything on each robot that runs and we keep metrics on it. These include how long it took to run, how many transactions it processed, and what the error rate is. Then I have to figure out ROI. So, the dashboard is huge and at the top of my list of things that I want to see.

We have a process for obtaining the right requirements for someone to follow. We go and observe the business and we record the process. That way, when we have to sit down and write the requirements, we can refer to the video and don't have to keep going back to the business because that is going to annoy them. We include the video when we send it to our developers and that way they have a visual for it, as well. When we put together formal documentation we show screen prints of where to click. After doing it a couple of times, one of our developers had this great idea to make things configurable so that we're not hardcoding a lot of stuff in there. With that configuration file, we just keep improving.

From a cost perspective, I can't speak to the advantages of attended robots because we do not have any. When I look up the pre-automation cost of doing a process versus post-automation, we give ourselves a two year ROI. We're not going to automate everything immediately, so we give ourselves a two year ROI and if it's going to be a positive ROI, we'll go with it. Of course, based on what it is, we'll prioritize. If it's a nominal ROI it will probably go to the bottom of our pipeline, but that's what we do when trying to evaluate initiatives.

My advice to anybody who is researching this type of solution is to try UiPath. Use the free version. I have a friend who does this as well, and I encouraged him to use the free download and do something simple. After it worked, they would up going with the product. With respect to the cost, you're going to recognize the savings immediately for the cost of the tool.

We are very pleased with this product.

I would rate this solution a ten out of ten.

I personally do a lot of process automation and data visualization. I work with a lot of people in procurement and finance to pull data from a lot of different systems, consolidating it, and creating reports, then presenting it. What I do a lot of is taking that consolidated data and creating automated reports with Microsoft Power BI and visualization tools. A lot of where people get hung up is pulling the data and the amount of time it takes to do that. So, people want to be able to automate their processes, as well as have my reports.

When I heard about UiPath, it addresses the initial problem of having to constantly pull data, get updates, consolidate the data, then model it in Excel or other sources, like databases. Being able to speed up that process, then connect it to automated reports, can fully lay out that entire pathway. 

It has a simple user interface. We used to have the training onsite Friday and Thursday, and while I personally have a computer science and web development background, a majority of the people there were finance and were procurement who didn't have any technical background. Yet, they are able to learn it because of the GUI and hotkeys, because it is just enter, drag this there, and do that. 

You don't have to write any code. You simply click function, open an Excel file,  and open web browser, then you just grab and drag it. This makes it easy to understand what you have to do and where you have to put fields.

It could be a little more aesthetically pleasing. 

I would like it easier to find things. How it works now: 

1. You look up all the different built-in functions that they have. Most are pretty straightforward. It is click in an open access web browser.
2. If you don't know the name of what you are looking for, but if you want to be able to do something, then you have to scroll down the page and click it, if it's found.

I would like a better way to find the little things that aren't simply named.

I haven't found any problems specifically using the tool. I have only had a few errors, but that is because of personal mess ups when I'm creating processes and a field is messed up or a variable is incorrect. I haven't had any crashes or faults with the free Community Edition and the bot that it has come with.

I have talked with the UiPath training staff who came to our site and worked with them. They helped us out with any problems that we had learning things.

I haven't communicated directly with any of their support team members.

The initial setup was pretty straightforward. It was easy for us, and we are government contractors. We had to get all the approvals, but once that was done, it was very simple to get it installed and set up. Then, you just have the desktop client right there. 

I assume going through any of the training on the UiPath Academy that you would have an understanding of how to work through installation issues.

I see the potential for ROI and how much time it can save me on cutting down weekly and monthly reporting. It will probably save me five hours a week and another 15 hours a month.

It is a tool, which does what you need it to do.

I went through two non-technical training course to get an understanding of using robotic process automation because I didn't know much about it before I started using the tool. That set me up well before the UiPath Academy to get an understanding of robotic process automation and where it's been going, because I didn't have much knowledge beforehand. However, I plan to go through the Academy training courses. I've heard that it's what UiPath uses internally to get ready for certifications.

I use UiPath to automate repetitive tasks within our organization. It helps us deploy processes without human intervention for some tasks.

UiPath has helped my organization, especially in the banking industry, by automating processes, reducing manual work, and saving costs. These improvements enhance process efficiency, reduce stress, and improve end-to-end efficiency.

The Studio is a valuable feature because it allows us to automate processes independently. It enables us to configure and manage everything through a web application called Orchestrator, which is particularly helpful for large organizations.

The documentation related to new releases needs improvement. It should provide a clear understanding of what was present in the old release, what's new, and how it affects users.

I have been using UiPath for around three years.

UiPath's stability is satisfactory. No product offers one hundred percent accuracy, but UiPath performs well overall.

The solution is very scalable. I would rate it eight out of ten for scalability.

Technical support comes primarily from engaging in UiPath's forum, where people share insights. I find the community engagement to be more helpful than direct product support.

Neutral

The initial setup was straightforward. Deployment doesn't take much time once the development and testing phases are completed.

The implementation of UiPath saves a significant amount of money and reduces manual errors, improving overall performance.

The pricing and licensing of UiPath are expensive. I rate it ten out of ten in terms of expense.

I recommend using this automation tool based on the specific needs of the industry or organization.

I'd rate the solution seven out of ten.

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.

I have done the certification in Microsoft Certified Solution Associate (MCSA) and Microsoft Azure Administration. I look after the actual environment site where we can run the bots. We watch the environment's behavior, and we operate the Orchestrator, which is connected to the AI system. We run different types of processes through Orchestrator, and I am the administrator of Orchestrator. I give the rights and assign roles to the users. 

UiPath has been performing very well. It is very easy to learn and understand. We are going to move the most work done by employees to the bots because the bots get work done in minutes instead of hours. An eight-hour job can be done in three to four hours. 

We plan to bring more bots for efficiency. We would like to add more bots and reduce the time taken for various tasks.

We can design bots in a static or dynamic way. We can use the dynamic way to perform the actions in any environment or platform.

UiPath has freed up employee time. The time saved depends on the complexity of the process.

UiPath is easy to work with and understand. If anything is confusing, we just send our questions, and we get the answer as soon as possible. Designing a process with email, Excel, and any other application can take more than 15 or 20 days.

UiPath saves costs. By using bots, we can save the costs of services provided by humans, but I do not have the metrics. We have many departments, such as finance and global compliance management, and it is hard to know how much cost it has saved.

Orchestrator and features such as Queues Triggers are helpful in monitoring the ports and looking after the performance.

I have done the UiPath Academy course to learn how to manage the environment and Orchestrator. I was able to learn many things through UiPath Academy, and I was able to work on Orchestrator myself. The benefit of UiPath Academy is that it is accessible from everywhere. You can continue watching the videos at home or in the office. The explanation, presentation, and instructors are very good. You do not have to watch the videos again and again. You can just watch it once, and you understand everything.

For UiPath Orchestrator and Studio, if I want to watch the performance of my machines at a specific time or time range, there is no option for that. There are options for one day or week, but there is no option to specify a date such as from Nov 1 to Nov 3. This option should be there for queues and monitoring.

It has been more than one year since I have been using UiPath.

I would rate it an eight out of ten in terms of stability.

It is a scalable solution. I would rate it a nine out of ten in terms of scalability.

We do not need much support to use UiPath. We are not getting many errors.

Positive

I have not worked with any other similar solution. I have only worked with UiPath Studio and Orchestrator.

We have worked on the Python scripts to design the bots, but it was complicated. We had to write more and more scripts and make them efficient. It was very hard. With UiPath, we found a very good option to perform the activities in an easy way. We do not have to code much. We can just drag and drop things and have a solution. 

It is mostly straightforward. We just need to call IT to install UiPath. I give the license via a machine key.

We have it on-premises. We have not connected it to the cloud or third party. 

In terms of maintenance, there are certain packages that we have to download for running the activities. For example, if I am using Python with UiPath Studio, I need to download a specific library.

We implemented it in-house. For deployment, there are two or three members of the team who work with UiPath and provide the infrastructure, and then we have about 25 developers. We have a development team and an operations team.

The development team develops the processes and the operation department runs those processes via triggers or manually. They are usually run on the Windows environment. There are multiple bots working at the same time, and we have the monitoring tool by UiPath, and we are also working via Kibana. Kibana works with Elasticsearch. We have all the logs and bots' performance metrics. We can view it all with one dashboard in Kibana.

RPA is the future. Every bank and organization is looking for bots to perform their jobs because bots are more efficient than humans.

It is an efficient and easy-to-use tool. If needed, you can get a lot of support through UiPath forums and other resources on the web.

We have not used the AI functionality in our automation program, but we plan to use it.

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

The primary use case for document processing, automating data extraction from previously hard-to-access documents. This saves time, reduces manual work, and makes hidden data more accessible and usable.

It allows us to extract valuable information from various documents, categorize them based on their types, and make the data within these documents usable for our needs.

Assessing an AI center's role in orchestrating various elements of AI capabilities is quite constrained.

I have been working with UiPath for three years.

I find it to be highly stable.

Scaling on-premises can be cost-prohibitive due to the need to invest in hardware and infrastructure. This cost factor makes transitioning to the cloud a more attractive and well-designed option for scalability.

Our experience with their customer support has been excellent. We've encountered very few issues that required us to reach out, but when we did, we could contact our dedicated representative, and they efficiently escalated the matter, resulting in a prompt response from their support team. I would rate it eight out of ten.

Positive

We have experience with Microsoft Power Automate, but it's important to note that UiPath and Microsoft Power Automate serve different purposes and have distinct target use cases. This uniqueness is a critical factor that sets them apart from each other.

The initial setup process was quite straightforward.

We initiated the POC to test the viability and implementation of automation before expanding the environment. The setup was designed with the understanding that we required distinct test and production environments. It was initially developed as an on-premises solution and is now transitioning to a cloud deployment. We've had a lot of success with Lydonia Technologies as a partner.

We now have access to critical data, and the accuracy has improved significantly. Additionally, the time it takes for processes or submissions to go through has been reduced from three or four days to just one day. While the cost savings in terms of dollar values may not be substantial, the real benefit lies in freeing up employees to concentrate on more meaningful tasks.

I find the pricing to be reasonable, especially when compared to other offerings in the same market.

My advice would be to begin with a small-scale approach and construct your automation incrementally. While it might be tempting to automate an entire process in one go, it's more practical to break it down into smaller components. This way, you can adapt and refine each piece as you go, reducing the risk of issues arising or changes occurring before the entire automation is completed. 

Overall, I would rate UiPath eight out of ten.