UiPath Reviews

We are a consulting company and we work for different clients. I have mainly used UiPath for financial processes, like bank and vendor reconciliations, order management, order processing, collections, and invoice processing.

UiPath automations have saved a lot of man-hours for business people. They used to have to do simple tasks, like creating reports in Excel and calculating with formulas. We just uploaded the data into SQL Server and then connected to Power BI through UiPath. It was a small project for us, just a matter of two minutes or so to put things in place, but it saved them a lot of time. With the bots doing this "small" work, it enabled the employees to relax and work on more valuable tasks.

The employees involved have been happy and they have also suggested a few other processes that could be automated, after seeing the results.

There was also an order management project in which we extracted details, such as delivery date and quantity, from a PDF. Before it was automated, that was a tedious task. It took a lot of time for people to do it and their accuracy was lower than the robot's. The automation reduced the team size for that business and they were very happy. They saw a very good ROI. And it used to take the business much longer to do small reconciliations, but the bots are so fast. They are seeing good results. It has reduced a lot of human error. Initially there are some errors, but once you learn from them and train the bot, you get accurate results.

We have only done a few attended automations, but they have sped up processes that require approval. In those situations, they play a major role. More than the monetary savings, the benefit is that people can concentrate more on the important work, and with less stress. But unattended automation is the most important process.

The OCR makes it much easier to extract the details, as does Advance Document Understanding.

I would also rate the ease of building automations as an eight out of 10. It's quite easy in general. In some cases we need to use a coding language like Java or .NET, but we can easily build simple or medium-level tasks. It's even accessible for business people. If we try to explain the code or the architecture of our design, they're able to easily understand.

The UiPath Apps feature has helped to reduce the workload for our IT department by enabling end-users to create apps. Even some of the business people have been trained to do that. They have been able to build small, attended bots.

And when it comes to minimizing our on-prem footprint, I would also rate it at eight out of 10. We have seen good results from our on-premises build.

And if we are not sure about something, we can get help from the UiPath community. I have worked throughout the whole cycle, and in all aspects we get good support. People voluntarily contribute to the community. It is a vast community and we get answers quickly. UiPath itself helps people connect and they give badges and goodies to people who are contributing well.

Initially, it was mandatory for us to get certification through the UiPath Academy. The course is free and even the business people have been interested in upskilling themselves. All the Academy courses are very good.

I have been using UiPath for over three years.

The stability is good, but they keep upgrading versions. If you want some of the new additions, sometimes you have to take a beta version.

The scalability is very good, and with the latest version it will be much easier.

Almost all our departments have used UiPath automations. Management is trying to identify what else is possible. It's spreading to all our company's departments.

Whenever we have an issue that we cannot solve, we contact technical support and they try to identify the issue and give us the best solution. If we give them our machine IDs, they try to get into the machines and resolve things. Some of our cases were really complex, and they visited our site. That was the best part.

Positive

The initial setup was straightforward. It is a little technical but not very complex. The deployment time depends on getting all the prerequisites in place but it usually doesn't take long, about two hours, on average.

Maintenance depends on the complexity of the automations. You have to monitor things regularly.

The ROI is very good. We have been able to deploy many processes and upper management is pretty happy with the investment they have made in the bots.

Compared to other solutions, the pricing is moderate.

We compared UiPath with other tools and then we made the decision to go with it. A few of our clients use other tools, but in our experience, UiPath is best. It is much easier to use, compared to the others.

We referred to industry reviews and we had discussions with peers and colleagues. I did some research into the market and then I chose UiPath.

Automation will enable you to concentrate more on the things that require decision-making and knowledge, rather than just doing repetitive tasks.

As we have upgraded the versions, it has reduced the time involved as well. Initially, it was taking some time. But once we and the whole business got used to it and understood how the bots work, things went way faster. The solution is improving every day. It has already moved to the cloud and it should start working on IoT because they have started with AI. That will make IoT will be much easier.

