Automation Engineering Manager at a computer software company with 51-200 employees
Real User
Top 20
Saves costs, makes it easy to build automations, and reduces human error
Pros and Cons
  • "UiPath saves costs for our customers’ organizations. That would just be the cost savings from RPA bots. I haven't really dug into the cost savings of the ancillary products, however. I know that one of my clients is using the test suite now after I had built a proof of concept for it, and they've fully implemented it. I'm sure there's going to be a lot of cost savings there as well."
  • "The license model changing every year can be a little bit frustrating. It's hard sometimes when things go from being robot-based to being runtime-based."

What is our primary use case?

We primarily use the solution for legacy data transfer, UI automation, CRM and ITSM automation, and call centers. Specifically, in call centers, using UiPath forms and form render has been really helpful.

What is most valuable?

I love developing in Studio. For my clients, the approachability of the orchestrator is really valuable. It takes a little bit to learn the licensing structure and layout at first, however, once they get it, it's pretty smooth sailing from there. The modern folders have become a great thing for any enterprise that's looking to automate using an orchestrator as a server.

I like to automate in Studio as I'm familiar with it. I honestly just like the platform so I like automating with Studio.

I really enjoy Document Understanding. I like how it all integrates together. Some of the stuff I've seen now with just the connectors and the way you can scale implementations is really exciting. While I do like Studio, I also like how it works with the rest of the platform.

We most recently built an unintended bot that saves them about $500,000 a year worth of GS 14 labor.

UiPath saves costs for our customers’ organizations. That would just be the cost savings from RPA bots. I haven't really dug into the cost savings of the ancillary products, however. I know that one of my clients is using the test suite now after I had built a proof of concept for it, and they've fully implemented it. I'm sure there's going to be a lot of cost savings there as well.

In terms of ease of building automation, it depends on the process. For anything that's ultra-low or a low-level complexity, it's very simple. Once you start getting sprawled out into larger automation that very much becomes object-oriented programming and is basically making a workflow. That's when you really need to take hold of programmatic concepts. You need to be a strong scriptor to be able to make the best RPA bots.

Our clients have reduced human error. That's one of the things that I tend to talk about the most. The bots can get work done faster, however, the reduction of human error is probably more valuable in some cases than just speeding up work.

In terms of UiPath Academy, everybody's used it. I've used it myself. My entire team has used it. All of our engineers are some sort of Pearson VUE certified now. Most of us have the Advanced Developer. A few of our younger junior developers have the associate, the RPA associate, however, they're working on getting the Advanced Developer and they lean on the Academy pretty heavily.

The biggest value in the Academy is the videos, which are pretty helpful. Sometimes you have to slow it down, however, for the most part, the way it goes through concepts, especially for somebody that doesn't have much programming experience, the videos tend to go through some of the more elementary things like variables arguments. That can get a little bit boring for programmers since they've been through that 100 different times. That said, that’s really where the strength lies as it does target a large group of different employees. As an engineer, I might pass by some of the boring stuff, however, I will still find things later on in the training where I'm like, wow, I actually never knew that.

What needs improvement?

The license model changing every year can be a little bit frustrating. It's hard sometimes when things go from being robot-based to being runtime-based.

Some federal users are still on the 2019 orchestrator or even a 2018 orchestrator. However, by being on them, they can't take advantage of modern folders. This issue is, once they get upgraded to 2020, and they start using modern folders, essentially you shouldn't really be using plastic folders anymore. Some of their frustrations aren't really long-term frustrations. Orchestrators have gotten really popular over the last few years. There are certain things that have made it so much better. That said, we're still in that transition where clients have been using classic folders and then they upgrade and they're going to have to change everything. Hopefully, they don't have to do it more than when they upgrade past 2020.

One of my clients upgraded their production environment from the 2019 orchestrator to the 2020 and everything was in plastic folders and I advised them to switch to modern folders and it was a pain. Once it was taken care of, it was great. It's just that it took a lot of convincing to tell them why it was better.

For how long have I used the solution?

I've been using the solution for three years. 

Buyer's Guide
UiPath
November 2022
Learn what your peers think about UiPath. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
656,862 professionals have used our research since 2012.

What do I think about the stability of the solution?

It's pretty stable. The biggest issue is just that more companies need to really adopt a change management system, whether that's through Service Now or is built-in change management, those alerts need to be going to the RPA center of excellence. 

There are things that will change or break the UiPath bot sometimes. They're very stable and they've become more stable if there's a change management system. Automated testing can make it so you can catch things that have changed with applications with RPA testing before they've occurred and then you can fix things quickly.

What do I think about the scalability of the solution?

The scalability was tough a few years ago, however, now it's exponentially easier with modern folders and the orchestrator.

How are customer service and support?

I've worked with UiPath support. I would put them at a seven out of ten as they need to be a little bit more timely. There have been issues with a client where support has taken a really long time to get back to us or they haven't updated our support ticket, even though we've advanced. Maybe it was an isolated incident. I have worked with support before where that hasn't happened. I felt like I got in a bad run of working with the support folks and the client was definitely not pleased.

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

I actually don't have experience with other RPA solutions. I came from a web development background and I went straight into UiPath and now the way that it's scaled out and now that I work in the federal government, UiPath has such a large piece of the market share. I've never really seen a need to learn any other automation solutions. I may learn Power Automate at some point, however, I would really prefer to stick with UiPath.

How was the initial setup?

The solution is pretty straightforward. I've run through complex issues, mostly the NuGet package and it's different with every customer. As far as the UiPath platform goes, it's pretty straightforward to deploy bots. It all depends on how an agency has its group policies set up for security and sometimes that causes issues. It's just about learning new ways to solve different problems that may be unique to an agency or may not be.

In the government, deployment takes a little longer. I would like to think development usually doesn't take that long, however, it's like going through ATO, especially if it's an unintended bot. Sometimes it can take like a few months. It just depends if they've got a center of excellence stood up or not. For example, if they've got an CI/CD pipeline or just a standard development life cycle, a lot of people don't have that set up and then it ends up taking longer as they have to go through ATO. It’s variable. Unfortunately, it's just a lot slower to get them deployed than in the private sector I think.

That’s no fault of UiPath. It's usually group policy security systems and things like that. I've had to talk to a lot of security folks and help walk them through things that need to be changed.

What about the implementation team?

We've been implementing our UiPath as well.

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

I don't really have too much to offer about the pricing part of it. I don't really work on that side of the business. I would say my only gripe about the pricing would be something like a Studio Pro license being more expensive than a Studio license, just to essentially get something that links Test Manager. Some people might've found that a little bit hard to swallow. From what I've heard, Studio Pro is going away and Test Manager is just going to come into Studio. That would be the only thing I've noticed that I thought was a little silly. Everything else is typically not really my side of the business.

What other advice do I have?

We have everything on-prem in our demo environment and the customers I work with typically have the on-prem offerings as well.

I have used UI path apps in our demo environment. I do not have any clients that are using it.

We have an AI center in our demo environment, however, I don't have any clients that are using it. I do have a client that's actually in the process of installing it right now and getting it through their governance model. That's as close as it would've come for our customers using the AI center.

To those considering UiPath, I would say, just go ahead and do it. RPA is pretty awesome. It's easy to get solutions out. There still needs to be a good bit of work done on the Citizen Developer Model, however, at the same time, as far as getting a team of engineers in there to automate things, if you get good RPA developers, you can get things automated really quickly. People can help you with your standard development life cycle. You just need to jump in.

