UiPath Reviews

We use it for handling processes that involve human effort savings. We are currently focusing on processes and problems that our users are facing in their day-to-day activities. It is used for the automation of business problems that are repetitive and error-oriented with a huge number of users working on them. We list down a set of processes where users are spending a lot of time, then we verify whether the use case is valid for automation using RPA. Once that is complete, we start programming the bot based on the requirements given by the user. We try to mimic each and every action performed by a human being by using UiPath Studio. It replicates what a human being does.

In terms of setup, the development happens in Studio that's on-premise, but the deployment of the robots is done on the cloud. They have their own cloud service called Orchestrator. UiPath hosts that, and it is available at cloud.uipath.com. It is basically the UiPath Cloud. The interface is completely handled by UiPath.

The biggest benefit is that before implementing automation, the users were spending a lot of time doing mundane and manual activities. Implementing the robotic process automation for processes that they were involved in helped them to avoid doing these manual activities and focus on more value-added processes. On the whole, it has helped the users to spend their time more wisely and also get more benefits for the same time spent. It helps us to improve user satisfaction by improving their working methodology because they are only doing things that are value-adding.

We are automating all the manual activities that can be successfully handled by the robots. So, the users are really happy, and we are getting good feedback from the users in terms of time savings. We are also achieving 100% accuracy in the output, which was not the case when the users were performing these actions. When they were performing the actions, the users had to validate the outputs, and the outputs were not as per the requirement. There used to be an error rate of at least 10% to 15%, but with automation, the error rate has been reduced to zero. So, the removal of manual activity and the reduction of the error rate to zero are two of the main benefits.

We are using it in our finance operations for our accounts payable process to process invoices. For this process, we were receiving invoices at a rate of more than 50 per day, and having humans perform those actions was not sustainable in the long run. So, we developed a robot that would automatically process invoices that we received through email. It extracts and updates the data into our ERP, and then, it sends an email to the users telling them that the invoice has been received, verified, and uploaded into our ERP. Now, we have a process that saves approximately two hours for five or more users on a daily basis. At an annual rate, we can save approximately 10,000 hours. We develop the bot in UiPath Studio and then deploy it in cloud Orchestrator via an unattended bot, which is a bot that runs on a predefined schedule. We have a particular time when invoices arrive in our inboxes. We set the robot to run at that particular time, and then the robot is able to process those invoices and proceed to the next action.

We focus only on processes that can be automated end-to-end, completely eliminating human activity. UiPath is flexible, and it allows us to build robots that prevent human intervention right from the start and all the way to the end. Then, we are able to deploy it on the cloud by using the Orchestrator solution. From start to finish, we have completely eliminated human effort, supporting our mission of end-to-end automation. For process analysis, we use a UiPath tool called Task Capture to understand the business case and draw a flow diagram for the steps involved in a process. UiPath has all the solutions required to implement end-to-end automation, and we are successfully using them for all our business problems.

This end-to-end coverage is important. Basically, we select processes where we can avoid human intervention. End-to-end automation is one of the key KPIs that we check before we even start automating a process. It is the first thing that we look for because we prefer no human intervention at all, be it for any kind of input, validating the output, or checking the logs of a process. All of these are predetermined and handled by the robot.

It is cloud-based. So, we do not have any infrastructure costs for maintaining the servers, etc. That is a big advantage. Also, Studio updates for development are pushed automatically. We receive the updates and just click on them, and Studio is updated. Overall, it saves a lot of time for the IT team because there isn't any involvement from IT resources after we deploy or install Studio on our system. From there on, there is literally no involvement of the IT department. That is how beautifully they have designed the tool for the updates as well as overall maintenance.

We went for the cloud to avoid any on-premises server costs that we might need to take care of on a recurring basis. The cloud was a big advantage for us. We are able to save approximately 15 lakh Indian Rupees, which would be $10,000 to $15,000, by not going for the on-premises setup. We were able to save that sort of investment in server costs by going for a cloud-based tool.

We were able to synthesize the value of this solution right from the inception. As soon as we deployed the bots, we were getting actual analytics for the run rate of the process and the total time of bot execution. Indirectly, the time during which the bot executes is literally the time that is saved from human effort. We get proper metrics of the time being saved by using Orchestrator. The other important thing is logs. In case a process fails, from the logs, we are able to derive insights about when exactly a process is failing. We are then able to develop a solution to handle these failures and re-implement them. So, overall the cloud solution gives us insights. It adds value to even developers' time by giving us an overall metric of the time saved as well as utilizing the logs for insights about the process runtime, et cetera. Overall, the cloud functionality is a great value addition.

It affects our ability to scale up automation. When we develop and deploy a process, other users in different departments take a look at the processes, and they are getting confident about the fact that this can solve their problems. We have been receiving requirements, and in that way, we are able to scale up the automation. On top of that, we develop the robots in a way that is modular in nature so that when we implement a process, we have reusable components that can be plugged and played into the new process. This improves the speed at which we can automate processes.

It has indirectly brought innovation from the users' perspective and developers' perspective. The users are saving time, and they are getting innovative in their day-to-day activities. In terms of development, we are on a constant learning path. When the vendor releases new software updates, we are able to effectively utilize those and implement them into our processes on an immediate basis, which improves the speed of delivering a process and the quality of output.

We can scale automation without having to pay attention to the infrastructure for doing so. We don't have to be worried about the cost involved with the on-premises setup. It is a cloud-based solution. So, when a requirement comes up and a bot is developed, only then we need to apply for the license and procure a bot. It has been beneficial because we don't need to pay any upfront cost until the bot is developed and ready to be deployed, and because the bots are delivered completely through the software service, that also indirectly proved very beneficial for global deployments and scaling of processes.

Its AI functionality is helpful to learn from the existing use cases and then implement the learnings on the new and upcoming test cases. As a developer, we need not spend any time developing templates for the extraction, etc. The AI module in itself has the capability to understand new forms of data. It can then accordingly extract and plug in the data to our templates without much effort. So, AI functionality has saved a lot of our time in developing a solution as compared to doing it the manual way.

We had one process where we had to use AI functionality, and we were able to eliminate any manual efforts. Previously, we had somebody who was verifying the output of the bot and after that only processing went to the next step, but with AI, we got the confidence that the bot has the ability to complete the action without manual intervention. That is one great example where AI helped to eliminate manual effort and improve the quality of the output.

It has significantly reduced human errors. Bots have quite a high performance rate with minimal or zero errors. The errors only occur because we haven't updated the business case in the bot. Once the business cases are updated in the robot, we do not see any errors. The bots follow all the steps as programmed and do not deviate from the set of rules defined while developing them. This reduction in human error has had a positive impact on users. The users had been feeling more comfortable using the robot output rather than relying on their own output, which sometimes had errors. So, overall the confidence level has improved and the lead time in delivering the output has also improved. The time they were earlier spending on the validation of their output has reduced. 

It has freed a lot of time. We only automate processes where we find huge time savings. We count it as full-time (FT) employee benefits. We only pick processes that have three or four cumulated FT benefits. With automation, we are saving at least three or four hours on a daily basis. This time is being utilized by business users in completing any other backlog work, focusing on other important things, improving their own work skills, etc.

Excel automation is extremely reliable. Excel integration is one of the top features that I have been using. We also have a feature called Document Understanding for processing the PDF format of an invoice by a bot. It has the capability to scan an invoice and then pick out the required fields, such as the name of the vendor, the details of the products being sent, or the cost of the product. There is an AI functionality that allows a user to program the required fields to be extracted, and the bot automatically follows those rules and extracts the data. Therefore, the AI functionality of Document Understanding is another important attribute that I personally like about UiPath.

I also like the Computer Vision functionality, where UiPath provides image processing abilities for robotic process automation. This provides a big advantage because images can be automatically processed without involving any additional tools. With an API, we can automatically link the Computer Vision engine and start extracting and processing images at a quick rate.

UiPath is a low-code platform, or mostly no-code platform, where coding is minimal. We can drag and drop all the required steps and then develop a bot in very less time. I am good at programming, but even a user who doesn't know programming can easily pick up the tool. The ease at which anybody can learn it is quite high. Overall, it is a 10 out of 10 in terms of usability. It is really easy to use with the tutorials that they have in place. Everything about it is quite simple.

We use Orchestrator to keep a track of all the robots that are deployed, monitor the logs, and deploy the robots on the runner machines. We use Orchestrator to upload the bots from Studio to the cloud and then deploy them to runner machines across our virtual machines. Once a bot executes, we get the logs, and if needed, we can monitor them to check that the processes are coming in smoothly. In case of any failures, Orchestrator also has the functionality to re-execute the process. So, we are utilizing the cloud to a greater extent for managing our robots.

The UiPath community is wonderful. It is one of the best communities where we can get a solution for any question that we post in a matter of minutes or hours. Whenever we post a question about any doubt or a bug, someone from the UiPath support team or community replies. Their knowledge is useful for other users who might face the same problem in the future. They have an MVP promotion where if I answer more than 100 questions, they provide us freebies or maybe certification vouchers. That's a good thing that they're doing to grow the community. I'm really enjoying the community members' involvement as well as their support shown during any problems that we face. I have also used Power Automate, and the community support of Power Automate is not that great, but the community of UiPath is very responsive.

It is expensive. Its licensing structure should be improved. They can introduce a license structure where they charge you on a per-minute basis rather than a full upfront payment. 

In UiPath Academy, the certification that they provide at the end of every course can serve as a good motivating factor for somebody who's learning it. That is a good thing, but one of the negatives is that previously, the certification program was free of cost, which helped a lot of developers to become certified developers, but recently, they introduced a paid certification course. I wasn't expecting that move from them. I would like them to go back to their initial certification method which was free of cost.

Sometimes, we do find that the bots misbehave or there are bugs that prevent the bot from executing even when the business cases are completely listed out. It could be that the cloud Orchestrator doesn't send the trigger to the runner systems to start the process because of small internet fluctuation. Sometimes, we find that the processes are killing the execution themselves and going into a halt state without any errors in the program. So, we do see some reliability issues, but these happen once in 20 or 30 instances. They are not on a regular basis. However, when that happens, it does create panic, and we have to immediately rectify it. If they can focus on that, it would be good.

I have been using UiPath for three years.

It is great. We are able to scale at a rate faster than what we had thought of because of the way we are able to develop our processes. UiPath literally automates most of the processes that business users are doing. So far, we haven't had any use cases that cannot be handled with UiPath, which helps in scaling implementation at a faster pace.

We have about a four-member team with analysts as well as developers who work with it, but the developers basically handle all the IT-related tasks. 

We are a manufacturing company, and we have deployed our solutions in almost every department. We have finance, planning, control, human resources, sales, and supply chain. We have 15 to 20 in each of the departments, and they are saving close to three hours individually. Overall, our estimated time savings are upwards of 100,000 hours annually. 

Our current usage of it is 30% to 40%. We still have a lot more potential to tap. We are still on the journey to reach 100% of user involvement where everybody is aware of the process. We are yet to hold the discovery workshops with all the users so that they're aware of the process. Right now, it is limited to a few people within the departments, but its usage will increase with time as we continue to automate processes at this rate.

We use UiPath Academy for the certification or onboarding of new members. When we onboard new members, we tell them to go through the UiPath Academy to get an understanding of the tool. It is free of cost, and it covers all the required modules for becoming an RPA developer. We use it extensively during the initial days as a developer, and over time and with experience, we learn directly from the tool.

They have a very responsive community. Sometimes, within minutes, we get a response to our query. We are quickly able to understand the solution that they provided and implement it. If it is a complicated problem, sometimes, the UiPath moderator from the UiPath company responds to the query and resolves it. If it is not resolved, we can directly contact their customer support. We are enterprise users, and we get quick responses to the queries that we raise. I would rate their support a 9 out of 10.

Positive

In between, we used Power Automate just to see the functionality, but we did not find it as intuitive as UiPath. We gave up on Power Automate, and we are now full-time users of UiPath.

I was around when it was set up. I had personally taken care of the installation. I found it easy and not at all time-consuming. I was done with the process in a couple of hours. In about four or five hours, I was done with the installation and setup of Studio and Orchestrator, listing the licensed accounts, and deployment of the random bots. Everything was completed in a matter of no time. I am not directly related to the IT department. I am just a developer, but I was able to handle it with no external support.

We did it in-house. We only contacted UiPath. They delivered the license keys, and we just keyed in the license keys, and it started working. That's it. Nothing else.

It is lightweight in terms of maintenance. There's no maintenance at all. It automatically handles all the upgrades via the cloud. There are no issues. It requires zero effort from IT.

Overall, you don't have a lot of savings because of expensive licenses. The licenses are quite expensive, and they are not cheap. It saves money but not significantly. However, we are not focusing so much on the monetary benefits. We are focusing more on the quality of output and time savings.

It does reduce the cost of digital transformation, but that happens after a year or two from deployment. Immediate benefits are not evident, but within a period of one to three years, we are able to make a huge amount of savings in terms of time. 

This digital transformation doesn't require expensive or complex application upgrades or IT application support. We didn't have any issues, and we never needed IT to support the UiPath tool. We have been directly using it as it is without making any changes. The impact of this digital transformation on our infrastructure was zero. There were no costs involved. It was used as it is without any changes in the infrastructure.

During the initial two years, we hadn't reached a breakeven point. When the development was going on, we had both costs. On one side, the manual effort was going on, and on the other, there was the licensing cost. So, we didn't have cost savings. After the bot was implemented or after about one and a half years, we were able to receive proper monetary benefits or what we call a breakeven point. So, when we started eliminating human activity, that got converted to cost savings. The accuracy of the process also indirectly improved our customer satisfaction. All in all, we were at a breakeven point, after a two-year period. That would be the general thumb rule for most organizations. So, at an immediate level, we did not receive monetary benefits, but after a period of about two years, we received monetary benefits or savings.

We rely on UiPath Academy for knowledge during the initial days, and it saves a lot of time. We don't have any monetary spending for setting up training because it is available for free. So, we have made some savings. It has saved us time and money, and it has been helpful in getting employees up to speed on the solution.