We're doing mortgage loan processing. When people are applying for a new loan, we're using it to gather all loan documents and validate the property ownership and do a title search. We then put the loan documents in a package.

We are using its latest version.

It used to take two hours to take all these documents and load them in, and now, it takes 15 minutes. So, we went from two hours to 15 minutes. We're able to process a significantly larger number of documents in a much shorter time.

It had pre-built integration with the scanning solution that we use called Kodak Alaris. They use our current scanners to scan in the documents, and then they have the software that allows you to load those documents right into UiPath Orchestrator. That gave us the ability to automate those processes.

It took quite a bit of time to understand some of the document types. Some of the documents were already pre-built, but some of the documents were new, and it took us quite a bit of time to get it to train on those documents. If there was any variation, we had to re-train it. It took longer than expected.

I have been using this solution for about four years.

Its stability is very good. 

It is enterprise-ready. So far, we are very happy with everything that we have been working with. It is designed for enterprises. 

We're going to continue to use it for the next five years. It is automating the roles. It has to do more with validation than anything else. The users like it a lot, and we're very happy with it so far. 

We have a third party for support, and they are very good. They are very quick to support.

All in all, it was pretty straightforward. We had to bring in third-party consultants to get it going. We were expecting that, but the costs were a little bit more than what we were thinking at the time.

From beginning to end, it probably took about four months. It included everything that we were trying to do. We got started right away, but the actual deployment took a little bit longer than what we thought it was going to take.

We've moved from different versions over time, and we were able to do it pretty seamlessly. We had another product called Automation Anywhere, and that took a lot more effort to do the migration. So, we were happy with the implementation time that UiPath took.

We took the help of a third party. Our experience with them was good. It was more expensive than we thought it was going to be, but overall, it was good.

For its deployment and maintenance, we have a team of four people in the house, and then we have five people outside who are actually continuing to do maintenance in terms of upgrades and new forms as they come up.

We have probably saved about $6 million using the product. We were going to have to hire about 600 people to be able to process the loans, but we only had to hire 150 people. We didn't have to hire 450 people, which was pretty significant.

We did pay more than what we thought we were going to have to pay upfront. We had a third party for implementation, and the cost turned out to be about twice of what we thought it was going to be upfront. So, instead of one month, it took us three months for an ROI, but we got significant returns. 

The hardware requirements to manage this was also a little bit more than we thought it was going to be, but our ROI was so high that in a way we earned it back. So, even though the costs were more than what we were expecting, the return was much better than we were expecting. We were supposed to go from two hours to one hour. That was the goal, and we went from two hours to 15 minutes. The benefit was more than what we were expecting.

Its actual cost turned out to be about two times more than what we thought it was going to be upfront. There were hardware costs that we were not expecting. Some of the server costs and things of that nature were higher than what we were expecting but based upon the return, it was a net.

We looked at Blue Prism, Datamatics, and Signavio. We just looked at the market and how many references they had that were in our market space. We were able to talk to a significant number of companies that were already using these products for the same thing, and that's what we based our decision on.

I would advise doing the homework upfront and seeing what the full impact is going to be. You should not just look at task automation; you should also look at the full process. That's because when you make a change in one area, you need to consider how that's going to affect another area in your organization. You may get a big benefit in one area, and then all of a sudden, you have to change the way you're doing business to take advantage of that. If you correct a bottleneck in one area, you might still have another area that's a bottleneck, so you need to look at the full process. This is something that we learned in general from our experience. As we were fixing different things and automating different things, there was another bottleneck down the road. We went from doing 10 a minute to 100 a minute, but when we went to the next process, we could only do 10 a minute. It didn't really make a difference unless we fixed that one too. That's why you have to look at the full end-to-end process.