I would rate UiPath solutions at a nine out of ten. The only reason I wouldn't give it a 10 is that, in terms of the installation of the product, sometimes the documentation leaves a lot to be desired. Sometimes it's tough to work through installation issues without actually contacting support. I do wish that was a little bit more streamlined.

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
PeerSpot user
Guhan Eshwar - PeerSpot reviewer
Assistant Manager at FirstSource Solutions Ltd.,
Real User
Top 20
Built-in .NET methods make code less complex, and APIs decrease development time
Pros and Cons
  • "I have worked with other automation tools and UI Explorer is the standout feature of UiPath. For web-based applications, we can interact with every HTML element, from head to tail. UI Explorer is a valuable addition to UiPath for creating complex, web-based automation."
  • "UiPath has a built-in functionality called Computer Vision to extract values from a PDF... The cost is based on how many documents we are using Computer Vision on. That makes it difficult to estimate ROI."

What is our primary use case?

My domain and expertise are in life sciences. In life sciences there is a process called pharmacovigilance, which involves monitoring the effects of medical drugs after they have been licensed for use. I create end-to-end automations, for case processing and full data entry. The customer will store details in an Oracle-based pharmacovigilance platform called Argus, where clinical data from the client and the product are stored. The UiPath bot has to capture the cases from Argus. Once a case has been input into UiPath, a mandatory status check, duplicate search, and case processing have to be done.

It then needs to perform full data entry in Argus. The full data entry consists of more details like patient information, product information, event information, and so on. The bot needs to validate and input those details into Argus and save the case. 

Some days there will be 1k records and on other days, there will be 2k records. On average the bot will process 12k to 13k records.

How has it helped my organization?

Pharmacovigilance is a big process. It would take almost 45 minutes for a human to complete a single case. By implementing UiPath robots in the customer's environment, the case processing time has been drastically reduced. The bot processes cases, end-to-end, within 20 to 25 minutes, depending on the case complexity, so that the customer is saving 20 minutes per case. The savings are equivalent to nine or 10 FTEs, which is huge. As a result of those savings, they have requested us to build more bots for them, for other processes.

What is most valuable?

The most valuable feature in UiPath is the UI interaction with UI Explorer. I have worked with other automation tools and UI Explorer is the standout feature of UiPath. For web-based applications, we can interact with every HTML element, from head to tail. UI Explorer is a valuable addition to UiPath for creating complex, web-based automation.

The AI Computer Vision and Orchestrator are also outstanding features. They make it very easy for developers.

In addition, the introduction of drag-and-drop APIs to UiPath enhances the development processes and decreases the time it takes, as well as the processing time. For example, if you wanted to read an email from Microsoft Outlook using UiPath two years ago, it would take about five steps or activities. Now, with the Graph API within UiPath, you can read an email message from Outlook within a span of five to six seconds, maximum. This API functionality is pretty easy for us to handle.

Along with this, UiPath also introduced Orchestrator access via API. It's not mandatory to log in to Orchestrator to create an asset manually in UiPath. Rather, you can use the Orchestrator API to call a bot process and the assets. This API functionality helps developers to develop components effectively, as well as reduces bot processing time drastically.

For how long have I used the solution?

I have been into RPA for almost six years and I have worked in the three major tools: UiPath, Automation Anywhere, and Blue Prism. I have been using UiPath for four to five years. I'm an RPA developer and do development for my clients. That includes designing and deploying bots in the clients' environments, and making sure the bots are running well.

What do I think about the stability of the solution?

It is stable. We are using the 2019 version. The versions are continually upgraded with the latest being the 2021 version. There are frequent updates but the version we are using is stable. We don't have any errors or bot crashes or other unexpected system exceptions during development. The stability is good across all versions.

What do I think about the scalability of the solution?

It's pretty scalable. It can be used across all major providers. If you want to automate Windows, web-based or PDF-based interactions, or do email or Excel automation, you can. We can also do terminal automation, mainframe automation, and Citrix automation. It covers almost every possible scenario for real-time data handling. 

We only have a couple of challenges, when a customer says we need to do this or that and UiPath doesn't have built-in functionality for that. We need to think differently and add some additional .NET components, for example. 

But UiPath is pretty scalable, and we can use it across all technologies for automation.

How are customer service and support?

If you don't find a solution in the Community Forum, you can raise a technical support ticket with UiPath. The support team works 24 hours a day, and we can get a resolution immediately. Both the Community Forum and the technical support play a major role and both help developers.

UiPath also has partners. Cognizant is a high-priority partner and they have their own SLAs for everything. If I raise a ticket regarding UiPath, if something is not working, the response time is very quick and the resolutions they provide are pretty standard. We haven't faced any difficulties in raising a ticket. Everything has met our expectations with respect to the technical support.

How would you rate customer service and support?

Positive

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

The main thing that could be improved is the cost. I have worked with other tools and the licensing cost of UiPath is slightly higher than the others.

Also, UiPath has a built-in functionality called Computer Vision to extract values from a PDF. If we want to use Computer Vision, UiPath has one drawback. The cost is based on how many documents we are using Computer Vision on. That makes it difficult to estimate ROI. Computer Vision has a dynamic cost. To propose a project to a client, a project that includes Computer Vision, we need to have some kind of standard cost so that they can calculate the ROI effectively. Computer Vision should not be based on usage.

This is one of the main drawbacks that I have seen in real-life situations, when quoting a price for a client. If UiPath improved in this area, they might have many more customers who want to automate PDF interactions based on Computer Vision, because it has huge scope.

Which other solutions did I evaluate?

The advantage of using UiPath over Automation Anywhere is the UI interaction. Automation Anywhere doesn't have a specialized feature like UI Explorer, or any other options to click on an image or interact with UI elements. Automation Anywhere has a Capture command and we have to work with that one command to interact with all the UI-based elements. But it's completely different in UiPath. UI Explorer enables multiple clicks and interactive activities. You can mimic the HTML per your project's needs. You can't work in the same way in Automation Anywhere. With respect to web-based automation, UiPath stands tall. AA has limited functionality.

The disadvantage of UiPath is in the PDF interaction. Automation Anywhere has a bot called IQ Bot, which is included in the licensing of Automation Anywhere. It's pretty easy to train it for a PDF document within the span of a few seconds. UiPath's Computer Vision has the same functionality as IQ Bot, but Computer Vision is pretty costly.

Other than that, Automation Anywhere is cloud-hosted and it has multiple ways for a developer to code. If you want to code RPA, or you want to code in a flow-based manner, you can do so with Automation Anywhere. But UiPath has only one mode, a flow-based automation. UiPath doesn't have code-based automation.

From the developer's point of view, if you have a code-based structure then what AA offers is as good as UiPath. 

A major advantage of UiPath is that since it is a .NET-based application, you can use all the methods and the properties that are available in .NET. You don't have that functionality in Automation Anywhere. If you want to read or manipulate a string, you need to use separate activities in Automation Anywhere, but with UiPath you can use the built-in .NET methods to read a string in a single line. The complexity of the code is smaller in UiPath.  

What other advice do I have?

Because I have worked in all the major RPA tools, I can say confidently that UiPath is very developer-friendly. If you are coming from a non-technical background, or you don't know coding, they have a separate portal for you to develop in, called StudioX. It's a low-code platform, a "citizen-developer" platform. Anyone who wants to use UiPath can use it without any background.

From the development, design, and testing points of view, I rate UiPath higher than other RPA tools for automation. Go directly to UiPath, rather than trying all the other tools. UiPath is number-one for development and testing.

