UiPath Platform Reviews

We are using the UiPath platform for back-office end-to-end process automation, combined with OCR and cognitive services.

In our projects, we provide our customers with a x2 to x6 efficiency improvement, error decrease, and SLA improvement.

• Core activities
• Excel activities
• All the cognitive activities
• Python and customer activities
• UiPath Go! (good platform for the community for knowledge sharing)
• UiPath Academy (best courses apart from other vendors).

• Provide a robot as a service model (subscription for the platform services) for partners to provide more chances to SMB to compete enterprises.
• More cognitive services from Google, AWS, Microsoft, integrated into the platform provide wider capabilities for developers and service providers.

We use UiPath to test automation for asset management, wherein we found it can help us to reduce the time and increase data accuracy.

We have many manual processes internally, so we decided to start evaluating UiPath for automation. We know that automation will help us to be more efficient and accurate.

Browser automation and schedule jobs which are the main activities that require manual work or visual validations by the users.

When using UiPath Studio sometimes I felt lost when trying to locate specific activities, so probably will be a good idea to improve the icons beside the activities, so I can remember easily.

Our primary use case of this solution is to automate a process that includes and prints out files that contain financial details of an insurance company into an Excel and apply some formulas on them.

UiPath had a great effect on the FTEs in my company since some of the most crucial tasks that were repetitive at the same time got automated.

The seamless development experience about the tool was great, and also the big number of packages and the community behind that backs everything.

Some more features for the newly developed mobile version would have a great effect on the future of the product.

My primary use case is for creating custom-specific products based on the customer's needs. The requirements can be received from the customer on emails and then based on it the order can be created. This reduces time, ensuring no human error and on time delivery. 

The total time taken to enter this in the system is less compared to the manual process which is indeed error-prone. This also removes the process of reviewing the order for correctness as the straight-through processing is enhanced. By making this scale on all the other locations and geographies, lots of time and effort can be saved. This also enhances the reputation of the services and organization. 

In addition to this, the confidence created by the successful implementation is a real eye-opener as the big step is taken with great success.

UiPath has taken automation to a pinnacle of excellence by mixing technology, attention to detail, and keen observation. The way UiPath has revolutionized automation with excellent coverage, user-friendliness is helping companies focus on their core areas. Employees can now focus on real problems than spend time on routine jobs.

Feature-rich options to help easy implementation: It's flexible, scalable, and easy to implement. The time taken to create the bot is less. 

The easy drag-and-drop options make it easy to solve the challenges within a short time frame. Another important aspect is the framework and other useful tools and templates available have that makes it easy to document the audit trail and also standardization.

More support for certification is needed to attract professionals. The certification process could be made more interesting.

I find the most valuable features are automation and RPA.

This solution needs improvement, especially in terms of continuing the process that is left in case of any kind of disaster that happens to the trimmers. If there is a state that can be maintained to removing the machines to another location and continue from there, it would be helpful. Right now, this is lacking.

I have not had issues with the stability of the product.

I have not had issues with the scalability of the product.

The implementation is simple.

It is a good product. I think if it could stream, rather than being stateless, it would be appreciated.

I did many small projects in UiPath like PDF extraction, website automation, and translated the data into different languages.

We are able to extract data from the PDF and website, then translate the data into different languages.

Recording and scraping which directly extracts the data from the website and saves it into the excel sheet.

We are not able to extract the data from the same type of PDF which is bulky in number, and scrapping is not so good.

Our platform, it's called Cevitr. It's a best-of-breed platform through which we offer automation as a service. In our world, we have two kinds of robots. Our robots have a personality. Jo is our robot. Jo is a gender-neutral term that can be John, that can be Josephine, that can be Joe. We have two variance of Jo. Simple Jo, which does the normal routine repetitive mundane stuff, and Smart Jo, which is more focused with the AI and cognitive capability. Both of these are part of our co-platform offering, Cevitr Jo.