It is expensive. Every product or component is built separately. All the components have a separate fee. UiPath Studio has a license cost. The cloud has a license cost, and bots have a license cost. These costs are recurring on a yearly basis. So, every product or component has to be licensed for a year, and on expiry, you have to renew it.

Their licensing structure should be improved. The cost of a bot is a lot. It is more expensive as compared to some of the competitors. It is probably $8,000 for an unattended bot. When I did a search on the internet, I found that other vendors offer much better plans. I would like UiPath to introduce some flexibility in the licenses. Instead of a full license, they can maybe introduce a license structure where they charge you on a per-minute basis rather than a full $8,000 upfront payment. If I'm just spending eight hours on the bot, the bot should only be charged for that time. There could be a per-hour rate. A plan like that would be beneficial.

Initially, it will be expensive, and it also won't be as per the initial thoughts that it is going to be a quick solution that saves a lot of time. With time, you can achieve cost savings but not immediately.

We had our eyes on UiPath from the beginning. We did not focus on others.

My advice would be to not use RPA as the only solution. You also have to use other complementing features, such as optical character recognition, so that the overall solution is usable. Just RPA can't solve all the problems.

There should be proper change management to bring awareness about the impact of RPA. A lot of time, people misunderstand and take it in the wrong sense that they might lose their jobs. The fact is that RPA can't automate everything, and skilled people will still be required for doing activities. We can only automate a certain set of manual activities.

I would also advise taking one step at a time. Automate a few solutions, check the user feedback, and then start scaling up rather than immediately scaling up without getting the user feedback.

I would rate UiPath an 8 out of 10. Overall, I have no complaints. Studio, Orchestrator, and all the other tools are top-notch. They are being updated with new features on a daily basis. The product is extremely good, and I have no complaints regarding that, but the license is something they can focus on. They can introduce some innovative plans for procuring the license.

We primarily use UiPath for outsourcing. Customers call us when they need extra people to fill positions, on a temporary or permanent basis, similar to a temp agency.

The biggest use case that is running right now is that we get job openings or requests from a lot of different third-party brokerages, customers, clients, vendors, et cetera. They all arrive through different platforms. We get an email saying there's a request, please check it out and let us know if you have someone to fulfill the position, and the request is implemented through UiPath. It's automated. We've created all of the mailbox folders based on the sender and the subject, so we know which customer or which broker it is. Then, we make the email follow a link to the information for the job opening or the inquiry and we put it into our Salesforce system.

There are a couple of smaller use cases as well, where we have task operations that have to be done weekly or daily. Mostly it's reading emails or reading schedules and making changes in files.

The automation of job inquiries has a lot of sufficiency on how we operate as we used to have multiple people need to be available throughout the day to manually check if an email with an inquiry came in, and that would require them to drop work and open the email, check it out and maybe take action immediately. Now that the robot is running and taking care of the need for filtering through all the results for them, employees can stay focused on the other tasks that they have. They don't have to keep an eye on a second monitor every time and drop everything they're doing to read an email only to decide what is relevant or not.

I understand work has to be tested. It hasn't impacted the entire company yet as I've been here a little short of a year now and we haven't made that big of an impact just yet. 

The most valuable aspect of UiPath is the community in terms of the way they open up their platform to the community and make it freely available for people to try and to practice. The amount of feedback from that community makes it very easy for us to get into UiPath and if you're trying something that you've never done before, you at least have some insights. There's almost always someone who has done it before or who has asked the question. I would say the community is one of the biggest extra treats for UiPath. 

From a technical perspective, I like the learning curve in the Studio and in the orchestrator - or the Cloud Platform as they call it now - due to the fact that it's easy to get into. It's easy to grasp the basics and to get started. You can scale up as fast and as far as you'd like or need to for your customer. It can do everything. You don't have to learn everything in advance to be able to work with it. It makes it really approachable.

Building automation can be really easy. The biggest challenge is to find the easy use cases as the use cases in the company can get quite complicated quite fast. That said, using the recorder in the Studio and then converting that to work in a mobile office is quite easy. I started in 2016 or 2017, and between then and now there's been a lot of changes. It's always been easy for developer-minded people to get started. However, now with the introduction of StudioX, it is even more focused on the different users and they have a different entry point for them. What I like about UiPath is that the training is really comprehensive. You can almost just record what you do by hand and then StudioX will translate that into a robot and then you can fine-tune it to make it more robust. Smaller costs can be easier steps. Just press record, do what you do, and then you're able to work with teams. 

Scaling automation without having to pay attention to infrastructure does make my job a lot easier for now. What I do see in companies is when they've taken the first steps and they start to scale up, a lot of them have policies or ways of working in place where they want to stick to the ways that they know. A lot of time I see customers will, in the end, do it by themselves anyway, so they use all of the upscaling functions that are available as they want to do it the way that they always did. 

UiPath enables us to implement end-to-end automation starting with process analysis, then robot building, and finally monitoring of automation. However, while it does facilitate end-to-end automation, it does take a lot of the development and running and monitoring of the robots on itself. That is something that is facilitated really well by UiPath. The process discovery and the analysis is rather newish within UiPath. Maybe it's not as well integrated into the community platform.

At this time, UiPath has helped to minimize our on-premises footprint as it is a cloud-based solution. It's important that the on-premise footprint has been minimized as it makes it easier for us being a small company. We have 160 people working for us in the Netherlands and then a couple in the Caribbean. Bringing new technology in like robotic process automation and then asking from the IT department to get me free service and results of my configuring and have all the discussions about what goes where, how the security works, how to find the work, who gets access, et cetera is easy. This is due to the fact that UiPath is offered on a cloud basis and I don't have to do all that on-site work, which allows me to get to building and talking about RPA quicker. 

The fact that the vendor handles infrastructure, maintenance, and updates saves time for our IT department. It helps us to implement a lot faster. The client companies can have a reliable cloud solution to help them do at least the first steps to get them acquainted with the product. It makes it a lot easier. It helps me a lot, and it helps our customers in starting out as well.

UiPath has decreased the time to value in that since it's cloud-based, I can deliver faster than I would be able to do on-prem. If we have an idea, or if we want to scale up, we can do so faster in the cloud solution than I could on-prem.

The product lowers the overall total cost of ownership by taking care of things such as infrastructure, maintenance, and updates, however, I'm not sure what would happen if we scale up.

The automation Cloud Platform has definitely helped reduce the time it takes to create automation. It brings a lot of things together. It's easy to use for clients and customers. It makes it easy to bring different disciplines together, so I don't need to think about how to reuse my code, or how to explain to the customer, and I don't need to share the processes to be able to release, run, and monitor and to get reports on the results. 

UiPath has reduced human error. There are fewer errors and the processes are less error-prone and once the technology has proven itself within the company, within the customers, people start to trust the robots to do what they do. Employees don't need to check the work that had been done as they know that if the robot reported that it was done correctly, then it was done correctly. In that way, it has saved a lot of time by not having to check anything. 

It has also freed up employee time. It's a three-person team and it saved them a couple of hours a week doing the work that they used to do. It saved them a lot more focus as they didn't have to monitor the email inbox all the time. They were able to apply more focus to the other things that they were doing. That said, it's hard to quantify the gains. However, overall, it has made them happy. That's one guarantee. They absolutely love that they gave the mundane work away to the robot because it was bothering them to be monitoring an email inbox all the time. It's given them the time to focus on cases that match the right people to the right inquiries or openings. I don't have any metrics on it, however, anecdotally, they tell me that it helped them to do the rest of their work better as they could apply more focus to more important tasks and placements are better attended to. There's much more focus and attention and better matches being made.

The solution has saved costs for our organization.

I'm trying not to sound negative about it as I like them a lot, however, the process mining and the process mining features stem further away from the development of the robots and the monitoring. The development, run, and monitoring are really closely knit, or really close together, and then process discovery is starting to get there. It's on its way, however, I don't see that it's as closely connected as the other three parts.

The automation operations have not brought down any company costs. Automation operations have gotten more expensive due to the fact that we added UiPath to them. That said, you do get gains at a different branch of the company. We didn't replace anything with UiPath. We weren't able to skip a step or program or tool, which makes it an added cost.

More documentation would be helpful, as they change rather quickly. There are two yearly stable releases and then a couple of community releases and data releases in between. Sometimes not all documentation is changed as quickly as the features are. Sometimes you can find something in the documentation that is not the answer, or not available in the product anymore. That's simply a side effect of how fast they develop the product. 

Sometimes it's not entirely clear what features are, for example, available in their community edition, or in the on-prem, or in the cloud. The difference between the on-prem and the cloud has become clearer in the past few weeks, however.

I've been using the solution for three years now. 

I started out at my previous company with systems integration. We started out with discovering robotic operations, discovering the tools, and suppliers. We chose UiPath and one of the competitors, as we found them to have the best suit with our customers. That was the end of 2016. That's when I started doing training in UiPath and started doing some custom integrations.

Now, I switched to a new job at a different company where they want to start an RPA practice as well and they chose UiPath solely for RPA.

From the operations standpoint, the stability of the cloud it's very good. I haven't had any issues with stability. The Studio will crash at random times. I've identified two scenarios where I'm able to make the Studio crash every time by just doing the same actions.

However, other than that, the automation was really stable, and I haven't had any issues or incidents. In Studio, I'd say it is good enough, however, there is some room for growth there.

Scaling automation without having to pay attention to infrastructure is a bit pro for UiPath as I'm starting an RPA practice. We don't have a lot of infrastructure engineers to build the project yet. Therefore, a lot of the time, with new customers as well, it will be a bit of a one-man show. Yet, what we can do is communicate to the platform and then make sure the infrastructure is there and then implement the platform and build a business analysis basically in an un-built realm. I have to do a lot of things by myself, so the fact that UiPath brings in the Cloud Platform and the Studio and it's all integrated and you can scale up without having to have too much. You need to know something about infrastructure to understand what it does for you, however, you don't have to do it all by hand. I don't need like three or four DP-trained individuals to be able to scale up or scale out. It's helped me get further faster.

Once you build the infrastructure and you know what you're doing and you know where you want to go with your platform and scaling, it's rather easy.

The only people really using it at this time are me and six trainees. There are a couple of ops people as well that are able to log in. We might have a total of ten people on the solution.

It's not being used too extensively now, however, that's for a large part due to the fact that most of my colleagues are working with our customers, so there are not too many internal processes or tasks. However, we do have plans to increase its priority as the tasks that we do have are at some points largely repetitive. We do a lot of operations and maintenance for our customers as well in different fields, so we are mainly looking at that for further automation opportunities.

Technical support has been pretty good. 

I get a quick response and it's usually constructive. I manage to fix my own problems a lot of the time using the community forums and information from there. I haven't had too much interaction with UiPath tech support.

We did not previously use a different solution. 

I personally implemented the solution at my company. 

We currently have it running, so some internal processes. And, we're looking to expand that into the customer landscape.

The setup is simple. They deliver it in a cloud environment, I didn't need to do any installs or make any arrangements.

You need to make an account and get started and watch a couple of training videos that will help you through it. The adding of the robots is very well documented in the forum, in the community, and in the training sessions. They have made it really easy to get started and to get the information you need to take the first step.

The deployment question is a tough one as I started out at this company while already having a communicators subscription on my own account. Therefore, I started out using that one and then gradually shifted toward using more automated resources. I don't have a clear overview of how much time it took to deploy. It might have been a couple of weeks overall, however, I was doing different things at the same time, and I never took a metric of how much time it took. I'd say starting out if the prerequisites are in place at the company, it could be a matter of days.

Tasks such as setting up an account, getting some service, et cetera, if you know what you're doing and you know what to ask a few questions before starting, it's a couple of minutes or hours. That said, in reality, there are always things you forget or things that they didn't do, so it always takes a little extra time.  

My implementation strategy was basically to figure it out as I went, which is not the best strategy, however, it was the best we could do due to the fact that the company didn't really know what they wanted to do with RPA. I was figuring out my own place in the company and then their wishes with robotics with RPA. There were a lot of things at the same time, so there was not a closed strategy other than to start up quickly, as soon as possible, get feedback, and then try again.

For now, I alone handle deployment and maintenance tasks. That will be the case until our trainees finish training.

We did not use a third-party service such as an integrator or a consultant.

We have not yet seen an ROI and have no concrete plans for any in the near future.

While I have one or two sheets from old presentations that have pricing information, they are over a half year old. I have no current insights. I wasn't included in discussions between the company and UiPath in relation to licensing. 

The company might have looked at other options. However, they did this before I was hired. Ultimately, they did want to choose UiPath, and I was hired based on my experience with the product. They chose UiPath at that time as they were working together with Oracle and that company has always been very Oracle-minded.

I use the community Studio and the Cloud Platform. I take the cloud from UiPath. I'm not sure where they host their solutions. I use the automation cloud from UiPath.

End-to-end coverage is not too important to my work at this time. Maybe if they were more closely integrated, I would be able to offer it more easily to my customers. However, now, due to the fact that I often go in at the first interaction with a customer or at a company, I have to introduce the concept of RPA, I have to introduce the product of UiPath, and I have to introduce or orchestrate the Cloud Platform and Studio. What I've seen is that that's enough for the first steps, usually, the company will have a pretty clear vision of what they want to start out with in terms of automation. However, introducing the process mining capabilities would add an extra step to the start-up that we have to do and what they want to see is faster results in the early phase. It's short the time from when I come in to initiate the first value, so they can appreciate the value and start the business cases and go from there. Maybe, once they are a couple of steps further on and they have a couple of automations, then they go look at the process of task mining as they have the infrastructure, they understand what the process automation is about, and then they start to see the value process or task mining. Therefore, the end-to-end factor, for my job, for now, is not too important as I don't truly use the end-to-end approach. I do the start by myself with the customer and then we go from there. Then, in the next phase, I will build them practices and they will start to automate the beginning of the process discovery as well. There is not something that I have initially do. Once companies start beyond that first phase and the first steps, then process discovery and process mining can be really important in automation. In a later stage, it becomes more important. However, in my case, I work a lot in the early phases and haven't seen too much of the process discovery products in that phase.

