What advice do you have for others considering Blue Prism?

Nowadays, nobody is willing to do custom coding; in Blue Prism also, we can inject any kind of C Sharp code and Python code as well. So, it is better to ignore those things and automate processes with more drag-and-drop features. By skipping the coding part, it will be easier for other people, like senior members who don't have a coding background, to learn about the solution and find it interesting. I would rate Blue Prism a nine out of ten.

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.

Blue Prism provides a comprehensive set of resources, including a university with numerous courses, to help users develop their skills. The courses are very clear and provide step-by-step instructions on how to use the platform. With these resources, one can learn Blue Prism on their own without any external assistance. I would rate Blue Prism a nine out of ten. Blue Prism is a great enterprise platform. Although it started with version six which had many user interaction tools, I recently read about new features that allow for interaction between robots and users to complete tasks. Overall, I think Blue Prism is a reliable platform for enterprises.

I rate Blue Prism eight out of 10. It's a good option if your automation team has that kind of budget. It is scalable and easy to implement. You can create lots of boards, but each will have separate licenses and require more resources or on-premise servers.

My advice would be first to assess your requirements. If you prioritize reliable security, Blue Prism could be a good choice for you, but it may come with a higher development cost than other vendors. Additionally, if you choose Blue Prism, you should ensure that integration is streamlined by developing your own code. When it comes to business, the process assessment should be critical in finding the right solution. Not all processes are suitable for automation, and there is a risk that ROI may not meet expectations if the process is not suitable. It's important to consider the required equipment and ensure the solution is designed to handle potential issues, such as offline support. The solution should also be designed with the expectation of needing support once deployed. During development, it's important to follow best practices to ensure the solution is efficient and has a high ROI. It's also important to ensure that the solution is reliable and does not break. Manual intervention may be necessary if there are any issues, so it's important to have a plan in place for business continuity. Overall, I would rate Blue Prism a seven out of ten because it has stability issues.

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

If someone wants to start using Blue Prism, I would suggest that they start learning database configuration, Object Studio, and Process Studio. I rate this solution a nine out of ten.

I rate the solution a seven out of ten.

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.

I would rate it a seven out of ten.

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 would rate this solution 7 out of 10.

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.

It is a pretty good solution. I would rate it an eight out of 10.

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

My advice to others that want to use this solution is to develop and invest in their R&D team. I rate Blue Prism a seven out of ten.

I'm actually not a technical person, I'm actually more of a finance person. I'm a business user. I'd rate the solution at an eight out of ten. I'd advise potential new users that they need to take an actual use case, an actual business point, and do a pilot on it first to visualize how the solution could potentially work. If they find that it's satisfactory, then perhaps they could work on other rollouts. The key is to develop more on the user experience side of things.

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.

I'm a customer and an end-user. I'm in a position within our company where people are saying to me, "We've got Power Automate from Microsoft, why should I use Blue Prism?" And with the Microsoft suite, Power Automate, and all of the cognitive automation is already included as part of Azure. And here I sit with Blue Prism, and now I need new gateways to integrate with that. It's going to be a little bit more work to make it work with Microsoft Azure than the product that is already there in Microsoft Azure. I must now basically justify to the business why do I need Blue Prism. It makes it very difficult in terms of their strategy if all the extra products that we want, we have to buy additionally. Whereas, if I compare it to the Microsoft Azure Suite of things, you get all of these features without having to buy them separately as you would need to with Blue Prism. It's a very difficult sell to the business. I would advise others to go straight to the cloud and not mess around with the on-premise solution. The reason is the on-premise solution will take you six months before you can start to show anything. Going to the cloud is probably a better option to get the results out faster. I'd rate the solution at a seven out of ten.

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.

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 would recommend UiPath because it is easier to use and faster to implement. But if a company has budget limitations and because UiPath has more licenses, if you want to acquire Orchestrator, for example, it requires another license. Blue Prism gives you a license for a robot, then a license for everything else. If there are no strict limitations on budget, I would recommend UiPath.

We're using the latest version of the solution. I'd recommend the solution to other companies. That said, companies should venture out and try other tools as well. You want to compare to ensure you're getting a comprehensive solution that covers your needs as an organization. I'd rate the solution eight out of ten.

We will keep on using this solution in the near future because we have invested in this, but I wish to go for Automation Anywhere, and down the line, we might be exploring that. It is currently not a fully-grown application, whereas many features in the Automation Anywhere are full-grown automation features. The Blue Prism sales team gave us a demonstration of the upcoming features a couple of weeks ago. They are coming up with a lot of features that are currently not there. I would recommend this solution only if the features they have planned in the upcoming version are there, and they are stable. Blue Prism currently cannot be compared with other products such as Automation Anywhere and UiPath. The full-grown kind of bot is something that is relevant for RPA use cases, but it is not there right now. It is there on the roadmap, but they have to take care of the stability. Right now, other products have definitely got an edge over this. Without considering the roadmap and features that they have promised in the next version, I would rate Blue Prism a five out of ten.

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 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.

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.

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.

