My company decided to go with Blue Prism because of the security it provides. One of the other reasons our company decided to use the tool is because of our strong partnership with SS&C Blue Prism's team.

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

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

Blue Prism has improved process efficiencies. We can get some maximum optimization with ticket processing. Blue Prism provides a large variety of robots that can automate and manipulate processes with very few problems. Furthermore, we can program multiple methods within a single bot.

We manage approximately twenty consoles in the UK, and we have achieved considerable savings with Blue Prism. We were able to automate a large task using Blue Prism to verify extensions and console tax, and we have seen great benefits from using Blue Prism for these tasks.

We have a customer who used to perform certain tasks manually. They no longer have to do that as the bot performs the tasks. They only need to review whether the bot is working as expected or not. It has significantly improved their process time, and Blue Prism has proven to be time-saving and resource-saving.

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 started with a very small team and small projects. As the project started getting success with Blue Prism we have a large number of teams now just for automating all the business procedures. Larger time was saved after automating the processes.

The business was very much satisfied with the results. Many projects involving Java, Mainframe SAP, Web browsers, and Windows were made. We did also use PDF automation using OCR and Surface automation which helped tremendously as our company is payroll-based and involves lots of file processing in which the toughest is interacting with PDFs. 

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

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.

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

The whole auditing activity is run at the backend without any screen scraping activity and other stuff that generally requires human involvement. It was deployed for this purpose, and it has been working perfectly well so far. There are certain hiccups that come in between, but our team is able to handle them. So, it is mainly being used for high-volume backend batch processing.

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

Blue Prism was our first automation platform. Originally, we used version 6.2, which was very geared toward core development. You need to have some development background to develop the bots, and they were pretty much heavy in terms of the monolithic way of the solution. But from version 6.4 onwards, there became a feature known as an API call. Technically speaking, they have actually increased their capability in API calls, which means that Blue Prism has a lot of flexibility to integrate with other enterprise applications. This API feature, which is available in version 6.4, has made our lives a lot easier compared to version 6.2.

It helps us reduce the number of people involved in mundane tasks.

In the case of Absa, it has really impacted them, the way the customer interacts with the organization when it comes to certain processes. They have become one of the better banks in terms of technology now.

When having to fill out an application, for example, there's an app. In the back-end of that app, the whole process is automated. They get an acknowledgment within a couple of seconds. That is the way it has a positive impact on the organization. If the end-user or the client is happy about the way things are going now, as oppose to the way things were before, then that's a big win.

There should be permanence across all of the automation technologies, such as UiPath, Blue Prism, and Automation Anywhere. It would allow the client to have automated processing of manual data work.

Currently, we are automating all of the manual processes. Once you have the bot built, you deploy it and it is obvious that it is going to help the client with reducing the man-hours, leaving them to focus on better quality work.

This is applicable for all RPA, not just Blue Prism.

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

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

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

An example of how this solution helped us is with our ticket creation process. When a client raises a ticket with us, we receive an attachment by email. We have to first read the content of the email and then the attachment. Next, we have to identify who the customer is, and based on that, we create a ticket and assign it to the appropriate team.

By using the automation in Blue Prism, we have reduced the manual activities of somebody reading those emails, figuring out whose account it is, deciding where it should go, and creating the ticket. All of these activities are automated.

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

This solution has helped us become more efficient, as we have been able to automate certain processes, up to 85% of the work in some claims processing areas. We've been able to use it to very successfully transform data from one system to another. We have also used it for underwriting new client take-ons.

Blue Prism can lower the average handling time immediately by 20-40%.

You also need to look at what is the long term goal. A long term goal could be that you want to keep, not integrate, with anything else. 

Blue Prism has a long learning curve because the coding is complicated. You need to be a very highly skilled developer. Blue Prism has a high coding skill and certification requirement that hinders your ability to automate quickly. 

Blue Prism moves out new versions very fast and their back-up compatibility is not good as compared to their competition. Essentially, this means you spend a lot of money just upgrading the bots.

Of course, Blue Prism is capable of improving one´s processes, especially in terms of efficiency. I´m not saying that it didn´t improve things at all at my company. However, my personal opinion is that improvement is behind what´s possible nowadays. As desribed before, attended automation and digital assistants keep becoming more important - if not crucial for a company´s RPA journey. And that´s exactly where Blue Prism in my opinion fails. Developing processes, you can feel that the solution is not made for attended automation. 

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

Using Blue Prism takes away from the work required to complete manual tasks. Also, repetitive tasks that are completed using RPA are more accurate, compared to those done manually.

There has been a huge amount of cost savings and freeing up. Employees got more vacation time allotted. That was a direct result of the time saved by RPA.

We are trying to speed up the process for our client because, being in the healthcare industry, they do have a lot of defects and issues. They are working on the latest products, which have different defects and issues. Being able to speed up this process, provide information to different business people, and make things easy is the value add. These tickets are also related to claims audits, so it would also speed up the claim process.

I do not have any IT training, but I am still able to master this skill and develop Blue Prism solutions. It has a very user-friendly interface for a non-technical person.

Automating these processes enhances the accuracy of processing the traditional process without any manual interventions. These processes can be reused which proved to be cost-effective and time to market also reduced.

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

ROI and efficiency savings. 

1 FTE can manage hundreds of bots via my GP RPA design and build methodology. Master processes can easily control subprocesses, such as load, work, and report.

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