UiPath Reviews

I use this solution for mortgage loan origination, loan servicing, and IT administration. I'm currently using version 21.

We use the solution on-premises.

UiPath saves us a lot of time, which translates into operational cost savings. We saved around $40 million in operations last year by operating 140 bots in production. UiPath saves us costs, improves compliance, and helps with scaling up and down our operations.

We use attended automation but not on a large scale. We have three or four bots.

Attended automation improves our ability to automate processes that are more complex or involved. We use attended automation for use cases that involve websites that require actual users to log in. It's really helpful because a lot of use cases deal with federal websites and external websites where we need to download client information, credit reports, and fraud reports. That kind of information can only be done by a human, so attended automation is necessary for those types of use cases.

Right now, we aren't completely into AI. We explored document understanding for text extraction, and we know the capabilities. We haven't even started our ML journey, at least from the RPA automation perspective. They're still in the robotic process, so we haven't moved to include automation.

This solution speeds up digital transformation and reduces the cost. It gives leverage for the teams to transform digitally, because the traditional digital solutions take a long time to set up. It can take a few months for a solution to be in place. That requires expensive or complex application upgrades or IT application support to support the digital transformation. If we wanted to add a new app that would have oversight of all the loans being originated, it would take between two to three months to build UIs, dashboards, and all the features around it. With UiPath, the same kind of overview can be set up quickly: within two to three weeks.

The solution absolutely reduces human error. Most of our use cases involve looking at the input data, doing calculations, and updating fields. That always needs to be done by a human, day in and day out, continuously throughout a work shift. This RPA solution reduced that piece of human error drastically. I would say that more than 99% of human error is reduced.

The solution freed up employee time so they can work on other useful tasks. That's one of the main advantages of this solution.

Some of the processes have to be performed after hours and over weekends. When those tasks are automated, it gives valuable work-life balance back to our employees so they can do something useful with their time. The main ROI is saving manual effort, which is how we reduce our operational costs.

We see improvements in saved time, cost, quality, and risk production.

Attended and unattended automation, which support web and email automation, are the most valuable features for us. Building automations is easy and quick.

The solution enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automations. 
We aren't using the complete suite, like Process Mining, Process Insights, and UiPath Insights, but we use custom tools. Having end-to-end coverage of all these processes in one platform reduces cost and makes maintainability very easy. 

We use Kibana Dashboards with UiPath Insights, which was introduced within the last two years. For process analysis, we still use a traditional business analyst type of setup, but we don't use Process Mining. It's something we are exploring.

We use the academic courses to train all of our new developers and also upscale ourselves with new platforms. UiPath Academy is a single source of training for our team and it's free. We also hire college developers and new developers from other teams who want to work in RPA. We recently started StudioX citizen development. Academy is where citizen developers can get trained quickly.

It covers all of the various products, and it's easy to search through courses. We can skip different sections and get to the part we're looking for.

The UiPath community is a big and vibrant community. I think contributors are being rewarded for their contributions, and that happens in an organized fashion. That's the reason why people are so actively involved in contributing to the community. I would say that 90% of our development queries are answered in the community forum. It's really good compared to other platforms.

There are a lot of AI and ML-based enhancements that could be included in the core product and activities. Right now, there are plugins available from external vendors like Microsoft and Google. If those AI and ML activities can be provided out of the box for developers to use, that would really help the product go from an automation RPA to one automation suite.

I have used this solution for four years.

The latest versions are pretty stable. I haven't seen any issues with stability.

It's scalable. If we have enough bots, we can quickly scale up and down. If it's on the cloud, it's easy to scale up. If it's on-premises, we need to set up the machines, which takes time.

It can take a long time to get a response from technical support. They have to go through multiple hoops to get a solution, so that could be improved.

I would rate technical support as five out of ten.

Neutral

For the initial setup, we needed UiPath's support team to be on board. On-premises setup is always really tough. I think the cloud version would be really easy to set up, but we haven't explored that.

I would rate this solution seven out of ten. 

It's a pretty robust solution. When it comes to automation, it's pretty easy to set up and easy to use. My advice is that the cloud version is the best way to go forward when you're setting up UiPath.

Our primary use case for UiPath is the automation of some of our processes. The main departments that have been affected are accounts payable and accounts receivable.

We are developing expertise internally. At least for the first year, we worked with an outside consultancy to provide us UiPath development. They were working with the business team here closely, but also helping to train our people.

The main parts that we've got are in the area of invoice automation, but we also have some bots that deal with the automation of some of our engineering applications within Oracle.

We run six bots, primarily dealing with invoice automation from our suppliers. That is working in conjunction with Abbyy. So, part of the process is UiPath and part of it is Abbyy FlexiCapture. We also have some engineering applications in Oracle that we also use it for. Examples of this are updating bills of materials, or printing out invoices.

The key savings and kind of the real business case of the project were to do with invoice automation.