Attended automation hasn't really helped us scale RPA benefits as we are a rather small company and there's only a small group that works with the product, and therefore, we haven't been able to use the assistance in the same way a larger organization such as a bank or insurance company might use it.

We don't use the staff solution yet and we have not taken advantage of the AI functionality. While I have played with AI, I haven't had any use cases to implement the AI sensor.

Overall, I am quite satisfied with the product.

I'd advise new users to start by doing instead of only reading. Start small, like finding small processes or if you're an individual, look at your own work. Find something you could do and automate that as it gives you the best appreciation of the value. Try it out in your own environment and just explore how it goes as that gives you the best insights. For me, when I started, it was a great feeling to watch your screen and watch your cursor follow the screen without doing anything. 

Keep asking questions when talking to users. When translating the biggest use case into other processes, spend more and more time talking to the users and going through the processes, and defining and understanding what happens. Otherwise, it's going to cost you a lot of extra time figuring out why you've got all these weird exceptions that you didn't expect. Everyone always talks about how easy robotic process automation is. However, only once you understand your processes from a user's perspective, you'll run into a wall. It's never standardized. It's never the same. I need to warn my customers more frequently about this pitfall, due to the fact that, yes ultimately, it's very fast, but it only is once you know exactly what you want to automate and that's why most of the time it's time-consuming.

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

We have automated tasks within our organization and are automating our marketing applications. Internally, we have automated in-person and webinar event creation for Microsoft. Whenever there is a request for creating an event that is covered on, for example, either on Jira or the Dynamics 365 application, the task makes an API and pulls data from both sources. It then creates an event on Marketo. It runs totally unattended. We have actually saved the build time that was previously around 45 minutes and we have reduced it to just four minutes.

Previously, we had a build time of around 45 minutes just to process one request. This was kind of a disaster because even in 45 minutes of build time, and this is the average build time, people were making mistakes. When these errors happened, the company had to actually pay money to the client. For example, if a company has an event at 3:00 PM on September 1st, and due to time zone issues, someone manually wrote \ 4:00 PM then people would arrive at 4:00 PM, whereas the event had started at 3:00 PM. Mistakes like that could become a very, very big issue.

Using UiPath, we were able to reduce these kinds of errors. We were also able to reduce the time by more than 90%, just by deploying the bot that could do API calls in order to complete a specific point of data gathering.

For the portion that we automated, the errors that were happening were reduced to 0% and the efficiency was up to 90%.

We've found the usability of Studio very easy. It's simple to understand everything. It's very simple to just start developing within UiPath. 

The Orchestrator is fantastic in terms of usability as all you have to do is just need to deploy your bot there. It gives you several options of how to schedule it, how to monitor it, and it also gives you the dashboard that allows you to see the performance of your bot.

I really like the fact that we have a cloud model, where we can actually go ahead and use their cloud to run our bot. That is a very good kind of feature. 

I really like AI fabric and the documented understanding model, as that actually allows us to do a couple of very complex POCs. They went very well and right now, those prefaces are currently in the pipeline. Hopefully, they will get started with them next month.

The ease of building automation using UiPath is very easy. When it comes to comparing it against other tools, UiPath might be the easiest one. It's totally subjective, of course. That said, there are scenarios where automating certain kinds of scenarios with UiPath is not that easy. Overall, it's pretty good at automating all kinds of stuff.

UiPath enables us to implement end-to-end automation. End-to-end coverage is very important. While working with clients like Microsoft and Google, we have to actually go ahead and make sure that you're actually providing all of these kinds of services. With services such as documentation you also need to be on top of the latest market trends. UiPath actually provides us with not only the ability to handle all of this but to also document all of these kinds of things. That is available, either as a part of some other products or is embedded within the Studio itself as a part of an extension. That is something that I really like as that actually reduces the time that I invest in the creation of the documents. That, and the client actually requires all of these documents before even we can go ahead with the contract, makes having them on hand so important. 

The Automation cloud has helped decrease time to value. Earlier, the deployment of an on-prem Orchestrator took around two to three days for proper configuration and for making sure that there's a disaster recovery mechanism. Automation cloud has everything built already within it, which makes things faster and easier. This reduces the amount of time that is required by us to deliver. Within our area of work, within marketing, time is everything. Once you have taken on the project, the client expects you to deliver it as soon as possible. The requirements that you're getting from the client are very, very time-sensitive. If you're essentially not delivering it on time, that is going to be an issue. Automation Cloud actually helps us to do that without thinking about other things. It actually goes ahead and does a couple of things for us that we don't have to worry about, such as deploying the Orchestrator on the cloud, making sure that everything is properly set up, and making sure that the disaster recovery option is there. These kinds of things actually save us days of time for installation, if not days of debugging time. 

It's very important for our company to scale up automation without having to pay attention to infrastructure. There are a couple of projects that we have where we don't really care about the infrastructure. If it is handled by UiPath, it's absolutely fine. However, for example, in the case of some of our elite clients, what happens is that they actually need to know the details and how data is being propagated amongst different servers. If we're not controlling the environment, if we're not handling the entire knowledge, we won't be able to give them the same thing and the project might go away just because of this fact. Therefore, I'm not saying it's not very important. It's actually very, very important. That's why we use both services that are provided by UiPath - both on-prem and cloud. That said, if we have projects where we don't need to worry about it, it's nice to have the option not to.

UiPath has helped us minimize our on-premise footprint. Their customer service has actually helped us reduce that. UiPath was released in 2015. There are experts on this particular thing in the market, and most of those experts are found via UiPath only. When help is provided by UiPath themselves, that can actually resolve the issue in a matter of hours rather than days.

We use attended automation. We usually use attended automation within the HR department. Basically, we're using it for onboarding, for monthly salary management. It's great for automating some of the basic SAP projects as these are the places where we require human interaction, either to handle the credential part or to provide some inputs. This actually helps bring confidence into the process and also phases out the work of a particular human. Automation has integrated with some human day-to-day jobs so well that now when employees come in, the primary thing that they have to do is just to trigger the bot and start providing input. Work that they used to do for the first half of the day, is completed in the first hour of the day. That's the kind of benefit that is being provided by attended automation.

There is good AI functionality and we use it for some proof of concept projects. That said, we haven't yet used it for more complex or involved automation or processes just yet. We have one project in the pipeline that we have to start working on this month. 

We use UiPath Apps. We use UiPath Apps as a form. Essentially, we have created UiPath Apps in such a way that helps HR people to onboard individuals. For example, whenever someone has to get onboarded, they have to actually provide some details in terms of who they are, their previous company, and some other basic details. Also, HR will need to provide some extra details, in terms of who will be the individual's manager, et cetera. Finally, IT has to assign some kind of role. What we have actually done, is we have created an app where a user or a new individual has to actually provide all the information. Then, HR just needs to select the particular role. Everything is pre-configured. We automatically assign specific roles. In terms of IT, we can now automatically assign specific resources such as laptops, monitors, or headsets to that particular person. Since everything is automated, within a couple of minutes of registration the person receives his new ID password and details. Instead of waiting for an entire day, it happens in just a matter of one or two minutes.

UiPath Apps has increased the number of automation we can create while reducing the time it takes to create them. Earlier, we used to create automation, in terms of forms. Those automations were types of attended automation. A person had to have specific access to that particular computer before doing this kind of work. In this scenario, the issue we had was that every time it was not possible to handle manual steps if we were onboarding ten people at a time. Everyone had to wait for their turn and that was not very efficient. What we have done is we have actually deployed UiPath Apps whose links can actually get loaded onto an individual's mobile. One just needs to open it on their mobile and get started. That's it. Everything executes parallelly. We have also made our system scalable so that multiple VMs can learn the process at the same time.

UiPath speeds up and reduces the cost of digital transformation. Doing so does not require expensive or complex application upgrades or IT support.

We have found that UiPath has reduced human error. We were getting some human errors related to time zone issues and some of the other issues such as daylight savings. There were several other issues related to accidental typing or of people not focusing properly, even after several integrations. That's part of the reason we went ahead and automated processes. Obviously, a bot only follows what you have programmed it, what you have programmed within it. The errors are literally reduced to zero within that specific section.

UiPath has freed up employee time. We have actually retrained the freed-up employees into UiPath to act as support engineers. As a rough guess, I would say that we have saved around 120 hours a week just by deploying UiPath.

The additional time enabled employees to focus on more essential work. For people who were actually acting as build personnel, we have re-deployed them as a person who actually interacts directly with clients or who does QA work. This is a higher position that comes with a higher salary as well. There have been promotions simply due to implementing UiPath.

Employees are pretty happy. Initially, everyone was scared that they might lose their jobs. However, but adopting UiPath methods and retraining people, some are even getting promoted and we find that they are actually encouraging automation processes so that new work can come in and the remaining people could also get on better.

The product has reduced the cost of our automation operations. In terms of marketing operations, for example, it has reduced the cost. Along with the help of similar investments, we need fewer people and more bots currently. That's definitely a big thing for us. We had a cost reduction of approximately 20% in our operations. This is just a ballpark. That said, overall, UiPath has saved our organization a lot of costs. I cannot speak to exact savings, as that requires business knowledge, which I do not have complete access to. 

The AI Center area could definitely improve. The StudioX model could also improve just a little bit so that the introduction of variables is better and would make it possible to pass on a similar kind of data in between multiple activities. This is a very simple concept, however, this kind of feature is not available within UiPath. 

From the business perspective, a little bit more insight on the dashboard that is currently available in Orchestrator would be ideal. I agree with UiPath having a dedicated tool for insights, however, right now, it's a paid tool. 

If I can get a little bit more data and a little bit more customization on Orchestrator, that would be really great.

I've been using UiPath for three years and eight months. I've used it for the same amount of time the company has used it.

The product is quite stable now. There are certainly some places where UiPath has to work, specifically in terms of actual stability, where there are still some unknown errors that are coming in. 

In terms of Orchestrator, I have noticed there are some places where there are glitches. Things are not very clear at first as everything is changing quite quickly, I'll say that. Even in the enterprise version, everyone wants to be on the very latest version. However, there is a drastic change between the versions themselves.

For example, 2019, 2020, and 2021 versions, all three are drastically different amongst themselves. This kind of change is definitely good for the provider in that they are doing something better. However, as a consumer, I don't really want to go ahead and go through an entire learning curve all over again along with handling my current job of handling all the work, just so that I can cope up with what changes the product team has made. It should not be necessary to go through this level of adjustment for each and every release. At this point, I have been through three to four migrations and in each migration, I have gone through some kind of a learning curve.

Automation Cloud actually helps us to rapidly scale up. We don't have to invest time now in configuring Orchestrator, or the cloud version of UiPath. All we have to do is we just need to basically request for a particular package and, maybe, either with the help of a package or with the help of the UiPath team, it is pre-configured for us. That way, we just need to utilize it. Therefore, scaling is simple.

The scalability is great. It has actually allowed us to schedule the bots or maintain the bots in multiple VMs without having any worries about how to utilize licenses, or how to actually go ahead and deploy the bots manually or install the bots manually on certain VMs. Everything is automated within the UiPath environment.

If we talk about attended users, right now, we have more than 10 people using attended bots. Their roles are essentially from the recruitment team, from HR. Some of the marketing staff are also using it in analyst positions. 

We definitely plan to increase usage and we're using UiPath pretty extensively. We have a couple of projects in the pipeline and currently, we're also working on some of the more complex projects within the team.

All the projects are having a specific date of delivery. Everything is running parallel as we also follow an Agile method. In this Agile method, if something is stuck, it will eventually impact the date of delivery. And we really don't want that. UiPath actually helps us a lot by providing 24-hour support and it helps us in setting a lot of the items we need to use. They do it quite easily and quickly.

On the scale of one to ten, it's definitely a ten. Whenever I have a doubt, they are always there. They even offer to get on a call with them and actually go ahead and resolve the issue themselves, if they know how to do it. 

Many times, there have been scenarios where the issue was unique to us. They actually presented us with some debugging steps that we can do on our end. Most of the time, those debugging steps actually helped us to resolve the issue. When none of these options work, they were very keen to figure out how they could actually improve the experience and what could be implemented by the developers within those specific parts of the product in order to resolve the issue. We have given them feedback in the past and in a couple of future versions, we were able to see those ideas implemented.

We were using AutoHotkey before this product, as well as Selenium. However, after implementing UiPath, we have not used anything along with it.

The initial setup was straightforward. The installation of the Studio was quite straightforward. We just had to go through all the legal terms and everything. Once we went through those, we just had to install it. The same thing is true for Orchestrator as the on-prem installation of Orchestrator is pretty straightforward. You just have to get the setup, link it with the skilled server, and then install it. 

Apart from that, the configuration within Orchestrator was very simple as there is only one file that allows us to log on to everything. It made it pretty obvious.

The deployment took somewhere around two days for the entire setup. 

In terms of the implementation strategy, firstly, we decided to set up all the databases and all the dashboard-related services such as Power BI. We decided to do this first due to the fact that the dashboards and databases are the base of any application. 

We decided to implement it first in Azure. On the same day, we decided to get the cloud version of the Orchestrator as well. It was quite easy in terms of Azure. There's a three-way plugin that is available there. We just had to install that on the specific VM and we were done. Finally, on the second day, we went ahead and installed all of the Studio. Once Orchestrator is up, we could install Studios and link them to Orchestrator in order to get the license. That was our strategy and our approach.

We essentially have one dedicated resource for maintaining all the deployments and to watch if anything goes wrong. We have three dedicated resources for maintaining all the bots that are currently running as well. We don't need a big team to maintain everything. 

In one of our projects, we actually used Azure Cloud for the deployment of Orchestrator and the deployment of packages. The experience is quite good. Azure provides the DevOps side of our service that allows us to set up the pipeline and automatically deploy any kind of project to the Orchestrator as soon as it is committed.

While the company has likely been looking at ROI, I don't directly deal with those details.

