Blue Prism Reviews

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.

I use Blue Prism mainly for backend operations where I don't need a lot of manual intervention coming in. Blue Prism is mainly for backend operations like auditing, reporting, compliance, and regulatory requirements.

I use Blue Prism for my customers. I really don't use Blue Prism in my own company or for my own automation. I do automation for my clients. 

If you look at the banking sector, there is a lot of regulatory compliance to be adhered to, and that's where Blue Prism has helped me a lot. Because of automatic compliance checking and auditing, Blue Prism actually gives my clients a lot of benefits, i.e. as an auditor which can check up to 100 transactions a day.

I can now basically sit back and look at over 100 transactions being checked per day. Blue Prism really brings down the number of people required, and it increases the speed. 

Blue Prism assists us in risk management through our compliance to regulations where the cost has been brought down to a very large extent.

The feature of Blue Prism that I find most valuable is the ability to build my own custom objects or use custom logic for doing the particular task. If there is a task that Blue Prism cannot do out of the box, Blue Prism provides me the facility of designing one and integrating it into the application. 

This process is called Visual Basic Objects. I can do all I like because I can add to the functionality of the Blue Prism tool as and when I require it.

Since Blue Prism gives me a lot of flexibility, I don't want the vendor to make any changes out of the box. I believe that there could be more community support, or there could be more support for developers like us from Blue Prism. 

Blue Prism provides a lot of documentation, but there is a lack of support. This is missing. A lot of times, you get stuck and have to solve the problem yourself. If there is a community that is working together and Blue Prism could support that, it would be very nice.

I really don't need any additional features because most of the time we create our own features to work on top of Blue Prism. I would really be happy if Blue Prism can integrate some kind of OCR and machine learning capabilities that are now commonly available in the market.

The solution is actually based on the previous technologies which are very stable from Microsoft. This is the SQL server and the WPF. I don't see problems with the stability of the solution. It's really pretty good.

The scalability's actually in the hands of the person who is developing the bots. Blue Prism out of the box is good enough to provide a platform. After that, the developer's creativity is to really scale it up. I don't see any problems with the scalability in Blue Prism. It's one of the finest compared to the other products.

In my customer organization, we use 15 developers. Everybody works on Blue Prism. In our customer organization, when we've written the bots, there are not a lot of people working on it because the work has been automated. 

The bots run on hundreds of machines right now, but there are very few people required to monitor that execution.

There are two roles. One is the person who is executing the bots and monitoring the results. That is a very small number, but the beneficiaries of this automation are multiple. 

We have a client where they have over 200 auditors. It's an insurance company. All of these auditors actually get the results from the automation which we have written in Blue Prism. 

The number of beneficiaries is much larger than the number of people we require to execute the bots.

When we deploy, we actually send in three people at the customer side to deploy the bots. We normally take about a week to have these three people on site, who will set up everything and we can also train on how these bots run, i.e. how these bots are to be maintained, automated, and monitored. 

It takes about a week. These three guys are there for a week for this particular exercise. Then we basically leave one person there for a month or so. By this time the customer's personnel are trained enough to take over from our guy. Then our guy comes back.

We have been in this for quite a long time. I myself have put in 33 years in the IT industry. Most of the time it happens that we are able to solve the problem on our own. We normally don't need to go to Blue Prism, but there have been situations that we wish that the technical support could have been better. 

Because we ran into technical problems, then the solution had to be found on our own. We basically had to create a workaround for getting the job done.

We have the background experience in the base technology which Blue Prism uses. Blue Prism doesn't do a lot of OCR, Optical Character Recognition, out of the box so we built our own. 

We tried to get in touch with the technical support, and then finally we figured out that it's not available out of the box. We built OCR functionality for Blue Prism ourselves and we extended the tool.

We work with almost every solution: Automation Anywhere, WorkFusion, WinAutomation, etc. We work with everything. Sometimes it happens that the tool which is needed for the client is Blue Prism.

Sometimes the client wants us to use Blue Prism. Sometimes we propose that we use Blue Prism for the client. We don't distinguish between which tool is good, bad or ugly. We basically go by which tool is specifically required for the job.

The setup was straightforward. There are scripts that do the installation and setup. The only thing that I want Blue Prism to look at is the deployment scenario. 

When we deploy this Blue Prism based bot, if we can get some sort of scripting help from Blue Prism in deployment, that would be nice.

