Blue Prism Reviews

We are using Blue Prism to automate any of your manual tasks, that are related to desktop, or web-based, email, and Excel. Any kind of automation for that matter.

Also, for any two handled records that have been created with many items and have been automated, we would use Blue Prism to manage them.

The initial setup and deployment could be simplified.

The stability could be improved.

They could add more AI-related technology. 

With their free version, they should provide some sort of community link where you can learn for free. It would be better. 

I have been using Blue Prism for approximately one year.

We are not using the latest version, when we used it last, it was version 5.

It is stable, but we faced some issues while we were automating web applications.

This is a scalable product. We were a team of 10 or 11 who were using this solution.

We did require support, but we got it from the website.

If you compare it with UiPath and you require support, there is a lot of help available from the forum, but while I was using it, Blue Prism didn't have an updated forum.

I did receive a few answers but the forum needs to be updated.

I was not a part of the initial setup up, but I believe that the initial setup may be moderate, it's not that easy. It requires some SQL connection.

It only requires one team member to maintain this solution.

Blue Prism is quite costly.

The free version provides you with a free forum for a month, where UiPath provides you with a community edition with their free version.

I would recommend this solution to others.

I would rate this solution a seven out of ten.

Normally, we work with the insurance and financial sectors. We create automations for reconciliation, account opening, account closing, and similar processes. Mostly, we work with Windows and mainframe applications.

The most valuable features are the exception handling and embedded control room.

This is an all-in-one product, so you don't need to have another application.

The debugging in Blue Prism is very nice.

They introduced AI and machine learning capabilities in-house, rather than third-party.

The intelligent automation, like document processing, is lacking and should be improved. I would like to see PDF processing capabilities, and invoice automation templates.

Technical support is in need of improvement.

We have been using Blue Prism for the past four and a half years.

The stability is fantastic and is one of the great points of this solution.

This product is easy to scale.

We have seven or eight people in the company who use Blue Prism on a daily basis.

I would rate the technical support a five out of ten. Sometimes we have problems because we understand the technical aspects, and they will give us a workaround instead of explaining that something does not work.

Technical support is an area that needs to improve.

In addition to Blue Prism, we use UiPath and Power Automate as well.

UiPath is more advanced, technology-wise, than Blue Prism, and they have more functionality. That said, Blue Prism has a beauty of its own.

Blue Prism is cheaper than UiPath.

The initial setup is really simple. Most of our clients already have their VMs up and running, so it normally takes a day to deploy, or a day and a half at the maximum.

We do the implementation in-house.

The DBA can perform the maintenance because we have a script running, and it's really easy maintenance.

Blue Prism has a really simple licensing model, where the licenses are not confusing and there are no hidden costs the way there are in UiPath. 

My advice for anybody who is implementing Blue Prism to first think about what their reason is. Based on that, see how they want to bring the product into the sphere. They have to think about infrastructure and then what kinds of applications they want to automate. This will dictate how they need to configure their hardware and environment.

I would rate this solution a ten out of ten.

Our primary uses for Blue Prism are Solution Design, SDD, PDD, and Coding.

It has improved our organization in that we have been able to reduce manpower a lot, as lots of manual tasks have now been automated. It has really been helpful in the field of insurance.

Blue Prism MAPIEx and the Java Bridge are really great features provided for automating Java-based applications and for allowing mail to send and receive smoothly.

It can be improved more in the field of Medicine.

Lotus Notes automation should be easier to understand.

Improvement is required with the DLLs for MAPIEx.

We have been using Blue Prism for five years.

Our primary use case is automating data entry-intensive tasks interacting with in-house applications.

This solution has allowed us to free up time for more "value add" tasks, increased quality through a reduction in data entry errors, and has benefitted us with shorter turnaround times for some processes.

The most valuable feature is the ability to do surface automation, allowing interaction with legacy systems where terminal emulation is still in use.

I would like to see the vendor improve the efficiency of Blue Prism interaction with applications. There are instances where the human user can complete the process faster than the "bot". It does not support (at least not well) scenarios where attended automation (back and forth hand-off between human and bot) is required.  

This solution has increased the speed, accuracy, and happiness of staff involved in the activities for which RPA has been deployed. 

The most valuable features are the exception handling and versatility with interfacing to existing systems.

We would like to see intelligent process automation that integrates RPA and machine learning. 

We use this solution in all area of our business. The most common use case is related to our financial sector and loan applications.

The most valuable improvement in utilizing process automation is the cost savings, but we have also had cases where the customer experience is enhanced.

The most valuable feature for us is that our developers find it quite simple to develop processes, and they like to use this solution.

The licensing models for this product need improvement. Compared to other tools on the market, it is one of the most expensive.

We understand that they will be launching an OCR tool, and we are looking forward to this.

We would like to see some desktop automation, although we have been told that the product is not going to be taken in that direction. Rather, they will continue to focus on product automation and we will have to incorporate other solutions.

We have had some problems in the Blue Prism environment. For the tasks our robots are doing, our success rate is between ninety-two and ninety-eight percent. So, there are some things that are not being successfully created.

We have managed to scale it up quite well, so scalability is ok.

There are approximately twelve thousand people who benefit from this solution. We have around twenty developers, and there are between one and two hundred people who have a direct connection to the RPA deployments.

We have had problems with the solution, but between our vendor and the Blue Prism technical support, we have managed to solve them.

This was the first tool that we started to utilize when it comes to RPA deployments.

I found this initial setup to be complex.

Our implementation was done using both our in-house experts and some external manpower.

My advice for anybody who is implementing this solution is to have some expertise in-house, and not rely solely on the vendor. Similarly, I don't think that it is a good idea to develop and manage your infrastructure based entirely on advice or direction from the vendor.

This is the first RPA tool that we have implemented, and we do not have a lot of experience with other tools. We are satisfied, but there is room for improvement. 

I would rate this solution an eight out of ten.

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

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.

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

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.

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.

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.

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.

We did not use another solution prior to this one.

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.

We used a consultant for the deployment.

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

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.

Our primary use for this solution is in the financial department.

It offers assessments by way of a robotics or automation readiness assessment tool, which was quite helpful. Otherwise, it is much like other automation tools.  

This solution is lacking attended automation, which is the worst thing about this solution.

We did not push the boundaries of our implementation beyond what you would normally expect for this type of solution.

We have not dealt with technical support for this solution.

Specifically for Robotic Process Automation, we did not use a solution prior to this one. We have used Test Automation tools from Mercury Interactive, which seems to be where RPA started.

The initial setup for this solution was complex because our client did not refine the processes. There was no time taken to make simple, reliable, and high-volume processes.

My advice for anybody implementing this solution, or any other RPA project, is to start with the right processes. They should be simple, and suitable for high volume or repetition. Do not make the processes too complex.

I would rate this solution a seven out of ten.