A couple of our clients cannot actually go ahead with the initial investment of Orchestrator as it costs quite a lot. The thing is that we don't need that much of a license in order to automate our processes. Having a free version of a cloud or having a cheaper version of Orchestrator has actually helped a lot.

Automation Cloud helps decrease UiPath's total cost of ownership. However, overall, if we talk about scalability, once the number of licenses that I need increases, ultimately, Automation Cloud might be a bit expensive. It depends upon the version you're using. Yet, since the license cost is increasing, what happens is if you go ahead and buy more than five licenses, then essentially you would have been in better shape if you would've actually bought the paid version of Automation Cloud and installed it on-prem. That would've been a cheaper option. It's subjective. Our scenario is just that we need two unattended licenses to do the job.

Some of the clients do consider the initial investment of UiPath to be expensive. It's seen as expensive specifically from the cost of getting a licensing for an on-premises setup. For some projects, UiPath can be overkill. However, it is the best software a company can invest in for automation purposes. 

I cannot speak to the exact cost, as I don't handle licensing directly.

It's paid per year. We get licenses not directly from UiPath. Rather, we get them from a vendor.

There are additional costs as well. For example, the cost of an SQL server is one. We are definitely using the Azure product suite as well. We had to actually invest quite a lot in SQL Server in terms of database management, just to make sure that everything gets logged properly and that the Orchestrator is functioning properly. 

We switched to UiPath after we compared multiple tools. We looked at certain parameters such as the ability to automate marketing tools, the ability to automate quickly, and how user-friendly it was. Out of all these three parameters, UiPath stood on top.

We looked at Automation Anywhere, Blue Prism, and PEGA.

I specifically have been using the community version of UiPath. The company has been using the enterprise version.

We do use the Automation Cloud offering.

We do not use the SaaS version of the solution. 

I'd advise users to give it a try. I started my career in UiPath and since then I've been loving it. I became a UiPath MVP as I really enjoy working with the product so much.

That automation does not need to be very complex, so you don't need very complex tools to automate any software. Tools like UiPath can do most of your job.

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

We have worked on multiple use cases, but most recently, we have worked on a payroll system. Previously, every month, we had to manually get certain details from HR, and we used to do the pay run for all employees in the organization. Now, we automatically extract the required information from the current system by using UiPath. We then prepare a sheet by using Excel, and the entire Excel sheet is processed by a bot. The final sheet is sent for the payslips for the entire organization, and the entire pay report is sent to the bank for payment details.

Automation reduces dependencies. When I have a process that is done by humans, there are dependencies. For example, I need to make sure that the required number of people are available in different shifts. Any process that is done by a human has to be split into eight to nine hours of work. After every eight hours, I have a replacement happening for the same work. So, multiple people are working in different shifts. In addition, any work through humans can only be done from Monday to Friday, or I have to get the team over the weekend. Making our team work over the weekend requires special permissions or approvals. With automation, I am at ease. I'm not dependent on anybody. UiPath is easily accessible from mobiles for the orchestration part. So, if I have a critical process that I need to execute and get the results, I can do it from my mobile. Even when I'm traveling, I can get real-time statistics. 

Previously, I used to get a request at any time to do the pay run for an employee. If the employee was on a leave on that particular day or was not available, I used to miss my target or deadline. Now, we are not dependent on anybody. We are completely independent. If I get a request, the robot is automatically going to process it automatically. I don't even have to tell the robot to run a process after getting a request. All my rules and validations are taken care of by automation before the deadline. If I'm away from the office, my robot can automatically trigger a process on receiving a request. So, we are able to meet all the deadlines, targets, and standards set by the company within the given timeframe.

It has helped in minimizing our on-premises footprint. We work for multiple zones and across the globe. If I have a UiPath architecture, I can deploy it anywhere. Irrespective of the country or continent or zone, I'm able to use the same deployment or the same architecture at multiple locations. It has reduced my cost of infrastructure and maintenance. The cost of everything has come down. Previously, we used to have servers country-wise and continent-wise, but now, we don't need multiple servers and multiple teams to maintain them. I can do things from a single location with a limited set of resources.

The majority of our processes are in the unattended mode, but we do have certain processes in the attended mode where certain end-users provide me the real-time information. We have designed a process where we give a specific form to the user. When the form is filled by the user, a process is automatically triggered, and the robot starts processing. It gives real-time statuses and information to the end-user in terms of what we are doing, how are we doing the calculations, and how are they going to get the benefit by opting for certain features within our organization. I can run my processes in the attended and unattended mode. So, I'm able to trigger both modes of automation very easily.

I am able to keep my customer data integrated. With humans, a data leak can happen, but in the case of robotics, my data is very secure.

The way the processing happens is also very smooth. For example, if I'm on leave or on a break, and a customer calls at my help desk, I won't be able to respond. Now, we have chatbots or robots running throughout the day. When the executives are not there and anyone calls the customer support team, customers are able to get a resolution. They don't have to keep calling or wait. Automatically, the bot is able to respond to their queries and concerns. We have been able to reduce the response time. My customers are pretty much satisfied with it, and they don't have any complaints. Previously, the satisfaction level of the customers was not that great.

The best part of automation is that we can easily integrate multiple technologies within a single tool. I can do it at ease with all of my data flow. Automation is happening across the globe, not only in my organization. Every time we do automation, we feel that there is something overlapping in every process. If I automate a process for my organization and your organization, 50% of the things would be the same. I can very easily maintain common things in automation tools through common libraries or common components. For the remaining 50% of things, we use different technologies. We are integrating optical character recognition (OCR) technologies for document processing. We are also using multiple machine learning methodologies to do pattern matching. We are using artificial intelligence to give a response that is comparable to a human response. 

We use its AI functionality in our automation program. We get multiple requests, and they can be through telephone, emails, or documents. When a request comes through the telephone, the robot or automation is designed to convert that to text. When a request comes through a document, we are using AI features. The document might not have a proper structure, and a customer can give any set of data in any format. So, we have built a special template or format, and this AI is helping us to extract the document with the most accurate results possible. We are getting an accuracy of 95%. With this, dependency is also gone. A human has to properly go through a document. Then, we have to convert the data to the file and process it. With AI, irrespective of the size of the document, which can be 100 pages or 500 pages, we are able to exactly locate the data that we're looking for, and we are able to extract and then process it through automation. We are able to smoothly integrate multiple things within a single process.

Its AI functionality has enabled us to automate more processes. It takes a human 23 minutes to process a 500-page document. With AI features, it hardly takes 7 minutes to process the same document. There is a great reduction in the time taken to do the same task, which is a huge benefit. With AI, I can look for, find, and extract specific information in a particular document, and then I'm able to process the information at ease. I can have documents in different formats. For example, each insurance customer or service provider can have different formats. A human would have to scan through multiple pages to reach the conclusion that this is the right data. AI can easily process different formats, whereas a human being has to be trained for different formats. Humans might also understand something and forget something, but that's not the case with AI or automation tools. They always remember the instructions given to them, which has drastically helped us in making our processes more accurate.

It has contributed to end-to-end automation in our organization. End-to-end automation helps us in completing things in a shorter span of time and utilizing resources in a better way. Previously, for every step of a process, we used to have a different team. We had a separate team for the following:

• Requirement gathering
• Answering the queries for the customers
• Responding to the queries by the ticketing system
• Responding to emails
• Processing particular processes at the backend
• Supporting the infrastructure in real-time

Now, all these things are done by robotics. I only need a few people to maintain my infrastructure. 

We use the UiPath Apps feature, and it has definitely helped us. If there is something that is not available within our team, we can directly use all the apps and features given by UiPath. We don't have to dedicatedly set up a team to design that app. If I have to design a new app or a chatbot for my customers, I can easily integrate the UiPath Apps feature instead of recruiting people, training them, and expecting them to give me the output. UiPath provides help and documentation, and if I require any licenses or support, UiPath's team is always available to assist us.

The UiPath Apps feature has increased the number of automations that we can create. It reduces the time to create automations. We can easily create automation. For a small process, we're able to roll out one automated process every 21 days. We are able to roll out an automated and complex end-to-end process every three or five months to our customers. Previously, it used to take us at least six months to one year to roll out the new features or new functionality to customers, but now, the time has drastically come down. 

It speeds up or reduces the cost of digital transformation. Every time we automate, we are able to speed up automation. We are able to do more things, and more people are working on automation. By using new features that UiPath is bringing and the learnings from my past experience, we are able to automate very quickly. Four and a half years ago, a process used to take four months. Now, it only takes 25 days for me. They have added many features, and I don't have to sit and design those features. They are constantly providing new features in their quarterly releases, and I can simply make the best use of them and implement them in my process.

Previously, I needed people in different shifts, and every human being might not have the same speed or enthusiasm. Humans also need breaks. A robot works throughout the day, and it has a consistent processing speed, so we are able to process more and more. I can plan a target with my robot, and I am able to achieve that. If I'm adding new customers, I just have to integrate one or two more licenses, which is very easy. I can easily create or configure a new robot and start processing. With humans, I have to train them again and again, whereas with automation, once a process is ready, I can use it in multiple robots. I can use it for 25, 50, or 100 robots very easily. I can scale my process rate very fast.

Previously, we were able to process 5,000 customer requests in a month. By using automation, we are able to do the same amount of work within 10 days or even within a week. If we add more human resources, it increases the cost for my organization, whereas, with robotics, I can configure 10 robots or 100 robots. It doesn't increase the cost a lot for my organization, and I can process everything that I want. I don't have any backlog.

It has freed up the time of our employees. This additional time has enabled employees to focus on higher-value work. I am utilizing resources in a much better way, and I am able to give them the work that is interesting for them or is relevant to their growth. When people in my team started working, they found the job interesting. After working for more than two to three years on the same thing, they don't feel that they're doing something new or learning something new. By using automation for a lot of things, I am able to train my team on the new things or technology that they are interested in or want to work with. I am also able to give the work that they're looking for. It is bringing more satisfaction, not only from the customers' perspective but also from my team's perspective. I am able to keep the same resources in my organization for a longer period of time because they're very happy. They are not dissatisfied with the organization.

It has definitely reduced human error. Our accuracy is 99.2%. With humans, our accuracy was 96%, and by using robotics, we have brought the accuracy to 99.2%.

It has also reduced the costs of our automation operations. In the initial year, we saved 10% of the day-to-day operational cost that we had when we were doing things manually. In the second year, it was 30%, and it has increased in the subsequent years. So far, almost 60% turnaround in the business profit has been reported.

It has saved costs for our organization. Previously, for a process, I had to train, for example, 100 people and keep them in multiple shifts. I also had to give them multiple facilities to be a part of the organization, whereas with robotics, I only have to design the process once, and I can use it in any number of bots, such as 10, 25, or 50. It also helps in scaling at no extra cost.

By using automation, we need fewer people for support operations. If the customer queries are taken care of by chatbots, my data and patterns are being analyzed by using AI and ML, and the scanning of the documents is taken care of by OCR, I need very few people for support operations. I need only 10% of people for providing support around the clock.

We are using the entire automation process most commonly. We are also doing scheduling. Our processes are running on a fixed date, so we are also using schedulers or timers. 

We are also using AI technology. We have AI Fabric, and we are doing the entire extraction part of the document through UiPath, which is very helpful. We're able to do everything within this single tool, and we are not dependent on other tools. We don't have to license more tools from the market and go to multiple tools to do the same work. Within this single tool, we have every feature that we need for our organization. 

It is a very simple tool to work with for anybody. Simplicity is the best in UiPath. It also has the best community support. If we are looking for any solution, we can directly reach out to UiPath at any point in time. 

The new features or functionalities that come with UiPath upgrades don't work perfectly in the initial days. Their new releases are not stable. We always find some set of issues. I have to work with the UiPath team for a week or so to resolve the issues, and then I'm able to use it. The stabilization should be there. We expect UiPath to reduce the number of errors before rolling out new features to end-users or customers.

In addition, many times, the apps or activities that we use within UiPath for designing are no longer compatible when a new upgrade happens or the version is changed. We want UiPath to look into it.

I have been using UiPath for almost four and a half years. 

It is one of the very stable tools. We don't see any breakdowns happening within the tool. 

We only have to design the process once, and we can use it in any number of bots. It helps in scaling at no extra cost. After we design a process, we can reuse it in subsequent designs. I just have to work on the things that are not already designed. So, there is a 10% to 30% reduction in the new processes that we design. Scalability improves with each and every design.

There is a user base of 100,000 users who are benefiting from automation at the moment. With manual processing, if I had a team of 1,000 people, then with automation, I would need 50 people to automate all processes. I would have four to five solution consultants or solution architects and around 15 to 20 developers and testers. There would also be people who are doing the business implementation, giving guidance to the customers, and doing the production rollout and handover preparation for the customers. 

Our usage is increasing. With every new process that we design, we are able to integrate more and more. Previously, we only used to integrate with OCR, and now, we are also using chatbots, AI, and ML. So, our processes are increasing, and we are definitely expanding.

The support that we get from UiPath is one of the best. We are a direct channel partner for the product. Every time UiPath comes up with new features or functionalities, they come and demonstrate that feature and help us to understand them so that we can help our customers with their implementations. We get direct support and the licensing, pricing, and certification benefits from UiPath.

It was pretty straightforward for us. We were able to build the entire infrastructure within a week. This includes getting licenses, doing the installation, and configuring the robots. We found the UiPath documentation very helpful while doing the installation and configuration. 

If I design a process today, I can deploy a process to production within 30 minutes of time. It is very quick. In terms of the implementation strategy, we go to the customer and understand their pain points. We then identify the processes that can be automated and tell them about the benefits and the timeframe for implementing a particular process to their server. We also tell them when will they start seeing the result and how they can achieve what they need by using multiple integrations of the tool. They don't have to spend multiple licenses on different tools. Everything can be done within a single tool.

We use a tool called TFS. With a single click, I can deploy my process from development to QA. In the same way, I can move my process from QA to UAT, and then with one more click, I can move it from UAT to production.

