UiPath Reviews

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

We are in the financial services industry. A lot of what we do is background data processing, and we use the unattended robots for a lot of it. We do have some attended robots as well, but most of our processes are unattended.

I am a developer, so I primarily use Studio. I write the instructions for our Orchestrator Application Manager to do everything we need in Orchestrator. 

We are currently operating an on-premises deployment, but we're in the pilot group for Cloud, so as soon as we get a date on that we'll probably be migrating.

One of the primary processes that we've automated is reporting. Prior to automation, our users were only able to run a few of the reports, a few times a week. Now, we're running every single report that there is to run, which is probably four or five times what they were able to do, every single day. Every morning they receive a summary of that work, so they're able to just get on and look at it, rather than during the close of the day. In financial services, the close of the day is crunch time. We work really hard to make sure that everything is done within a set about of time because there is a domino effect. One person has to be done before the next person can finish, and they're not having to dig back and try to figure out when these issues happened. We're providing it to them upfront. We can say exactly what happened, which account they need to look at, and on what date. This means that we're ahead of the issues, rather than trying to backtrack and find them.

We are not currently running in a Citrix environment, but the only reason we're not is that our sister company hosts our Citrix environment, so we can't install any of the services that make those environments much easier to utilize. For example, we can't install the computer vision component because we don't own it, so they won't let us.

Our team is really small, there's only six of us on the actual RPA team. However, we work really hard with the business to get buy-in in every department. We're trying to roll out at least one automation in every single department. Our company's goals for the next year, I believe, every associate of the company is supposed to have proposed a task that they are doing, whether it's daily, monthly, yearly, whatever, that could be automated. Then our team will ingest that, prioritize that, and work through it. But, we're really trying really hard to get our whole company involved, and we're getting ready to kick off this campaign to try and get more attention to it and to try and get people using it. We want it to be more than just a buzzword. We want it to be something that everybody's talking about regularly, and using, and excited about.

When it comes to getting people interested, I think it's probably a combination of education and sharing the experience of those projects that we have rolled out. When people are really seeing that with the projects that we've rolled out, our close is shortening, they become interested. What we say is happening, or will happen when we're rolling these automations out, is happening. Getting that to be shared from process owner to their team, to the teams that they're working with, it acts like word of mouth for those that are affected. We don't like it to just all come from us, the technical team. We don't want to simply tell them that it's going to do something. We want others to talk about what it has done for them and suggest they should take advantage of that too.

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. We don't struggle with it.

I took the UiPath academy training, and I love it. We are looking at an unrelated tool right now, and we found no comparison between their training and the UiPath Academy. We were spoiled with UiPath Academy, and we didn't really realize how good that training really is.

The thing that I love about the developer training; the level one, level two, level three... level one really does walk you through it. It gives you, literally the walkthrough, so when you don't understand, you can go back, you can look at, and see exactly how to do it. But by the time you're in level three, it's not doing that anymore. The requirements are a little bit looser, you have to figure out how to interpret the words or the requirements, and it becomes more challenging, but I think that that's important, because, by the time that you're actually working real projects, it's not a walkthrough anymore. You have to figure it out on your own.

From the point that we purchased our UiPath license until we had our first robot was approximately three months. It did take us a little while, but we knew that we purchased our licenses before we were really ready to hit the ground running. We function out of such a small team, and we were still working with UiPath trying to figure out which partner we wanted to bring in for consultants because we wanted somebody with experience. We didn't want someone who just finished the training just run in and try, and I think we learned a lot working with that consultant.

We did work with a second consulting group, Machina Automation, and we loved working with them. They're great. They're just so supportive, and they really want to make sure things are right. It's never just sending them the requirements and pounding it out to get it into production. We work with them really deeply to try and make sure that they understand the process, we understand the requirements, they express their concerns to us, we express our concerns to them, and we work together. It's not like we just send them the documents and they send it back as a project. The whole way through we touch base with them every single morning. They're always asking what more they can do and how they can help. They ask if we're happy with what we received.

We do time card reviews, so the time that they spend with us we're actually able to go back and validate, based on that, what they've said they did, that indeed it is what they did. We had received some scrum and sprint training from them. We've had actual developer consultants, we've had mentoring hours for our developers. So we've had a lot from them, and they've been able to help us with everything. Anything we ask, they try to accommodate us. For example, we asked if they had any experience with Kibana. They did not but said that they would find somebody who does.

