Blue Prism Reviews

We have a partnership with Blue Prism and I'm a software engineer. 

This is a good solution. I like working with multi-bot architecture, it's very flexible. 

In the object section, there are certain things such as the navigation in the UI that could be improved. It would be helpful for developers. I'd like to see more technical support for the team and the provision of some community versions for people to learn the product. I believe it would also benefit Blue Prism to better understand the requirements of those using the product.

I've been using this solution for almost four years. 

The solution is generally stable although we have had some inconsistencies. 

The solution is definitely scalable. 

The value of this product could be greatly improved if we could get satisfactory answers from the technical support. The last time I opted for a learning license from one of my colleagues, I never received a response from the company.

The initial setup wasn't too complex and didn't take a long time. 

We have various use cases for the solution and deploy it on AWS Cloud.

When we need specific reports, the default reports posted in the interactive clients are not helpful but can be useful. However, this means we can utilize only the minimum level, but we want to use more input data from the Blue Prism tool, which means we need to fetch more of the data from the table side, and for this, we need to integrate many tables for this integrating of data. So it becomes difficult to get a BP database onwards.

We are additionally migrating the Blue Prism database to different clouds. Blue Prism currently supports SQL Servers, and structured data, it is stored as an income performer. When we migrate to a process from a different environment, we either need to go with the complete restoration of the GP or we need to lose the data. This is because if you have ten processes, five processes may complete the testing. Other processes may still depend on the current environment when we move to live production. So since it can take weeks or months, we may lose the data while waiting, and we cannot integrate both from different clouds. 

Hence, the solution can be improved by enhancing the process's data storage and by including a common check. Sometimes, if the developer fails to identify a timetable directly, it will impact other processes. Currently, all processes are stored on the various tables in the Blue Prism, and the pre-check can ensure the developer is notified.

The solution can be improved by switching off data DB and including a report section with a morphing feature, like more reporting waste.

We have been using the solution for a year and a half, and we are recently migrated to version 6.10.2.

The solution is stable. I rate the stability a nine out of ten. 

I rate scalability an eight out of ten, but when we interact with different environments, it is difficult to communicate, and DB synchronization is problematic. We currently have approximately 50 people utilizing the solution in our organization.

Technical support is often delayed as it takes four to five days to resolve issues since some people work across different time zones under constraints. Additionally, they are not traceable when we need to forward the case to a high level, and it takes another week to escalate to a higher level, which is unacceptable.

Deployment depends on the process' complexity level. It depends on if you want a straightforward process or gradual deployment over two weeks. For example, one week for the UIT testing and another week for SIT testing, four days for UIT testing and working at the QI level, and the following week for production, and in one month, we can take up hyper care. This is the best practice.

We did light scale mode for the deployment process, so when one process came into the picture, we ensured that the production environment would be ready for that process. So far from size, without any delays in the project deadlines and once the process is developed and code reviews are completed, we take internal approval to move the code to the following environments. So we can use duplicate and use different tools for pushing this code in the CIPD environment level or move this cycle management, like import and export processes.

We implemented it in-house.

The license is expensive, however, I cannot share the exact cost.

I rate the solution a seven out of ten.

Our primary use case for the solution varied, and some of the use cases were in financial and billing, while others were in managed services and automating infrastructure. It is deployed on-premises.

The biggest benefit the solution provided was in the financial sector. Specifically, in billing and processing orders for customers. So it focused on processing manual data that was coming from various systems or interfaces and putting it into the billing platform.

We find the stability and the ease of reusing code design valuable.

We had a lot of challenges managing authentication and reusing or using external authentication providers. For example, in API interaction, we need to get tokens from a centralized authentication platform that was always running for us. The solution can include attended robots similar to UiPath in the next release.

We have been using the solution for approximately five years and are currently using version 8.6.

The stability is good, but it is not perfect. I rate it an eight out of ten.

I rate the scalability an eight out of ten and it could be improved.

We had a good experience with customer service and support. I rate them a nine out of ten.

Positive

I was not part of the initial setup.

We implemented the solution in-house, with an internal IT support operational team consisting of approximately ten people covering shifts so that they will be able to monitor and maintain the robots 24/7.

Based on the project, the solutions have a return on investment or breaking point at roughly 18 months. I rate the overall ROI a six out of ten. It is just a little bit above the breaking point but it is worth it. It does not have much benefit in the long term because our businesses are changing, and the time to use the robot was short.