I would rate Blue Prism an eight out of ten. It is a good tool.

I would rate Blue Prism an eight out of ten.

I would recommend this solution to others who are interested in using it. I would rate this solution a seven out of ten.

You should suggest a tool only after you study the architecture of an enterprise. Every tool has its own features, upside, and downside. It is not about necessarily going for Blue Prism, Automation Anywhere, or UiPath. For implementing a solution, you definitely need to look in the market to find out what suits you. You can then go for it. Blue Prism, Automation Anywhere, or UiPath are on par. There is not much difference in those tools at an enterprise level. The early development cost and the cost of the platform differ in these three tools. There are some clients who say that "We want only Blue Prism. We don't want to look at anything else." In such a scenario, you can definitely go for Blue Prism because it is on par with other competitors. The biggest lesson that we have learned from using Blue Prism is that it is important to choose the right processes and the right complexity of the processes. You can't choose highly complex processes where you have around 800,000 steps or very volatile processes where the team is involved in the application layer or at the process level very frequently. These kinds of things could be avoided. I would rate Blue Prism an eight out of ten because it is a very old tool. It has been around in the market for quite a while, and they have their own learnings. It is a complete package at an enterprise level, where you can have analytics and attended and unattended automation. You can run your scripts, and at an enterprise level, even security aspects are very strong as compared to what is generally required by a client. There is room for improvement. All the new features that are coming up are not being used by many clients, and a lot of learning has to happen.

We primarily use UiPath, and we also use Blue Prism and Automation Anywhere. UiPath, Blue Prism, and Automation Anywhere are the three leaders in RPA. We kind of make sure that we include all the pros and cons. Blue Prism provides a lot more reliability and security as compared to others. That's the reason it is still in the game. I would rate Blue Prism a seven out of ten.

Try to think of standard automation questions related to security, change control, and things like that before you get started because once you get developing, it is hard to go back and implement those things. I would rate Blue Prism an eight out of ten.

I would recommend this solution to others. I would rate this solution a seven out of ten.

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

I would recommend this solution to others. I would rate Blue Prism an eight out of ten.

I think it's very important for an organization to evaluate what kind of use cases they have: what's their roadmap and how long is the journey that they're looking at. As the market says, most organizations are looking for this digital transformation, and Blue RP is only part of it. For any organization that needs to adapt to a digital transformation, automation RP does play a good role. They need to evaluate what exactly they want to do and then engage with Blue Prism about how to go about doing it. Remember to always bring in the experts in the market at the beginning of your journey, and work together. That helps a lot. On a scale from one to ten, I would give Blue Prism a rating of seven.

I don't think that I could recommend this solution. I prefer working with UiPath.

My advice is that not all activities can be automated by using Blue Prism. There are certain levels of criteria that need to be calculated before choosing a particular RPA tool. There are things that need to be considered before choosing economically. In the next release, I would like to see improvement in cognitive abilities, AI, and document processing. I would rate Blue Prism an eight out of ten.

I would rate this solution an eight out of ten.

The suitability of this product depends on the use cases. For example, if you are looking into processing invoices then Blue Prism is not the tool that I would choose because the others have better OCR capabilities. If document processing capabilities and a test suite were added then it would be great because our customers who need these features would not be forced to use other products. If I were to rate this tool in isolation then I would score it a six or seven out of ten. However, as I am comparing it to other similar solutions, I have to score it less. I would rate this solution a four out of ten.

This is a good RPA product and definitely one that I recommend. When I want to automate stuff with the web site, perform web scraping, or interacting with Excel and SAP, it is quite stable. The bot does not just fail. Once you capture the underlying application control, it's there and will not just break. I've seen other RPA tools wherein you do the automation, do the recording, and once you replay it, it doesn't work because of some random lag in the timing of the application. Similarly, if something changes then it may not work. In Blue Prism, you have complete control over that. Overall, I would say that this tool is very good. It is one of the best in the market. I would rate this solution an eight out of ten.

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.

My advice for anybody who is implementing this solution is to have some expertise in-house, and not rely solely on the vendor. Similarly, I don't think that it is a good idea to develop and manage your infrastructure based entirely on advice or direction from the vendor. This is the first RPA tool that we have implemented, and we do not have a lot of experience with other tools. We are satisfied, but there is room for improvement. I would rate this solution an eight out of ten.