It is mandatory in our company to use the UiPath Academy to do RPA certification. Almost everyone has completed advanced professional certification in UiPath. The Academy covers every topic extensively, as far as what developers need. I don't come from an IT background but I learned it. UiPath teaches everything from scratch. With a little bit of coding knowledge, it's very easy to learn development using the Academy portal. The major advantage is that, since it is a video-based series, you get a clear idea of the modern-day functionality. They explain everything with an example and they give you use cases for practice. 

If you want to be an architect, they have a course for that. If you want a developer diploma, they have a course for that. And if you want to learn a specific topic, like deployment or testing, they have courses for them.

For anyone with experience in another technology who wants to learn UiPath, or wants to do RPA projects, it's a matter of 10 to 15 days to go through all the videos and you can start working. That's a big advantage of UiPath. The Academy makes learning easy.

They also have a Community Forum. If we have any doubt, we can interact with other developers around the globe. It's very interactive and we can learn what things are intended to do. About 90 percent of the time, you can find a solution using the forum.

Other than the Computer Vision cost model, the features of UiPath are pretty awesome to use. As a developer, there aren't any drawbacks or difficulties when using UiPath.

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
Flag as inappropriate
PeerSpot user
Buyer's Guide
UiPath
November 2022
Learn what your peers think about UiPath. Get advice and tips from experienced pros sharing their opinions. Updated: November 2022.
656,862 professionals have used our research since 2012.
Head Of Delivery at a tech services company with 51-200 employees
Real User
Top 20
Scalable, easy to learn, and straightforward to set up
Pros and Cons
  • "The solution is very scalable."
  • "The studio design is a little different. If you go from one tool to the next, you might be a little shocked at how things are organized."

What is our primary use case?

We primarily use the solution for our clients. 

How has it helped my organization?

One interesting use case we've seen is that the product team leveraged UiPath to expose an API for their customers to then fulfill a service request.

It was part of their deal that, for them to sign this large contract with one of their clients, they needed this functionality. The product team has a huge backlog, and it wasn't going to make it based on everything else they had to deliver, so they actually leveraged UiPath to expose this and give them a service they just didn't have before.

What is most valuable?

When comparing it to, for example, Blue Prism, one of the key value points is, other than the full platform in general, the ability to trigger automation on demand. Basically, when the work gets loaded into the queue, the work can then be started without having to run things on a schedule.

The solution has improved the way an organization functions. For example, in general, in the context of RPAs, it's really about the focus of picking those tasks out of people's daily efforts so they can spend more time with the customers. What you get off the back of that is dollar for dollar savings. You invest in this tool, and you get back dollars by hours, however, beyond that, there are these peripheral benefits that you get that are a little harder to measure. You’ve got to have good guys out there to capture this.

In terms of endpoint satisfaction, customer satisfaction, you have to look at it within the business and their measurements before and after you've done something to actually see what is happening and attribute it to what you've done with UiPath.

We haven't done anything that hasn't saved money yet.

At the beginning of a journey, we were looking to get maybe 1X our money back in that first year. We try to get that at least. Depending on the size of the organization and complexity, it’s possible. As you go into year two, year three, you're almost looking at a multiplier reflecting that year. For example, a four-year-old program might get a company around 4X, if not more, in return. Of course, that also depends on how far you've implemented this product. You need to put money in to get money out, in a sense.

If you've got a pipeline of X and you only have three developers, you can only chew through that pipeline at a certain current rate. You want to look at the value and say, "Well, what if we doubled our staff?"

I have a calculator that shows, for example, if you have $10 million of savings sitting on the table through 20 things in the pipeline. If I put one developer on that, it will take me three years to go through that and build that out. At the end of that $10 million of value, imagine if instead, you had everything all automated on day one. That's a total max value, and you would get somewhere around 23% to 30% of that value returned.

If you double that or if you put a staff of three developers on that same pipeline, you finish earlier and you get about 75% of the total value. If you go to four developers or five, you get closer to 83%. Now, if you put 20 developers on there, you're only going to increment it to 95%, however, then you’ve just increased your total cost as you have to try managing 25 at the same time. The main idea being, based upon your pipeline and the size of your team, you can potentially increase your total return value within a fixed time.

The ease of the use of creating the building automation is actually improving year over year. For example, there are some training programs for UiPath, and it generally takes about a week to get through it. That’s on UiPath Academy.

If you actually use it with modern design, modern objects, and all the new things that have been released recently, you actually save time on training. If that shaves 20% of your training, you can also shave 20% off of your building capability or the requirements. BY using UiPath Academy, you save time on your projects.

It's fairly easy to learn, as a solution. However, it’s not that easy where you're just going to throw non-developers into it. Your first three days of UiPath training are actually doing .net. That's the one thing the market puts out there incorrectly is that your operations team can just jump on this. You still need a developer mentality as you're still dealing with exceptions and things that aren't the way humans think.

That said, in terms of usability, it's highly useful.

UiPath Academy helps streamline and keeps employees up to speed in the solution.

The biggest value of the Academy is that it's free. That's a major piece. It's fairly well organized, and they put things into channels based upon what your role is within your RPA program or your business, and that helps you stay focused in terms of what you need to learn.

What needs improvement?

The solution needs resource locking. This kind of leads toward scaling which is one challenge. It's not major. However, it is when you have multiple bots running the same process and they need to access the same piece of information to read and write. There's not a strong capability to manage the lock and have the capability to say "I have ownership of this file. No one else can touch it" and then release it, allowing the next one to pick it up. That's a key differentiator that I see between them and Blue Prism. That one feature is lacking.

The studio design is a little different. If you go from one tool to the next, you might be a little shocked at how things are organized. I don't see them changing that any time soon. However, the design could be improved upon.

For how long have I used the solution?

I've used the solution for about four years. 

What do I think about the stability of the solution?

The solution seems to be stable. I haven't had any issues yet.

What do I think about the scalability of the solution?

The solution is very scalable. I haven't pushed it to 100 plus or anything like that. However, based upon scheduling and triggers and SLA management, it's much easier to scale.

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

We did work with other RPA solutions in the past. The differentiation comes from the triggers, and the attended automation. The platform now is a big part of this. 

For example, Blue Prism is one of the tools that we work with as well. If you want new functions, new features, say, process mining, you have to go to Celonis or someone else, whereas UiPath is providing this platform with new capabilities almost daily.

It also depends on what kind of COE you want to build. Looking at Blue Prism, they have a nice UI as well. It's very business-focused. With UiPath, you need to have some developer capacity. There's .net in there, and some people just might not get that. However, at the end of the day, if they don't get that, should they be building processors? There's a bit of a challenge there.

How was the initial setup?

The initial setup is not that complex. It's more about the client's setup. For example, the domain, entries, things like that, would add to the complexity you face.

If everything goes well, you can get things set up probably in a few weeks. I would say a month or so is needed for deployment and implementors should set expectations. For example, security depends on how much the organization is ready to take it on as well. If you don't get their buy-in right away, then you're just going to get delays.

What was our ROI?

Most of the companies see a good ROI from the solution.

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

The pricing and licensing get a little complex. There are so many different options that you can choose from, and practice adds to the time to figure these things out. Whereas, with, for example, Blue Prism. It's a pretty standard basic model. UiPath gets a little hectic at times.

What other advice do I have?

The customers that use the on-premises version tend to use the latest version of the solution. 

While those using the cloud version of the UiPath apps feature are in the UK, the US users are not using that functionality. Mainly most of our focus has always been on RPA and then expansion. From what I've seen, we've mainly been using UiPath. At least on the North American side, it's been relatively new. That's why they aren't using apps yet.