As solution architects, our role is to help the design team understand the design that has to be built. They take care of the design and testing. For the production rollout, we have an infrastructure team. We also sit with the business team to make them understand the process, how robotics works on a day-to-day basis, and what are the things that they have to monitor. Whenever we design a process, we make sure that all the complexities are handled. We are also handling all the compliance, and the integration is done smoothly. After a process is designed and approved by our business team, our accuracy stands at 99%.

In terms of maintenance, it doesn't require expensive or complex application upgrades or IT application support. UiPath is pretty simple. The basic infrastructure works in most of the servers, and we don't need frequent upgrades and maintenance. It is very easy to maintain.

We have seen an ROI. In the initial year, we saved 10% of the day-to-day operational cost. In the second year, it was 30%, and it has increased in the subsequent years. So far, almost 60% increase in the business profit has been reported.

There is no additional cost apart from the standard licensing. There is a one-time cost for the infrastructure setup.

We did evaluate multiple RPA tools such as Automation Anywhere and Blue Prism. In terms of the ease of designing, the ease of use, and from the cost perspective, we found UiPath to be the best tool for our customers.

Anyone who wants to automate processes should understand the process, its complexity, and the volume of the processing or the number of transactions to be processed. You should do proper analysis before you select the tool and licenses.

UiPath provides a lot of benefits and reduces the cost for an organization. It is one of the best tools in the market. The support that we get from UiPath is one of the best, and most of the features provided by UiPath are simply amazing.

Initially, people are hesitant to use automation because they don't know what automation can do. Anybody who uses the technology in the right way will get lots of benefits from any technology. Your implementation strategy has to be proper. You should check the feasibility of using a particular technology with existing processes in the organization and the benefits you can get.

It helps us in reducing the time, and we are also able to bring more business to the company. By making my processes digital, I'm bringing more revenue to my company. We visit a customer's site and try to find out the processes and pain points. After that, we analyze the entire solution within UiPath and tell the customer about the best solution and what would be the reduction in time as compared to the normal process.

I would rate UiPath a nine out of 10.

We have licenses for 15 robots and they are running internal processes. We develop them using UiPath Studio and we only use unattended automation.

Our primary use case, which is 70% of what we have automated, is related to our booking system. Instead of having 10 agents who handle the booking or creating the reservations, the work is done by the robots. Sometimes, bookings are very simple where you have just airfare or the hotel, but in our case, it's quite complex. We call it dynamic packaging, which will have a flight component, you can have a hotel component, different attractions, meal options, a rental car, and more. Instead of entering all of the options manually, which can take up to 10 minutes or 15 minutes just to create a single booking. It is similar when we perform other tasks, such as making a payment. These things are normally done in our target system. I have created robots and workflows in UiPath that are triggered by the database, and they complete these tasks automatically. We have 15 robots conducting the job.

The second use case replaces the agent when once we get all information from the outside system using a .NET application and store it in the database, it creates parameters for the robots to make a booking or reservation at Universal Studios for attractions.

The third use case covers all of Europe and it is a completely automated car booking system. 

Basically, our use cases are all about travel and booking systems for Universal Studios, general dynamic packaging, and car rentals.

UiPath has definitely improved the way our organization functions. It normally takes one agent approximately six hours to create reservations in the booking system manually, and now the job is left to RPA with UiPath workflows. It saves between 40% and 50% of the agent's time, leaving them time to work on something different.

The accuracy of tasks has been improved because everything is data-driven, and there is no problem that comes from human error. The system is almost bulletproof; if you send garbage in then you get garbage out but definitely, there are no human mistakes. For example, instead of entering the name of the customer, it comes straight from the database. The same is true for options like the times of picking up and dropping off your car. The only problem that we have is not related to RPA; it's the case where the target system is not responsive. For example, if you're moving from one screen to another and the system doesn't respond, then we are notified via an alert. 

The improved accuracy and shorter time to complete tasks, freeing up resources for other jobs, translate to money saved. Given that our processes are complex, the automation of them takes a load off of our end-users. In some cases, they have to perform data entry in several different systems. For example, in order to make a booking, they have to use three different systems with three different interfaces.

With RPA, in general, there is also a fear that jobs will be lost but when you're always swamped at work, including overtime, night shifts, and working on weekends, RPA is a big help. 

UiPath has helped to reduce our hardware footprint by between 20% and 30%. We now have only 15 virtual machines running instead of 15 physical desktops. The amount of hardware required to operate the business is directly correlated to the number of human operators and the software that is running.

UiPath has saved us significantly in terms of costs, primarily because of the manpower we used to have for the booking reservation system. It frees up resources for the agents, IT staff, and people from various departments. For example, we have group reservation systems for car booking, flight booking, and others. UiPath has made an impact in all of these places and the cost saving is very beneficial. In the first year, we saved over $100,000 on the booking systems. After the initial project in the first year, two or three more systems were built, for a savings of $300,000 annually before COVID.

In terms of the time we are saving, it is quite low these days because of the COVID-19 travel restrictions. Pre-COVID, we were saving approximately 80 hours per day. The reclaimed time for our employees is now available for them to work on higher-value work. The savings is not only from the data entry but for troubleshooting errors, which no longer needs to be done.

We have offices in Montreal, Vancouver, and Toronto, and the majority of agents are stationed in Montreal. I am working in the Toronto location, so I cannot comment on the majority in terms of how employee satisfaction has improved. What I have heard from the executive management is that more people are happy because they are able to better focus on what they want to do. This is especially true because they do not have to spend many hours troubleshooting trivial issues. Instead, they are concentrating on higher-value work.

We are using approximately 70% of all of the activities that are available in UiPath. These include web scraping and data entry, where the information is stored in a database. We also perform database queries.

The biggest benefit that we have from UiPath comes from using the API.

The features that we use most often are database communication, scraping, and PDF functions. The only features that we don't use are those related to Excel, for spreadsheets.

For smaller projects, we are only passing parameters from .NET applications but in the newer projects, we are using features such as database communication and data scraping.

The ease of building automations is great. When I talk about UiPath, I am usually referring to Studio, which has a very intuitive and easy-to-use interface, yet it is very powerful. This is something that has improved with the help of forums and tutorials. In 2016, it was more difficult because there were really no forums so we had to contact the head office in Bucharest, Romania when we needed help. Getting a demo had to be done in the very early hours and there was lots of communication back and forth. It was a struggle to find solutions, although to be fair, they've been very helpful. These days, it is very easy to use because there are numerous examples, and UiPath Academy is available, along with other resources.

We have been using the UiPath Apps feature and it has helped with the ease and time required for creating automation. Everything has improved over the past several years, as in the past, there were no examples or tutorials available. There was no manual and it was very technical. At the time, you definitely needed programming knowledge in order to handle some of the scenarios. It was at times like this that we relied on support from Bucharest.

Even today, there are only a couple of programmers in the company who develop the bots. Even with the Apps feature, I don't think that the end-users are ready, although this may be because of the way that our organization is structured. Everything is given to the IT department because our scenarios are very complex, and not a simple case of data entry or something like that. With such complex solutions, it is definitely too difficult for our end-users.

There are a few areas that need to be improved, one of which we have already raised with the salesperson and technical team.

The first area that needs improvement is backward compatibility. If you have a newer version of the UiPath Studio or any product, then quite often, if you're a year behind or so, you cannot compile the whole project. This means that you have to rebuild system modules. It's not like a Microsoft product that is always backward compatible. For us, that is a huge obstacle because sometimes, we have to rewrite entire workflows. In our case, this is a massive undertaking that will take three or four months to complete. This is the main issue for us and it doesn't happen with minor release updates, but with major ones, we have to rewrite the entire project because it doesn't compile.

The licensing should be more flexible and more affordable.

We used to be able to integrate with .NET applications, where all of the business rules reside, and then invoke robots or workflows from there. Now, that capability has been removed, so we have to use Orchestrator. Converting our projects requires a lot of work because we have to move all of the business logic to the UiPath workflow. It is not an ideal situation for us because keeping the business logic inside our .NET applications is more flexible and more scalable.

When I was taking some UiPath Academy courses, I noticed that they gave us more complex tasks. There were expert-level examples, but the junior examples are missing. Furthermore, they give you high-end, very technical guides, but there are not really any examples. This means that you really have to dig and use the forums and ask people questions. Essentially, you have to try and find the solutions by yourself.

In general, if you have very large and complex solutions as we do, the overall workflow layout could be improved because navigating through the network components can be very inconvenient. You can still see the high-level of the workflow, but not a detailed one. It may take you several minutes to get to the component you were looking for. In terms of navigation, the mapping solution could definitely be improved. There are always workarounds. What you can do in this case is use the flow charts with the sequencing module to break it down to a more general view. This makes it faster to get to the module that you want to improve or fix.

I am a Senior Lead Developer in my company, and I have been using UiPath since 2016. I was one of the very early UiPath users.

Stability-wise, we haven't really found any issues lately.

In the earlier versions, from 2016 and 2017, there were some issues that were never resolved by the UiPath team. The newer versions, especially while performing web scraping, are much more stable. Once it was deployed, we haven't seen any issues with the .NET applications.

Instability in our use case is the result of the target system; for example, the one that is operated by Universal Studios. If they are unresponsive for perhaps 20 or 30 seconds and the robot is expecting to see a certain screen, especially when it normally only takes two or three seconds to move from one screen to the other after submitting a request, it is going to cause a problem. However, that's not the fault of UiPath or RPA in general, but a fault of the source or target system.

I estimate that with all things considered, UiPath is 99.9% stable.

UiPath is very scalable. We are a mid-sized company with approximately 200 to 250 employees.

There are three or four of us who have hands-on experience with the product, and there are between 100 and 110 end-users. This includes four or five departments spread across three different locations. Our end-users are primarily business users.

Our goal is to increase our usage of UiPath but we are currently downsizing due to the COVID situation. We have some projects in mind, but we have to wait to see what happens with the travel industry. With approximately 50% of our employees laid off, no progress will be made. However, down the road when we get back on track, we plan to use other areas of the system. That will include manipulating spreadsheets, data entry, interoperability with other systems, and interfacing with it.

The technical support is definitely good, although there were some issues that never got resolved. The situation is that we are based in Canada and our salesperson from Toronto organizes the meeting with the technical staff from New York in the US. There were times when they couldn't help us because the majority of them had been with UiPath for two to three years. They didn't understand how things were working back in 2016, '17, or '18, well enough. Ultimately, they never found a person who could help us and to me, that is not really acceptable in terms of finding a workaround or the fastest approach to resolve the backward compatibility and .NET Integration.

What we needed was somebody with five or six years of experience and they could simply not find one.

We had some basic automation running prior to UiPath, but it was native SQL and .NET applications. An example is that we were using scaping options available in Microsoft applications, but it wasn't really RPA. UiPath has definitely helped us to reduce the costs of our automation operations. Everything is now run from one application, and you can use the workflows to collaborate between databases, spreadsheets, and booking reservations. Basically, it's end-to-end in terms of the development lifecycle because originally, our tasks were only partly automated.

If you consider automated testing solutions then we were using Selenium for things such as load-testing, in a previous company. I had no experience with a full RPA solution before UiPath in 2016.

In our early stages of automation, the task would start and then only get to a certain point before a different application had to pick it up. We had a scheduler that was responsible for this. The scheduler would see the partly completed task, then take it and put it somewhere else for a third application to take over. Now, all of this is done using the UiPath API.

Specifically, in terms of overhead operations, UiPath has saved us approximately 80 hours a day, which translates to between $4,000 and $5,000 per day, just in one department. If you multiply this by 30 days then it is a lot of money. Given that it is a ballpark figure for just a single department, it could be even more.

Back when we first installed UiPath, it was complex. But now, it is much easier because they have grown. It is much easier than it was five years ago, although, at the same time, we haven't had many issues in the process of implementing and rolling out our solutions.

Our deployment is on-premises and entirely private.

These days, it takes less than a day to deploy. In 2016, it took us almost a week for much simpler deployments because there was no proper documentation. Fortunately, at the time, we got lots of help from the technical staff in Romania.

When we first started with UiPath, it was not even close to what it's today. It was much difficult to create a strategy because it more or less was a black box. We purchased the product and there was only UiPath Studio, nothing else. There was virtually no documentation and more or less, everything was left to us, our team, to develop this strategy.

Implementing it was more of a trial and error process than it is today. Finally, we did it. We moved our automations from the development environment to the staging environment, and then finally into the production environment. Now, it's pretty stable. At the time, however, it was pretty cumbersome and difficult because there was no proper documentation or guidance from UiPath. Nowadays, it's pretty simple.

There are three of us in the company who are responsible for deployment and maintenance. We also handle the monitoring, implementation, troubleshooting, and updating of the product and robots.

We also have an infrastructure team that is outsourced from a company in Toronto, Canada, called Carbon60. Our experience with them has been a little shaky, but we are handling it okay. They could not really help us as much with the initial setup of UiPath because they did not have experience with RPA. We gave them the specs required for our infrastructure, and they set it up. Overall, approximately 90% of the setup was our responsibility.

Compared to four or five years ago, the licensing in terms of price is less flexible and less affordable. Recently, because of the COVID situation, we need 15 robots. Ideally, we could use five robots and Orchestrator instead, and pay the difference, but the vendor refused to take this offer.

We are currently using the Community Version of Orchestrator for training purposes.

When we started looking at UiPath, they had less than 100 customers in the world. We had been looking at three different options that included UiPath, Blue Prism, and one other one. In our case, we were using a legacy application that was Java applet-based, and the other products were not able to handle that well.

From what I recall, back in 2016, UiPath was the only option that supported Java applet-based automation. We needed the functionality because one of our internal applications was not web-based, but Java applet-based, and depended on it. It did not work immediately and there were some workarounds, but with some help from the UiPath technical staff, we were able to handle it. This is the main reason that we ultimately chose UiPath.

Essentially, UiPath was the only option that was able to handle Java applet automation. With that covering the front end, we automated the whole process.

