UiPath Reviews

I have multiple use cases as part of this solution, since I work in different domains with different technologies and applications. We use attended and unattended bots.

One use case was for a credit-based client where we worked on the UI automation of the application. We were using UiPath Automation Cloud because our team is spread across different geographical locations, like the U.S, APAC and EMEA regions. We had different RPA developers who are developing the script simultaneously and putting it on the system, and our business case was that we wanted to automate the UI applications. Since there were different developers in different geographical regions, they created the bots on their system. Due to the cloud offering, we were able to move the bots to production using a click of a button. There is also an Orchestrator offering as part of the cloud, which is hosted. Once we had a thorough peer review of the bots being developed, we pushed it to our production-ready cloud-based Orchestrator. From there, we use it to run the script. That is an unattended bot, which is also one of the features. Since it is a credit-based UI automation, there are some instances where manual intervention is required in order to see whatever data is sent out to the client, if it is in the correct order or not. That is why we use the unattended offering of UiPath. Both these technologies help us a lot in creating our production-ready implementation. 

For another use case, we did an implementation in the SAP application. It was a procure-to-payment (P2P) cycle, where a third party sends out the invoices which get fed into the SAP application, then it gets verified and goes out to the payroll team. Once that is verified by the payroll team, the payment is released to the concerned vendors. All these points of entry were being done manually: the third-party invoices entered into the SAP application, SAP verification, and the payroll team verification. Since it involved a lot of financial data, people were very hesitant to get it automated. However, since we had this UiPath offering, that initial hesitation was turned into a very good implementation of whatever we wanted to achieve as part of this UiPath automation. We were using the unattended bot as part of the cloud offering. We ran the processes at night from Orchestrator, so people working from home didn't need to stay up late in order to run the processes. Since we were using the cloud unattended bot service of UiPath, we were able to trigger the whole process in a single click of a button, which is amazing.

As part of the UiPath offering, we have three offerings: Studio, StudioX, and Studio Pro. These three offerings are provided via cloud on a single system and installed on our laptops or desktops.

I am working as a senior analyst. As part of this particular role, I have to cater to the client's needs if they want to get a UiPath implementation. Then, I do the consulting as part of the implementation. I also get involved in the PoC development and how we should use the cloud offering, e.g., what benefits are there.

We were able to move prototypes, which were in PoC stages to production very quickly, which helped us a lot. There has been more collaboration happening because of the cloud implementation. Because we have different geographical locations where in RPA bots are getting developed, at the end of the day, everything is pushed into Orchestrator Cloud. From there, we can execute it. In terms of collaboration, this has been very helpful. 

UiPath Automation Cloud has helped us to minimize our on-prem footprint. We were able to get our prototypes into production very quickly. In turn, this helped us to get stuff minimized quickly because we were able to move the prototype as part of the PoC into production faster. We were also able to scale. For example, if we had new people joining the team, we could easily move them into the cloud offering and add a new tenant. We have added two or three new members who could readily go ahead and use the solution to develop RPA bots.

It is a single point of truth. There is no discrepancy or ambiguity. We can go to the leadership team, and say, "This is what it saves us on costs, man-hours, and effort that we used to do manually versus what we are doing now using the bots."

The most valuable feature (as part of the cloud offering) is Orchestrator. Even if we have the RPA developers spread across different geographical locations, we are able to get the bot ready and pushed into Orchestrator, where any non-technical guy can come in and run the process. When I say non-technical guy, I mean any person from the business or leadership who just wants to see how it works. They can go ahead and log into Orchestrator and execute the process.

The Orchestrator portal is very intuitive, so you don't have to run around and talk to anyone. It is so intuitive because it is like using a web-based application. For example, nobody has to train us to go and do whatever they want us to do. It is so intuitive that we can figure out, "Hey, this is what I need to click in order to add new tenants. This is what I need to click in order to change the geography from India to APAC or any other location. In terms of execution, whatever bots are in execution right now will be shown there. Also, whatever bots are not running, they will be displayed as part of the dashboard as well as the failures.

UiPath provides granular, role-based access control and management, which is very important as part of the monitoring. When we want to drill down on why there is a failure, we need to do a root cause analysis as part of understanding on why this particular bot failed and what could be the reason: 

• Is it because of some kind of data issue? 
• Is it because of an issue from the product? Then, we need to reach out to their support teams. 
• Is it because of an incorrect implementation of the bot or feature that we want to get implemented as part of the solution?