We don’t have any clients that are using the solution's AI functionality in their automation program yet. I’ve only played around with it myself.

From a road mapping perspective, I'd advise potential new users that your key is the business case. If there's no business case, then this solution doesn't make sense for you to get involved or do anything else. The first part is to really understand the business case. Just to substantiate getting it into the company. Once you have that, that's basically your low-hanging fruit. 

That said, the key is not to hang everything on one process, not to sit there and bank it, as the concept is a program approach. Over time, it is going to sustain itself. Companies need to be ready to look at a process and think if it's a good idea first. And as you move through the steps, you're basically doing additional checks. As you learn about the process, you're also learning what it's like behind each process and what the value add is. At each stage, users need to ensure that it makes sense to continue. 

I'd rate the solution at a nine out of ten. While there's always room for improvement, market-wise they are at the top of their game. 

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 and reseller
PeerSpot user
Ramesh Kuppuswamy - PeerSpot reviewer
Senior Software Developer at a tech vendor with 10,001+ employees
Real User
100% error reduction, better customer and employee experience, and reasonable price
Pros and Cons
  • "There are two features that I like a lot in UiPath: one is the Orchestrator option, and the other one is the Studio option."
  • "The dashboard view could be more visually appealing. Dashboards in any software should stand out with colors, numbers, and other things, but in UiPath, the dashboard is not that visually appealing. The UiPath team could make it more visually appealing for us to get more insights."

What is our primary use case?

My main use case for this product is process automation. For example, we use UiPath to make quick and easy applications for our internal office use.

How has it helped my organization?

It has reduced repetitive tasks. We now have more efficient processes. Manual testing was one of the time-consuming tasks that we used to do. Our testing team used to spend days and nights testing. UiPath has completely boosted the process. For example, previously, if we needed three employees to do a particular manual test, now, because of the automation that is available, we require just one employee. It has saved a lot of time, and it has also enabled us to deliver better-quality products. With automation, less manual work is involved, and the quality of the product that we deliver is very good. We have also been able to automate a lot of tasks, such as compliance tracking.

It's very easy to build automations using UiPath. Most of the things are just drag-and-drop. People with zero to minimal coding knowledge can build applications using UiPath. It's straightforward. One thing that facilitates this is that a lot of in-app guides or inbuilt tutorials are available, which makes UiPath very easy for a beginner who is starting out with UiPath. With such a good knowledge base, it becomes very easy for them to get a grasp of everything and start building applications.

It enables us to implement end-to-end automation. It also improves the employee experience. In software development, especially in the field of testing, there are many repetitive tasks, and they are prone to many manual errors as well. Automation through UiPath boosted employee morale, and it also improved the customer experience. We have been able to deliver better products on time to customers with UiPath.

It's a cloud-based solution, and it has helped to minimize our on-premises footprint.

With the AI functionality, we have been able to identify areas where automation can be implemented. We are trying to identify where process automation can be brought in and efficiency can be improved. The AI functionality is good, but there's a lot of initial work that needs to be done for this. It has enabled us to automate more processes. Within a month, we have been able to automate around 40 to 45 processes that were pending for a long time. It has definitely speeded up the entire process.

It speeds up digital transformation and also reduces the cost of digital transformation. Less manual intervention is needed, and less manpower is needed. It definitely reduces the overall cost for the company. Also, when something is automated, it's very quick. Redundant or repetitive tasks are completely reduced, and a lot of time is saved. So, it definitely saves time and cost.

This digital transformation didn't require expensive or complex application upgrades, or IT application support. Everything was inside UiPath. We just took some additional training from UiPath to get it implemented. Other than that, we did not use anything.

It has reduced a lot of human error. With manual testing, there were a lot of errors. With automation, that has been completely eradicated, and a lot of time and effort has been saved. It has reduced human errors by 100%.

It has improved our customer experience as well. We provide services to our clients or customers. Any human error leads to a delay in delivering the application. With automation, we have completely removed human errors, and we are able to satisfy our customers. It has impacted the retention of our customers.

It has freed up employees' time as well. A task that previously required three or four employees just requires one employee now. We do not spend all our time on a process. Once we implement and start an automation process, everything happens automatically. We can concentrate on other aspects of software development. It has saved 20 hours per week or 4 hours per day. 

It has saved a lot of costs for us in terms of employee reduction. We now need just one employee for a task rather than four employees. So, there are savings in terms of employee salary. We are also able to retain customers better, which has improved our revenue. Overall, about 25% of our cost has been saved. We were losing revenue and customers because they were not satisfied. With UiPath, our efficiency has improved, and the time to market has reduced. 

What is most valuable?

There are two features that I like a lot in UiPath: one is the Orchestrator option, and the other one is the Studio option. I especially like Orchestrator because it's very insightful for us. It's like a centralized hub to manage and maintain all of our process automation and task-mining. It systematically organizes each and every folder so that it's easy for us whenever we need to know, set, or take something. Studio is where we primarily do most of our designing. It's a very good tool. Most of it is drag-and-drop. These are the two main useful features for us.

What needs improvement?

The dashboard view could be more visually appealing. Dashboards in any software should stand out with colors, numbers, and other things, but in UiPath, the dashboard is not that visually appealing. The UiPath team could make it more visually appealing for us to get more insights.

Another improvement area is related to product updates. Earlier, we used to get monthly updates about the product, but that has stopped now. If they could bring that back, it'll be very good.

We have recently tried the AI functionality. There is a lot of learning that we need to do with regard to AI. It's good, but it's not as smooth as Orchestrator or Studio. The AI aspect of the product could be better. We're currently working on allowing the AI to automatically detect areas where automation can be brought in and efficiency can be improved. That needs some more refinement. It's currently not straightforward. Sometimes, it just repeats whatever it said previously, so nothing new comes out of it. The AI aspect of the product can be much more refined. Apart from that, I don't have anything else. It's a well-thought-out and complete product. It's very easy to use and easy to understand.

For how long have I used the solution?

I've been using UiPath for around a year.

What do I think about the stability of the solution?

It's a cloud-based solution. It's very stable, and we just need to make sure that it's up to date. Personally, I have not seen any bugs, errors, or performance issues with this. We are not using an on-premise model. It's cloud-based. So, the service is always available, and it's always quick. It's very stable, and I have no complaints.

The applications that we develop with UiPath are also very reliable. They don't crash or have any performance issues. They are very stable and reliable.

What do I think about the scalability of the solution?

When we started with UiPath, our main use case was to be able to quickly and easily make applications for internal purposes, but now, we are doing a lot more with UiPath. We are doing compliance, and we are doing AI-related process automation. It's definitely a scalable solution.

It's deployed across multiple departments. Each department has its own RPA functionality and RPA usage. In my department, 20 of us use UiPath, but I'm not sure about its users in other departments. 

How are customer service and support?

Their support team is very knowledgeable. Whatever issues we have, they try to explain them to us in a better way. The SLA or response time is pretty quick. It's 24 hours for us. I have no complaints. I would rate them a nine out of ten.

In addition to the support team that UiPath has, I depend on the user community for all my queries. I see the UiPath Community as the main support tool. It's my go-to space for anything related to UiPath, and I am very satisfied with the quality of the community.

How would you rate customer service and support?

Positive

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

I am not aware of any other solution that we used to use.

How was the initial setup?

It didn't take a lot of time to implement, which is a very good thing about UiPath. In about two to three weeks, we got the entire setup done. That was very quick.