In the future, because UiPath was not able to handle the legacy projects that we developed in RPA, we might consider another product like Blue Prism. We would assess potential solutions based on backward compatibility.

We have been thinking about using the Orchestrator with the cloud option, but because of the current world situation, especially because we are in the travel industry, our income has been significantly reduced. At this point, we are more or less in survival mode, so we decided to stay as-is.

We were also supposed to get Orchestrator, the latest web developer, and a production license but we gave up because we cannot afford it at the moment. Travel may be idle right now but post-COVID, which hopefully is next year or by end of this year, we're going to get the official Orchestrator license.

Originally, we were using .NET applications, which is the technology that has driven the business. It's huge, and with the newer versions of UiPath, it is no longer possible because we have to use Orchestrator. At this time, we are more or less working on a workaround and it's a massive project that is probably going to take six or seven months to complete.

We are not using the AI functionality yet, although it is something that we're planning to look into, eventually.

The biggest lesson that I have learned from using UiPath is how much time was consumed by our manual processes. Definitely, we have freed up resources for our business team. In terms of accuracy, there are no human errors anymore. Consequently, we can free up between 30% and 40% of our agents' time in terms of analysis and billing. In summary, the biggest thing that I have learned is that using RPA is about improving accuracy and reliability.

My advice for anybody who is implementing UiPath is to start with the training. These days, especially younger developers, people are very keen to jump on developing RPA and they're doing this stuff without using Academy or other training. Rather than do that, I suggest people get familiar with the product and use the training material first. Use the examples that are provided because the UiPath Academy is amazing in terms of that.

In summary, this product has a very intuitive and powerful interface. There are very good examples and scenarios on the UiPath Academy website, and technical support is very helpful. You can also find lots of good examples in the community forums. There used to be only one OCR option, and now there are two different flavors of OCR, which is definitely one of the pros. However, the major cons are backward compatibility and licensing in terms of flexibility and affordability. We also lost some of the functionality for .NET integration, which was a problem for us because the capabilities are simply gone.

I would rate this solution an eight out of ten.

Our use case is mainly for PDF automation for invoicing. Specific data from the invoice needs to be gathered, entered into, and compared within the SAP application we use. We face challenges as the formats of the invoices change and can range in length from a single page to up to 100 pages. 

We've integrated a tool called ABBYY FlexiCapture and ABBYY will help format and be used as the source of input for the UiPath bot. This bot in turn will process each and every necessary customer detail to the SAP application. If everything is correct, and the data meets the parameters, an email will be sent to the customer, attaching the necessary invoice. If there's an exception, we'll be able to look at that too.

There are some other sets of use cases as well, which include SAP or Hyperautomation. However, we also do generic workflows where we have data from multiple domains and will need to build our XML output. The XML output will contain a lot of data (such as the date, time or name of the customer) which will keep changing and is not fixed. I built a bot using UiPath that I host on Orchestrator which can monitor this data.

Another use case is placing job descriptions into an analyzing tool to search for keywords. Depending on the sort of description which we have pasted in, it will throw out a certain set of outputs, such as if the word is feminine, masculine, how many details it contains, how long it's going to take to complete the description, et cetera. This part has been done using an API key, and therefore it's not a normal cut and paste job. 

There are a lot of processes that are, even today, done manually. I can take a simple process in, for example, ServiceNow, where issues are made into tickets and put into queues. Previously, a person would have to pick up the ticket and then assign it to a variety of people, but first, before even doing that, they would have to check in on those team members and figure out who had the most or least workload to be able to address the ticket.

This process is automated now. There's no human intervention in assigning tickets. The bot will monitor the queue and when a person raises a ticket and can monitor which person is working on which ticket number, and who should get the next ticket. The turnaround tie has been reduced by a lot and is also saving us costs when you look at it in relation to the entire project as a whole. 

The most valuable feature is the API.

It's really compatible with other solutions and it got integrated when I was working with ABBYY. There is no dependency. I just need to trigger my bot and that's it. I didn't need to go and separately trigger to work on every part of it. It is really good when we talk about the integration of UiPath with any other tools.

I am currently working through the documentation to help with understanding the solution and it is really great.

From a studio perspective, I really like the feature of debugging.

It’s making automation really feasible and ensures that it takes less time.

The ease of building automation using UiPathis great, even if a person doesn’t have a development background. Just by going to the UiPath Academy and doing the basic certification, any user can start to understand the process and begin automating.

In my first organization, there were two or three developers including me, and our challenge was that we had a lot of projects. We had certain process analysts that would run on different sets of processes. We were able to train them and make sure that they understood the processes and could start developing. We saw a lot of progress in them, and, due to the fact that the tool was really easy to use and didn’t require a lot of coding, they were able to do a lot just by drag and drop functionality.

UiPath enabled us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automation. It really supports the end-to-end deployment of any project or any task and makes it very easy.

The Automation Cloud has helped decrease time to value. If there was no Automation Cloud, we would need to run the bot from the studio all of the time, or we would need to create an upgraded file and trigger it via a third-party application, like VBScript or something like that. It has reduced a lot of time. It also makes deployment really easy. For example, if I am working in a development environment, I publish to the cloud, it will start reflecting in the Orchestrator and I just need to push the package. From the Orchestrator itself, I can trigger that particular package to any other machine. That makes life a lot easier - just publishing the package and testing in any other system and understanding how the UAT is going.

The deployment in production is really easy. I have tested Orchestrator and production Orchestrator and I just need to copy the package from the studio and download the package and push it back to the Studio or Orchestrator production, and the work is done. I don't need to manually copy and paste the packages again and again.

Automation Cloud, in a way, helps decrease UiPath's total cost of ownership by taking care of things such as infrastructure, maintenance, and updates. There’s no need, for example, to host on different servers or a defined cloud. It has definitely reduced a lot of costs due to the fact that, instead of going for a different set of applications for a different set of projects, now we are relying on UiPath for most of our work. Whether it’s invoicing, finance, or an HR process, we can rely on UiPath to automate a particular process instead of going back and forth across multiple tools.

Automation Cloud allows us to also effectively scale up automation. It is very easy to monitor any process which is running correctly, and, with automation, you don't need to have any separate application downloaded into your system. It is just an URL. You just need to have a URL and you just need to enter the URL and you can monitor from any system and easily understand how the process is performing.

On top of that, with Automation Cloud, suppose you have 10 licenses. You can see how many licenses have been consumed by how many processes and what the outcome of the processes was.

Moreover, you can integrate your cloud with other tools and create a dashboard. With a UiPath dashboard you can see, for example, the percentage of success rates, the failure rate, and how many processes have been successfully done or what quality. From the management side, we don't need to go to the logs and check what has run. We can directly look into a dashboard and we'll come to understand how many processes are running successfully and what are the outcomes, and how many licenses have been consumed.

It is important that we can scale automation without having to pay attention to infrastructure. I’d rate the level of importance at an 8.5 out of ten. It is helping a lot.

When we talk about automating a web application or we need to work on a different set of applications, we used to get integrations and we needed to have, for example, a PowerShell scripting application license. Now everything is being replaced by UiPath, or most of it is. It does not require you to have a license for a different set of tools all the time. If you have UiPath it is easy to integrate with any third-party tool and it is easy to automate a web application or desktop application or even code. If I know the coding, I can just do coding right in UiPath itself. Instead of going for multiple tools, for multiple projects, it's just a single tool for multiple projects.

We can use the infrastructure and we can also host it. Suppose there are two users who are accessing the same VM over a different time zone. They can rely on the same VM and they can use the same UiPath tool and do not necessarily need to have a separate licensing for it.

UiPath has helped minimize our on-premise footprint. Mostly now, everything is on the cloud instead of on-premise and it is making life easy. For example, suppose a person who is working on-premise, if he logs out, then the other person can log in and cross-verify the work he has done. With the cloud, now the transfer of files is easy. If a person falls sick or something happens that he's unable to make it then the other person who has a login or credentials with him can just directly go in and start working. If a code is being published in the cloud, we can just copy or download the code and cross-verify how it's working.

We do use attended automation. We use it relatively less compared to unattended. However, in certain cases, where the project is too critical and we do need to run all the time, it’s nice to have that option. Attended automation helps scale RPA and benefits our organization by automating specific processes that require human, robot collaboration. There are certain processes where you can't automate end-to-end. We have to rely on a human being occasionally, and it’s nice to have automation we can collaborate on. At the same time, we do largely take advantage of automatons where no human intervention is required.

We use UiPath AI functionality, although not much is being used in any of the projects which I have worked on. I’m just looking forward to it, as I am currently working on documentation understanding before diving in.

UiPath speeds up the cost of digital transformation and has also reduced costs. I started with Blue Prism and then I got my hands on UiPath. Now, I can see the transformation which is happening and I can see the comfort which we have with the tool. I can also see how it’s a lot easier to deploy the tools.

The solution has helped our company reduce human error by a significant amount. For example, when I automated the complete process and I put everything in GPL step by step and automated using UiPath, the best thing that happened is that there was one invoice that got stuck and I could see that the bot didn't process it. The bot has sworn an exception stating that there is a certain set of values that a bot should not process, if it is not matching, the quality is not matching, then the bot cannot process it. When the customer logged into the particular invoice and they saw that, okay, the value which is being mentioned in the invoice is below the threshold critical value. For the first time in over a period of 13 or 14 years, they came across a particular invoice that got stuck with this particular amount, which was below the threshold level. The bot captured something that needed to be dealt with, and the client was so happy it was caught as it saved the company a lot of money - around $1 billion. After catching that threshold, they have monitored all the invoices for the past 13 or 14 years and they came across a lot of differences. It has played a major role in saving a lot of money.

UiPath has freed up employee time. The faster you deploy, the better. We look at months instead of weeks when calculating time. If a ticket, end-to-end, takes 24 hours to resolve, for example, with automation, we’ve managed to reduce that time down to seven to ten hours. It will keep following up and sending emails until there is a resolution, and those reminders are quite helpful in moving the process forward. It’s definitely allowed employees to focus on more important tasks and there’s less time spent on follow-up.

In terms of employee satisfaction, when we are developing something and we have a proper outcome, it makes life easier.

The product has reduced the cost of our automation operations. Not for all the processes, however. If the process is really simple, just like 10 pages or 20 sequences or 10 activities, then the cost is high for a particular license, for a particular process. That said, when you talk about the complex process, where the process takes 48 hours or 90 hours to process a particular activity manually versus what the bot can do in just five to ten minutes, it impacts the cost. Now, a single bot is taking care of that and there is only one person instead of many who monitor the process. Likely, it has reduced costs a lot, roughly 50 or up to 70%. Overall UiPath has saved costs for our organization. Processes that needed five people can now run with just one or two running things with a bot.

When the Orchestrator got upgraded and UiPath didn't get upgraded, we started getting errors regarding the managed packages, the packages were not getting upgraded. There are little things like that where we’ve had trouble. We have just made sure that if the company is upgrading and they have a license to upgrade Orchestrator and the Studio, they do it simultaneously instead of waiting for a week or two weeks or one month. If they have upgraded the Orchestrator, and they have not upgraded the studio, it will impact the developers.

In terms of the upgrading of the on-premise orchestrator, there are organizations that are upgrading their developing environment but they're not upgrading the production environment. Therefore, now, when the bot or the particular package will move from a higher-end environment to lower activities, it is not working well and it needs to get downgraded.

While delivering or providing the license, we need to explain to clients that this particular product, if you are working on a development and production environment, they have to keep them on the same packages or they have to keep your production higher, so that if they move the packages, it won't impact anything.

I've been using the solution for the past five years.

The solution is very stable. I have not faced any difficulties at all. 

Until now, it hasn't scaled a lot. From 2018 to 2021, the tool, the overview, the look and feel of the tool have been scaled a lot. It has scalability, definitely. We haven't scaled it a lot. 

In our organization, we have between 100 and 150 users on the solution.

The vendors are really helpful. Whenever we have a concern regarding any of the issues, including if there is an issue with upgrading, it gets resolved well. For example, when we upgraded the studio and didn't upgrade UiPath’s Orchestrator, there were some issues. The board was not connecting to Orchestrator. We had to raise a ticket to our support team and it got resolved. 

I'd rate them at an eight out of ten, as we've gotten a good response overall.

In the last five years, I have worked in two to three organizations. All of them have started exploring automation tools. I've used Blue Prism as the very first tool, then I got the opportunity to work with UiPath and explore the different sets of opportunities with it. 

At this company, WinAutomation was previously used. That was four years ago.

The initial setup is pretty straightforward. It's not too complex. 

We have a server we implemented the solution on. We installed the certificate to have the application installed with the Orchestrator URL.

The deployment took around two days of full-time work for us. There were multiple servers involved.

The implementation strategy was very simple. We got onto a call with the UiPath team and they had a lot of data with them, including all of the details regarding the applications. We wanted our certificates to get installed and we had our internal team involved as well. Between the two teams, it was working properly and it got installed in less than the expected amount of time. 

We have a team of 25 to 30 people that can handle deployment and maintenance. Maintenance would be, for example, if you have certain packages missing, someone would have to deal with that. Or if something wasn't working as required. Another example of maintenance might be if we are accessing multiple applications, or if we are accessing SAP, and there were tools that the bot accessed, the maintenance team would need to go and check the particular environment on which the bot is going to get deployed.

From the very first organization, I have implemented UiPath end-to-end.

We don't use a third party for deployment now. We have our own team. There's an internal team within our current organization which deploys everything.

I don't have any details in regards to the pricing.

We did POCs in the past with WinAutomation and we also looked at Automation Anywhere. At the time, we were looking to deploy more on the cloud, which is why we went with UiPath instead.

I am just an end-user of the product.

I'm not sure if the version we are on now is the latest. It likely isn't. We are in StudioPro currently.

I'm not sure about the infrastructure side of things, in relation to the cloud, as I'm more on the side of developing and deploying the project. We have an internal team that looks into cloud deployment and other stuff. While we were working on and purchasing the license from UiPath, the very first instance, then definitely the team got integrated with the UiPath team, however, after that, the internal team is capable of handling the end-to-end part of it.

