Blue Prism Reviews

I work with an insurance organization and we are currently using it to automate our back-end office processes. For example, within insurance, you have claims and you have policy owner services, and you have different business units. We are looking at those processes and automating them through Blue Prism robotics.

Mostly we use the Design Studio to develop the automation. It's great. We put them into deployment and have the automated process running. It's essentially the Design Studio for Blue Prism and the entire methodology of delivery that is the most useful or valuable to us.

The solution can scale. 

Technical support is very helpful.

It's not very easy to use. There is some learning curve that you need to manage as an individual.

In the past we have had platform challenges with Blue Prism, like the scheduler functionality doesn't always work as expected and there are content downtimes as well. On the stability, I will probably rate it a little lower than medium.

If they could have process recording and task recording also in place, that will help expedite the delivery for the automation.

I've been using the solution for about six years. It's been a while. 

The stability could be better. The scheduler functionality doesn't always work as expected and there is content downtime as well. It's okay, however, they could work on improving it. 

The scalability is not an issue. Scalability is good. We are using it for around 500 robots, and the scalability is not an issue at all.

In terms of users, we have around 50 odd configurators that actually use Blue Prism on a daily basis. Within the technical team, there you have a few project managers and within each project team, you have a business analyst and a configurator and then, you have a setup process controller who manages the processes.

At this point, we do not intend to increase usage.

Blue Prism provides us with the technical support we need. They even have a monthly catch-up with our team and we are able to raise our technical queries during that time if we have any. There are no issues at all. We've been very satisfied with their level of attention and assistance.

I wouldn't know about the setup process. That's really more for the infrastructure team. I can't comment on it mostly due to the fact I wasn't a part of it.

We have an enterprise-grade license with Blue Prism and it depends upon your requirements. We ask for additional production bots, which is the main parameter for the license cost.

We're customers and end-users.

There are multiple tools in the market for RPA - Blue Prism, UiPath, Automation Anywhere, et cetera. I wouldn't rate it better than anyone else, and yet, I wouldn't rate it less either. It's as good as any other tool. Therefore, every company will need to do its own analysis and select the tool that makes the most sense for them.

I'd rate the solution at an eight out of ten.

We use Blue Prism to target the financial service industry. Our core use cases are specifically in insurance and banking.

Within our company, there are two developers that use this solution. 

Whether we increase our usage of this solution is going to be a market-based or market-driven decision. 

Although it's very simple to work with, it's a bit limited in terms of capability compared to similar solutions. 

I have been using Blue Prism since the beginning of 2021.

Blue Prism is stable enough. 

Blue Prism could be more scalable. 

Most of our use cases are back office-based. They usually don't interfere with our day-to-day operations. We tend to run most of our robots in the evening after working hours. The support is mainly remote. So it's not really a big deal.

We started with UiPath and Automation Anywhere.

Before we started using this solution, we were programming directly from things like Python, which was really cumbersome and complicated. The mid-levels specifically around continuity, and plus one capability internally. That's why we decided to use existing development tools like UiPath, Automation Anywhere, and Blue Prism. From an implementation perspective, they're a lot simpler to use. We no longer have to do a full-on manual implementation and develop from scratch.

The big vendors should consider some sort of unbundled pricing model that allows them to price accordingly to a customer's needs. Because developing robots manually took too long, this solution gave us a lot of flexibility when it came to pricing. A lot of global vendors have a very big problem understanding the price structure or price requirements of frontier markets, like Africa.

Compared to UiPath and Automation Anywhere, on a scale from one to ten, I would give Blue Prism a rating of six. 

I would recommend Blue Prism to others. From a tool perspective, UiPath is by far and away the best tool to use. Unfortunately, it's rigid around its pricing. Blue Prism is more affordable, but it won't provide you with the same features and functionality.

I have been using this solution to develop internal web-based applications. Some of the applications are interacting with desktop applications.

It saves time. By automating repetitive tasks, we are able to save a lot of time. There are also fewer human errors.