It's a cloud solution. We have deployed it on AWS. Being a cloud solution, it requires very less maintenance from our side. That's one of the very good things about UiPath. We just need to make sure it's up to date.

What was our ROI?

We have definitely seen an ROI. Customer satisfaction has improved a lot. We have been able to retain customers better, and we have been able to reduce manual errors by 100%. 

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

Its pricing is straightforward. There are two editions: one is the community edition and one is the enterprise edition, which is a paid one. The paid edition is priced reasonably.

They charge extra for additional training and implementation, but that should be bundled up with the enterprise edition itself. All in all, it's reasonably priced.

What other advice do I have?

To anyone considering UiPath, I would advise checking out the trial version of UiPath before going on to the actual version. Before you start using UiPath, there are a lot of things you need to get your head around. People who generally use UiPath have zero or minimal coding skills. This is something that you definitely need to know.

You can try out the UiPath Academy as well. They provide certification courses. I have not used UiPath Academy, but I have seen my team using it for the certification program they offer. I have heard that it's very good.

I would rate it a nine out of ten because I have not faced any issues with the product. Whatever we wanted to achieve with this product, we have been able to achieve.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
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.
Flag as inappropriate
PeerSpot user
Digital Strategy Manager at a energy/utilities company with 10,001+ employees
Real User
Top 5Leaderboard
We have saved dozens of FTEs annually and increased the quality of processes where automation has been deployed
Pros and Cons
  • "The most important and valuable feature of UiPath is the ease of creating automations. It's a workflow-based model. End-to-end coverage is, no doubt, very important, because when you use a fragmented solution, the overall process flow becomes shaky. UiPath has the required capabilities to create an end-to-end solution for a business case."
  • "The cognitive area is one where there is room for improvement. Automation Anywhere has grown in that area, whereas UiPath still is more dependent on third-party integration. That is something which they should be focusing on more. They should acquire a product and get it integrated."

What is our primary use case?

We use UiPath for cases where we have to do a workflow-related mechanism. Most of these use cases are small, Excel-based solutions and desktop-solution-related workflows, where one or two applications have to be connected, along with the Excel operation, for the end-to-end workflow creation.

We use both attended and unattended automation.

How has it helped my organization?

We have created 10-plus solutions using UiPath, and the savings that have been generated from these solutions are around $1 million. They are very cost-effective solutions: finance, order-to-cash, and protocol-to-pay processes. It has created value on the higher end, because the processes were quite cumbersome. We re-engineered the processes and started using UiPath for workflow automation.

We have saved roughly 50 FTEs on a yearly basis. It also enables us to use a lower skillset workforce, which is a cost-effective measure.

Quality, no doubt, is one of the key parameters of automation. UiPath has resulted in quality improvement for the overall processes where it's deployed.

It's on the OCR side and the workflow side where UiPath creates value to us.

What is most valuable?

The most important and valuable feature of UiPath is the ease of creating automations. It's a workflow-based model. End-to-end coverage is, no doubt, very important, because when you use a fragmented solution, the overall process flow becomes shaky. UiPath has the required capabilities to create an end-to-end solution for a business case. For our scenario, the business cases are quite small. That way, the turnaround time to create a solution is short and it becomes very easy to deploy, which is quite helpful for us.

Another important feature is the OCR capability, which integrates quite easily with other kinds of tools. We have integrated with ABBYY and we have even used the Amazon OCR engine. From an integration perspective, it is scalable enough to integrate with third-party solutions, whereas that kind of thing becomes a bit of challenge when we use Automation Anywhere.

We are able to use Python scripting and Python libraries for data extraction.

We also use the solution in creating attended automations. They are very much division-specific and are currently used by the procurement and the finance teams. These are on-demand, data reconciliation activities that are performed once a week. The bot is clicked by the person who is attending, which is generally a procurement or a finance guy. These are tedious activities so that's why we have the dedicated license for the attended format.

It is quite user-friendly with the drag-and-drop functionality. It has connectors which are quite suitable and industry-standard for basic applications that we use on the desktop, like for the Microsoft suite. From an integration perspective, it has done well.

We have also used its selector technology to automate processes with dynamic interfaces for one of the finance applications, where the UI screen is changing.

What needs improvement?

The cognitive area is one where there is room for improvement. Automation Anywhere has grown in that area, whereas UiPath still is more dependent on third-party integration. That is something which they should be focusing on more. They should acquire a product and get it integrated.

For how long have I used the solution?

I have been using UiPath for around two and a half years. I have used both Automation Anywhere and UiPath. We have both tools.

What do I think about the stability of the solution?

UiPath Robots are quite robust, and from a maintenance perspective it has become easy, if you create logs. It's pretty good.

What do I think about the scalability of the solution?

In terms of scalability, as I mentioned, it has certain challenges, but with the minimal capacity which we are running, it becomes easy to maintain the bots.

We have 10 to 12 automations already in place, and there are around five to six more in the pipeline, which are still being rolled out. The RPA tool we used is determined on a case-by-case basis.

How are customer service and technical support?

UiPath technical support is pretty good. Most of the answers are provided by the community forum. If you raise a ticket, they are proactive in getting back to you and addressing the point. It's good.

How was the initial setup?

The initial setup was okay. I was involved in the setup of Automation Anywhere four years ago, and with UiPath. Compared to Automation Anywhere, it was much smoother because the community side is quite good with UiPath. In the early days when we were facing issues, we had the UiPath community support to find answers. We did not have to raise a ticket with UiPath because we were able to get our answers in the community forums.

The first case took us around seven to eight months to put in place. The first one is, obviously, always a tricky one. We also picked a use case of medium complexity and it took a bit of time. Later on, we started building more of a workflow solution using our low-cost workforce and, after that, the journey was quite smooth. Initially there were some hiccups, but once the team understood the tool itself it became easy.

We deploy developers who require a lower level of skill sets, developers who do not have that much training. They are normal .NET developers whom we train for one and a half months on UiPath and they start developing UiPath solutions. We have a center of excellence with our developers who work on UiPath. We recently hired two more, so we now have around 11 developers who are working on UiPath.

Taking UiPath courses to get up to speed has been very helpful. I am certified for the tool because of the courses. The curriculum is at least on par with that of Automation Anywhere, although I would say it is much better. The only issue is that the courses are very limited. The AA University has increased to a vast number of courses, and most of them have become free for the end-user. The UiPath course material is good, but there are notably fewer courses and less certification available for people like us, who are more on the business side. AA has a business analyst program and a program manager certification, but I was not able to find anything specific like that in the UiPath Academy.

Our strategy with UiPath is that we generally go for unattended automation because that doesn't lock up our licenses for the bots. We prefer solutions which require unattended automation, because of a lack of budget and other constraints. From the deployment perspective, we have a dedicated server and we're following the minimum guidelines which are required to conform to the deployment standards.

What was our ROI?

The ROI generated is quite high because of the cost factor.

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

It is much much cheaper than the Automation Anywhere. That is a key differentiator. It is targeted at mid-level enterprises. It is cost-effective.

There are no additional costs beyond the standard licensing fees. We have taken few of the training-related services from them. Once we move to the cloud version we may require some consulting services to move from on-prem to cloud. That would be the only other cost associated with UiPath.

Which other solutions did I evaluate?

When it comes to the main differences between UiPath and Automation Anywhere, UiPath is cost-effective. It is quite a lot cheaper than Automation Anywhere. It is also drag-and-drop, a fact which makes basic automation very easy compared to Automation Anywhere. It's quite user-friendly. In addition, the OCR functionality is quite robust in UiPath because it also provides a third-party integration. Python scripting becomes easy and that means our OCR solutions are quite good. These are the pros of UiPath. 