We don't use UiPath as a SaaS solution and we do not yet use UiPath apps.

In the process of UiPath, speeding up and reducing the cost of digital transformation, I have never required expensive or complex application upgrades or IT application support, however, we have a different set of teams that work on the licensing part and the management side of it. They likely worked with UiPath to get their issues resolved. I do not have much knowledge regarding this.

A person who's starting on UiPath can also up-skill himself with the tool as well as it is easy to learn. 

The best part about UiPath is that they provide a trial version. Any organization or any individual or any business looking for automation solutions can give it a try. There are a lot of things which you can explore and you have a lot of integration. If we have a module that is already running, which has been designed in almost any language, you can just integrate that in UiPath and keep that running.

It is reducing a lot of dependencies on other tools and it's making sure that our lives get easier from the deployment and monitoring perspective. From the licensing and the cost perspective, there are a lot of items that are really helpful. In terms of integration with third-party tools, they have a lot of packages which are available on the internet. You can download the packages and integrate it with any other tool. It really makes UiPath a better solution for organizations compared to any other tool.

The biggest lesson I have learned from  UiPath is that if a single step of the solution is not working, you have to keep trying. There are other ways of doing things. You have options. There are a lot of ways by which a user can understand and explore.

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

I am an RPA developer and I work with UiPath in that capacity.

Our current use case involves the automation of a process involving healthcare-related data. This is confidential data that is received from the customer and inserted into Oracle forms. Reports are then generated from it and these reports are then used by the organization, which is in the healthcare domain, for their analysis.

The data being analyzed includes medical and treatment history. For example, with the current pandemic going on, there are all sorts of healthcare data that is related to it, including various types of treatments. When somebody walks into any clinic or hospital, all of the treatment is entered into a database and we get an extract of it. The analysis is used to get more details.

Another interesting use case, prior to this one, involved the documenting of invoices. We were working with approximately 250 different samples of purchase invoices, many in different formats. One might be a native PDF file, whereas another could be a scanned PDF, and yet another might be a simple handwritten invoice that was converted into a PDF based on a picture that was taken from a mobile device. We were receiving these invoices from our client and they wanted to extract data from them. It was accomplished by using the Document Understanding features in UiPath.

The other notable use case had to do with issuing refunds for purchases that were made on an e-commerce site. When a customer made an order and there was a problem that resulted in them wanting a refund, there were multiple ways that the client could request one. A refund application could be received by the customer care department in the form of a simple call, which was a verbal request, or as an email written by the customer, or as an automatically-generated email that was created based on filling out a form on the website.

Regardless of which of the three input methods is used, the refund request is gathered and sent to a mainframe application. At that point, the information is extracted from the mainframe and the refund is issued using another application.

The automation of these tasks using features such as artificial intelligence and document understanding has reduced our costs. For example, with the invoice processing use case, there was a team of between 20 and 25 agents who were doing it manually. Obviously, a team of that size has a large cost associated with it. Also, the volume was very high, which meant that the team was not able to deliver on all of the work. There are approximately 250 vendors sending invoices to our customer to process the data, which translates to about 1,000 documents being sent on a daily basis, to be processed by only 25 people. It was a huge task. With this level of volume, people tend to get frustrated. 

We implemented the automation and the team size has now been reduced to only five or six people, and that is only required to monitor the bots. For example, they check to make sure that the data being fetched using document understanding is at par. We have set the minimum confidence of the documents being scanned at 90% and each day, a report is generated and sent to the customer. Overall, it was a very cost-saving implementation.

When it comes to building automations, it's pretty simple. UiPath has a lot of features, starting with process mining. For example, when a business person wants to start from scratch, they don't necessarily know which process to automate. They can use the process mining feature available in UiPath to get an answer as to whether a particular process is worth automating or not. Features like this are available to shorten the processes. Once a process is identified, we can go ahead and implement and develop the automation. Overall, it is very easy to develop automations because of the inbuilt features.

UiPath provides us with features to implement end-to-end automation, and it begins with the initial steps. They have process mining or task mining features to help companies that have an appetite for automation but don't know what they want to automate. Once a process analysis is completed, it can determine whether a process can be automated or not. At that point, we can proceed to the bot development.

Once the bot has been developed, there are different options, including third-party support, for deploying them. After a bot has been deployed, they have the hypercare facility to monitor and maintain bots that are in production. Taken together, all of these features facilitate end-to-end automation. This is very important to our work. 

Consider that UiPath did not always have the process mining feature. In those days, in order to do process analysis, companies had to hire Subject Matter Experts (SMEs) for different domains at the beginning of a project to determine which processes could be automated. For example, if there were a requirement for a healthcare process then the company had to hire a healthcare SME. The SME would assist in process analysis and in the determination of whether it was something that could be automated. Nowadays, with the help of the process mining features, we no longer have to worry about who is doing the analysis.

From our standpoint, we have to do the recording and supply the inputs. With this, a report will be generated and it will tell us whether the process can be automated. If so, then the developers or an architect will come in and do the development. Following this, the DevOps team will come in for the deployment. Finally, the production support and monitoring are taken care of by the developers.

Using the cloud-based deployment helps reduce our on-premises footprint because we no longer have to take care of servers and local databases. There was a separate team taking care of the networking aspect, and another team taking care of the databases. For on-premises deployments, there are different teams that come into play, whereas with a cloud-based solution, we don't have to worry about anything. UiPath takes care of deployment and the databases, and everything is automatically handled. I can't estimate an exact percentage of how much our on-premises footprint has been reduced, but it has really made a significant impact in terms of substituting or replacing the on-premises facilities.

Attended automation has helped to scale our RPA benefits and in fact, in my almost five years of experience, I have not come across a scenario where the automation could be purely unattended. In the use case with the invoices where we used document understanding, there was still a minimally-sized team of five people in place after the implementation. They monitor the processes and if the criteria of 90% are not met then the invoice will be rejected and sent back to the vendor. In this case, attended automation is really helpful.

The Automation Cloud saves our IT department time because we don't have to worry about hiring different teams for different tasks. The infrastructure maintenance is handled by the vendor and all we have to do is pay for our licenses, then everything is ready.

Automation Cloud has helped to decrease our time to value. You don't have to worry about how the installation is to be done, you just have to pay the license fees and the team will do everything. They have packages, and you just have to give them the numbers according to what you need. Based on that, they will propose a solution and propose an infrastructure for you. Once that is agreed, they will do the installation within a very short time. After that is complete, your developers can start doing the development and within no time, you will start seeing the ROI.

The Automation Cloud has indeed decreased our overall costs.

It is really helpful for an organization to use the Automation Cloud when they do not have sufficient resources available themselves. In situations like this, the UiPath Automation Cloud plays a very important role. You just have to give them the number and they propose the solution including the infrastructure. You just need a few developers and everything else is taken care of by the Automation Cloud team.

We have a lot of clients who are looking at digital transformation, but they don't know what tool to use. There are a lot of vendors available in the market who provide products that are similar to UiPath, but UiPath has a lot of very strong marketing, a strong sales team, and at the same time, the product is very good. UiPath helps in doing quick installations, quicker deployments, and quicker turnarounds. Ultimately, it really helps with digital transformation for any organization.

Digital transformation requires an upgrade, but it is not very complex and not very costly. A company may have to be 25 to 30 million dollars to upgrade, which is a significant cost, but if it saves 100 million then in the end, the organization is saving money.

UiPath has helped to reduce human error to a great extent. When humans perform the same task over and over again, we tend to get bored and frustrated. Our excitement goes down day by day. However, when it comes to machines or bots, they don't get bored and they don't get frustrated having to do repetitive work. This leads to fewer errors, which has a positive impact on the business. There are fewer escalations and the customer is happier.

Our automations have helped to free up employees' time by reducing how long it takes them to complete their tasks. It leaves them time for learning or performing other jobs, and in general, it helps to reduce work hours. I estimate that percentage-wise, it saves my team between 30% and 35%. The total time saved is approximately 250 hours per month.

One of the ways that our employees benefited from having time freed through the use of automation is upgrading. A lot of people, in particular our technical staff, upgraded by learning new technologies. This ultimately led to helping the organization because they are able to work on different jobs.

Automation also leads to an improvement in employee happiness. If you ask them to do the same thing over and over again, on a daily basis, they get bored. When 30% of the time is saved by using automation, it frees up perhaps two hours a day for them to do different work or even recreational activities. 

UiPath contains a lot of very useful features.

The artificial intelligence and document understanding features are very good and have been helpful when it comes to processing handwritten or unstructured, especially when there is a high volume and it is repetitive. 

Using the artificial intelligence and machine learning features had a drastic impact on our use case. In the scenario where we used document understanding, we were able to successfully automate the use case without artificial intelligence. However, there was not a sufficient improvement. The success rate was between 78% and 80%. We did not use these features originally because they come at an extra cost and we did not have approval. When we were given approval and acquired the licenses, we re-implemented the automation and included the inbuilt AI and ML models. Our success rate went up to between 92% and 93%, which is significant.

The Orchestrator is in drastic need of improvement. Three or four years ago, the Orchestrator UI was very simple and comfortable to use but now, they have added so many features that it is difficult for new users to quickly understand it. The latest implementation that we did was so complicated that nobody was able to understand it, aside from the developers. Generally speaking, UiPath needs to improve the interface, and the overall user assistance should be boosted.

The developers are the core users of the product and it's important to make the product easy for them to use. The easier it is, the more people start using the tool. Then, as there are more developers available, more organizations start to hear about RPA tools and Uipath.

I have been working with UiPath for approximately four and a half years, across three different companies.

I have found that one or two times out of ten, UiPath Studio hangs and needs to be restarted. These types of technical glitches do happen but not often.

In the organizations that I have worked in so far, the UiPath features and the licensing available meant that we didn't have to worry about the infrastructure setup or scaling. You can start with a small number of licenses and robots, with little infrastructure requirements, and gradually, as you need more robots and more powerful infrastructure, you can scale up. It has great scalability. 

Even if somebody is using the community edition, we are able to build a PoC for them. In fact, using this approach gives us a pretty good idea of how the automation will proceed. Based on this, we get an idea of what the infrastructure will look like. Then, if everything fits into the customer's budget or request, we will go with the enterprise edition and implement the solution. Throughout the process, scalability is not an issue.

In my department, we have between 70 and 80 people working with UiPath. Out of these, 80% are developers, perhaps between 10% and 15% are business analysts, and the remaining people are solution architects or tech leads.

We use UiPath extensively because it helps with quick implementation and a short turnaround time. Deployments are very quick and easy to do. Given the current pandemic situation, I don't see the demand for UiPath or any other RPA tool going down.

I have been in contact with technical support many times and they are very good.

The issues that we typically face are related to Studio and sometimes licensing. The support has a fast turnaround time and if the organization is large, with a lot of licenses, then they have dedicated support for them. It is not necessary to deal with customer care, for example. Instead, dedicated technical support is available and they are really good.

The companies I have been with did not use another RPA tool prior to UiPath.

As a developer, I have not been directly involved in a UiPath installation or implementation. It's generally the responsibility of the implementation team that every organization has, and developers don't have the authority to simply download and install or implement UiPath. That said, I have given my input in the past.

Every company has a QA team and once they identify and finalize which automation software they want to install, the implementation team takes care of it. In my experience, the developers are given an instance of it to use after this.

It used to be a very simple installation, although, as I have seen UiPath change over time, it has become very complex. They have now Studio versus Studio X. They also have the Automation Cloud, which is different from an on-premises deployment. Somebody who is new to UiPath will not be able to do anything.

In terms of how long it takes for deployment, it depends on what process you want to automate. A very simple process can be automated, end-to-end from process analysis to deployment, in about a week. Complex automations have been taking us between six and eight months to complete. It all depends on what kind of automation you are doing.

In general, the implementation strategy is simple. Again, it depends on what kind of process we are automating. If the process is very complex and it involves a very high volume of data to be processed and stored, then it will require greater network bandwidth and more database storage. It may also need a fast server, with regards to processing speed. 

All of the implementations that I have seen have involved an in-house team. There are different departments involved, such as the networking team, the database team, or the IT department. Also, for the latest implementation that we did, involving Automation Cloud, the UiPath team helped us.

UiPath has reduced our overall costs. For example, if you are replacing 25 to 30 humans, where instead you only have to pay for licenses, the expenses are much less.

The company and our clients see a return on investment through savings in time and costs.

There are different licenses available, including variations for an on-premises versus a cloud-based deployment. For example, an on-premises installation is very easy and not very costly, and is suitable for a client with a simple optimization that does not have cloud-based requirements. Generally, companies do not have to worry about infrastructure because of the different options that are available.

Different licenses are used to activate features that the organization wants to use. For example, they offer licenses for UiPath Studio X, attended automation, unattended automation, document understanding, and so forth. They also have customized licensing and packages available. For example, if a customer requires 50 attended and 150 unattended licenses, but it does not fit into an existing package, then UiPath will create one for them.

They have an on-demand, floating license available for companies to save on costs. In this case, if a company wants 40 licenses and is only using 10 at a time then they only have to pay for the ones that they are using, with the remaining 40 triggered only when requested.

There are other automation tools on the market, such as Automation Anywhere and Blue Prism. Of these, UiPath is very strong and this is because of the UiPath academy for training, the UiPath certifications, and other things that impact the RPA developers.

The company that I am with did not evaluate other products before choosing UiPath.

Over the time that I have used it, the number of resources available in UiPath has grown to a very high level. For example, with the advent of Automation Cloud, the organization no longer has to worry about protecting against on-premises failures.

I have used the UiPath Apps feature but have not yet put it into production. I have completed a PoC and done some self-learning, but I haven't yet come across a scenario or process where we have to implement it.

We completed a proof of concept where our client was looking for customized input forms for their client. In that case, if I had to write the code for this customer's input form, I would need to hire additional resources at an extra cost. It might be, for example, code that has to be written in Java. In UiPath Apps, we were able to create a customized form for our client within a span of two to three days. It would be able to handle their various survey-related inputs. This feature is very helpful because it is much quicker than writing customized code for the client.