The development takes about a month for a particular project, but we need a couple of days to set up the whole thing at the customer's side. I think that can be reduced a bit. 

We have our own scripts written, but our strategy is to write scripts and then install them at the customer's side. Still, there is more that could be done.

We do the Blue Prism installation ourselves. We don't use anyone from the outside.

We really don't bear the costs. The cost is borne by the customer. It runs into about $100,000 per year per customer for Blue Prism. 

We need to add the hardware costs to set up the servers for the SQL server, and then we need to budget for about a week to set up the entire infrastructure. 

We need to add the cost of the people who will be working during this week. There are other costs, but it is the same for any tool. 

We normally budget around $30,000 for the first year for the hardware, setup, and people cost.

We evaluate other options every time. It's not that we do it only once. We have experience with seven tools. We basically look at all seven tools in terms of the features provided, the flexibility, the resources that we have, and also the cost of the tool. It also depends on the budget the customer has. 

Then we select which tool we are using based on an assessment matrix. We figure out which tool actually fits into all the criteria of the project.

We've evaluated WinAutomation, Automation Anywhere, Kofax Kapow, and WorkFusion. Those are the main tools.

Most of my customers, which are large financial services/institutions, supply chain, and logistics companies, are now looking to scale up by a factor of 10. 

We have a customer who is a bank in South East Asia. We have developed about 32 bots and now they are looking at around 200+ more to be deployed.

It depends on how much it costs them to automate, how much budget they have, how much time they have, and what the benefit is that will come in. Most of the time the benefits are huge as long as they are able to create the budget for it.

There's only one piece of advice, and it's not dependent on Blue Prism. The advice is actually to get two different sorts of people who are good at the job:

• One is your designer of the automation system.
• The second one is the developer of your automation. 

If everybody is looking at automation, the first investment should be into getting the right people onto the team.

Blue Prism comes in at a 9/10. It comes in at nine because it's a mix of everything that a developer would want from a platform and from a solution. 

Blue Prism gives you flexibility. It gives you scalability. It can basically go and do large data processing in the back end without disturbing anybody very efficiently. 

That's why I give it nine because like all other tools, the moment you bring in the front end with all of the manual intervention, you run into delays. You run into problems. You run into risks of creating mistakes and errors, then getting lost within the automation. Blue Prism can handle large volumes and that's why I give it a nine.

Predominantly, this platform is used for Robotic Process Automation. It's a low-code tool that doesn't require much technical knowledge and is easy to introduce to your business users in order to make them citizen developers. 

Most of the manual operations and administrative work are low-hanging candidates for automation using this tool. 

It can be used for your infrastructure or application monitoring use case.  

The tool has an extended feature of integration with different databases which can be further extended for analytics/visualization tools. These include Tableau, PowerBI, QlikView, and Splunk.  

The product has impressively increased the productivity and digital transformation effort within the company. The product's USP which makes it different from its competitor is the robust enterprise implementation and the maturity of this product. Its core design works towards building an Object Library. The product has enormous potential which customers can take advantage of thanks to the overall product maturity. The product is available in both the cloud and on-premise.

The core strength of the product is the database schema, reflected in its UI behavior and strength. 

From a leadership point of view, integrating the DB into any of your analytics/visualization tools can give you every insight into your program's health in terms of license utilization, ROI, support landscape, current scope, and future backlog capacity. 

We have integrated the product with our centralized infra-monitoring tool, which gives us real-time insights into BOT health and also the health of the underlying resources.

Emerging technologies adoption is a challenge for every organization, especially the products which address productivity/automation. 

The unstructured data, decision-making through machine learning, building data mining repos, and building smart contracts using blockchain will bed needed in the future. 

Any product that can make itself sustainable with its clients has to make sure they are making the right effort to integrate or upgrade its toolsets to cope with future needs.

I have been using this product for the last six years.

The product stability allows me to work on value-adding work rather than doing maintenance.

The product is fully scalable based on your capacity and automation needs.

We are at the top support tier and have had a good experience so far.

Positive

I have worked on most RPA tools. The company had already selected this product.

It is not complex to set up if your IT team has basic 3-tier application set up knowledge in the case of enterprise-level set-ups. Anyone can do single-machine set-ups by just following the instructions.

We handled the implementation in-house.

The ROI is a combination of soft and hard benefits. This is our 5th year using the product and we are easily getting close to 65% ROI.