Regarding the cons of UiPath when compared to AA, the first one is the level of scripting details. Custom scripting is quite lacking in UiPath. It's more a drag-and-drop functionality which doesn't allow that higher level of customized scripting when compared to AA. Secondly, the scalability is quite robust in AA as compared to UiPath. Even though we are not pushing the limit, the general opinion out there is that UiPath fails quite visibly when you try to scale solutions that involve operations plus a new product rollout. That's a challenge with UiPath. And, as I mentioned, AA has improved a lot in the cognitive area and UiPath has not reached that level. It relies more on the third parties.

What other advice do I have?

Even if you are a large enterprise and you're trying to start your RPA journey, UiPath is the answer. It sits in the top one or two solutions, along with Automation Anywhere. It's one of the leaders in RPA, and with the low cost model of the license structure, it is very easy to start with UiPath rather than with Automation Anywhere.

If you are looking for a strategic approach, where you have projected that within five to six years you will roll out 250 to 300 bots, scalability is something you have to factor in when starting your journey.

We haven't used the solution's artificial intelligence. We tried to run a PoC using a chat bot, but it didn't do well. I don't think UiPath has its own AI engine. They provide an API-level integration with other AI tools. We had a challenge there because most of the AI functionalities had to work on the cloud. We had to integrate with the Google Cloud and Amazon cloud, but both are in the public domain and transferring data from our office to the cloud was a challenge. We hit a wall. For that scenario, we moved on to Automation Anywhere, which provides us an on-prem solution.

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.
PeerSpot user
Enterprise Optimization | RPA | Digital Transformation | Intelligent Automation | Next Gen Tech at City National Bank of Florida
Real User
Reduced human error, frees up employee time, and offers a great ROI
Pros and Cons
  • "The time to value is excellent on this solution."
  • "In the world of NextGen technology, it would be ideal if they could speed up their beta products."

What is our primary use case?

We primarily use the solution for the typical banking and transactional use cases. An example could be something such as homeowner's association transactions. That incorporates multiple departments in a bank, including treasury management accounts and opening an ACH. All of those areas are very transactional in terms of the rules-based processes that they follow.

We also use the solution for wire transfers. We have a lot of those. Then, from a business perspective, we look at lines of business as well. It can be used for residential and commercial lending. It's very process-driven and very transactional. We're able to incorporate automation in those areas very easily.

How has it helped my organization?

The solution allows us to do more with less. If we have a relationship with a third-party bank to onboard with a thousand accounts with a 15-day turnaround time, depending on what the relationship is, without automation, without RPA, you'd have to hire at least 10 or 15 contractors to get that done. That’s from a contractual perspective, to make sure that you meet the deadlines. However, automation just allows you to scale. You can save the same scenario in multiple areas. The scalability and the time to scalability on offer are key. And that's where we see the value as an organization.

What is most valuable?

The time to value is excellent on this solution. It is incredible. Unlike any other technology, which is really generally workflow-related, this RPA will give you quick wins, as demonstrated by the return on investment.

The solution has saved costs for our organization. We look at it from different lenses. We look at it from an actual savings perspective. We forecast it and then we annualize it to understand where the product will be or what it will bring us in the long and not just short term. For us, it’s very ROI-driven.

I’ve been with the bank for nine months now, and we went from having two processes automated to now having actual savings of about a little over $300K. It's not bad. There are about 30 processes in production. If we annualize that and forecast out we can see how we can continue to grow.

We have been able to reduce human error. I would call that the cherry on top. You don't really track that until you have it automated. However, if the alternative is having end-users upset that mistakes happen, having the level reduction we’re getting is great.

The solution has freed up employee time by a lot. We see it wherever it's very transactional heavy, where we had multiple team members. Now the teams are built by bots and people. Where you had three people before, now you have a person and a bot executing. So far, we have likely saved, in these nine months, a little over 11,000 man-hours. That's quite a win.

This additional time enabled employees to focus on higher-value work. That’s the whole purpose. We tend to look at ROI, not just money. It's also what else are the employees doing. We’re saving money from a man hours perspective, and, from a cost avoidance perspective, we’re not having to hire. The folks that work for us actually can do valuable work. They can focus on better decision making, more time with the customer, better relationship making, et cetera.

My team has started to utilize the UiPath Academy. My team is composed of multiple different skill sets from PMs to BAs to engineers, and so forth. Even at the level of IT, with the teams that manage infrastructure, sometimes I have them taking some of the infrastructure courses in the Academy. The Academy works well due to the fact that they prep you to grow quickly. If you don't understand how the technology operates, it could be a little bit difficult. You do have to train a little bit to understand it a little bit, however, it's not very difficult, especially when you have access to the Academy.

Having the Academy has affected the process of getting employees up to speed big time. Their appetite to get better and better is just enormous - not just due to the fact that the product is good and it's providing that information to do that, but also due to the fact that they're seeing results. That's helping them want to do it better and faster. It’s a win-win situation there.

The Academy has a really good curriculum for very particular skill sets. It's hard to be an engineer and have to learn a bunch of different stuff that won't necessarily concern you. UiPath has been able to really compartmentalize that learning capability so that it makes sense to different groups and speaks to their level of expertise. That’s probably the most valuable aspect of it.

What needs improvement?

In the world of NextGen technology, it would be ideal if they could speed up their beta products. My team handles all next-generation technologies that we implement in the bank. For example, we're looking at task mining right now. It's theoretical, however, that product is going to be tremendous. That said, it's still a bit in beta. For us, if they were trying to get new items a little bit quicker out there, that would be ideal. They're running with it, therefore, I'm not overly worried. They also want to provide a good platform for its users, and so I understand why they want to make sure it's good. The competition, in reality, even though it's growing, is not as strong. The feedback is just me being picky at this point.

For how long have I used the solution?

We've been using the solution since 2015.

What do I think about the stability of the solution?

So far, we have had very few issues and the issues really have been around very complex knowledge. We have reached out to UiPath to get advice, and they responded, and it hasn't been bad at all.

What do I think about the scalability of the solution?

Scalability has not been an issue. It's not even a topic of concern. The concern is more on the business side and can you manage the growth from a business perspective. The technology's there and I want to automate more. However, with automation, the question is if you can manage it.

We do have plans to increase usage. 

We have about 30 automations in place. That means about 60 to 70 people are using it. They work in shifts and they'll come in and they'll use their bots to process stuff while they do other stuff. 

How are customer service and support?

Technical support is great. In the times we've used it, they've come back relatively quickly.

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

I started with UiPath a long time ago and I actually worked for Automation Anywhere. I was head of their cognitive product. Therefore, I used them for a while. They're not a bad product at all. They're really good, however, their scalability is a little bit of concern. For us, coming back to UiPath was probably a good decision.

How was the initial setup?

The initial setup is complex. However, that's okay. It's also not supposed to be easy. You have to learn a little bit about what you're doing. Any technology would be a little bit complex. Once it's in, you can get that learning curve moving. With the actual users, that's where the trick of the implementation piece comes in. Once you're through it, however, that's where UiPath becomes really tremendous.

The deployment was maybe 60 days, however, it wasn't necessarily just because of UiPath. In banking, there's red tape. It takes time to get certain aspects approved. It takes time to get the right infrastructure in place. The enterprise has to be willing to put the time in just as UiPath has to put a certain time. It's a blend. As we were implementing, we were still putting things together and setting up governance. It was not just the technology. You still have to prep on the business side.