UiPath allows us to implement end-to-end automation. We utilize the Task Capture functionality for some of the initial parts. Then, building the bots is done with Studio, and Orchestrator is used for monitoring. It's complete, end-to-end automation.

The invoice reconciliation has been very useful. We now process 80% of our invoices automatically, of which 80% of those get no human contact. The remaining 20% of the ones that are automatically processed are either exceptions or they are certain expense items or the price doesn't match up. In this case, there's some human intervention, but we are getting a high percentage of things going through automatically.

This automation has enabled us to move some headcounts into different, higher value-adding activities instead. We have freed up approximately 10 full-time employees by using UiPath. We didn't let anybody go. Rather, they've been moved into other more creative roles.

The most valuable feature of UiPath is its usability. It's very easy to understand. I think in general, some parts of the process were difficult to grasp, and there were challenges along the way. But now at this more mature part, it's definitely increased employee satisfaction. People have been able to move into higher value-added, more enjoyable tasks.

We've got a group of citizen developers that work on UiPath. These are people that weren't developers but given a bit of training and its ease of use, they have been able to utilize it.

Both members of my team and I have used the UiPath Academy, and the training has been really good. It has enabled us to utilize the citizen developer approach. It is because of the conciseness and quality of the teaching that we have been able to employ citizen developers. We didn't really envision that as something that was possible, but given the ease and usability of the tool and the quality of the training, that's been possible for us.

UiPath has definitely helped to reduce human error. The main process that has gone through automation is the accounts payable process. Now, some of our suppliers may offer discounts and stuff like that. So, it's reduced the time for us to get things into the system. We've got increased visibility, and we've reduced the number of people working on this process, ultimately meaning cost savings as well.

The one negative that this solution has is its reporting. I found it a bit confusing because it was suggested to us that we use Elastic and Kibana for reporting. To me, this seems a little bit fragmented. I understand that UiPath has the Insights feature, but it wasn't what they recommended for us and I think the reason is that it isn't powerful enough for what we want to do. Ideally, we should not have to utilize other tools for reporting.

When it comes to speeding up our process, it has not made any impact. This is because the licensing and agreement part is quite time-consuming. Where we may have wanted to scale up quicker, we've been limited by signing contracts or getting things moving in that regard. As such, it's not really sped up our procurement process or enabled us to scale as quickly as we'd like when we wanted to.

We scale up some parts of the system quicker and we were seeing large delays in processing some of the documents that we wanted. This problem was that we didn't have the hardware or software ready for us to scale. So, in that regard, we've not found the ability to scale beneficial.

The error handling is in need of improvement. We'd had a problem tracking when errors occur, and troubleshooting how things are captured in production.

I have been working with UiPath for between 18 months and two years.

My impressions of the stability are largely positive. However, I'd like to see more emphasis placed on error handling for production.

With respect to scalability, I'd like to see it be made more fluid. It was a bit slow for us to be able to scale. If it was more elastic or there was a different way of billing it instead of having to sign up we had to sign up for a year-long license, it would have been useful. It wasn't that we minded the length of the contract or the cost. Rather, it meant that there were contracts that had to be signed, etc. 

With the processes that have already been implemented now finished, we're actively looking at where else it can be deployed. There is even interest from the executive team. They would like to see it used further.

UiPath has an active community but we've not really engaged with them very much. When we were in need of help, we contacted support and our account executives, but not the community.

The technical support has been really useful. I would rate them a ten out of ten.

In general, they've been very responsive, and easy to get them on a call if required. I've been really happy with the SLAs they've provided to us.

Positive

This was our first RPA implementation.

The initial setup was fairly straightforward. As we are using the on-premises solution, we've had to invest in additional hardware.

We used a consultant to assist us with our deployment. We definitely found it beneficial because it gave us experience. We didn't have any experience with RPA, and they helped us to get off the ground and provided some best practices.

There are three members of our team that are responsible for bot deployment and maintenance. One is a UiPath developer, another is a support developer, and the third is a business analyst.

We have definitely seen a return on investment.

UiPath has helped to both speed up and reduce the cost of our digital transformation. Compared to traditional automation approaches, it's been a lot quicker and less costly to implement. It very minorly affected us in terms of needing IT support. For example, we've had to work with our Oracle applications team, as well as our infrastructure team, in getting some of those parts set up. Overall, I've not found it to be burdensome.

UiPath has definitely saved on costs for the organization. I think that initially, there was some skepticism. Obviously, there were significant implementation costs but now, we're definitely seeing the fruits of that. 

Our total savings at the moment is between 50,000 and 100,000 per year.

The licensing fees are billed annually.

The company evaluated Automation Anywhere and Microsoft Power Automate before choosing UiPath. I can't speak to the pros and cons of the different options because the decision was made just before I became involved.

Overall, in terms of ease of building automation, our experience has been positive.