I would like them to work on the process mining solution that they have to give us a better picture of the full end-to-end process. That was what was really missing. They do have a process mining solution that you can run up front, but it wasn't very good. We ended up running into things thinking why didn't we know that. If we had a better tool upfront to give us the bigger picture, it would've saved us a lot of time and effort down the road.

I would rate it an eight out of 10.

Our primary use cases are for any financial business process. Primarily for myself, I was with an organization that did a lot of back-end middle office, and front office automation for many midsize banks and credit unions.

We saw anywhere from three to five times ROI, based on the business processes that we were able to automate, and its ability to enable the organization to do more with less.

It increases operational capacity. We noticed that it even helped a lot of the C-levels with employee morale and to keep their retention as well. If you enable your FTEs with the tools that they need to do their day-to-day operations, that's naturally going to create growth.

Our clients have absolutely seen a reduction in human error and time savings. As long as the accuracy of your data is there, the bot can learn the business process, based on how you develop it. It's emulating human behavior within graphical user interface automation. We've definitely seen an incredible amount of ROI on that.

The most valuable features are the ease of use and the amount of resources and community that are out there for UiPath. They have all of the information that you would generally pay for with other providers. It's a very easy-to-learn solution as long as you put time and effort into it.

UiPath has a low-code and no-code approach; the user interface is intuitive. It's something that can generally be used by either a business user or anyone that has a high-level understanding of IT.

We use UiPath's Apps feature. Depending on the applications that we're looking to build and connect users with, or any of the existing connectors or apps that exist with the UiPath, we definitely utilize this.

The Academy is a huge catalyst for allowing your business users or your IT users to learn the solution at their pace. It's a very intuitive Academy that's provided free of charge. It's something that really enables the organization to help them develop citizen developers. Enabling users is the biggest hurdle that a lot of RPA users or anyone that's looking to implement RPA is going to be facing. UiPath has a tremendous amount of training and information that's out there through their Academy. It's definitely attracting a lot of organizations to lean towards UiPath.

The biggest value we've seen from the Academy is the amount of operational capacity that it allows for organizations to do more with less. Anytime you look into or embark on an automation journey, you're really looking to drive efficiency through automation. That is something that's really needed as you start to go into 2022 and post-pandemic.

There should be a little bit of a longer trial version. I know that their existing trial version is around 30 days. I think it would be very beneficial to make that a 60 day trial for active POCs.

We have been using UiPath for three and a half years,

The stability of the solution is really improving itself from where the organization really started to embark on automation. Year over year, they've added new features, and really what made automation more of an omnichannel approach.

It's not just another tool to develop bots, but it's a tool that has process mining and tax task capturing. It's something that only comes in with an end-to-end approach, rather than other RPA tools in the market that only have point solutions just for development and really don't have an end-to-end solution.

Scalability is something that is quite remarkable at this point with their cloud solution. Growing your RPA footprint doesn't really propose a tremendous amount of a challenge anymore. Their cloud approach is going to definitely help them move forward in 2022 with a good amount of growth.

I found the initial setup to be fairly easy. If there were any complexities, I know that they have great support, resources there internally to again guide you through that automation journey.

The form of engineers that they have, as far as the level of understanding and so forth, is quite remarkable. That is where they're really leading the market.

They should provide a clearer and more of a definite approach for any organization that wants to sign beyond a one-year, two-year, or three-year contract.

A little more visibility and more clarity would help, even for the partners. There should be more visibility into the price measure.

Compared to Blue Prism and Automation Anywhere, in terms of the pros, UiPath has built a great community around the solution. The amount of training provided by their Academy is something that is really helping them scale the organization. That's where Blue Prism and Automation Anywhere can take some notes from UiPath, as far as what they're able to provide to the market.

Ease of use is something that is definitely moving the business users into adapting UiPath at a much greater scale. Simply because it requires less technical knowledge.

Someone without an actual IT background can come in and start developing their own bots to help them from a day-to-day basis. Those are the pros. Obviously, the cons are that those other organizations can start providing a little bit more information to their prospects. Even as a partner, sometimes it becomes challenging.