We are moving from single sign-on to no password sign-on. As we are moving ahead with technological advancement, maybe that feature can be added. This totally depends on how that technology is accepted by the people. If people in big enterprises are not willing to switch and don't want to move away from the single sign-on, then it will be very difficult to digest this. However, whenever there is a change, it is very difficult to digest. Eventually, people will like it. I believe if it is implemented as part of UiPath, who is a technological leader in terms of RPA and new stuff when they roll out every release, then this would be a good area that they can look into for enhancement.

They could add more features in order to get that dashboard more intuitive, e.g., how easily can we visualize everything being reported. I believe this should be improved as part of our Orchestrator offering. Now, we have different visualization tools being used, like Power BI. The data gets flooded into those kinds of tools and the dashboard is easy to understand. So, someone with a non-technical background can see the dashboard and understand what has happened. However, to provide detailed analysis, there has to be some improvements so we can provide drill-down data to developers showing, "Hey, this has gone wrong." If they could also incorporate that as part of the reports, then it would be very quick to view on the dashboards.

I have been using it for two years.

UiPath has a number of offerings: on-prem Orchestrator, Automation Cloud, Automation Hub, Cloud Orchestrator, Task Mining, Task Capture, etc. Sometimes, it feels like other new areas are getting more focus compared to areas, like dashboard Insights, which should be more relevant. They should focus on these other areas to make the cloud offering more robust. Though, they are working towards it and releasing updates. Therefore, eventually, they will look into it, work on it, and iron out any kind of discrepancy.

It was very easy to scale up. Since we started getting a lot of data from the client which was getting filled as part of the UI-logged application, we were able to push in data as part of the UI. So, we were able to reduce replies to clients significantly.

We find the solution to be scalable. Since this RPA technology is now widely accepted as part of our enterprise solution, businesses are coming in. Once the business team is onboarded, we can easily onboard the people who have technical expertise to create the bots, analyze them, and provide logic on how we need to design the bots. As part of the initial stages, we only have a business person, a solution architect, and a tool expert. First, we create the credentials for them, then we provide the solution to the business as part of a PoC. After that, if we are using any other traditional system, then it will take a lot of time to get 10 or 15 people onboarded in order to develop the solution in a fully-fledged manner. However, since we have the orchestration capabilities, we can just go in that particular Orchestrator dashboard and create our tenant with a few clicks. We can also move in and out between different geographies. For example, if I want to go and look into what is happening in the Indian service line, I can just go and click on that particular service line, which is already configured as part of Orchestrator.

Initially, when we were going with the idea of creating an RPA bot, the first thing was to get a nod from the business to make sure about how scalable the solution is. At times, what happens is once we get the business sign off, then it takes around a month or two in order to get the team onboarded with all the necessary accesses. Once they get all the accesses, they will start working on the solution. However, in this particular case, as part of this Automation Cloud offering, we didn't have to waste any time after we got the business nod, saying, "Hey, you guys can go ahead and implement this full-fledged solution." Since the orchestration capabilities are there, the moment we received an email from the business, we shot out an email, "Hey, we are getting these pieces and have already created the credentials. Tomorrow, you can get the ball rolling in terms of solution development."

There are multiple channels where we can reach out to them. One of those channels is the Community Forum, which is being constantly monitored for any issues. So, if anybody has already faced it, they go ahead and have it answered. Or, if nobody has seen it before, then the forum moderator comes in, and says, "Hey, why don't you go ahead and reach out to the IT support?" So, this is a channel that gets a response and has faster ways to directly approach the support team managing the servers.

The UiPath Community Forum is worldwide. It is being monitored by community moderators. I have seen feedback being put through to the IT support team, then that is put through to the right channels to get addressed. They really listen to the customer feedback, which is what I appreciate about them. 

The support is responsive at resolving any kind of tickets or issues when we reach out for help. This is one of the primary factors for going with Automation Cloud versus other cloud offerings, like Automation Anywhere and ElectroNeek. UiPath support is very much available and provides a solution. Even if they don't have the solution, they tell the affiliate, "This is how much time it will take," or "It will be released in the next update."

We don't need any IT support in order to maintain this particular solution. Since it is a cloud offering, everything is taken care of by the URL.

In case of any issues for the setup and updates, we reach out to the UiPath support team.

