UiPath Reviews

We are partners of UiPath, and we are also programming for them. We are using it internally in our group, but we're also using it to develop automations for our clients. 

In terms of its use cases, we have implemented several automations in financial departments, mostly related to preparing reports, but UiPath is not limited to that. We also had use cases in HR departments for calculating bonuses, for instance, for large companies with more than 1,000 employees or for centralizing the hours worked at certain building sites for a construction company, etc. 

We automate whatever a client needs to be automated. We will discuss possible use cases with a client and prepare a short evaluation regarding the costs and benefits, then it´s up to the client to decide.  

UiPath develops increasingly towards cloud solutions. We still have clients who prefer to have it on-prem, but new clients will mostly opt for cloud solutions. The clients decide on the cloud provider, and we basically use whatever the client wants. 

One of the most interesting use cases we had was for a carrier that has about 300 trucks all over Europe. They check the bills that the truck drivers bring back from the gas stations and compare the amount of fuel in the bills with the consumption the GPS system of the truck has actually recorded. In the past they prepared these reports manually, which was quite complicated. It took them almost half an hour for one report, and that 300 times per month. They had to compare the figures from the GPS systems with the ones that were stored in the cloud and with the figures that they had in their accounting based on the bills from the truck drivers. We automated the whole process. With the automation we could reduce the time for preparing a report from half an hour to about 35 seconds, and the process is completely running in the background. Apart from the data regarding fuel consumption, we also included some additional information in the reports that they always wanted to see, but never could implement, due to time constraints - such as when a truck is due for the next service, how much time the drivers use cruise control, and so on. This was quite an interesting and a little bit unusual use case.

Very often, UiPath has been helpful in centralizing data. TPA is a tax, audit, and accounting company, and internationally we are part of the Baker Tilly network. One of our international Baker tilly partners has to centralize the financial results of a multinational client from 40 countries every month by retrieving and processing information out of the balance sheets. Previously, they had to prepare this manually - automating it saved dozens of hours every month. At TPA, for instance we have a client with more than 200 companies. We have to integrate data of more than 200 general ledgers every month for them. That's something that we have automated internally.

In two and a half years of using UiPath, we haven't had any issues regarding its stability. It is working very well.

Their customer service is excellent. Whenever we have a question, we immediately get a response. We have calls with their teams, and being in Bucharest, where UiPath also has one of their offices, we are often able to meet them in person. That's working pretty well.

They are permanently improving their products, that´s a huge advantege compared to other RPA providers. In comparison, I have heard that Automation Anywhere sometimes has issues that remain unresolved for quite a long time, but UiPath is permanently bringing up new versions, new products, and new solutions. Until now, we did not run into any issues, we could automate anything we had agreed upon with our clients. We have not had one case where we would have reached the limitations of UiPath.

Some of the licenses, such as for Document Understanding, are a little bit expensive, and sometimes potential clients hesitate when they learn about the license fees. We hope that they will reduce the prices over time. Apart from this, I don't have anything to improve.

In terms of new features, it is already difficult for us to keep up with what they're offering because there is so much happening, and we always have to take care that we're not missing out on something.

We have been using it for two and a half years.

Stability-wise, we have had zero issues. It is working very well.

Their support is really very good. When it is about new products, such as Document Understanding, we have to understand:

• How does it actually work?
• What can it do?
• What it cannot do?
• How to sell to the client?

We often have very detailed calls with the staff of UiPath, and if the client is in Romania, we often go with somebody from UiPath's sales team to the client. When the client is abroad, we frequently include somebody from UiPath in the calls to have an introduction for the client.

Positive

When we started with RPA three years ago, we did not use UiPath. We used Foxtrot/Nintex at the beginning, which was quite unreliable, they had severe stability issues, especially with more complex automations. We stopped working with Foxtrot/Nintex after about three or four months because there was something going on all the time, and we couldn't offer it to clients.