With respect to saving time, I don't actually track that because I am a developer, but I know that our goal for next year is twenty thousand hours. That's the big goal that we're working towards. With one of our processes, I think we're going to hit about thirteen thousand hours if we can just get that one process done. That's a statement review. We sent out tens of thousands of statements, so we'll be able to review every single one of those. This would be a huge saving in time.

I think right now we have about one hundred and thirty-six processes in production, and a lot of what we've done so far is in the finance section of the business. As such, a lot of those are only run on a quarterly, or monthly basis. We have some annual processes, and we have very few daily processes, but those daily processes add up over time.

In addition to the hours that we have saved, one of the big things we're working on is accuracy, control, and staff avoidance. Staff avoidance is the work that couldn't have been done otherwise because we would have had to hire someone to take on all of the work. So, we're able to do more than what our current staff is capable of doing. We add that into our time savings.

But, more than that, we really do focus on accuracy and timeliness. We're able to speed things up. We're able to ensure that things are exactly as expected. We spent a lot of time in the early stages of our planning, really trying to optimize our processes, so we get our original documentation, we take it, and our team works with the business to optimize that. After we get sign-off and we've optimized the manual process and got it documented and signed off, then we do a developer review and discuss ways that it can be made easier. Then we do a review for development and optimize it. Finally, once we get that signed off, we actually start our development.

We spend a lot of time on the front end of the process, making sure that everything is accurate and reliable, and we're going to be able to deliver faster as expected, and it's going to be able to handle all of these different errors or use cases. Following this process has worked well for us, so far.

I think the most valuable feature is being able to run processes in an unattended way where we can schedule them, and then have the report sent to the process owner's inbox in the morning. The is great for us, and we use it a lot. It saves the users a lot of time, and we're able to do a lot more for a user than they were ever able to do on their own.

I would like to see a biweekly scheduling option in Orchestrator. We've actually built into our automations a roundabout way to process every two weeks but it would be really nice to front end a biweekly schedule. Being in the financial services industry, we do have a lot of projects that run on weird schedules. We've kept some of our automations attended just because they're ad-hoc. They might need to re-run them. We don't want to have to wait for Orchestrator managers to kick those processes off. But, outside of that, there is no need for this one to be an attended robot. It's a perfect candidate for unattended automation, just the scheduling is the problem.

With respect to the stability, on a scale of one to five, I would rate this solution a five. We haven't ever had any issues with it.

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

When I first started at the company as an intern for my department, it was only myself and my boss, who's now our COE manager. The very first thing that we did was meet with all of the different functional departments of the company, and we explained to them what RPA is. We explained the types of processes that it can help take off your desk and asked for ideas from each department about what could be done to help them.

We took that, and we built this huge backlog of perhaps three hundred different items, prioritized them, and worked with others to explain that it was needed. At this point, we did PoCs with UiPath and Automation Anywhere.

I found the initial setup to be straightforward. They had me sit in on it and I don't work infrastructure, so there were some things that kind of went over my head. They did a lot of planning. After some help from UiPath, it went really fast.

UiPath helped us with the implementation. We worked with them to really figure out what our infrastructure needed to look like. 

We evaluated both Automation Anywhere and Blue Prism in addition to this solution. We ruled out Blue Prism pretty quickly. Our sister company uses Automation Anywhere, but we liked UiPath, primarily for the reason of our experience working with them and the sales team. To me, it was so much more than just working with the sales team, they're our friends now. We still talk to them and we have relationships with these people. We actually just ran into one of our developers for our PoC. It's a culture you want to be a part of.

In comparing with Automation Anywhere, one of the big reasons we went with UiPath was the support that we received. Any question we had was immediately answered. If they didn't know the answer, then they would search to find the right people in the company who did. I think that that's more valuable than just saying that they'll find us an answer. You always got the feeling that they were going to follow through, just by the conversations that we have had with them. I think that really sold us, a lot.

Also, watching the road maps for both companies at the time, initially it seemed like Automation Anywhere was ahead, and that UiPath was catching up. Then, when UiPath started releasing what they were going to be doing, as opposed to only what they were working on right now, we realized they were really going to be moving ahead. I think that kind of sold us too. Just watching what's on the road map, and how it fits in with what we see our company doing in the next few years, they aligned really well. I think that was the point where my boss really realized that it's going to be a good fit for us.