The solution is costly. I rate the pricing a nine out of ten, with ten being the highest price. It was approximately 700 euros monthly. Additionally, there was 25% included on subscriptions for maintenance but the percentage varied from year to year.

I rate the solution a seven out of ten. The solution is good, but its authentication features can be improved, and the price can be more affordable. I advise new users to have a clear business value and a good process defined before implementing the solution.

We've implemented Blue Prism for various banking operations for HSBC. It's used to provide support for various areas of business like mortgages, screening teams, and payment processing. So based on the process requirement, we prepare best cases and use cases, then we cater to the requirements of the business. There are around a hundred people at HSBC divided up among four digital operations center teams. These are spread across the globe in India, China, Europe, and Hong Kong.

For payment processing, our department needs to handle all inbound and outbound payments. Each transaction has to be reviewed and screened at two levels. This entire process takes around 40 minutes of uptime. So that is the time actually, whenever we initiate any NEFT or IMPS payments. So it takes generally 20 to 40 minutes time to deposit the funds. So in this scenario, RPA helps this particular department to reduce that processing time. 

So earlier it was taking around 30 to 40 minutes to complete this entire cycle. Now the first level has been automated, and the robots are processing this payment. 
Level one is completed within a few minutes, so the payment automatically goes to the level two team. This has cut the processing time by around 30%. Now it takes less than 20 minutes to process. That's just how it helped in this particular department. There are other examples of similar time savings in other departments of HSBC.

We use Blue Prism's automation features for any activity that is repetitive and has to be done repeatedly.  We have implemented this solution for our existing processes where the management transformation team has conducted a proper investigation and proper methodology.  All of the processes that we've automated have been completed successfully, and the bots are able to process them as expected.

There are a couple of challenges in Blue Prism's latest version. So the main difficulty is when the bots are in a run state. If the schedule calls that, then the schedule information is not being received by bots in the right way. It means the bot is already running, and there is a schedule in place that is not functioning as expected. Also, there is a scenario where the bots are not handling volume as expected, especially when there are challenges with other environments. So there are a couple of areas where we have found that bots are not working as expected, especially in version 6.4.

I have a total of four years of experience with Blue Prism, two of which I spent working for digital worker management where we were specifically responsible for run activities. I know how to react to any situation where the bots are not working. I know what action needs to be taken, who to contact, and how to prioritize each action. In these areas, I'm very strong. So based on my experience, my efforts, and my inputs, I have had the opportunity to move to as a configurator or a developer. So for the last two years, again, I've been part of this development team.

We have been working with the bots for the last two years, and they're working as expected as of now. 

There are a couple of projects where data science using the R language has been integrated into the Blue Prism solution. The R language data science specialists have designed a solution that helped us to process the payments based on previous investigations or previous decisions. So looking at previous decisions and creating models about the probability of approving or denying payments helps the bots process decisions quicker. So in this way, R language has been integrated with Blue Prism. This particular solution has been producing good results. It's able to make better decisions than a human and faster.

Most technical issues are handled in-house. There are two teams. One is the configurator or development team. The other is the worker-management team or digital workforce management team, which is nothing but the run team. If they find any issues, they create an incident ticket and send this to the program team or development team. So these teams will actually add that work on it to resolve the issue. That's how it happens.

Four years ago, the bank did not have a specialized team for this RPA solution, so they started taking support from Accenture or Ernst & Young teams. So the initial processeswere automated by these teams. Two years ago, HSBC started its own teams to develop the solutions using Blue Prism. Blue prism is the only automation solution HSBC has used so far. 

It depends on the types of applications and processes being automated as well as the number of applications being used for that particular process. As the number of applications increases, so will the complexity depending on the situation.

When the DOC team shares our stats with the operations department, we quantify the potential cost savings of using a particular automation solution. Generally, we speak in terms of the number of full-time employees used for a particular process. So, if there are 10 people working to complete a particular task, how many people do we need after implementing Blue Prism? If the remaining work is being completed by seven people after the implementation of RPA, then we have saved 30% using Blue Prism.

We are on a yearly license. There are two types of licenses. One is for the VDI license and the other one is for the Blue Prism license. For HSBC we have yearly licenses. Altogether, I think $750 per annum needs to be paid for this VDI license and the Blue Prism license is different. 

Blue Prism is a bit higher priced compared to other payment-related or investment-related solutions. At the same time, it also provides more security than those solutions, specifically for the banking and insurance sectors. Moreover, this Blue Prism provides the flexibility to automate daily banking-related activities. 