Usually, we start with relatively simple automation. Most of the clients start with a small studio and one robot license, which is anyways included with the studio for an extended proof of concept. They have done automation where they see that it is working, and then they start discussing other more complex automations with us.

We also have clients who start right away with quite complex processes, sometimes almost too complex. If a process would need six months or more to automate, clients tend to lose patience. We always prefer to start with a process that can go live after two, three, or four weeks so that they see that it is working, and then extend it step by step. 

My advice would be to start automating something that really hurts but is not an extremely complicated use case. It should be a process that takes only a few minutes being performed manually, but is being performed frequently. These are  use cases that usually can be automated within a few days because they are not very complex processes, and automating them delivers quick results. Based on this first experience, you can have a discussion with us or the other partners of UiPath to see what else would be automatable in your organization. Many times, clients have some suggestions of what could be automated, in most cases classical RPA solutions, but there is so much more all around RPA to better understand your own organisation, such as process mining, task mining, and other solutions that UiPath has recently finalized and brought into the market. 

I would rate it a strong nine out of 10. It is not yet perfect, but then, nothing is perfect.

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.

The primary use case is the automation of many reports, dashboards, and tables that were created manually by some of my colleagues. The tasks involve collecting information from SAP Solution Manager, manipulating some of the data based on business rules that have been implemented, and then storing the data in a specific way that can be used in the next part of the workflow. This includes using Excel and the aim is to create a PDF report that is sent to the top business line managers.

UiPath is the perfect tool to implement a solution like this, with continuous operative tasks between Microsoft native applications such as Excel, Outlook, and PowerPoint.

Before our UiPath implementation, the organization spent approximately two junior FTE on these tasks, and another 0.2 senior-level FTE in order to guide junior resources.

This process runs every day and if these tasks are executed manually, it means that two resources need to be staffed forever. At the end of the project, the organization gained a boost of two FTE saved and released, able to move on to other projects. This produced real value for the organization.

The efficiency of the process was the key success factor.

UiPath has the simplest low-code user interface that I've seen in my professional life. You simply drag and drop the activity on the flow, in a clear way, with clear names, and manipulating clear variables/arguments based on parameters. These are the key points in my humble opinion.

The library creation platform is really simple to use. Basically, it works like a normal flowchart application and once you've published packages, you can use and re-use these packages like activities in another workflow.

Last but not least, official Microsoft office integration is really useful, although all of the official integrations are very easy to use.

The UiPath Connect! and UiPath Go! communities come to our support every time we need to implement something challenging.

There are features that could be implemented on the coding side; for example, automatically assigning a unique ID for the "activity" used during the flow. As of now, if you use an activity via simple drag and drop, the activity keeps the original name. If you don't change the name of the activity manually then you will lose some information during logging. It would be useful to put a simple incremental ID on each activity, so even if you don't change the activity name, you will know where the process becomes stuck.

During the last update, the connection between robots and the Orchestrator (cloud) changed a lot. It would be a good idea to provide an easy way to use a single type of robot, regardless if it is a standard robot, floating robot, connected user, etc. Basically, have a simpler way to deploy robots in development, testing, and production environments.

I have been working with UiPath since 2017, and I plan to continue.

This product is really stable, and this is true for the on-premises deployment as well as the cloud version.

This solution is really scalable. It can be used in other organizational departments or on other robots in order to boost your automated tasks.

The vendor provides really good support; fast response time and great quality!

UiPath was my first RPA solution.

During the initial setup, care should be taken when configuring the robot connection. If you choose the "modern folder" setup then you could be struggling.

I am part of the vendor team, implementing RPA for other clients.

We have a 300% return on investment.

The price and setup costs need to be supported by a strong business case.

We evaluated Blue Prism, Automation Anywhere, WorkFusion, and Selenium (for web automation).

We use Studio, the Orchestrator, and we have attended and unattended robots.

Our primary use case is automating back-office processes from the corporate side. One example is the automation for ticket closure for some of the customer complaints. We also use it to fill information gaps between systems. Instead of having information run through standard APIs, we have it copied over from one system to another.