The initial setup is very easy. It is like installing an app on your iPhone. That is how simple it is. Basically, it is not an installation at all. It is just signing into a cloud account. As part of the cloud offering, we are provided with a URL, which gives us access to the Orchestrator instantly. There is no setup whatsoever. You don't have to go and download any EXP or MSA file on your system, then double click it and a number of forms are popping up. It is nothing of that sort. It is a single URL, where you can log in with your credentials, and that is one time activity. After that, it is a single sign-on the moment that you access that particular URL.

The implementation was frictionless with the single sign-on feature.

By using the Automation Cloud version, when there is a new version pushed out, then I do not have to do a reinstallation again in order to get all the newest features. Since I am using the SaaS offering, the new functionalities being pushed out as part of the newest version will be easily accessible to me without doing an uninstall or installation. This is a good part of the offering.

We are seeing a good ROI.

The maintenance work has been reduced because of the bots. Initially, the time that we invested in order to zero in on this particular product was 60 to 70 percent of the job data. This helped us a lot when we were deploying it.

This solution has reduced business costs. For example, products and bots that we designed for UI automation were also deployed for back-end services.

The setup cost is minimized drastically since it is a cloud-based offering. We don't need to have a dedicated person or team to monitor it. We just subscribe to the services, get the URL, login, and the next moment, we are creating tenants and the service line. Then, "Boom!," we are ready for executing the bots from our test check.

Our license cost is reduced since we don't require any IT support. 

I used the free versions of other vendors when we were trying to zero in on the solution that we wanted to use. We used a few other competitors of UiPath as when we were doing the PoC, and the features that we liked the most and made us lean towards UiPath were its intuitiveness and ease of use. We liked how Orchestrator can be used by the business or by anyone with a non-technical background. That is what helped us to make our decision in favor of UiPath. 

With other tools, we had some issues with their support where they were frequently not reachable. They were not able to set up any discovery calls, such as, "Hey, this is how it is going to work." They also don't have very active community forums. 

Instead of talking to the support or sales teams, we investigated on our own. We went to the UiPath Academy, which is readily available, and looked into its documents, which were highly detailed. We also monitored their Community Forum, which is being moderated properly. Then, we read some reviews on IT Central Station, seeing how people are reviewing it and why they are paying for it. For example, if their whole community is coming out with good words, then there has to be something which they are doing well. That is what made us make the decision to zero in on UiPath Automation Cloud.

When comparing UiPath with different vendors offering RPA,like Automation Anywhere or ElectroNeek, we initially thought that Automation Anywhere was ahead of the game and UiPath was playing a catch-up. A few weeks back, UiPath had a good investor round, then they went all guns blazing out in the market. There is a lot of community awareness in terms of UiPath implementation. So, I believe the road ahead for UiPath is very good. 

One of the newest upgrades that we had was in respect to payments getting added. New functionalities are getting added. They also work on the feedback that they get from interviews conducted by sites, like IT Central Station, who take unbiased reviews. They work off this feedback, which is why they are upgrading their products out in the market.

I haven't used the AI Fabric solution as of yet because we don't have a business case for it as of now.

If you are ready with your own business process that you want to get automated, then I would recommend UiPath for its intuitiveness. You should consider the intuitiveness of the UiPath as one of the parameters in your solution decision. For example, if you have the business process ready, then that is half the job done. The other half will be taken care of by your RPA developers or solution architect. So, if you are using UiPath, the learning curve is very small. You don't need to invest a lot of time. 

They have their UiPath Academy learning website, where you can go in as well as ask your team members to learn based on their roles. There are different series of educational videos based on job roles and how that particular role should look at UiPath as a solution. For example, as a manager, if I'm going in and looking into the UiPath, I do not want to be bothered about how I'm going to pull in activities and develop the automation bot. As a manager, I am going into Orchestrator to see how many bots have executed successfully or failed. If I was a solution architect, then I need to know how to design the service lines if they are located in different geographical regions. 

Everybody is really looking for some kind of solution that eases our life since we are working from home. It takes a toll when we are working from home. When we have these RPA bots coming to our rescue, then it makes a difference in our day-to-day life. Then, we can spend more time with our loved ones rather than spending more time in front of our laptop screens.

I would like to rate it as nine (out of 10) because I believe no one is perfect and all the bots are being developed by humans. Going forward, I read on a forum that UiPath is developing an AI feature where the bot will autoheal itself. Once the autohealing feature is implemented, I would rate the solution as 10 (out of 10) because there would be no manual intervention.