I am aware of the pricing. When compared to most of its competition, it's almost near the same in terms of cost.

I have worked on most of the RPA tools. 

The rush to implement RPA is normalizing now. I hope that more companies will invest more time in process evaluation, design, and re-engineering, rather than starting to develop BOTs just to be in the rat race.

In our case, all use cases are relevant to the telecom industry. In the telecom industry, we are the service providers for various telecoms such as Vodafone, AT&T, et cetera. We are the service providers. We are doing some processes and we are doing support in the networks as well. In terms of the internet, when it comes to supporting the network, there are some processes that need to be completed manually. Therefore, we will take those processes from all the verticals. For example, we did this project for Telus, and we identified the processes to where we can implement automation. We sought out processes that were good areas for automation adoption.

We identify those areas for clients and map them out.

The solution's most valuable aspect is the fact that it is systematic. It's a very systematic tool. We can do all these things like array and cache. It's very useful.

We were able to create a few new processes which we automated. 

The mapping is very good. On mapping, we can order the tools required for automation.

The analysis itself is very good. We're able to say which areas can be improved and which are the easiest areas to automate. Typically, it's good at revealing which decision-making areas could be automated effectively.

The tool is very technically sound.

The product is very secure. 

The solution is not user-friendly. It has a very high learning curve. People should be able to learn it easily so that they will get interested in using it. 

While the solution is more secure, it's very hard to find people trained on that. I need different people, not only those who are trained on RPA tools. I cannot get people in Blue Prism. Without the resources, people just move to Automation Anywhere or UiPath which are more user-friendly. In comparison, UiPath is much easier to use and you can find people who are well-versed in it.

The product needs to put out more videos, similar to Automation Anywhere, which does that a lot. You can find a lot of videos online in relation to Automation Anywhere and UiPath, however, this is not the case with Blue Prism. There's just less information available. 

Blue Prism needs to provide better training. They need to start something similar to Automation Anywhere University or UiPath Academy. If they had some courses at different levels (basic, advanced, and master), there would be more educated personnel available.

The solution needs to provide a trial license - whether it is on cloud or on-premises. They need to provide a standard environment to work with. We need to have practice in installing the data center and connecting it to the database. 

We need to understand how we can migrate from one lesser version to the higher version and what is the load balance and how we can manage that. We need to understand better how our core system is managing that. Proper training would help with understanding.

I've been using the solution for about two years at this point.

The solution is quite stable. We haven't had any issues with it. It isn't buggy or glitchy. It doesn't crash or freeze. 

I'm strongly involved with Automation Anywhere. I've been working with Automation Anywhere since 2019.

While Blue Prism and Automation Anywhere are very similar to each other in terms of capabilities, Automation Anywhere is much easier to use. 

Even in Blue Prism or UiPath or Automation Anywhere, the attributes are very similar to each other. However, Blue Prism is got a larger barrier to entry due to its high learning curve and lack of strong training.

We prefer the fact that, for example, on Automation Anywhere, we can use trial versions and we can use that time to train employees on how to use it. With Blue Prison, there doesn't seem to be a trial option.

We are not very familiar with the Blue Prism installation or if it's easy or not. Those areas are a bit of a gray area for me as I'm not doing many installations. 

The setup and installation we didn't do ourselves. We did these projects in the client end roadmap. The client has the Blue Prism tool. They set up everything themselves. Our job is to go there and to be able to provide the roadmap.

Likely, the installation takes about two or three hours, I would estimate.

The product has its own database, such as an SQL server. We often install supporting tools, however. There are some coming out now, such as Python, Java, and VBScript editors. Certain items, such as Java Runtime Focus should be installed. There are different installations depending on the client. If it is not on the cloud, the installations definitely take some time. It might take two hours or more.

Our clients handle the initial setup themselves.

Unlike other options, you need to buy a license. You cannot do a trial. At least, that was always the case a few years ago. With UiPath or Automation Anywhere, there are trial versions. It's a drawback for clients if it is still true that no trial option is on the table.

I'm no longer using Blue Prism. I deal more with UiPath now. However, I am certified in Blue Prism. I tend to take care of the delivery part. We talk with the clients and understanding the clients' requirements, understand the project, then divide the project into activities and map them out. I will help to architect it. If there is any trouble in capturing those areas then I will analyze this in Blue Prism or Automation Anywhere. 