When I was in business school, they taught us that the things that users like the most are the things they didn't know they needed. I think UiPath does a great job of anticipating the users' needs, and they meet them before we knew that it was what we needed. I am excited about the next release.

I recently had a discussion with my father, who works for one of the energy companies in my state. He works at the IT level but on the infrastructure side. When I explained to him our savings in terms of hours that we have had since adopting RPA, he was very excited and is now heading their RPA initiative.

RPA is making a difference and it's really changing the way the workforce works.

My biggest advice for anybody considering this solution is to get their quality improvement, and Six Sigma teams involved because I think it makes a huge difference in terms of understanding processes. When you can get your processes understood, you can get people on board early, at every level.

I think it's really important to have proponents for automation, just in general. You want to have the automation mindset at every single level. Of course, it's important to have your C-level bought in, but it's important to have the people who are doing the work bought in too. If you don't get their buy-in, it's going to be much more difficult because a lot of the work that you're automating is at their levels. You're working with them on a day to day basis to understand their process, to understand all of the rules behind what they're doing. So, buy-in, and process understanding, that's just critical. You can't move fast without those two things.

We have nothing bad to say about UiPath. We have regular communication with them and all of the concerns we have are always addressed. They're addressed quickly and they're addressed well. They really listen to what the customers want.

I would rate this solution a ten out of ten.

The primary use case is invoicing and billing. The first thing that we used it for was some content migration from one video hosting provider to another. We later on moved to invoicing and billing, which included time sheets, management, and feeding data into our accounting system.

The features that we use the most for our use case include reading PDFs, email integration, and web and desktop automation talking to other desktop software.

We have generally found it easy to use, but we also develop some extensions. We are actually a software development shop, so we have developed extensions to the core UiPath platform. They have made it pretty easy to do that.

UiPath could use more OCR use cases to help with those features.

I would like to see higher end AI type features natively in UiPath. Some native integration over time would help.

We found it to be quite stable.

We have a relatively small use case. Most people have entered the market on a small scale. The maturity will come in, maybe over this year, as people start to scale up. 

I expect some issues will surface when it starts scaling up. However, that happens with any software. 

The eagerness of UiPath engineers and their salespeople to help us along the process has helped us align ourselves more with UiPath.

Support is good, helpful, and eager to help.

The UiPath Academy is great. It was one of the reasons which made us choose the tool, and align ourselves with it. It was easy to get the software, and train on it. If you're doing professional work, you don't want to have untrained people work on it. This will not lead to success.

As a software development shop, we value training quite a lot. They made it easy to help our developers come up to speed with the software and get certified.

The initial setup is quite easy. We have worked with some other RPA tools, but they took us quite awhile to get setup. With UiPath, it was relatively easier to get started.

We have seen ROI by it saving some hours for us. We are a small company. We use the tool mostly because we want to learn about the software. We also save some hours, but we do it to learn and help other customers who are doing it at much higher volumes. The savings for us is relatively lesser than the savings for a larger customer.

ROI is a bit tricky. Customers need to implement simpler use cases: Get ROI from the tool, learn it, and re-implement it. This is just the nature of how RPA works. I see a lot of opportunities for it.

When customers start scaling up their use of RPA and have learnt how to use it, that is when the real ROI will start trickling in. When you start off, it will take some effort to get it right. Once you developed some maturity with the process, and you're scaling up a lot of use cases, and you have one bot doing a lot of different things and being able to share a lot of processes with a few bots, that's when you will start seeing good ROI.

This tool gives opportunities for people to be productive in other areas, which is hard to measure sometimes. The first step is to get them there, then determine where you can go from there. ROI is a very long term thing. The product lets people focus their skills on what they are good at, which is a type of ROI.

UiPath made it easy to learn their software. When we looked at a variety of RPA tools initially, UiPath was the easiest to get started with. It has good Academy content and an open platform, which is easy to download and start using (the Community Edition).

We have been looking at other RPA solutions, but we like UiPath quite a lot.

When it comes to finance and HR services the product has great potential. Our company is big, so there are a lot of opportunities.

We are doing automation internally for financial processes.

