UiPath Reviews

We are using Orchestrator, Studio, attended and unattended robots.

I am on the business analyst side, so I do not have much experience with Orchestrator.

We are using this solution to automate processes for our clients. They typically have mundane processes or something that's super repetitive, that we're able to quickly automate for them and see that return. We did do an attended bot with them as well, to improve their call center.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would say it's a four. This is a rating from the business side, as opposed to the development side. We understand what the features are, and when new releases come out we have an understanding of what's feasible. I am not rating it a five because sometimes we do not know whether a use case is feasible or not. It means that I may have to speak to one of the developers to see whether it can be done with the tools and the features that are out there.

We host the UiPath Academy RPA training every other month for our clients. I have not taken the full course, but on a scale from one to five, I would rate it a five. This is based on the number of people who sign up for it and look forward to attending it, just to learn the basics of RPA.

In terms of how long it takes from purchasing a UiPath license until having the first robot, the average is probably four weeks. It depends on the complexity of the process. 

We have helped our customers to reduce some of their manual work, but they also benefit by freeing up their time to use elsewhere. Some of the processes we have automated have people spending hours locked up trying to finish.

It is also that we are improving areas such as the production line, or even automating some of their dashboard reporting to get more accurate information a lot quicker. We've been able to help cut that down but then also provide accurate data, and faster as well.

With respect to saving time, this fiscal year we were at seventy thousand hours saved across the enterprise. That is significant and has been across different departments and different regions, as well.

In terms of eliminating human errors, we do not have an exact calculation. We do get a lot of good feedback about the bot's performance doing well.

The most valuable aspect is the different capabilities and features that can be applied to different processes. I don't consider one particular feature more valuable than the others because they are all relevant to what the need is.

I would like to have a guidebook of examples that help me to determine the feasibility of specific use cases, based on the tools and the features that are out there.

With respect to the stability, on a scale from one to five, I would rate this solution a five. I haven't had much in the way of negative experience with it.

There are approximately two thousand people working on RPA across the firm. On my current project, we are a team of about sixteen people at our client's site.

I cannot say for a specific client, but I do know that our clients are constantly looking for what's out there. Whether it is from banking, automotive, or retail, they want to know what they can do to improve their firm or their company. RPA has been on the rise in the last three years, so I would say they want to be able to get hours back and save time so that they can allocate resources elsewhere. They are always looking for a tool out there that'll save them money and time.

In regards to ROI, we track it upfront. We have asked for the information to assess if a candidate process is a good use case. Then we track it in our dashboard throughout the year just to ensure that we are actually calculating the hours correctly. We'll then follow up to make sure that they are seeing those changes and they are receiving those hours saved. We have found that over the year, they are seeing a return on investment.

We track data in terms of money savings that the tool provides. I don't have the dollar amounts, but I can say that there are some processes where we have saved $50,000 USD just on a single process. It really varies on the complexity of the process and the time it would take to complete without automation.

I have worked with other tools and I see them as pretty similar.

My experience is with Blue Prism and Automation Anywhere. I'm not developing, so I don't have any details on the tool itself. My preference for UiPath is based on what seems to be the goal, and what is easier to understand. It rolls out more features and newer features, faster.

I am looking forward to trying the new UiPath Connect feature. I have seen the demo and it seems like that would be helpful for my role, specifically being on the business side. It is able to assess the use cases and determine what percentage they are RPA-able. I think that it will be super helpful.

My advice to anybody who is researching this solution is to try UiPath Academy Live first before they invest in the tool. This will allow them to get a better understanding of how it works, and get familiar with the services provided.

Sometimes I have questions. If I didn't have any questions then I would rate this solution a ten out of ten.

Overall, I would rate this solution a nine out of ten.

Internally, we use UiPath to automate financial transactions, specifically for invoice processing.

Externally, on the client side, we use automation in the financial space, primarily. There are various use cases from generic file uploads to transaction processing that we implement for our clients.

We have some processes that haven't been completed flushed out. Right now, there has not been an exact improvement yet.