The number one piece of advice that I can give anyone that's embarking on automation is that automation is something that's been proven. It comes down to why wait and automate today, and whether it's going to be a low, medium, or high complexity bot. That's something that organizations need to embark on it now, instead of waiting. 

I would rate UiPath a nine out of ten. To make it that 10 they should provide a little more clarity on their subscription and pricing market.

There are lots of use cases. Mostly, there are many gaps in organizations that buy a lot of software and a lot of automation platforms like ERPs, however, they don't know how to actually create an end-to-end process and connect those systems. In those cases, they end up like small islands in a big organization. What I started doing was filling those gaps. After that, we use the RPA to fulfill that. For me, a lot of processing in Excel or some processes that needed multiple users to interact is what we use the solution for. We just capture those tasks and convert them to RPA bots. Basically, we've automated a lot of manual tasks.

We do not use UiPath in the contact center environment. In our case, contact centers here are really dependent on CRMs. Even using chatbots in contact centers is still very new in Iran. These foreign branches, these foreign companies that are in Iran, do not see any potential to use RPA in this scenario. 

Mostly, UiPath has improved my career. I am an RPA Developer, and without UiPath my job wouldn’t exist. UiPath changed my career. Due to UiPath (not Automation Anywhere or not Blue Prism), there’s a noticeable increase in the speed of development. I was a C# Developer and it's helped me a lot. Generally, UiPath is in the top 10 and has offered a lot of new technological shifts and people are talking about it more. When people are talking, there are great opportunities. There are now new voices that can be heard. 

UiPath is constantly listening. That's a good point for UiPath - it's always listening from its community to its top customers and interacting with comments. Due to the fact that it listens, it integrates new software, goes into end-to-end automation, and changes for the better. Someday they will have Autonomous RPA, a real Autonomous RPA that can actually decide like a true robot, not just a robot that works on a script. One day they will offer a true robot that can finally decide what to do in certain situations, not by just using something like document understanding that we call Machine Learning. UiPath is very, very good at giving true innovation to people. It’s a win-win for everyone.

RPA is actually something that can be executed, that can be used side by side with many programming technologies.

The speed of development in UiPath is very fast. For example, sometimes you want to do many frameworks and the budget is low, with the timeline being very crucial. With UiPath Studio and with the whole UiPath platform, it can be very fast to develop and deploy. That's the main advantage for me personally - that the speed of development is great.

UiPath enables us to implement end-to-end automation starting with process analysis, then robot building, and finally monitoring. They are all there. The one exception I’ve noticed is that end-to-end automation is still lagging, I have reasons for that. However, the monitoring of the robots or even using insights is there. They are the prerequisites for an RPA platform. They are great suites. They are necessities.

I like parallel processing. I like that a robot can do some parallel stuff while the user continues to do their own thing. If it needs interaction, we can just pop up a clear window or apps, for example, or through email, in order to inform the user about the robot's request.

AI Automation overall has enabled us to automate more processes. However, when we go forward and move forward, we see that we can digitalize those documents before it needs to be processed by an image machine-like OCR or even Machine Learning. For example, there are still handwritten documents. We’ve convinced many organizations to drop those handwritten documents and use digital products for us. Those are immediate time savings for the process. We are not using document processing anymore, for example, in a specific organization. For processes that still need to have handwritten or printed out documents, document understanding could be fine. I really hope, however, that they shift to AI, which is what RPA lacks. RPA lacks Autonomous Automation, that's something that everyone is waiting for. We’d like to have a robot that's actually using the computer with its own mind, not just the workflow we give it.

For end-to-end scenarios, UiPath is still growing. I'm not saying that UiPath isn’t good. There is a lot of potential. They're using UiPath Actions or Apps, for example. Dashboards ensure that end users can interact in a new way with robots or with the whole end-to-end automation. RPA is a technology that hasn't maxed out yet.