UiPath has features available for attended automation, although all of our automations are unattended. Similarly, we don't yet use the solution's AI functionality but it's something that we're really interested in starting to use.

My advice for anybody who is looking into implementing this product is to ensure that the processes they want to automate are standard and standardized. That was a key barrier that we realized, and it delayed things for us by quite a bit.

I would rate this solution an eight out of ten.

With federal governments, a lot of the use cases vary around what they're doing, however, it's just a lot of PDF, Excel, and Microsoft Suite automation and then interacting with their custom and web-based tools for subject information.

We don't use it a ton internally. We do more consulting services where we help other organizations get it set up. We're trying to look at maybe more internal ways to use it, however, most of what we do is external. That's just our entire model.

The typical spiel with UiPath is you're getting rid of the tedious and redundant work and you're saving time for people and bringing them up to do more human-oriented tasks.

Anything and everything under the solution has been very helpful for us. UiPath Studio is the most valuable for what we're doing simply due to the fact that it’s development software.

The most valuable part is how it interacts with the websites. A lot of the other automation solutions aren't doing that. A lot of what we do is involved in web-based automation and that's pretty key.

As a developer, the ease of building automation is great. I don't know if it's easy for the typical business user that I interact with. That's why there are professional services to develop and things like that.

We do use the UiPath Academy courses. UiPath Academy is great. It's one of the best online training platforms I've seen. That said, it’s an average user base that we're working with. I've had to teach people how to copy and paste. That level of user is not going to learn how to do variables and selectors and things like that.

The science of the software's easy enough to pick up if you know how to develop and I thought the Academy was fantastic at helping the learning process along.

The biggest value that the UiPath Academy offers is just the ability to train somebody up and know how to use UiPath in roughly a week.

The solution has saved costs for organizations. The exact amount is very tricky to quantify as I have multiple clients. It depends on which client we’re talking about. A lot of them are coming up in the beginning stages. My first client saved around 200,000 hours, which was significant. More recent ones may be in the tens of hours at this point. Those numbers relate to nobody specific, just a fledgling RPA program.

UiPath has reduced human error. That said there's plenty of bot error that occurs. You have to be aware of that if you are going to replace humans. I haven't honestly tracked it to see what the percentage is on errors on any of my projects, however, I would assume it is a reduction, and yet not quite 100%.

Right now, reducing errors is not yet important for our business and the businesses that we consult for. We don't really come across processes where there are so many errors. That's what we need to fix. It's not why people are using it. They're using it for the ROI value.

The solution has freed up employee time. It generally allowed the employees to focus on higher-value work and their level of satisfaction with the job.

I’m not sure if the Academy fulfills all of our needs in terms of staying up to speed with the solution. I haven't really gone back to the Academy after I first got through the development training to look at other solutions and stuff. I usually just rely on meetings with UiPath.

The stability needs to be improved, as does the scalability. 

We've used the solution for four or five years.

In terms of stability, that's where there's room for improvement.

It just comes down to a lot of selectors and items of that nature. Selectors can fail randomly and then start working again and can cause issues. That's been our issue with stability.

The scalability is directly tied to the stability. It's a lot harder to scale the solution to run on a lot of computers. Each of these has some unique issues when it comes to deployment.

With my current client, we have probably around ten users at this time.

Technical support is great. Also, the UiPath forum is super helpful, however, when I've used the license key, you got actual support and that's been really good.

I'm not aware of the company using a different RPA solution previous to UiPath. I personally only use UiPath.

The initial setup was straightforward. The deployments have taken six months to a year.

We have seen a return on investment from the companies that are utilizing this solution.

The individual robot and studio licenses are good. Usually what I see clients shake their heads at is the add-ons, the AI capability. Insights, for example, was very expensive. My client didn't want to get it due to the price.

Orchestra is usually acceptable as it's part of the package, however, the other stuff that's not studio or robot, usually, clients aren't, in my experience, interested in paying more.

We are primarily focused on UiPath due to the fact that that's what our clients are using, however, we're vendor agnostic. We support UiPath, Blue Prism, and Automation Anywhere as well. We have developers that are all trained in each of their usages. Whether we use them all at once or suggest them depends on the client. We have one client where they're using a bunch of them, however, most of our clients use UiPath I'm with the federal government, and UiPath is the only one that's really approved to do that. 

I'm not sure which version of the solution we're using.

We do not yet use the solution's AI functionality in our automation program.

I would advise new users to be patient due to the fact that it's going to take a while for it to get stood up. Also, when you are working with the federal government, there are lots of approvals. Other than that, new users should make sure they get use cases and have everything very well documented. Users need to understand all the decisions and the logic behind it. That's the main advice I'd give.

I'd rate the solution at a nine out of ten.

We're a revenue cycle management company for medical billing. We've reallocated our charge entry employees. We're using bots now to do the charge entry on medical claims and then also payment posting along with eligibility and AR. We've been able to reallocate about, just within this last year, probably eight employees. They've been reassigned to more valuable work - things that the bot can't do and actually requires a human to do. We've been understaffed, so it's actually worked out great for our company.