So far, in those Blue Prism projects, it's very straightforward with rule-based - straightforward in the process automation. We will concentrate on low-hanging areas first and we will identify only those areas that we can automate easily. I'm sorry. In terms of automating end-to-end process, we will concentrate only on to 60% to 70% for our automation.



Premarajan:
So come back to the courses, in that way, we are not much familiar with the Blue Prism installation, how this installation takes time, it's easy or not. Those areas are a little gray area for me because I'm not doing much in the installation. But if you ask us if in the installation of Automation Anywhere, definitely, I can say I'll answer that. I can see that screen by screen. When we install it, the watch screen will come first like that. I can say that because I personally did installation Automation Anywhere installation.

Premarajan:
I set up a lab system in Tata so that our employees can train. I did a lot of things. Like that, I installed a UiPath as well in my system. I installed even [inaudible 00:26:08] also they provided, Microsoft has. They also provided a trial license to me when I asked. They also provided.

Premarajan:
But Blue Prism, those days, didn't provide me the trial version and they didn't help me, how to install it. No idea. That is a shortfall I can say about Blue Prism. [crosstalk 00:26:29]-

Emma:
So you were-
Premarajan:
It's very limited when we needed the license or those who purchased the Blue Prism people can work on Blue Prism tool. Others had no chance to learn. That I can say one way it's good. In the other way, people were not aware of the tool. That is, I can say it's good except for one drawback.

I'd rate the solution at a seven out of ten.

Across different business areas, the use cases differ.  The back-office, for example, are more along the lines of reconciliation of data, the back-end operations. We have use cases in our dispatching department as well, where use cases can be like data is gathered for traders to make intelligent decisions, or nominations power plants to the website. 

Some use cases in our procurement area and our financial services.

Our goal is to free our employees to do more value-added tasks, while the robots do the manual activities. That way, employees can move on to more sophisticated tasks. The robot does its work but the employees are still in control. For example, the dispatcher is still on the desk and looking at what a robot has nominated, for example.

We have use cases where RPA is integrating it with machine learning, with chat bots. . Our idea was to start with the basic robot and then make them more sophisticated by adding natural-language processing or machine learning. We have a couple of use cases there, as well. But the repetitive-task use cases are more common.

Our application server and our database are on Azure cloud. But you have to use a virtual machine to access it and that virtual desktop environment was on-prem. Currently, a project is going on to move them to virtual machines as well. So the Blue Prism hosting is currently on our private cloud, Azure, and the virtual machines are on-prem and will be moved to Azure in two months.

There are multiple advantages. 

Time saving is definitely one of them. We do not build robots if they are not going to be effective; Process Improvement is key. You don't want to automate a non effective process.

it can be quality, it can be 24/7 operations, it can be compliance. 

For example, in terms of time, a back-office operations guy would spend, let's say, a number of hours doing reconciliation activities from one system to another, which is something that can be done by a robot quite quickly.

When you look at the front-office, for example, the advantages are more quality-based — less human error. Our dispatching desk , a human error in entering values/nomination can cause imbalance/penalty costs. So five minutes of dispatcher time is different than five minutes in back-office operations. That's why we never say it's only time-savings. The benefit could be avoiding the cost of error. And the opportunity, to do more value adding tasks in the time saved.

As for 24/7 operations, for example a billing robot which can generate the bills before employees are in office.  Then there are some compliance or audit-related situations, where you need to prove auditability of some of the processes. It used to be a human saying, "Yes, I have done the check," but now, if you have a robot checking it, you have everything in the system so an auditor can look into it. I would not say time is the main motivation; the motivations are multiple.

Another advantage, is future of work and modernising the workplace.

And then some are really not technology-related, is that business and IT are coming closer together. Business understands IT and IT understands the business.  We have a federated COE. I am the head of the COE and it is more like a matrix organization where people from different organizations report to me functionally, and I just run an end-to-end customer journey. The way we implement has also changed. It's not that you build a robot and it's with IT, and IT maintains it. No. The business is still accountable for the result of the robot. these are not quantifiable advantages but you see them at the organizational level.

The ease of use is quite good. We have some internal developers so some of our training is more an introduction to robotics. The second module of training is more delivery-related, using the robotic operating model. The last one is Blue Prism-related training and that phase is already available via the Blue Prism portal. We have access to the portal with Blueprism. if somebody is interested in developing, they can learn that via the portal. I make the environment available to them. But the ease of use is really good because a lot of business people, who have some idea about logic and who can think in logic, can configure things, because there is no coding.

