IT Central Station is now PeerSpot: Here's why
Fatih Arpas - PeerSpot reviewer
IT Director at GarantiBank
Real User
Saves us development time, good documentation, integrates well with Elasticsearch
Pros and Cons
  • "UiPath integrates well with Elasticsearch, which is a great search engine."
  • "The logging capability that comes with Orchestrator does not allow you to create smart reports."

What is our primary use case?

We are using the on-premises UiPath solution for both attended and unattended bots. At this time, we use unattended bots primarily to facilitate integration between applications, and we are not using the attended bot capabilities. Generally speaking, we develop integrations for our core banking system, which was written in-house and running on a mainframe. It is a highly-developed system that we started using more than 30 years ago. When it was created, we didn't have the integration capabilities that exist in other applications or core systems, today. This means that in order to have external applications communicate with the core system, we need to develop integrations. Examples of this might be web services or other APIs, and that's why it takes time to do. We have teams to do the integration, but considering that the core banking system is in Turkey and all of our teams are busy, we don't have enough resources to implement all of our integration projects. Now, for the past three years, we have been implementing bots to handle integration by moving data from the applications to the core system, and from the core system to the applications.

How has it helped my organization?

The biggest benefit for us is time savings in terms of developing satellite applications for the core banking system. We are developing the robotic API, and we are integrating our internal front-end applications with the core system. Using this approach, we can easily get and set data from the core system, and we can see the results for each transition. We can learn about what happens in the core system with the help of the bots. The amount of time that we save depends on the use case. For example, if we implement integration between core banking and the applications instead of native integration through development, it saves a lot of time. I prefer native integration versus using the bots but sometimes, you don't have this opportunity because it will take too long to put into production. Other times, you can't justify undergoing a large development process for just a small integration, so it's enough to solve the problem using the bots. There is another use case where our operations teams perform repetitive tasks using the bots. For example, when performing the task manually, users have to take the data from one screen and enter it on another screen. We have never tried to calculate how much time we are saving in cases like this, although I'm sure that we are saving a lot of time. People in the organization have been asking for more projects to be automated because it is easier for them. When their tasks are automated, they are more relaxed and can focus on other more important tasks, as opposed to the repetitive ones. Getting away from repetitive tasks puts you in a position where you can make more decisions and be part of the smart part of the business. This leaves the easier, repetitive tasks for the robots.

What is most valuable?

There are a lot of really useful features in UiPath including the Orchestrator and the Studio. The Orchestrator is one of the main tools that I use because I like to help orchestrate the bots. It is the heart of the tool and it gives me a lot of flexibility to automate or manage bots that are in the field. The Orchestration Server is one of the most important features and when you perform a deep dive, you see that it has a lot of functionality. It's great. The Orchestrator has other features such as computer vision, AI, and machine learning, and it complements the bots and the Studio. UiPath integrates well with Elasticsearch, which is a great search engine. ElasticSearch is more capable than UiPath for searching logs. I'm filling the gap in log reporting using ElasticSearch, where I'm feeding the logs into it and then creating dashboards, or using the analytics parts of ElasticSearch and Kibana. The UiPath Academy is a very valuable component of this solution. Many of our employees have used the courses. With it, a person who has a little bit of an analytical mindset can easily learn to do many things. If somebody is willing to develop themselves in RPA, the UiPath academy is more than enough to do so. They will understand the components that make up the ecosystem. The academy is very good, well constructed, and has a lot of labs and exercises to help one learn the system by themself without any help, and very easily.

What needs improvement?

The logging capability that comes with Orchestrator does not allow you to create smart reports. You have the logs from the bots and what's happening on the machines because you get all of this information from the logs. However, UiPath is more capable when it comes to collecting information about your processes, time saved, or process execution. They have some smart report dashboards. The installation and initial setup is difficult for non-technical organizations.
Buyer's Guide
UiPath
June 2022
Learn what your peers think about UiPath. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
610,336 professionals have used our research since 2012.

For how long have I used the solution?

We have been using UiPath for more than three years.

What do I think about the stability of the solution?

Stability is something that we should consider in two parts. The first concerns the bots and how they are running the tasks on the machines. This comes down to what kind of developers we have because if you are developing properly, and implementing all of the exceptional cases that may occur during the execution of the process, it's very good. I haven't had any issues in cases like this. The second part is the Orchestrator, and I haven't had issues with this either. In the more than three years that we have been using this environment, including the time in production and our test environments, we have never had an issue. We have had two or three incidents because we didn't have enough space left on the database storage, but that was not related to UiPath. Rather, it is related to the infrastructure. Another time, the SSL certification expired so we had to renew it. Otherwise, stability-wise, we haven't had any problems.

What do I think about the scalability of the solution?

Scalability is very good, although we have not reached a point where we needed to scale the infrastructure. The high availability and scalability are two of the main features in the UiPath environment but we have not needed to go in that direction yet. At this time, we only have five bots in the organization and that is enough. We are not planning to increase the numbers at this point because the number of bots that we have can be managed on a single node. We don't have clusters or multiple bots because of the criticality of our processes, but these are things that you can add and set up to share the workloads. Although we don't use it, I think that it looks really promising. In our team, we have a business analyst and developers. Some of the roles for the developers are varied. At most, we have three people on a project who are working with UiPath.

How are customer service and support?

The technical support for UiPath is good. When we first started contacting them between two and three years ago, the support for everybody was the same. However, they're now offering different tiers of support that require a different license and cost. There is one basic technical support, where all customers have the right to open tickets and try to solve the problems. Then, there are different support levels where you can pay extra and you can get more assistance for solving your problems. Up to this point, all of the problems that I have had are mostly related to upgrades and installations, and they have only been from time to time. So far, I have been able to solve problems with basic technical support. Some of the problems I have solved on my own, whereas with others, I have needed a small bit of help from technical support. I can say at this point that the support is good, although really, I haven't had any major problems that necessitated a lot of support.

Which solution did I use previously and why did I switch?

We have used other RPA solutions in the past, but not to the same scale as UiPath.

How was the initial setup?

The initial setup is not very complex, but it depends on the profile and experience of the person who is using it. Considering we had a great deal of deep experience in the project implementation and also the technologies, we are familiar with everything. This includes tasks like installation of the infrastructure, configuring the databases, configuring the virtual machines, and installing the robots' features. For less technical organizations or people, it will be difficult to implement the UiPath infrastructure. In that case, they will need the help of partners. It's not so easy, but it's well documented. In fact, one of the good things about UiPath is that everything is very well documented. The deployment takes no more than two or three weeks. Our implementation strategy started with developing bots using the trial license. We found the bot implementation was very easy. The trial includes everything that you need to develop workflows and the bots that run on the machines. When you get to the point where you need to run multiple bots in production, you need the Orchestration server. We did not install Orchestrator until between four and six months after we started with the trial. In the beginning, we were testing UiPath and creating some small projects. These were very easy to implement. After that is when we decided to buy the license and move the bots to production. In terms of maintenance, it is not critical for the bots. It's the Orchestrator that has to be maintained and kept up to date. Every year, you need to upgrade your infrastructure with the latest release, so there is some annual maintenance. If it is on-premises then you also have to maintain the hardware that everything is running on. Of course, there should be somebody responsible for taking care of the databases and general system maintenance. The operating system, for example, should be maintained by someone. All of these things are layers and sublayers on top of the solution. If instead, you implement the cloud version of UiPath, then you can get rid of all of the maintenance. In that case, you have only the bots and the Orchestrator, which are hosted on the UiPath cloud, and you don't have to worry about anything. UiPath does the upgrades and performs all of the maintenance, which is nice. In the future, we may go in this direction. However, at this time, maintaining the infrastructure in our organization is easy and not a burden for us.

What's my experience with pricing, setup cost, and licensing?

I can't say that UiPath is expensive but I can't say that it's cheap. The cost that we are allocating for RPA doesn't burden us too heavily, so what we are paying is acceptable compared to the gains that we have in the organization. That said, it is relative because it depends on the size of the organization, the budget, and other factors. From our point of view, considering our budget, it is okay but for another organization, it might be expensive. There are some features, such as UiPath Insights, that require you to purchase an additional license. The logging capabilities are also a feature that you need to pay extra for.

Which other solutions did I evaluate?

While we were searching for solutions, we read the documentation for UiPath. We found out that UiPath was originally started as a Romanian company, where we are, so we figured that we would try it since this is where it was first implemented. Our tests showed that UiPath was very promising but we kept investigating other solutions. We tried Blue Prism and we tried Automation Anywhere, which are both RPA tools. We also did some studying, looked at the Gartner report, and did some further analysis. Ultimately, we decided to buy the licenses from UiPath because it was solving all of our problems.