The ease of building automation isn't a problem. It seems to be very easy to do to a point. Our challenge is we work in a live environment. We're not able to use a test environment when we build things out. We have to go very slowly.

I'm not that familiar with the product, with the solution, however, the UiPath apps feature and OCR are great. That said, we're not using any of the apps currently.

The biggest benefit we've seen is the accuracy. Even just with employees calling in sick or not having enough staff. We’ve been able to fill those roles.

The robotics piece has been a huge thing. We're doing medical claims. We're always worried about claims not getting paid. This has been able to capture those claims so that people get paid the first time. One of the other things we track is how many times we touch a claim. For example, how many clicks. We couldn't do that before. That's been very valuable to us.

We’ve improved our efficiency in a way for sure. Even just our cost analysis has improved. When we do new contracts, we know what it's going to cost exactly.

I don't know if it's UiPath as much as just what we do is really complicated. Even the consultants that we've used with UiPath, even they've said, wow, this is very difficult what you guys do. There are a lot of moving parts, so it's not as much of a UiPath problem in terms of limitations. It's just our own processes.

Right now, I don't think I've been on there long enough to know if there are missing features or functionalities I’d like to be added.

I’m talking to people right now, to see how it can do things better or how we could use it more effectively. We’d like to discover what worked for other people.

We've been using UiPath for about maybe a year and a half tops.

I haven't had any problems or concerns right now concerning stability. The biggest concern I do have is that we've already invested six people in this. We're going to have a lot more that will, more or less, not have the robotic piece as part of their job. That work will be reallocated. I have about a hundred employees that UiPath could technically reallocate.

When I look at that, I worry about if something does happen or it doesn't work or there's no backup. Then, suddenly, I don't have employees. Right now, we can jump in and some humans can do the work if necessary. My concern is that in the future they won't exist. This hasn't happened yet. I hope it doesn't.

Scalability hasn't been a problem at all. We can just continue to add bots every time we need them. It's been easy.

We started with two. Three months later, we added another two. After another three months, we add another two. From our standpoint, it's great. My UiPath rep was shocked that I keep adding more, so that's good.

I have not used technical support.

That said, we had one issue with UiPath where something didn't work. We talked to them and it was taken care of within a couple of days.

My vendor is working with them. They mentioned there was an issue with insights that they are working through. Insights are still not quite functional, or there are some resources we need. However, the vendor is dealing with it directly. It's a work in progress. 

We did not previously use a different RPA solution. 

The initial setup was pretty easy. We didn't have any challenges with that. I contacted one of our vendors and they ran with it. We didn't have issues at all.

With the vendor, it took us about 30 days to deploy UiPath. After that, in terms of implementing bots, the first bot took us about three months. Once we did the first one, it just went really quick after that. We could reuse some processes which made it faster. There was a lot of reusing of the same. We were also internally understanding what information they need and how it works.

It was all new to us. I'm still learning the acronyms they use. We need to learn what they are talking about. We’re not IT-based at all. It's definitely different.

We had the solution implemented by a vendor. They implemented it all. We didn't have any challenges as far as that goes.

Our experience with the integrator was good. I would say that they didn't realize how challenging it was going to be or, at least, the person who integrated didn’t. At the same time, they know almost everything about my business now.

UiPath has saved costs for our organization. For example, we’ve allocated six employees that are paid around $40,000 a year and we've implemented six bots to do those same functions and they're around $8,000 a year. In a way, we’ve doubled our staff, and almost tripled our ROI.

We had a problem before with the pricing, however, for the most part, it's fine where it is now. My ROI is fine. It works great. I have zero complaints.

You have to do a package at a time. That's my only challenge, where sometimes I don't need that many licenses. 

When you first sign up, it's a package that can renew every five years. I don't necessarily need everything. I'd prefer just to pay for certain pieces. 

We did not evaluate any other options. We started using UiPath due to a referral at a neurological healthcare conference about four years ago. The speaker suggested UiPath. I actually didn't know of any other company until after we were on UiPath. We've since talked to others who have used other solutions and they mentioned that we made the right choice when we chose UiPath.

We started on-premise for the first six months and then we actually moved to the cloud.

We do not use their UiPath apps feature as of right now.

We are mostly using unattended automation.

We haven't really calculated the reduction in human error. We're just moving on to our Insights app. We're just getting ready to launch that, so we're not there yet. We don't know what that turnaround will be.

We do not use UiPath's AI functionality in our automation program right now.

Our teams have not yet used the UiPath Academy courses.

I'm a little concerned about having to bring on more people that are not in this industry. We're going to have to start them over from the ground up, which takes time.

When we first started, we wanted to know if it really worked. We got a certain budget and just started using it, and now I can say that yes, it does work. We can see that now that we've stepped back. We should have done it earlier. That's what I would tell people. I would definitely tell people to look at it first, before anything else. 

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