We are a small but global company. We are about 1,200 people. We are a logistics company, and most of our employees work in our warehouses. So, our office workers are somewhere between 400 to 500 across the globe. Being a logistics company, we are maybe a little bit old-fashioned. There are a lot of papers going back and forth, and we are trying to automate different scenarios. We cater provisions to ships, so we are basically a grocery store for ships. 

One important thing is when a ship is going into port somewhere, they put in an order for whatever provisions they need for when they leave port again. So, we need to be quick at expediting their orders. When they put in a request for a quote for whatever products they need, we need to respond very quickly, because the tendency is that whoever responds first gets the order. So, we want to do that. We are trying to sort of increase the speed of those types of operations as well as the quality of them. 

It is hard to really pinpoint what it is we are doing, but it's the communication between customers. When we receive a communication from a customer, we want to move the process through our company as quickly as possible and with high quality.

We are fairly new to UiPath still. We do intend to use it company-wide and have started out with purely unattended scenarios so far.

We invoice every month quite a substantial amount of money to our customers. We saw a problem in that about 20 percent of our invoices were sent to the wrong addresses. That meant that, at month's end, when we were expecting money to come in, we would be missing around 20 percent of our cashflow that month. Of course, we wanted to prevent that because 20 percent of the cashflow of $300 to $500 million a year is a lot of money. 

We have automation that runs every night through all our invoices. Because we have some problems with our master data in the company, it does a number of measurements, on whether an address for an invoice seems to be the correct address, and a number of checks, such as, what ship was the goods delivered to? After that, it looks up information through the international registers of ship ownerships, then it will do a number of checks, giving each invoice a score as rating the probability that the address is correct. If it is below a certain threshold, then we will do some manual processing, and we are looking into UiPath Action Center for this. For four or five of our largest branches in the US and Asia, we have seen a significant improvement in the payments at month's end, which has definitely improved our cashflow.

The administration is a SaaS solution, which helps to minimize our on-prem footprint. The only things that we have running on-prem are the machines running the robots. Everything else is handled in the cloud. We don't need to worry about backups, etc.

We are adopting as much as we can some of the things that should reduce the maintenance costs. We are using Robotic Enterprise Framework in our development and Automation Hub to sort of qualify our ideas. So, we are trying to implement a uniform way of doing things throughout the lifecycle of an idea. UiPath supports this fairly well, and I think it will get even better.

Just this week, we are launching our Automation Hub effort because we need to start building a pipeline for our automation candidates. Right now, we have eight or nine ideas in our Automation Hub. That will grow quite quickly because we need the help of Automation Hub to decide on which idea that we will be moving forward with next.

UiPath continues to add services to the Portal. It is fairly important that they are all managed from the same place because it is a single point of access, which was a factor that really played into our choice of vendor, UiPath. We use Automation Hub to sort of collect ideas and discover what ideas are good for information, then we use Orchestrator to manage them once they have been developed. We are hoping to use Insights at a later point, when that is available in the cloud, so we have a complete end-to-end solution in one place. 

Automation Hub is an immature product. We have only been using it seriously for about a week and have already seen some things that will give us a few headaches down the road. We are committed to using it and will continue to use it, but I have some suggestions for improvement. We have been in contact with our local UiPath office about that, and their initial response was positive.

We would like to see more detail and refinement. It is still a young product, and we are confident that the product will improve a lot over the next few months.

We are hoping for some integrations between Automation Hub, Orchestrator, and Insights.

We are missing a way to quantify that money isn't everything with this solution.

Our license was activated sometime in July. So, we have been using it for about six to seven months.

We have seen a few quirks here and there. Overall, we are satisfied with the stability.

We have only a couple of handfuls of automations running, which are very stable. So, we are not doing much maintenance at all. Maintenance needs half an FTE, if even that.

The potential scalability is really good.

I don't know what the scale is for UiPath Portal. There are still signs that it is a young product, but we see it moving and improving at a really good pace. So, we have high expectations.

The technical support has been good. I have only used them a couple of times. The response has been good. They are knowledgeable. 

One of the big reasons why we chose UiPath is that it has a big following in online communities. It has a good forum itself: Forum.UiPath.com, but I really wish that UiPath would have moderators in their forums who are more active. There are a lot of questions that go unanswered, and that is a shame.

We didn't previously have any other automation solutions in this company.