Externally, for our customers, we are developing a shared service center. This is not restrained to any one specific area, like HR or finance. Anything that is manually or taking a lot of human effort, we try to automate (by selling it to our customers).

The Unattended Robots are good and handy. If you have the proper team and environment available, especially a team who is experienced and knows how to develop with a sense of excellence, then a lot of tasks can be done outside office hours. Then, the next day, teams can come in and have the information that they need readily available.

UiPath needs to improve Orchestrator and its back office licenses. For example, three or four people logging in on a license should be able to get in, but they can't, even though its Unattended.

Why can't we just increase the capacity of the VDIs, so we can use capacity that is there?

Stability depends on the type of structure that you are putting in place. I think it is important that you run 16GB, with not more than three or four processors in parallel.

If I need something, I go to my account managers, who are nice people. They respond back quickly and get back with a lot good options, which I like. 

My development team does connect with the technical teams. The feedback, which I receive from them, is very good. There have been instances, which we have highlighted and identified something, then the UiPath technical team accepted it, said whether they would fix it in the next release, then fixed it if needed.

The UiPath Academy is fantastic and amazing. I'm a big promoter of it in my discussions with customers.

When it comes to Studio, it is an easy solution to install. Anyone can go download and install it. Though, I'm not sure if just any company can install it, because you need to have permissions from IT in order to install it on your computer.

When it comes to Orchestrator, you need an approved structure from IT security. There are associated firewalls that have to be installed with your IT partner's help. Then, it is quite straightforward.

UiPath helped us with the installation.

It is not easy to see ROI quickly. 

It is not a cheap solution. There is an annual licensing cost for all the components.

When it comes to back office licenses, why can't we have parallel processors running on one back office license? I understand the commercial aspect, but when you have servers and a node locked license, you should be able to use the license from different instances.

UiPath is quite a customer-centric company.

Most of the time, I am a developer. I also have to develop some best practices, but a lot of the time, I'm working on the application and creating Unattended Robots. We have a large amount of old school manual processes which we need to automate, because we have a lot of full-time employees just doing boring stuff. 

I started last year, so I am a bit fresh in the organization. We have two people: One who analyzes and other develops.

I am using version 2018.4, which I find easy to use. We can see some major changes with each version. The IT department sort of hates that I come by every quarter of a year and want an upgrade, but it is very much worth it. There is a lot of stuff happening out there, and it's dangerous to be left behind by a few versions. 

We have a few people who are very happy to be relieved of their (almost) full-time job of processing customer applications, then processing those applications further along into the company and having that be their full time job. Now, these employees are able to do some more enlightening stuff.

The automation technology is mainly in the financial involvement. We also supply a lot of the power for users. We have a lot of documents which have to be signed and processed, and in those areas, it's nice to have automation and easy to see the benefits.

The seamless integration with programming underneath, so if you choose to, you can get a bit technical with stuff. If there is something missing, you can make it yourself. 

The increasing amount of possibilities in Orchestrator to control robots and schedule them, with the possibly of a dynamic schedule in the future. In addition, there is API access to Orchestrator.

I've seen the roadmap. It looks like some of my wishes are in there, such as the debugging of the last X amount of savings before the robot fails. 

I would also like more script access to the flow of activity, so we can try to see a text version of what we have in the user interface.

Most of the time, the product boils down to making something that works by itself. 

I haven't encountered any real issues with the stability of the product. It is hard to evaluate since it works through so many systems.

We haven't had that many scalability questions arise yet, because we are still in the process of getting people to adopt this new technology. I have looked at the features, and it looks promising.

We have a plan for licensed upgrades, which is a straightforward, easy procedure. This is based on our knowledge from migrations of earlier versions.

We started out by going through the few basic certifications which were in the UiPath Academy a year ago, though there are more now. Even though my coworker is not a developer, he just wanted to have insight into how you use software, so we both did it. 

The UiPath Academy was very good. It tries to help and provides a sort of education not from where somebody is attempting to sell you something. While you are sold product, you push yourself to pass the courses to get to the juicy stuff, and it is on your own accord.

This was a new product for the company. Leadership though this was a good place to start.

The initial setup was complex, which was done by the consultants. After that, we adapted the product a bit, and it has been pretty easy.

The initial setup for our virtual environment was straightforward, as was the installation with it. Afterwards, we were up and running with our virtual machines.