The Apps feature did not affect my IT department's workload but it did reduce the work required by my team. This was important because our client was not originally seeking to use UiPath for this part of their project. Instead, they had confidence in us and asked how it could be done, and whether Uipath could accomplish it. When we completed the input form using Apps, it definitely helped in reducing my organization's workload and in turn, reduced the overall cost to the client.

In summary, the features are very good and there are plenty of tricks and tips available, depending on what it is that you're trying to do.

I would rate this solution a nine out of ten.

We are an auditing firm who has a certain level of tasks that are open for automating. These are complete steps, which can be performed by anyone, standardized, and do not involve any human intelligence. These are just basic human tasks. It is a long process, where in-between there are certain validation and verification steps as well as certain steps that involve a lot of documentation to go through. The organization is targeting all these tasks, which are completely static and can be automated, so they can get rid of them. Then, employees can work on something more useful as well as more productivity-oriented tasks.

Currently, I am dealing with our internal COE, providing RPA solutions to internal and external clients. UiPath is a driving force in our COE.

It is on-prem. There are a couple of discussions going around upgrading UiPath because there has been so much advancement with the solution.

Document Understanding was a game-changer. One of our clients has manual billing that needs to be processed. With the help of Document Understanding and UiPath Action Center, we created an excellent workflow for our client. It also gives us better accuracy. Now, there are hardly any exceptions in the client's billing documents that are being processed.

In my previous role, I presented some clients the end-to-end installation design of UiPath, e.g., building a PDD using Task Capture, going to UiPath Studio to build the actual solution, and then later going to post-production Insights. 

UiPath has helped to minimize our on-prem footprint. Most organizations prefer on-prem because it reduces the risk of compliance issues.

Attended robots have been very beneficial for our users. UiPath saves one robot for every user. We have a couple of clients who are using attended automation for their day-to-day tasks.

From an organizational point of view, the most used feature is Orchestrator because that is how we manage more than 100 users. When there are more than 100 users, it is important, and probably better, to have some place to manage them. Orchestrator is doing that for us very well. 

The most exciting new feature is UiPath Apps. I have explored it in-depth to get a better understanding. I think this product will be a game-changer for my organization as well as for my clients. It will revolutionize the way that we are providing licensing and proper access to a user. It also revolutionizes the way people are using it. Everything will be on the cloud, which I think is the most interesting feature of UiPath Apps.

UiPath Apps will definitely help to reduce the workload of our IT department by enabling end users to create apps. If you are creating an app and sharing it over the cloud, that removes the dependency of having UiPath installed with the correct version as well as Internet connectivity. Or, you might have a global server in the background that is not functioning very well. There are multiple issues related to connectivity of the UiPath robot when deploying it on a user's machine. 

If you are giving access to a group of users and adding Azure container or any other container provided by UiPath, then this reduces 10 to 15 hours of work from the IT or support guys who are manually doing all these things by themselves. Not every user must have the new step of getting the UiPath license and software installed, it is really static. You are eliminating that task completely by having UiPath Apps on the cloud. This is definitely convenient for users to use.

We are not using UiPath Apps in my current organization. About two to three months ago, I created UiPath when I was at TCS. It was there that we demonstrated the power of UiPath Apps versus normal, conventional methods. It reduced our work through scalability. It helped us to easily scale and was more convenient, because giving new or temporary access can be a pain. 

It is very easy to share UiPath Apps. When you want to start or remove it, you can do it with a simple click within the cloud. It is not that complicated. Also, the usage is better in UiPath Apps compared to the conventional UiPath robot. In UiPath Assistant, you can access the portal and simply run it over there. Therefore, you will not have a problem with the background functioning of the UiPath robot or even connectivity issues. Scalability and ease of use are favorable for users when they are using UiPath Apps.

Recently, I have been exploring Automation Hub. Its idea to pipeline a feature will be very useful for our guys managing RPA products on a large scale. 

When it comes to debugging, there is some improvement needed for UiPath compared to other RPA tools. There are features to edit the workflow or content of the automation file while we are debugging. For example, we have 10,000 lines of code that we have integrated by 10 different users. So, there is one integrated code and you are debugging it. After some time, you might find a line which is not an error. You may have forgotten to remove it or change the value to your desired criteria. It is really a pain to stop the entire debug session and just edit it, then start again at zero. It will do the same steps again just to reach that level or step where you were actually stuck previously. Whereas, in different automation tools, whether you are on the findings step or in-between a debug session, you can actually edit that information. This is good because sometimes the developer also forgets to add or remove certain values in-between a long code. I think this should be improved in UiPath. This should already be in consideration because I have been in touch with UiPath a couple of times because of this.

My current company is currently looking at the end-to-end solution. However, Insights and Task Capture are major concerns. Task Capture will give you a skeleton of the PDD, then you have to edit it. The skeleton is only there for simple automation, and we have complex scenarios. It is so complicated that the PDD generation using Task Capture will not give you even 20% of the output. While Task Capture is something promising, people are looking at it with greater expectations than it provides. People are not using Task Capture or Insight because of their limitations. These features could use improvements and enhancements.

I have been using UiPath for three years. I recently switched companies. I worked with Capgemini and TCS prior to this company, where I was in their COEs and providing solutions to clients. This is the first time that I have been on a project for PwC. Since the start of 2018, I have worked mainly in COEs and have interacted with around 30 clients up until now.

PwC, as a firm, has been using this technology for four to five years.

I have been using UiPath on a different powerful system that has high-end RAM. Sometimes, it crashes due to the use of multiple components at once. For example, when I was using Druid with data service and another UiPath product. Developing was quite easy. However, when debugging, sometimes it would freeze. I don't know whether it was because of my system and its compatibility, my system's configuration, or the fact that we were using so many high-end tools and products at once. 

The robustness of the tool, when it comes to using high-end products, is something that I am currently exploring. This is something that is currently a bit of concern for other developers as well. I have been interacting with a lot of developers around the globe. As a part of that, I tend to share my experiences. They have shared that it will sometimes freeze, even with simple automation. Because we are using new features or products all at once, it freezes. I think this should not be the case. If you are using long, heavy code, and it gets frozen at one point, I can understand that. However, 10 simple lines of code, while using three or four products at once, is getting frozen. That should be taken care of or improved.

To troubleshoot the system crashing, we contacted UiPath. They were kind enough to reply and have a discussion. They are working on this and trying to make it more convenient so future releases will solve this problem.

As a part of a COE, we get clients who expect us to present the entire proof of concept as well as a PPT or presentation. For example, why they need to go with UiPath, what are the advantages/disadvantages, if any, and why we should not go with another tool or solution as a whole, not just RPA. The main point for us when presenting UiPath is the ease of usability and scalability. We don't need major infrastructure changes, just two or three URLs to be widely fitted. Then, they need to decide if they want unattended or attended robots. The scalability is the major driving force which excites our clients and us, because there isn't a need to have media-heavy software or heavy processes changes.

Clients don't want every user in their organization who joins to have a long process to get through the start up. Automation Cloud is something they were very much interested in exploring because of the scalability. They find it very easy to use and scale, because not all the clients have a certain set of users using robots. 

I have seen user usage explode from zero to a bigger audience of 22 users.

UiPath is used extensively in my current organization on a large scale. There is also a plan to scale it to more users.

PwC has their internal teams providing a "help center" sort of infrastructure to them. If there was a need for any help, or some basic doubt, it is solved internally. PwC's internal help center exists already. However, for major issues, we reach out to UiPath, as a customer, so that we can receive a response and clarity on issues.

The technical support is really great. I have been in touch with all sorts of UiPath support because I was in the COE and our clients were completely global until my latest assignment. I think UiPath India, France, Belgium, and Canada are timely. They provide a very precise support experience. They were kind enough to let us know the actual reason, because just saying that it is a bug is not something that we can comfortably accept or digest. Also, they have been kind enough to follow back up on updates and bugs that we have reported.

As a whole, I have reported more than 25 bugs across all their products. They were kind enough to reach out to the same forum where we raised the ticket. They were kind enough to reply that these are the updates that they will roll out in the next version. It is good to have this interaction as well as a heads-up regarding your bug reports. I think the technical support is on the mark and doing their job really well.

The learning tools and support are really great. They have the most engaging forum across the globe, compared to other RPA tools. The learning and engagement are really up to the mark. That also brings confidence to our clients and us. We are a part of their global community forum, which is a benefit for us. 

Their marketplace has grown tenfold in the last year. It is because of the developer's involvement as well as involvement from people in the community. UiPath is creating their own statements and usable components, which adds value to our presentation. The tool is growing, and developers and community members are growing with them. 

My previous companies migrated from other RPA solutions, like Automation Anywhere, Blue Prism, and NICE Robotic Automation, to UiPath because of the value of its features and the quality of the overall solution. I migrated my clients from those companies so they could have a better ROI and reduce the cost of maintenance. We also migrated from scheduling tools, like AutoSys, to provide better accuracy and ease of use.

My current company was not previously using an RPA solution.

The initial setup and implementation are standard, simple, and user-friendly. UiPath just requires basic adjustment, then it is plug and play. It is very easy for everyone to understand, e.g., non-technical clients can understand what has been changed.

If the deployment is done properly, you will see better data accuracy with UiPath than manual entry. If the deployment is done by someone without much experience, it will affect the quality of the solution due to bad coding. You can't just leave it to the tool.

Using Automation Cloud makes it easier to deploy.

It takes almost two weeks for us to implement from scratch because we must understand the client's infrastructure, create a solution design, and then present it to them.

We present our clients with a PoC, including a document that justifies the work and costs. We also give them a standard robot that we created for demo purposes. This way, they can visualize how it will be implemented and mapped in their organization.

For deployment, one or two people are sufficient: one from an infrastructure background and another from a technical background. Sometimes, it is complex or hard to understand the client's needs when it comes to the deployment of Azure, Nvidia, or AWS servers on their VPN connection.

The amount of staff needed for maintenance depends on the size of the solution, e.g., the bigger solutions will need more people. However, the maintenance and support activities can also be automated and that reduces the need for support and maintenance. Three or four support team members are enough with the help of a robot.

The last ROI calculation that we did for a client showed that they saved 25% of their time by automating a manual task with an unattended robot for a single machine.

Overall, the cost remains the same to the client and us, when using Automation Cloud, because of the amount of money spent on the cloud migration and cloud usage.

At my previous company, in the best scenario, we removed almost 200 hours per month of client usage, making it automated with almost zero errors. So, about 32 employees were freed up from their work per month, and now there are only two. This has enabled employees to focus on higher-value work that involves human-base interaction. This saved the client money and provided a recruitment benefit.

UiPath has been useful for improving employee satisfaction. Employees are now spending time on more value-add work instead of something static, whether it is boring or hectic, that they have been working on for ages. This gives employees a sense of advancement.

I would rate the pricing as seven out of 10, where 10 is the most expensive. The pricing increased with the latest release. It used to be cheap. Now, it is expensive. However, it does come with supported features, which almost justify its cost.

Building automations is very easy. I have used multiple RPA tools. Developing automation with UiPath is very convenient compared to other tools. 

Development is very easy. I have been exploring certain markets based on the marketplace component and its native integrations with ServicesNow for the chatbot. I think development is where UiPath stands out as a winner compared to other tools because starting to automate is very easy.

Compared to other RPA tools, UiPath is leading with new feature additions every quarter. Obviously, all the new features will not be incorporated into the solution or be helpful for the client. We see the organization putting in efforts to grow at a rapid pace, including ML, scaling, and everything on the cloud, like data servers. UiPath gives us the confidence to present a tool that can be relied on because it is constantly growing. It constantly has certain new features added which can be beneficial.

With UiPath, not everyone needs to understand the code, which is great. This makes it superior over other tools because it is easy to understand. This contributes to profits because clients prefer UiPath over something else because they have more confidence using it.

Blue Prism has the ability to edit in the middle of a debug. As far as I have explored, Blue Prism is leading on the debugging front and stands out against UiPath. Debugging in Blue Prism gives users a lot of usability to edit the workflow. This makes it easier for developers to run things once and get things done. Otherwise, debugging multiple times can sometimes be a pain.

People migrate to NICE Robotic Automation because they were having difficulty maintaining their software with a limited number of staff. 

It is easier to become more proficient with UiPath than other RPA tools, especially Blue Prism. Training can be done at almost no cost.

I would suggest automating a policy that is not a requirement and follows a process. As an RPA user, it is your responsibility to get things done in an efficient way. If a user is doing A, B, C, D, it might not be required that the robot do the same thing. There might be a shorthand that can take you from A to D directly using the robot. For example, it can go directly to a page and not have to click 10 things like a human.

If you use it properly and consciously, it can increase accuracy and reduce error. If you don't, then it will be the other way around.

As features are concerned, it is reasonably priced compared to any other heavyweight tools in the market.

It is beneficial that there is a SaaS option because this offers a diversified cloud environment. If we expand and explore more cloud options, then having a SaaS solution for UiPath will be beneficial for us. Right now, SaaS comes with a certain amount of compliance issues for my company. 

UiPath AI Center is very useful. I think it is a game-changer when it comes to better usage. However, I haven't had much of a chance to explore it on an enterprise level. Not many clients are using it because of the exposure risk. Once a lot of developers start exploring and developing on it, then more companies will have the confidence to say, "Yes, we can push to that," which will increase the usage of UiPath AI Center.

Everything on the UIPath Cloud is a template. It is just a starting point. You have to dig into it and do more exploration to make it better.

Using Automation Cloud would be very beneficial for us, as a COE, because we are getting rid of the mundane tasks of infrastructure, maintenance, and upgrades, which we do not think are our primary job.

Biggest lesson learnt: UiPath has the fastest growing community with the quickest learning tools. It is easy to automate. It requires basic understanding and effort to get started. 

I would rate UiPath as 9.5 out of 10. I have concerns about the debugging capability, where if I need to edit something while debugging, I can't do it right away without stopping the process.