What other advice do I have?

When you use this system, you are using features from several different modules. It's something like an ecosystem where you have the bots, Studio, and the Orchestrator. If you are not using all of them at the same time then something is missing. They complete each other. If, for example, you don't have the Orchestrator and are only running the bots then it is a different kind of automation. In the past, as I was using UiPath, I found that there were additional features that I wanted, but regularly and with each product update, they were bringing in new functionalities. At this time, I don't have a project that is waiting and cannot be implemented due to missing features. All of the tools that they deliver, for the time being, together are enough to implement any type of project. We are not yet using the AI functionality because to this point, although that is because we don't yet have a proper project for it. At the same time, the AI and machine learning functionality are very important to us because we are planning to use them. We have not used the UiPath Apps feature because it is one of the new features that has come out lately, and we haven't had the time to gain a deep understanding of these technologies. We have some rough ideas about how we can use this feature, but for the time being, we do not have a project that needs to be solved with UiPath Apps. My advice for anybody who is implementing UiPath is to start with studying the processes and trying to determine whether they are good candidates for RPA. In order to automate a process, you need structured data such that the inputs and outputs are somewhat predictable. Once you know what it is that you want to automate, you have to understand the capacity, and then if you have any candidate processes, you can begin developing. UiPath is the RPA solution that I recommend. However, it is important to know, before purchasing a solution, which of the processes are good candidates for automation. I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
User at a healthcare company with 1,001-5,000 employees
Real User
Frees employee time, reduces human error, and offers great training
Pros and Cons
  • "The product has freed up employee time - and it's not just the employee time. We do have some triggers that run. Some jobs are run that people use to manually do at night and weekends. We also don't have to hire additional people just to learn 80 different types of things in a claim and identify correctness manually. The robots will go through and then they can identify if there are specific things that are wrong. That part will go to our experts and they'll review those exact issues."
  • "I'm a developer and I'll move things around and they'll change order, or I'll try to save something and it won't save the first time. I'll have to open something twice, open something three times. I've got a list. I'm working out quirks with UiPath."

What is our primary use case?

Since we are a healthcare organization with HIPAA rules, we're on-prem. Our use cases boil down to claims testing and membership testing. It'd be institutional professional dental claims and making sure our membership is loaded correctly.

How has it helped my organization?

We have to configure our software to pay claims and pay providers. What we're realizing is that, the more claims that we can run through the system, the more accurate we can get, the faster the payment on the claims, and the faster the payment to our providers.

What is most valuable?

The only features we're actually using are the orchestrator and 32 unattended bots.

The value of that is the power to be able to run our thousands and thousands of claims and membership to make sure that everything looks correct.

The solution has saved costs for our organization. I know it's over a million, however, I haven't done the exact numbers.

UiPath has reduced human error. We’re finding out that what we've built for configuration in the past, we're finding mistakes that we did a year ago. Now, the bots are proving that and we've been able to correct those past mistakes. This way, we don't have inaccurate payments or recaptures.

The product has freed up employee time - and it's not just the employee time. We do have some triggers that run. Some jobs are run that people use to manually do at night and weekends. We also don't have to hire additional people just to learn 80 different types of things in a claim and identify correctness manually. The robots will go through and then they can identify if there are specific things that are wrong. That part will go to our experts and they'll review those exact issues.

This use of bots allows for employees to do higher-value work. We also have been able to up-skill some of those people to sometimes a leadership role or a different role they would normally never get due to the fact that they were always manually looking at the claims and membership. This has definitely affected their level of satisfaction at work.

I don't know if we have an accurate estimate of how much time we are saving. I just know we do volume and we do thousands and thousands of claims a day, and therefore, it really helps.

We use UiPath’s Academy. That's how we learned the system. We actually learned it in six weeks and then started the development after that. It's very powerful and I continue to use it today.

It’s helped employees get up to speed with the product. This is especially useful when we get newer versions or we onboard other people. That's part of our syllabus. The first thing a new user has to do is go to the Academy and take some of the classes that we recommend. Then we identify, “okay, did you like it? Is this for you? Is it not for you?” et cetera. It’s a quick win where we don't have to take our time as we've got other work that we have to get completed. It acts as a filtering system for us. Both us and the employee can see if it’s a good fit very quickly. We can find out at an early stage instead of a year later.

The biggest value of the Academy is just knowing that we can do so much more volume and get in some more accurately without human error, or having people working nights and weekends. That has always been a really big push and we've been able to slowly work away from that.

Obviously, we’re not in a perfect world yet, however, getting rid of the manual aspect has been great. People just get burnt out. You can only look at things manually for so many hours. If you've been doing this for 10 years, it's got to be frustrating for those people who are always afraid they’ll get their job taken away. At the same time, for them, it’s so much easier as they don’t have to look at 80 things. They can look at five things that failed and then enjoy time with family and have a work-life balance. That’s big.

What needs improvement?

We've coded up to like 80% of what's possible. We really cut our pain points and said "this gives us our value, our bang for our buck." What we're doing now is saying, "okay, well, how do we improve it?" We've got another area or we've got another part of the software that we use our application that UiPath interacts with. Right now, our main concern is what else we can do to make it even more accurate or get more information or test more information to make it a solid pro program.

I'm a developer and I'll move things around and they'll change order, or I'll try to save something and it won't save the first time. I'll have to open something twice, open something three times. I've got a list. I'm working out quirks with UiPath. There are just UX things where if I copy this and put it here, it should look the same as it was, and I don't know why it doesn't. It could be my machine. It could be my local machine and it might just be that conversation with the premium plus to say, "why is this doing this?" Or maybe there could just be a setting, where we didn't check that box when we set it up. 

For how long have I used the solution?

I've used the solution for two years. 

What do I think about the stability of the solution?

We actually had to spend about four months of maintenance to make sure that we got the solution to how we wanted it. We brought in a contracting firm and they didn't know the company and they just kind of said, "here's what bots can do." 

What we did is we did an assessment program for two months. During those two months, we looked at what they built, which was great. This got us up and running and showed us what's possible. 

Then, we took those two months to identify, for example, if the database maybe should have been set up a little better to interact with our other databases. Or if the coding should have had different paths of risk that they didn't know about. If you don't know the business, you don't know the risks, and therefore, you don't know how to set it up. That's why we did all of that assessment and then we spent four months fixing it to adjust to what we thought was a better path or a more stable path in order to support the robots.

What do I think about the scalability of the solution?

The scalability potential is astronomical. We've got so many areas in the company, including finance and pharmacy, and there are all kinds of different areas and authorizations that you can actually go down and say, okay, now we have time. Let's put it on our calendar. 

The next piece we're looking into is the citizen developer angle. We know that has some power potential, however, we have to have regulations and audits. We want to be careful if we do start moving in that direction to really understand if it is right for the company and is helping people versus if we build something wrong what that would mean to manually have to correct that. That's time nobody has.

How are customer service and support?

Technical support has been great. We usually get answers within hours of a request. I thought we were on the premium support plan and now we're going to go to the premium plus, I believe they call it. That starts up here for us in November.

We've had some challenging solutions where it has taken us several weeks to work through it. They tell us "here's what we recommended". That said, we know our system. It's just like any other contracting firm. They don't know your system and your solutions, however, they give you the recommendations. At this point, we've been able to work through everything that we've had technical issues with. We decide to do some of them a different way. Technical support has been supportive of this approach. It's like a partnership, and that really makes a big difference.

Which solution did I use previously and why did I switch?

We started with Rational Robot in 2005. I actually developed that. I've been with the company for over 20 years. I started with Rational Robot and then we moved to some C Sharp and some coded UI.

We tried Test Architect for a little while. We've used different RPA methodologies and UiPath seemed to fit a little better with where we are and the robustness we wanted.

We switched when we moved over to new healthcare software. The old one was just COBOL and green screens, and it was hard to automate it. We did, however, it was very difficult. When we moved to this new application, we needed to make everything more quality controlled, and the only way to do that was with the robots.

How was the initial setup?

I was not a part of the implementation process. 

The deployment process took about eight or nine months via our vendor. 

What about the implementation team?

We brought on some contractors to do our initial setup, including a proof of concept, and they built part of the system and after that, we took it over. They were what we called a vendor tracking firm.

What was our ROI?

We have definitely seen an ROI.

The biggest ROI was in the configuration. We're realizing we may be setting some things up wrong and that's not how the customer should have been set up. When we see things fail, we ask why is this failing? And then we go upstream and find out that we didn't even build a specific thing and realize that it was a mistake, a key entry, a mistype, et cetera, and the bots catch that on the backend.