The other features are quite comparable to what is in the market right now. There's nothing special about them. But ease of use is important because the business can also handle it.

There are some weaknesses of the tool as well. For example, Blue Prism has been a little bit slow when it comes to the commitments on their roadmap. They had some delays last year, so I hope they make it up this year. They promise, but they are not meeting everything they promise in their roadmap. For example, they were launching a Decipher tool. It was delayed by more than a year. It has still not launched.

Also, the Control Room  for the robots is not very sophisticated. That can be improved. 

We are now going to some attended bots, as well. How do you make attended robots work? It is something that is counterintuitive. On the one hand, I'm saying I need an enterprise tool, and on the other hand, I want attended bots because some cases deserve it. While I need an enterprise tool, I now have some use cases where I want to have an attended bot as well and the tool is not very sophisticated on that end right now.

I have been using Blue Prism for a little more than three years.

It's stable. We haven't faced any problems with it.

We haven't faced any issues. We are in the scaling phase and we are scaling well. We don't have a problem there. It's scalable.

We have > 60 robots that are live and the demand is high. There are multiple business areas that are live, and there are many more in the pipeline. 

Blue Prism's technical support is really good. If you raise a ticket you get an answer within 24 hours, and we have not paid anything extra for support. The maximum I have had to wait was two days. Getting an answer in one or two days is really good. And we generally get an answer from the product team, which is very good. And if they can't solve it via the support ticket in writing, they call you and discuss it.

You also have account partners so if something needs to be addressed quickly, you can make a call. Blue Prism has also visited us two or three times and that is really good. We have a good relationship.

We did not have a previous solution.

One of the major features, and it's why we selected Blue Prism, is that it's an enterprise-level automation. We wanted something that would be enterprise software, so we could monitor it centrally and maintain it centrally, while giving people the freedom to work independently as well. We didn't want a situation where I build a robot and now I'm looking at it on my screen. The idea was to free up peoples' time so that they could do something value-add while the robot is running on its own machine. This enterprise-level type of software was the need and Blue Prism fulfills that.

I have been involved right from the beginning and the initial setup was okay. It was not something that IT could not handle. We didn't run into a lot of trouble.

Setting up our infrastructure was not a problem from the Blue Prism side, but it was more with our infrastructure. Our company is a little bit complex. But it did not take more than four to six weeks for the infrastructure setup, and that was three-and-a-half years ago, so it might be even faster now. 

For maintenance of the solution I have an application manager. I have somebody who does service-enabling so that the robots can move to production. For delivery, I have a project manager, and there are BAs and developers and, for each business area, I have an implementation lead and, of course, a process expert/owner. In my COE I also have these roles and I also have a deployment lead who takes care of the policies and the procedures around the robotics for the entire organization. I also have a solution architect and another role called dependency manager, because there are a lot of different engines we have to manage since we're working with a lot of applications.

We used a consultant in the beginning and we also now use an integrator.

The use cases I outlined are the areas where we are seeing ROI: Quality, compliance, error-avoidance, opportunity cost, and time-saving.

The pricing is scalable for a enterprise-level solution. It's quite scalable and it's quite comparable with the market. If you really scale well over the number of licenses you have, you can achieve economies of scale and it comes out to be very cheap.

There are no costs in addition to the standard licensing fees. There is an option to increase your support levels by paying another 10 percent or 20 percent on your licenses, depending on how much support you want. We are still happy with the support.

There were three leaders at the time we did our evaluation three years ago and were quite equal in terms of their functionalities. One of the factors that led us to choose Blue Prism was the enterprise-level functionality. 

My advice is "go for it." It's good. We are satisfied that we have achieved with the tool, and we are continuing with it. 

Having said that, I would advise that you are free to explore the market and do a study, but in the end all the tools are very similar. It's more about how you will handle it in your organization. That is what is more important. There is not just the tooling around it. There is also the people management aspect, and process management. So there's a lot that goes along with it; more than just the tool. One of the things that I like about Blue Prism is that their operating model is quite good.

The biggest lesson I've learned is not about Blue Prism, it's about RPA as a whole. As I said, it's not just the tool or the technology, it's about how you bring in change management in the company. How do you take people along with you? How do you explain the journey? How do you set up the operating model? Because for scaling, your operating model is really important. You can't just put two robots in place and then think that you will scale because there are a lot of considerations around it. How will your organization adapt to it? For example, when a human joins your company he or she needs an ID. What about robots? Do they need an ID? How do those processes fit in when they operate? How will they communicate with humans? There's a lot of change management around it for the whole organization. 