In terms of maintenance, on my team, I have about seven people, three engineers, a couple of business analysts, and a couple of PMs.

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

The pricing could be a little bit better for document understanding. I ran the pricing scheme for intelligent documents. With understanding at Automation Anywhere, there's room to maneuver. They can do a little bit better in making it easier for customers to dive in. I know it's available, however, it is what it is.

Which other solutions did I evaluate?

The organization evaluated Blue Prism, Automation Anywhere, and UiPath. 

We went with UiPath due to the fact that they gave us a good deal and we wanted to try it out. We started little. At the hedge fund, we're actually now at over three bots in production. Automation Anywhere's a little bit pricey at the moment. We just kind of pulled the trigger on UiPath and it was a blessing. 

What other advice do I have?

We're just customers and end-users.

While we are on-premises, we're starting to use the cloud including some of the modules from the cloud, document understanding, task minding, et cetera. We're using the latest version of the solution. 

I'd advise those considering the solution that there's a secret sauce to it. It's not just the technology. People need process systems and a really good partner. That's how you get it done.

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.
PeerSpot user
Michal Duda - PeerSpot reviewer
Senior Automation Developer at a healthcare company with 51-200 employees
Real User
Top 10
Customizable, user-friendly, and great for automating tasks
Pros and Cons
  • "The solution is user-friendly and has great training materials available."
  • "At this point, debugging, for me, is lacking the ability to edit on the go."

What is our primary use case?

I'm using the product primarily for building automation projects for shared services users. It's for internal customers. It's a shared services center for finance, HR, IT, and all processes like that.

UiPath enables you to implement end-to-end automation starting with process analysis, then robot building, and finally the monitoring of automation.

I use UiPath mainly for building a robot. I always use unattended bots. However, I also use it for task capture. I use the Task Capture feature a lot. It's pretty much a game-changer since Task Capture has become available, as creating documentation takes a lot less time than before. As for UiPath, I'm using it for building a solution and then testing using not only UiPath but also Orchestrator. In the end, we also use some document templates from UiPath. It's pretty much present all the way through the life of a project.

How has it helped my organization?

UiPath has sped up or reduced the cost of digital transformation in our organization.

For me as a professional developer, this is an obvious fact, however, people can notice that the robot can do their job a lot faster and they can concentrate on completely different things. They don't have to do simple tasks, repetitive tasks, and that's when they realize that this transformation is happening. Some people did not believe that it would happen so fast, yet, by using UiPath, we can prove to user that a process can be transformed into an automated one in a really short time.

It's reduced human errors in our company as well. I can use an example as a VAT declaration. That's one error that would cause some financial consequence for our business. After creating an automated project process, it is impossible for a declaration to be submitted with an error. It's basically eliminated typos or human errors in the case of VAT declarations and financial consequences.

The solution has freed up employee time. It's difficult to estimate how much as there are a lot of projects and I'm not the only developer on. However, thanks to my bots, we could free up, so far in half a year in this company, two FTEs, two full-time employees. Obviously, it doesn't mean that these people were let off. They are doing their job, however, they've just got different tasks, more complex tasks to do.

What is most valuable?

Mostly I'm using Studio. This is my main tool for work, and, for Studio, I can say that this is my favorite out of all the automation platforms. 

I like the fact that you can use and customize activities from the marketplace. The fact that even though the built-in activity sometimes cannot cope with some tasks, you can still find solutions outside of UiPath, internal kinds of built-in functions. You can use the third-party package marketplace. 

I like the way it handles debugging as it's very comfortable and it keeps the project under control. 

I'm also using Orchestrator. The newer version of Orchestrator is really very user-friendly and it's easy to manage projects there.

For basic automation, it's very easy to learn and it's easy to use. It's intuitive for basic functions. However, for more complicated automation, it gets more complicated. This is expected. The more advanced the project, the more advanced the skills you need. That said, as a basic product for simple automation, it's very easy to use.

The solution is user-friendly and has great training materials available.

I use the solution for automating my own work sometimes. I work at building small robots to make work go faster. For example, I'll create a robot that will help to create documentation. For example, analyzing arguments and workflows inside a project and outputting them in a DXC file or things like that. It's small ad hoc automation that makes life easier.

What needs improvement?

At the moment, I'm pretty satisfied with it. Thinking about UiPath, I can't see any downsides and the downsides are in like companies' infrastructure.

At this point, debugging, for me, is lacking the ability to edit on the go. It lacks the ability to stop the process on a breakpoint and being able to edit or even go a step back. At the moment when I'm debugging I'm only able to stop the process, check the locals etc. It is not possible to change anything in the code, go step back and try the changed code. You have to start the debugging process from the beginning. It is just slightly annoying and it was there since I started with version 2016. It's not a showstopper at all, just adds some time to development. I'm not even sure it could be done technically, it's just a wish.

For how long have I used the solution?

I've been using the solution for about four years at this point. I've used it for a while. 

What do I think about the stability of the solution?

There are occasional errors happening, which cause the software to freeze up. However, this is not more than once every two weeks and I'm always able to recover the project. I would say it's stable. Regarding working automation, I also have no problems as the errors that we have on ready robots never result from UiPath's issues. They result more often from infrastructure issues or robot problems.

What do I think about the scalability of the solution?

Regarding UiPath scalability, it's great. It's one of the biggest advantages. Over the years, you're able to build a library of modules that sometimes make your work a lot faster. You can use a few modules and you will have 70% of the project done. Every module that you work on, which is new and can be reusable, is very easy to make into libraries and to reuse.

In my organization, closest to me, there are only about five or six people on the solution. However, we also use external contractors and consultants who use UiPath and there are even UiPath MVPs there. That said, in my company, it's only developers, operators, and a project manager.

We have plans to employ more developers and to increase usage. 

We have an RPA department, which is using it and it's cooperating with all other departments in terms of creating automation. We have specialists that are specializing in using UiPath for automation. We create automation projects for every department that requires it. The people who are using UiPath are using it pretty much full-time. It's a full-time development. We are planning to increase the size of the development team as the projects are flowing and the backlog is growing. From the business side of our company, the satisfaction is high. The demand is growing.

How are customer service and technical support?

The solution has exceeded my expectations over the last few months and technical support overall has been great. The way they approach customer service and help us through issues has been great.

How was the initial setup?

The initial setup is pretty straightforward. I'm not a system admin or anything like that and I was able to set up UiPath on the server. It's pretty good.

How long it takes depends on the database that I'm working on. That said, last time it was not even the one full working day. It depends on how much data you have to back up. Usually, it's a few hours.

What was our ROI?

While I'm not the correct person to ask about ROI, I can say that UiPath has reduced the cost of our automation operations by making it 30% faster. 

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

I don't know the exact prices, however, I know that compared to other companies, other solutions, it's the best value for money, at least in our country.

Which other solutions did I evaluate?

I tried Automation Anywhere and also Blue Prism. At that time, there were only these three available for us. That was four years ago.

What other advice do I have?

We are customers and end-users of the solution.

We use the enterprise edition of the solution.

At the moment we are not using the newest version. It's 2019.

It was not my choice to use UiPath. At the beginning of my automation career, it was chosen for me. However, I was able to test other automation software and give my feedback to the employer and UiPath was the winner for me. At that time I was a finance worker. I was not a developer, a professional developer yet. For me, it was the user-friendliness and the way that you could very easily start your adventure with it, and then learn as you go. I have to say that the training packages for UiPath were very good and are enough to make you start working with it.