Our initial setup was very straightforward. Our deployment took only a couple of days. We are a small operation with only two unattended licenses. We created the Orchestrator account and installed the robots on two servers. 

As far as development goes, we really just have the base package. Then, we are adding on Automation Hub right now.

We did engage with their local consultancy. They sort of helped us build a strategy for the infrastructure structure setup and strategy, as far as how to identify candidates, operations, and development. However, initially, we just wanted to pull the trigger very quickly. We had an evaluation phase of a couple of months, where we were testing different products and had tried to set up UiPath before, which helped.

We have used Carve Consulting, and our experience with them has been fantastic. We are working with this third-party consultancy to have them come up with a couple of ideas for some solutions that would involve AI Center for the end of this year or next year.

The initial deployment needed just a couple of people from our side, including me. I worked a little with some of our infrastructure guys, getting the accounts set up, the service division, provisions, etc.

We just haven't scaled to a point yet where there has been any kind of return on investment.

There are not very many users because the stuff that we have automated so far has just taken work off people's hands. Where a person used to spend all day uploading pricing data into a database, we have a bot doing that now. So, people are not using UiPath, they have just sort of been relieved of their duties. While that sounds bad, we have made an effort to find areas where FTEs get to spend time doing what they are best at.

The licensing is too expensive. It is not a cheap product. We constantly have to build business cases where we have to justify our existence as an RPA team. 

We have engaged in a long-running licensing agreement because we believe in the product.

We have used a third-party consultancy, and that's definitely not free.

We looked at a local variant of Kofax RPA called SmartRPA, which was built by a Danish company. It is basically Kofax RPA with an Orchestrator service built on top of it. We evaluated that. We also looked at something called OpenRPA, mainly due to price.

UiPath is built on top of Windows Workflow Foundation, which is a platform that I have worked with previously. So, there was a lot of familiarity and extensibility. Then, we looked at how good the product is at automating desktop applications. There was not really a contest there; UiPath was better by far.

The fact that this is a SaaS solution very positively affects how fast we are able to innovate when it comes to automation. When we did the evaluation of what product to choose, UiPath versus something else, the ability to assess deployment of the whole administration was a key factor.

In our decision to go with UiPath, it was very important that we didn’t have to worry about future installations and upgrades of Orchestrator. We just didn't want the trouble of having to do upgrades. With UiPath being a young product that is evolving very quickly, we would be doing on-prem upgrades every few months and we don't have time for that. So, we liked the idea that it is a cloud-based setup.

Security was a factor in our decision to go with the solution. We didn't look into all the technical specs and certifications. We just looked at some of their customers, and said, "If that bank is using it, and it is used in the defense industry, then they know what they are doing." They had good references.

It is the best product.

It is an automation product. At the end of the day, it is software development. If there is anything that is important in software development, it is that you have a defined process from beginning to end, from the birth of the idea until it has been put into production and eventually retired. So, you need to have a defined process for different stages in the lifecycle that you need to be in control of. The product somewhat helps us do this with Automation Hub and the Robotic Enterprise Framework, but we are looking forward to even more tools for stuff like that.

So far, we are still in the meat and potatoes space. We haven't really gone into the AI or Document Understanding stuff yet. 

UiPath Portal is good overall for enabling administrators to work with Orchestrator. I have seen a lot of improvements, even in the last six or 12 months. We are learning as we go. For the first few months, we were working in a classic folder. Now, we are adopting modern folders in order to better be able to scale our efforts.

UiPath provides granular, role-based access control and management. Right now, that is not so important to us because we do everything unattended. So, we have a couple of service accounts that run everything. However, once we move into attended scenarios, then it's really important that we have that granular control.

I know that there are some new features coming out in regards to deploying automatically and elastically, but we haven't looked that much into them. We don't expect them to be a problem.

We are looking forward to doing attended robots, but that will probably be in the second half of this year when we start looking into that.

For the size of our company, we started fairly big. We went all in, buying licenses, consultancy hours, etc. We have spent a lot of money this first year. I would probably advise someone to start small but still be ambitious. Do a lot of PoCs and see how it fits into your organization. There needs to be a lot of disciplines surrounding it, e.g., if you just stay with five or 10 automations, then things are good. However, once you build 100, you start running into maintenance problems and things like that, so there needs to be a discipline. 

You don't need to spend a million dollars to sort of get off the ground, so I would advise people to start small.

I would rate this solution as an eight (out of 10).