I've created an app for conversions and exchange rates. Every day I need the exchange rate of a certain currency and I use the API free exchange and UiPath.

It's also used for the reconciliation of invoices.

I've used it for the creation of an onboarding bot for employees to be onboarded onto a website with a remote system. I used AWS and a virtual machine and created a Google Form from there, and used UiPath's computer vision to do onboarding activities and extract data from files. PDF files can then be entered into the remote system. UiPath can be used to fill the forms.

It can be used for web extraction tasks as well, for example, for booking flights, where you can extract the flight details for particular search criteria and place them into an Excel sheet.

It can also be used to extract data from invoices in order to populate an Excel sheet, for a portable format. I've created a process that used documents as a learning model and extracted the invoices, using logic to output the transactions. 

Another use case I tried was extracting data from Amazon based on exact data. The same can be done on Linkedin using the Linkedin API. I'm fine-tuning and extracting data, putting the outputs on Google Sheets.

I've experimented with many use cases and automated many processes. 

It's low code/no code which makes it very easy to work with. 

Building automation using UiPath is easy. If I see a video or some instructions, I can do it. Things are doable. You learn. If there are use cases or there is information online, you can replicate the process.

Adding activities is easy. All of these partners are integrated into UiPath now - including AWS and G-suite. You have activities already built right into UiPath and they are working to make everything as low-cost as possible.

Then you have OCRs which offer the Document Understanding. I can do a PDF extraction using just OCR in a normal way.

I love the Document Understanding. You can see whether a document is valid or not. You can accept or reject. I came up with a .NET background. I used to write so many lines of code for doing a certain thing. Here, you have a for a loop. You don’t need so much code.

I remember when I used to work for a UK client, a gas utility, and at that time we used a read-through data driver, and got the Excel data, and again validated everything. However, for that, we used to write around two, three pages of code. Now, using UiPath, you just do a real Excel activity and you get the entire sheet. Automation has made our lives easier.

I can scale automation without having to pay attention to infrastructure. Now, since the cloud has come into the picture, everyone is going to the cloud and everything is easier but with the new cloud partners like Google, AWS, Azure, and Oracle. A company may not have its own on-premise orchestrator.

Earlier, you needed three servers for production, testing, and development. Since UiPath has both cloud orchestrated and on-premise, it's easier for organizations to use less physical space. For smaller organizations, they can go to the cloud. For larger they can have their on-premise orchestrator. It’s flexible.

UiPath enables me to implement end-to-end automation starting with process analysis and then robot building and finally monitoring of automation. There are many process mining tasks, capture tasks, mining, et cetera. More things have to be automated - such as deploying, managing, and enhancing for continual improvement. It has all the components.

For a beginner, end-to-end coverage may not be essential. When we talk about automation, we should know what can be automated so that we ease our lives and that doesn't mean we have to remove the resources. You don’t have to involve the employees. You just need to simplify the task so that there is continual improvement. Users should consider not only, how to automate but what needs to be automated. If it is automated, how it can be improved gradually and what are the returns? Sometimes that doesn’t necessarily mean you need end-to-end. You just need simplicity.

I do use the attended automation. For some processes, I use the attended automation for testing purposes. I use the attended if I'm using UiPath assistant, otherwise, it's normally background processes that are unattended.

Attended automation will be for Document Understanding when I'm training a robot, for example, for what is the format or validating the time I'm using attended one. If I'm asking a user for particular search criteria, or for currency exchange it's mixed but mostly unattended.

Both attended and unattended work together - the human as well as the robot. However, it depends on the scenario. Unattended means you are not dependent on any human resources.

The orchestrated cloud, which is a SaaS, it's quite helpful. If I just want to install UiPath studio in my system and I'm least bothered about what environment it should be, what infrastructure should be, where I'm going to deploy, it is quite useful and quite easy when there is a SaaS option available.

I’ve used the AI functionality for sentiment analysis such as getting reviews from the websites about a particular product or service.

UiPath offers great object detection where you have a magistrate and you can detect whether you want to detect the people. If you want to extract how many people are there in that image, for example, during a social distancing sort of event, that can be used for object detection. I've used object detection for images in terms of extracting a number of people.

I’ve trained the system to read different types of invoice formats. I've used the email or Document Understanding that can read separate invoices, receipts, utilities, et cetera. I’ve used the solution to create processes for invoice reconciliation.

The AI functionality is quite easy to use. For tollgates, for example, when they charge for tolls, the solution can be utilized for seeing the number plate, and through the image, get the data, extract the number of data from the numbers plate, use the driver information from the number plate of the car, et cetera. It becomes a very easy AI model. Without any type of knowledge in AI, you can use those out-of-the-box functionalities.

The more training you do with machine learning, the better results you get in the end.

I use the automation cloud feature.