We're able to do that quicker. It's manual labor and it's tedious. Now, manual labor's fine if you want to go in and manually check this, that, and the other thing, however, when that's your day job and you're checking the same 80 fields compared to a spreadsheet over and over, it's just got to be frustrating and employees feel it. You hear it on the call.

With UiPath, we can ask the question "what can we do to support you?" We're not going to replace people; we want to get them to a better place. Our employees understand that. It took them a while, however, they do understand that now and think the solution is really cool and are thankful for the support. It's a tool, not a human being's replacement. 

What's my experience with pricing, setup cost, and licensing?

I don't write the checks. I don't know what the actual cost is. That's always on leadership. My understanding is it's a reasonable price for the value that we're getting out of it.

Which other solutions did I evaluate?

We did look at the Power Automate desktop. It doesn't have the orchestrator to control things, and it has some other limits. When we do formulas and try to validate what the value should be, they are very difficult or impossible to set up on the Power Automate. At some point in time, I'm sure we'll be able to do that. In today's world, what we need right now is UiPath.

What other advice do I have?

We're just a customer and an end-user.

We do not use the solution’s AI functionality in our automation program. We just do some checks and then just make sure via verification that everything matches in the configuration to the actual claims from the inbound files to the outbound.

There's an automation hub, test, capture, process, mining, all of these other features we haven't been able to purchase yet, due to the fact that we want to make sure that our bread and butter, the claims of membership, is solid. Once we have that in a good place, which we're hoping will be in 2022, we've already talked to our sales rep about the next steps. They've talked about the other features and offered recommendations. We'll go down that path next year and it'll be really exciting to see what else we can do to bring on the other areas of the company.

I'd advise potential new users that they definitely want to do some kind of proof of concept against other systems. I have heard other companies here that have said, okay, we're going up against four other automation tools. That's great. However, do your homework. You need to go and present everything to your leadership and showcase the solutions. 

As we get some of the demos of software, we can kind of compare them to what our system's needs are. A new user can say, well, maybe these are our top two. When you get to your top two, that's your time to bring somebody in, an expert to discuss what you're trying to do.  

If you do choose to go with UiPath, that UiPath academy is so valuable. That's a big asset. If you do the premium plus care, they will support you through and help you get things set up and running or make it better. We've been up and running for two years. Their goal and my goal is to see how to make things better to continuously improve the system and make everyone happy.

I'd rate the solution at a nine out of ten. There are just a few system quirks I'm trying to work through. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Buyer's Guide
UiPath
June 2022
Learn what your peers think about UiPath. Get advice and tips from experienced pros sharing their opinions. Updated: June 2022.
610,336 professionals have used our research since 2012.
Sumesh Velu - PeerSpot reviewer
RPA Specialist at a comms service provider with 10,001+ employees
Real User
Top 20
Great AI for business functions, reduces human errors, and makes it easy to deal with legacy applications
Pros and Cons
  • "The two reasons that we went with UiPath were, one, the learning curve, and, two, the community edition of UiPath, which had everything we needed to dig into the solution. Whereas with the other companies, there wasn't that option. With Blue Prism, for example, we had to buy a license in order to check whether the tool was going to work for us."
  • "There are a lot of cloud solutions that we already use in our organization. However, with UiPath, we have stayed on-prem out of concern for security. We don't have clarity on if cloud solution is going to work securely."

What is our primary use case?

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

How has it helped my organization?

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

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

What is most valuable?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

What needs improvement?

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

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

For how long have I used the solution?

I've been using the solution for four years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

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

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

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

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

How are customer service and support?

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

Which solution did I use previously and why did I switch?

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

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

How was the initial setup?

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

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

What's my experience with pricing, setup cost, and licensing?

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

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

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

Which other solutions did I evaluate?

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

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

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

What other advice do I have?

We are customers and end-users.

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

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

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

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Vikram Modgil - PeerSpot reviewer
Founder at Pi Square
Real User
Good training, and easy to automate processes that can have immediate ROI
Pros and Cons
  • "I really like that I am able to tell the story, using Orchestrator, how humans work, how bots work, and how humans and bots work together."
  • "UiPath should offer an on-demand cloud-type model where you can get bots for five minutes, ten minutes, an hour, or whatever duration you need."

What is our primary use case?

We use attended and unattended bots, Orchestrator, and Studio for development.

We're seeing increasing adoption of Studio because more people see how easy and straightforward it is to use a lot of the features. It helps that UiPath training is free. Our entire team, including our salespeople, have gone through the training. It's free and it makes a big difference. For the salespeople, they're able to talk more intelligently about RPA.

On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In fact, I have taken a lot of ideas from their training to educate my customers about RPA. When it comes to RPA, a lot of it is education because some of them don't know exactly how automation can be done. I've told UiPath that I use their training in my presentation, and it is great.

We are working with a technology company called Rammer, Rammer.ai. What the Rammer software does is listen to conversations to learn the details of what is being discussed. A third-party system is used to transcribe the conversation into text, then Rammer will learn the details without much training. It knows the topics, it understands what is talked about the most, talked about the least, how much we are adhering to the script if it's a call center use case, or if it is a simple meeting use case then it knows who is assigned what tasks, it recognizes the follow-ups, and it knows the summary of the discussion. All of this is summarized in a nice, consumable manner. So now, when a bot knows all of this information, it goes into Orchestrator, logs all these activities that are picked up by unattended bots downstream, and they trigger all those processes back. So it's a massive consumption of all of those heavy use cases.

We have not yet run automations in a virtual environment, although we do have customers who are asking for it. We are not sure if we will need UiPath's help for this yet because we haven't tried 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. Really, it depends on how clearly we understand the requirements. So a lot of times we are able to find process gaps, which wasn't the case earlier before we started thinking about automation in this manner. I would say the ease of use is actually dependent on some of those factors as well.

Usually, starting is the biggest challenge for most people, and I think this is because it is in a trial environment and there is a lack of documentation, with multiple people doing one part of a small subset of a task. There are these challenges and then if none of them are documented, you need to figure out the process flow. From person one, where does it go? This can change when people can do multiple things.

It becomes a very complex web to understand and navigate through. We need to understand the task and how it should be performed. For developing the robot, it's very important to have the clarity upfront, otherwise, we cannot code them. That is the biggest challenge, I feel.

From the point that a UiPath license is purchased until the first bot is ready is almost immediate. This is because we usually start with a PoC on a small scale, just to see if automation with this approach makes sense. By the end of the PoC, we'll normally know exactly how many bots are needed. Sometimes it is on us, more than the customer when we cannot estimate every process that is outside of the departments and division that we work with because we just work at finance. For example, we can't just estimate what marketing would use, and so on. That will sometimes delay things.

What is most valuable?

The attended and unattended classification and simplicity are great, and it's easy to explain to people. Right off the bat, the task performing the lowest granular entity is very clearly defined, which is something that I like.

I really like that I am able to tell the story, using Orchestrator, how humans work, how bots work, and how humans and bots work together. Orchestrator really tells a lot more than just being a simple task manager.

What needs improvement?

In future releases of this solution, I would like to see more packaged solutions.

We would like to see intelligence built into the core. Specifically, we would like to see the recognition of human to human conversations. That intelligence would be great because we have some very important use cases in that space that we are seeing. Our focus is moving closer to one hundred percent in that space, as all of our new work is related to conversations.

UiPath should offer an on-demand cloud-type model where you can get bots for five minutes, ten minutes, an hour, or whatever duration you need.

What do I think about the stability of the solution?

With respect to the stability, on a scale from one to five, I would rate this solution a five.

We don't see many failures, and this is partly because of our approach. We start by creating something called a heat map, which I learned in some of the training from UiPath. The training clearly explains how to handle errors. It includes which process to automate fully and which processes should be automated partially, with a human in the loop.

We start with the right approach. We understand the process and we have the heat mapping that gives us full clarity of where the exception flows are and how to handle them. So when you do that, it becomes second nature to handle those exceptions. We are pretty comfortable, and we are applying the best practices, which adds to the stability. 

What do I think about the scalability of the solution?

Talking about our own people, we have roughly sixty-five who are either developers or architects. For our customers, the number is growing all the time. The requests for training and setting up workshops for them comes to us every week, basically from different customers. We don't know the extent of automation beyond the people we work with because there are other vendors like us who are also there, so we don't have the exact number but what is refreshing to see is that even VP level or senior-level employees are interested in learning. They ask us if we can hold a workshop for their entire team, whether they're doing the development of bots or not. Hopefully, that will increase the numbers, but right now I don't have an estimate on the total number of customers. I only know on our side.

How are customer service and technical support?

We have tremendous support from UiPath. We can say that from our perspective, we are very fortunate to be in the Pacific Northwest and that team is one of the best. It doesn't matter if we are big or small, they help everyone. So every time we have an issue or a challenge, whether it's engineering, presales, architecture, or development, we get all the support.