We run automations in a virtual environment, and the implementation was pretty easy and quick.

We used the Community Edition before purchasing our license. From the point that we purchased our UiPath license until we had our first robot was approximately one week. We found it to be very easy and very fast. We, as a Contact Center, usually face a lot of problems when we suggest any requirements. When we started with RPA, it took approximately one month for a very complex process to be automated.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate this solution a five. It is very easy. You can use the UI, or you can use APIs for the connection. In the end, you can do it.

On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In two or three weeks, an RPA developer can do everything.

In the Contact Center, the key issue is the handling time. RPA has helped us to decrease our time, and eventually, it will help to decrease the headcount.

For one of our processes, it reduced the time it takes from five minutes to somewhere between forty and fifty seconds. That saves a lot of time.

In terms of eliminating human errors, there has not been much difference because we have very strict processes and strict steps for them, so human error was minimal, to begin with. Our success is in the reduction of time to complete them.

The unattended, back-office robots are the most beneficial feature.

The Form Builder for back-end robots needs to be a web portal instead of a full desktop application. 

With respect to the stability, on a scale from one to five, I would rate this solution between three and four. For exception handling, it means that a senior RPA developer has to understand the reasons behind the process. If they have not been exposed to it then it is easier to perform some simple fixes and continue the process.

We have implemented eighteen processes so far, they are they used in several departments. In total, we have approximately four thousand people who are using this solution.

From a scalability point of view, we're not that confident that we can have the robots running twenty-four hours a day with a huge transaction. Being a telecom operator, we have a lot of transactions and the stability of the unattended robots needs some enhancement.

I think that both customer support and technical support are very good. When we have any questions or any issues, we are connected immediately. 

We did not use another RPA solution prior to this one.

We learned about RPA because one of the contractors was working on an RPA PoC at our company, and we were convinced that it could help us a lot. The IT people were invited to see the technology and from there, they decided to implement it with our in-house IT group.

The initial setup of this solution is straightforward. We used the Community Edition and it is very easy to use. 

We performed the implementation on our own.

We realized ROI in approximately six months. Our cost savings come from savings in agents.

From a cost perspective, unattended robots are better. They run twenty-four hours a day and do not require running on a client machine. The attended robots are not as cost-effective.

We did evaluate one other RPA solution before choosing this one. Our main reasons for choosing UiPath were the price and the ease of development. The Community Edition is very useful, and we are easily able to find RPA developers working in UiPath. This is different than with some of the competing products.

My advice for anybody researching this solution is that it is easy to download and it has a big community. A PoC can be done easily, and you can decide from there whether this solution is suitable.

This is a good solution, but the stability of the unattended robots needs to be improved.

I would rate this solution an eight out of ten.

I have used UiPath Orchestrator, and we have created both attended and unattended robots for our clients.

We have been using the new AI and OCR technologies with UiPath, and we are currently trying to implement the Citrix log capability that was recently introduced.

We are not running our automations in a virtual environment. When we automate any Citrix-based application, it's all email-based. There is a Citrix receiver and we communicate with that, which helps automate Citrix applications much faster.

Most of the clients I had seen have been running in virtual environments, although I have seen some of our clients running on the desktop. We have also seen hybrid scenarios.

One thing is that virtual environments can be standardized pretty quickly. So, that's an advantage. Normally, the companies, which are leaning towards more cloud now, will be happy with this. So, I think that is one factor. As you move virtual machines to the cloud you can migrate your bots to the cloud faster.

I have worked on various different domains including the public sector, commercial, healthcare, energy, utility, and federal. These are the different customers for which we are implementing solutions. Now, the customers are moving towards AI and natural language processing. They are more into chatbots, how they can use artificial intelligence, making use of data science, and putting more machine learning on board.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it two and a half. I'd say it is about marketing. You can develop anything. There are very small processes that you can develop with having minimal experience. However, when you start implementing complex processes, I would say you need to be a background developer.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. All of my team members have been using UiPath Academy for training and certification. It's not just with the U.S., but outside the U.S. as well.