So that's how Blue Prism is being used for the banking sector. Senior management team is looking into alternatives. For example, Alteryx is the one tool that is being introduced to HSBC. Currently, we are undergoing training for Alteryx and are exploring ways to cut down on costs.

If you are looking to automate repetitive standard activities that need to be done by a human investigator or any manual process involved, Blue Prism will help. But when you need to automate other types of activity UiPath can offer better results than Blue Prism. In terms of cost, UiPath is a bit cheaper when compared to Blue Prism.

There are pros and cons to this particular application, Blue Prism helps us complete a particular process in a better way. It may give us better results or produce the same result faster. But there are many unknown challenges, like application latencies. Maybe Blue Prism or automated processes might not be able to handle those situations properly or it might not be able to deliver the expected results sometimes.

I would rate Blue Prism a seven out of 10. 

The use cases range from document ingestion, process enablement, and data management, including financial records cleanup.

So it's essentially the arms and legs for digital processes. So the clients have processes that have tech enablement, but there's stuff that needs to orchestrate the different tools and bring them all together into an end-to-end automated process.

There is room for improvement in the pricing. 

I have been working with this solution since 2017. So, we have a mix in our portfolio. So, some of them still have the older versions, but some of the newer clients are on the latest versions.

I would rate the stability a seven out of ten. Because a lot of times, there are specific versions of things that you have to use. So browsers, plugins, all that good stuff. 

For example, some of our clients had their clients on auto-update. And what happened was it was updated during the auto-update, and then the bots would fail because there were plugins or features that were specific to versions of Chrome that we included in the solution. But on the upgrade, they would then fail. On some of the older versions, some of the challenges were around the actual configuring of the virtual machines and their allocation of memory.

In essence, you had the physical memory on the machines, but virtual machines weren't configured properly, so they would run out of memory.

The scalability of the solution is a two-factor thing. 

The ability to scale up and scale out of the Blue Prism portfolio, meaning the agent server monitors all that good stuff, is pretty straightforward. I would rate the scalability for on-prem a seven out of ten and about eight out of ten for the cloud. 

But the second factor is a lot of the scalability has to do with the latency of what you're connecting to. And so if you're connecting to something that isn't particularly scalable, it doesn't matter how many robots you scale out. You're constrained by the latency and the size of the application or solution or service that the robot is using. 

Therefore, scaling is normally an organizational issue such as procurement.

We have around nine customers using this solution. 

The customer service and support depend on your customer level. So, if you're a platinum implementation partner or a platinum client, you obviously get better support than if you're just using the standard features. But we've been involved with Blue Prism from the beginning, so we have a bit of a privilege for this.

The difference is UiPath, you are part of the community, and getting support from within the user community is actually quite effective. But it's just because of a significantly larger install base.

Positive

The biggest challenge is at the infrastructure layer, especially if you're doing on-prem. Getting all the network and firewalls and all of that sorted out because many clients want you to use the robot on the production systems, but the production systems are in tightly controlled network environments. It normally means opening a firewall, subnetting, and all that kind of stuff. But getting the software up and running and getting the agents up and running, all that type of stuff, that's pretty straightforward. 

On the cloud side of things, it's providing access from the cloud platform to on-prem data. So it's more client-specific security and networking issues that are the challenge versus installing the software if you do on-prem or configuring it if you do it in the cloud.

We provide the maintenance for the solution for some of our customers. We are the solution provider. That's a full-stack contract, meaning that we run it, manage it, maintain it. 

And then, for some of our customers, we are an enablement partner that's really about providing design and build and training. And for some of them, we provide secondary or second-level support.

I've considered other options because of how Blue Prism's product and its acquisition by ACM have shaped its direction. Blue Prism seems to be moving into a more confined space and may not be as open as UiPath. 

In UiPath, the ecosystem just feels a lot broader, and there's a lot more innovation and commercial models. 

With Blue Prism, everyone wants to charge for everything, whereas in UiPath, you know, the community guard. There's a lot of really good stuff and useful stuff coming out of the community guard that are solving problems because they need to be solved, not necessarily because there's a business model or a commercial model sitting behind it. 

Blue Prism is definitely more about the seats and tires, whereas UiPath is for the sneakers and jeans guys.

Overall, I would rate the solution a seven out of ten. The only reason that I'd rate it as a seven is because of the commercial model. Blue Prism has some great features from a technology point of view, but they're more on the pricier side compared to UiPath. The difference in technology and the solution doesn't warrant the difference in pricing.

The solution has cross-application features where it can be set up with SAP, email, or SharePoint.