The credential manager and logs are most valuable. We are using Blue Prism for complex processes because it is easier to troubleshoot in Blue Prism, and the logs are very accurate. It provides the ability to create smaller tasks, which makes it easier to troubleshoot.

Its image recognition or the OCR part should be improved. The quality has improved in the latest version, but some of the handwritten documents are not that accurate. 

Its interaction with the Citrix environment should also be improved. Their technical support should also be improved.

I have been using this solution for at least three years. 

It is pretty stable as compared to other RPA solutions. Its stability also depends on other applications.

Their technical support is not that reliable. They are quite slow, and their response is not that proactive for our questions or issues.

For other RPA tools, you can just search the web for information, but for Blue Prism, there isn't that much information.

It is not hard to install. You just need to design the database. 

Deployment is pretty fast. For deployment within our team, the server is the same, and we just configure it to run on our machine. For deployment outside our team, we just need to install the server and then configure the machines. It is not that complicated.

We did it on our own.

In the Philippines, fewer companies are using Blue Prism because of its cost. I don't know the price, but I know that its price is higher than UiPath.

It has good stability, and it is easier to troubleshoot. We don't have a need to increase its usage because we are currently using it for complex processes, and our number of users isn't going to change.

I would rate Blue Prism an eight out of ten because it has some room for improvement.

We primarily use the solution for finance, specifically accounts payable.

The solution has improved our organization in that our AP administrators and AP clerks don't have to put the information into the ERP. The RPA does the transfer upon approval over to the ERP system. You don't have to code and create backend APIs or custom code to integrate the systems. It makes things much easier overall.

The object modeling is the solution's most valuable aspect. It's been quite helpful for our organization. The reusability of it has been great. Being able to create an object and use it for multiple processes has been very useful for us.

The initial setup is straightforward.

The reporting system, specifically the system admin reporting could be improved.

If there were more business analytics, that would be quite helpful.

In general, however, the solution isn't really lacking any features.

I've been using the solution for three years. It's been a while at this point.

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's extremely reliable in terms of performance. 

The scalability has been good so far. If a company needs to expand it, it can do so with ease. It's not a problem.

We have several hundred users on the solution currently. Blue Prism operates on the enterprise level and the activities of the digital workers happen on the servers. So virtually no one needs to interact with it directly. It's mostly on an administrative level that there are some people accessing the application and its reviews, exceptions, and things like that.

I have limited familiarity with other RPA products.

The initial setup is very straightforward. It's not overly complex. A company shouldn't have any issues with the process.

The installation itself takes maybe a couple of hours, however, the customization, depending on the complexity of the process, can be anywhere from six weeks to eight months. It really depends on the complexity.

Per five digital workers, you need one or two individuals for maintenance.

We are an integrator. We are able to help our clients set up the solution.

We are a reseller of the product.

We've been working with the most recent version of the solution in our organization.

I have been happy with this solution overall. I'd rate it at a ten out of ten.

We use it mostly to mimic what our operation agents are repetitively doing so that they don't have to do the same thing over and over again. We are using it to eliminate the repetitive tasks that require no thinking or intelligent decision making. We are using the latest version of Blue Prism.

It is able to eliminate repetitive tasks and bring efficiency. At any point in time, the bank needs to hire 10 to 15 operation agents. In operation teams, the turnaround rate is always very high, so we are constantly understaffed. Capacity has always been an issue. With Blue Prism, we are able to automate a lot of tasks. 

We can also scale up and down. We can scale up our operations when we see larger volumes and scale down when we have lower volumes. We can have new bots, licenses, virtual machines within days, but we cannot have an agent trained up within days. It takes weeks to hire people and train them.

Its ability to talk to different systems that we have is a valuable feature. We use Pega, which is like a credit card processing system. We also use a Debit Process Manager, which is like the Visa debit application. In the bank, we have credit card and debit card sections, and we need to kind of investigate some of the transactions when customers are complaining about the charges. Blue Prism can log in to a different system to perform the exact actions that the agents are doing. This feature has been very helpful.