We use UiPath for a lot of different scenarios including recording daily time capture, ordering meals for teams, and more technical work related to tax and audit. The most common uses for me personally are for drafting and sending emails. This has saved a countless hours of time. Basically, if it can be automated then we are automating it.

UiPath has opened up a lot of opportunities in our organization to save time through automation, but maybe even more importantly, it has created jobs and opportunities for many who want to work in the tech space. This work is highly satisfying and makes a real impact on the quality of life for those involved.

My favorite features and upgrades that I have found the most valuable are the ability to create custom activities specific to our organization's needs. This ability to customize what we need has really opened up opportunities to automate programs that otherwise would not work properly. Legacy systems can be finicky, but this feature makes it possible to use APIs and get the work done that we need.

I work in a highly regulated field and so many of the features offered by UiPath are not allowed because of one reason or another. I would definitely appreciate efforts to be made to build useful tools that meet regulatory standards in different fields so that we can all get the most out of automation.

We have been using this solution for two and a half years.

We use many different solutions, but I am personally most familiar with UiPath

If you are a smaller organization, use the free community version of the software to get a feel for its features and abilities. Then, once you are comfortable with how it can be applied, work with UiPath to implement it. It will take sacrifice, but the returns are great.

We evaluated all options and decided on different tools for different scenarios. These tools include Automation Anywhere, Blue Prism, etc. 

One use is in our corporate tax accounting group. Our environment includes systems such as SAP, Vertex, several homegrown, and of course Excel. Other use cases include automating a timekeeping system and performing cell phone bill analysis. Environmentally, all use cases involve different systems.

For corporate tax accounting, we use UiPath to pull data from multiple sources (i.e. SAP, Vertex, etc), and then use multiple pivot tables in Excel. They were doing this manually, and it consumed about 40 man-hours per month. With UiPath, we have that down to about five hours per month.  

The most valuable feature is the ability to stop the process after it has been started by an individual user. This allows for some dynamic events, but still gain the automation. The underlying architecture (i.e. Elastic stack) is decent, but there probably needs to be better ties there to maintain at least an n-1 version on the Elastic stack.

Improvement should definitely be made in the area of screen capture, where Adobe Flash is still being used. Trying to 'read' a screenshot (vs looking at HTML) was a challenge, and even when Flash goes away, there will always be a need to do a screenshot and then get data from it.

We have been using the product for about two and a half years.

In general, at least for us, product has been very stable, but we are not doing extremes with it.

It will scale somewhat both vertically and horizontally. The basic solution for that will be to add more servers.

No other solutions were tried.  

The actual UiPath install was somewhat complex. We did have a learning curve on the elastic stack.

We implemented this solution in-house.

You need IT support in installation and operations. This is not the job of 'just' plug and run.  Costing and licensing were generally in line with expectations of this type of software.

We looked at the top three providers in this space, including Blue Prism.

Overall, the product is good, and we are happy with it. There is always a concern about the company's business viability, but that is a risk with any software company

We use Orchestrator, Studio, and of course the bots for indexing documents received from outside providers.

The best example of the way this product has improved how our organization functions is by the increase in efficiency it has helped us achieve.

The most valuable features are the ability to schedule tasks and using Orchestrator to centrally manage our bots.

Areas of this solution that have room for improvement are a couple of activities that have issues. We would like to incorporate machine learning so that we can do some of the quality checks that we do automatically instead of relying 100% on manual quality review by humans.

Additional features that we would like to see included in the next release are those they seem to already have planned. I am very intrigued by the AI capabilities that we saw in demonstrations. Having that capability would be absolutely fantastic.

On a scale from one to five where one is not stable and five is very stable, I would rate the stability of UiPath platform as about a four. There are two activities that we use that fail about 5% of the time. UiPath is fixing that — as far as we understand — and so we should get a solution very soon.

We currently have just two people in our organization involved in the automation program. That could potentially expand under the right circumstances.

Our team has had the opportunity to use the UiPath Academy RPA training. On a scale from one to five where one is the least beneficial and five is very beneficial, I would rate the UiPath Academy in training our team as a five-out-of-five. We literally started at ground zero with UiPath software, and, without the training, I don't think we would know exactly what it can do.

I also think the source support and technical support for this solution are both very good.

From the time we purchased our UK UiPath license until we had your first robot in production was really before purchase. We had a proof of concept opportunity prior to purchasing the product, so we could make sure it worked for our purposes.