We originally used a consulting company, Deloitte, but then decided that we wanted the knowledge to be in-house.

It has helped eliminate human error. Data quality is a concern, and it helps to alleviate some of our data quality issues.

It has saved the company time.

We use the performance benefits of it to make a case for future hiring of people, so I have great expectations from it. I would rate the current ROI and performance benefits as an eight out of ten.

I heard that they also evaluated Blue Prism. The leadership went with UiPath because it had more transparency, had a better cost, and was more risk-free. They decided to give UiPath a shot before deciding on a long-term solution.

Get buy-in from your leadership early on, because it's very hard to get stuff done without it.

We are only using Unattended Robots at the moment. However, we are very excited about Attended Robots getting a foothold. It is something that we want to investigate more, since Attended Robots are feasible in our organization.

We are using UiPath to automate our cache application and to download documents to help our finance team.

We're saving a lot of time for all our associates in our company. As far as metrics go, each project that we complete is saving us on the order of 40 hours a month, so it's saving a lot of time.

It also allows our associates to do things that are more interesting, instead of having so much repetition in their jobs.

In addition, we've seen performance benefits because it removes the human error portion of running a process. It makes it easier for the owners of the process because they don't have to worry if they've made a mistake. They also don't have to look something up because the RPA would have everything for them, ready to go. Performance has improved a lot, as well.

I like that it's very flexible, so we can design our automation the way we need to. Some other RPA tools don't really allow us to use all the applications that for our team.

It's also very easy to use. There is a lot of drag-and-drop. There are many different ways to complete a solution. For example, if we're trying to manipulate Excel data, sometimes one solution will be really slow and ineffective, but UiPath gives us the ability to find multiple ways to do the same thing and complete the same solution much more quickly.

There are a lot of solutions in UiPath where we have to know some programming languages. I'd like to cut some of that out, with features that perform those tasks without having to know programming languages. I work a lot with my team members who don't really know programming that well, and I have to walk them through how to do different coding things to effectively develop their RPA.

It can be complicated to get a stable solution, but once you're over that learning curve, it's very easy. At first, it's complicated to figure out how to get a stable solution using UiPath.

We're constantly having to use our solutions on multiple servers and expand to multiple teams, so we need to work a lot with IT. They support the servers and make sure the servers are a mirror of each other. If they're not a mirror, then it can be difficult using UiPath. But once they're a mirror, it's very simple to finish a solution and move it onto a different server or to a different machine, where someone else is using UiPath.

From my experience, technical support is very fast in responding. I will submit a ticket and, by the next day, they're already working the ticket and helping to find a solution, so it's been a very good experience.

We were using another tool before UiPath. The one we were using was Kofax Kapow and it uses a different style. It was very restrictive and they had to update a lot of features for us. There was a large learning curve, as well. When we started using UiPath, I felt the learning curve was smaller and we could get into it a lot easier. It was less restrictive and more versatile in what we could do with it.

When we first started learning UiPath, they gave me the project to install Orchestrator and Studio into our server environments, so that was another learning curve for me because initially, the installation of UiPath was very difficult to figure out. But they've upgraded it since then and it's much easier now. We've now sent that function to our IT teams to do.

I believe Blue Prism was also under consideration, but I was not part of that decision.

Use the forums and surround yourself with people who are technical. Use UiPath Support a lot because, if you don't have a programming background, it can be difficult to figure out how to organize your development in a stable way. If it's not stable, it's going to give you a lot of headaches trying to constantly maintain it.

For UiPath, we have about three different teams of developers in my department. Each team supports a different group in that department and each team consists of about three developers. In terms of maintenance, we're maintaining our jobs. Once we deploy a solution, we're currently maintaining it ourselves. Whoever develops the project makes sure that it's working, but we're also looking at other solutions for maintenance where we would give it to another team. All they would do is make sure the robots are running.

We've used UiPath RPA Academy training and it's a very good tool to figure out how well you know UiPath. I wouldn't use it as something to learn the tool, because there is a lot more in UiPath than is in Academy. But I like Academy because it confirms what I've learned is the way it's supposed to work. It gives you a good basic foundation.

I would rate UiPath as a ten out of ten. I think it's the best RPA tool out there, although I have not used the other one that people talk about, which is Blue Prism. From what I can tell, they're about equal, but my experience is with UiPath and I like it a lot.