Someday, there will be no legacy software or very intelligent processes that will use APIs. It’s my understanding that UiPath bought some company that specializes in API Automation. For end-to-end automation, UiPath needs to integrate all those components, rather than task automation to process automation, real process automation. With RPA, if you read the HFS report, you see that the process version is actually not a process. It's tasks. Perhaps in their next LTS release, UiPath will actually gain to that point.

There are minor bugs. Every major software has bugs. That said, all are solvable, all are resolvable, and it's not a very bad thing.

Mostly, licensing must be improved somehow. Licensing is very expensive. Even in many industrial countries such as the USA or UK, UiPath is still very expensive. For example, Microsoft now owns its own RPA, Power Automate, and the pricing is much more reasonable than UiPath. UiPath licensing is very vague and expensive. There are some ways that they can reduce the cost to make everyone benefit from an RPA.

UiPath needs a lot of maintenance. Every RPA vendor, every RPA on-premise software, needs a lot of maintenance. The cloud version has reduced that, as far as I know. It’s resolved the maintenance issue so that users can focus more on other things. Every new feature will be first on the cloud version and eventually, we can benefit from that.

We use document understanding. For English documents, it helps, however, for Persian documents, due to the fact that the models, the Machine Learning models, that are pre-built, are based on English or other common languages. If we want to actually use Persian, we need to use AI Fabric and build our own models. It's now out of our budget to do something like that here.

It's almost been three years since I first started using UiPath.

I don't like the stability very much as it has minor bugs.

You see that processes break without any reason. When you check the system, check every log, even view robot logs or logs in the network level and you see that it has, it's only then that you realize the issue was a bug from the UiPath platform. Once that happens, you must go to the community and explain the situation to each other. The good thing is, there is a community right there and you can learn from each other. 

Scalability is great. UiPath has many capabilities. Anyone, via a simple search, can go through UiPath and even try the enterprise version and just see for themselves that there are many, many, many capabilities. You can use .NET and there are many NuGet packages that you can use or you can even design your own custom package. There are many great platforms, such as Insights, Action Center, UiPath platforms, and so many different types of robots.

In terms of technical support, I do not have the opportunity to speak with them, as we are in Iran, and, due to sanctions, we do not have a direct opportunity to speak directly to UiPath's support. Therefore, I cannot have an opinion on their services.

I'm familiar with other RPA solutions such as Automation Anywhere and Blue Prism.  

I saw a lot of people that are going to RPA. I put myself in their shoes. However, from my perspective, UiPath has a great community. The UiPath forum is very good compared to Automation Anywhere and Blue Prism. Every technology can be learned, sooner or later. That said, the first thing that any kind of technological software needs to have is a good community to facilitate that learning. Without community, you cannot spread the word, you cannot spread the knowledge. It's the first thing that UiPath has over both of these other solutions. 

And the second thing is, as a technological matter, UiPath is much better. The other two lack the connection, lack the integration. The user interfaces of both Automation Anywhere and Blue Prism are terrible. I do not like them. They're not very intuitive and they are not easy to learn. UiPath is using Workflow Hosting Foundation from Microsoft and great integrations with .NET, which is so much better than the other ways that other vendors are approaching things.

I'm typically involved in the setup. I'm involved in every phase of the process. 

The setup is straightforward. They're using .NET Core now and before that, they were using ASP.NET's Standard Framework. The company has relied on default application configuration as far as, for example, in web.config or .JSONs. Most configuration must be done in the UI itself. I don't really like to just manipulate files at the system level just to do something. I believe that's the way now, however, that can be improved. It could be just in the UI and the certainty would be much better.

The length of time it takes to set up a robot deployment depends on the project itself, however, for a small project, it can be in one month to 45 days.

The initial deployment of UiPath is not more than three days.