For anybody who is implementing this solution, it is important that you do not implement a process that is inherently flawed. Especially for more complex processes, you have to figure out how to solve those and re-engineer them. You want to enhance the processes. Secondly, ensure that your design team is allowed to complete the design and move onto the next process. You do not want to have them repeatedly called back to enhance the process, because that slows down your rollout strategy. You need to get buy-in from the business around what you're going to automate, and how you're going to do it. That is how you're going to leverage it going forward. If you don't have that then you can automate and put bots out there, but if the business doesn't support them or doesn't adopt them as co-workers then you're going to be battling against scaling. Anybody who sets out on this journey should be looking to use them on a large scale, and not just as a point solution. I have not used other solutions so it is difficult to compare. However, in terms of support and the ability for us to start using the solution, it was quite easy. I would rate this solution an eight out of ten.

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

If you need only server-side back-end process automation, use Blue Prism. If you need assisted automation or services automation, use Automation Anywhere or UiPath. On a scale from 1 to 10, I would rate Blue Prism with an 8.

We performed quite a few POCs to help understand the platform. One of the most important things while working with RPA is choosing the right process, understanding the process, and ensuring that you pick the right process for RPA activities. That was the key to our success. The process should not be too complex, and not be too simple. If it is too complex then it will take too much time to implement. At the same time, it should cater to your immediate needs so that you can demonstrate the tool's features to the leadership. My advice is to do a pilot project before adopting any RPA platform. Try one or two key integrations, such as the Outlook and OCR integration that we have chosen. Another important point is that there might be some fear in the team. Some people are concerned that bots are taking away jobs. It is important to ensure confidence in the team that the RPA will not replace humans. Rather, it will enhance their capabilities in terms of resources that are being used for mundane tasks. The message to take to the organization is that bots will handle the simple tasks, while humans can do more intelligent activities. We have not fully explored the platform, but it is enough to capture our requirements. I would rate this solution an eight out of ten.

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.

My advice to those looking to implement this solution is to have a clear understanding of what RPA is. Some of our clients are confused between RPA and AI, so before planning to implement any automation, they have to have a full understanding of what RPA can do, and what the limitations of it are. This solution does not have support for attended robots. Most of our solutions are for unattended robots that perform unmonitored tasks. In some of the departments, they have a need to automate tasks that are in front of them, and without this feature, there are certain operations that cannot be handled. I would rate this solution an eight out of ten.

My advice to others would be to let them start with the standard enterprise-wide robotic automation solution. If they're looking for fewer process automation bots, Blue Prism would be incredibly expensive. They should have a ballpark figure of the number of people under the processes, then Blue Prism is an excellent tool, but if you lessen the number of processes then it's costly. On a scale of one to ten, one being the worst and ten being the best, I would rate this product around seven. Blue Prism is the same for enterprise-wide implementation but if you're considering the entire tool, technical support, implementation needs all these things; I would adjust my rating.

This is a highly scalable tool and can be used to automate various traditional business processes from various industries, be it IT, financial, manufacturing, etc.

In terms of world usage, the market slice Blue Prism has, it is only in third place now, simply because it has been lacking in certain areas. The lackluster Robotic Process Automation Blue Prism is a dumb robot, as opposed to Automation Anywhere which is capable of cognitive learning - and that's a big plus. Even if it's in a very simple manner, even if it's not an IQ Bot, there is a lot of cognitive learning that's built into the other platforms which I find much better to use. Even if you take out UiPath which is bigger - it now has a huge amount of money that was invested by Israeli investors who have pushed UiPath to a point where it has expanded to almost every country now, including trying to get themselves established in South Africa. Even if you take them out of the picture, and they are the biggest threat, Automation Anywhere, which is much younger than Blue Prism, is still way better and rated much higher than Blue Prism in terms of market share and popularity, ease, etc. If I wanted to choose a platform, depending on the environment, I would not be fixed on one platform. The companies that I worked for previously only focused on Blue Prism while others only focused on Automation Anywhere. That's the wrong approach. You should be agnostic, you should use a tool that is appropriate for the scenario. There are some things that, obviously, Blue Prism will do way better, way faster than Automation Anywhere and there are some cases where Automation Anywhere would be more suitable. For example, if you are looking into natural language processing, Automation Anywhere does a far better job of it in terms of reading an email and making a decision based on the content of the email. Blue Prism can't do that. I would also say you need to get your planning right. Once you have that right, you'll have no issues with implementation. Seek advice from people that have successfully implemented it. There are many community groups and a lot of people in the Blue Prism community, so become part of the community; there's a lot to be learned from that. Overall, it's pretty solid, it's pretty good if you want to start doing things in robotics or process automation, but it's definitely not the end of it. I would suggest that people always look at other platforms and see where they could be used in a given situation.