The scalability could be improved so is rated a six out of ten. 

In terms of scalability, I think that Blue Prism has the capability to work with a sufficient number of robots, which should be adequate for most enterprises. I haven't encountered any issues with scalability, although we have worked with organizations that have a varying number of robots, ranging from seven to twenty-one. While twenty-one might be considered a medium to large-sized organization, I don't believe that it's necessarily a small number in this context.

Scalability is good, I would rate the scalability of Blue Prism a nine out of ten.

In our organization, we don't use Blue Prism for automation. Instead, we assist other organizations with their automation needs. 

We have a team of about ten developers, which includes DevOps and other personnel who work on automation projects.

Our clients typically range from medium-sized to enterprise-level businesses. It's rare for us to work with small clients as it can be challenging to find tasks that are financially feasible to automate due to the initial investment required for setting up the robots. However, I cannot say that small clients wouldn't need RPA.

If a user has a distributed architecture, then scalability is very good. The solution can be scaled within a few days; the user doesn't have to wait for months. Around fifteen people in our organization are using Blue Prism. 

Blue Prism is a highly scalable solution that has been used by over 1000 people across the three companies where I have worked to date. As of now, 50 people are working as developers, and 200 people are working at an architect level.

The product’s scalability is quite good but not as good as Power Automate. Our developers, testers, and support team uses the solution. There are around twenty developers, three to four testers, and a ten-member support team.

We have plans to increase our usage.

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

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

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

I rate Blue Prism nine out of 10 for scalability. 

Blue Prism scalability is good. 

The requirements for deployment and maintenance differs from process to process. Certain processes take around three programmers and one solution architect and technical architect. It really depends on the project scope.

In total, we require a minimum of four to five people for deployment and maintenance. 

I give the scalability an eight out of ten.

We have around 18 people using the solution in our organizations. We have around 30 licenses to easily scale if needed.

When compared to other RPA tools, Blue Prism is highly scalable and reliable. I have deployed Blue Prism processes that required deployment for up to fifteen users per process. Due to other factors, deployment permission is needed if the workload exceeds the system's capacity. Typically, it runs smoothly without issues, but in cases where the workload surpasses our support team's capabilities, we can deploy up to fifteen percent of the portal's resources, and the system continues to function effectively even at that scale.

The solution is definitely scalable. 

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.

The scalability of the solution is good.

The solution can be suitable for all sized businesses, but it depends on the use case.

The scalability is good and I haven't seen any limitations as yet. Right now there are about 20-30 people using it in my organization.

I would rate the scalability a nine out of ten.

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.

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

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. 

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. 

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.

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 rate the scalability an eight out of ten and it could be improved.

Scalability is not at all a problem. It works perfectly well for a batch operation.

In terms of usage, we have seven users who use this solution.

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

It is scalable, it depends on the requirements. At this moment, it is scalable. In terms of enterprise scalability, I'm not sure. However, it does scale from one particular area to many areas, including accounting, treasury, payroll, et cetera.

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

It is scalable. We are using some central objects.

It is difficult to expand the use of Blue Prism in an environment. For example, if I have 10 members in my team and I decide that it isn't enough, and in response, I want to onboard 100 more people, it's difficult to do. This is related to the costs of licenses and infrastructure.

The difficult question becomes if I want to get 100 more people involved in automation, how do I scale the team?

When it comes to scalability, nowadays, it's about citizen development models. Everyone wants to use RPA, which means that any number of people might be doing it. As a center of excellence, if I tell them that they need additional infrastructure, licenses, and training to accommodate it, then onboarding 100 people is a large commitment.

Improvements could be made by supplying a URL to the website for training, creating group licenses, and using a plug-in instead of a dedicated machine or virtual machine. If we could install an agent on a machine without any license for development purposes then it would be helpful.

Currently, we have approximately 100 users.

We are actually expanding into other centers of excellence, or what we call a COE.

Due to the fact that we are a COE, the group finance, the group tech, we have about a thousand plus users at this time, and that will grow.

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

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

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

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

Is it scalable? Yes and no. From Blue Prism's perspective, it's easy: you spin up a server and start deploying your blocked runners, making sure to keep them running; but from an organization's point of view, there is a lot to do on the infrastructure side — you have to pay special attention to the infrastructure where you can run your bots. So, it's scalable, but there is a cost associated with it. Every organization needs to be very careful in regard to how they're scaling it: are you going to scale it horizontally? Are you going to scale it vertically? Are you going to scale out? These are the questions that must be carefully considered when scaling it up. Otherwise, your cost will be exponentially higher if you don't pay attention to these factors.