From the point that a UiPath license is purchased until the first robot is ready totally depends upon what use case we are implementing. There are different methodologies that people use. Some build the bot without exceptions and it can go to production. Like a very simple process can go to production in two to three weeks. A more complex bot will take eight to ten weeks, and depending upon the process, it can go longer. I have seen tasks when a human is performing the job and it takes him around twenty minutes per transaction. But, when the bot comes in, it actually completed that same transaction in five minutes. But, to develop that five minutes of processing, it was understanding system availability and testing. Then you have to do load testing. It takes ten weeks or so.

Our clients decide to implement RPA for several reasons. The first reason, of course, is to have work completed faster. Second, when there is a workload, you can work on it more efficiently and with fewer people. Consider an open enrollment in October, where the open enrollment starts at 10:00 AM and there are a lot of transactions flowing in. Now you have to hire a human and train them. With the bot, we can just scale up instead. Finally, the bots are errorless.

In terms of eliminating human errors, it is a one hundred percent reduction. When you implement bots, it's error-free, as long as you have implemented it properly. The robot does not get tired, so the error rate is actually zero.

I would say, more important than saving money, it's more about business growth and client satisfaction. Our clients all serve someone, so it's more about customer satisfaction. The employees benefit because sometimes they have to do repetitive jobs, and they get bored with them. So, they can use automation and apply their brains somewhere fruitful.

Overall, automation is always improving customer satisfaction. Response time is improved, errors are reduced, and productivity increases because work is being done around the clock.

The most valuable feature of this solution is that it is user-friendly. I was a coding developer, so I know how to write code, and I've also used other RPA tools. This solution is workflow-driven, where you can easily relay what you had written. If someone has to read the code, it is very readable.

Second, I've always been a Microsoft technology guy, and they have provided the facility where we can implement any of the C# code into it. We have .NET code, and that's why I like it. We say it's a tool, but I would say it can also be leveraged as a custom coding tool. We can actually do whatever custom code you want.

I would like to see more machine learning features and capabilities for more accurate OCR.

With respect to the stability, on a scale from one to five, I would rate this solution a five. It's stable. The thing is, with the software, we have a few glitches here and there, but what I like is that we have the right support. When we actually reach out to verify, we get a faster response and also a faster solution. The responses are effective and fast.

The responses are effective and fast.

I have seen some cases where there is backend automation, but it was a series of processes. With this solution, they combine all of it into one. There were few human-interactive automations. Rather, it was batch-job processing of databases, etc.

The complexity of the initial setup depends upon the client.

There is admin access and a whole lot involved. There are safety concerns from client to client with their security policies, and it may take time. I have hardly seen any clients where it's easy to set up, within a week or two. It takes longer because of the client's own security policies. You have to get a lot of clearance because there is a lot of admin access that UiPath needs. If I had to rate the setup, I would give it three out of five.

A dedicated person is required to maintain this solution. The same way humans get sick and need doctors, the bots get sick and you need a maintenance person.

I would estimate that our clients see ROI, on average, in one year. It depends on what they are trying to save. If it is FTE then eventually you'll be getting everything. If you are trying to have a faster experience, it totally depends. There is a development cost and a tool cost that have to be considered. It also depends on the complexity of the processes and how long they take to code.

We have clients who use almost all of the RPA solutions. The most common ones are Automation Anywhere, Blue Prism, and WorkFusion. We don't recommend. We advise. We can implement regardless of the solution.

The choice is dependent on various factors. What we have seen is that most companies have a technology stack. Some have a Java shop, while others have a Microsoft shop, or others will use a different technology stack again. People tend to choose what best matches their technology.