Its ability to engage with external systems and websites is also very valuable. Each of our RPA projects could go across different systems. We have an in-house banking system. We also use the Visa network, and we have to go to different sites to do a lot of data scraping to ensure the data in our system matches the data in the Visa systems, and we just deal with some of the charges.

It isn't very easy or intuitive for our developers to program the bot to make intelligent decisions. A bot, for the lack of a better word, is stupid, and it can only do what we program it to do. It cannot make intelligent decisions. For example, if we are reviewing Uber charges, they could be posting their transactions under different corporation names, even though they are under the same parent company or group. A human can easily understand that it is the name of the same company, and it just has an asterisk or space, but a bot cannot do that. When a bot cannot complete the transaction, it sends out an exception rate, business exception, or system exception for a human to do a manual review. The exception rate has been high because the bots cannot make decisions that we think are very simple, which is understandable because that's how they were programmed. There is potential in utilizing the higher intelligence side of the tool, but it is not easy to code higher intelligent actions.

It is a very lengthy process to get the provisioning to ensure that it is kind of doing what it needs to do. Provisioning involves multiple things, and it is quite complicated and not the best experience, but it is not just because of Blue Prism. Blue Prism is easy, but it takes a long time to onboard into our in-house system. 

I have been using Blue Prism for one year. I started doing the RPA project a year ago. I am providing consultancy to a specific business unit to ensure that the tool is deployed in the right way and meets the business need.

I'm involved with in-house systems as well as external systems. For provisioning, I get new bots. It involves multiple things, and it is quite complicated. It is not the best experience, but it is not just because of Blue Prism. Blue Prism is easy, but it takes a long time to onboard into our in-house system. The provisioning of our in-house system or external systems is a challenge that we have internally.

In terms of users, on the technology side, there are three main roles. We have developers, delivery managers, and business analysts. Business analysts gather different requirements of the business unit to ensure that developers know how to program our bots. The delivery manager is like a project manager who ensures that the projects run smoothly and prioritizes different tasks when any change requests come in or there is any change in the schedule. 

On the business side, there is the subject matter expert and a manager for the operation team. There is also an operation agent who does the demo of how humans are performing their day-to-day job so that the technology team can understand what a bot needs to do. There is also the redesign component of it to ensure the bot is not just mimicking what the human is doing. It is also doing something more and better. 

I don't think that there was a tool that we used before Blue Prism. There were various things that people were doing in silos on their computers. Blue Prism is probably the only automation tool that was rolled out at an enterprise level. We are also rolling out Power Automate.

We have different teams that do the provisioning. It is not my area to do the setup. In terms of the setup of the application, it is not hard to set up. The bank will have everything resourced and pushed into our computer. All I do is just click a button and install it, but there are a lot of things that happen in the background, which I don't know.

We have to do our business case before we wrote out RPA projects. Based on our tracking, the business benefits for the last three years have been on track. Most of our projects get returns within one year based on the human capacity that we are saving, and we have seen and are on track for the business benefit.

The billing is on a yearly basis. They send us the bill every year. My business unit is billed by the technology team, so I don't know exactly how much they pay. In my business unit, we have our first-year license costs, and then we have our ongoing costs. Our bots cost projected per license is $8,600. Our projected support cost for every year is about $38,000. Our operation agent costs anywhere between $50,000 to $55,000, so the saving is there, but it is still kind of expensive for us, but I'm looking at it from the technology kind of billing us for it. This is the cost that we have for our technology team, which is different from the licensing of Blue Prism.

I would rate Blue Prism a six out of ten, which I consider as a good rating. Seven is very good, eight is excellent, nine is outstanding, and ten is perfect as per my standards.

We've started to use some of the new features such as translation, cognitive, and we are finding them useful. We are also finding API integrations very useful.

We would like to have something, not particularly within the tool, that gives flexibility to the end-users to schedule the bots themselves. There should be some kind of control room flexibility so that they can go in. We don't have to always keep that centralized with us. 

We would also like to have inbuilt scheduling and resource pooling to distribute the bots on servers from within the platform. I should be able to distribute or orchestrate them internally so that if one bot takes a little longer than planned, it automatically shifts to another server. 

