Kofax RPA could improve web-based automation and there should be a choice of what browser we can use, such as Google Chrome, instead of an inbuilt browser from Kofax RPA. Additionally, Kofax RPA is missing an orchestrator that other solutions have, such as UiPath.
Robotic Process Automation (RPA) Orchestrator Reviews
Showing reviews of the top ranking products in Robotic Process Automation (RPA), containing the term Orchestrator
Kofax RPA: Orchestrator
Kofax RPA could improve web-based automation and there should be a choice of what browser we can use, such as Google Chrome, instead of an inbuilt browser from Kofax RPA. Additionally, Kofax RPA is missing an orchestrator that other solutions have, such as UiPath.
Automation Anywhere (AA): Orchestrator
reviewer1681449 says in an Automation Anywhere (AA) review
Software Engineer at a tech services company with 501-1,000 employees
I would rate Automation Anywhere seven out of 10. It is a simple tool to learn, and with A360, they have gone way beyond. They also have an intelligent bot. However, I would suggest going with Microsoft Power Automate ranter than Automation Anywhere because Power Automate's cloud flow is easier to use. In addition, you can use Power Automate with very minimal coding. With Automation Anywhere, you need extensive knowledge of SQL and .NET. You have to learn so many things before implementing Automation Anywhere.
I have worked on Automation Anywhere for four years and also UiPath. Between these two, I have found Automation Anywhere easier to work on. Also, it's stable because I have delivered around 20 plus automations on Automation Anywhere to date. Based on my experience, I have found Automation Anywhere to be more stable and accessible. I prefer Automation Anywhere.
In my previous organization, I had worked on UiPath, but I haven't worked on UiPath much for the last two-plus years. So I only have six to eight months of experience on UiPath. I find the Orchestrator feature quite complex and difficult to understand. When I was working on UiPath, they had just introduced their advanced features in Orchestrator, so I found UiPath much more valuable from the .NET perspective. But if we're talking about how easy it is to program, Automation Anywhere is more straightforward. For the past one or two months, I have started getting my hands on Power Automate. In terms of cloud flows, I find Power Automate more useful. Every tool has its pros and cons. After working on Automation Anywhere for around four years, I do find it easy and scalable. But now, now that I've been introduced to Power Automate, I find that I like it because of built-in connectors and templates.
reviewer1641549 says in an Automation Anywhere (AA) review
Associate Vice President at a computer software company with 10,001+ employees
The initial implementation is straightforward. Most people are using the orchestrator on the cloud or the control room and when it comes to the creator and bot runner, it will always be on the on-premise. The cloud implementation is easy, you do not have to install anything, and when we use it in the Automation Anywhere Cloud, it becomes even easier.
The time it takes for the implementation depends on the environmental requirements. For example, if it is single or multi-node architecture. If it is a single node, it is straightforward. If it is a multi-node architecture, then it will take a little time. You just have to understand the other component that is present, such as any secondary server.
Blue Prism: Orchestrator
reviewer1542615 says in a Blue Prism review
RPA Solution Architect - Lead Developer Individual Contributor at a tech services company with 51-200 employees
I would recommend UiPath because it is easier to use and faster to implement. But if a company has budget limitations and because UiPath has more licenses, if you want to acquire Orchestrator, for example, it requires another license. Blue Prism gives you a license for a robot, then a license for everything else. If there are no strict limitations on budget, I would recommend UiPath.
We use attended and unattended bots, Orchestrator, and Studio for development.
We're seeing increasing adoption of Studio because more people see how easy and straightforward it is to use a lot of the features. It helps that UiPath training is free. Our entire team, including our salespeople, have gone through the training. It's free and it makes a big difference. For the salespeople, they're able to talk more intelligently about RPA.
On a scale of one to five, judging how beneficial it is, I would rate the training a five, for sure. In fact, I have taken a lot of ideas from their training to educate my customers about RPA. When it comes to RPA, a lot of it is education because some of them don't know exactly how automation can be done. I've told UiPath that I use their training in my presentation, and it is great.
We are working with a technology company called Rammer, Rammer.ai. What the Rammer software does is listen to conversations to learn the details of what is being discussed. A third-party system is used to transcribe the conversation into text, then Rammer will learn the details without much training. It knows the topics, it understands what is talked about the most, talked about the least, how much we are adhering to the script if it's a call center use case, or if it is a simple meeting use case then it knows who is assigned what tasks, it recognizes the follow-ups, and it knows the summary of the discussion. All of this is summarized in a nice, consumable manner. So now, when a bot knows all of this information, it goes into Orchestrator, logs all these activities that are picked up by unattended bots downstream, and they trigger all those processes back. So it's a massive consumption of all of those heavy use cases.
We have not yet run automations in a virtual environment, although we do have customers who are asking for it. We are not sure if we will need UiPath's help for this yet because we haven't tried it.
With respect to how easy it is to automate our company's processes, on a scale of one to five, I would rate it a five. Really, it depends on how clearly we understand the requirements. So a lot of times we are able to find process gaps, which wasn't the case earlier before we started thinking about automation in this manner. I would say the ease of use is actually dependent on some of those factors as well.
Usually, starting is the biggest challenge for most people, and I think this is because it is in a trial environment and there is a lack of documentation, with multiple people doing one part of a small subset of a task. There are these challenges and then if none of them are documented, you need to figure out the process flow. From person one, where does it go? This can change when people can do multiple things.
It becomes a very complex web to understand and navigate through. We need to understand the task and how it should be performed. For developing the robot, it's very important to have the clarity upfront, otherwise, we cannot code them. That is the biggest challenge, I feel.
From the point that a UiPath license is purchased until the first bot is ready is almost immediate. This is because we usually start with a PoC on a small scale, just to see if automation with this approach makes sense. By the end of the PoC, we'll normally know exactly how many bots are needed. Sometimes it is on us, more than the customer when we cannot estimate every process that is outside of the departments and division that we work with because we just work at finance. For example, we can't just estimate what marketing would use, and so on. That will sometimes delay things.
Kishore Kumar says in an UiPath review
RPA Developer at a tech services company with 10,001+ employees
I like the document understanding feature. It gives us more accuracy.
The AI and machine learning features are very useful for us.
UI Targets enabled us to quickly build automations within multiple applications, even without the right connectors. For example, we can drag and drop Outlook activities.
We use UiPath selector technology is a wonderful feature, especially compared to other RPA tools.
From mobile applications, we use Orchestrator where we can monitor processes and share them.
The fact that we don't have to worry about future installations and upgrades of Orchestrator, was important in our decision to go with UiPath, because those things are already built in. We don't need to worry about the infrastructure part. It is maintained by the UiPath team. They also have better community support to help us if we face any problems. That is one of the great things about UiPath.
Having the cloud-based version allows us to be at the latest version of UiPath Orchestrator and different products without having to take care of the upgrade process.
UiPath's portal for enabling business users to trigger and monitor jobs is a big deal for me because it's something that we have been trying to do for a long time. We have been asking for it. With the previous solution, which was the orchestration platform alone, it was not a good approach because the business users would have a lot of information on their hands and you have to either split your licenses so that they could not access everything, or create your own web portals for them to access specific parts.
The fact that they now have an intermediate portal where they see only their processes, which they can monitor for themselves without getting too much information that is not relevant for them, is a big deal. Something as simple as triggering your own process, which in the past would require dedicating a full license to, can now be done through the portal. It might be a task like checking emails for customers or creating your own application with their API. It's a huge increment in quality.
The portal can also be used for administrators and although we have the Action Center, we don't use it that often. From the point of view of administrators, I can say that the recent improvements make our life much easier. It also enables us to think of more complex setups. In the past, I would never allow certain configurations because they would either be a security risk or it would just create more problems than solutions. Now with the current interface, especially with what they will be adding in the future in terms of more governance from the platform, they just enable you to do more complex things. It allows you to go a little bit beyond what the normal scope would be.
That applies to the platform as well as the orchestrator in the new modern setup. They have the option to split within the same tenant and different companies, or different company departments. Also, the fact that you can dynamically allocate the licenses so that you don't have to worry or have to split them, brings us to another level.
It offers more granular and role-based access control and management. We now have more complex scenarios that in the past we would not even consider because it would be a problem if someone were able to see something that they should not see.
The fact that this is a SaaS solution is important to us and it is clear to me that they want to push a SaaS solution, more than the on-premises deployment. It means that we have the latest version without having to upgrade the systems. We always have the latest version of the studio, for example, and there's no disruption to our services. Furthermore, we are able to follow all of the previews that they come out with. We can try all of their new products, which is something that in the past, we would not have been able to do. It would have required, for example, upgrading our system twice a year. Certainly, we wouldn't be able to do it at the speed we can now.
Being able to minimize our on-premises deployment is really important. It was almost a given for us because we lost some of our interfaces during the cyberattack. From that point on, the company has had a clear policy of cloud and SaaS as a priority. The fact that we have the opportunity to access all of our services without any requirements from our side suits us very well.
The vendor continues to add services to the portal and we are connected through their insider program. This is something that we are really happy with.
It is helpful for us that new services being added to the portal are all managed from the same place because it simplifies our work, makes it cohesive, and makes sense from a philosophical point of view. Definitely, if they had it on different platforms, it would take away from the ease of management. The fact that they have it in a single place makes everything a little bit more interconnected. What they are doing seems to make sense and for me, it is good because we only have to take care of one single platform. This also speeds up our processes, which is a plus.
On the topic of security, especially coming from a cyber attack, having SOC 2 certification is important because it is a requirement for us. We probably would have tried to find an intermediate or an agreement, but the fact that UiPath is now SOC 2 certified means that we have complied with requirements.
In the past, stability has been great. However, more recently I have been facing some issues, and I'm hoping for some resolution. For example, we recently upgraded to the new orchestrator in Studio, and we had to upgrade a few packages also, In particular, the UiPath automation packages.
Some of our GUI activities, which are not fully backward compatible, have been facing some issues. Consequently, some of our bots have been impacted. We have already raised the issue and we are in discussion to find a resolution. This was the first time we actually faced an issue in terms of reliability with UiPath.
Our past experience has been very good, and I cannot say that we have any complaints regarding the reliability of UiPath solutions.
I have multiple use cases as part of this solution, since I work in different domains with different technologies and applications. We use attended and unattended bots.
One use case was for a credit-based client where we worked on the UI automation of the application. We were using UiPath Automation Cloud because our team is spread across different geographical locations, like the U.S, APAC and EMEA regions. We had different RPA developers who are developing the script simultaneously and putting it on the system, and our business case was that we wanted to automate the UI applications. Since there were different developers in different geographical regions, they created the bots on their system. Due to the cloud offering, we were able to move the bots to production using a click of a button. There is also an Orchestrator offering as part of the cloud, which is hosted. Once we had a thorough peer review of the bots being developed, we pushed it to our production-ready cloud-based Orchestrator. From there, we use it to run the script. That is an unattended bot, which is also one of the features. Since it is a credit-based UI automation, there are some instances where manual intervention is required in order to see whatever data is sent out to the client, if it is in the correct order or not. That is why we use the unattended offering of UiPath. Both these technologies help us a lot in creating our production-ready implementation.
For another use case, we did an implementation in the SAP application. It was a procure-to-payment (P2P) cycle, where a third party sends out the invoices which get fed into the SAP application, then it gets verified and goes out to the payroll team. Once that is verified by the payroll team, the payment is released to the concerned vendors. All these points of entry were being done manually: the third-party invoices entered into the SAP application, SAP verification, and the payroll team verification. Since it involved a lot of financial data, people were very hesitant to get it automated. However, since we had this UiPath offering, that initial hesitation was turned into a very good implementation of whatever we wanted to achieve as part of this UiPath automation. We were using the unattended bot as part of the cloud offering. We ran the processes at night from Orchestrator, so people working from home didn't need to stay up late in order to run the processes. Since we were using the cloud unattended bot service of UiPath, we were able to trigger the whole process in a single click of a button, which is amazing.
As part of the UiPath offering, we have three offerings: Studio, StudioX, and Studio Pro. These three offerings are provided via cloud on a single system and installed on our laptops or desktops.
I am working as a senior analyst. As part of this particular role, I have to cater to the client's needs if they want to get a UiPath implementation. Then, I do the consulting as part of the implementation. I also get involved in the PoC development and how we should use the cloud offering, e.g., what benefits are there.
Developing and deploying robots with UiPath is very straightforward. It hardly takes five minutes to deploy a process on Orchestrator.
reviewer1509951 says in an UiPath review
Associate Consultant at a computer software company with 10,001+ employees
We develop and deploy use cases in the area of the cloud. We have deployed over 100 use cases. Most of our use cases are related to SAP applications, web applications, and mainframe applications.
One use case example is related to mainframe applications. The bot monitors mainframe applications 24/7. If there are any new jobs, they are identified, then the bot changes the status of the job to differentiate it.
Previously, we are using the 2016 version of Orchestrator, then we upgraded to the 2018 version of Orchestrator. Some clients are deploying the 2020 version. It depends on the client. We suggest using a version back to clients, i.e., the 2019 version.
We automate retail, sales, and agricultural services.
We are using the solution's selector technology for UI automation. That is the most important feature for us. For example, one of the applications in our company is being updated day by day, by the development team. We use selector to make it dynamic.
We also use the latest version of the desktop Assistant tool for some queueing activity in UiPath Orchestrator. The tasks in the queue are continually updated and then they are run by robots. Using Assistant, we get a lot of information about our queues, like if something fails, for example. Also if a robot fails we get robot status-type information from the Assistant. The Assistant plays a good role because, if a process is going wrong, we have control. Using the Assistant we can stop that process. It is a most important feature from UiPath.
UiPath helps to implement end-to-end automation, although the discovery of processes, gathering requirements, and creating the design, all happen outside of UiPath. But the development, which is developing the bots, then testing and then deploying them, does happen end-to-end within UiPath.
The end-to-end development capability is important, but this is because every tool offers this and it is expected. That said, there is definitely room for improvement in that end-to-end should include process discovery. It is end-to-end, but those ends can extend further than what it currently is. In that sense, it's no different than other RPA tools.
Another way that UiPath improves the way our organization functions is that the robots can run 24/7. If you think about a human workforce, they work eight hours a day, they take days off, they get sick, they leave, and they take knowledge with them once they leave the company. But, the robots can be run non-stop 24/7, and each process can be scaled up. The same process can be run by one bot, or it can be run by 10 or 100 bots. This means that there's a lot more flexibility that the bots bring, especially for high-volume processes that perhaps even have some peaks, such as an end-of-month rush to produce invoices or meet a deadline or an end-of-financial-year crunch.
These robots have an easier time addressing and variability when it comes to volume. They really create a lot more scalability to where businesses can grow and know that they can meet the demands of the future. So, they're a lot more future-proof, whereas people are harder to rely on.
Speaking from a business perspective, it's the FTE savings. A company obviously needs to spend money on UiPath licenses and development costs, but those costs are oftentimes lower than the cost of that FTE, the full-time employee, whose work is getting automated. If you purely just think about the financial benefits, it's the lower staffing costs.
There is also the ability to free up people. This means that even if people aren't replaced and their salary isn't saved, what they can do is pivot their focus to, for instance, be a lot more customer-facing or do a lot more strategic or creative tasks that perhaps get pushed to the side because there's not a lot of time allocated towards performing them. Now, FTEs have a lot more capacity to contribute and perform tasks that still to this day cannot be automated, like creative thinking, complex decision-making on the spot, strategy, and just human interaction.
In the beginning, employees meet automation with a critical eye. They're thinking, "Well, what's going on? Why are these robots coming in? Are we going to work alongside them? How is this going to work?" But to be honest, in the end, there are winners and losers. What I mean by that is that some jobs are replaced, and that's just simply because of that FTE saving that is usually the driver to justify the cost of development. But on the flip-side, the employees that do stay and do work alongside the bots are usually a lot happier because they have to juggle a lot fewer things.
The robots are there to make people feel like people and not like robots, where they just do the same thing over and over and don't enjoy their job or don't enjoy what they do. A robot takes that away and helps people enjoy their work a lot more because they can do non-repetitive tasks. They can be a lot more customer-facing and perhaps build stronger relationships with their customers, know them better, and have more time available to work on other projects or work on other things that they may never have had the time to do.
In our organization, the robots work on multiple projects. The amount of employee time that is freed up depends on the project and what you are automating, but a pretty good estimate would be a 20% to 40% savings.
With respect to the reduction of problems related to human error, the fact of the matter is that some employees, whether you like it or not, are more error-prone. By automating a process, we were able to standardize it, and therefore, identify the cause of the human error and remove it by replacing the process with a robot that makes a more reliable judgment in terms of action. It is literally just an if-else statement. It's a lot easier to quantify and therefore it's a lot easier to evaluate, and therefore the result is a lot more reliable. Whereas with an employee, let's say the output of their work is a lot more unreliable simply because they could be working on 10 different things on the same day. There could be a deadline approaching, and the quality of work fluctuates with an employee because of it.
With a robot, you will notice that over time, in fact, the quality improves, and that's just the basic truth of RPA. It doesn't happen automatically, and it does require work. It happens because you see the results of the automation and you see areas for improvement, ultimately leading you to make adjustments. You iterate on the RPA solution and make it better over time.
Although it does not improve automatically, through a conscious effort you can be a lot more confident in the output and then be able to see unbiased results at the end of the day. Part of these results is your exception rates, which can be errors. It can be failures, whether technical in nature or decision-making business rule types of errors. Then, you can adjust your process to where it can positively improve that exception rate, and just iterate on that to where it becomes acceptable. Moreover, it's quite stable, which is not the case with the human workforce.
The automation cloud Orchestrator has its benefits and negative sides. The benefit is the fact that it's web-based. A person who has the login credentials can access it without the necessity to have something installed. The development and the monitoring of the bots are separated in UiPath, where the development happens in the Studio and the monitoring happens in the Orchestrator.
In other tools like Blue Prism, it happens in the same place. I've used both, and the Orchestrator is nice. It has a very nice UI, it's user-friendly, it has a lot of features, and I find it quite easy to use. For example, you can see all of the machines, you can see the robots, and you can schedule them. If the business wants to see a lot more across the output of the Work Queue, they can have that visibility from Orchestrator, which is great.
The downside of Orchestrator is the package deployment, which is perhaps another minus of UiPath in general. The deployment of a new package does not take a long time, but there are a lot of steps. It's not an intuitive process. If you have to release a lot of packages, which does occur, especially in the early stage of deployment, when you are releasing hotfixes, or when something goes wrong and you need to redeploy a fix really quickly to minimize business impact, it does slow you down.
I wish it would be just one or two clicks, rather than the whole importing or exporting and connecting to the desktop application and everything that accompanies it. I wish it were a lot easier. Again, it has its upsides but it's not perfect.
reviewer1510449 says in an UiPath review
RPA Developer at a maritime company with 1,001-5,000 employees
Just this week, we are launching our Automation Hub effort because we need to start building a pipeline for our automation candidates. Right now, we have eight or nine ideas in our Automation Hub. That will grow quite quickly because we need the help of Automation Hub to decide on which idea that we will be moving forward with next.
UiPath continues to add services to the Portal. It is fairly important that they are all managed from the same place because it is a single point of access, which was a factor that really played into our choice of vendor, UiPath. We use Automation Hub to sort of collect ideas and discover what ideas are good for information, then we use Orchestrator to manage them once they have been developed. We are hoping to use Insights at a later point, when that is available in the cloud, so we have a complete end-to-end solution in one place.
We are using UiPath primarily for unattended automation. We are automating processes for business functions like finance and go-to-market.
We have Orchestrator which is hosted on the cloud and we also have UiPath deployed on-premises. We have three different instances of Orchestrator: one for development, one for staging, and one for production.
The stability is usually really great. However, at this point, we are uploading a new version because the stability is not right. They told us that our version, 18.4.5, is not 100 percent compatible with Orchestrator. Therefore, we don't have the stability that we had before.
reviewer1513164 says in an UiPath review
Automation Consultant at a manufacturing company with 10,001+ employees
The initial setup is straightforward and very easy. The main component is called Orchestrator and then there are two more components called Studio and Development Robot. These two are connected to Orchestrator, and once the development is complete, you can do the unit testing on the same machine. After this, you publish the package.
Once the item is published, it will be pushed to the Orchestrator and then connected to the bot. This is where you're going to run the process. Once it is complete the bot will start running. The whole process will take approximately 10 minutes and you can move the data to production.
When the process is running in production, Studio allows you to troubleshoot from there, without having to move it back to the development machine.
The price of Orchestrator is pretty high in general as well as compared to other solutions, because Automation Anywhere does not charge for its Control Room.
We primarily use UiPath for end-to-end automation. We develop both attended and unattended bots and we use the Orchestrator module, hosted in Azure.
Some of our typical use cases involve automating operations like downloading files online, analyzing and capturing details, saving them in another location, transferring them, and uploading them in other forms.
There are a lot of really useful features in UiPath including the Orchestrator and the Studio.
The Orchestrator is one of the main tools that I use because I like to help orchestrate the bots. It is the heart of the tool and it gives me a lot of flexibility to automate or manage bots that are in the field. The Orchestration Server is one of the most important features and when you perform a deep dive, you see that it has a lot of functionality. It's great.
The Orchestrator has other features such as computer vision, AI, and machine learning, and it complements the bots and the Studio.
UiPath integrates well with Elasticsearch, which is a great search engine. ElasticSearch is more capable than UiPath for searching logs. I'm filling the gap in log reporting using ElasticSearch, where I'm feeding the logs into it and then creating dashboards, or using the analytics parts of ElasticSearch and Kibana.
The UiPath Academy is a very valuable component of this solution. Many of our employees have used the courses. With it, a person who has a little bit of an analytical mindset can easily learn to do many things. If somebody is willing to develop themselves in RPA, the UiPath academy is more than enough to do so. They will understand the components that make up the ecosystem. The academy is very good, well constructed, and has a lot of labs and exercises to help one learn the system by themself without any help, and very easily.
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.
There are some enhancements that can be made within Orchestrator, such as the addition of new dashboards that provide us insights into processes that are already running, which would help us a lot.
There are features that could be implemented on the coding side; for example, automatically assigning a unique ID for the "activity" used during the flow. As of now, if you use an activity via simple drag and drop, the activity keeps the original name. If you don't change the name of the activity manually then you will lose some information during logging. It would be useful to put a simple incremental ID on each activity, so even if you don't change the activity name, you will know where the process becomes stuck.
During the last update, the connection between robots and the Orchestrator (cloud) changed a lot. It would be a good idea to provide an easy way to use a single type of robot, regardless if it is a standard robot, floating robot, connected user, etc. Basically, have a simpler way to deploy robots in development, testing, and production environments.
I have worked on two UiPath use cases. The first use case is for the IT Infrastructure team for submitting server requests. They receive a request from a third-party portal through email, and then my bot reads the email and fills in the details in the company portal.
The second use case is the data extraction from Word documents. The team receives Word documents with some important contract information. I extract those paragraphs and put them in the CSV format given by the customer.
We are using UiPath Studio 2020.10.2, and the Orchestrator version is 2019.
reviewer1618680 says in an UiPath review
Manager and Lead - Digital Center of Excellence at a consultancy with 1,001-5,000 employees
Most of the time, we work with financial services to automate financial transaction monitoring systems. We go through multiple CRM and financial systems, then query the transactions based on the KYC information. We use OCR operations, using UiPath Robot, to fetch information, such as, identification number, passport number, and their tax information. We extract this information, then validate with our financial data or transactions data to ensure that there is no fraud nor anomalies in the system. If there are any suspicious transactions or potential fraud, we do manual investigations. Those manual investigations are redirected from the robot to a human agent, then the human agent verifies the information. If there are any cost validation requests from other systems, such as Salesforce and PeopleSoft, then another bot will be triggered using UiPath Orchestrator. After that, we do the remaining processing. At the end of the processing, we use the UiPath analytics service. That analytics service uses UiPath logs, which helps us to understand how the bot is performing and how many transactions we have validated. From that, we look at how many were successfully processed and how many were manually handled, i.e., exceptions. We identify business exceptions for any transactions during the initial pre-validation stage, such as the user identification number is not valid or input data validation errors. For example, passport information must be an alphanumeric eight digit. If the bot identifies that the value is not eight digits, but four or five digits, then it is an invalid record straightaway. We can see this from the reporting and performance graphs.
We do automation for our HR processes, such as onboarding processes. On any day, there are five or six people who need to be onboarded. This is one of our standard business cases. We have a UiPath robot design using UiPath Studio and then it deploys in Orchestrator. This robot is being used by the HR admin. They can fill in the key information of the user, e.g., name, level, and their package. So, they import all this information, which includes my identity information, mobile number, email, and IDs on an Excel file, possibly along with a few other associates joining tomorrow. Once those entries are made in the Excel file, then the user can trigger a robot. They also need to keep the file in a designated folder. The robot will read the file from the designated folder. Then, one by one, it will read the records or line items from Excel and open an SAP portal. After logging through the SAP Portal, it inputs the required employee information. After that, it will go to Microsoft Azure Active Directory to QA the user, email, and ID. It will then go to PeopleSoft to create an HR record for the salary information, leave information, and the level at which the associate is joining. At the end of this process, it will update the status to, "The associate has been registered successfully." It will then send the updated final report to HR, saying, "The processing has been completed." The bot triggers information with their newly created email ID. They can then access or receive the onboarding information. This is how it works.
Depending on the client's requirements, we use UiPath AI Center and UiPath Apps for custom requirements. Most of the time, we don't need them. There are some times that we do based on the client's requirements.
I am using UiPath Studio, UiPath Orchestrator, and UiPath Robot.
Initially, I used the on-premises deployment model. For the last two years, we have also been using the cloud deployment option, UiPath Cloud, along with the on-premises. This is based on a client's requirements.
We have faced challenges when installing market-related data. We need to dig deep when we are installing it with Orchestrator and/or VMware. All the documentation is available, but it needs to be prepared in advance. Whereas, we work in real-time.
UiPath makes it easy to build automations. It is very user-friendly and they provide all of the courses in the UiPath Academy. We can learn starting with the basics, and it is really simple. One person needs between two weeks and one month to learn it.
This solution provides us with the ability to do end-to-end automation, starting with the discovery phase and process mining. After that, we move to the building page where we have Studio X, and then we can deploy the automation on the cloud.
UiPath has helped us to scale RPA benefits by automating the backup of all of the projects running in the organization. This bot runs every night and reduces our workload for one employee by eight hours, or one day each week.
UiPath handles all of the infrastructure updates and maintenance, which is really good.
The cloud offering has helped us to see time to value quicker. It has helped us in many ways, including with the automation of repeated tasks. One example is that I created a bot for myself that is responsible for filtering all of the spam emails from my inbox on a daily basis, and then removing them. The first step is the identification and the second step is removing them. This saves me time.
The automation cloud has helped us to reduce the total cost of ownership because we can manage everything through Orchestrator.
UiPath has definitely reduced the percentage of human errors that we have in our processes. In our system, all of the bots follow our best practices so there is a very small chance of error. The reduction in error rate depends on the process. For example, the OCR is not very accurate so the errors are higher but if the process involves an API or SQL queries then it is very good.
This product has helped to reduce the cost of our automation operations. There is more of an upfront cost but it is one-time, and then we start saving.
With respect to building automations, UiPath is very easy to use. I have trained people to use this product and it is so easy to use that even on the first day, people are able to start working with it.
UiPath enables us to implement end-to-end automation and it starts with features like task mining, process mining, and task capture. Then, we have Orchestrator, where there is a control room that gives you insights, and you can create dashboards using Kibana.
We have done work for a giant logistic firm, and the end-to-end coverage is very important for them. If you are spending and investing money then you should get a return, and the return, in this case, is measured by FTE savings.
Another way that UiPath has improved the way our organization functions is that we have introduced automation to clients that were not even aware of it. For example, we have a client that we have worked with for many years and we were ultimately able to introduce them to RPA. At this point, we have automated many of their processes. Essentially, when you automate a process or task for a company that is not even aware of RPA, they will start using it, which is very helpful for us.
UiPath has definitely helped to minimize the on-premises footprint for our clients. We work with a non-profit organization that we have done some automation for. Since they are non-profit, keeping infrastructure costs down is important. They run events each quarter and in the administration of those events, they have highlighted what they want to have automated and some of the processes include using AI and ML. As a result, the company is growing and creating new products.
I have seen companies that were hesitant about starting with automation because they were worried about the cost. However, in the long run, it saves a great deal in terms of FTEs, effort, and costs. Ultimately, it has helped to reduce the cost of digital transformation for our clients.
This product definitely helps to reduce human error. For example, if there is any human input that is required by the process then UiPath will help to catch these kinds of errors.
UiPath has also helped us to free up employee time. One use case that helped to free employee time was for our client that had to reset lost passwords manually. It was quite common that one of their users lost a password and needed to have it reset, so we created automation for it. The bot interacts with the Unix server to reset the password and the process is now free of manual effort.
Especially for a larger organization, time is money and if you're saving time, it's definitely saving you money. Overall, UiPath has reduced costs for our clients.
I am a UiPath developer and my role in the company is as an automation developer specialist. I'm working mainly in UiPath Studio, not Studio X, and I also work with Orchestrator. We are using attended automation.
We are automating the processes in our company, for example, in the finance department. One of the ones that are now automated is invoice coding determination, which no longer involves humans. At this time, 80% of our processes are completed by robots. The remaining 20% is approved by humans but I think that this will improve later.
I'm using the product primarily for building automation projects for shared services users. It's for internal customers. It's a shared services center for finance, HR, IT, and all processes like that.
UiPath enables you to implement end-to-end automation starting with process analysis, then robot building, and finally the monitoring of automation.
I use UiPath mainly for building a robot. I always use unattended bots. However, I also use it for task capture. I use the Task Capture feature a lot. It's pretty much a game-changer since Task Capture has become available, as creating documentation takes a lot less time than before. As for UiPath, I'm using it for building a solution and then testing using not only UiPath but also Orchestrator. In the end, we also use some document templates from UiPath. It's pretty much present all the way through the life of a project.
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.
The Studio is where the development takes place and the interface is very user-friendly. You have the ability to drag and drop components, and this is part of why I think that Studio is the best feature in UiPath. The next best feature is Orchestrator.
The Orchestrator is quite good because it is a one-stop shop where you can run robots after creating them using Studio. You can create queues, monitor the bots, and if there are any issues then you can debug them at the Orchestrator level.
UiPath has a low-code feature called Studio X, which is specifically for business users. They can just drag and drop activities like reading emails, retrieving email attachments, reading data from Excel, and posting data from different sources into different platforms. It is a very good platform for business users who don't know much about coding. It is customizable in the sense that business users can have the system follow a set of simple steps, although it won't do complex things.
UiPath Insights is a feature that has everything from a tracking perspective, which tells you how the bots are working at the production level. It provides statistics about the live environment including how many processes are being run, how much time the bots are being used, and the productivity in general. There is more analytics available from data services, tests, and the AI center. All of these features really help when it comes to analyzing the data, not only from a development perspective, like tracking data on how much a robot is at a log level, but also from the end-user level in a production environment. Reporting on productivity in a single day will show how much time the bot was run, for example, 80% in terms of time or 90% utilization, and other such details.
The UiPath App feature is something that we can use to create simple apps, and these can act as integrators. Suppose there is a process that uses 10 different screens, we can create an app that will be integrated with all of them. As a developer, all 10 screens are used in my workflow, and instead of going to each of them, I can create an app that uses all of the fields that are relevant to me on each of the screens.
The speed at which we were able to create automations for our contact center was very good. One of the reasons that we choose UiPath over other tools, such as Automation Anywhere and Blue Prism, is the ease of development. When it came to setting up the contact center, it was only the connection between different platforms that took time. The bot creation and the workflow creation were quite easy. It took approximately one and a half months to create the whole automation for the contact center, which is quite good.
UiPath makes it very easy to develop automations. The interface is user-friendly and makes it easy to perform operations or use services, whether it is a database or another product. We can perform tasks on Microsoft Azure, for example. Many operations can be completed using inbuilt packages.
For whatever activity we want to perform, it only involves using the drag-and-drop capability, so it is easy to do. Anybody can do it. No programming-specific knowledge, like .NET, is required.
It is easy to develop custom components, which makes life easier.
UiPath allows us to implement end-to-end automation starting with the process analysis and ending with the monitoring. This is important to us because for any new process that we identify, using the task capture methods helps us to gather the documents that are required to automate it. After we develop the automation in Studio, we can easily monitor it using Orchestrator. It is helpful to have a complete solution from start to end, with all of the features that it has.
Using automation means that we increase our process output with minimal effort, which is something that every company wants to do because there is a saving in terms of manpower. It is definitely helpful in our organization.
The amount of time or cost savings depends on the process. For example, some processes that take four or five people to complete can be done using a single bot. Also, people can only work six or seven hours a day, whereas, with automation, the bot can run 24 hours a day. Not only is the process done more quickly but at less cost.
Attended automation has helped to scale RPA benefits because we have some scenarios where human collaboration is required. These are business-critical processes, so any level of automation is important for us.
In addition to savings in time and cost, UiPath further saves us money because of the reduction in human error. When a human is performing a task, mistakes happen. When the bots are used, there are no errors and when the number of mistakes is reduced, the business has more income.
UiPath has helped to speed up digital transformation, although hosting it requires IT support. For example, if UiPath needs to be updated or our infrastructure needs to be expanded, then it requires the help of IT support.
We have a cross-platform infrastructure, where two servers are sitting. We have Orchestrator, which we connect to our virtual desktop infrastructure (VDI). In the VDI, we have a UiPath stationed.
From India, I work for an Australian client. Previously, I worked for a European client. In order to work with the client network, we have a dedicated Wipro laptop. In that Wipro laptop, we log in and connect via the VDI. In that VDI, we have UiPath Studio. Using UiPath Studio, we are doing development for the client and automating functional business processes.
We are extracting data from Salesforce using a particular report that is sent by the business SMEs. We pick exact fields end-to-end, then we put these values into Salesforce. Next, we extract the value and data from Salesforce, putting that into an Excel application. After putting the return to Excel application, we generate a service request for the business and send transaction reports of the bot's performance and accuracy at the end of the day. The business was taking around four to five hours. Our robot takes around eight to nine minutes in order to automate this end-to-end automation.
For another use case, there is an application that submits invoices for an insurance client in Australia. Right now, the business is doing this. Whereas, the bot operations reads a file on the hard drive, picks up that file, and puts it into SharePoint where the bot performs some operations. After doing those operations, the bot will report the status, whether it is valid, invalid, or an exception. When we get the file, we develop the application that submits the invoice. After that, we capture the data from the Excel application and submit a request. This is an end-to-end process. This bot only runs after business hours, five days a week, so it doesn't impact the application. With this process, we send daily transaction reports, the success ratio to the client, and present the entire picture to our peers and business holders.
We have set up our own cloud, which is internal. UiPath has a different cloud. Per our governance, we are not allowed to use another cloud. We are using our hosted internal cloud, which is hosted on our internal servers in Australia.
We may take student records and place those records into a particular template which we then upload to an application, whether a web application or a desktop application. If a human was involved in doing this, it would take days to filter the Excel and create a template based on a particular record. But by setting up some business rules through UiPath coding, it automatically applies those rules to create the template and upload it to the application. We can then send a notification to the user by email, because we have connectivity with Gmail, Outlook, and SMTP.
A human being can work eight hours or nine hours per day on average, but a robot can run 24/7. With automation, we can save time and money by continuously running things on the same machine without any errors. The accuracy can be 90 or even 100 percent, depending on the logic of the code. It also helps the communication between clients, users, and our organization, improving the partnership. It definitely reduces human error because it's automated and well-tested. It increases work volume because it's very fast. In terms of the amount of time it saves, for repetitive tasks it can save 90 percent of an employee's time. Employee satisfaction has definitely increased.
UiPath is also helping us to increase the number of tasks we can do. For example, if a human being is reading an Excel, doing some operations and validations within it, it will take hours or days to complete. But using a UiPath robot, we can simply create the set of necessary instructions in our code so that it will run within minutes or even seconds sometimes. It is very fast.
We use every component of UiPath, from Studio to Orchestrator. It's very helpful and it is very fast. Orchestrator is very beneficial because we only need to create a particular robot once and then we can simply connect it to machines. It definitely saves time because we only need to maintain the versions of a package and the code, and that can be done locally or via Studio. Because there is a chance code could be deleted on a local machine, the fact that Orchestrator is in the cloud means we can definitely retrieve it from there.
Orchestrator also helps save time because there are scenarios where we have multiple stages of input, where something depends on a value. As developers, we don't need to provide the particular input and again publish the same package. We just go to the cloud, check the process, check the assets, change the value, and it will automatically update. It's a robust solution. Like its name, Orchestrator really does help us orchestrate things.
Also, non-technical people, the users, can see what is happening in their jobs. They can check the status of particular scheduled jobs and see whether they are running or busy, and how many bots there are.
Attended robots are also helpful because sometimes we have a scenario where a user cannot share credentials because everything must be secure. In that type of situation, we need attended automation that can be run on a particular machine in front of the user. While it's running, they can do other work on the same machine. That kind of implementation enables us to automate while keeping things more secure. This is important to us because security is a main concern. It allows users to keep their information safe, rather than making it available on other machines. It's their intellectual property and we respect that.
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.
Aditya Vaddiraju says in an UiPath review
RPA Developer at a tech services company with 10,001+ employees
We don't use the UiPath Apps feature yet. I did a PoC on it and it looks like a wonderful product. But when we are using Action Center with Apps, the Action Center stage is built in Orchestrator, but the same field is not built in the Apps. We have to work around that particular process, to make Action Center and Apps work together. Action Center waits for a particular input when a particular task is triggered. This stage is not built in Apps. UiPath Apps should be stepped up in terms of its functionality and integration with other UiPath products.
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.
Between version 19 and version 20, the Orchestrator tool interface has changed a lot. It totally changed. The menu changed, the place of the button changed. It took me a week to understand and to make myself used to this new interface. In the end, I found it's a good change and it's helping so much in understanding what the robots are doing in terms of checking logs, extracting some data there to make some analysis, and giving reports to the director.
The scaling could be better. There are so many parameters and options to check and so much to do before the solution is ready to use. Not everyone knows what to do at the outset and it's all a little bit complicated.
One of the most valuable features is that UiPath is easy to deploy, especially for medium-sized companies. It is also easy to scale.
Also, the fact that you can scale automations without having to pay attention to the infrastructure for doing so is quite critical. The infrastructure could require a lot of maintenance resources and affect costs, so that feature is quite important.
UiPath enables you to implement end-to-end automation, with its full range of tools, starting from Automation Hub, which is the initial point for gathering your processes from business lines. It's driven from employees or a center of excellence, and goes on to include implementation, and the reporting in Orchestrator is quite powerful as well. The end-to-end coverage is important, as clients always like one tool that covers their needs and plans.
Maciej Gułaj says in an UiPath review
RPA Developer at a engineering company with 10,001+ employees
I made the right decision to go with a solution that can scale automation without having to pay attention to the infrastructure and to develop my skills in terms of RPA.
I had to do tests with Blue Prism and UiPath. Currently, I use UiPath, as I find it's much easier to use than other RPA tools. For example, I really like Orchestrator, from a user perspective. The control of both is really easy as it's centralized in NonProduction Orchestrator, and it's really easy to operate it. There's general ease of development. In Blue Prism, for example, if you want to develop something, first you need to prepare the object layer, and after that, you can go to the business layer and connect it in one solution. In UiPath, we create just a component and connect components together which is more logical.
If we look at the development part, UiPath Studio has been great due to its ease of use and its UI. The availability of the UI store helps us understand the complete pre-hierarchy of the UI elements that's available on the browser or website. It's easy to use and it can be manipulated in the way we want it to. It allows us to do more work on the browsers.
The integration aspect is very useful. Right now, I'm working on SharePoint and that integrates nicely with UiPath. The integration model is really, really great, and 99.9% of the time it works. While technology can fail occasionally, UiPath has a great track record.
The ease of building automation using UiPath is quite good. The kind of projects or processes we have been able to automate has been helpful. We need to determine if it's a complex process, which is dictated by the number of steps. We look at the number of steps and work to determine if we can improvise and reduce the number of steps, and, if so, how. We look at if the process ever requires human intervention and where. The type of human intervention might dictate the complexity of the process, as well, for example, the number of applications we are working on. We might have to write some code on the backend or maybe we are working with an API. Everything needs to be assessed before going into an automation process.
UiPath has reduced human errors. Previously, everything was manually tracked with changes noted on the tracking sheet and we would do a copy/paste from one place to another. There was always a chance of human error. However, when this process is automated, there was zero chance for mistakes. While there may be exceptions, it would be only in rare instances the automation itself would make an error.
The product definitely reduces cost. If a company deploys automation within their organization, they need to understand that automation needs some time. One process will not necessarily reduce the cost. They need to see there will be results in the long run. It just takes time and they have to understand automation. They have to implement automation within the organization. Often, organizations will start the automation process, and then they leave it as they believe the cost is going up. They perceive this due to the fact that they need a separate system for development, a separate system for testing, and a separate system for operation, plus they need three servers for the Orchestrator. However, in the long run, automation actually lowers costs. It's just a hard up-front number to look at.
All the features, all the packages, everything, have been great. All of the artificial intelligence which we are getting is super-useful, as are all the needed updates.
All the features are valuable as, much like any application, it cannot work without just one feature. For example, we have PDF automation, we have Excel automation, Citrix, SAP, and we have SharePoint automation - which makes it so that we can automate anything. All the features combined allow us to work on multiple projects or one specific project.
The ease of building automation using this solution is good. I really enjoy the flexibility. It's also very easy. We do need a few coding skills with languages like C# or Power Automate. However, it's got a good UI, with drag and drop functionality. That makes it easy compared to other tools, like Prism automation. UiPath is much better and it's highly recommended.
Scaling automation without worrying about the infrastructure was easy. I simply did some googling and looked to see which automation tools were out there and which was the leader. There were multiple training portals - including UiPath Academy, where I was able to pull all of these tutorials and insights. There's also a free forum where queries are answered. It made everything quite easy.
The solution enables us to implement end-to-end automation starting with process analysis, and robot building. This end-to-end coverage is important to me as we follow an agile methodology. We have an RPA development life cycle. This product gives us all the tools and everything we need. The requirement gathering and document preparation come as standard models. We have UiPath Studio for testing and UiPath test features for maintenance. We have the Orchestrator where we can maintain everything as well. We can see where things are working or not. In fact, we have integration with PagerDuty that gives alerts if something is failing or not working. It's really important that UiPath has integrated across all the life cycles, and that all the phases are working properly.
UiPath has helped to minimize our on-premises footprint, which has been very important to me. It's very important due to the fact that we can build a robust and scalable solution for an enterprise and have security in UiPath. It's very important that customer satisfaction is there, no matter what we are developing. It's very important to our organization.
It's a very fast solution. It can provide a result or automation to a business process within seconds. If we have an API, we can integrate EPS as well instead of using the UI. Basically, we can get any solution we need within seconds. It's very fast.
I have noticed that the solution reduces the cost of digital transformation as we are saving on manual hours. It's reducing them. We don't have to hire more people to do these manual jobs, which has helped us reduce the cost.
We did require application upgrades and IT application support. We wanted to update get all the latest features that UiPath often releases. I've seen every month or every year we get all of these new packages. It's better to include the latest version to get all the latest features.
With UiPath, we have reduced human error. Humans are prone to making errors that they can make at any time. The bot does not. It's continuously given proper feedback. The lack of human errors has affected business a lot. The bot allows for complete confidence that perfect work is being done. It has also freed up employee time. We've saved thousands of hours. We have ten processes that are running in production. Up to this point, with those running, we have saved up to 1,918 hours from the automation. On top of that, employees can now focus on higher-value work. It has improved work satisfaction. There is more self-motivation that boosts the work, which we are doing.
The solution has reduced costs overall via automation. However, I cannot speak to exact cost savings. As a whole, it's saved our organization money.
UiPath enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring all of our automation. They have created a platform to handle everything from process analysis to deployment. If you just had UiPath Studio, you would have to procure something for your attended or unattended robots. You would also need a tool to capture the process or task itself. Similarly, you would need a tool to collect the ideas from subject matter experts. If you don't have a platform that covers end-to-end automation, it becomes very challenging, and you'll have to find ways to procure those applications. With UiPath, you don't have that headache.
It has reduced human error and saved time. These two are probably the best things that we achieved from automation. We recently did a deployment for a customer who had purchase orders and other stagnant stuff from 2011 onwards. These purchase orders were not closed even though they have been receipted and invoiced completely. We did robotic process automation to takes care of these purchase orders. It is a recurring job that takes care of all POs that were created in the last one year and closes them automatically. It used to take 5 to 10 minutes for the customer to close one purchase order and recheck everything. There were probably 22,000 to 23,000 purchase orders every year. The business benefit that the customer got was close to 1,200 hours in a year, which is a massive saving.
It has freed up employees' time. It has definitely reduced the time for our clients. The time saved varies based on the project. It has saved the time of associates in completing their tasks, and they can focus on a lot of other things. In one of the use cases, an employee was spending 10 hours every month to complete a process, which is 120 hours in a year, whereas the robot takes just one hour every month. So, the robot takes 12 hours as compared to 120 hours taken by a human, which is one-tenth of their effort. It has reduced around 90% of their time for this project. For the purchase order closure project, the robot has saved close to 1,200 hours in a year. That's a huge saving.
There are other use cases where savings were not huge in terms of the efforts or hours, but the robot was very much compliant with a company's processes. It eliminated any sort of human errors that could have occurred. For instance, balance sheet reconciliations always had some sort of issues and were prone to errors. The robot completely eliminated all those issues.
We use attended and unattended automation. We have a couple of robots on the finance team's laptops, and they trigger the process as and when required, such as for month-end clearing, which is a process where the end-users have to do some kind of clearing task in the SAP system. They can trigger it as and when required. This attended automation has helped in scaling RPA benefits. The overall benefit was in terms of the efficiency with which the robot gave them the mismatches. At the end of the day, it is giving the end-user satisfaction. They don't have to repeatedly do the same steps for every company code and intercompany code. It has definitely saved a lot of time for the end-user and provided satisfaction with the process.
With cloud offerings, UiPath handles infrastructure maintenance and updates, which saves our time as well as our clients' time. The clients do not want to worry about the infrastructure and other such aspects. We are generally the ones who provide services to the clients and deal with these things. When they use the automation cloud, it is definitely time-saving because we don't have to install patches and other things. If there is a new service that they introduced, such as data service, we don't have to install anything new on the automation cloud. It is all taken care of pre-default. We just have to enable it or disable it as per our need. That definitely saves some time for us.
Their automation cloud offering helps in decreasing time-to-value. It definitely reduces time as compared to on-premise because all that you need to do is procure an automation cloud and the licenses for the UiPath team and enable them. With the on-premises setup, there is an overhead of installation of orchestrator on the virtual machine. In this aspect, an automation cloud is better than installing everything on-premise for the client and setting up the orchestrator and things like that. The automation cloud doesn't have any other thing that reduces your time. Other solutions, such as Blue Prism, provide the same benefit when you use a cloud-based orchestrator.
Earlier, it was a bit complex as we had to configure our robot with the orchestrator or the studio that was providing details. Now, when we are installing, everything is taken synchronously. We don't need to enter the required areas. It is automatically catching that from that environment.
The time it takes to deploy depends on the system resources or the system specifications. Usually, it will take around 23 to 40 minutes for the installation, however, now that they have improved their installation time as well, it may only take 20 to 30 minutes.
For us, the deployment plan is basically to focus on the data perspective. We don't want to lose any of the aspects of the data, which is already running, so we do take a backup first. The orchestrator has a different environment structure, which has already been configured like a development rather than a UAT.
These are the phases that we are using on a regular basis. Once it is certified for the first stage, only then does it move to the next phase.
We require 22 people to maintain the product. They are largely comprised of the DevOps team.
Oracle itself has been very helpful when using this solution, thanks to the redundant task they've currently defined. All those are being automated. We mostly use the UiPath Assistant, Video, and Orchestrator. These are the only three products that we use day-in and day-out for our clients.
The ease of building automation using UiPath is great. It technically provides good features in order to develop, automating different kinds of applications using UiPath.
UiPath enables you to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automation. It's usually very important. In some regulation cases, redundant cases, it’s been very useful. Instead of avoiding human intervention digitally, we are utilizing the UiPath to build up automation and run those in unattended mode.
If we could use the UiPath Apps feature, it would increase the number of automation and reduce the time it takes to create them. That said, at this time, I do not use this aspect of the solution.
UiPath has reduced human error in some cases. For example, a client has monthly payroll activities, which have to be done for multiple entities and in multiple in order to ensure the reports to be pretty good. It's a huge asset, having these multiple entities. It takes a lot of time for a human to execute the task. Here, automation plays a key role and it creates everything automatically through unattended mode. Of course, when a human is involved, there are chances for errors, such as missing the entities and updating the parameters. All of these things are instead being taken care of by automation. The likelihood of error is removed when the human intervention is.
The product has freed up employee time. It’s likely freed up more than a day, an average of 12 hours at least. That’s 12 hours per day. It allows our employees to focus on more high-value work.
The orchestrator is one of the good features they have.
Internally, internal queue management is another feature that is really helpful when it comes to managing the work and checking the workload.
The latest thing that they added is reports that show the handling times and all those things.
The ease of use of building automation using UiPath is good and I would rate it and an eight out of ten with the version I am using. If we move to the latest version, there may be a couple of new features, such as modern variable management, that would bump it to nine out of ten.
UiPath enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring automation. With the new versions, it does, at least. We are not using those features in my current organization, as we have some other tools in place.
End-to-end coverage is important to us. We use the older version. We started using it three years ago, which is why we build a lot of items ourselves. If the features were released two years ago, we'd likely use UiPath for everything.
It is important that we can scale automation without having to pay attention to the infrastructure of the automation. We're very interested in the cloud. It offers many benefits. Even though we are on-prem now, in terms of managing the infrastructure, it will likely be really helpful to move to the cloud, so that we don't have to bother about all this infrastructure stuff in the future.
It reduced the cost of digital transformation and it is allowing us to actually move to digital items, as, most of the time, when we were trying to present things and things were not digital, it helped us to advance very much into a digital space easily.
It does not require any expensive or complex application upgrades or IT support. For some applications, it requires some modifications. Even if it's 10% or 20% digitized, we are trying to use UiPath to do the stuff for us instead of doing the application, upgrading, all those things. In most cases, it's not very costly for us.
UiPath has reduced human error. It does all the time. In claims, there used to be a lot of human error. Especially in payments, sometimes it would pay more or less or the wrong person, and now, it's all automated and errors have stopped.
The solution has freed up employee time. It depends on the process, however, if I had to take an average, it is probably freeing up one full-time person, which is eight hours. On a monthly basis, around 150 hours are saved for a medium process.
This additional time has enabled employees to focus on more important work. Employees are happier, and, depending on the process and what they were doing, what kind of involvement it requires, the solution is motivating employees.
The product is reducing the cost for other operations, as it's an automation tool. While we are paying for automation, it is reducing the overall operational cost. Not specifically automation operational costs, but other operational costs. We are seeing an average savings of around 30%.
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.
For our organization, the Orchestrator has the most useful setup. All automation is more or less the same. With UiPath, the difference is the Orchestrator. The amount of integration it has is actually what makes it different from all other vendors.
I would rate the ease of building automation using UiPath at a nine out of ten. For automation in UiPath, you use a package. For example, if you want to do MS Office automation, you have an MS Office package. If you want to do Outlook automation, you have a certain set of packages that support that. If you have the package for that purpose, it's very easy to manage.
For ServiceNow, they did not have a package until last year. There was a UiPath team-supported package that was an unofficial package developed by a UiPath employee. Last year, UiPath came out with its own package, and that helped. Now we have standard automation for ServiceNow. That's actually made things more streamlined.
In terms of implementing end-to-end automation, the process analysis is currently outside of UiPath, but everything except that can be done by UiPath. For us, creating end-to-end automation using UiPath is not that very critical. Process analysis is a bit of a situation-specific thing, and at times, it's usually better to keep it outside of the tool. It always helps within the tool, however, it depends on the convenience and comfort that the client has. I wouldn't want to expose my ERP data directly for automation.
Typically, it takes two to three years to see the breakeven. The difference between on-premise and on-cloud is that the lead time is a little less. That's about it. Therefore, the amount of trouble and setup and that sort of thing is the only item to consider.
The Automation Cloud offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure, maintenance, and updates, however, only to some extent. It's not a lot. In the long run, it makes it easier to get breakeven from the initial implementation. The maintenance happens a little less as well. When you're updating the Orchestrator, that is where your major maintenance jump comes in. If you're not upgrading your Orchestrator version, it's more or less the same. From an ownership perspective, if you're not upgrading Orchestrator, only your VM license and hosting cost will be different. This depends on the client.
If you already have an Orchestrator in place, having an automation cloud doesn't really increase or decrease the ability to scale. That would only be only in the case where you want a complete separation environment. In that case, you'll have to use a multi-tenant kind of setup. If you do that kind of a setup, it's the same if you do it on-premise or on-cloud. The time to ramp up should be the same.
We use a mix of attended and unattended automation. Attended automation is primarily helpful for a few things like where the application's less stable, where things like Citrix are involved, which already have their own set of infrastructure issues.
UiPath has reduced human errors in the organization. The lead time is reduced, as well as the lead time to activity and the lead time to develop. Specifically, if you do development in UiPath versus any other OEM, you see a very significant difference in implementation lead time from a development perspective. They're much simpler to develop and manage in UiPath. If you go to other OEMs, it's very complex at times. If it takes 10 steps in another OEM, UiPath takes it in one to three, max.
The solution has freed up employee time by as much as 30 minutes per day. It's allowed employees to focus on higher-value work. The primary benefit of automation is doing low-complexity repetitive work outside of working hours. That's the biggest advantage that I've seen. Even if you're sleeping, there is already work being done in the background, so that the next morning, when the employee comes, he has more relevant work in front of him. He doesn't have to do any paper-pushing jobs. Automation can do that instead. That's the biggest advantage.
reviewer1642377 says in an UiPath review
Senior RPA Developer at a marketing services firm with 10,001+ employees
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.
UiPath has a full suite of capabilities. It has, for example, an end-to-end automation suite. From a development point of view, it is pretty helpful to have access to all of the activities on offer that anyone can understand.
The Studio as well as the process mining are great. Document understanding is another useful feature. It has eliminated the business analyst side where you have to go through each department and find out which processes are there, and take a different tool to get those all processes in one place and create a process workflow. All of this can be done with process mining.
With document understanding, we have the capabilities of having UiPath understand and create documents, which previously was quite a lengthy endeavor. You just have to install it and follow the steps. It will automatically take a screenshot and create a document for you and then create a brief description of it.
It’s easy to build automation using UiPath Studio. From a developer's point of view, it is easy due to the fact that you don't need much of a coding language or coding background. You just should have a clear logic behind it. If you're clear with the logic, a layman can handle the task. They do have Studio X features, which is for the layman who doesn't have any background, who doesn't have any coding or developer's background. They can automate their own work. Even an SME who doesn't know anything about automation could automate small tasks.
It’s great that we can scale automation without having to pay attention to infrastructure. That is very important actually. For example, scaling automation plus giving attention to the infrastructure can be a little hectic and time-consuming. If there is any way where we could reduce this work or optimize it, it would be great from the implementation point of view.
UiPath enables us to implement end-to-end automation. Right from the start, you have document understanding and process mining as well as the Orchestrator, which helps you with getting an overall view of the bots in our organization.
End-to-end coverage is the most important thing, due to the fact that, if it is end-to-end, we don't need to go to the market and look for any other application. If you can get end-to-end, you don't need to go for other products which simplifies everything. It's easy for us to maintain and work with it instead of having to integrate and manage multiple systems, multiple products, and multiple applications.
UiPath has helped minimize our on-premise footprint. It has helped us with quality control savings. We have saved many efforts previously requiring full-time employees. It’s one of the most important factors when we work for clients. If a client is hiring us to automate many processes, there are different intentions of doing it. If we are able to help them reduce cost, reduce and do some quality control, it is important for them. For example, previously, if work required ten employees, we have been able to reduce that down to six or sometimes four personnel maybe.
The UiPath Studio has reduced human error. It has helped us with quality control very often. In the past, mistakes have cost us. It has saved costs as well as saving us money related to fines or penalties.
The solution has freed up employee time. Instead of doing the same mundane work every day, we have just automated that part and now the employees have more free time to do more meaningful work. In terms of hours, from a department's point of view, we have saved around half, that is four hours per day, maybe about 80 hours per month. The additional time enabled employees to focus on more important work.
We have found that the product has reduced the costs of our client’s automation operations. With my previous client, we calculated an average of 40% in reduction of personnel and 40% in cost savings. UiPath has saved us money across the organization. The average saving is likely around 40% to 45%.
It's low code/no code which makes it very easy to work with.
Building automation using UiPath is easy. If I see a video or some instructions, I can do it. Things are doable. You learn. If there are use cases or there is information online, you can replicate the process.
Adding activities is easy. All of these partners are integrated into UiPath now - including AWS and G-suite. You have activities already built right into UiPath and they are working to make everything as low-cost as possible.
Then you have OCRs which offer the document understanding. I can do a PDF extraction using just OCR in a normal way.
I love the document understanding. You can see whether a document is valid or not. You can accept or reject. I came up with a .NET background. I used to write so many lines of code for doing a certain thing. Here, you have a for a loop. You don’t need so much code.
I remember when I used to work for a UK client, a gas utility, and at that time we used a read-through data driver, and got the Excel data, and again validated everything. However, for that, we used to write around two, three pages of code. Now, using UiPath, you just do a real Excel activity and you get the entire sheet. Automation has made our lives easier.
I can scale automation without having to pay attention to infrastructure. Now, since the cloud has come into the picture, everyone is going to the cloud and everything is easier but with the new cloud partners like Google, AWS, Azure, and Oracle. A company may not have its own on-premise orchestrator.
Earlier, you needed three servers for production, testing, and development. Since UiPath has both cloud orchestrated and on-premise, it's easier for organizations to use less physical space. For smaller organizations, they can go to the cloud. For larger they can have their on-premise orchestrator. It’s flexible.
UiPath enables me to implement end-to-end automation starting with process analysis and then robot building and finally monitoring of automation. There are many process mining tasks, capture tasks, mining, et cetera. More things have to be automated - such as deploying, managing, and enhancing for continual improvement. It has all the components.
For a beginner, end-to-end coverage may not be essential. When we talk about automation, we should know what can be automated so that we ease our lives and that doesn't mean we have to remove the resources. You don’t have to involve the employees. You just need to simplify the task so that there is continual improvement. Users should consider not only, how to automate but what needs to be automated. If it is automated, how it can be improved gradually and what are the returns? Sometimes that doesn’t necessarily mean you need end-to-end. You just need simplicity.
I do use the attended automation. For some processes, I use the attended automation for testing purposes. I use the attended if I'm using UiPath assistant, otherwise, it's normally background processes that are unattended.
Attended automation will be for document understanding when I'm training a robot, for example, for what is the format or validating the time I'm using attended one. If I'm asking a user for particular search criteria, or for currency exchange it's mixed but mostly unattended.
Both attended and unattended work together - the human as well as the robot. However, it depends on the scenario. Unattended means you are not dependent on any human resources.
The orchestrated cloud, which is a SaaS, it's quite helpful. If I just want to install UiPath studio in my system and I'm least bothered about what environment it should be, what infrastructure should be, where I'm going to deploy, it is quite useful and quite easy when there is a SaaS option available.
I’ve used the AI functionality for sentiment analysis such as getting reviews from the websites about a particular product or service.
UiPath offers great object detection where you have a magistrate and you can detect whether you want to detect the people. If you want to extract how many people are there in that image, for example, during a social distancing sort of event, that can be used for object detection. I've used object detection for images in terms of extracting a number of people.
I’ve trained the system to read different types of invoice formats. I've used the email or document understanding that can read separate invoices, receipts, utilities, et cetera. I’ve used the solution to create processes for invoice reconciliation.
The AI functionality is quite easy to use. For tollgates, for example, when they charge for tolls, the solution can be utilized for seeing the number plate, and through the image, get the data, extract the number of data from the numbers plate, use the driver information from the number plate of the car, et cetera. It becomes a very easy AI model. Without any type of knowledge in AI, you can use those out-of-the-box functionalities.
The more training you do with machine learning, the better results you get in the end.
I use the automation cloud feature.
We are not bothered about any patches or any work that has to be done to maintain the infrastructure; the vendor does it.
The automation cloud offering has helped decrease time to value, however, since I have not deployed real-time projects, I cannot give exact numbers on the decrease. That said, from my experience, I feel that it is true.
It’s my understanding that the automation cloud offering helps to decrease UiPath's overall cost of ownership, however, at this time, I just use the free version.
The solution enables you to be better and better with cloud features that are quite accessible.
In terms of UiPath Apps, I have used them, however, just for my own purposes, for my own training purposes, as I was learning. It is easy to use and pretty much drag and drop. For the basic things, the user can do a lot with minimal training. You can do everything with low code and less coding knowledge as well. A person may not be technically sound, however, even with minimum knowledge, they can create apps using UiPath apps. That's the interesting part of UiPath apps.
UiPath reduces the cost of digital transformation. It does not require expensive or complex application upgrades or IT support.
UiPath has reduced human error. For example, let's say I'm filling a form using a document. Typos, errors, spelling mismatches, et cetera, are reduced when it is handled by automation. When we automate this process, the robot minimizes the error since a human is not involved in this case of data entry. It will extract whatever data there is in that document and it will fill in the form. Similarly, for calculating Excel data, we can avoid calculation errors.
reviewer1642950 says in an UiPath review
Application Development Specialist at a tech services company with 10,001+ employees
I am a software developer and I am a full-time RPA developer for my company. We create automation for internal purposes as well as for our clients.
I have implemented 15 to 16 processes end-to-end that cover use cases including Excel, front-end web-based applications, backend Windows applications, and sometimes Citrix. I have also done some Adobe Flash Player automation.
The REFramework (Enhanced Robotic Enterprise Framework) is what we use for most of our use cases.
We are using Studio for development on-premises and we use Orchestrator in the cloud.
Jyothi says in an UiPath review
RPA Consultant at a computer software company with 10,001+ employees
Orchestrator is very useful for deployment and publishing, maintaining queues, and running jobs.
In UiPath, REFramework is useful for different use cases with predefined code templates. There are well-established steps. There is a step for code marginalization. Similarly, there are separate steps for initialization and processing. For closing an application process, a step is there. So, it is very well modularized for getting the transaction data. If there is one exception or anything wrong happens with an application, it will log the exception in the orchestrator and send an email. It can also close your applications and end data processing. So, everything is well organized and separated, and we can log the exceptions separately in the queues as business exceptions or application exceptions. We can have the complete report of a particular queue.
For document understanding, there are so many features. I haven't used them practically, but to read a PDF, there are patterns and semi patterns. A wait option is also there for somebody to come and correct it. It can wait until somebody comes and corrects it, and then it will do the processing. So, all of the features are very useful in UiPath.
reviewer1647894 says in an UiPath review
Senior RPA Developer at a tech vendor with 10,001+ employees
The Studio and Orchestrator are pretty valuable. They seem to have a lot of connectivity and usability. It's pretty easy for people without a coding background to use it.
It's pretty easy to build automation using UiPath. It's a little hard for some activities because there's not enough support. There's not a lot of adoption with that activity, but the ones that are commonly used have pretty good support.
Its end-to-end coverage is important to us. If we have it all on one platform, we don't have to bounce around other software. But, we ended up doing a little bit of both.
There are many great features in UiPath that our clients consider valuable. I definitely like Studio. The Studio's a very powerful product, which helps very easily to build automations. Nowadays, there's also a StudioX for citizen developers, which doesn't require coding.
Orchestrator, which helps users monitor and schedule robots, manage assets, credentials, et cetera, is also very useful.
The third feature worth mentioning, I would say, is Insights. It is reporting and dashboards. Once the robots are running, it is quite valuable to see how those robots are performing. You can see KPIs and other aspects of both robots and processes.
Worth mentioning is the Automation app, which helps to manage the automation initiative end to end, especially building the pipeline and collecting the ideas.
It is quite easy to build automations with UiPath, especially now that they are segregated depending on seniority, meaning that you have the regular Studio and Studio Pro, which are truly for developers, however, you also have StudioX, which is more for people without a previous coding background. That makes it quite easy to use. People with a business background find it quite easy to pick a tool up and use it in daily automation. They didn't have any previous experience with programming or making macros or whatever else, and still, they have no problem with UiPath.
UiPath enables users to build end-to-end automation, and this is what we are doing on a daily basis. UiPath enables mainly our clients (through us) to build end-to-end automation in their processes. When I mean end to end, I mean that we help them to automate the chain of processes and do not focus on the single practice itself.
End to end coverage within UiPath is a great advantage and offers great possibilities. It is really important to have the ability to do end to end. Though it is not applicable all the time, it still is a nice option to have and use when needed.
Very soon after starting the RPA journey, customers realize much more important benefits than time-saving itself and FTE saving or FTE reduction. There are things that happen, like quality improvement. Whenever the work is done by robots, it is running in a much more stable manner and without any human mistakes and errors. It is also sustainable, predictable work, meaning that robots do not get sick or have a bad day, or face conflicts with each other, et cetera. They just do their work. They also can’t get viruses, such as COVID which means that we don’t have to worry about losing staff.
We have a customer speech workload that was growing dramatically in relation to COVID and having processes already automated, it was very easy to sustain and even upscale the delivery. The customer experience is better as well. It is not only important to spend less time or fewer resources in delivering the service to the customer, it is also important that the customer gets a quick response. Overall, the customer experience can be much improved when using robots in the processes.
In terms of the Automation Cloud offering, UiPath handles infrastructure maintenance and updates to save time for our client's IT department. Having UiPath in a cloud enables enterprises and customers to focus more on the automation initiative itself, instead of managing all the hardware and dealing with all their hardware problems and having more or giving more time to the IT department. Instead, you can use everything out of the box from day one and focus on bringing benefits to your end customer or end employee.
The Automation Cloud offering has helped to decrease time to value from UiPath. I would say that Automation Cloud increases time to value dramatically in the sense that you can start from day one. Literally day one, you can go and start automating the processes without bothering with all the infrastructure topics. The time required to deliver the first benefits is reduced dramatically.
Automation Cloud’s offering helps to decrease the solution's total cost of ownership by taking care of things such as infrastructure maintenance and updates. It helps to reduce the cost of infrastructure maintenance, especially in the early stages of the projects, as well as on small and medium projects (for the long term). Not all customers or enterprises have strong IT departments or strong infrastructure in-house nowadays. Even large enterprises are moving more and more towards cloud services, even though they have strong IT infrastructure teams in place.
Automation Cloud is able to scale well due to the fact that we can, in a matter of minutes, or, in the worst case, hours, double the capacity. I would say that it positively and dramatically affects the scaling factor.
UiPath is a SaaS offering. It enables our customers to really quickly adapt and start using the technology almost from day one. It is very easy to start developing. It is very easy to start.
We are using UiPath Apps for our customers. However, this feature has not yet helped to reduce the workload on our IT department, or on our client's IT department by enabling end-users to create apps. Mainly, we are still involved as a service provider in the creation of the apps for the end-users. That said, where it brings added value is it reduces the limitations or the need to have an additional user interface, as you can create this app or user interface directly in UiPath to have an even better user, employee, or even customer interaction.
UiPath apps definitely increased the number of automations created. You can take more into the scope, what wasn't there before, with just attended or unattended automation, considering the fact that you can build a better user interface or any user interface from the very beginning. Before, there were only simple message boxes and prompts. Now, you can build really nice forms to interact with your end-users. It helps to accelerate initiatives.
Our teams have used UiPath’s Academy courses. Every team member of our company went through UiPath Academy. We always start with and actively involve UiPath academy.
UiPath Academy courses are a part of our standard onboarding procedure in the company, especially if we onboard junior developers. The very first thing we direct them to is UiPath Academy. Everyone starts with a basic foundation and goes through to a diploma and certification, and only then will we build on top of that more specifics about our standards, of our delivery approach, et cetera. I would say that UiPath Academy is a core and basic start for each and every employee in the company. Based on that education, we will later elaborate on different topics.
The biggest value I see behind UiPath Academy is its simplicity in terms of delivering the information. Even if you don't have any previous development experience and coding experience, all the explanations, videos, practical tasks, and reading material is formed in a way that is really easy to understand. The biggest value I see is its ability to bring people up to speed from really different levels, including very, very junior people with no previous experience in coding, programming, or the creation of robots.
UiPath's user community is excellent. Being an MVP, for me, the community has huge value in the whole end-to-end journey of RPA. Meaning that, at the very beginning, whenever you need to learn new things, you can always find a lot of useful hints in the forum and in the community. Later, when you already have delivered some solutions, you might face some problems. Luckily, very likely, you are not the first person to face those problems. There is always someone who already has had this problem and may have even raised it in a forum or on YouTube, et cetera. Even when you are already deep in delivery, sooner or later, there will be a point where you reach out for help to the community. The community, therefore, plays a crucial role for developers and automation specialists - be it business analysts, developer architects, et cetera. Having a strong community is definitely one of the most important factors that sets UiPath apart.
I'm not actively involved in other communities, and therefore wouldn't be able to compare UiPath to other similar communities. I can only say that the UiPath community is very supportive and very active in responding to any queries. The way it’s organized, it’s inspiring the next generation of forum members to help others and pay forward with insights based on the help they receive. UiPath’s community is really responsible and supportive.
In terms of reducing human error, at the very beginning, almost every company when starting the RPA and automation in Germany thinks of FTE saving as the main benefit. However, very quickly they recognize how huge the value is behind the quality improvements that happen after automation. It is quite obvious that robots are not doing human-like mistakes that may be caused by, for example, not paying attention or not getting enough sleep et cetera. Robots also cannot get bored. Very often, and whenever you have to process 1,000 or 10,000 records in more or less the same manner, it just becomes super repetitive. A mistake can appear in manual work as humans can lose focus on redundant tasks. This is not so when robots are involved.
In terms of time savings and error reduction, usually in our initiatives, we can see not higher than 5% of error rates when executed by robots. Even in those cases, I wouldn't say they are errors and more likely exceptions, which are documented and later handed over with specific explanations. A good KPI for our robots is to have less than a 5% exception rate. Related to this is that, by improving quality, we still save a lot of time as it can reduce the number of reworks which we might have afterward. For example, in one of the projects we were delivering, it reduced by eight times the amount of reworks or fixes, which the customer needed to process due to human-directed errors. Mistakes and fixes, therefore, were reduced by eight times.
Nathan Betters says in an UiPath review
Shared Services Projects Leader at a construction company with 10,001+ employees
The on-prem orchestrator was an issue for us. When we bought it, it was a mistake. Our IT team thought it would be the best option for us, however, it's way more complicated to use. Out of the box, it feels more complicated. That said, once you get to know it, it's fine, however, it was incredibly hard to set up on our enterprise systems. Whereas, with the cloud deployment, we were live and up and running in an hour. The initial setup took us about two weeks. That was a little bit of heartburn. It would be helpful if UiPath could offer some sort of support outside of a ticketing system.
We do use the UI apps feature. We are working with consultants. They actually know more of the technical details and they're supposed to be transferring data. I'm more of a functional person that understands the design and the processes, not the programming, coding, or details. I'm learning that as I’m in training for the RPA. I'm about 70% through training. I've been taking that through UiPath
Getting up to speed with UiPath has been tougher due to the fact that the programming that I learned in school is very different from the programming done today. The younger people, I'm sure, pick it up much faster.
It is helping our onboarding process and is useful in getting me up to speed.
The biggest value I get from the UiPath Academy is the ability to connect the software to the processes that we’re trying to automate and being able to understand the functions in terms of where you would go to get an even better understanding. I do find that their online help is very beneficial as it offers solid examples. In fact, sometimes that's better than the training itself.
There's so much out there and there's so much to learn as it's not one software package. UiPath Academy provides us with the ability to use all software packages and interconnect with them. The opportunities are amazing and also intimidating.
The automation cloud offering helps to decrease the total cost of ownership of UiPath by taking care of things such as infrastructure. We have gone and moved many more things to the cloud. We have a Hyperion solution in the cloud that we use for consolidation.
The most valuable aspect of the solution is the ability to follow what the robots are doing. Currently, I've been working on the automation hub. That's the next step. You can use the orchestrator to see how they're doing, for example.
We’ve realized some efficiencies in our current processes due to UiPath. That said, I'm a novice. We've just begun with these five processes. That's why I want to do the reporting and figure out the analysis as I want it to basically sell itself.
In terms of the ease of building automation within UiPath, that's something that I need to discover with the IT team. What I do like is that once you do something, you store it in a library. And then you have plug-and-play automation that you can add to others. You don't have to keep redoing the same work over and over again. That's going to be a huge benefit.
In terms of reducing human error, inherently, it has to improve accuracy. Now that we’re focused on it, we’re testing it, and if it's not a hundred percent accurate, it's not going to production. We absolutely anticipate a great reduction in human error.
Allen says in an UiPath review
RPA Controller at a financial services firm with 1,001-5,000 employees
The Orchestrator is most valuable because we get work periodically throughout the day. It'll ebb and flow. We have a really tight SLA, so we're able to have bots on demand. As soon as work shows up, the bots are picking it up.
In terms of ease of building automation, it is pretty straightforward. Once you learn the tool, it is pretty easy to use.
I have used UiPath's Academy courses. They have helped a lot in getting up to speed with the solution. I came from Blue Prism. Once you know a system, you try to map another one with the way you did things in the first one. I was able to figure it out pretty quickly by just going through the courses. The content is pretty good. They have everything you need to know to get started.
One of the features I've found valuable is UiPath Studio. We have a huge development team of about eight to ten people and they are currently working with it. We also have a citizen developer program that is leveraging StudioX.
Orchestrator is important for us as well.
These features are valuable because they allow different groups of people to complete their tasks. UiPath is a robust platform. It helps us cater to different audiences.
The initial setup was pretty straightforward. The deployment took about six weeks.
We had the infrastructure in play in December 2019 and were functional by April 2020.
We had pieces set up already, however, we had people running orchestrators on boxes hidden in closets. We decided to centralize. Now, everything is in the data center and going on the virtual machine. Everything's under that control. Therefore, in total, it took about four months to have it properly set up.
The solution has improved our organization, specifically around all the operational aspects of the bot. Once we deploy them through the orchestrator we use insights to see how the bots are performing, what errors are referring to, and just the general health insights would be the biggest lift that we've gotten out of the solution. Building the automation is a little bit easier and quicker on the platform than where we were before.
The most valuable features of UiPath are the possibilities. For example, we're excited about what's coming and we've saved some time with the bots, however, we're still learning. The idea is once we get really good at process mining it will be really good at building bots. We'll be able to uncover those opportunities and then execute on capitalizing on them.
I'm not sure of how much time we've saved, in the tens of hours per month. While it's not nothing, they've been small use cases to build up the capability. We are still figuring out how to build bots, and how to get the orchestrator all set up.
We're doing a crawl, walk, run, taking our time and doing it right. We are building up the center of excellence. We're out of crawl and we're in to walk, however, we're not running yet.
So far, the conversation around automation and cultural change has been really powerful in terms of re-thinking our processes and asking if there's a better way to do it. right now, we're beginning to understand that we don't have to be stuck where we're at.
It's changed the dynamic of how we look at our processes and how we talk about why and how we do what we do. That's been tangible.
Our teams have used UiPath Academy courses. It has been instrumental and we couldn't do it without those courses. That was one of the reasons why we selected UiPath. They're robust and it is easy to access training modules.
The biggest value that we've realized from the Academy is confidence. Just getting over that initial hurdle of understanding what we're doing has been huge.
The only features we're actually using are the orchestrator and 32 unattended bots.
The value of that is the power to be able to run our thousands and thousands of claims and membership to make sure that everything looks correct.
The solution has saved costs for our organization. I know it's over a million, however, I haven't done the exact numbers.
UiPath has reduced human error. We’re finding out that what we've built for configuration in the past, we're finding mistakes that we did a year ago. Now, the bots are proving that and we've been able to correct those past mistakes. This way, we don't have inaccurate payments or recaptures.
The product has freed up employee time - and it's not just the employee time. We do have some triggers that run. Some jobs are run that people use to manually do at night and weekends. We also don't have to hire additional people just to learn 80 different types of things in a claim and identify correctness manually. The robots will go through and then they can identify if there are specific things that are wrong. That part will go to our experts and they'll review those exact issues.
This use of bots allows for employees to do higher-value work. We also have been able to up-skill some of those people to sometimes a leadership role or a different role they would normally never get due to the fact that they were always manually looking at the claims and membership. This has definitely affected their level of satisfaction at work.
I don't know if we have an accurate estimate of how much time we are saving. I just know we do volume and we do thousands and thousands of claims a day, and therefore, it really helps.
We use UiPath’s Academy. That's how we learned the system. We actually learned it in six weeks and then started the development after that. It's very powerful and I continue to use it today.
It’s helped employees get up to speed with the product. This is especially useful when we get newer versions or we onboard other people. That's part of our syllabus. The first thing a new user has to do is go to the Academy and take some of the classes that we recommend. Then we identify, “okay, did you like it? Is this for you? Is it not for you?” et cetera. It’s a quick win where we don't have to take our time as we've got other work that we have to get completed. It acts as a filtering system for us. Both us and the employee can see if it’s a good fit very quickly. We can find out at an early stage instead of a year later.
The biggest value of the Academy is just knowing that we can do so much more volume and get in some more accurately without human error, or having people working nights and weekends. That has always been a really big push and we've been able to slowly work away from that.
Obviously, we’re not in a perfect world yet, however, getting rid of the manual aspect has been great. People just get burnt out. You can only look at things manually for so many hours. If you've been doing this for 10 years, it's got to be frustrating for those people who are always afraid they’ll get their job taken away. At the same time, for them, it’s so much easier as they don’t have to look at 80 things. They can look at five things that failed and then enjoy time with family and have a work-life balance. That’s big.
In theory, the scalability is great. In practice, if clients hear "oh, you can just build a bot and then put it out to everybody" - that's not really the case. There's going to be that deployment and configuration process where you have to work with each of the analysts or whoever you're working with to actually make it work on the computer. There might be more expectation management needed. Sometimes, for example, a computer has quirks, and we have to do this and that. That said, overall, after you get situated, it's very easy to manage from the orchestrator new packages, et cetera. My assumption is that it is good.
Getting the bots going and working is the most valuable aspect. We have about 20 or so in production. We're building out from there. We've been very focused on Studio and Orchestrator, as opposed to some of the other product lines. Because a lot of what we're dealing with pertains to advanced technical people like myself that are helping them along that journey.
It's easy for me to build automations but I am a computer scientist. I have a deep technical background. A lot of what I've been doing is trying to teach people how to build resilient bots, and how to build processes that will run. To me, one of the big things to meet your ROI is that you need to build things upfront that work. You need to verify them, test them, componentize them, and put them together. Otherwise, you're going to spend too much money on the backend with maintenance.
If you can get people to think about what do to in the event of a failure, even from the developer side of it, then they can create things that we can run, and we don't have to do so many new maintenance and operations tasks on it. That's vitally important.
I have used the UiPath Academy courses. I'm a certified developer. I didn't know UiPath at all. I went through the Academy and trained myself. When I brought in new developers, I had them do modules and I sometimes go visit them.
The Academy is pretty good. It's very helpful to have something like that. Personally, my favorite side of things that UiPath is bringing to the table, is a community edition in the cloud. I can go out and play with the latest and greatest. I have my client's laptop, but I also have my own personal laptop and I go out to the cloud and do tasks out there.
I want to bring what's new, help bring to the forefront what we might want to do in the future, and get a hands-on perspective, without having to go to the client and bug them about bringing in a license for something. That's great and I hope they continue with that.
The fact that they're not charging for training is great. It brings on more developers. The barriers to entry for people are low. And the more developers you have, the more adoption you're going to get.
We've been using UiPath since 2013. The Orchestrator is on the cloud and the robots are on-prem.
reviewer1695108 says in an UiPath review
Automation Engineering Manager at a computer software company with 51-200 employees
I love developing in Studio. For my clients, the approachability of the orchestrator is really valuable. It takes a little bit to learn the licensing structure and layout at first, however, once they get it, it's pretty smooth sailing from there. The modern folders have become a great thing for any enterprise that's looking to automate using an orchestrator as a server.
I like to automate in Studio as I'm familiar with it. I honestly just like the platform so I like automating with Studio.
I really enjoy Document Understanding. I like how it all integrates together. Some of the stuff I've seen now with just the connectors and the way you can scale implementations is really exciting. While I do like Studio, I also like how it works with the rest of the platform.
We most recently built an unintended bot that saves them about $500,000 a year worth of GS 14 labor.
UiPath saves costs for our customers’ organizations. That would just be the cost savings from RPA bots. I haven't really dug into the cost savings of the ancillary products, however. I know that one of my clients is using the test suite now after I had built a proof of concept for it, and they've fully implemented it. I'm sure there's going to be a lot of cost savings there as well.
In terms of ease of building automation, it depends on the process. For anything that's ultra-low or a low-level complexity, it's very simple. Once you start getting sprawled out into larger automation that very much becomes object-oriented programming and is basically making a workflow. That's when you really need to take hold of programmatic concepts. You need to be a strong scriptor to be able to make the best RPA bots.
Our clients have reduced human error. That's one of the things that I tend to talk about the most. The bots can get work done faster, however, the reduction of human error is probably more valuable in some cases than just speeding up work.
In terms of UiPath Academy, everybody's used it. I've used it myself. My entire team has used it. All of our engineers are some sort of Pearson VUE certified now. Most of us have the Advanced Developer. A few of our younger junior developers have the associate, the RPA associate, however, they're working on getting the Advanced Developer and they lean on the Academy pretty heavily.
The biggest value in the Academy is the videos, which are pretty helpful. Sometimes you have to slow it down, however, for the most part, the way it goes through concepts, especially for somebody that doesn't have much programming experience, the videos tend to go through some of the more elementary things like variables arguments. That can get a little bit boring for programmers since they've been through that 100 different times. That said, that’s really where the strength lies as it does target a large group of different employees. As an engineer, I might pass by some of the boring stuff, however, I will still find things later on in the training where I'm like, wow, I actually never knew that.
Pricing is working for what we have right now. We set up two Orchestrator environments and we're unable to use our single license of the analytics on both. That's a bit of a problem. We'd like to see a dev environment for us that is free of licensing. It's development versus production. Charge us for production, don't charge us for dev. That's about the only complaint I would have.
The pricing was great at the start, and so, down the line, we have been enhancing all these features. We are seeing that, as we are looking for opportunities to grow, the number of robots that we need to purchase and the software cost is going to go up.
UiPath has increased the cost. We feel that it's good, however, based on all the new features, which we are pursuing. That said, we expect that whatever robots that we have purchased or whatever the standard platform that we have from UiPath should continue with the pricing that they had earlier.
There will be an offset, however, when it comes to the existing platform like Orchestrator or robots, and we are expecting that the margin should be less.
If you're smart about it, you understand what your needs are, you can get an ROI out of it without having to go get the full-blown solution. You don't want to drop $20,000 on an orchestrator unnecessarily. You can ease into it, into adoption, without dropping a lot of money. Maybe some attendant bots, and an unattended locally on a large scale, in a small area.
If you do that and start easy, you'll get a return on investment. Eventually, when we start scaling, we'll pay for the orchestrator. You'll need that when you start getting a lot of bots, and it becomes like herding cats. It gets crazy. That's what you need an orchestrator for. While you can avoid a cost at a certain point, you're probably getting diminishing returns, and then it's going to be more costly to manage something all over the place. It's best to start small and then add on.
reviewer1695615 says in an UiPath review
Associate - Robotic Process Automation at a financial services firm with 10,001+ employees
The orchestrator is very valuable for us. The ability to have processes, especially transactional processes, be fed into and triggered from there is excellent. I really like the ease of use that allows not just typical developers to use the Studio version, but also StudioX, which allows citizen developers with little to no coding background to be able to automate their own process. Studio limits a lot of the coding you would generally do in Visual Basic and offers a pretty easy use case for people who want to get into development, who might not have that background.
I’d rate the ease of automating within UiPath at an eight or a nine out of ten. Maybe even a perfect ten. They make it very simple. It's a really good platform and for everything I've used it for so far, I can't think of how I would do this X, Y, or Z differently. I really like it.
In terms of our adoption of it, we just started using it this year. We haven't had a large volume of bots delivered and put into production, however, with what we're using, we have a lot of proof of account sets and use cases that are getting pushed along that are going to save the company time in man-hours.
It's going to save the company a lot of potential risks in terms of manual error. It's also something that can be used to automate processes that are very heavily related to compliance procedures as well, where you don't want as much manual touch for the same reason and you don't want to risk, even if it doesn't take that much time for a person. With automation, you remove the risk of somebody making an error.
We don’t have a crazy amount of metrics. We're really in the process of adopting it into the organization. I'd say within the next year, we're really going to be seeing a very large adoption of it.
We have seen direct savings in costs. Every project we deliver in time save has an associated cost reduction to it. If you're saving, for example, four hours a day on a manual process, you're saving that money. You’re also saving on anything that's related to risk. I don't have any hard numbers on the amount of time that's been saved, however, it’s been positive.
Our teams have used the UiPaths Academy courses. It’s helped make the process of getting employees up to speed with UiPath very straightforward. It's one of the better learning platforms I've seen. Between them and Alteryx, they both have very good learning platforms.
What's really important is that you don't need to wait for instructor-led training, which is infrequent. We have it sometimes, still, even when we’re having it a few times a year it gets expensive. The online training, which covers most of the same material, is a really good way for people who don't want to wait for the instructor-led training and want to immediately get their own feet wet.
The Academy is very comprehensive. It's well structured and training is easy to follow. I've used other tools that have been much harder to follow online. This one I really like.
The biggest values that we’ve seen From UiPath Academy are ease of use and ease of scalability. The solutions you make based on the infrastructure that's built around it can be made to be very scalable. There's so much that depends on other terms, such as the data that we have on our own processes, that it's going to be the yes or no, whether or not a process we build can be scalable automation for other teams. As long as we get the data and the processes lined up in the right way, we can make very scalable processes, which is good as that's more cost savings for fewer bots and that's really like what we want to see.
The database connectors I found are not fully free and expire after 30 days. That is something I would like looked at for MongoDB specifically. With regards to this, I was working on a project that needed a robot to read data from a MongoDB database. To achieve this, I used the CDATA ODBC driver because I couldn't find a direct Activity to achieve this from Studio. See the link to the CDATA ODBC driver for UiPath here https://www.cdata.com/kb/tech/...
It would also be great to have UiPath Insights included in the free Orchestrator. The Insights module is currently only available for paid licenses. It would be great for developers to have it included in the free version because then we could try it out.
It had pre-built integration with the scanning solution that we use called Kodak Alaris. They use our current scanners to scan in the documents, and then they have the software that allows you to load those documents right into UiPath Orchestrator. That gave us the ability to automate those processes.
I work for an international consulting firm and we work with enterprise clients. Our job is to provide them with RPA solutions and ultimately, we would like to provide opportunities for them to have every kind of automation.
We began with use cases in accounting and controlling departments, after which we moved to automate banking, legal, and IT processes. Nowadays, we are reaching out to HR to help automate some of their minor processes.
To this point, our implementations have been in an on-premises environment. At this time, we are in the process of migrating our on-premises UiPath environment to the cloud.
When I joined the RPA team, coming from a DevOps position, I assisted them with IT-related tasks such as implementation, packages, etc. I went on to become an RPA developer and began working on business sue cases. As part of my duties, I search for opportunities, help find internal clients, and improve governance inside of our enterprise. I am involved in all of the steps in the framework.
Our first automation was an on-demand service, used internally for us. We deployed an on-premises orchestrator, also used on an on-demand basis. Once we got this experience, we started building other solutions.
We deployed an internal chatbot named Alex, and our employees can ask whatever they want. For example, you can ask Alex what your salary is. Depending on your privileges, you will get more or less information. Everything is done using robots.
UiPath enables us to implement end-to-end automation, starting with process analysis, then robot building, and finally monitoring of automations. UiPath has been doing well in terms of Orchestrator and how we can see the execution and the reports and results of our test cases. It is doing well in these aspects, which is very important for us. We are doing end-to-end automation and monitoring using Orchestrator, and it is quite useful. This is something that we were looking for while deciding on the automation tool that we would like to go with, and that's why we decided to go with UiPath.
It has been helpful for regression testing. We are developing a big web application, and we are expecting changes every quarter. The development and deployment have been going on every quarter for the past two years. Previously, we had a team of seven or eight people who were doing the manual testing. By automating the testing, we have reduced the team's size to half. The remaining team members are not just analyzing the executions that we are doing with UiPath; they are also providing support. It has increased employee satisfaction because they don't have to do repetitive work again and again. It has been quite good.
It has been useful for unattended automation, and it has also reduced human errors in our organization. Reduction in human errors is the best benefit that we have got from the UiPath implementation.
The initial setup is completely easy and straightforward. It is just like installing software in a system by clicking "next, next, next." At the end of it, you have Studio in your system.
If you need to allocate a particular system to Orchestrator, even that is a very simple process and there are videos available on the internet that show you how to set up the process quickly.
They have multiple tiers for technical support. I've used all of them. With the Premium Plus Support you get immediate remediation. You have a support representative available who is like an account executive and who is the go-to person for any issues. It's very easy and very quick.
The mid-tier is Premium Support where you don't have a direct point of contact, but you still get priority service.
We recently had a production issue with Orchestrator. I opened a ticket on February 2nd and we just resolved it this morning, six days later. It wasn't a big issue but it took them some time. That was with the free support. I didn't expect them to prioritize it
Overall, they are responsive. The top-tier support is a 10 out of 10, the mid-tier is about an eight out of 10, and the free support is about a seven or eight out of 10.
UiPath Orchestrator is definitely a plus point in the product. This helps in all formats of UiPath version ranging from PoC till Product Deployment.
The user interface is amazing. If we want to look at the conditions, we can do so easily. We can just search and we can find it. It's very simple.
They provide architecture that is really amazing.
It is quite stable. It is really good and very reliable, which is what I really want.
You can scale the solution very well.
I have used automation. The report was helpful. It trains employees - even those that didn’t have any experience. In UiPath, it’s not as clear how you go about things or where to click. It's very difficult to change items. The best part of UiPath is the automation.
I have a downloaded code. When you ship the plan from one country to another country, there will be a lot of historical data in the item. Typically, we have to delete this manually. It is a lot of data. We have exclusively recruited people for this job in the past. Then, we came up with some designs for the automation and it has saved them plenty of time. We are able to finish all the deletion of unnecessary data in record time. That was a really easy way to help save time and human resources. Automation Anywhere is really helpful financially.
Manually, a task like this would have taken around 30 days to deal with 10,000 lines of deletion. Now, with automation, the same task can be done in two days.
In the past, our recruits have come from Ireland. I’m not sure how much labor time we’ve saved with UiPath, however, it’s significant.
I have tried UiPath’s Academy. I got certified from UiPath. The best part is that the lectures are really good. They also provide the trial motions, which is really helpful when learning.
I have watched UiPath Academy’s orchestrated videos and done the pre-development. I completed the entire video and then did the test. They have certified me for Orchestrator and the developer parts.
One really good thing about UiPath is the user community. We can just search for a term and get help with questions. Most questions will be answered by the community. That is really amazing and helpful. Participating in the community makes UiPath really easy. It's very easy to find solutions to questions you have.
The UiPath community compares well against other RPA communities out there. On a scale of one to ten, I would say that the automation ranks at a nine. It’s a helpful tool.
We use attended bots as well as unattended bots.
Attended automation has helped to scale RPA benefits in our company by automating departments or all specific processes that require human-robot collaboration. We know how to use automation with merchants so that they help you with authorization for the end-users. The robots have really helped us in specific use cases, especially around logistics, for example.
We have just started using UiPath’s AI functionality. We are exploring it now after we got some orientation from UiPath. Within one year, we'll start using it for the plans that we have created for this year.
UiPath automation has reduced human mistakes. That is the best part. If somebody, a human, does the same continuous actions, mistakes will happen. With automation, we’ve had zero errors at this point.
reviewer1848285 says in an UiPath review
Business Analyst at a manufacturing company with 10,001+ employees
UiPath allows us to implement end-to-end automation. We utilize the Task Capture functionality for some of the initial parts. Then, building the bots is done with Studio, and Orchestrator is used for monitoring. It's complete, end-to-end automation.
The invoice reconciliation has been very useful. We now process 80% of our invoices automatically, of which 80% of those get no human contact. The remaining 20% of the ones that are automatically processed are either exceptions or they are certain expense items or the price doesn't match up. In this case, there's some human intervention, but we are getting a high percentage of things going through automatically.
This automation has enabled us to move some headcounts into different, higher value-adding activities instead. We have freed up approximately 10 full-time employees by using UiPath. We didn't let anybody go. Rather, they've been moved into other more creative roles.
Using UiPath for automation is a little bit costly but it saves a lot of time, and it also reduces human error. When humans perform tasks, there are a lot of errors that come about. However, when a bot performs the same task, the number of errors is significantly reduced. This is the reason that companies are implementing UiPath and undergoing a digital transformation.
In our experience, bots run with minimal errors, in the one or two percentage point range. Of the thousands of items that they process, very few will result in an error. Humans, by contrast, normally have an error rate of 5% or 6%.
It is very easy to develop automation using UiPath, and I would rate it a four out of five in this regard. This is true whether it is IT automation, UI automation, desktop automation, or otherwise. We have even performed Citrix Automation recently, where we used remote runtime. In that case, we had access to a lot of features and this made our work very easy to do.
This product enables us to implement end-to-end automation. Some of our clients use the process mining feature, which includes task capture. Then, based on that, they generate the process design document (PDD). After they have the PDD, the bot is designed using Studio, and then it is ready for deployment. Deploying a bot includes publishing it using Orchestrator, and once it is running, Orchestrator monitors it. From end to end, UiPath is part of the process.
This is important to us because some of our clients are not very technical. They have ideas of what they want to do, so they walk us through the steps in a process. During that time, we will begin using the task capture capability to record what they do, making it easier for us to gather ideas and requirements. The whole process is an easy way to capture good use cases for the client.
Most of our clients are now opting for cloud-based deployment. This is important to them because they don't have to store everything on their on-premises servers. Essentially, they don't have to waste any space.
One of the projects we have been working on is for a medical company. It includes fetching medical records from the company's web-based portal. These records have to be pasted into Excel and consolidated. We then send them back to the client via email. We use Orchestrator to schedule the process to run every day at three intervals. It is running as an unattended bot.
We have also used it for another company to help with their employee onboarding process.
reviewer1859118 says in an UiPath review
Senior Software Engineer at a tech vendor with 1,001-5,000 employees
One feature that I personally found valuable was the orchestrator. It is a pretty mature platform as of now, and it was three to four years back when I started to first use it. It has matured quite well. They had a major change a couple of years back. Our company transitioned from an older approach to a newer modern approach that they deployed. The orchestrator platform was very well-suited to the new approach - as was the development studio. It's really easy to use and intuitive. That has matured quite well as far as I can tell. These two are what I liked the most about the product.
UiPath’s ease of use and quick deployment times were great as the cloud orchestrator, which did not need much of a setup.
To build automation using UiPath is fairly simple. The studio is quite easy to use. Even now, with the community edition, it’s great. If we want to learn to start or try out something, we do not have to wait for licenses or anything else. That said, we can also get an enterprise trial. If we want to do something, learn something, even during our personal time, we can just download it. They also provide a free orchestrator version as well, so it becomes quite easy to learn and develop.
The building, deployment, and manual deployment processes, for small-scale projects, are very easy. If we need to build something, we just publish it, and it generates the NuGet package. It's very easy to deploy there.
The materials and the training courses are all pretty well-structured to get started with.
UiPath Academy courses have assisted in the process of getting our team up to speed. The basics were there even when I started out. I was not initially an RPA developer. I was into server operations before this. The UiPath Academy training really helped a lot with the initial courses, where they give you a tour of the platform and each and every activity. For audiences who are not much into software development, these courses can guide them towards that. The building blocks got us up to speed. They have very good courses there.
Regarding the Academy, it is a great learning platform for basic tasks. However, for more complex information, I turn to UiPath Forum. Sometimes I need some Python or C# scripts or am building custom libraries there. That gets shifted onto different platforms like Stack Overflow. We Google other platforms as well for the other types of queries.
UiPath Forum is a pretty good place in terms of the user community. Most of the queries that are posted generally get answered. Sometimes, even for smaller issues, we do not go directly into UiPath support and we first try to resolve the issues via what we find in the UiPath Community. Overall, it’s a pretty good place to solve our issues, and the community as of now is pretty active.
We saved time in our IT department since we started to use this solution. UiPath handles infrastructure for the orchestrator and its maintenance. There's a pretty good amount of time saved as we had initially had a server on-prem deployment as well. However, it became cumbersome to deploy multiple databases and they have some Elasticsearch requirements and security updates that need to be regularly maintained and in sync with UiPath. Due to this infrastructure overhead, our time could be consumed maintaining everything. Without them handling the infrastructure, we'd be maintaining instead of building automations and deploying them. We realized that an automation cloud would be a better option which is why we switched.
UiPath reduced human error. That said, we do not track errors in the process. It's a good metric to track as well, however, we currently do not track it.
It reduced employees’ time on certain tasks. The main purpose of automation is to save us the number of hours that the project will take. There are many other parameters, however, the time saved is one of the big ones.
reviewer1860774 says in an UiPath review
UiPath Solution Architect at a financial services firm with 10,001+ employees
UiPath Orchestrator is a treasure, and UiPath Studio includes various packages to integrate with solutions like Salesforce, ServiceNow, and Excel. They also have mainframes, web automation, and the API package.
Orchestrator contains a lot of useful apps, data services, and machine templates. From a usability perspective, the most valuable aspects are its custom activities, libraries, and object repositories. In terms of integration, I like the ability to use APIs and call automations from UiPath apps. The most valuable feature from a human-in-the-loop perspective is the action center.
Our customers appreciate the support that UiPath provides, and they don't want to go with a third-party vendor like Microsoft Visio, Form Recognizer, or Google Cloud. They're hesitant because some integration is required. The lead times for closing queries are longer with third-party vendors. For instance, it takes me about two or three weeks to set up Document Understanding in my project. But it took us three months to establish Form Recognizer with a client.
In addition to the out-of-the-box functionality UiPath provides, it can host our custom models. That's something that comes in handy when we need a custom model. So far, we haven't taken it to production yet, but we are still baselining the technology. At the moment, we are doing a baseline project where we try to perform four POCs simultaneously. We are baselining Google Cloud Platform, Azure, and AWS with UiPath's AI center and machine learning services and comparing the four.
The most valuable feature in UiPath is the UI interaction with UI Explorer. I have worked with other automation tools and UI Explorer is the standout feature of UiPath. For web-based applications, we can interact with every HTML element, from head to tail. UI Explorer is a valuable addition to UiPath for creating complex, web-based automation.
The AI Computer Vision and Orchestrator are also outstanding features. They make it very easy for developers.
In addition, the introduction of drag-and-drop APIs to UiPath enhances the development processes and decreases the time it takes, as well as the processing time. For example, if you wanted to read an email from Microsoft Outlook using UiPath two years ago, it would take about five steps or activities. Now, with the Graph API within UiPath, you can read an email message from Outlook within a span of five to six seconds, maximum. This API functionality is pretty easy for us to handle.
Along with this, UiPath also introduced Orchestrator access via API. It's not mandatory to log in to Orchestrator to create an asset manually in UiPath. Rather, you can use the Orchestrator API to call a bot process and the assets. This API functionality helps developers to develop components effectively, as well as reduces bot processing time drastically.
reviewer1865436 says in an UiPath review
RPA Analyst at a tech services company with 501-1,000 employees
The solution helps a lot when we are dealing with big companies where governance is a must. We can have multiple centers of excellence at different places in the company. UiPath is easy to deploy and easy to manage for such companies as we can centralize a lot of things in one place.
For example, with Orchestrator not only can we monitor all the bots and processes, but it helps in the development phase as well. If we want to have custom libraries that solve specific problems for the company, we can create those custom libraries and share them throughout the organization. This helps a lot when it comes to governance, compared to other automation solutions.
I created a project based on attended automation and it was successful in helping the user. It was a bot to create engineering reports and the user was able to implement it on a daily basis. I have a positive view of attended automations. Having said that, unattended bots are preferable because we want most of the processes to be automated, end-to-end, and not require the user to start them. We use attended robots only when there is no other solution. So attended bots are not as relevant as unattended robots, in my experience.
In addition, because the user did not need to create that report anymore, he could focus on more analytical thinking. That is something that I always say when starting an RPA project. Users become freer to do analytical thinking and not robotic thinking where they just click here and there and move some Excel files. I would estimate it saved them five to eight hours a week.
In a lot of the projects I have worked on, reducing human error was one of the priorities for the automation. When working with human resources, for example, reports could go wrong if the user did not create them properly. This could cause the company to have to pay fees. Automating those reports reduced the risk to zero and helped with compliance.
UiPath also reduces the overall costs of automation operations. Although it's more expensive as a solution when compared to other vendors, because it's a very consistent application and there is really good support from the UiPath team, it is the fastest when it comes to developing and deploying automation. It is surely the most reliable in the long term. That's where UiPath is at the top.
The direct integrations are most valuable. You can directly link your account to multiple platforms, such as Google Drive and Visio, without using an API.
We have used the Orchestrator's trigger creation workflow to create multiple triggers for our automation processes.
UiPath Orchestrator is incredibly useful. It's the main dashboard platform we use. The studios and development boards are also helpful. Orchestrator provides a single platform we can connect with the other legacy systems and manage all the bots.
Orchestrator lets us see the entire process across various department units so that they can see the separate tenants and units. The application can multi-task to handle processes even when we have a long queue. If the queue is piling up, we can assign multiple robots to clear the queue quickly. We can find the ETA for the queues and everything inside Orchestrator.
reviewer1895613 says in an UiPath review
Process Automation Analyst at a non-tech company with 1,001-5,000 employees
My previous company was in the banking sector, and we had done automation with websites, UI, SAP, Excel files, and PDF. In my current company, it is being used for finance and HR. We have ERP, CRM, chatbots, etc. We are using this solution to integrate different systems.
I use UiPath Studio to develop the code, and I use UiPath Orchestrator to publish my work. We have our own UAT systems to test the code. We can install the UiPath in the test environment and find all the compilation errors in the debug mode and fix them. We also have version control. If we upload a version and it doesn't work, we can downgrade the version. Everything is tracked in UiPath Orchestrator.
We are using it on-premise. In my previous company, it was on the cloud, and we accessed it through the cloud.
I tested the Process Mining at my previous company and I don't think it's suitable for RPA processes. It operates at a way higher level and, using it, you may find an area in which you can optimize a process, but it doesn't just give you a defined process for automation. It doesn't necessarily help you to identify the processes.
The Task Capture component offers the ability to record a process and it will give you process documentation. It tells you how many clicks are being made, and it will create screenshots. It tells you the basic activities that are being done in the process. When we tested it, the quality of these documents was very low. It took more time to take the output and make it useful than it would have taken to analyze and document the process ourselves.
We are not using any of that. Together with the customer, we are manually defining and documenting processes. We are doing the actual automation, of course, with UiPath. In terms of monitoring it afterward, it's 50/50. Standard Orchestrator definitely offers you some ways to monitor your processes. It tells you how many processes failed and why they failed. You could also define a process that sends you an email when it fails.
UiPath also offers some BI components, but that requires a separate license and costs. We are not using them. The whole BI reporting functionality of standard UiPath is not that great. We use external dashboards in Power BI.
We also have a calendar application because, with standard Orchestrator, there's no overview about when you have bots running and when you have free slots. So it's also not great for planning license usage. The whole visualization piece, out-of-the-box, is not so nice. UiPath is mainly the automation tool for us, and it's definitely great for that. But in terms of analysis and monitoring, there's definitely still potential for the software.
I am not an experienced developer, and working with UiPath has taught me a lot. We use UiPath Orchestrator with a combination of unattended and attended bots. That functionality allows you to manage your platform virtually. You can monitor everything and assign new roles to users.
I'm the lead robotics engineer in my organization, and we are involved in marketing and research for new technologies such as mobile phones and laptops. We are an organization with 219 employees and started using UiPath for laptop marketing and advertisement for our customers.
Our clients have different requirements and strategies, and we build software robots tailored to their needs. A customer can send an email with attached PPTs, Excel sheets, PDFs, and images, and the bot can extract all the data and express it in the required format. This is uploaded as an article onto our website, and on our platform, so the marketing, advertising, and technology solutions specs are taken care of without any human intervention or involvement. We designed 39 robots for the same number of clients.
Our second use case is for invoicing; customers share checks for payments with us via email, and we have bots to extract that data and input it into our SAP ERP system, which is fantastic. The RPA automates billing on the financial side of our organization.
We use the solution across 17 locations with servers managed centrally from our main office, connected using the UiPath Orchestrator. We have 19 licenses but only use 17 currently. We don't have more than seven end users as this is purely a tool for internal use; our customers don't have access.
I would recommend it to new users who are choosing among automation tools.
Also, if a company is new to it or the users who are setting up are new to it, they should be aware of the preparations involved in setting up the environment and setting up UiPath. That can be a little challenging if they are not aware of certain things.
I rate UiPath at eight out of 10. There are a few features or approaches they could enhance, such as an option to view all the variables, as I mentioned earlier. Also, since the code can be very big, we might be searching for certain things that are not available. I'm more concerned about the debugging and evaluation parts.
And in Orchestrator there are a lot of features they can enhance.
The specific feature I like is folder organization, and it is in the Orchestrator tenant. This is very useful because it keeps all of my folders and data in a centralized tenant.
The menu options are easily accessible in the Orchestrator tenant, which is something that I like very much.
The UiPath Academy was pretty helpful for us in the initial stages. We were able to learn more about the software and what is there. They also provide courses and certifications, which assist with learning and getting employees up to speed.
It took only a week for me to completely get a handle on the software. Taking the initial training and certification courses is a hassle-free process. It is not difficult to induct somebody and have them start using the product.
The courses that they offer provide hands-on experience, and I think that it's a good initiative that they are taking on by doing so. It helps to ease the learning curve and allowed us to learn more about the world of automation.
UiPath has a user community that is very knowledgeable and friendly. Our peers in the UiPath community are able to dumb down responses to a beginner's level of experience, regardless of what queries we have put forth. Whatever we have wanted to do with RPA, they have been able to help. We now have a good level of comfort in terms of interacting with our peers in the community.
We have experience with other communities and have found that the discussions are generally at a higher level, which may be too difficult for a new person that is just starting out with the product.
Generally speaking, I like the features that I am using and I could not really say where improvement is needed in that respect.
reviewer1910595 says in an UiPath review
Technical Consultant at a tech services company with 501-1,000 employees
The best part is the way UiPath provides the ability to automate everything, including the architecture and Orchestrator. The interfaces are very user-friendly and intuitive. It's very easy to build automations. Someone who is not very technical can understand quite a lot and start to automate.
All automations are built starting with process analysis, then robot building, and monitoring. One person can gather the requirements, build the automation, and monitor it. This end-to-end coverage is very important. I can't even imagine how it would work if not in this way. This is the essential part of the automation: the idea, the implementation, and the maintenance.
UiPath's approach allows adding new workers, new agents, or robots to perform quicker and in parallel. For example, if you create two extra virtual machines with two extra robots, a whole bunch of operations will be performed three times faster. This kind of implementation is very convenient. And, we can change the way automations are deployed in Orchestrator and make it more efficient as well. We can do all these kinds of things really easily and quickly, like in minutes or less than an hour. That helps to scale things. You can change something in an automation in several minutes and deploy it or publish it in Orchestrator, and it already works. The challenge of implementing innovation can be addressed very quickly and very efficiently. The challenge is that we have to change our automations because other applications change with time. They have new user interfaces. But we don't need to upgrade anything to automate.
Several of our team members are studying the UiPath Academy courses at this moment. It has definitely helped because they get to know about new features that make automations more mature. One of my colleagues said, "As I read and study more in this course, I begin thinking more creatively and in more interesting ways." That means their understanding is growing and that it is changing their perceptions of what they can do with UiPath.
The information in the Academy is structured, starting with simpler concepts and moving to more advanced levels of knowledge, gradually. Also, you really learn about things you haven't used before. Thirdly, it leads you to the certification exam and getting the certificate on passing this exam. That makes you a good candidate for better jobs.
UiPath also has a very nice community of developers. When I face problems that I can't resolve by myself after several hours, I Google it in the UiPath Community and almost every problem can be solved by searching their resources. I work with different vendors and not all of them have such a big and open community. This is a real advantage. I'm not very familiar with other communities in RPA, but I can say that this community is, by far, more useful and more open than any other vendor's community I have seen.
I am very happy with the stability of it.
I wish that there might be a better, easier method of updating our platform, especially for on-prem. I believe most of their customers are cloud-based. So, they don't have to worry about updating their Studio versions or Orchestrator. Being on-prem, it can be difficult because we must reach out to have that version. We can't just plan on our own. We are always at least a six-month step back versus the current version.
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.
reviewer1976400 says in an UiPath review
Developer at a wholesaler/distributor with 10,001+ employees
The complexity of the setup depends on what you're trying to deploy. If you're deploying only the orchestrator and setting up robots, it is pretty straightforward. If 10 is difficult and one is easy, I would rate the setup a three or four.
The certificates needed to set up the orchestrator can be confusing and frustrating during setup. For the most part, what you need to do is straightforward. When it comes to installations that require a Linux virtual machine, Docker configuration, or Kubernetes, the setup is more complex. It is more complex to set up an on-premises configuration compared to a cloud configuration.
I deployed the software and the Orchestrator Studio. I run eight or nine virtual machines that I have our LOS on and created processes where the LOS can feed the work queues so it takes care of different processes on schedule every day. The deployment took four months.
William Cusick says in an UiPath review
Sr RPA Architect at a tech services company with 201-500 employees
The Orchestrator really stands out as the most valuable feature. We don't have to train anyone. They can usually pick it up really quickly. It is easy to use and intuitive.
A lot of the packages are very easy to work with. There are some challenges when updating a package that you've built or a library that you've built in UiPath. Overall, the extensibility is really nice.
reviewer1976424 says in an UiPath review
Technology executive at a financial services firm with 10,001+ employees
I was not involved in the initial setup within our environment, but have managed the deployment of several hundred automations and the process is straightforward.
It is very easy to use our CICD pipeline to deploy and monitor solutions via the orchestrator tool.
Nitisha Mungara says in an UiPath review
Business Analyst at a healthcare company with 5,001-10,000 employees
With the latest upgrade of Orchestrator, about a month ago, sometimes, when we are running our bots, the server crashes and the bot has to stop. There is a certain time limit to it. About two or three hours after it runs, it closes down and the bot stops and you have to rerun. There is some sort of a timeout issue.
It's something that we are still figuring out with the support team from UiPath. We don't know if it's something internal to our systems or if it has something to do with the upgrade. We have been in that loop for quite a while and have yet to receive a resolution.
reviewer1978710 says in an UiPath review
Manger at a computer software company with 501-1,000 employees
The Insights could be improved to be more user friendly and less reliant on code for building specific dashboards.
The Orchestrator could be improved to make it easier to manage folders where bots are stored.
reviewer1978716 says in an UiPath review
RPA Developer at a computer software company with 501-1,000 employees
The upgrade process could be improved so that it does not require download and reinstall. It would be nice to have an upgrade option that talks directly to the orchestrator.
Some documentation can be improved. For example, documentation for integrations and activities tells you what it does but does not tell you how to fill in variables or fields. I had issues finding some things I needed for new activities or integrations.
The biggest pain point we've seen so far is that we have trouble identifying best practices in certain areas and circumstances. There is no shortage of resources in the Academy and on the forums that have great information. That said, a lot of them are specific to use cases, or they're too generalized, which makes it difficult to know exactly how we should be handling a certain scenario or just some basic things about how to best set up the folder structure for our given environment.
It's been difficult to navigate that as it is still so early in our implementation of RPA. We want to ensure we're doing it right to establish a good foundation from which we will build all of our future automation. We are constantly concerned that we're not doing something the right way.
During a UiPath conference attendance, I really appreciated having access to experts directly. I can just ask them, "Here's our scenario. In this context, what's the best practice?" And I can get a straightforward answer. We don't have access to them outside of this conference. I don't always have the time to watch the videos or go through the multi-hour-long training to get to the one best practice that might be nested inside a larger training.
Finding some of the answers ourselves is difficult since they are contingent upon our scenario and the context we're building. There's not a one size fits all. To that end, it's no surprise that there's not going always to be a single solution that can just be published to say, "Always do this, this way." Without that context, we really do need to be able to talk to somebody, and we haven't had that yet.
In terms of the UiPath community, I probably can't answer a whole lot of questions since I'm so new; however, for a community like that to function and succeed, there have to be enough people with the expertise that are willing to put in that time for free. In a realm of automation that touts itself as a solution for people who have no time, it's no surprise that there are not always people that are willing to sacrifice what time they don't already have to begin with to give out free service.
Once I have automation ready for production, I don't see a way to deploy that to a production tenant environment without manually recreating everything. In a typical development environment in software development, you develop in one area, and then when it's ready for deployment, it's packaged up with all of the assets and everything that it needs, and then you deploy it to the production environment. You do some final testing to ensure the deployment takes, and you're done. Whereas here, it seems like I'm having to recreate everything manually. I can import the automation, yet I need the whole structure and orchestrator and all of the assets (75), and I have to recreate everything manually. It seems something is missing.
reviewer1978977 says in an UiPath review
Developer at a recreational facilities/services company with 10,001+ employees
The UiPath Studio has been very necessary for us.
Orchestrator is a vital feature. We have a sizable infrastructure, so it is necessary to have Orchestrator deploy all of the robots in all of our servers. It is not possible to work only with one computer. Therefore, that is an essential feature for me.
We've been able to save on man hours. We save around 60 manhours daily per department. For example, the maintenance department works with many people, and we can save on labor.
All departments use automation; however, mainly the logistics department benefits. The finance department comes in second, and after that, production. We've created more than 40 automation so far. We use both attended and unattended robots.
Even if you are just on a laptop, you can have UiPath.
I've used the UiPath Academy. It's necessary to have credentials for the infrastructure. It helps us understand the features of UiPath properly.
I use the UiPath community a lot. When I have a job, I can write a question about it and get a response from an expert. It's quite a valuable service. With the community, we can reduce the time to resolve issues. We can learn from other people who have faced similar challenges.
Setting up automation can be easy or complex, depending on the project.
reviewer1137945 says in an UiPath review
Chief Robotics Officer at a tech services company with 11-50 employees
The environments that it can be used in can be very complex, such as "multi-tenant," where a tenant is the protection of data from Orchestrator, where you have segregation or air gaps. We've done some projects with a defense ministry that are very complex and we've done some very simple ones.
Most organizations start small. There will probably be a pilot with a cut-down version of what is needed. As they grow and scale, they will invest in more tenants and in more infrastructure and more components of the platform.
So far, we've only focused on UiPath Studio and the Orchestrator piece. It's been great and we are looking to expand it to the digital assistant platform soon.
The UiPath community has been great. There are a lot of great mentorships, a lot of forums, and a lot of people who are very interested in growing the community. It's been very nice to work with them. Anybody who is in UiPath has been an amazing partner for us.
We have also used UiPath's Academy courses and we have two members who are now UiPath Certified. It's a very easy training course to follow. It's low code and comes with a lot of resources and a lot of forum assistance. It enables people to learn without feeling the pressure of having to figure it out on their own.
reviewer1986627 says in an UiPath review
Director of Transformation at a retailer with 5,001-10,000 employees
UiPath Orchestrator is a valuable feature for us. We started with all attended bots without Orchestrator, on-premises, or on the cloud. It was almost like a very low-cost way to prove that we needed this technology and that we could use it. So, for our first year, we did that. For the second year, we got Orchestrator, and it gave us the ability to utilize the bots more effectively. I thought we were going to have more attended bots, and we didn't because the process owners wanted things to happen in the background and wanted to be able to schedule them. Being able to do that and not have to have someone worry about triggering the bot or babysitting the computer while the bot runs, etc. have been the biggest game-changers for us.
The biggest benefit we've seen from using UiPath is time savings. Since June, when our fiscal year started, we've saved 8,000 hours so far. We're measuring everything in terms of hours saved, mainly because that's where we see the most benefit. I haven't really seen a big cost reduction, like replacing people with automation. Our teams are pretty slim right now.
A lot of the time what we found was that people were working extraordinarily long days. Now, they're actually able to do their job because they don't have all these other things that they had to take care of before. With some of our use cases in customer service, we've been able to avoid costs by not having to hire temporary staff. This is because a lot of the transactions that they would've taken care of are now done by the bots. They are doing it faster and more accurately. We have automated 36 processes so far. We have three attended, but most of our processes are unattended.
The biggest value of the UiPath Academy courses has been the ability to point new citizen developers to it. They are self-guided and require very little oversight from the team, so it provides the ability to grow a citizen development community with very little time from our team. The UiPath Academy is also useful for onboarding new team members; you can point them to some of the basic courses and have them get an idea of what RPA is all about, what we have, Orchestrator, etc.
I do all my developing in Studio. I develop and publish into the orchestrator cloud, and then I try and run everything unattended. So, Studio is a very valuable feature for me.
Another feature that I've been using a lot is the new integration app with Microsoft that triggers emails.
The UiPath Academy courses are great because when there are things that you don't know right off the bat, it helps you develop, learn, and grow within the platform. I've done a few courses and plan on doing more. It's definitely helpful for me being someone that didn't come from a development background. I taught myself UiPath in the beginning, and now that I know how expansive the Academy is, I'm definitely going to take more classes so that I can learn exactly how much I can do with UiPath.
It remains scalable for us. We're not a huge shop yet as far as the number of bots, so it remains to be seen. It will be interesting when we try to reorganize our Orchestrator to make it more scalable. I can't really answer that one yet, as we haven't really tried to scale a lot.
The solution is easy to set up and deploy both on-premises and in the cloud.
As a solution architect, I am involved in all phases of deployment including discovery, development, implementation, and post-production.
The deployment process includes exporting workflows as a package, saving and loading the package in the source control tool, and pushing the code to the orchestrator. The process is very simple and there is no real maintenance after deployment.
The scalability depends on how you develop it. If you develop it to be scalable, then it will be scalable. In terms of Orchestrator, the platform is pretty good at scaling because it allows you to keep deploying it and branching out.
The stability of the product is very good.
If you look at the key components and the visuals, I mean the Studio, the Bot, and the Orchestrator, the Bot and the Studio are within our environment. We haven't experienced any issues. What is left is the Orchestrator, and we haven't seen any outages so far.
Tony Kilanowsky-Reyes says in an UiPath review
Revenue Systems and Process Manager at a consultancy with 1,001-5,000 employees
The low to no-code is by far the most valuable feature. Developing a bot in under a minute that saves you an hour a day is phenomenal.
The user community is great. Looking at the forums, when a question is posted, the responses are fairly quick, either from UiPath or the community itself. In my past role, I posted to the community before, and I had been able to answer some questions as well. Then, it's nice to know people are having the same problems you're having and finding solutions.
I've taken UiPath Academy courses. I've taken mostly the developer ones, and then I'm looking into more of the admin side, with the Orchestrator and project management side of it. The biggest value is that it walks you through step by step and you're doing it alongside the course. It's hands-on learning. It's one thing to watch a video. It's a different thing actually to play with it and have something start working.
I love the REFramework and the Azure Queue and Orchestrator. Those are great features. They all work well.
The UiPath community is awesome. That's one of the reasons I use UiPath. There's so much stuff available everywhere. For example, if you go on Google and search for a subject, you are going to find information on either YouTube videos or community sites. There's just a lot of information available about everything. Also, a lot of super complete documentation is on the UiPath website. Any question we get, it's super easy to find technical information on that subject.
I've used the UiPath Academy courses. It has helped me start very quickly since they're all free, and there are many courses to choose from. When I started, I used my first two weeks to just do Academy training, and that's how I started. They have a complete curriculum. It's pretty nice.
reviewer1986756 says in an UiPath review
Director of global process improvement and automation at a manufacturing company with 1,001-5,000 employees
We are still surfacing demand for automating processes based on sustainable or environmental causes. We aren't using any automation to promote any good causes just yet.
I have yet to be a part of UiPath's user community and have yet to understand what they offer.
We haven't gotten into the UiPath Academy. We partnered with a couple of vendors, and I'm not sure if they're Academy-certified people.
At this time, while we do use AI, I'm not sure if it's UiPath's AI. We are still surfacing the process. We've done a proof of concept, and we have to measure the metrics to see if it makes sense for us to move ahead.
For us, at least, the cost is the biggest factor for us to scale up. For others evaluating the solution, they need to look at ten years down the road or what is their vision for automation. Only then can they effectively evaluate the products.
This solution was simple, and it was easier to use, so we took this first, and now we're pretty much married at this point. There isn't anything to complain about, however, if we had the vision to see where we would be, we might have looked at other products more. I don't have any complaints as of this point. As of now, the cost is the biggest sticking factor for us.
I'd rate the solution seven out of ten.
You have the studio licensing, and the orchestrator. The architecture is complex, at least from a business point of view. There are a lot of moving parts that I have to work with. As with any product, I would just want it to be up and running immediately without the hassle of maintenance. I feel the maintenance factor in this product is high.
One of the improvements that could be made is the support interface. I've talked to one of the product experts today about how they could better show when there are issues with a particular job. Right now, we tend to find that everything just looks okay unless we really go out of our way to highlight issues. What we would really love is for there to be a way to flag in Orchestrator exactly which jobs had warnings, exactly which jobs had business exceptions, exactly which jobs had exceptions that were handled, and which ones had unhandled exceptions. Right now, we are forced into this success or failure state. The lack of granularity makes it very difficult for us to quickly and easily find where we need to address issues.
There is no out-of-the-box way to configure granularly. This is where our maintenance processes are starting to come in. They're trying to fill those gaps, yet realistically, it would really be better to just have those visuals right there in Orchestrator without us having to rely on making our own API calls and checking for special criteria outside of what UiPath would be able to detect on its own since we're setting it within the code itself.
The UiPath Academy courses are disorganized. We have trouble identifying exactly what we want people to learn from within the list of courses, and since they've changed so much, it's sometimes hard for me to know what my coworkers are learning versus what I learned. I don't know where either my gaps or their gaps are. I don't know if I need to assign extra training or if maybe I need to go back and take a newly added training. That can be difficult for us.
Our challenge with UiPath is getting the infrastructure assets up to speed, particularly on the Orchestrator side. However, I just now came from a demo for UiPath Web, and it seems to be to enable serverless robots, which would definitely be a lower barrier to entry.
Our pain point is just on the infrastructure side and getting the assets coming up to speed. It's a big bank problem. We have a very large IT organization, which is not always aligned with the needs of teams like ours.
The way they stay on top of Orchestrator is really helpful because that has been the platform that controls everything. The dedication to that is pretty helpful. Every time there's a new release, it seems there are more and more features. It's also not hard to learn.
When it comes to the UiPath Community, everybody is helpful. If you don't know how to do something or you want to learn about something, it's pretty easy to connect with other people or talk to people at UiPath to get that knowledge or learn how to do something. You can also just point somebody to UiPath Academy. They go from knowing nothing to being pretty good with things pretty quickly.
There are two features that I like a lot in UiPath: one is the Orchestrator option, and the other one is the Studio option. I especially like Orchestrator because it's very insightful for us. It's like a centralized hub to manage and maintain all of our process automation and task-mining. It systematically organizes each and every folder so that it's easy for us whenever we need to know, set, or take something. Studio is where we primarily do most of our designing. It's a very good tool. Most of it is drag-and-drop. These are the two main useful features for us.
The option to record processes is the most important feature of UiPath. We can use it to record every action automatically and it is then converted to a workflow. This workflow defines the complete set of processes so that we can automate every requirement.
A related feature that is one of the highlights is the AI. We have used many other scraping solutions, but none of them was effective. UiPath, however, can easily scrape data from webpages and applications and it works flawlessly with any program including .NET, PDF, legacy, and SAP.
UiPath has three components, UiPath Studio, the robots, and UiPath Orchestrator. UiPath Orchestrator is a web-based application for deploying, monitoring, and scheduling bots. With Orchestrator we can manage everything regarding the bots. We can customize the actions, but there are also templates. For example, one of the templates enables you to upload to OneDrive from Excel sheets. We just add the parameters and the automations are done.
We have used a few of the UiPath Academy courses, basic classes, because we use the Community Edition. When we move to the more advanced version of UiPath we'll be doing more of the classes. The Academy is very user-friendly. We don't require any further lectures or other sources for learning. A user can watch these videos and start operating the next day. All the actions and features, everything, is clearly demonstrated in the videos. It has proved to be very informative for us.
Kryon RPA: Orchestrator
Kryon RPA's interface isn't as developer-friendly as UiPath's. I'd also like to see more seamless integration with other solutions. For example, with UiPath, we can use a lot of APIs. I also like Orchestrator from UiPath. We can control all of the robots that we're developing in the machines in the bot runners. UiPath Apps is a new tool that I like.
Microsoft also has some amazing tools, like Power Automate Desktop, Power Apps, and Power Automate Online. These tools can integrate with bots on Power Automate Desktop.
Jiffy.ai Automate: Orchestrator
The workflow engine is definitely a very strong asset of Jiffy.ai, because it is easy to configure. It has a nice user interface. It is also scriptable. It doesn't have a steep learning curve. It is quite easy to learn, so you can become productive very quickly. Up until now, their automation tool combined with the workflow engine has been their strongest asset. It has helped us extract information out of an application which otherwise would have to be done manually. So, it gives us the opportunity to automate a lot of tasks related to extracting information, rather than delegating that to actual people. It has saved us hundreds of hours per month. It has covered the work of two or three full-time operators.
Jiffy.ai's app-based approach is suitable to automating entire complex business processes and to an approach that only automates specific tasks within a process or workflow. My impression is that the solution is so flexible that it can combine multiple applications into the workflow and interact with all of them. For example, in a Windows environment, it can launch one UI application, interact with it through the workflow, launch a process into a remote virtual machine (or interact with a remote service), fetch the result, and then feed this back into the local desktop application. My understanding is that it can deal equally well with tasks within a single process and tasks that span multiple applications in multiple environments.
It can definitely support integration with other third-parties. The combination of all these features can create very powerful applications. Our use of Jiffy.ai so far is a bit limited because we are using desktop workflows and the AI aspects of it. However, combining these can create a powerful set of features for creating more advanced applications. It can be an integral part of a bigger system. For example, you can have a front-end application that is delegating requests back into the Jiffy.ai, then Jiffy.ai will essentially act as the orchestrator for back-end services. So, it's quite powerful. The fact that it has a UI means it is accessible to non-technical people as well. So, you can get from the design phase to implementation phase very quickly.
Jiffy.ai has its own notations for specifying the theme navigation of individual nodes. That notation has the most common structures that you would expect from a programming language without some of the most complex features, like memory management or complex design. I feel it is accessible to junior developers. Now, you can be productive, even if you don't know any code despite designing the workflows. I see this being done in two ways:
- You can have someone who is non-technical design the workflow, essentially designing the control flow, specifying the input and output data, and treating this as a black box.
- You can have a junior developer who is familiar with the notation that Jiffy.ai is using for implementing individual execution nodes fill in the gaps. Of course, it needs some testing.
This is the development model that I see which is suitable for workflow entry. This means essentially that we don't need to engage expensive senior developers into managing the system. Also, it means that we can get from design to production faster. Essentially, this now provides an advantage, which means we use Jiffy.ai for more automation tasks as we become familiar with the UI and scripting notation.
Reviewer92674 says in a Jiffy.ai Automate review
Head of RPA COE at a transportation company with 10,001+ employees
Before we chose Jiffy.ai, we looked into other solutions, especially bigger, more established solution providers, like UiPath, Blue Prism, and Automation Anywhere. In terms of simplicity of usage, Jiffy.ai is easier to use since they are on a webpage. We put a portal on it and everything is available there. The UI is a bit more user-friendly and intuitive.
In terms of trying to do end-to-end process automation and how easy it is to do it, these are big pros and cons when compared to UiPath. In some ways, they are easier, and in some ways, they are not. I like with Jiffy.ai that we can use Python, but with UiPath, we can't use Python and need to use .NET. I'm unsure if they have enabled Python now. We also have a lot more flexibility with Jiffy.ai, e.g., we can connect to Google or any kind of system without having to do integration. We can just go from the front-end and record it. UiPath has this as well. You need to install Orchestrator on your PC. Then, you can install the design anywhere, because it is web-based, which is an advantage.
In other solutions, you have to install and set it up. If I have a new developer come in, then I have to install the system on their laptop before they are able to do their work. With Jiffy.ai, you can do it anywhere, on any laptop, as long as the laptop has access to the webpage. You just need access to the webpage, then you are able to do it. We control it from the portal as well. So, if I want to shut down or restart the bot, then I just have to go to the portal. I don't have to go to somewhere else, log into the server, or remote desktop to several laptops to do it. Everything is centralized on one laptop in one portal: the user access, the bot management, the task management, and the user interface for the human to manually handle certain stuff. Everything is on one page. This is an advantage over other solutions.
Microsoft Power Automate: Orchestrator
I would suggest others to go for it. It is definitely a great solution, specifically at the given price. It is really hard for companies that are starting with RPA to justify the costs of some of the competing products, which could be 20, 30, or more times more expensive than Power Automate.
Even at a corporate level, it would be tough to get to a stage where you would find the product having some inefficiencies or some gaps as compared to its competitors. I don't have an experience where we are utilizing the orchestrator, have unattended bots, or are coordinating 20 or more bots, but according to our partners, it is working in such environments. It is about how you actually utilize the product, how well organized you are, how good are your processes, how you are able to build them in the product, rather than the super hard limitations within the product.
I don't really have a full experience with it, but from what I see and what I've learned, I would rate it a nine out of 10.