Blue Prism Review

Easy to use and has helped us to automate the majority of work in some areas


What is our primary use case?

Our primary use for this solution is to automate and run our mundane operational processes.

How has it helped my organization?

This solution has helped us become more efficient, as we have been able to automate certain processes, up to 85% of the work in some claims processing areas. We've been able to use it to very successfully transform data from one system to another. We have also used it for underwriting new client take-ons.

What is most valuable?

The most valuable feature is the design studio and its ease of use. The security and control room features are also very good.

What needs improvement?

I would like to see it better integrated with, or layered over, Java-based systems.

A feature that I would like to see in the next release is the ability to easily call on the robots to fulfill part of the process, and be run by the users in the business, where the robot can simply be activated rather than running mass processes from a control room. Essentially, I think that keeping the human in the loop is important. Blue Prism does have some vendors that partner to accomplish this, but it would be nice to have it built-in, rather than have a separate vendor with a separate license contract.

For how long have I used the solution?

Between one and two years.

What do I think about the stability of the solution?

We don't have problems with stability. It is one's own IT infrastructure that lets you down, whether it is networking or otherwise. The system itself hasn't been a problem.

What do I think about the scalability of the solution?

We're only in the process of scaling so it is difficult to say. One of the things that the developers have said is that it's quite slow, and quite cumbersome when layered over Java-based solutions. Whether it is scalable in that space, or not, is to be determined.

We have fifteen robots running.

How are customer service and technical support?

We have had to contact technical support from time to time, and they are responsive. We've always received feedback from them. Typically, the only time that we've needed them is when our own IT support has had problems in the Blue Prism space. Sometimes, after we've contacted them, they pointed us in the right direction and actually found that the problem was on our end. These are some of the types of problems that they have helped us to solve.

If you previously used a different solution, which one did you use and why did you switch?

We did not use another solution prior to this one.

How was the initial setup?

The initial setup was relatively straightforward. The system itself is not overly complex. Rather, it's more of how you get your own internal IT infrastructure geared to be able to handle the new technology.

Deployment can take between four and six weeks per process.

Our implementation strategy has been to first focus on those processes that are going to deliver the greatest return on investment to ourselves and our clients. Typically, it's a small team that is supported by a vendor. Over time, they take over the development of the robots and they manage the control room.

The number of staff required for deployment and maintenance depends on the number of robots that you have running. Our entire team is six people, including business analysts, an engineer, a control room operator, and two developers. One of the developers is a senior developer who is able to validate and sign off on what is developed.

What about the implementation team?

We used a consultant for the deployment.

Which other solutions did I evaluate?

We did not evaluate other solutions. We chose this one based on recommendations from the consultants that we had.

What other advice do I have?

For anybody who is implementing this solution, it is important that you do not implement a process that is inherently flawed. Especially for more complex processes, you have to figure out how to solve those and re-engineer them. You want to enhance the processes.

Secondly, ensure that your design team is allowed to complete the design and move onto the next process. You do not want to have them repeatedly called back to enhance the process, because that slows down your rollout strategy.

You need to get buy-in from the business around what you're going to automate, and how you're going to do it. That is how you're going to leverage it going forward. If you don't have that then you can automate and put bots out there, but if the business doesn't support them or doesn't adopt them as co-workers then you're going to be battling against scaling. Anybody who sets out on this journey should be looking to use them on a large scale, and not just as a point solution.

I have not used other solutions so it is difficult to compare. However, in terms of support and the ability for us to start using the solution, it was quite easy. 

I would rate this solution an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email