Setting up UiPath doesn't have any standard process. There's just documentation. We are always using its documentation.

We do not have any relationship with UiPath directly. We are just a contractor doing RPA for foreign companies that are based in Iran.

Iran has sanctions against it, and there are a few companies that are local branches of foreign companies, and those that have licenses from UiPath all use on-premise deployments. We're always using the latest versions of the solution. Right now, we are on version 19 and it's in the 2010 LTS.

I didn't have the opportunity to use UiPath Cloud. I'm in Iran and I don’t have access. There are some capabilities that are still in the cloud version, like Apps.

While it depends on the project requirements, much of our work is on attended automation. I see attended automation as a gateway to an RPA solution as users are very busy and we cannot just pop-up in some programs, random programs, and stuff so they end up having to wait. I do not believe that attended automation helps users as much as an unattended version can help. This is due to the fact that at some point, someone still has to be involved in the process.

RPA is a new technology and a new shift that there's no good book on how to manage. Maybe there are some, however, they can be obsolete rather quickly, as the technology is changing and with every new version. That's why hands-on experience is the best way to learn. Even for UiPath, without any practice, without any hands-on experience, and without any good community, you cannot do anything.

If someone wants to learn UiPath, first they must sign up within the community and then go to UiPath Academy. Start there. Practice. Get in touch with people in the community, and then create a small use case and do some hands-on work. Practice is very crucial in RPA. Don't forget to review official documentation as well, as it will save you lots of time. 

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

One of the use cases that I have recently completed is related to SAP and the interaction with Excel and our internal application. We are going with the JD Edwards EnterpriseOne ERP application and we used UiPath to help in this area, and were able to do so within a few days.

Some of our people are going for process automation and some are doing desktop automation.

It helps our developers learn and implement things faster.

Also, the UI Targets feature has helped us with some difficult situations. We were using other solutions for these situations but our company has moved away from them to using UiPath, and it's working very well. 

UiPath provides lots of integration to our ERP application and lots of new updates are coming out day by day. It helps us to automate our tasks.

We are using the solution's selector technology for UI automation. That is the most important feature for us. For example, one of the applications in our company is being updated day by day, by the development team. We use selector to make it dynamic.

We also use the latest version of the desktop Assistant tool for some queueing activity in UiPath Orchestrator. The tasks in the queue are continually updated and then they are run by robots. Using Assistant, we get a lot of information about our queues, like if something fails, for example. Also if a robot fails we get robot status-type information from the Assistant. The Assistant plays a good role because, if a process is going wrong, we have control. Using the Assistant we can stop that process. It is a most important feature from UiPath.

An area which the UiPath team is rapidly working on is machine learning and artificial intelligence. At the moment, it is a little difficult to understand. If they could add some more training on it in their Academy, it would help customers to learn about these features.

I have been using UiPath for the last eight months.

We only use the stable versions, regardless of whatever they are releasing, to avoid bugs and errors. In the stable versions, we have never found any issues or any bugs. If there is any issue, we have a team that will contact the UiPath team and we will get quick solutions. But so far, we have never had any problem or issues with a stable version of UiPath.

We use the Assistant to handle all the robots' actions. We are scaling and tracking it. That is very important for us. The scalability features of UiPath are awesome.

In the eight months I have been working with UiPath I have implemented seven or eight projects. Day by day we are increasing our usage of it, and UiPath is also increasing the product's features and adding technologies. That enables us to work on more projects, as it is easy to integrate.

We have been able to implement a lot of little projects. That is one of the reasons that it is cost-effective. In addition to the affordable price, it just takes a few days to develop solutions for these projects.

In India, a developer costs about 16,000 rupees per day. Using UiPath, all our projects have been done in 30 days. If we tried to do these little projects in another technology, they would be more costly because they would be more time-consuming.

Our company is based on automation. UiPath is the correct solution for this. It is cost-effective and has an affordable price.