Which solution did I use previously and why did I switch?

Our customers usually don't know much about RPA, so one of our jobs is to educate them on it to get them interested. Gradually when they understand, it moves forward.

How was the initial setup?

In the majority of cases, the initial setup of this solution is simple to medium in terms of complexity. We are finding very few complex scenarios at the moment.

I think the overall architecture is simple. It is very clear and very straightforward. UiPath's product team is doing a great job in is creating a lot of very out of the box integrations and analytics, and that always helps. That is good, but I think if people are not trained yet and they think that it's easy, drag-and-drop, and simplistic, those folks struggle a lot.

We've seen that people think "Oh yeah, it's just some scripts and drag and drop so we can do this easily" and that misconception exists. We don't treat it as an easy scenario, so we gave it all the respect that proper Python code, a data science problem, or a highly complex situation deserves. When you approach it that way, it's at best at a medium complexity.

In general, we treat it right in the middle. It's not that straightforward, but the architecture is simple enough that the development complexity is medium. That's the simple and medium combination.

What was our ROI?

When it comes to ROI, for some scenarios it's immediate on the day you go to production. Doing the math, if it is automating thirty hours of work in a week, it is going to be the moment you turn on the switch.

Sometimes when the expectation is set at a different level, the KPIs are different. It may be that the customer is looking to have an "X million" dollar cost saving. It just depends on how you're defining the KPIs. So in those scenarios, obviously it'll build up to that saving.

A lot of people talk about the total cost of ownership as being a real saving or real value for products. So there are just all these different layers of complexity in that. I mean in theory it is immediate at the moment you turn on the switch, but then you need to consider the bigger picture, and it's not a straight answer. It'll be different.

What's my experience with pricing, setup cost, and licensing?

The most important tip that I would share with respect to the licensing is that you should not think of a bot as being able to do only one thing. You should always consider the downtime and utilize the bots properly. That's the way you can have exponential ROI from just that one simple investment.

Even though these bots don't really cost much, you still want to say there are resources like a dedicated machine that is there, there are electricity and all kinds of resources that also go into it. So the overall cost, we should look at that. If a bot is doing ten hours' worth of work in five minutes, there are twenty-three-plus hours work that the bot can actually do. So, think of orchestration.

Which other solutions did I evaluate?

Some of our customers have tried different solutions. There are some customers who have even tried a lot of competing products and they're not satisfied. They have a very low expectation from what automation should or could do. So for us, that's even harder in terms of educating them.

People who don't know anything about this kind of automation, sometimes it's a little bit simpler to just run them through an hour or two of our workshop, but people who already know about it may have set their mind in a certain manner. Sometimes for those customers, the customers with experience in other solutions, are usually a little bit more difficult to convince. They have doubts that have come about because of whatever they've been using, and they don't fully understand the capabilities because UiPath does things very differently from others.

So on both ends, education is a challenge.

What other advice do I have?

We are very excited about the new things that have been announced recently. There is the integration with AI, with AI fabric. There is Studio X, which has pre-built APIs with Microsoft Office and all the other Salesforce integrations that they've come up with. These are very exciting because that will increase adoption even more. People already understand unattended and attended automation, and now with Studio X being available so easily, and with analytics being part of its fabric, it's going in the right direction.

We have a very nice step-by-step flowchart that explains how to approach or what processes to automate first of all, and what are the chances of change or variations and all of that. While we are developing this, we at least are following the best practices from all the training that we received to ensure that we have taken that int consideration and we have not picked the process that is hard to automate, or which should not be automated. Then, it's more of a system change or any transformation that the customer should do first and then do automation. Basically, we should not do automation for the sake of it.

At my company, we don't work with any other RPAs. When it comes to customers choosing this solution, it should depend on the use case. If there is a strategic advance that they need to get and they need to really think of analytics and intelligent automation, UiPath makes a very compelling case. I think that it is important to choose your solution wisely and do it based on your use cases.

From a cost perspective, there is a big difference between the attended and unattended bots. One is twenty-five percent the cost of the other, which is a massive difference. Our customers use both, and we like this a lot because the way we utilize attended and unattended bots are the right way to do it. If you need to do multitasking and handle a lot of tasks, the choices vary.

Specifically from a pricing point of view, I think it is justified. When I first heard the price, and obviously I didn't ask about the duration or subscription levels, I thought it was a monthly price. Hearing that, I thought that it was cheap. Later, I was told that it was an annual fee. So for me, I understand that my customers can afford this price, and I am happy with that.

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Jacqui Muller - PeerSpot reviewer
Application Architect at Dimension Data
Video Review
Reseller
You know upfront what everything will cost
Pros and Cons
  • "UiPath has definitely assisted us in speeding up our digital transformation journey. We have been able to create a whole bunch of different components that we reuse throughout our solutions. This means that when we have great, new ideas that we want to implement into our solutions, we have now found ways to do it in such a way that we spend less time trying to implement the fixes or cool new enhancements and more time actually realizing the value. In doing so, we have also seen a reduction in cost and an increase in FTE savings."
  • "UiPath has a wide range of features that they have brought into their ecosystem. If I look at something quite specific that we would like to see going forward, that would be the integration between Data Service and Insights. It is great that we are able to visualize our return on investments using Insights. We can see a whole bunch of metrics and how our processes are performing. I think what would give us a lot more power is if we could link that to Data Service and actually pull through some custom information."

What is our primary use case?

Some of our use cases for UiPath range all the way from development to operational support through to business enablement. Our biggest focus internally is to enable a business to do what they do best. We generally provide solutions through the use of UiPath to cater for streams, e.g., Procure-to-Pay, Hire to Retire, and quote-to-cash.

We are using it to build solutions that can heal themselves. So, we make sure that our operational team is aware as soon as something fails with the processes that we have built. If one of the use cases or failures has already been listed, we note the fix and try to implement that. If that doesn't work, then we hand it off to a human to look at the task. 

In terms of some of the use cases that we have in the business, we do quite a lot of ERP automation. So, we work with SAP quite a lot. We also have a lot of back-end data that we need to bring in and process as well. So, we use our SQL databases to perform tasks, e.g., allocating payments to bank accounts in our ERP system.

Because our development team is rather small, we try to create as many reusable components and solutions on the UiPath platform to make our day-to-day jobs a lot easier.

How has it helped my organization?

What has helped us the most from UiPath is that they haven't just provided us with a toolset or range of products, but actually provided us with a framework and hyperautomation lifecycle that we could use as a guideline throughout our own journey in automation.

UiPath has definitely assisted us in speeding up our digital transformation journey. We have been able to create a whole bunch of different components that we reuse throughout our solutions. This means that when we have great, new ideas that we want to implement into our solutions, we have now found ways to do it in such a way that we spend less time trying to implement the fixes or cool new enhancements and more time actually realizing the value. In doing so, we have also seen a reduction in cost and an increase in FTE savings.

What is most valuable?

From a development point of view, one of the most important, useful features in the deck is definitely some of the offerings that UiPath has in terms of UiPath Studio. Having the components for the Object Repository and Data Service available make your solution reusable and decrease your development time so you can go to market more quickly for products that you are offering clients. That has been really useful in our landscape. 

UiPath has gone a very long way to make sure their tools are easy to use and the products that they have in their end-to-end hyper automation lifecycle are easy to learn and teachable to people that you work with.

What needs improvement?

UiPath has a wide range of features that they have brought into their ecosystem. If I look at something quite specific that we would like to see going forward, that would be the integration between Data Service and Insights. It is great that we are able to visualize our return on investments using Insights. We can see a whole bunch of metrics and how our processes are performing. I think what would give us a lot more power is if we could link that to Data Service and actually pull through some custom information.

For how long have I used the solution?

We have been using UiPath at the company internally for roughly just over five years. 

We have been a reseller of the UiPath product to our clients for roughly three years.

What do I think about the stability of the solution?

UiPath solutions are definitely very stable. It is very easy for us to build quality solutions and put them into production, then be able to trust the solution that we have put into production. For any automation center of excellence, that is quite important. You need to have a level of trust in your organization, inside of your environment and inside of your solutions. 

This also is attributed to the quality of our developers. We have strong, skilled developers. Without a product like UiPath, stability would not be such a great factor, especially if we had to go with a different approach or tool sets.

What do I think about the scalability of the solution?

We have had a lot of experience trying to scale our solutions. Because of our automation journey, when we started out, we created processes that were very specific to the problems that we were trying to solve. They were actually quite static. The processes that we developed were aimed at addressing a problem specifically. As time went on, we started changing our design-thinking approach and our approach to designing and developing solutions, in such a fashion that we now try to create our solutions to be more dynamic. 