We are not bothered about any patches or any work that has to be done to maintain the infrastructure; the vendor does it.

The automation cloud offering has helped decrease time to value, however, since I have not deployed real-time projects, I cannot give exact numbers on the decrease. That said, from my experience, I feel that it is true.

It’s my understanding that the automation cloud offering helps to decrease UiPath's overall cost of ownership, however, at this time, I just use the free version.

The solution enables you to be better and better with cloud features that are quite accessible.

In terms of UiPath Apps, I have used them, however, just for my own purposes, for my own training purposes, as I was learning. It is easy to use and pretty much drag and drop. For the basic things, the user can do a lot with minimal training. You can do everything with low code and less coding knowledge as well. A person may not be technically sound, however, even with minimum knowledge, they can create apps using UiPath apps. That's the interesting part of UiPath apps.

UiPath reduces the cost of digital transformation. It does not require expensive or complex application upgrades or IT support.

UiPath has reduced human error. For example, let's say I'm filling a form using a document. Typos, errors, spelling mismatches, et cetera, are reduced when it is handled by automation. When we automate this process, the robot minimizes the error since a human is not involved in this case of data entry. It will extract whatever data there is in that document and it will fill in the form. Similarly, for calculating Excel data, we can avoid calculation errors.

More videos are required. There are basic videos that can help you learn about the product, however, there need to be more in-depth videos to help you through certain tasks. For example, I was trying to use an API for conversion. I was doing it for a single transaction, one by one. There can be cases where it will not go for a simple conversion or simple transaction, and it will be a bulk action. In that case, I may need to upload a file. I was searching for an upload control however, I could not find anything to assist me.  It would have been helpful to find some sort of instructional video for this task. The file upload, where you upload a file and select a file so that you can extract data all those things based on that file is a commonly used feature - and yet, that was missing. 

UiPath apps may be able to increase the number of automation I can create while reducing the time it takes to create them. However, they need to elaborate on the process. I need more articles on that. From the point of view of the person developing the automation, I need more details on writing the correct code or doing the automation, which I hope will be coming in the next releases.

They require an improvement in the IEP. I don't know whether it's a bug or something. I find that, with drag and drop, you have to drag it in a particular fashion. 

When they add new features, they should offer some in-depth sessions on them to help people get comfortable with the changes. 

It would always be helpful to have new partnerships between UiPath and different cloud vendors. 

I started using the solution in February of this year.

I am on a gap year. I used to work for an IT company, and I have taken a gap. To re-skill myself I started learning UiPath. 

The stability is quite good. You have other options, such as Automation Anywhere and Blue Prism. UiPath will be like coming out with new revisions in the coming years that will continue to compete with those.

Even now, it's quite stable and quite reliable, even if the changes which are coming, in the much of the deployment, are felt good. There are frequent revisions. I have no experience in other automation, however, from what I've seen, even as it changes, it's stable.

Scalability is quite good. It has alliances with different cloud vendors so that you can scale your robots. You can have different instances, different new virtual machines, and in the cloud. You're not concerned about what to install and you just pay as you use. The cloud vendors make it very scalable. 

Once I am employed, I do plan to increase usage.

I use the forum for any queries. I didn't face user technical problems for any robots that I am using. I have not been in direct contact with technical support.

The initial setup is straightforward. 

You just go to UiPath.com and register with your user ID or any email ID. From there, you install the UiPath Studio and you set your workflows. Once you publish, you get it in your orchestrator, attach the process, create a job. And then you run it. 

It's quite easy to create a workflow, publish it, and deploy it in the orchestrator. Next, you have to tag the correct robot, the correct machine, and the correct sponsor. In any environment you want.

For small processes, the deployment would hardly take a few minutes to deploy.

Maintenance is light for the cloud instances and really does not need much. The cloud vendors do the work, however, users need to pay for the services which they use.

I handled the initial setup myself. I did not need an integrator or consultant. 

I can't speak to the exact pricing of the product as I am using a free version of it right now. I'm not paying any licensing fees to UiPath.

I shouldn't say you need licenses for many things for today, however, for working on Visual Studio, if you want to automate something, you need a license, which costs you around 5,000 to 6,000 Rupees. If you want to do some extra Microsoft office activities. You need the maximum office license, which is 70,000 Rupees. That said, with UiPath, you need not have Microsoft Office installed. You can still read the data and extract the data in an Excel format. You can then share the data from those automation activities with no third-party license cost and no software licenses.

UiPath can help save costs in an organization. There are so many legacy systems wherein you have so much data migration, and many things which are done manually can be automated and you can save resources while doing something new. 

I'm just an end-user. 

My first experience with automation was, "Okay, which product to learn?". After all the reviews and reading, I decided to start with UiPath. My previous background was .NET web development. I was a full-stack web developer with seven-plus years of experience and I found that I really like when a product is built on a .NET framework. I realized that "Okay, it's better to do something, learn something and I have a background of the platform so let's start from there".

