What is our primary use case?
We currently have 150 bots in production. It is used the most where there are repetitive, cumbersome tasks. Where we do need to have somewhat of a decision made, we put it into a decision tree. This is our primary use case.
We are looking into other use cases, such as:
- How do we use it as a platform for pretotyping?
- How do we use it as a platform to drive forward machine learning and artificial intelligence usage in our company?
How has it helped my organization?
We have automated assignments where we previously used employees. The outcome of this has been a greater customer experience achievement. We simply are solving tasks faster, and at the same time, we have been scaling down employees.
We have started to do tasks more often and faster than we have ever done them before. For instance, some of the things in finance, we only did that once per quarter. Now, we have started doing them once a week. This gives us greater insight into those areas.
The most important outcome here is the amount of insight which you receive when you put power to a process. It gives you the insight that you wouldn't have had when you had 20 employees working. With two bots doing the work, you suddenly get a data foundation that you didn't have before. Then, you can build upon the bots, instead of thinking you know what is happening.
What is most valuable?
The platform is object-orientated. You can create and reuse objects, which is a great feature.
UiPath has decided that people who are great at what they do can be invited into the platform and utilize services on the platform. This is another great feature, and one of the reasons that we initially chose the product as our platform.
The solution is easy to use. When you put it together with the UiPath Academy, it's easy to get it going and understand. The drag and drop feature makes it simple and easy to use. The UiPath Academy is great and helpful.
What needs improvement?
We tried utilizing the virtual environment, but we had some issues in that area. It's one of the areas that we haven't revisited over the last half year because our volume is that high for us. Thus, it is one of those things that we have sort of left on the side for now, but I do hear there is some great stuff coming with it.
What do I think about the stability of the solution?
We haven't had instability issues.
What do I think about the scalability of the solution?
How are customer service and technical support?
The customer and technical support are great. We have received fast, sufficient responses. There is easy access.
Which solution did I use previously and why did I switch?
We did not have a previous RPA solution.
We were in a place where we needed to do something differently. At the time, RPA was something different. So, we needed to sort of examine, "Could this help us?"
How was the initial setup?
The initial setup was straightforward.
What was our ROI?
We saw ROI in eight or nine weeks, so it was fairly fast. We have seen a lot of performance benefits, which I would rate as a ten out of ten.
The solution has helped to eliminate many human errors.
What's my experience with pricing, setup cost, and licensing?
Our licensing costs are roughly 1.1 million Danish krones a year.
We see some elements in the license model that we're trying to figure out how to utilize. There have been some elements in the license model where UiPath has helped us solve them commercially, and having a license model which is more focused on scalability would be a great feature.
If UiPath really wants to put Attended Robots out to everyone, there will be a cost issue. We have some that we are testing now and what their effect will be. However, these are the robots where the license model needs to change before we go full throttle in that direction.
Which other solutions did I evaluate?
We also looked at Blue Prism and Automation Anywhere. We selected UiPath based on its object-oriented approach.
There is something off in UiPath's licensing model. Their competitors have started targeting us now because they know that we have a lot of bots. They have different types of licensing models, and say, "Because you are having so many jobs with so many job bots, you can save money on the platform by using us instead."
What other advice do I have?
Play with it and have a playful nature. Acknowledge that you don't know what you're doing with it, then just acknowledge that you're going to make mistakes. The only difference between being good or great at this solution is your ability to learn from your mistakes, because you will be making mistakes. Also, you will be overpromising when working with this solution.
For automation technology, in general, the system landscape is quite wide. We are just starting to put RPA on the shelf for automation. We are pushing a machine-first approach. RPA is the sort of tool on the shelf now helping us become a more efficient customer-oriented company. It is a tool in the landscape with plenty of existing tools, but this is the one that is the most easily accessible for the business people.
We built ourselves some automated documentation, and it was fairly easy to copy. One of the things that people start doing is documenting what they're doing in an organization and updating the documents, then freely sharing them. We would like some sort of automated documentation, as this would be helpful.
Start Your UiPath Free Trial
Accelerate your digital transformation now with free access to the UiPath Platform