Because of the life expectancy of automations, and specifically RPA, a lot of experts would say that you need to go back after 6,12, or 18 months to reevaluate your solution and see if it needs to be redeveloped. What we have seen in our landscape is that if we try to make our solutions more dynamic, and actually cater for more than what we set out to cater for, having to enhance our solution later on takes a lot less development time. So, scaling out the solution has become immensely useful and our way of work.

We have roughly about 100 people within our organization directly communicating with our UiPath environment, either through our robotic assistance or bots, right down to the granular level of developing solutions. Some of the roles include our developers, operational support, and business users.

How are customer service and support?

I would definitely say that the UiPath technical support is quite proficient. They help us quite quickly. Their responses always direct us to the answers that we are looking for. If they don't know the answer or can't assist us, they give us that feedback. They go ahead and find the answers or make the needed changes. They then come back to us and provide feedback. 

We have really enjoyed working with the UiPath team quite closely throughout our partnership. It has enabled our journey further. I would definitely rate them as 10 out of 10.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

If I look at some of the other technologies and tool stacks that we have used to do RPA or automation, the adoption rate is a lot less. This is because of the way that developers need to struggle in some cases to get through the learning and usage of these tools.

How was the initial setup?

I was not directly involved in the setup of the applications and ecosystem. From what I have been able to gather, we did have quite a lot of support from UiPath and the setup was quite straightforward. It took four hours maximum.

What was our ROI?

UiPath has definitely helped us realize some of our full-time equivalent savings (FTE savings) in regards to some of the reusable components that we have and have placed specifically in the business. With the offerings that UiPath has, we are able to easily see what our return on investment is, how we have structured and deployed our solutions, what we have deployed, how long it has been deployed, etc.

If we take a look at the last six months, we have about 105 processes that we have in production at the moment. If we single out a specific process that we have been working on and has been in production for quite a while, then measure that over the last six months, we can see that we have saved roughly about 380 hours on that process. Or, we have saved 380 FTE hours. That equates to roughly 77,000 rand. That has been quite a big savings. If you take the time saved across our 100-plus processes, we are looking at close to 2,100 hours that we have saved in the last six months. That has a financial value of between 500,000 and a million rand. 

UiPath definitely has reduced human error for us. Because a lot of our processes are quite focused within the financial space and we integrate it with our ERP systems, we have seen a reduction of human error come into play. We have also seen that the provisions made for human error have also been reduced.

What's my experience with pricing, setup cost, and licensing?

In the RPA industry at the moment and in automation in general, UiPath's pricing model is the most consistent. So, if you are looking at year-on-year growth and pricing, or even if you are comparing solutions, each vendor has their own take on how they are going to generate profits and expand their return on investment. By far, UiPath is the most consistent with their pricing. They make it quite clear what they set out to achieve with their pricing and product. That makes their product so much easier to design for, as you don't need to change your pricing and go back to clients every time that you introduce a new aspect into the solution.

If I did have any advice or extra information that I could give surrounding the UiPath product, one of its strengths is that you know upfront what everything will cost.

Which other solutions did I evaluate?

We found that UiPath Academy courses that they provide, as well as the help through the forum, have greatly enabled us to more easily use this platform. Compared to other vendors and other tool stacks, it is a lot easier to use as well. 

If I look at the UiPath offering and compare it to Microsoft Power Platform, and while Microsoft Power Automate has definitely come a long way and done a great job of making its way into the market, there are still key differences between the two platforms. Because Power Platform is still relatively new, the resources and support are a little bit more tedious to get around than with UiPath. With the UiPath community, because of their extensive work that they have done within the community to build developers, you get a lot more support on forums. 

In terms of usability of the platforms, UiPath has been doing this for a lot longer. So, the user interfaces and all around user-friendliness of their platform definitely show, in the time that they have spent working on the product. 

If I look at some of the things that Power Automate offered before the latest updates in the UiPath offering, Power Automate was able to allow you to trigger processes completely differently to the way that UiPath does. UiPath has since taken a step up and released their integration services, which has helped bridge that gap quite a lot. Being able to link to a process is a lot easier than it used to be.

If I compare scalability, development time, and ease of use of Power Platform to UiPath, specifically around the RPA components of the solutions, there is definitely a noticeable difference. 

As an organization, we took Blue Prism, WorkFusion, Automation Anywhere, and those types of vendors and platforms into consideration when selecting our platform of choice when our center of excellence was formed. When making the decision at that time, the stakeholders involved decided to go with UiPath, mostly because of what they had to offer and their consistency.

What other advice do I have?

The advice that I have to customers who are looking to start off their automation journey, or essentially take on a new vendor like UiPath, I would definitely say one of the challenges for us was getting our governance and standards right. As soon as we got that right, and we fixed our design-thinking approach, we realized how we could make sure our solutions were scalable. We then started seeing a higher return on investment. My advice would be to focus on the small things, make sure that you understand your processes and what goals you are trying to achieve, and then start with the beginning and end in mind. So, know where you want to end up and see how you are going to break your solution up into phases to be able to get there.

UiPath has had a very interesting impact on our environment. We have found it quite difficult to find RPA developers within our country, specifically those who have the skills that we need and can do what we do. So, we have had to rely on upskilling people as much as we possibly can to be able to deliver the solutions that we are delivering. In doing so, UiPath Academy has been quite helpful and handy, specifically because it is a lot easier to onboard a new employee or somebody who has less experience with UiPath. The training is free and easily available. If there are any issues or questions, the Academy team and the community are always around to support and answer any questions. 

What is quite impressive about UiPath is that they followed the same trend of having two major releases a year. I think those are the two most anticipated events that we have within our team as well. Because we have a roadmap, we know more or less what UiPath is planning and hoping to do. Our partnership enables us to have a closer view at that information. UiPath Insider Program allows us to see some of the previewed items as well. 

For those who aren't quite sure where they want to go just yet, keep an eye on the forums, blog posts, and UiPath in general. Look at their major releases before making any huge decisions. UiPath has a track record of consistency, and they have got some great reviews and implementations that I think we could really all learn from.

I would rate the UiPath platform as 10 out of 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Reseller
Flag as inappropriate
Head of Business Applications at a legal firm with 1,001-5,000 employees
Real User
Top 20
Web scraping is easy to use, intuitive, and usually pretty consistent
Pros and Cons
  • "The ability to use APIs within UiPath is really helpful. The web scraping is really great. It's so easy to use, it's very intuitive, and it's usually pretty consistent. When web pages change you need to update it, but it makes it quick. If you need to do another quick process, it's really easy to get it quickly and set something up. I can just scrape data from a website and save it somewhere."
  • "The documentation can be a little bit lacking. I think they improved it a little bit last month. Last time I checked, it seemed like they spent a bit of time trying to improve it. Sometimes some of the processes are nicely documented. UiPath offers training, which they provide on their website. They teach you how to use it, but for some processes, it just seems like the documentation isn't really there. It makes it a little bit difficult when you're using a specific process from the first time."

What is our primary use case?

We're mainly focused on finance for the time being so we've used UiPath for invoice processing and e-billing reconciliation. It makes sure that all of our converting information matches within our client databases. We've done a couple of solutions that track budget spend for certain clients, making sure that if the budget overruns or comes close to overrunning, then someone gets notified. If we get a new client or if a new legal case is opened, automation can make sure that all that information is then uploaded into our database. 

We've done a couple of smaller automations for the legal teams. These have been fairly basic ones though. There were a couple that download files from an email for them, and then rename them with the correct naming conventions, and saves them into correct drives. 

Another use case is to remove outdated users or information from our databases in line with the GDPR system.

How has it helped my organization?

In a general sense, UiPath has helped with data lineage, understanding where a process starts, who it rests with, and where it ends. It has made the process that we have automated a little bit more clear of which parts of the process are necessary, which are the parts that hold up the whole process, and which are the ones that are needlessly complicated.

For starters, it just helps give a bit more of an understanding of our processes once they're automated. Secondly, it's changed the way that we approach problems. We're tied into contracts that we might necessarily not want to be, but because we rely on the solution, we don't have a choice. Whereas, because UiPath is so versatile, we can use that to fill in gaps to take over processes, which otherwise in the past, we thought that only one specific tool could do for us. Now, we feel like we'd be less reliant on these specific tools to do a specific job. 

Third, a lot of teams are starting to understand that things can be automated. Whether it's in finance, HR, or even the legal teams, we started speaking to all the different teams and now they're bringing work to us and they're getting an understanding of things that do need to be done by a person and which don't. People aren't just doing work for the sake of it now. If they think there isn't a point to something and it can be automated, they bring it to us and we automate it. So, it's changed the way that we look at processes and don't just hardheadedly get someone to do it for no reason.