UiPath is not the only technology we are using, but we are migrating to UiPath because it is cost-effective. The previous solution was Blue Prism, but for the little projects, it was not the right solution.

In addition, the Control Room is really required for other technologies, like Blue Prism, but there is no need for it with UiPath, because we manage and deploy it with our team only. We don't need to worry about the Control Room.

For the beginner the UiPath Academy has a lot of training available. It's important to go through the training. After the training you can easily work on any project in UiPath. So first of all, follow the training. For intermediate-level users, UiPath is the correct solution. These users just need to keep up to date, day by day, because the UiPath team is rapidly updating the features.

The Picture in Picture functionality for attended automations is a new feature. Up until now we have not used PiP, but we have some use cases for an internal project we are doing and are looking into it for the future.

We are using UiPath Automation Cloud, but we have not yet migrated our on-premises UiPath instance to it. We are thinking about the on-premise because it fully depends on our own enterprise. If we go to the cloud, we will be able to collaborate better with our team and what others, because it is "public."

My primary use case of this solution was to automate BMC Remedy and SAP use cases. I used UiPath to automate various tasks in SAP. I developed several bots in client virtual machines using UiPath and then connected the virtual machine to the UiPath Orchestrator. Once connected, I scheduled the Bot.

The manual effort of employees for repetitive tasks has been tremendously reduced and thereby the employees are concentrating on different fields. Furthermore, human error is completely wiped out because of the Bots. The tasks that used to take a lot of time to get finished by humans are now accomplished in a short span of time by the Bots.

I found the Library option as most valuable because first, we can avoid the development of the same task again by developing and publishing a task as an activity into the Orchestrator, and second, in case of any changes required, the developer can make the required changes and republish in the Orchestrator with the new version. At this point, others can download that task as an activity and can use it with their Bots.

Apart from the library, I like the API activities and the activities which we can call Python scripts from.

The area that must improve is while releasing a new version, it must be capable of running the bots developed in the older version.

It would be nice if we can develop an intelligent bot that can make the right decisions.

Please include the option to select the time zone while scheduling the Bot in orchestrator.

I have been using UiPath for the past one and a half years.

We use only unattended robots with Studio and Orchestrator. Our primary use for the bots is in finance, so we only do finance use cases like AP (Accounts Payable) invoice retrieval.

The solution has improved the way our organization functions because no one has to sit for hours just spending time retrieving documents. The staff just picks up the documents they need in the morning, start their analysis right away.

What I find the most valuable about UiPath is flexibility in adding code. That ability is the most important feature for me and what I do.

In the next release of this solution, I would like to see better scheduling options. Because of the schedule limitations, you can only schedule one process at a time. There are situations where I might want to build five processes that need to work together. As I can only schedule one at a time, it isn't currently possible.

On a scale of one to five where one is unstable and five is very stable, I would rate the stability of the UiPath platform as a five. There are not many issues at all. On other platforms that we use, we always seem to encounter small things that cause problems. For example, with other solutions, we have had problems processing things like resolution and there is always an issue. But with UiPath, I can control almost everything from the robot and get it working.

There are ten people in our organization involved in our automation program and I think it can be scaled at any time.

While we don't use technical support directly, our team has used UiPath Academy RPA training to become more familiar with the product. On a scale from one to five where one is the least beneficial and five is the best, I would rate the Academy experience as a five. We've also used the forum. In all, between the implementation help, the Academy and the resources, I would rate the support as a nine-out-of-ten.

From the time we purchased the UiPath license until we had our first robot in production took only about one month, and that was without previous experience with the product. The initial set up of the product was straightforward, so it was all pretty efficient.

We did not need to use an integrator, reseller, or consultant. We did the entire implementation all in house. The only exception is that we did get some help from UiPath by working with them directly. 