The initial setup process was straightforward. We started with just Studio, and not Orchestrator. Our deployment was just a simple matter of installing Studio. It was very simple to install.

We have not seen a return on investment in a way that we can account for exactly because we have not done that evaluation. At this point, we have projected some ROI numbers but we don't have the final ROI. I think it did not take long to see the ROI as it didn't take months. It probably just took a few days to see a difference.

The performance benefits we have seen at this stage of our deployment is in the form of increased productivity. So, in our development processes, we have at least doubled the performance of the process we have automated.

The solution also helped to eliminate human errors. I really don't know the percentages we have not done that evaluation, but I know it does eliminate them as it is evident in the results.

On top of that, the solution saves our organization time which is also evident in the fact that the staff members who are using the bots can double their performance.

On a scale from one to five with one being the most difficult and five being very easy, I would rate the interface of the UiPath platform as a four-out-of-five. I chose that rating only because our legacy software is a bit difficult to automate. The selectors end up not always being accurate.

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. I don't think I have enough understanding to give it a ten. However, it seems from our investigation of other platforms, that UiPath is one of the easiest RPA systems to learn and use.

My advice to anyone considering RPA as a solution is to do your homework upfront. Learn what the platforms can do before you just pick one and start trying to automate.

We are using UiPath Studio, Orchestrator, and attended bots.

We are automating 12 shared services processes. They are from the finance, HR, and procurement areas. These processes are run at a high frequency and are required to be captured on two different platforms. We have implemented this solution to stop entry clerks from having to do the same job twice, on two different platforms.

We run automations in a virtual environment and it is successful. The implementation was fast and we realized the benefits quickly. Currently, we have deployed three processes and we are going to roll out more processes in patches.

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 four. Some of these processes have difficult exceptions that had to be handled, which is why we opted for the attended robots.

On a scale of one to five, judging how beneficial it is, I would rate the training a five. The training is rich in content and the material, products, and methodologies are explained well. The concept of automation can be very easily digested by anyone, even if they are non-technical.

From the point that we purchased our UiPath license until we had our first robot was approximately a month and a half. I was not the person doing the configuration, but I managed the process through interaction with the technical team. It was a straightforward and easy process.

We have realized performance benefits through the use of this solution. We were able to decrease the processing time of one of the processes from 15 minutes, under certain assumptions, to one minute and four seconds.

One of the calculations that we have done to determine the time we have saved is for one type of process. It used to take 7,000 person-days each year but now takes only 160 person-days a year.

Using this solution has eliminated a lot of human errors. It is now done based on preset values, activities, and rules. Exceptions are properly handled and the robot will take the information from the source system, which is fundamentally correct all of the time. The robot only needs to capture the data as it is from the source, and copy it to the destination, and this eliminates the errors. When humans are in the middle of the process, mistakes can happen.

The design capability in Studio is great.

The way that you can monitor the robots within Orchestrator is helpful.

Together, the aggregated features add value to the day-to-day operations of the business.

I would like to see more options in terms of configuration.

More information should be made available on the AI Fabric features, and how it can be used as part of a larger ecosystem.

Unattended robots could be cheaper.

So far, we have not noticed any crashes or any issues with the platform itself.

In total with the partner that we are working with, we have 12 team members.

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

RPA was on the strategic roadmap for the transformation of the organization. When we came across this plan for the shared service teams and operations, we started to build a use case and try to see how RPA can help us. Basically, it's a strategic thing for my organization and we will continue scaling it up to other business areas.

We had assistance from a local partner in Saudi Arabia. I would rate our experience with them five out of five. They have the right capabilities and the right knowledge. They were committed and dedicated to the successful completion of this project.

We did not evaluate other options before choosing this solution. The capabilities of the platform are good, as is their presence in the market. They have a very qualified team that gives you all the possible support, can answer your questions, collaborate with you, and ensure that you are on the right path to completing your automation projects. They try as much as possible to make your story a success.

They handled the PoC for us, and we implemented the full solution as soon as it was successful.

The time freed up for our employees allows us to enhance and scale up their competencies and capabilities.

This solution is very good. The team is effective and they are constantly focusing on the product's roadmap and enhancements. As a platform in the ecosystem, this is a promising product for anyone who is considering automation projects in any organization.

My advice to anybody who is researching this type of solution is to have a look at UiPath. Take an in-depth look at their fabulous knowledge base that is available on the product.

I would rate this solution a nine 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.