I use UiPath to automate repetitive tasks within our organization. It helps us deploy processes without human intervention for some tasks.

UiPath has helped my organization, especially in the banking industry, by automating processes, reducing manual work, and saving costs. These improvements enhance process efficiency, reduce stress, and improve end-to-end efficiency.

The Studio is a valuable feature because it allows us to automate processes independently. It enables us to configure and manage everything through a web application called Orchestrator, which is particularly helpful for large organizations.

The documentation related to new releases needs improvement. It should provide a clear understanding of what was present in the old release, what's new, and how it affects users.

I have been using UiPath for around three years.

UiPath's stability is satisfactory. No product offers one hundred percent accuracy, but UiPath performs well overall.

The solution is very scalable. I would rate it eight out of ten for scalability.

Technical support comes primarily from engaging in UiPath's forum, where people share insights. I find the community engagement to be more helpful than direct product support.

Neutral

The initial setup was straightforward. Deployment doesn't take much time once the development and testing phases are completed.

The implementation of UiPath saves a significant amount of money and reduces manual errors, improving overall performance.

The pricing and licensing of UiPath are expensive. I rate it ten out of ten in terms of expense.

I recommend using this automation tool based on the specific needs of the industry or organization.

I'd rate the solution seven out of ten.

I have worked on multiple use cases with UiPath dealing with SAP, SharePoint, or a web application. We had to extract the data and do some automation of data processing. We were taking data from one environment, such as from an Excel sheet, and processing it. These were the use cases for which we used UiPath extensively.

In addition to app integration, there were use cases related to various frameworks such as REframework and State Machines. We used the REframework at the enterprise level to be able to handle exceptions and bot failures and make automation healthy, robust, and steady.

We have also done automation for a healthcare department for claim processing.

UiPath saves the execution time of processes running in the production. If a process was taking three to four hours previously, with UiPath automation, it can be completed within an hour with better exception handling capability and less dependency. It saves 50% time.

UiPath is capable of handling the complexities involved in taking data from different environments. It is also capable of exception handling. If any application has limited functionality, we can use UiPath for automation with that particular application. With advanced selectors and linked queries, we can get the data from the application or interact with the application.

UiPath Document Understanding has helped to reduce the data entry work and physical copies of documents.

UiPath enables us to implement end-to-end automation. For every organization, it is very important that automation is robust enough.

UiPath can help minimize your on-premises footprint. It depends on whether you plan to deploy your automation on the cloud or on-prem. On-prem has various challenges and restrictions, but it also has benefits.

UiPath speeds up digital transformation without requiring expensive or complex application upgrades, or IT application support. App integrations are advanced and robust. It is plug-and-play. You can integrate with Excel, Outlook, SharePoint, SAP, and various databases. There are pre-loaded activities. You can integrate with GitLab or GitHub. It has inbuilt activities for enterprise-level applications.

UiPath reduces human errors, but it also depends upon the process. It depends on how much interaction is required and what exception rates are there. When everything has been identified, it can reduce errors by more than 70%.

The first feature that I like is the exception-handling capability. The second feature is the REframework provided by them, and the third feature would be the Orchestrator functions. There is also the feasibility provided to monitor the ports and deploy the code. There is monitoring, retrieving, and all those things. We can use the web or mobile application. These are the key features of UiPath.

For handling complex scenarios, REframework is good. It has good exception handling and in-built mechanisms.

The certification can be made more affordable.

In terms of features, we get regular updates, and AI has recently been integrated. As of now, I do not have an area of improvement. They have already improved the functionality of Orchestrator. As compared to two or three years ago, Orchestrator now offers different functionalities and services. There is a difference, and it has improved.

I have been using UiPath for more than three years.

It is stable. Our organization has licenses because we cannot upgrade the application in sync with the Community version. The enterprise has to stick to one version for a certain period or whatever tenure has been mentioned in the license. The Community version is the playground for UiPath. They upgrade it, and all the beta version updates are there. They come to know how things are going and what are the responses and challenges.

It is scalable. It is used in multiple departments. The size of the organizations that use UiPath varies. They could be MNCs or startups.

Their support is good. After procuring the licenses, when there is an issue, there is a dedicated support team. They respond well.

The UiPath Community is vast. It provides an opportunity to get help from others. They provide good support, and the MVPs are actively engaged in responding to the queries that people are posting when facing any challenge. We can find relevant information by searching with keywords. It is good.