We offer UIPath as one of our core technologies on a platform, through which we offer automation as a service. There are multiple use cases for our end customers on UiPath. It's one of our core offerings as a core product on a platform. I think UiPath as a production, it's obviously one of the leaders in the RPA space and there are quite a few technology features outside which are quite good for us. But I would say one of the key differentiators of the product itself is the community enablement of the platform. If you talk about how they enable write from their training, it is being opened for everybody to be able to enhance their skills to the new UiPath Go!, where people can come and collaborate and create and put compliments for others to share. The whole community enablement of UiPath is a fantastic way for customers to benefit and move forward.

As a product, the stability that it brings in, the volume of transactions it's able to handle, and some of the leading feature functionality in terms of AI and cognitive capability. It's absolutely brilliant.

We are focused more on the unattended space. That's where our predominant offering is. Though in the newer version of UiPath, there are new features coming up in the attended space, which we might have a look at. From a cost point-of-view, since it's a platform offering, we are able to offer it as a service so it's not a price per robot that we typically charge our customers. It's a slightly different model.

I think from a feature functionality point of view, it's an evolving product. There will be more features added. Every product is going up. I think from a UiPath perspective, it is evolving as we speak. But I think where it could really improve is being able to create a development platform that is easier to use. Today, as an end user, if I have X number of developers, each of them have to have a studio environment to be able to use. Typically, that's not a license model. But if that is more easily accessible to the development teams. Without constraints, it would be easier for us to use this platform more widely among our customers. So, I think, from a licensing point of view, studio environment should be more easily accessible. But other than that, from a feature functionality point of view, I think it's pretty comprehensive.

We've been quite pleased with the stability of UiPath across platforms and even things like Citrix. There, we have found UiPath to be quite good so far.

It has been able to handle certain volumes with ease. We believe that it is one of the products, which is  quite scalable. The tech support so far has been good. But like I mentioned earlier, what we find is the community. It's brilliant. 

If there is a standard problem that we have, we probably aren't in the first people in the world to have faced it so we can very well go to the community forums and ask questions and get them clarified. 

It's pretty straightforward, like most of these products. RPA is a technology. It's been around for a few years so it's very easy to deploy to end customers. Even the installation for usage isn't that technically complex, but we had to have had to cross certain boundaries to make it extremely robust on the platform. We have done those investments and made it seamless as possible.

ROI is for our end customers. With the technology like this powering our platform, we're pretty confident that we can give quite a good reasonable ROI to our customers.

We have a best-of-breed platform. It has other products in it, as well. UiPath is one of our key products and platform. What we want to give our customers is a comprehensive portfolio of end-to-end capability. This is across simple RPA to more robust AI-based process automation scenarios. To be able to do that, we have to have a best-of-breed capability. You know, we will be plugging in the right components. UIPath is a core component of that.

We are early in the journey with UiPath, We've had it for a few months, and I would say on our basis, I would definitely give it an eight. We are very happy with the product so far and we hope to do much more with it.

I work in finance functions, so typically implementing it within our finance accounting hub that we have out in Manila when most of our processes are stabilized and globalized experts. So, it's a very good fit to have our processes automated out in Manila.

We are in the early stages of implementing our robots, but at this stage, you already see things like our customer satisfaction, so we're supporting your finest teams, so they are already getting benefiting it, and very much tedious tasks that sitting with the team, they're actually find they don't need to do the tedious tasks. 

Funny enough, that out in the Philippines, they are actually welcoming robotics because it creates capacity for them in order to bring more work into our accounting hub, so that would be where I can see a real benefit in our organization already. 

I think we very much focus on traditional development opportunities, so API to API connectivity and those type of things are very much the way that we're doing things. We have development teams out around the world that develop, and I specifically work with financial functions and develop our finance systems, typically more of a traditional development focus rather than using robotics opportunities, but we are starting to see robotics becoming a bit more prominent. People are more interested in it, and people are starting to engage a bit more with the robotic side of things. I think the benefit of using robots is actually becoming a bit more visible within the organization.