It checks our invoice stage for one of the processes that we do for e-billing. Previously, there wasn't anyone to check the financial data that we have in our systems against our clients and our recipients, and making sure that it all matches up. That process wasn't done at all so a month or two months later, a client would come back to us and say, "Hang on, you billed a strong amount or you've put our billing address wrong" which is obviously a little embarrassing. These things went completely unobserved for months. The client had to chase us, complain, and tell us we needed to fix it. Whereas now, it's more of a proactive approach rather than waiting for clients to come to us and tell us that we've done something wrong. We actually have the automation that can check and then validate those mistakes before they're even a problem and before they're spotted by anyone.

We're still in the early stages but we are starting to reach the point where UiPath is speeding up the cost of our digital transformation.

The digital transformation has made a couple of the lawyers' jobs easier by getting rid of the admin staff. It's freed up time and it makes things easier for everyone.

UiPath has definitely reduced our processing times as well. It really depends on the process but it has sped up. 

It has also decreased our error rates. At the moment we're looking to purchase an orchestration platform. At that point, we'll be able to collect more information about exact numbers and we'll actually have the analytics. 

What is most valuable?

The ability to use APIs within UiPath is really helpful. The web scraping is really great. It's so easy to use, it's very intuitive, and it's usually pretty consistent. When web pages change you need to update it, but it makes it quick. If you need to do another quick process, it's really easy to get it quickly and set something up. I can just scrape data from a website and save it somewhere.

The ease of building automation depends. UiPath makes things that are fairly simple but looks a little bit tricky in another language really easy. But if you're trying to do something really complicated, then sometimes it can be a little bit more tricky. It depends, sometimes it's really simple for fairly basic automations, I think it's fantastic. But when you want to try and get into the nitty-gritty and try and write your own code and then stick in there, it can sometimes be a bit difficult to use.

What needs improvement?

The documentation can be a little bit lacking. I think they improved it a little bit last month. Last time I checked, it seemed like they spent a bit of time trying to improve it. Sometimes some of the processes are nicely documented. UiPath offers training, which they provide on their website. They teach you how to use it, but for some processes, it just seems like the documentation isn't really there. It makes it a little bit difficult when you're using a specific process from the first time. 

If you're trying to invoke a method in UiPath, if you're trying to write a C# in there directly,  or if you need to do something which can't really be done in UiPath, but it can be done in C# or Python or something else, sometimes it's not that intuitive. It can be a little bit more complicated than it needs to be. I think that integration with other languages could be a little bit better.

For how long have I used the solution?

We have been using UiPath permanently for around eight months, but we've been using it in-house for about a year before that.

What do I think about the stability of the solution?

UiPath itself is very stable because it interacts with so many different applications. I noticed in the past, at times, when using it with browsers, for example, using it with Google Chrome or Firefox, occasionally Chrome or Firefox will update and UiPath can take sometimes a week or two to update with it. For that week, you're able to use any solution that involves Google Chrome or Firefox, because it's waiting for that update. I've seen that happen with a couple of different applications, not as much recently. UiPath itself is very stable because it can interact with anything. If anything is updated and UiPath doesn't have time to update drivers to match that, sometimes you can get left a little bit stuck.

What do I think about the scalability of the solution?

It's not really easy when you're using orchestrator to scale up and create a server, add a new bot, get a new license, and get it running. 

At the moment, it's just me using UiPath. I'm a developer and the architect for the solution as well. But we're planning to expand the team next year. 

We have a couple of processes that are running constantly, so I think we're using it as much as we can, and as much as our licenses allow. We're at a point now where we need an orchestrator to keep track and run everything at the same time. We're in the process now of purchasing that. I'll see where we're moving to, to expand quite far beyond that after we've got it. We're just at the point of ramping up.

How are customer service and technical support?

I've sent a couple of requests to support when we needed licenses and when we changed to a different computer or a different user, and they got back to us really quickly and solved it within a day or so. I've been pretty happy with UiPath so far. I think every time I've sent a request to them, it's been resolved pretty quickly, and even if they couldn't resolve it super quick, the response times are usually within 24 hours or so, which is really good. I can't remember a time where we've been stuck in the dark with them.

Which solution did I use previously and why did I switch?

I've used Automation Anywhere, but I haven't really used it within my work.

How was the initial setup?

The initial setup was pretty straightforward. I implemented UiPath for a couple of years before I came to my current company. It was quite easy, but even the first time it's always been quite easy and quite simple to implement.

The initial setup only took a couple of days to get it all installed properly and cleared with IT. In terms of getting the first process up and running, it took about a week or two because we already had a couple of processes that were available. That's just a case of tweaking them, making sure they're all okay, and then just getting them set up and getting more packaged up.

Our initial strategy was mainly to focus on finance and to try and reduce the outsourced headcount with a couple of the finance teams. We outsource a lot of our work to a couple of other companies and we want to reduce the cost of that, so I automate it in-house. Our other strategy was to try and free up as much time for our lawyers as possible to make sure they weren't bogged down with work. It gives them more time to focus on the clients and work up better relationships with them.

What was our ROI?

We're still looking at the process that we've automated and seeing how much time and money we're saving with this crisis, but we don't have that information at the moment.

What's my experience with pricing, setup cost, and licensing?

The pricing is pretty fair. Sometimes the pricing can be a little bit strange. There are different prices if it's for a specific user, a specific PC or if it's an attended bot or unattended bot. The price can be quite different, but I think when you talk to UiPath or when you look at the pricing sheets, there's not always a justification of why a certain license is more expensive than another. 

Licenses are more expensive than another but I wonder why there's such a big difference, why attended is four times more expensive, and that sort of thing. In terms of the orchestrator, I think it was a bit too much. It used to cost about 20,000 pounds a year. Now, they are ramping up costs. If you get an orchestrator but with just a few blocks, it's cheaper and then you can add up more parts to the orchestrator. So the cost goes up, which I think is better.

What other advice do I have?

Definitely to try and get as many teams involved as possible to open up the conversation about RPA within the business. It works best when you've got lots of teams who have an understanding of RPA and how it works. They can come to you with their potential projects and you can filter through them and see which ones are going to be the most helpful.

It's hard if no one else in the business really knows RPA or how it works, or if there's a bit of a wall there. It's important to introduce RPA to as many different teams as possible and to encourage people to get involved, think about the processes that they do in it, and try to identify what can be helpful.

It's important to keep RPA close to the applications and the IT teams because if you're using RPA or UiPath you're going to need to be able to be speaking to your team who need permissions or admin privileges, or you need apps to be updated. It's important if you're going to put it in, have it as close to apps and development as possible.

It's a case of understanding that it's not a case of trying to get everything automated that you possibly can. The goal shouldn't just be to automate everything. If you've got a process and you can do 99% of it automated but you can't automate the last 1%, you can but it's going to be really fairly inefficient. Understand that it's fine for a process to have some bits that are automated, some of which are done by a person. The hybrid workforce, rather than going into the strategy of just automating everything is ideal. I've learned that trying to find that balance and getting that communication between the two is good.

I would rate UiPath a nine out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Associate - Robotic Process Automation at a financial services firm with 10,001+ employees
Real User
Top 20
Great online training, reduces manual errors, and makes it easy to automate processes
Pros and Cons
  • "Every project we've delivered that has some sort of time savings to it has had an intrinsic ROI."
  • "I would really like the ability to bring OCR connectors into Studio X, if possible. Right now we're only using OCR and Studio as that's where the plugins are available."

What is our primary use case?

We primarily use the solution for operations processes in our corporate investment bank. For example, screen scraping, querying from databases, or any transactional processes. Those are what we're really looking at the most.

What is most valuable?

The orchestrator is very valuable for us. The ability to have processes, especially transactional processes, be fed into and triggered from there is excellent. I really like the ease of use that allows not just typical developers to use the Studio version, but also StudioX, which allows citizen developers with little to no coding background to be able to automate their own process. Studio limits a lot of the coding you would generally do in Visual Basic and offers a pretty easy use case for people who want to get into development, who might not have that background.

I’d rate the ease of automating within UiPath at an eight or a nine out of ten. Maybe even a perfect ten. They make it very simple. It's a really good platform and for everything I've used it for so far, I can't think of how I would do this X, Y, or Z differently. I really like it.

In terms of our adoption of it, we just started using it this year. We haven't had a large volume of bots delivered and put into production, however, with what we're using, we have a lot of proof of account sets and use cases that are getting pushed along that are going to save the company time in man-hours.