The solution could be more user-friendly. I would like the see the inclusion of a recording feature as in Microsoft, SAP, and other legacy systems. Users can play the recording and use it for future use cases. The recording can help with the automation and configuration. I would rate the tool’s interface a seven out of ten. It needs to improve.

We have been using the solution for around two to three years.

The product is quite stable.

The solution is scalable. We have around 100 users for it in our company and we intend to scale up the numbers.

We have never contacted the tech support team since we have our own internal technical team.

The solution is enterprise software so we will try to maximize our usage during the available slots. We will get ROI with the high price since there will be some value added with automation. I think that after doing a cost-benefit analysis, we are on the positive side.

I would rate the overall solution an eight out of ten.

I'm one of the senior consultants in the company I work for, we are a service provider and we provide IT services to our customers. One of these services we provide is automation, using tools, such as Blue Prism.

We are upgrading to version 7.01 of Blue Prism in a few months.

We are using Blue Prism recently for statistics processes, which is the automation of SAP transactions for our logistics departments. Additionally, it is being used for SAP transactions within our IT finance service department. We do many things with it, such as partial reset and ticket re-keying. We have incident tickets logs from the IT department, which can be from emails, and we do re-keying exercises.

Blue Prism can improve a lot. The interaction with Google Chrome can be massively improved. I know in the next version there are slight improvements. We don't know how much, but we are comparing them. At this moment, Google Chrome is a massive issue within the toolset, due to the way Google Chrome receives updates regularly but Blue Prism is unable to cope. The spy method of Google Chrome is not as user-friendly as Internet Explorer is. However, Internet Explorer is being discontinued from their support, therefore it's not the best browser to be using. This has caused us major issues in the last six months. 

Our customers go through platforms, such as CyberArk and Citrix. The way that Blue Prism interacts with these applications could improve. There are a few other issues, such as memory, but these are the key problems that have offered issues in the past six months or so.

I have used Blue Prism within the past 12 months.

We have had a mixed experience of the stability of the solution. The problem that we have faced might be our infrastructure. The application itself can't be completely blamed. I think some of the issues are down to our VM infrastructure, the application service that we use, and the host that the servers are hosted on. In terms of the application, we have not seen many issues.

The technical support is very good.

I have used UiPath previously.

You don't need to be a technical developer to develop in Blue Prism, you follow the natural way you have developed. Whilst with UiPath, you need some development background to be able to develop in it.

We have been using Blue Prism for approximately eight years and when we first set it up it was a bit complex, but we always had support from the license of Blue Prism and other providers that we have within our organization. The whole process was fairly easy because of the support we had.

My advice to others would be to make sure they fully understand the use cases. If they are implementing it for customers, you're going to come across connectivity issues and make sure that you fully understand that it's not going to work right away. You're going to have to have a few releases into production, be mindful of Google Chrome and the issues that you may come across.

I rate Blue Prism an eight out of ten.

As for primary use cases, we have done purchase order processing for close to five countries, and we also do non-compliance in terms of the field assets deployed by a company to hospitals. That is, we use it as an asset tracking solution.

From technical perspective, Blue Prism is pretty good.

Overall, it's a stable and scalable solution. Installation is straightforward as well. 

Blue Prism could be compatible with Oracle's suite of ERPs. We have seen some issues related to this.

They could do much better with their intelligent document processing solution. They're pretty behind and don't have attended bots.

I would also prefer a better UI in the administration screens The user interface is pretty bad from an administration perspective.

I would like to see a lot of features like process mining.

I would also like to see a lot of different innovative solutions like human-bot interaction, handover managerial systems, and collaboration systems for process capturing, storing, and evaluating and getting discussions done within businesses.

We have been providing Blue Prism to customers for more than three years now.

From a platform perspective, we see compatibility issues with Oracle's JD Edwards software sometimes, but overall, to my knowledge, the solution is stable.

It's a scalable solution, and scalability is not a problem.

With regard to the initial setup, it's a pretty straightforward from Blue Prism's perspective. It's not as complicated as the installation of a WorkFusion solution, for example.

The actual installation, that is, setting up of the environment, can be done in less than a week from scratch.

We have four or five customers using this solution, and I have close to 50 or so people working across these customers. We have a combination of staff, such as architects, developers, managers, infrastructure engineers, etc.

Our customers pay for an annual license.

The product is good even though there are a lot of shortcomings. Also, the access to the company itself is very difficult. Obtaining a partnership is difficult, and getting support is difficult as well. So, I'd rate them at seven on a scale from one to ten.