Ease of use and speed of development are the most valuable features. 

The overall integration with Microsoft stack and a few other third party vendors, like Google, are very useful to us. Having these built into the product speeds up our development, so we don't have to code a bunch of connectors on our own.

I would like to see some sort of better implementation of the Python modules. Right now, any error code that Python throws up turns into a generic error that is difficult to track down. I would want to see some sort of integration that at least lets me debug the issue.

Its pretty difficult to do source control through the typical Git functions because of the nature of the UiPath and the visual element. Some sort of method to bring source control home for us would be very helpful. A way to systematically track which actions or activities were added and subtracted from a given process before adding to a repository would be very helpful to us right now. Our team of developers is growing, so control has become somewhat of an issue for us.

Ease of use has definitely exceeded expectations. Initially coming in, UiPath had some features that needed to be implemented that weren't quite there yet. Now, we are on 2018.4 and all of the features that we desperately needed are there. Thus, ease of use has been pretty great.

We have looked into scalability a lot. So far, we haven't done anything that involves a 100 bot. However, the scalability seems pretty easy. Scaling up to just five bots running in parallel has been very easy.

If we are going to build up the environment, we would run on virtual machines. We would connect through Remote Desktop Services, not through Citrix.

The technical support has been fairly good. I like that they pick up on interactions in the forum. However, some of the transitions from the forum to submitting a ticket are a little clunky. If a ticket could be submitted on my behalf on the forum, then have me boot over to where the ticket is, that is fine. Just kicking me out of the forum, then having me submit a ticket seems counterintuitive to me.