When we started initially, most of the business users were afraid that the bot was going to take their job. That is not the case. The bot is actually helping them with their substantive, day-to-day work, by handing the repetitive work. So, after seeing the benefits, I've seen a lot of users now leaning towards bots, and they are very happy with RPA.

I am looking forward to the new version where they have implemented libraries. One thing they have done is merged the media packages into one. 

From a cost perspective, there is a difference between attended and unattended bots. I have implemented both, but most of the plans are moving towards unattended. The unattended bots come at a higher cost. For an attended bot, it is being used while the user is at the machine, and is more like an interactive bot. While there is a huge difference in cost, I still prefer unattended bots. I see less benefit in using attended bots and say that I would use unattended eighty percent of the time.

When I'm implementing an unattended bot, I am actually putting it on a machine. I can run as many unattended bots as I need on that one machine. I can do this with attended bots, but the thing is, you need user interactions. Now think in this way, if the user is not there, the attended bot is waiting for that user. Secondly, I see some of the use cases that are really helpful and suitable for attended, but I would rather go with unattended because it's going to show that I don't need a physical machine and it will be more efficient.

My advice to anybody who is considering this solution is to start with the UiPath Academy and do the training. Then, look through some videos, implement a process or two and see how comfortable you are. At this point, you can move forward with it. I would say that it is pretty easy to understand.

This is a good solution, but I'm a hardcore custom developer. I still want that flexibility in my hand to do whatever I can do. With a tool, there are always limitations in terms of policy and rules.

I would rate this solution an eight out of ten.

We primarily use the solution for the financial processes. 

In our company, we are freeing up 14,000 hours per month.

All of the UiPath's components, meaning Studio, Orchestrator, and Unattended Robotics, are really important for us because they offer really clean processes. The one that generates more value for us is the Orchestrator because we are planning to really scale up the factory. It helps us to have an overview and control. With the insights that they announced recently, I hope we have really great control over it in the company.

In terms of ease of use, I would rate the solution five out of five. It's really intuitive and any people that have the basics of coding can handle it. 

In the next release, they need enterprise connect. That's something we were wondering about. 

The solution could maybe use more artificial intelligence components or stuff we can start to use in the AI field. 

It could use an easy integration with SAP. Most of the processes of our company are in SAP. Sometimes it's kind of tricky to automate it.

I'd rate the stability four out of five. We haven't presented problems but sometimes with the UiPath robot, the robot attended license breaks.

We have reached out to technical support. We are in Columbia so sometimes there are slow responses because they don't have too much capacity to attend to us in Latin America. It could be better.

Our time to market in implementing our first robot was four months because it was new for everyone in the company. We started too many processes at the same time and we were preparing everything around the company. It was slow. It was four or five months.

The initial setup was easy. We didn't have any problems.

We implemented the solution ourselves. Our IT department and our robotics architect handled it. We also had UiPath help us with the set up as well.

I'd rate their assistance five out of five. They helped us a lot.

Unattended robot costs are high.

For our company, we have money to buy the solution and we have a huge contract with UiPath, but for companies that are smaller, the costs are too high. For example, a company that is not too big, because they have to pay in dollars, may suffer because conversion rates are high.

When we started we started with UiPath and Blue Prism. We made 14 processes with each and we decided to stay with UiPath. Mostly because of the IT architecture. We really like the Orchestrator, for example. It was like a huge consideration we had because Blue Prism is like a closed book and we didn't like it too much.

We utilize the full UiPath package. We are all on the cloud using the Microsoft Azure platform. 

We also use it within the virtual environment. It has been tough implementing it. Sometimes it doesn't identify the selectors or the images. It has a higher risk of failure. It's risky to have a centralized process.

We plan on automating the drilling process, the upstream and midstream process of the company, and the transportation of oil and gas for the company. Those are the main areas for us that we are aiming to automate. We started with back processes such as financial processes, logistic processes, and HR processes because they are not the core. As we continue learning about it, we will focus on the back-office processes.