It's going to save the company a lot of potential risks in terms of manual error. It's also something that can be used to automate processes that are very heavily related to compliance procedures as well, where you don't want as much manual touch for the same reason and you don't want to risk, even if it doesn't take that much time for a person. With automation, you remove the risk of somebody making an error.

We don’t have a crazy amount of metrics. We're really in the process of adopting it into the organization. I'd say within the next year, we're really going to be seeing a very large adoption of it.

We have seen direct savings in costs. Every project we deliver in time save has an associated cost reduction to it. If you're saving, for example, four hours a day on a manual process, you're saving that money. You’re also saving on anything that's related to risk. I don't have any hard numbers on the amount of time that's been saved, however, it’s been positive.

Our teams have used the UiPaths Academy courses. It’s helped make the process of getting employees up to speed with UiPath very straightforward. It's one of the better learning platforms I've seen. Between them and Alteryx, they both have very good learning platforms.

What's really important is that you don't need to wait for instructor-led training, which is infrequent. We have it sometimes, still, even when we’re having it a few times a year it gets expensive. The online training, which covers most of the same material, is a really good way for people who don't want to wait for the instructor-led training and want to immediately get their own feet wet.

The Academy is very comprehensive. It's well structured and training is easy to follow. I've used other tools that have been much harder to follow online. This one I really like.

The biggest values that we’ve seen From UiPath Academy are ease of use and ease of scalability. The solutions you make based on the infrastructure that's built around it can be made to be very scalable. There's so much that depends on other terms, such as the data that we have on our own processes, that it's going to be the yes or no, whether or not a process we build can be scalable automation for other teams. As long as we get the data and the processes lined up in the right way, we can make very scalable processes, which is good as that's more cost savings for fewer bots and that's really like what we want to see.

What needs improvement?

There are some external dependencies. When we have APIs available, UiPath does have that option that we can hook into APIs. That's really where I'd like to be down the line, more like hooking into APIs, data warehouses, so that you don't have to worry too much about the screen scraping functionality, even though that's a great big part of what it does.

I would really like the ability to bring OCR connectors into StudioX, if possible. Right now we're only using OCR and Studio as that's where the plugins are available. I don't know enough about the back end of what makes this feasible versus not feasible. However, at the moment, with StudioX, you can only really read and digitize PDFs. If they can bring in the OCR connectors, they'd allow citizen developers to be able to read in a larger breadth of documents that they would generally need Studio to do.

For how long have I used the solution?

I've been using the solution for about ten months. 

What do I think about the stability of the solution?

The product is as stable as it can be for the processes we use to expand on that. We do a lot of screen scraping and web scraping a lot. I want to move away from this in the future. However, the stability of those bots is going to ultimately be reliant on how that webpage looks.

We're looking at very specific parts of the website, such as the HTML tags. If those stay stable and we build our identifiers on those sites to be relatively dynamic, the process will be fine. 

What do I think about the scalability of the solution?

We do plan to increase usage.

The idea is to train up more citizen developers. We need to strike a balance between getting the tool out to the citizen developers and making sure that they're following the governance procedures as well. There's also a little bit of risk of it due to the fact that you give people licenses to build and then they can build something on their desktop. They can just, without going through the proper governance, run it. Therefore, you need to make sure things go through the correct governance. That's why we're trying to make sure we have a very good system in place so that when we grow and are training system developers, everything they do goes through the correct controls and governance process.

We're planning to keep building the users over time. We really want to start looking in the next year from more of a top-down perspective, across larger organizational issues where we can make more scalable bots rather than strictly or mostly automating one-offs. We're looking for where there's more commonality across different businesses that do similar processes, and maybe access similar data sources.

I'm not sure exactly how many people are using it across the organization currently. My guess would be at this point there are 75 to 100 users. However, I could be completely wrong. I'm just guessing, as I don't know all the citizen developers, and who in the operation's teams are using it.

How are customer service and support?

I have not used technical support, however, some people who work for me on my team have. I manage a small team of developers. They have worked with UiPath consultants who are on contracts with our COE. They've been extremely helpful with working out some kinks that they've come across in their projects. 

Which solution did I use previously and why did I switch?

I haven't used blueprints on my Automation Anywhere. We used to use Automation Anywhere and we are moving off it in favor of UiPath, though I never used those other tools myself. I use ALteryx and it has some RPA abilities, although I use it much more for just basic data transformation workflows. I have coded RPA bots and Python before. What I like, with UiPath, is it's still a tool that's based on code - Visual Basic, VB.NET. However, the coding is really for the most part restricted to your data manipulation, working with variables. The control flow that you normally would need to code in Visual Basic is all drag and drop. I really like that versus straight coding. It still gives you that flexibility of a lot of development environments, however, you can have that drag and drop canvas that allows you to really not need to program as much of that control flow. 

We moved towards UiPath as it's cheaper per bot and it enables more of a citizen development model as well. Automation Anywhere bots were only developed by our COE at the time and UiPath COE's going to use them also, however, they're allowing users in operations to use both Studio (if they have the taste for it) and StudioX. It gives a lot more citizen development capabilities for more advanced functions and automation-type stuff, whereas previously, you would normally need somebody on your team who happens to know BBA to do it. 

In the past, if you have someone from the team who knows BBA and makes something, and they leave and their code breaks, you're screwed. However, if you have a StudioX bot, if it breaks, it's going to be much easier to look into the issue and fix it. It's also supported by our C0E's tech infrastructure. Those are the main driving points for shifting off as well.

How was the initial setup?

I was not involved in the initial setup. I've interacted with UiPath only as a user. I was one of the first users, however, I had nothing to do with deploying the tech infrastructure and developing the governance and controls. I'm just a developer.

What was our ROI?

We have seen a return on investment. Every project we've delivered that has some sort of time savings to it has had an intrinsic ROI. I don't know the total ROI across the organization, however. I work in one specific part of the company and it's been adopted in a few places. I don't know the total ROI that's been delivered yet.

It's my understanding that it's delivered close to a full headcount so far, in terms of productivity of capacity. There are approximately eight hours a day of time-saving for every workday of the year. That's where we are right now, as we've really just begun adopting it. We're not really deployed into production, and the larger-scale projects aren't in place yet. So far, the projects have been smaller tactical builds that we've been using and it's been delivering up around eight hours of time saving a day. 

What's my experience with pricing, setup cost, and licensing?

I don't know the pricing enough to really comment on it. I know we're getting a better deal in automation than what we had with Automation Anywhere bots, at least per bot deployment. However, I don't know what the licensing costs are.

What other advice do I have?

We do not yet use the Uipath apps feature or their AI functionality in our automation processes. That said, with AI, we're bringing it in and we're definitely planning to use it in the future.

I'd advise new users to make sure you have the controls and governance structures, first and foremost, and you want to make sure those controls are going to be in place and understood before you start deploying licenses to users. I make sure that everything is going to be done and compliant with the audit. As somebody who works in financial services, which is a very heavily regulated industry, that's something that really needs to be kept in mind. You don't want to develop what are essentially just user tools that are not going through the proper controls and treat it like a lightweight software development lifecycle project. You need to make sure those controls are in place, and yet, don't do it too much to the point where it's going to deter the users. At the end of the day, we're not making software, however, we still need to strike that balance.

I'd rate the solution at a nine out of ten. Nothing is perfect. I know you UiPath wants to improve the stuff that has not been perfected. I'm not going to say it is a ten out of ten, even though I'm struggling to think of what I don't like. Something that would be very helpful for UiPath is to go back to try to build OCR in StudioX. That would be ideal. Also, being able to implement different types of loops in the Studio would be great. Right now, you can only do a four-loop in a repeating loop. If we could implement wall loops, that would be nice. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Shubham Agrawal - PeerSpot reviewer
Software Engineer at Tech Mahindra
Real User
Top 20
Minimized our on-premise footprint and has helped with quality control
Pros and Cons
  • "I've contacted technical support many times and they are very helpful."
  • "While UiPath Studio helps speed up the cost of digital transformation, in a way, it requires expensive or complex application upgrades or IT support, as it needs an entire setup. That setup requires support from different departments, and that comes with a cost."

What is our primary use case?

For a current client, we have around 22 to 25 use cases, and it's all based on the financial side of things. The client is in finance, and we have use cases all of which are comprised of different tools, including SAP and their in-house CRMs. It's about automating the process where we take some data from the CRM tool and upload it to SAP. It also involves uploading the files to the FTP server. 

For example, one use case is where the applications used are Oracle, and SAP, and STP. We just download the data from Oracle. There are different files that we download from Oracle and upload to the FTP server. From that FTP server, there is a different team that takes those files and creates a Tableau dashboard. 

How has it helped my organization?