In my experience, I would say that it is the best platform for people who are willing to learn to automate. Also, if you want to use automation software, you have to consider hiring someone who has experience in it. Even though UiPath is so user-friendly and so intuitive, you still need to have a professional who has some experience.

It's very important to educate people to make them aware of what the RPA is. To be honest, from my experience, humans are the weakest link here, and people who are submitting, for example, input data for robots, cause the most problems. It is important to invest in the education of people and to raise awareness about RPA. 

I'd rate the solution at a ten 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.
PeerSpot user
Mukesh Kala - PeerSpot reviewer
Application Development Senior Analyst at a tech services company with 10,001+ employees
Real User
Top 10
Reasonably priced, scalable, and excellent for creating automation protocols
Pros and Cons
  • "The solution reduces human error significantly."
  • "The should be more out-of-the-box models if UiPath keeps adding on."

What is our primary use case?

In our organization, we are using UiPath as a service model. It is an on-premise model where UiPath is deployed on-premise. We are not using it on cloud services. 

We have a center of excellence that has been set up to communicate with UiPath for all the licenses, for all the tools, et cetera. Individual teams will connect and will communicate with the development team to get those licenses. For the team structure, we have a COE manager, and a COE is again communicating all the relevant information to the teams.

First of all, you would have to go and submit an idea to the COE team. The COE team will review and see this is the correct candidate for our solution and we can leverage it as automation. They provide us with the required licenses and the cycle continues.

The use-cases for the UiPath are limited. For example, if you are coming from a banking background, there would be use-cases it comes from the data solutions. If you are coming from an insurance background, would have use-cases where you would have benefits that are being reconciled. Healthcare might be dealing with patient data, et cetera.

If I talk about the support teams, in general, the use-case for the UiPath is as a ticketing system, where you have a lot of data to add to the queue to remove the need to add items manually.  

UiPath has the ability to implement with multiple systems. You can extract the data from any other application, click the data to enter the specifications, and start the automation cycle. That way, you have a technology that helps you to build a fully automated enterprise.

Our use case depends on the client and their needs. It's specific to their industry. We basically use the product to build automation for them.

How has it helped my organization?

We have seen the benefits both in terms of cost-saving, and time-saving. If you are doing automation which a human or an entire team is doing, let's say five hours a day, and there are seven to eight people doing the same amount of stuff, then you can automate that. 

When it comes to automating your process where the company is paying for software if you can use it to make robots that take energy away from repetitive tasks, you end up saving a lot of man-hours - which helps pay for the software.

Savings are measured both in terms of active saving or cost-saving. Then again it entirely depends on the kind of automation you're organizing. 

What is most valuable?

The most valuable feature of UiPath the process mining. The half capture was a tool that was provided by UiPath in the earliest reviews which simply allowed you to record the operations

It's great for automating tasks specific to business cases. It makes it very easy to do so as well.

The solution offers pretty good analysis capabilities.

The solution ensures there is proper documentation throughout the process.

The product creates a kind of skeleton for developers to help them work faster. 

UiPath is a low-cost platform.

If you are someone who is coming from a business background, and you don't have much coding experience, and you don't want to go through the coding world, UiPath, has UiPath StudioX. With the help of UiPath StudioX you can automate your items to read emails, download specific things, and do other small automation tasks that do not require advanced coding.  

If you are a developer who is more into coding and wants to do more coding, you have Studio and Studio Tool. Based on your level of expertise, UiPath has various levels of product: StudioX, Student, and Studio Pro, for example. It is always good if you have a programming background as sometimes you might need to write a small piece of code, however, it is a comparatively very easy task compared to the other traditional programming languages where you have to write a lot of code to do simple automation.

With the application of AI in recent releases, automation such as document reading can happen faster.

The UiPath app feature has increased the number of automation you can create while reducing the time it takes to create them. Recently, we had a UiPath hackathon which was contacted by UiPath for automation. We went to an NGO, and, for that NGO, we created a solution with the help of UiPath apps. For example, we used to create the invoices that would take seven to eight minutes to manually create. However, with the help of UiPath apps, we were able to do the same path in less than one minute. We have seen a drastic change.

The solution reduces human error significantly. When you are doing a process for more than five hours, you might deal with human error. However, robots don't make mistakes and can run 24/7 without issue.

What needs improvement?

You do need some coding experience.

AI is not available on older versions. I don't know if it is available in the latest versions of this review. Most enterprises, I'm working with still are at the previous version of the UiPath studio.

UiPath needs to enable more of the features which are available. For example, today, if I have to implement an automation path for the mainframe application, I cannot do the mainframe application without the client. I cannot just do a trial. If UiPath could create dummy applications for the developers who want to try new features, that would be helpful. 

The should be more out-of-the-box models if UiPath keeps adding on. Recently they have added a model in their AI section. However, it would be useful to have out-of-the-box models direct themselves towards plugins. 

You need to continually update the solution as, if you don't, after a few months you won't recognize the product due to all of the new releases. It will be like using a completely new device.

For how long have I used the solution?

I've been using the solution for five years. It has been a while.

What do I think about the stability of the solution?

Stability-wise, UiPath can handle the different varieties of stability on the applications you are automating. 

For example, if you choose to automate applications that are expected to change in the next few months, then UiPath cannot help you. That takes an entirely different form of planning. However, the more stable the process, the less likely any part of the process will change, the better UiPath can assist. 

What do I think about the scalability of the solution?

The solution is scalable. If you have to add new functionality to the robots, you will find that is definitely scalable. Let's say you have automated a process and you are getting 1000 tickets only, and then you suddenly get an influx of 10,000 tickets. You don't have to go and run and change your code or anything. Scalability-wise it is just with the click of a mouse that you can handle the change. And, just as easily, you can decrease usage if there are only a small amount of tickets. While developers and coding will be necessary to make it happen, I would say the solution scales extremely well.

How are customer service and technical support?

I have not contacted UiPath via the contact center. The firm I'm working for has a center of excellence. We do not, as individual developers, directly communicate to UiPath. There is a team that sits in the company that communicates with UiPath, as we're an enterprise. We don't have direct access to the UiPath team.

That said, I do interact with them on the community edition, which I also use, and I find that if I raise a ticket, they listen to my feedback and adjust accordingly. They're excellent.

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

I have not used any other solution.

How was the initial setup?

The initial setup is straightforward. From an enterprise point of view, from the client's point of view, there are certain restrictions that the company might have in place that could affect the way it's set up. 

The company needs to have a checklist to ensure it's set up optimally.

That said, there are no drivers, no scripts, nothing. Everybody can do it. You just have to click on the approve button, select it, and the job is done, that's it.

We do our own implementation strategy, however, I am not directly involved in what exactly has to be implemented. There are separate teams for that.

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

While I can't speak to how much users pay for enterprise-level editions, I can say that their community version is quite good and free to use. I've used the community license for the last five years and it's been great.

What other advice do I have?

I do mostly 90% unattended automation. I have created only one attended automation for a client and that was a specifically requested requirement. That was a bit difficult to automate. 

One piece of advice to everybody who is working in UiPath would be to practice and keep UiPath updated as the technology is growing and it is getting updated frequently. If you do not keep yourself updated for three or four months, you'll be dealing with a completely different tool. Keeping it updated allows for the gradual changes to come in in a way that a user can handle, as opposed to having to re-learn or re-discover the product if you have let updates lapse for months.

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

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.
PeerSpot user
Buyer's Guide
Download our free UiPath Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2022
Buyer's Guide
Download our free UiPath Report and get advice and tips from experienced pros sharing their opinions.