A prerequisite for us in the company is to go through the UiPath RPA Training Academy. They have many courses, including foundations and advanced certifications. I'd rate the Training Academy four out of five. If they didn't explain too many things that would be great. They do basic stuff that will help people have a different mindset about it. They need more of an overview. Use cases, examples and more explanations about the activities in the UiPath would be useful. 

I'd rate the solution nine out of ten.

We are using the attended, unattended, and Orchestrator components of this solution.

Our primary use case is developing automation around revenue cycle management in the healthcare space.

We run automations in a virtual environment and we are very happy with that ability. It is much more time-consuming when compared to running it directly on the server, but it is very reliable and it is a great way to create automations that you wouldn't otherwise be able to create. Of course, we prefer to go directly to the same environment.

With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a four. In order for me to give it a five, it would have to be such that a user could go in and develop it easily with a point and a click. I think it would be extremely difficult to build a platform that was that simple for the end-user, but I think UiPath has come a long way and is very good at making it easier and easier as we go along.

We have at least ten developers who have gone through the certification training with the UiPath Academy. On a scale of one to five, judging how beneficial it is, I would rate the training four and a half. The training is wonderful. There are certain elements of the training platform that are not keeping up with the product though. Also, some of the things that are in the documentation are not up to date. Being a little outdated, it can be kind of frustrating for the people that are going through it. But, it's a great way for people to get a good understanding of how to use all of the elements of the process.

From the point that we purchased our UiPath license until we had our first robot was approximately three weeks. 

In terms of eliminating human errors, they are one hundred percent gone. When we build the bots we build them right, and there are no more human errors.

With respect to saving time, for the processes that we have built, it saves at least ninety percent of the time that humans were taking. We have to have somebody that monitors the bots. In case they stop, they have to start them up again.

We are a development shop for UiPath, so we use the Studio all day long.

We really like the Orchestrator and how I'm able to see what's going on with all of the different automations.

On the development side, more documentation on how to structure the setup for different environments would be helpful. Our biggest struggle had to do with questions like:

• Do I need to have fifty monitors to run fifty different bots?
• Do I need to have fifty separate computers around fifty different processes at the same time?

There was no really good documentation to teach us how to do that, so there was a bunch of trial and error involved in figuring it out.

We know that we didn't want on-premises computers, but we didn't have any documentation to explain how to set them up in the cloud. We went through several different iterations before we finally got that right.

Ultimately, it took us about three months before we decided on the structure that we wanted, so better documentation on infrastructure would be very helpful.

The product, itself, is generally very stable. On a scale from one to five, I would rate the stability a four. We do have situations where we've run some updates and then ended up with some OCR things breaking on us. But overall, we build automations for our customers and they don't really know that there are any problems whatsoever, because they're generally pretty easy to resolve.

We have approximately twenty people involved in the automation side of the business, but it's growing rapidly.

I have not used technical support other than the online forum.

This was our first RPA implementation.

The initial setup of this solution is straightforward. It just works. You download it from the cloud and install it on your computer. You might have to update your .NET framework, so make sure that it works. It is very visual and very intuitive, so you're up and running in no time with Studio. With Orchestrator, it takes a little bit of getting used to in terms of matching up Orchestrator with the computers that it's linked to but it took hardly any time for us.

We deployed the solution ourselves.

We have seen benefits, but I would say that it took us longer than most because initially, we were building through an RDP connection. We were also connecting to a software platform that is inherently slow. Between these two things, it took a lot of extra work to get it running and recognizing all of the images and stuff like that.

I can say for sure that we've seen savings on efficiency and labor for performing the tasks that we've automated. As a result of that, we've invested a lot more in training developers and building their skills. We're cash negative on the deal, but it's because we believe in the product. For the processes that we are actually doing, we are seeing savings right away, which is why we're investing more in UiPath.