When I started using this product, I found the academy was quite open, and in the forum, there were people who were training as well. I found that while I may not get 100% of the answers I need, 85% to 90% of the time the answer is there if you search. 

Many people do not know RP automation, and it's great that they have these free resources - which is rare for such a product. Each region has a chapter where people working in this area come and share their knowledge and experiences.

Currently, I'm using the 2019 version of the solution. It's not the latest, however, it's not much older. I'm using the enterprise as well, which is free for 60 days. I started using UiPath apps as well. I'm learning so I use the cloud orchestrator to deploy my processors. 

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

I use this solution to automate business processes that are rule-based. This includes the automation of different applications and background processes, such as posting invoices.

UiPath makes it very easy to develop automations. The interface is user-friendly and makes it easy to perform operations or use services, whether it is a database or another product. We can perform tasks on Microsoft Azure, for example. Many operations can be completed using inbuilt packages.

For whatever activity we want to perform, it only involves using the drag-and-drop capability, so it is easy to do. Anybody can do it. No programming-specific knowledge, like .NET, is required.

It is easy to develop custom components, which makes life easier.

UiPath allows us to implement end-to-end automation starting with the process analysis and ending with the monitoring. This is important to us because for any new process that we identify, using the task capture methods helps us to gather the documents that are required to automate it. After we develop the automation in Studio, we can easily monitor it using Orchestrator. It is helpful to have a complete solution from start to end, with all of the features that it has.

Using automation means that we increase our process output with minimal effort, which is something that every company wants to do because there is a saving in terms of manpower. It is definitely helpful in our organization.

The amount of time or cost savings depends on the process. For example, some processes that take four or five people to complete can be done using a single bot. Also, people can only work six or seven hours a day, whereas, with automation, the bot can run 24 hours a day. Not only is the process done more quickly but at less cost.

Attended automation has helped to scale RPA benefits because we have some scenarios where human collaboration is required. These are business-critical processes, so any level of automation is important for us.

In addition to savings in time and cost, UiPath further saves us money because of the reduction in human error. When a human is performing a task, mistakes happen. When the bots are used, there are no errors and when the number of mistakes is reduced, the business has more income.

UiPath has helped to speed up digital transformation, although hosting it requires IT support. For example, if UiPath needs to be updated or our infrastructure needs to be expanded, then it requires the help of IT support.

One of the things that I like is that they keep adding new features, such as machine learning models. For example, if you are reading a PDF copy of an invoice then the RPA should be able to identify and understand it. Rather than using rules to identify different formats for different kinds of invoices, machine learning and AI should be involved.

We are using the AI functionality and it gives us the ability to have more automation, saving more time and manual effort, and at less cost. This is possible because UiPath provides pre-built and pre-trained AI models that we can import, depending on the use case.

Some of the processes we have implemented are very complex, and these are the ones that we need AI for. Some of them involve human interaction and cover use cases such as taking different formats of invoices and pushing them to SAP. We have had good success when working with the machine learning capabilities.

The Action Center and Task Manager are very good for business users. The features are helpful because these days, business users are expecting more than a simple rule-based operation in RPA systems.

UiPath Studio integrates well with third-party tools such as Git. It is easy to maintain code from within Studio.

Many of the features that UiPath has are good, although better documentation is required for them.

I have been using UiPath for three years.

I have had issues with previous versions but the latest updates have resolved my problems. As of now, the stability is very good.

Scalability is very good in UiPath.

We have five UiPath users in our project; one is a lead, another is a manager, there are two developers and a consultant. At this point, I'm not sure if we plan to increase our usage.

I have been in contact with technical support in the past, and I would rate them a ten out of ten. They respond very nicely and help to resolve our problems.

When we deploy processes, it takes about half an hour. It varies depending on the process but half an hour is the average per activity.

UiPath is easy to maintain and support. We have a support team and QA teams, and they are responsible for monitoring the processes and the bots. They will check the activities that take place in production.

The number of staff required for maintenance depends on the architecture that the client has.

The licensing model is very good.

We chose UiPath because it is more flexible and has better licensing terms than some competing products.

We use some third-party tools in conjunction with UiPath. For example, to maintain the code and for versioning control, we use Git. We have two or three years of experience with Git and not only is it compatible with UiPath, but it is also easy to use.

My advice for anybody who is implementing UiPath is to start with the documentation. There is a lot of good documentation that includes best practices and plenty of examples. Using the documentation, one can easily learn UiPath.

I would rate this solution a nine out of ten.

I have been using UiPath to develop automations for my company. We are a manufacturing company that uses SAP as our primary enterprise application. We are currently meeting with many different business areas and hearing about all of the different processes that they would like us to automate for them. Since UiPath works within SAP, it should help us get some easy wins!