It's a digital transformation, or you could just call it a transformation. You need to think about a lot of moving parts around it. The tool and the technology are quite easy actually, because all the companies are quite experienced in it. But change management and the transformation part are quite difficult. 

Another thing to think about is how do you choose the right processes to automate? You could think about just automating randomly, or you could think about whether a process is even needed for the organization. Why is somebody doing it? Maybe that process is not even needed; it's obsolete. You might get rid of some processes. We did that as well, and sometimes RPA is not the right solution. So think about automation as a whole. These are some of the things that I was given advice on.

I'm not a technology specialist, I'm a process transformation expert. It's not about technology in the end, it's about what you have done as a transformation to the company. The ways of working have changed. The way you look at a process has changed. A back-office analyst is now building robots himself, for himself. The way he's looking at the process has totally changed. 

We do a lot of RPA training as well. We have a in-house-built curriculum where we have multiple training modules. When people do the training, they change the way they look at processes. They are already thinking about robots or digitalization. You can call it the future of work. When you began this journey, you never thought you would have these kinds of advantages. But now you have them.

I would have given Blue Prism a nine out of 10 if they had delivered on their roadmap, especially Decipher.

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.

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.

We like the reliability and robustness of Blue Prism. The object design way of implementing things actually brings a lot of reusability for us because you can design your objects once and leverage them in multiple automations. So, we use this extensively.

There are a lot of things that could be improved. The very first thing is their control room, and they are still sticking to the desktop version, which restricts access. You can't really access it from anywhere. The entire industry is moving towards cloud-based solutions. Blue Prism should make it RPA-as-a-Service cloud version. I would definitely like to see how they could really make it more accessible, going beyond desktop applications.

They have recently launched their web version, but that is still a read-only version of the control room. The web version of their control room could be accessible from anywhere so that I don't have to go and log into a specific machine.

Additionally, we tried integrating some of the applications to Blue Prism, and there was no REST API. It is still following the older mechanism using SOAP API, which again restricted quite a number of the integrations that we wanted to do. Exposing their artifacts through web APIs, REST APIs, would be good, which is normal nowadays.

It would be good to build more objects; they have very limited objects available, that is, implicit objects. If I need to connect to ServiceNow, I would need to build all those things. So they could really step up and create customized objects as an implicit feature that they could include.

I've been working with it for two years. We've been using versions 6.4, 6.9, and 6.10 and are currently evaluating 7 as well.

I think Blue Prism has the capability to scale its automations. In terms of handling a load, as well as extending the digital workforce for a single process, it supports multi-bot architecture.

However, as far as robustness in terms of when we scale robots, that is, when we want to extend the robots for a process where multiple bots are working, I think Blue Prism has a certain edge because of the maturity this tool has gained over the years.

I work very closely with the support team and their professional services teams, and I think that Blue Prism provides very good support.

I worked with Automation Anywhere before Blue Prism.

The initial setup is fairly okay in comparison. With Blue Prism, I could configure all of the types of configuration that Blue Prism supports. Whether it is single sign-on, app server-based, database, or single login, it was all quite simple.

Blue Prism has a higher cost with respect to RPA enablement, particularly if you are trying to start with RPA. If you are a middle-scale company, then the cost of robots and their overall infrastructure can become really huge. You would feel like this is really a costly affair to start with RPA.

So, Blue Prism has a higher cost if you are talking about middle-scale companies. However, if you're thinking of having more than 50 bots or 100 bots, perhaps this will have a lower impact on your cost. In general, Blue Prism is costly.

If an organization is more focused on internal automations which belong to their own infrastructure and they want to comply with their security requirements, then I would recommend Blue Prism.

If, however, an organization wants to really move forward towards the cloud and towards intelligent automation and integrations, then I would definitely recommend UiPath.

If you want to build your team, look for a person who has development background because of Blue Prism's implementation. It follows object-oriented concepts, where you create your object, which is like a reusable class or reusable artifact.

Even with regard to processes, you have to really think of developing them or writing your automation in such a way that it complies with what has been designed in the objects. I think a developer mindset is very much required for developing automation through Blue Prism.

Overall, I would rate Blue Prism at six on a scale from one to ten.