For people who are researching this type of solution, I would suggest that they test all of them out. All of them give you an opportunity to try them. We initially made our decision to go with UiPath after looking at Automation Anywhere and Blue Prism. One of the primary factors that drove us to UiPath was developer feedback. Asking developers what platform they would choose to develop on, all of them said UiPath because it's very flexible and very intuitive. A lot of people are familiar with the .NET framework, so it's easy.

My advice for anybody who is implementing this solution is to first speak with people who have already deployed it in a similar type of target environment. Once you know how to set it up, it's easy. It depends on the infrastructure that you want, or need, for your organization. Otherwise, it's just going to be a bunch of trial and error.

From a cost perspective, the unattended bots are obviously much cheaper than the attended bots. However, to build a bot to automate a process where an unattended bot can run it is also more costly for the end-user. For us, it makes more sense to have attended bots. We also have access to a very low-cost labor pool. Because of that, it's cheaper for me to just have somebody monitoring the bots, running them manually.

Overall, this solution is awesome. I'm very excited about all of the new things. We've been doing automations for about eighteen months, and with the product from that time, to where we are today, many new things have come in. I mentioned the problems that we had with the RDP connection but Computer Vision comes out, and it makes things much easier and much more reliable. Fortunately, all those have now switched over to running directly on the servers where we're running the software, so the need for us has gone way. At the same time, I have used Computer Vision and it's great.

I would rate this solution a ten out of ten.

We are using it for financial applications in the financial sector. We also have a couple of bigger federal customers who started RPA development on their own, then needed our help. 

Internally, the RPA offerings team is developing more resources, so we can support all our customers. This involves a lot Pegasystems, ERP, and homegrown systems.

We are really seeing that RPA in the production, where people are using it, they are getting benefit.

Screen scraping credentials of whatever features that it has. The robot can log into the system, scrape the data, and enter the data into the system. This eliminates a lot of the manual work that the team had to do, which has improved the performance. Our teams used to do a lot of data entry, and this repetitive work has been reduced. The same resource can now work on some high-end work.

The ease of the use is good and exceeded my expectations. The implementation became easier and more standardized. Also, our development time has been reduced. Using ReFrameWork, we saw that the code become organized very nicely by UiPath and the implementation became easier and more standardized with more prebuilt components, which reduced development time. If you load the ReFrameWork nicely, you can do things faster and more standardized.

I have found there to be setup issues with Chrome. Right now, I am using IE.

I am looking for more batching processing because of the ODI framework. While they have a process where they log everything into Orchestrator, then they process it. However, when I have 50,000 to 100,000 records being batch loaded and processed one-by-one Orchestrator, I am apprehensive about it.

Stability looks good except that we see that when we run the bot sometimes somewhere in the middle it fails. It will recovers, but I don't know why and can't answer to my customers why. I don't know if something can be done to eliminate the failing piece. I don't know whether it is a stability issue, but it should be handled in future. Other than that, stability looks great.

If you start using Orchestrator, and you put your Orchestrator on a very high-end machine, it can handle thousands of bots. I don't see any issues with running multiple processes on a single bot, then connecting it to Orchestrator.

Before using UiPath Academy, we used the customer support to answer our initial questions.

This automation is not exactly like other automation that we used to do. This is a different type of automation where we are not disrupting the existing codes. We are providing all these features to the customer.

The initial setup is simple. Once you install Studio, you can do the development within minutes.

Once the bot is programmed, it eliminates human error. It doesn't make any mistakes if you have programmed it correctly.

Right now, we are not working with other vendors.

I would recommend UiPath and its bots.

Most of our work is with unattended bots. People are more keen to work with unattended bots because they just want to schedule it somewhere in the night and let the bot run, then come in the morning and have it ready.

Everyone in our organization has used the UiPath Academy. We are certified in it. There are three levels of training, which we had to go through before the final certification. The Academy is very good and well-organized. We went through it step-by-step.

One of team members developed a bot in a Citrix environment for a project, and it looked great. From his machine, he connected to Citrix, logged into the application, did some data scraping, and built an Excel file, then provided the data.