As a company and for our client, we see any sort of legacy system or too many individual systems as somehow needing to be integrated. This is the bread and butter for RPA, and where we started our conversation (and our clients' conversations).

The complexity of the initial setup depends on who you are. First time implementing, it seems a little complex. If you know how to develop UiPath, it is more straightforward. I had to walk somebody through the implementation setup of the environment because they had a lot of questions about where they were going. For software development is not that complex, it is pretty straightforward.

Having some understanding of database management and services is helpful, so you understand the inner workings of UiPath.

It has definitely eliminated human error in our internal process, somewhere between full production, deployment and testing. There were definitely some error prone tasks that we eliminated. If I had to give a ball park, maybe 10 to 20 percent of the process was error prone, which we were able to resolve with UiPath.

For time savings: What used to be a 15 minute task, now it takes the bot two minutes for the bot to run through, for example.

Generally, we push unattended. We think the cost savings is better with unattended. As far as ROI, when you are talking about returning man-hours or moving people off work, unattended does that efficiently. Attended doesn't always save much time. Thus, we push unattended for cost.

We have seen general platform survey before implementing RPA of the different market vendors.

Personally, I looked at other platforms, and it is hard to transition from UiPath. It does have ease of use that now I am used to.

If you are starting with development, start with the UiPath Academy. For the end user or client, start conversations about security and prevention now, while you get trained up on development.

Internally, there is not a lot of automation in place. We are using a good robotic process automation software to bridge that gap right now and get us further down the automation road. 

We use the UiPath Academy for new hires. The new training programs, both the previous and current versions, with the UiPath Academy work out for us. I have the previous videos, then the current new slide deck idea. It is pretty streamlined and high level, but it is good for getting new people started.

Also, I used Academy just last week. I used it for security because I had some knowledge gaps on security with UiPath.

We have a lot of maps worldwide which order some stuff from my department, and this is the compiled path. This goes into our database, then it comes to us. 

It uses data that we have already in the company, which is just sitting there waiting to get picked. You just have to tell a robot that a human does this, now you do it. We have so many processes which could be done like this. Right now, it's just scratching the surface. We are really exciting about it.

The product is very intuitive and easy to use, and I am not a developer.

The product is stable with no downtime.

The product can scale and meet our needs going forward.

I haven't used UiPath's technical support.

The UiPath Academy is good. I started there and learned how to use the tools.

The initial setup was very complex. We had the data, but we had to streamline it. You can build a robot in 30 minutes, but the robot needs to get the data correctly. This was hard to do because the laboratory in the U.S. uses the system one way, then the Chinese lab does it another way, so we have to streamline those before we can use the robots. 

Therefore, I should have looked at the data beforehand, since it took too long to get the data to be recognized correctly. We have learned from that experience.

The product has saved us on time.

We use it to automate functions in supply, finance, and HR.

It has saved time and brought efficiencies to our company.

The licensing mechanism allows us to share licenses between different users.

The speed of development needs improvement. They need to make it easier for non-trained people to be able to develop alterations that work the first time. On the development side, the initial development processes should be a focus.

The product is not easy to learn if a person has no interest in the product.

The product is stable. We have not experienced any downtime.

We have not scaled up yet, so it is too early to tell.

The technical support is very good. They are knowledgeable. I always find the right person. It is probably the best thing about the product.

It is easy to use because we receive support from UiPath. Also, the product is easy to train people on and get people using it. You don't need a technical background to learn it.

The initial setup is straightforward enough, not too complex.

It is not oversold. It does do what it was advertised to do.

We use other vendors and find all the products quite similar.

The support that we get from the company is good, and it does everything that we expect it to do. It seems to be a very good product, so far.

As a system administrator, I have to create a roundup report before the office begins and at the end of the day. The report consists of statuses of each thin client we have. The robot does all the stuff in just 2-3 minutes, saving our 1-2 hours of time done by a dedicated person.

• We can now run multiple robots remotely and easily so as to prevent daily checkup failure. 
• There are multiple testings run on each console by UiPath.

Orchestrator, data scraping and academy by UiPath are the best of all, for someone having cloud knowledge can exploit the technology.

• Linux environment is needed.
• RHEL/Ubuntu support is needed
• More academy and learning tutorials are needed on Udemy or edX.

Training with automation use cases including files manipulation, web automation and various desktop applications in the supply chain, HR activities, tax, and financial activities.

UiPath created many opportunities for our company to provide automation solutions for customers due to its powerful set of activities and features.

The Orchestrator and many activities such as those related to web automation and information identification within images (OCR), as well as the possibility of integrating external scripts and libraries within the software.

• Adding a "goto" feature
• Adding "run from this activity"
• Logging events/warnings to log files in order to follow the execution
• Simplify Orchestrator.

• PMO processes
• SAP automation
• Tickets organization
• HR system management

For example: In SAP, the chain needs to be monitored, and when it fails, it should be restarted. So continuous monitoring was a difficult task. Automating this process saves lots of manual hours.

It saves time, cost, manual efforts; it avoids or eradicates human errors by automating business processes.

• ReFrameWork
• Orchestrator
• Debugging
• User-friendly
• Easy to learn
• Easy to find an error
  
  

• Citrix automation
• Work management
• Repository of authors for implementing any changes in the code
• Improvement while navigating in Orchestrator
• Include export job records option in a different format.

We use UiPath for automation.

As a consultant, we have been involved in many client projects and deployed UiPath using a hybrid model.

UiPath enables us to implement end-to-end automation.

UiPath's User Community is good.

UiPath helped us reduce our on-premises footprint.

UiPath helped us reduce human error.

UiPath's support for various types of interfaces is the most valuable feature as it aids in automating the end-user systems we want to streamline.

I would like to have the ability to make changes at different stages of the development process without having to start from the beginning each time.

Automating with UiPath is not as easy as it appears in the advertisements.

I have been using UiPath for seven years.

UiPath is stable, but not 100 percent reliable. I would rate its stability an eight out of ten. If we need to restart the project, open the file again, or close down the program and open something else, UiPath does not behave consistently every time.

UiPath is highly scalable.

The initial setup is straightforward. The deployment takes around one month.

I give UiPath a seven out of ten.

Maintenance is required. We need to make changes to the code due to updates in the systems on which the automation is running. There are updates in the IT environments, such as operating systems, and also in the UI part. The newer features in UiPath bring new updates, and its components necessitate modifications to the code.