The stability issue is there, especially when you scale it up. If you're doing 1000 processes a minute or every 10 minutes, and then you scale it up to 10,000, I think Blue Prism has a problem with that. Guys from the banks have told me they really don't look at Blue Prism as being scalable enterprise-wide because it does tend to fall over.

Having said that, I haven't necessarily heard of issues like that in the international environment, but I have heard of issues like that here in South Africa. Having read of the success stories, worldwide, and the extent to which they've been involved in enterprise-level, I wouldn't necessarily say this issue has come to the fore.

I would rate the product's scalability a nine out of ten. 

The solution might be scalable. It depends on the process that we want to automate, actually. It looks to be pretty scalable overall, however.

We only have about 50 users on the solution currently.

We do plan to continue usage.

We have not scaled that high for any of our clients yet. We have four or five bots that have been running with no issues.

Blue Prism is scalable.

It's really easy to scale.

It is scalable, but scaling this product is a little bit expensive for us. We are based in India, and it is not fitting in the budget. To add more bots, we have to put in a lot more money. 

So far, we have automated almost 13 processes. In terms of the number of users, we have our partner and four to five technical people who are being led by a manager. I am from the client's side, and we have three people in our team. So, there are seven to eight people who are working on it.

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

My clients are enterprise-level organizations.

It is definitely scalable. The whole market of RPA is definitely scalable, but it again depends on your feasibility and complexity when you study a particular environment and process. It also depends on whether you want to scale in the whole organization or different departments or you want to scale up into different areas. All RPA solutions are on par in terms of scalability. There is no difference between them.

We have 300 resources that are using Blue Prism at different levels.

It can be maintained by three people and it can be done by our IT team as well. It is not hard to maintain

At this point, it is hard to say how scalable it is. We have more than 200 employees using it.

I rate the solution's scalability as an eight.

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

Blue Prism could be more scalable. 

It depends on how you code this.

We have managed to scale it up quite well, so scalability is ok.

There are approximately twelve thousand people who benefit from this solution. We have around twenty developers, and there are between one and two hundred people who have a direct connection to the RPA deployments.

It has good scalability.

An RPA scales as you add bots to your ecosystem.

We don't consider the number of users with respect to utilization. Rather, the solution is used by one of our departments. They have adopted RPA to handle one of its processes as a pilot project.

We have seen a lot of use cases, but it is still picking up. Not too many departments are coming up with RPA as a strategy, but I believe it will soon pick up.

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

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

It is not currently an issue on our side because the company has pretty strong and fast machines. Because these machines do only RPA and nothing else, they can handle the work of a lot of employees and do a great job with that.

We're only in the process of scaling so it is difficult to say. One of the things that the developers have said is that it's quite slow, and quite cumbersome when layered over Java-based solutions. Whether it is scalable in that space, or not, is to be determined.

We have fifteen robots running.

I have found Blue Prism is easy to scale.

Blue Prism is not suitable for small companies. They have a solution that covers partners, it's suitable for enterprises.

When you need to run more processes, you buy more licenses, but you will spin up more VM. Scaling not is a problem for Blue Prism.

This solution is scalable, but I don't have a lot of experience with this area. I am basing this only on what I have heard.

We have approximately 500 end-users.

Due to the limitations, we don't have plans to increase our usage. We are considering a change.

The scalability depends on the code that we write. For example, there are business objects as well as processes. If they are architected and coded properly then it is very easy to scale with less effort. I have no complaints regarding scalability and it is as good as other tools.

Scalability was easy.

This product is easy to scale.

We have seven or eight people in the company who use Blue Prism on a daily basis.

The scalability is dependent on the design. If the process is designed, in advance, such that the capability of expansion is in place, then it will be very easy and simple. Otherwise, it will be quite difficult.

Our client's roles vary. Some of them are developers, others are business users, and the end user will be the process controller. Some of our clients are looking into purchasing additional licenses because they are using this solution extensively.

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.

Blue Prism is designed to be scalable. You need to properly design the automation so that if you want to expand it and use multiple robots, it will work without issues. 

This is a scalable product. We were a team of 10 or 11 who were using this solution.

I have found that the scalability could improve.

We have three users in our organization who are using this solution.

We have a team of three people.

Regarding scalability, we design processes very modularly with separate object and process layers for each application. This modular approach makes it highly scalable.