We are making use of attended bots. Unattended bots are of course a huge benefit. I can see the future if I use the 80/20 rule; I can see probably 80% of our bots will be unattended when we will implement 20% into attended bots for our organization at the moment. I don't know how that will look like if we say everybody in organization using bots, then of course attended bots will become very prominent, but where we are right now, I can see unattended bots will become very attractive for us right now, so probably seeing the bigger opportunities at the moment, and those big opportunities, unattended bots will be well suited for.

It is difficult to get your head around attended and unattended bots, but once you get to understand the differences, I think yeah. I can see benefits and pros and cons on both sides, but typically where we are now, we use attended bots. I can see us moving with our big opportunities into unattended bots, and where the future takes, I don't know. I'll let you know then.

I think it's the ease of use for the developer, so we can actually make use of people within subject matter experts rather than having fully fledged developers, so that's one of the main features. And, I think, based on that, it is actually the speed in which we can deliver some of these automations, so the delivery and the build of the box is actually much quicker than your conventional development, so those will be my two top points at this stage.

We've created a bot within our collections team. We are doing a reconciliation, and since implementing the bot, which was at the beginning of this year, we hadn't needed any changes onto the bot. 

Scalability very much so, so exactly that reconciliation bot we were able to apply to different reconciliations within our collections team, and they fall. Yes, it's very much scalable as well, so we are running four different bots at this stage for our collections reconciliation process.

I think we will probably make use of the community more, so asking questions within the community forum. I've not really had to engage with technical support directly apart from our sales person that we could ask questions from, etc., but generally, the technical questions are more posted onto the discussion forum and answers being given and taken from there.

Our proof of concept was done using PwC, and they've helped us build our proof of concept. The reason for that is they've delivered a piece of work where we wanted to see whether this has already been delivering a piece of work where this really fell into, so we engage with them often to help us deliver a proof of concept, and that was very successful, and of course that helped us roll up more into the business and taking a little bit more on internally rather than continuous support from PwC.

Coming from a person that doesn't' know much of robotics or anything of that, as it's a new technology. I think it was quite difficult to get your head around that first. Setting it up, installing the software's very easy on occasion, but getting a grasp and understanding of the difference between the studio and the difference between the robots in that regard was quite difficult to get your head around not only for us who's been setting up the center of excellence but also for explaining to the business the different components and then just understanding what the different components does, and I think it's maybe more around terminology. We're building a bot that's running on a bot, but the building of the bot is in studio.

It's a very easy concept, but it makes it difficult for the business to understand what you're talking about and what we're working in and what actually runs the bot and those type of things.

We are starting to see a return on investment. I won't be able to answer that right now, probably only be able to answer once I start analyzing it, but we are starting to see a return on investment. I think it will probably take a good few months before I can analyze how well we're doing. I think fairly soon we see a return on investment.

Does it fit in with the business, what they expect? I don't know. That's a given that the solution absolutely does, so if I come back to our original example of the reconciliation bot within our collections area. I think there's almost 100% human errors reduced. The bot doesn't make any errors, so we've seen it running smoothly for the last since the beginning of the year, so last nine, 10, 11 months.

Citrix environments are quite difficult. It takes more time to develop the bot itself. Accuracy's maybe a bit of an issue there, so from a Citrix type of environment, I'd probably try to avoid it from my side, but it's just because I don't like to work with the images. I'd rather work directly within hotkeys or whatever.

I think I would rate the product probably at about an eight, which is coming down to the usability. It's really easy to use. It is easy to implement and roll out getting people involved. I think there is drawbacks in terms of the understanding of where the process is, so it's maybe on our side, understanding the process and which processes are suitable for the bot and what the bot will be able to do then with those. I think taking a subject matter expert and giving them the expertise to build bots limits your ability to understand the full capacity of the product. I think there's a lot of things changing within the product very quickly and to keep up with all of the enhancements that you're making makes it a little bit difficult, but over all, it is very good, and if you apply correctly to your processes, you will definitely seen an improvement in your process and return on your investment.