UiPath has allowed us to remove tedious work from our daily process, saving us hundreds of hours. We are currently using it to process separations for people leaving the company. This was a 100% manual process before UiPath and it was required to be completed hundreds of times each month. The team doing the work was extremely overworked and UiPath has allowed them to see a little bit of light at the end of the tunnel. 

Orchestrator is essential, but I love how Studio includes so many activities that are pre-programmed to do what is needed.

Who doesn't love the recording feature? A recording is great to use when doing the first build of new automations!

The most important feature of all is the UiPath community and the forums, as they have helped me with countless questions!

One of the problems with UiPath is that it doesn't interact with some programs, such as AD and Chrome, and it would be great to have even more included!

We have been using UiPath for six months.

So far we have not had any issues with the stability.

We have not scaled, but from what I've read it should scale easily.

We did not use another solution prior to UiPath.

Understanding how everything connects was a little difficult, but UiPath offers classes that walk you through the setup. With the classes it was much easier. 

We implemented using our in-house team.

Do your research, the infrastructure piece is important to understand before purchasing. Also, you need Orchestrator to implement UiPath properly, so don't let anyone tell you different!

Finally, you don't need to start with 100 bots... my advice is to start small and then scale. 

We looked at Automate Anywhere and writing scripts, but UiPath seemed like the best path.

There isn't much that I don't like about the product. I love all of the new features and products they are releasing this year, and I can't wait to see where this goes in the future.

We are using Studio, the Orchestrator, and both unattended and attended bots. We are using the product primarily to index and process patient records into patient charts when records come in from outside sources.

An example of how this product has improved the way our organization functions is that it has doubled the number of records that we process per hour.

The most valuable feature for us is the unattended bots. They are valuable because records come in automatically from the vendor with a cover sheet, and that cover sheet has a QR (Quick Response) code. An unattended bot will take the record, and based on the code can index it and upload it to the patient's record with no human intervention.

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of the UiPath platform as three right now. There are some nuances in it that are throwing some error codes when reading the QR codes. But we are in the process of working with UiPath to get that issue corrected.

Right now we have about five people in our organization involved in the automation program. We can expand that as necessary.

Our team used UiPath Academy RPA training. Two of the individuals on the team have gotten their certifications.

On a scale from one to five where one is the least beneficial and five is the most beneficial, I would rate the UiPath Academy as a four. The team really liked it. The two people that have certification are our two main developers. They had been doing their academy in concurrence with our deployment while they are still working on the project. They both said the academy has been very helpful.

We also have a customer support person dedicated to us. They call them Customer Success Managers. We use them and then we have also had to reach out to the home office in Romania. They are working on a solution for us right now. The service, on the whole, is very good.

I was part of the decision process in choosing UiPath as our RPA solution. We had not previously been using another solution but knew that we needed to invest in one because we looked at our employees' overtime records. We were paying for overtime and did not see the need to just for scanning and indexing. A bot can run 24/7, so the bot takes care of processes that can be automated instead.

The initial setup process was complicated because of us and the requirements of our organization. It was not because of UiPath. But even with those complications, from the time we purchased the UiPath license until we had our first robot in production took only about three months.

We did not use an integrator, reseller, or consultant for the deployment. We used internal staff and the UiPath engineers helped us along.

On a scale from one to five where one is very bad and five is excellent. I would rate our experience with UiPath as a five. They have been very responsive and have given us engineering support at no cost. They seemingly did that just to ensure that we were successful.

We are starting to see a return on investment. It has only taken us about a month to realize that. Basically, we have seen a performance benefit. Where it was taking a human about an hour to do ten records, we have estimated that we are going to be able to up that count to about 80 records an hour. One of the humans that is doing the manual part of it has already said that the product has helped double their workflow. The solution has also helped to eliminate human error by approximately 85%. I would say that it is going to save us at least 40 hours a week right now. I also think that is a conservative estimate.

For our licensing cost with this solution we have invested $90,000 right now, but that is to cover several facilities. The UiPath solution is not expensive considering that.

UiPath was the only RPA solution we looked at. They are TRM (Technology Reference Model) approved and they appeared to have the best platform.

On a scale from one to five where one is very difficult and five is very easy, I would rate the ease-of-use of the platform for automating our company's processes as a four. The UiPath product has fit our model the best. Number one, because in the VA (Veterans Affairs) hospitals the RPA solution has to be TRM approved and not all RPA solutions are. They have also been very helpful because we have a little bit of a unique system. There are some nuances in an older system that we are still using that can not be changed at the moment. They have helped us work around those issues and they have provided the technical support that we needed.

On a scale from one to ten where one is the worst and ten is the best. I would rate the product overall as a nine. From everything that I've heard from the staff, the ease-of-use and the effectiveness of it are really good.

If I were to give advice to a colleague at another company who is researching RPAs, I would tell them to go with UiPath because of the product and the culture of the company. I think the culture of the company is one of the reasons that you are going to ensure that you will be successful.