UiPath Academy has been useful in learning about new topics and new versions.

Neutral

I am quite new to Automation Anywhere, but a better exception-handling mechanism and the ability to interact with various applications make UiPath more unique. The drag-and-drop interface is attractive to people who are not very technical. The user experience is more intuitive.

We have on-premises and cloud deployments. The deployment part takes about a week because we have to prepare the production environment. A week is good enough for the deployment.

The number of people involved in the deployment varies. Support teams are there. Developers are also there. There are also people from the change management team.

Like any other software, it requires maintenance.

I would recommend UiPath to others. Overall, I would rate UiPath a nine out of ten. It is robust and scalable, but there is always scope for improvement.

I have done the certification in Microsoft Certified Solution Associate (MCSA) and Microsoft Azure Administration. I look after the actual environment site where we can run the bots. We watch the environment's behavior, and we operate the Orchestrator, which is connected to the AI system. We run different types of processes through Orchestrator, and I am the administrator of Orchestrator. I give the rights and assign roles to the users. 

UiPath has been performing very well. It is very easy to learn and understand. We are going to move the most work done by employees to the bots because the bots get work done in minutes instead of hours. An eight-hour job can be done in three to four hours. 

We plan to bring more bots for efficiency. We would like to add more bots and reduce the time taken for various tasks.

We can design bots in a static or dynamic way. We can use the dynamic way to perform the actions in any environment or platform.

UiPath has freed up employee time. The time saved depends on the complexity of the process.

UiPath is easy to work with and understand. If anything is confusing, we just send our questions, and we get the answer as soon as possible. Designing a process with email, Excel, and any other application can take more than 15 or 20 days.

UiPath saves costs. By using bots, we can save the costs of services provided by humans, but I do not have the metrics. We have many departments, such as finance and global compliance management, and it is hard to know how much cost it has saved.

Orchestrator and features such as Queues Triggers are helpful in monitoring the ports and looking after the performance.

I have done the UiPath Academy course to learn how to manage the environment and Orchestrator. I was able to learn many things through UiPath Academy, and I was able to work on Orchestrator myself. The benefit of UiPath Academy is that it is accessible from everywhere. You can continue watching the videos at home or in the office. The explanation, presentation, and instructors are very good. You do not have to watch the videos again and again. You can just watch it once, and you understand everything.

For UiPath Orchestrator and Studio, if I want to watch the performance of my machines at a specific time or time range, there is no option for that. There are options for one day or week, but there is no option to specify a date such as from Nov 1 to Nov 3. This option should be there for queues and monitoring.

It has been more than one year since I have been using UiPath.

I would rate it an eight out of ten in terms of stability.

It is a scalable solution. I would rate it a nine out of ten in terms of scalability.

We do not need much support to use UiPath. We are not getting many errors.

Positive

I have not worked with any other similar solution. I have only worked with UiPath Studio and Orchestrator.

We have worked on the Python scripts to design the bots, but it was complicated. We had to write more and more scripts and make them efficient. It was very hard. With UiPath, we found a very good option to perform the activities in an easy way. We do not have to code much. We can just drag and drop things and have a solution. 

It is mostly straightforward. We just need to call IT to install UiPath. I give the license via a machine key.

We have it on-premises. We have not connected it to the cloud or third party. 

In terms of maintenance, there are certain packages that we have to download for running the activities. For example, if I am using Python with UiPath Studio, I need to download a specific library.

We implemented it in-house. For deployment, there are two or three members of the team who work with UiPath and provide the infrastructure, and then we have about 25 developers. We have a development team and an operations team.

The development team develops the processes and the operation department runs those processes via triggers or manually. They are usually run on the Windows environment. There are multiple bots working at the same time, and we have the monitoring tool by UiPath, and we are also working via Kibana. Kibana works with Elasticsearch. We have all the logs and bots' performance metrics. We can view it all with one dashboard in Kibana.

RPA is the future. Every bank and organization is looking for bots to perform their jobs because bots are more efficient than humans.

It is an efficient and easy-to-use tool. If needed, you can get a lot of support through UiPath forums and other resources on the web.

We have not used the AI functionality in our automation program, but we plan to use it.

Overall, I would rate UiPath a nine out of ten.