We would also like its price to be lower.

I have been using this solution for about one and a half years.

It is stable.

It is absolutely scalable. We have close to 200 automations written in Blue Prism. We have five to six people who work on this solution.

They're good. We didn't find any issues.

This was our first platform for automation. We have used other tools such as K2, but Blue Prism is the only full-fledged RPA platform that we've used.

The initial setup was easy.

Its price should be lower.

I have heard that UiPath is catching up in a big way and offers a lot of flexibility. You can also evaluate UiPath.

I would rate Blue Prism an eight out of ten.

I'm an IT consultant and I implement Blue Prism for my clients.

The only good thing about Blue Prism is the execution speed.

The interface is okay; it is like drawing a workflow map, which some people prefer.

For developers, they should have some kind of recording feature. Their competitors have this capability, so it is a big thing.

If you execute too fast then your code dies.

The stability can be improved by building something on top of it, code-wise. When you are running the software, it needs to attach to whatever window you are on, and then you need to build it separately. This is where you get stability.

This solution is scalable because they have an object library, which others do not have. In terms of reusability, it's great.

My clients are enterprise-level organizations.

In terms of support, they have almost everything for Blue Prism. They have tutorials and other such materials.

I haven't raised any tickets with them, so I do not know about their real support model.

I use UiPath for the most part.

I have some experience with Pega RPA but it's garbage, so I don't use it.

The initial setup is straightforward. You just need SQL and then you can install it.

Ultimately, this should be set up on the cloud using Azure or another provider. however, there are lots of companies that haven't brought their automation off-site, so they are on-premises deployments.

This is a very expensive product and this is the reason that they're losing their market share.

I know that Blue Prism is trying to improve because they have acquired some other vendors.

To summarize, I think that this product is good for business but it's terrible for developers.

I would rate this solution a seven out of ten.

The primary use case of Blue Prism is for financial services. It can't be accessed via a simple web application like you can do with its competitors. For financial services where the main requirement is to retain data in-house, Blue Prism is the way to go. I'm an RPA engineer and we are customers of Blue Prism. 

Blue Prism has helped the company in areas such as invoicing, requests on an augment coming from customers and things like that.

I love the development phase of Blue Prism because there are simple things you can put in place that help you understand workflow and how implementation acts. I love how Blue Prism can use the same variables and objects used on other processes, the really key value is the object sharing. I like that you can forward so you can speed up the process while it's executing which you can do on other RPA tools, but you can also simulate the feed tool from two to four and reach the output quite nicely.

For me, a web application that can improve the connection between robot and human, and share information simply without any file sharing, without any access from the machine, that has the tower controlling it, is the easiest way to share information.

The user interface could be improved and I would like to see a web interface to easily access robot information. The key value of Blue Prism is also its main weakness because Blue Prism is quite connected to its data, so anything you do on Blue Prism is logged on the database. It's quite difficult to read these logs, so I would like to have a more valuable way of understanding how robots work on the environment. Blue Prism doesn't manage variables well. It's annoying because you have to declare visually every variable but there's not a list of the variables. You have to open the graphical elements and check the variables.

I've been using this solution for one year. 

It's a stable solution. It has a quite simple architecture and is very connected to the machine on which Blue Prism works. The RPA tools are connected with the machine, with the applications, with the credentials, and that improves stability.

The solution is very scalable because you can deploy a robot on the machine and with the same licenses you can deploy another robot on another machine. 

Technical support is quite good although I think not as good as with some other solutions. UiPath, for example, has great support, great speed, and they're right on the issues. Blue Prism has that too but they're not as good as the others. 

The initial setup is quite straightforward and similar to other solutions. 

This is an expensive solution. I think Blue Prism has a licensing mode quite different from the other RPA tools.

Blue Prism is a very secure solution because you can implement a structure as a high availability infrastructure. If you have, for example, three machines and one license, you can put this license on any of the machines. If the first machine is down, then you can put that license on another machine.

I would rate this solution a seven out of 10.