UiPath Studio helped us automate many processes that have helped us save money. Even though the tool price is there and the license costs are there, it has given good ROI. For example, automating a process can reduce the work to half or maybe 60%. We divert efforts to different work. Therefore, it has been pretty useful in terms of savings and quality control.

For example, one client had a focus on quality control. There are instances where employees make some minor errors that could lead to major losses to the organization from the department's point of view. We automated that process and it gave us more return in terms of quality control. Fewer errors ultimately were made which saved the company from losses.

What is most valuable?

UiPath has a full suite of capabilities. It has, for example, an end-to-end automation suite. From a development point of view, it is pretty helpful to have access to all of the activities on offer that anyone can understand. 

The Studio as well as the process mining are great. Document understanding is another useful feature. It has eliminated the business analyst side where you have to go through each department and find out which processes are there, and take a different tool to get those all processes in one place and create a process workflow. All of this can be done with process mining. 

With document understanding, we have the capabilities of having UiPath understand and create documents, which previously was quite a lengthy endeavor. You just have to install it and follow the steps. It will automatically take a screenshot and create a document for you and then create a brief description of it. 

It’s easy to build automation using UiPath Studio. From a developer's point of view, it is easy due to the fact that you don't need much of a coding language or coding background. You just should have a clear logic behind it. If you're clear with the logic, a layman can handle the task. They do have Studio X features, which is for the layman who doesn't have any background, who doesn't have any coding or developer's background. They can automate their own work. Even an SME who doesn't know anything about automation could automate small tasks.

It’s great that we can scale automation without having to pay attention to infrastructure. That is very important actually. For example, scaling automation plus giving attention to the infrastructure can be a little hectic and time-consuming. If there is any way where we could reduce this work or optimize it, it would be great from the implementation point of view.

UiPath enables us to implement end-to-end automation. Right from the start, you have document understanding and process mining as well as the Orchestrator, which helps you with getting an overall view of the bots in our organization.

End-to-end coverage is the most important thing, due to the fact that, if it is end-to-end, we don't need to go to the market and look for any other application. If you can get end-to-end, you don't need to go for other products which simplifies everything. It's easy for us to maintain and work with it instead of having to integrate and manage multiple systems, multiple products, and multiple applications.

UiPath has helped minimize our on-premise footprint. It has helped us with quality control savings. We have saved many efforts previously requiring full-time employees. It’s one of the most important factors when we work for clients. If a client is hiring us to automate many processes, there are different intentions of doing it. If we are able to help them reduce cost, reduce and do some quality control, it is important for them. For example, previously, if work required ten employees, we have been able to reduce that down to six or sometimes four personnel maybe.

The UiPath Studio has reduced human error. It has helped us with quality control very often. In the past, mistakes have cost us. It has saved costs as well as saving us money related to fines or penalties.

The solution has freed up employee time. Instead of doing the same mundane work every day, we have just automated that part and now the employees have more free time to do more meaningful work. In terms of hours, from a department's point of view, we have saved around half, that is four hours per day, maybe about 80 hours per month. The additional time enabled employees to focus on more important work.

We have found that the product has reduced the costs of our client’s automation operations. With my previous client, we calculated an average of 40% in reduction of personnel and 40% in cost savings. UiPath has saved us money across the organization. The average saving is likely around 40% to 45%.

What needs improvement?

I'm pretty much happy with all of those tools. I don't have anything in mind that I could see improvement.

While UiPath Studio helps speed up the cost of digital transformation, in a way, it requires expensive or complex application upgrades or IT support, as it needs an entire setup. That setup requires support from different departments, and that comes with a cost.

I came across one problem while upgrading. We were upgrading from the 2019 version to the 2020. There was one thing that was not mentioned either on the website or documentation, and we had to take support from UiPath. The documentation needs to contain each of the scenarios which could occur while upgrading the solutions. As it is now, this is not the case. That said, when we ran into issues, UiPath Support helped us through it.

For how long have I used the solution?

I've been using UiPath for five years now.

What do I think about the stability of the solution?

We've had outages once or twice. For that, they have a workaround. If a server goes down, we should have a backup server for it. If that's the case, it is just a few steps needed to migrate or we can take the setup from another server. That's it. It's pretty good in general. 

What do I think about the scalability of the solution?

The scalability is fine. For example, if the bot count is about zero to 100, we have the capacity. And if it goes beyond that, then we have to increase the features of the systems and servers. It could take time if we scale beyond the limits, however, it's still possible. It just requires an upgrade. 

What's required is managing all the infrastructure and getting all the permissions from the client which is what could take time. Scalability can be an issue when it goes beyond the mentioned limit.

In the current organization we're working with, it's totally unattended bots where no user is actually using this tool. That said, the bots are in production, which works 24/7. No user is having this access to the tool. It is all unattended bots.

In the previous organization, there were 58 to 70 users as we had attended bots. They were using bots in their daily routine.

It's a routine for us to use this product every day and deploy this solution. We are definitely looking at increasing it and scaling. We have a lot of work in the pipeline.

How are customer service and technical support?

I've contacted technical support many times and they are very helpful. Based on the severity and priority, they do help us on priority and they are very helpful in terms of responding, supporting, and maintaining. If they can't help us by email, even after giving clear instructions, they'll bump you to a different level and help. It can be just like spoon-feeding us. They are very patient and try to be very clear.

Which solution did I use previously and why did I switch?

We were doing automation, however, it was just .com and .net. We used to write five lines of code just to click on one button, which is just an activity right now we have in UiPath. We switched to UiPath to do end-to-end processes which would require large amounts of code if we kept doing what we were doing.  

How was the initial setup?

I've implemented UiPath from scratch many times. 

The process is quite straightforward. You just have to have the installer and just click install, and then after a few steps, it is done.

Setting up just UiPath Studio hardly takes ten to 20 minutes or maybe one hour if you're facing some complexity. Setting up an Orchestrator with all the robots could take a while.

Our implementation strategy is based on whatever the customer's requirements are. Different clients have different requirements. My previous client, for example, didn't want the cloud as they were pretty concerned about the security as they deal with financial data and they don't want the data to go to the cloud at all.

Clients have the option of on-premises or cloud. Based on that, we just go with the requirements. Some clients want attended bots due to the cost, and some want unattended bots due to the features. 

In terms of maintenance and deployment, how many people you need depends on how many processes you have with the client. Right now, with the current client, we have 22 to 25 processes that we have automated. We are just three users who are developing, testing, maintaining, and supporting this project. However, it varies and often depends on the process and client and how many bots.

For maintenance and support, you don't need many people. For development, if they're at 10 people, five or four could do the work in terms of support and maintenance.

What about the implementation team?

We handle the deployments for our clients. 

What was our ROI?

While the clients might have released some reports, I don't have much knowledge about ROI. 

What's my experience with pricing, setup cost, and licensing?

I do know about the prices of attended and unattended bots as well as Orchestrator. 

There are costs related to Orchestrator, Studio, and attended bots. There are also infrastructure costs, and, while implementing this tool in any organization, there are different costs attached to it.

The price for the attended bot is between $1,800 and $3,000. The unattended bot was $8,000 last year.

Orchestrator is around $20,000.

Which other solutions did I evaluate?

We looked at Automation Anywhere and Blue Prism, however, about five years back, where UiPath, Blue Prism, and Automation Anywhere were the leaders in the market, at that time, just UiPath had the free training and Intuit training for their tool. The other tools didn't have any training, or if they had, it was paid. That's why we chose UiPath, which ended up being the best out of the three anyway.

What other advice do I have?

The company I work for is a UiPath partner.

There have been multiple companies that I've been working with. Two remain the same. I've been using different tools as well. It's been on and off with UiPath.

We are not using the latest version of UiPath. The latest version is 2021. We are using 2020. This is due to the fact that the client that I'm working with has a stated policy as to using a minus one version. They believe it could not be a more stable version for any product. 

At this time, we don't use the SaaS solution or the AI functionality. However, I have enrolled in AI training to better understand it. We do not yet use the automation cloud or UiPath apps either.

In terms of employee satisfaction, from the experience I had from interacting with the client and different users, they are happy as well as sad. They are happy in terms of moving away from the mundane work that has been taken off from their hands. They are, however, both sad and afraid that they could lose their job.

I'd advise users, if they're a layman, to go with the training. Just start with the training from the UiPath website itself, in the RPA Academy. That is sufficient for anyone to start with. They have all the courses that start right from scratch for every role, be it business analyst, solution or product developer, et cetera. In six months, even starting from scratch, you can excel on this product.

With UiPath, it really is possible to optimize so many things. 

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

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Download our free UiPath Report and get advice and tips from experienced pros sharing their opinions.
Updated: June 2022
Buyer's Guide
Download our free UiPath Report and get advice and tips from experienced pros sharing their opinions.