We have experienced some return on investment and performance benefits, and it only took about one month to see it. There is one monthly process we use and in just one run — the first time we ran it — something that took two people two days was done in two hours. So, what took 16 hours to do analysis on before has been cut down to two hours. It is hard to say how much money that saved as we just changed the allocation of resources. The solution also helped to eliminate human errors which are even harder to account for.

We chose to try UiPath because we wanted to test the SQL capabilities that it has. I don't know that I would say we evaluated other options before choosing it as a solution. We currently work with both Blue Prism and UiPath at the same time. 

On a scale from one to five where one is very difficult and five is easy, I would rate the ease of use of the platform as a seven. I think that especially business users who don't have more of a technical background can get lost in all the different features that are available.

For this solution, we could totally deploy with attended robots, but our business just isn't ready for that yet. I think, with the adoption of Studio X that we might be in that position, but not right now.

On a scale from one to ten where one is the worst and ten is the best, I would rate this product as a seven overall. The scheduling feature just isn't there yet to allow more flexibility in programming and use, but the development is much faster and the flexibility better than much of the competition. The introduction of open-source changes the game for RPA solutions.

The advice I would give to a colleague at another company who is researching this solution or a similar one would be to clearly evaluate the use case. Don't just breeze through and assume you need automation. Take a good look at what you actually need to do, make sure the solution fits, and make sure the targeted processes are processes that should be automated.

We use unattended robots and the Orchestrator module. I am most familiar with the Orchestrator. We are very new to this solution and just getting into it.

We are a financial insurance company and we do VoW, Verify on Web. We have a bunch of different insurance carriers.

We run automations in a virtual environment, VMware, and I haven't seen any problems with it.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a five. For my part of it, this solution seems very useful. I have limited exposure to it because I do more of the installation, the configs, etc. I don't really work with the workloads, although I see what is being worked with. We have our in-house developers who are doing the integration into our in-house programs, so I watch what they do and it just seems that it's very easy to pick up on.

I have not used the UiPath Academy, although I think that the developers have. I did not get any feedback from them about it.

I was not involved at the time, but I think that from the point that we purchased our UiPath license until we had our first robot was approximately three to four months.

In terms of eliminating human errors, I would say that we have a twenty-five percent reduction in the number of them. However, it is hard for me to say because I'm not that clear with it prior to the incorporation of the robots.

With respect to saving time, because of the commitment to the development and the installation and the bringing things onboard, at this point, we have not saved time. In daily operations, we do save time. I would say that we save between twenty and forty hours a day.

Our organization has improved because of the time savings. We've got robots now taking ten seconds to do what people were taking four to six minutes to do. It's a whole department of people that are now free to do other things.

I like Orchestrator and how easy it is to manipulate and get your data, to see what's going on. My job is to make sure that the system is running, so it's very easy to go to the Orchestrator through the dashboards. If it's not running, you'll see through the logs what's not running and what has caused the problem. At that point, normally, I escalate it to whoever needs to work on it.

The company likes this solution because of scalability.

One of the things we're struggling with it how to project how many robots we need to do these processes, so better documentation or assistance in this regard would be useful.

With respect to the stability, on a scale of one to five, I would rate this solution a four. I cannot give it five, yet, because I have just not had enough exposure to it.

We have about twelve people working with this solution, from developers to the business side to the IT side.

The idea of RPA was brought back down to me from our VP of IT, but I'm not sure where he got it from.

We have already seen a workload that has been moved off of our employees. It was within the first two months of the bot being developed. It is not my place to say the amount, but I can say that it is substantial and six digits. 

From a cost perspective, the unattended bots are going to be a major saving for us. We have a lot of mundane, routine tasks that need to be done. I have not done very much with the attended bots, so I'm not sure how we might benefit from using them.

My advice to anybody who is implementing this solution is that knowing what it is you want to automate is the most important thing. We were kind of blind walking in on that. We had one process we looked at and now it's throughout our company. People have all kinds of ideas about what we can do with automation.

I would rate this solution an eight out of ten.