Automation Anywhere (AA) Scalability

Logeshbabu Jothy
Head Transformer at FLSmidth
I would say that scalability is a critical aspect of using RPA and maximizing efficiency. When you develop one bot. You can just use it for N number of ports with the same source code. So it doesn't require any retooling. Scalability is very high. There will be some process deviations or some nonstandard aspects associated with any process that may require rethinking and interaction. For example, maybe because of the ERP (Enterprise Resource Planning) or the different systems that we use or integrate at the time of taking over those processes, scaling may be influenced. The classic example for our company, I would say, is that we have grown manyfold by acquiring lots of companies in the last three decades. Every time we acquired new divisions or companies, it is not only about the revenue or products. We also get legacy systems or along with those entities, there will be some processes and practices which are nonstandard for our organization. We'll need to incorporate these different systems in the ERP. But scalability is always possible. With the RPA only those areas where there are differences need to be fine-tuned in your RP source code. Then you can redeploy it successfully. Beyond that, we also take this as an opportunity to evaluate processes because we don't look at the RPA project as an isolated project. It is an opportunity to grow and improve automation in various ways and not just this one project alone. Even before we automate something, we look at processes to scrutinize what are the nonstandard activities we do. We look to see if there are ways we can make the process more lean, simple and straightforward. This can actually make the process that I'm trying to automate more efficient. Then it is also easier to accomplish the development, easier to integrate with other processes, and more adaptable when you automate the process. Working this way, I know for sure that what I am automating is going to be an efficient process. So scalability is very easy and very simple to achieve especially compared training individuals in a process. A bot needs no training. Making tweakings to the source code and deploying successfully in production is much faster and easier. Because of these reasons, I would say scalability is pretty efficient and easy to achieve using RPA. We plan to increase usage in the future both in our current departments and new divisions of the business. View full review »
William "Sonny" Kocak
Sr. RPA Developer at Ally Financial Inc.
The scalability is limited more by our money and our hardware than anything. The scalability really depends on how much RAM and how much network bandwidth we can do, how many servers we can apply. I know we can just keep adding to the cluster and I know clients could keep popping up. Since we're at the forefront of this, it has not been an issue. However, I do know that, within a year, when we start having multiple clients running and we have multiple developers in there, I may have a different response. But, again, I think we would just have to add more Control Room servers and more resources to the servers. We haven't hit a scalability limit issue yet. View full review »
Automation Manager - Nordic at a financial services firm with 1,001-5,000 employees
The scalability is good. I think we haven't really used the Bot Farm product yet, but that looks very exciting. We're planning on moving the infrastructure into the cloud and it's then a very interesting prospect to be able to scale up from 100 bots to 1,000 bots with just the click of a button. To my knowledge, it's probably the most scalable RPA software out there. We haven't really met any major challenges when it comes to scaling up, other than our own computers. But that's an in-house problem, not an Automation Anywhere problem. I've talked to people using other RPA vendors and they have said they face some major issues once they pass 40 automated processes, but we haven't really faced those kinds of challenges. It has been running smoothly. It's very scalable and it's easy to have control. There is a good audit log in the Control Room. And there is the ability to create your own roles and have strict, role-based access control where you say: This role is able to run this bot on this machine but it's not able to run another bot on the same machine. That's good from a security standpoint. View full review »
Find out what your peers are saying about Automation Anywhere, UiPath, Blue Prism and others in Robotic Process Automation (RPA). Updated: January 2020.
398,890 professionals have used our research since 2012.
Priya Batish
Business Advisory Manager (AVP) at Accenture
Scalability is just scaling up the number of bots, so scalability is not a problem. You can increase the number of machines and number of bots to scale up the solution, but it can be sometimes very cost prohibitive. E.g., typically, it requires a dedicated machine, and it can't be a shared environment. This can be a bit of a constraint in terms of the number of machines being used. Otherwise, the solution is completely scalable. In case the process requires more throughput, you can just increase the number of bots which are working. Also, if you are doing this properly, then you have to make sure that there are not multiple bots running at the same time which might be at cross purposes. View full review »
Sharad Soni
Director Of Innovation at Quantum AI
I'm not yet happy with the scalability of Automation Anywhere. Scalability is good up to about 100 bots. Beyond that, I need to spread it into multiple sites, which means there is additional licensing cost. View full review »
Director of Operations at XLNC Technologies
Other tools tend to give me exceptions when I am scaling them on the cloud. While the infrastructure might be available, systems won't be able to talk to each other. The codes tend to miss paths, and sometimes codes are not getting applied in the application. However, with Automation Anywhere, we haven't seen any such issues until now, wherein large scale developments are being found to be unstable. The good thing about Automation Anywhere is the website has a detailed architecture which talks about having a load balancer and how you can scale up. Currently, I have been working with clients in the US and Dubai through remote support. I have been developing bots remotely where I have been able to access their virtual machines. The virtual machines are separate for creators and runners. I have around six creators on virtual machines, which is good enough to start off. There are around 25 runners which are deployed on 25 VMs. This is in US. That's how we are operating them, and it's the largest setup that we work on. In India, clients start small. They start with a starter pack, which is only allowed to be issued by an implementation partner. If you go onto the Automation Anywhere website, there is nothing called a starter pack. So, organizations will tend to start small with a starter pack, which may come in a bundle of two or three creators, one runner, and one controller. They want to test how it is functions in their organization. If they can pick up low hanging fruit, which means if they're picking processes which are smaller but high in volume, then they will have higher ROI. Then, these organizations tend to jump onto an enterprise level deployment in a maximum of six months. That is the trend that we have seen. However, the moment the client starts going big and is not able to get the right ROI in place, that's where they tend to start dropping the ball. Then, they start looking for another RPA software or decide RPA is not for them. View full review »
Guruprasad Belle
AVP at a software R&D company with 10,001+ employees
From the scalability standpoint, I don't think there will be any issues except for the increased costs which could prohibit some companies on a limited budget from scaling. So technically it is pretty good, but there may be some restrictions or interference in budget or integrations. We are using one or two bots that are running continuously. View full review »
Technical Lead - Robotics at a tech services company with 10,001+ employees
Automation Anywhere is definitely scalable in several ways. It's easy and accessible. It's designed the best — almost perfect. It has many more usable components than I was familiar with, and I had so much to learn. Now, with some experience, it is not foreign, and we just don't need to build to get what we want. But to get that you need to start at the design phase, you should not start at development at all. People try — even me — when you're starting, just to aim at building usable components. We can ask a developer to do that, but then the developer will not design to build a reusable component. It will only be specific to his assignment, the development, his process, and he will get it done to complete the job. Scalability starts with a designer who is the one who makes the call. They need to know what to standardize or how to do things by thinking globally to make sure that a resolution is usable and adaptable if desired. That is the standard we adopted. Other big companies have more bots compared to our 50. They may think what they have is a lot more scalable than it is. View full review »
Kalyan Bitra
CTO at Sage IT
With scalability, from what I've seen when we visit some of our customers, they don't look at how do you optimally run the bots. You can run bots left, right, and center at the same time, even though there is no dependency required. That is where the stability of the automation level is great. But, if you deploy it in the wrong way, the stability would be impacted. For example, running multiple bots on the same VDI, you don't have to do it, nor do you have to tie a bot to one VDI without multitenancy. Those are some of the challenges that we've seen and can be addressed. View full review »
BPM Analyst at a financial services firm with 1,001-5,000 employees
The scalability is good. It is very easy to scale. It doesn't take us hardly any time at all if we need to spin up a new Control Room or Bot Runner. The slowest part is probably on our end, getting the hardware. It took us two years to scale from pilot to the number of bots that we are currently using. I wasn't involved in the early days of the PoC. I came into the group a little later after that, but now, we use a federated model. We were sort of the center of excellence for it, working with our business partners. In a number of cases, our business partners are now developing their own bots. We have developed some, where the business partners didn't have much of an interest to doing the development. They wanted to be involved in the creation, so they understood it, but they didn't want to do any of the coding in the background, so we do it for them. We do all the production support. I like to go by actual executions, not number of bots, because we have some bots that need to be executed multiple times during the day. Last time I looked, we were well over a 100 different executions in a week. View full review »
Venkata Sreedhar Nalam
Technical Architect at a financial services firm with 10,001+ employees
We are using it on a pretty large scale. We currently have close to 60 bots running in production, but in the coming couple of months, we will scale up close to 120 bots. We have plans to scale up much larger, then eventually move to the cloud. That is in our roadmap. A big problem that we are facing with the tool is that it is not scalable. For example, we have processes that are going to run for 36, 40 hours. It is running as a single trigger. Currently, Automation Anywhere doesn't support multi-trigger. For multi-trigger, you develop a solution once and install in multiple machines and run parallel. AA doesn't support this so we had to do workarounds to make that achievable. We also got a tool from Automation Anywhere that was supposed to fix or patch a problem, but it didn't work. It was a horrible, pathetic product that they brought out when it wasn't ready. We had such a very bad experience using the extra feature. We worked with Automation Anywhere to get it to function. They also said that they don't know that the tool will work if you set it up because someone developed it and he left the organization. That feature is still not there in Automation Anywhere. Even in higher management, they instructed us not to use that feature, even for basic functionality. That's how bad the product was. I just discussed it with one of the product owners about the same, and they also kind of agreed that the solution was brought out prematurely. In all, they wasted our time on something that did not work. View full review »
Abdul Subhan
Senior Automation Engineer at Ryan india
Automation Anywhere is an excellent example of a solution that scales up. When we develop a task we modularise it and upload it into the repository. If another team member is working on another project and they require a section of my bot then it then gets downloaded and modified. Somebody else plugs in the variables, etc. In this way, the scalability is great. At the moment, there is no setup in place. We don't have a Citrix environment. It's mostly web-based. We also have in-house built applications that we use for our day in and out operations. View full review »
Process Architect at LinkedIn
The product is definitely scalable. A lot of it will depend solely on the architecture of the organization who is implementing it. If you are using on-premise servers, it is much harder to scale up versus if you are using cloud-based architecture. Automation Anywhere provides the tools and expertise to make it scalable. At the previous company that I was with, we had a pilot in September 2017 with approximately 20 bots. Then, in production, it took nine to ten months. With the organization that I'm currently with their process took a little longer, but they were standing up their COE initially. So, they went from pilot to about 30 bots in production. This took roughly a year and a half to two years. With regards to process, there is a lot involved. If you want to have a successful RPA and Automation Anywhere implementation at the ground level, you need to lay the foundation and the framework. Therefore, you need to build your center of excellence, and make sure you have dedicated people who will focus on whatever their role is: People related to support, governance, development, architecture, oversight (who will work with your security teams to get your reviews done), and IT personnel (who will provision servers and licenses and do control room administration). There is a lot involved to take it from inception to a successful program. View full review »
Principal Analyst at a Consumer Goods with 10,001+ employees
As far as being able to scale our usage of the product, until now, we have been doing well in diversifying. In the future, we expect to be able to get more from the tool. Our ultimate goal is to use the tool to automate most of our internal processing and reap the benefits of RPA. Multiple users are currently using the product. View full review »
BPM Analyst at a financial services firm with 1,001-5,000 employees
The scalability is easy. Installing license keys, bringing up new Bot Runners, and all that stuff from the Automation Anywhere side of it are easy. It's very easy. I've had little-to-no difficulty doing any of that. I have to go through the paperwork of hardware, VDIs, etc, and that's all on our side. But, from an Automation Anywhere standpoint, it's been very quick and easy to scale. View full review »
Shashi Pagadala
Manager of RPA Development at CommScope Holding Company, Inc.
When I talk about RPAs, it is to say, "Can this problem be solved with RPA?" Scalability-wise, we are in good shape. In terms of AI incorporation, this type of scalable incorporation would be benefit everyone. The trend looks like we are going to reach to this point in a good manner. We were able to put more than 40 bots into production. There are around 20 more in progress. On average, we were able to save around 25,000 hours of manual efforts. View full review »
CEO at Nine A Business Connect
Scalability is huge. I have seen organizations who don't want to invest big during the initial phase, even if they have a big appetite to deploy hundreds of bots. They normally start with five or 10 bots. The best part about Automation Anywhere is you can start with five, 10, 50, 100, 200, or 300 bots. Today, the Control Room can manage 300 to 400 Bot Runners in a single architecture. So, organizations don't have to worry that after a 100 bots they won't have to do another architecture change or shift the entire environment here or there. They can keep on adding bots and keep scaling their organization to hundreds of bots. You can configure bots to do multiple tasks in a series or in batch mode, depending upon the type of task. Ideally, when you assign a job to the bot, it will try to finish it. But, if there is some parallel processing required for some business requirement, I can make a few bots do the job parallel, then I can take over from where the other guys left off. That is another ease of Automation Anywhere. Bots can be configured the way you want to perform your operations. View full review »
Business Transformation Manager at a maritime company with 10,001+ employees
It seems pretty scalable. We're looking into scaling up in the near term. The pool seems pretty scalable and good to us from what we've seen so far. We currently have six or seven processes that we've automated using Automation Anywhere and we're looking to increase that number quite a lot here in the U.S. We have a prioritized list of another 50 or so tasks that we'd like to try to automate with the solution. In addition, we're working to generate interest among some of our other agencies and countries worldwide, in using it. View full review »
Technical Lead at Verizon Communications
As of now, we are migrating from a Micron database. Once we have completed that, we believe the scalability will be a cakewalk. We have almost 500 bots spread across different portfolios. They are scheduled and running on daily basis. We did not integrated this solution with any other applications. This is running as a standalone thing in our environment. View full review »
Gurvinder Singh Dhaliwal
Director at Goldensource
Right now, we have one Control Room and two bots. In the next coming weeks, we'll be putting four more bots and our second Control Room into production. We plan to use the second Control Room in a development role. After the four bots are complete, we will start creating bots for the IT and finance departments. View full review »
Vice President & Head of HR - L&T Defence at a tech services company with 10,001+ employees
Scalability-wise, they have increased it a lot, based on the clustering method. As a technical architect, I'm going with always-on production and data centers. That means that if any data center goes down - there is a natural disaster or something else that happens - how do you make it such that you can bring up another data center? I'm coming up with a design for that based on the latest version, version 11. View full review »
Technical Analyst at Tesco India
We have 50 bots live in our organization. We have three environments: staging, pilot, and production. In staging, the developer creates and tests their bot for internal testing. After that, we deploy into the pilot environment. That is hypercare which is for User Acceptance Testing (UAT). It is there that we run the bot in unattended mode for one and a half weeks at least with huge volumes. If we have no issues nor errors, then we create a ticket to deploy into production, our center of excellence. This is what our support team does. They will deploy into the production environments. We keep an eye out for at least 10 to 12 days as hypercare. At 12 days in hypercare mode, if we are not getting errors, then we run it in unattended mode as much as we can. We are using Automation Anywhere in our business units. We have plans to increase the level of the tool's use. We are planning to move onto the cloud, but first, we have to see if it will work with our business SLAs. If it is good, we will move over. We need to do a test first to determine whether the bots work well or not, which will take about three to six months. Then, we will make a decision on whether to move over to the cloud, the A2019 version. My team is excited for this version. We would move over to Microsoft Azure because our company is already using it. View full review »
Mahaan Pai
IT Analyst at Tata Consultancy Services
I feel the one thing which I can tap to enhance the scalability of the system is the AI component of Automation Anywhere — that is IQ Bot. I think this is something which can really grow into a massive Bot solution with great advantages. I heard recently that the accuracy of that data reading for invoice processing is something like 70% accurate currently. I think they are trying for 90 or 90 % plus as a goal now. View full review »
Country Head and Controller at Evalueserve
We have seen results, and the results are good. But, it will take me another couple of quarters to answer on the overall scalability and consistency of this bot. View full review »
Senior Director, Digital Transformation at a financial services firm with 501-1,000 employees
We're not really there yet, in terms of scaling, but based on the high-availability issue, right now I'm not too confident. From everything I've heard, though, it seems like people are running hundreds of processes on a Control Room, but we haven't really done enough to know about scalability. View full review »
Abhineet Sood
Consultant at Zs
Scalability is an important aspect of it. We believe they have been doing it pretty well. Earlier, we were doing everything as an on-premise implementation. Later, we moved to an AWS environment, hosting everything on our cloud machine. This helped us scale the whole solution and reach our multiple clients in projects that we were engaged in very quickly. We believe the A2019 version is meant to scale the tool to a larger audience. View full review »
Brian Walling
Global IT Director at a logistics company with 501-1,000 employees
We didn't have to scale too far, so we didn't experience its scalability. View full review »
Matthew Wilde
Director of Shared Services at iHeartMedia
We're a small user, so we haven't had any problem with scalability. We've talked to a lot of people who have used it on a much larger scale. For us, it's very easy to add TaskBots. We're more than satisfied with the scalability. We're always looking for expansion of the solution within our company. We use most of the commands available. There are very few that aren't applicable to what we're doing. We're always trying to get the solution into other departments within the organization itself. We use it a lot within the shared services, the area which we own. But outside of the company, we have several projects that are not within the shared service and we're always looking to talk to the other departments and get them involved. We have 25 bots, meaning 25 licenses. Our core team that does development has four people plus a project manager. View full review »
Kyoichi Haida
GM Business Process Planning Dept at a insurance company with 10,001+ employees
It is highly scalable. At the time of implementing this solution, we thought that the scaling might be challenging if the setup process took a lot of time. However, it turned out to be very scalable because, by segmenting, it can also be applied to other new business processes. In addition, it can be done without engineers or system engineers. It does not need to be developed, but we do need to set it up based on rules. The cost for scalability is much cheaper than developing a new system. View full review »
Prateek Kapoor
Global Intelligent Automation & Transformation Leader at Juniper Networks, Inc.
Scaling is very easy. We were able to scale it up very easily. For 2018, we thought of doing eight projects, but we completed 25. We're definitely planning to scale up, but scaling up does not depend on Automation Anywhere. It actually depends on our organization's strategic plan, and how fast we want to do it. As an organization, we want to be a tortoise in the journey, rather than being a hare. We want to have a consistent pace of implementation. Initially, we were like the hare and did some extra implementations, but now we are trying to match it up with the pace of the organization. Sometimes, too big a change can rock the boat, which we don't want to do. But equally, we were able to demonstrate that this application can do wonders for the organization, help us to digitally transform the way we're working, and introduce a new way of working to any organization. Now, humans have started adopting bots as their new team members. View full review »
IT Analyst at a manufacturing company with 501-1,000 employees
From the current setup that we have, I'm not sure how much we can scale up. We had an initial PoC and our first go-live was less than a year ago, so we haven't had those discussions on what it would take to either increase by one or two servers or 20 servers, or what that would look like. View full review »
Nachiketh Ramesh
Associate Consultant at a tech services company with 51-200 employees
Scalability is very good, except in the case of IQ Bot. IQ Bot has problems with respect to scalability. As an example, consider that you want to upload one thousand POs per day. You have two machines, and you want to split the work, but there is a problem. IQ Bot is going to put the output into the same output path, but how do you know which machine has generated this output? How do you map it? This is an inherent flaw that hinders scalability in the long run. IQ Bot doesn't even let you know whether an output has been generated. They have a database, and I built a custom bot to look at their database to find out if the output has been generated, or not. However, people have told me not to touch this database because it is proprietary. The other point with regards to scalability is that it doesn't just happen out of the box. You do not just add a hundred more machines and have it work in the same manner. You need to use it in tandem with an SQL database, or another application like Tableau. If you do then it will be very strong and very robust. It will be loosely coupled but highly scalable. View full review »
Automation Lead at Universtity of Melbourne
We've gone down the Reagan approach, which was referred to in the session earlier today, where we essentially started out with that low hanging fruit. We built confidence within the business and from there, it was quite an easy sell because it was quite obvious to the business that we could deliver and could deliver fairly quickly. In terms of scalability, we've had to grow the team slightly. It's really important to have the right team. You need someone with a lot of experience around the tool. From there, you can bring in a range of skill sets, including SMEs. We have SMEs on the team now that don't come from an IT background or development background. By having that range of skills, we've been able to sort of up the velocity of releasing bots. We could always do better though, and we're still learning. View full review »
Director of Business Process Improvement at a pharma/biotech company with 10,001+ employees
We are pleased with Automation Anywhere's ability to scale. We are convinced that it is a platform that we can scale, and we are convinced that it can function and operate within our environment. We have six-plus use cases in production today. But those business processes are very complex. They are touching many systems. Our definition of a bot is a business process, not a task. Some companies call a bot a task. We don't do that, we call it a business process. We have six business processes that are running, which are very complex in nature. Regarding the scalability of a single business process, we have found that to be very easy. We have found Automation Anywhere to be very friendly when it comes to that. We add capacity in the form a virtual machine and a license to scale and meet the needs of the business. View full review »
Chinmay Dhabal
Application Developer Analyst at a tech services company with 5,001-10,000 employees
We code our bots with tasks and subtasks in such a way that we can easily combine them when new features come up. View full review »
Scott Francis
CEO at BP3
As a partner of Automation Anywhere, I view it as part of our job is to create scale problems for Automation Anywhere to solve. To make the solution big enough that it finds those edge cases. We haven't had any problems with scale and stability with Automation Anywhere, so I hope to create those problems, then work with Automation Anywhere to solve them. View full review »
Senior Consultant at Ernst & Young
I can introduce IQ Bot. I can introduce my Python script that I'm trying to work on. If I'm not able to make it with an Automation Anywhere, I can go out-of-the-box. I can try to build in my own programming language where I have expertise or I might not, but in this way, I am putting it across different scripting mechanism and running it the same bot. This is something which I think is very good and we can scale again to a different level with different use cases. View full review »
RPA Developer and BA at a financial services firm with 10,001+ employees
If you look at our shared services, we are growing and we need to keep our costs flat. This means I cannot hire more people. This need for greater efficiency is made up by what I have been able to gain out of the automation. We are actually using automation to move more processes into our shared services. Ours is a private business and we create big cement plants. One project could last for five years. When we land a big deal our volume spikes. It's a very cyclical business. It has been very easy for us to deploy scalable solutions now. View full review »
Bill Weathersby
Board member at Transform AI
If you write them correctly and have good architectures internally, then scalability is relatively straightforward. This also applies to reliability. However, you sort of need to write a few before you get to this point. As more of these go to production, these are going to be the two big drivers. Probably one of the faster scales that we have done is we did a prototype with IQ Bot that had about 500 invoices and a 1000 vendors. In about two and a half to three months time, start to finish, we went from the original amount to 15,000 invoices and 2500 vendors. I would suggest in that 90 to 120 day time frame, if you have done things properly and your architecture is good, that you should be able to scale at any pace that you care to. View full review »
Engineer at a healthcare company with 10,001+ employees
To scale from pilot to the number of bots we're currently using went pretty quickly. I have talked to other teammates who are working on Automation Anywhere and developing the bots. I've heard really good feedback on that. It's within weeks, and sometimes days, depending on the complexity. Doing a simple password reset went really fast. If they are doing something on an OTC process or a P2P process or integrating with SAP, it will be a long process. First, you have to get approval from all the business owners and understand the process. That takes time. But the technical aspect - once you have everything in place and you know what you are going to do - the coding itself, is pretty fast. View full review »
Software Engineer at The Travelers Companies, Inc.
Scaling has gone remarkably well too, the ability to literally just spin up another bot. We have a collection and we'll add a couple more and no big deal happens to the scheduler. It has worked well. To scale from pilot to the number of bots we’re currently using has taken about two years. We did a lot of experimenting before we committed to it, but once we got through a couple of those experimentation projects, we were able to form a team, figure out exactly what we were going to have to accomplish from a business point of view, and dive in. After those couple of pilots, it took about a year from when we initially startied playing with it. There was a little bit of getting our feet wet, feeling comfortable with it. But now, we have several teams and it's working great. View full review »
Senior Consultant at a financial services firm with 501-1,000 employees
The scalability is fine. You can create small, repeatable tasks. You can expand through different bots. So, you don't have to recreate the same stuff. Automation Anywhere provides the facility so you can reuse components to make a scalable solution. We are improving scalability on a daily basis, as RPA is new to us. Our code is now more scalable and reusable than we developed our basic structure. Going forward, if we have to create a new bot with any given scenario, it will take 20 to 40 percent less time to create. This is because we have already made the scalable, reusable components. View full review »
Product Owner of RPA at a mining and metals company with 10,001+ employees
We are now scaling it up on the operations side for people literally sitting in the mines. They want to use Automation Anywhere for their day-to-day operations. That's the next scalable area that we're looking at. We have developed a competency within the team as well as with our partners but we are at a juncture where we want to scale up. We are figuring out how we want to do it. One of the discussions that happened in today's forum was the different operating models we can have: a COE, business unit, or federated model. Today, I'm having calls with couple of Automation Anywhere guys to understand the best fit for us. That's how we will decide how we can scale up. We have the potential but we need to do it in a manner that can be sustainable over a period of time. View full review »
Deepinka Singh
Developer at Yokogawa
The scalability is great. Nearly a 100 bots have been deployed in finance, HR, and mostly engineering. We will be implementing bots going forward in procurement. It has taken us two years to scale to our current number of bots because we spent a lot of time on training at first. View full review »
Sagakumar Gangipelly
Sr. Software Engineer at Ryan India Tax
Currently, I have developed between 20 to 25 bots. From when I started, we have deployed as a team between 30 to 40 bots. Their status is as fully running on our client machines. View full review »
Tax Technology Partner at Ernst & Young
I think we have more than 50 clients who use our solution at this point. So, the scalability of the platform is well proven. Every client is looking at scalability because they don't want to do just one or two processes. But, you will not be able to realize the value if you just limit yourself to a limited set of processes. So, the scalability is a very important task for clients. But there are certain challenges in scaling up. To be able to identify the right use cases that bring value is huge and very important. Secondly, the technology infrastructure can be challenging if you scale up because you always have to add new servers to scale. That has always been a challenge. Having said that, I think what we heard today from Neil, there's a cloud version available that will be easily scalable. That is extremely exciting as a developer. That will be able to address a lot of the scalability issues that we've come across from our clients. View full review »
Reginald Christian
Head IT Operations and Infrastructure at a consultancy with 10,001+ employees
In terms of scalability, you have to leap frog forward. Overall, you need to work at achieving a digital workforce to scale the entire landscape of the organization by having them look to the future. It is not only the RPA part, but also you have to adopt AI and ML type technologies which can holistically cover the entire aspects and take the organization to the scalable level. View full review »
Rajeev Mall
Finance Head of BSO Senior Group Division at a manufacturing company with 10,001+ employees
If you ask me, my personal belief is you can’t even begin to imagine what you can do. You can imagine, but you are limited by your own imagination and thinking, so you can go exponentially. View full review »
Dimitris Papageorgiou
Partner at Ernst & Young
I think it's a very scalable application as well, but I think the scalability is not just tied to the technology itself, it's also the organizational appetite to go fast and go the right way forward. The huge component of that is talent, and I think Automation Anywhere, with the internal consultants that they make available to clients on occasion, does accelerate the adoption. From a pilot to scale, I would say the couple of clients that I've actually worked with took about six months to one year to get to what we would consider a repurchase point, but I wouldn't necessarily call that scale. The model that we bring forward to clients, at least in the past, was one where we actually teach them how to fish versus fishing for them, so we're not necessarily there to see them all the way through scale. We're there to see them through stability. View full review »
Henry Parrot
Automation Consultant at Neuralify
I have a very positive impression of the scalability of Automation Anywhere. The Control Room enables you to take an automation that was built once and have it be deployed in a very effective way. View full review »
Ayas Mohapatra
Automation Officer at a financial services firm with 51-200 employees
Considering the automation that we have done, we have not been required to scale. View full review »
Pratyush Kumar
Delivery Manager, Robotics Process Automation at a retailer with 10,001+ employees
We are still small from a robotics implementation standpoint. We are just about 20 bots right now with no issues. If we scale up to 500 bots, I am not sure how the infrastructure and systems will behave, but I have had a good experience from a scalability standpoint on the tool so far. I have a team of about 25 people with six people in support with the rest in development. At any given time, we have more than 50 people running Automation Anywhere. View full review »
Madhuvankumar V
Senior Software Engineer at EMC Corporation
Scalability is very good. Compared to others, Automation Anywhere is on top. We have more than eight hundred developers in our company, and most do not have a technical background. View full review »
Brian Dsouza
Sr IS Manager at Amgen Inc.
We have them implemented in a cloud-based environment. Cloud by itself allows you to scale. As long as the software works there, it allows you to really scale. To scale from pilots to the current number of bots that we are using, it took three to six months. That was the time frame. We started pilots on some functions, and learning from our pilots was key. View full review »
Finance Process Automation Lead at a manufacturing company with 10,001+ employees
Scalability is dependent on the organization and customer size, but it's a stable platform. We have not faced issues as we have scaled up. View full review »
Kumaran Dayalan
VP of Corporate Finance at Refinitiv
The product is scalable. Obviously, scaling the solution requires some time for development. Whenever you identify something that can be automated or want to work on something that already exists which is similar but slightly different than what you need, it requires time. So there is time expenditure involved in scaling, but the solution is definitely scalable. We have about 11 accountants working on it. View full review »
Dona Manuel
Technical Lead at Titan company
As far as scalability, it is one of the most important things for us. We were looking for that only when we went to upgrade our process. We want to automate any of the processes that we can by using Automation Anywhere. It is the whole point for us using the product. View full review »
Gopalkrishna Baskarabhatla
Architect at Cisco
We have already launched more than 20 bots live into production. They are up and running. We are doing very well with these. We are in a convenient spot for delivering 50 to 60 more bots in the next couple of quarters. Because it can accommodate 200 to 300 bots, the scale is not a constraint for us. It is scalable. View full review »
IT Project Lead at a financial services firm with 51-200 employees
Our first business unit who started their journey two years ago went from one bot initially to about 55 over a two-year period. Typically, they were averaging a new bot about every two to three weeks. That was with a team of five to six people sort of dedicated to the process. We have had consistent growth with our numbers over that time. View full review »
Business Transformation Manager at a maritime company with 10,001+ employees
So far, it's scalable. We have four developers doing the developing in Automation Anywhere. We set it up so that things are triggered automatically by somebody putting a file in a folder. Right now, we have seven bots in production for seven departments. The four developers handle deployment and maintenance of the solution. We're looking to increase usage of the solution. We're doing a workshop in a few weeks to bring a lot of our managers in to get them thinking about things that exist in their areas that can be automated. View full review »
Senior Consultant at Ernst & Young
This product scales easily. You can just plug-and-play with whatever components you want to use. You can just add in things easily and you can scale it up. View full review »
Avinash Nyamati
Senior Analyst at Merck KGaA
We are a midsize company in the Indian market running one or two bots. From a scalability perspective, I don't think there will be any issues. It is pretty good. View full review »
Service Delivery and Operations at a pharma/biotech company with 10,001+ employees
We have more than two hundred and fifty licenses, although they are not all currently in use by the bots. View full review »
Sujay Ghosh
Team Lead at Accenture
It is definitely scalable. It is very flexible when it comes to scalability. I have had projects in which the total benefit was about 12 FTEs across the globe. We would start off with 0.5 FTEs when we went into live production. Then, we started onboarding other countries or regions, and getting roles onboarded was pretty much seamless. Scaling up is a good thing that Automation Anywhere has for it. View full review »
RPA Developer at a consultancy with 1,001-5,000 employees
What we're trying to figure out right now is how to scale this. That's where the hardware comes in. For the most part, scaling with the application is more a matter of building the infrastructure around it. To scale from pilot to the point where we are now, where we're developing three or four bots every two weeks, it took us six months. A lot of that was trial and error, creating our standards, and hiring developers to whom we could pass the projects. View full review »
Suneel Sharma
CRO at
The clients whom we are approaching and want to get onboard have a huge application requirement. So, we are requiring that these applications are well suited for the Automation Anywhere product. We feel that there is a lack of trained professionals in the market. Therefore, we have a branch where we can train people, so they can scale up into our application's deployment. View full review »
Ronaldo Firmo
Automation COE Manager at a mining and metals company with 10,001+ employees
Scalability is associated to the number of bot runners purchased. More bot runners can be purchased at any time depending on how the demand grows, and AA offers the ability to process bots in a platform called bot farm. View full review »
Sachin Chitranshi
Senior Consultant at Ernst & Young
Scalability is a trend we are experiencing in IT. We have to have a scope for a project and we have to create a scope again in the future millennia. So I'm waiting just to see the functionality of the additional features in this package. View full review »
IT Consultant at ITC Infotech
We have IQ bots. In IQ Bots, they have the option of uploading around a maximum of 150 documents at once. So, if your organization is generating some PDFs or images on a daily basis, maybe it's hundreds of documents, you can upload them at once. You have to train IQ Bot for one of these documents, then it will automatically take for the rest of these documents. It will easily map all the keywords and extract all the exact information that you want. That is important. View full review »
Assistant Project Manager at a tech services company with 201-500 employees
The scalability of this solution is very good. We have operations on the other side of the world, such as South East Asia, so we tend to have different languages. The IQ Bot is able to read these languages, which will help us to expand into other regions, as well. View full review »
Architecht at a insurance company with 1,001-5,000 employees
The scalability is good. We started with very few bots and it was quite scalable. We now have about ten Bot Runners. View full review »
RPA Lead at Juniper Networks
We are not using it to its full scale. We have deployed only nine bots in production and two in development. We are only using three or four bots completely. Rest are going unused, so we are not looking to scale out anytime soon. View full review »
Consultant at Deloitte
I'm impressed with the scalability. We are able to do changes. We are able to scale from different environments now with the Control Room in version 10 and 11. The scalability is pretty good. It is up to the mark of the other market competitors. View full review »
Sr. Manager at Tata Consultancy Services
I don't think that we will have any challenges with scalability. We started in a small way and I'm sure when we really require it, we will be able to scale. View full review »
Senior RPA Consultant at a Consumer Goods with 10,001+ employees
I haven't found any scalability issues with it. If the volume increases tomorrow, another bot can be added from the Control Room. I worked with a single deployment model, which didn't have a load balancer requirement. Higher availability deployments require load balancers. View full review »
Cognitive Lead at Quosphere
We initially started off with a customer who had just three bots. We've now scaled them to 15 bots. It didn't take us more than an hour to scale. Automation Anywhere helped us scale from one bot to 100 bots within a period of hours, if not minutes. Unless you're scaling from 10s to 1000s, I think Automation Anywhere has it covered. View full review »
RPA Developer at a financial services firm with 10,001+ employees
The scalability is perfect. It is a reusable product. We have around 200 bots in the entire company. We have allocated separate systems for these bots. We have almost 350 processors that we have automated using the bots. View full review »
Saurabh Soni
Manager at Ernst & Young
If you have 500 digital works for an enterprise, then someday you will need to update. Automation Anywhere is not very scalable because the update and upgrade process requires immense effort from the IT organization to do a tool check. Automation Anywhere Control Room should update to the newer versions with one click, including the newer features. There should be minimum effort required from the IT organization. The major resistance from any organization is from the IT organization because they have a lot of dependencies and will sometimes resist doing changes because they have other activities and applications to manage. Future versions should minimizing their work. View full review »
Sunil Ranka
Founder at Predikly
This product has pretty scalable so far. The number of customers is growing year over year. People are deploying hundreds of thousands of bots. We haven't hit any scalability issue at this point in time. View full review »
Jayadeep Keeripunathil
IT Manager at Accenture
We started off with this showcase piece. Now, we are going into details regarding how we can scale. Can we scale it horizontally? Can we just start putting VMs on it? So, these are the factors that we are assessing right now, but we feel that it is scalable. View full review »
VP IS Global Development at a manufacturing company with 1,001-5,000 employees
We're still pretty small, so we haven't had a need to scale out too much. We have seen the roadmap for scaling out, and it doesn't look to be too difficult. So, we should& have a problem with it. We have only had the tool for about eight months. From start to finish, we have put over a dozen bots in place, some of which are highly complex and took a lot of weeks to properly deploy. View full review »
Senior Manager at a tech vendor with 10,001+ employees
From pilot to production, we scaled our last bot in about nine weeks. It was a very interesting process because the building deployment can be done pretty quickly, but if you don't narrow down the scope early, you can face a lot of challenges. I don't think this necessarily has to do with the platform. It is more about understanding and narrowing down your scope from the beginning. It's okay to add more functionality later, but that adds delay to your overall timeline. However, being that it's very easy to configure the bot and add components to it, this is one of the benefits of building with Automation Anywhere. You can make changes pretty quickly. With everything, you will have to be careful and not get caught up always making changes. You have to really narrow the scope down quickly and build it in very small components. Don't build everything end-to-end. Break down your processes, as much as possible, and deploy as little functionality as possible. This makes it way more easy to manage. It is also a much better way to build a bot. View full review »
Rakesh Rajagopal
Automation Leader at Hexaware Technologies Limited
In terms of scaling up, we have not had issues with bots which are in production. In UAT, there have been scaling issues. But in production, as long as a solution is good, then it works. View full review »
Ravi KantMahendru
Program Manager - RPA at a tech services company with 501-1,000 employees
It's a good to some extent. We faced an issue where the IQ Bot was very unstable. There were out days, but it's just good their support team is quite helpful. Whenever we set up new environments, we may face these type of issues. However, these are technical challenges which we might expect from any tool. These are new things for everyone, even for Automation Anywhere. Initially, we faced stability challenges with the IQ Bot server, but now those are stable as compared to previous versions. View full review »
Program Manager at Yokogawa
We are just in the path. This year, we are trying to do ten times more than last year. We are trying to do about 100 automated processes this year. I have confidence that the solution is able to cater our needs. View full review »
Systems Analyst at a manufacturing company with 10,001+ employees
Nothing is stopping us to increase our scalability. The scalability is good. View full review »
Developer at CommScope Holding Company, Inc.
It's a scalable product and process. We've been using it for a long time. There are few products in the market, out of which we chose Automation Anywhere because it suits our company very well. We have a scope of expanding the process and bring new teams in to be involved in this as well. View full review »
Sangameshwar Biradar
Assistant Professor at Gitam
This is a scalable solution. View full review »
Joel Samuel
Manager at Tata Consultancy Services
Scalability is awesome and on par, but they could do better. View full review »
Kunal Goel
Digital Expert at a consultancy with 10,001+ employees
Scalability is good. It's one of the better ones. View full review »
Baskaran Chidambaran
RPA Specialist at Olam International
Scalability is up to the mark. We have been building our solution from the low to high level. It is scalable. View full review »
Deepika Bale
Specialist Quality Operations at a pharma/biotech company with 10,001+ employees
We had had issues with scalability. Recently, we had a use case which we were working on, but we could not do it because Automation Anywhere could not connect to the system. It was an older system, and perhaps the newer systems are more compatible with this solution. We have seen a few companies that use downgraded systems, and that is where we see that Automation Anywhere does not work. View full review »
Amrit Goswami
Automation Developer at
The scalability of this solution is good compared to others. View full review »
Sunilkumar Venugopal
RPA Solution Architect at Olam International
For scalability, we are still working on the bot utilization framework and have created additional frameworks apart from the existing automation framework. View full review »
Gagnish Relhan
ETL Analyst at Teleperformance
The scalability is pretty impressive. You can scale it from one computer to hundreds of computers. You don't even need Citrix. Once it is on the cloud, you can access it from anywhere. View full review »
Head of Automation at a comms service provider with 1,001-5,000 employees
Scalability works fine. One of the key features that we chose, the bot as a service or the BotFarm, when they launched version 11.3, they decided not to have the BotFarm anymore. This put us in a situation because we expected to have bots on demand, just like our cloud software. This would have been cost efficient for us to use. We hope to see this again being realized with A2019. I hope the scalability from an on demand basis improves. View full review »
Software Engineer at Accenture
We have so many use cases. When customers come to us, they'll ask for a very simple use case, they will not know the features of Automation Anywhere and what we can automate. Once they get to know it after we automate one process, they will want more features which they'll ask for. They'll give us more use cases for us to do. We have done many bigger tasks. If the customers are doing it manually, it will take them 12 to 24 hours. But, if they're doing it through Automation Anywhere, it will done in half an hour to an hour. View full review »
Global Head Training at Acronotics
I don't think there were any challenges. Everybody who wants to do RPA can start very small. They do a PoC, build a few bots, and then they scale up. I don't see a challenge as long as you have the right people doing what they are trying to do. A lot of use cases in our organization are only two to three bots initially, and now, they have 40 to 50 bots. So, I don't think there is an issue in terms of scalability at all. View full review »
RPA Lead at Volvo Construction Equipment
It is a very good scalable product because the MetaBot provides a feature where we can reuse our code for whatever we have developed. We can use it in different areas with the same code. It is reusable. So, it is a scalable product. View full review »
Consultant at Ernst & Young
Scalabilty is good. View full review »
Senior IT Design Analyst at a retailer with 1,001-5,000 employees
The company started the pilot a year and a half ago. That phase was probably six or seven months. Then, it took a little over a year to get it up and running. We also did an upgrade to the newest version, and that took some time. Overall, it took about a year to scale up our bots. View full review »
Sunil Ranka
Founder at Predikly
In terms of scalability, we haven't been in a situation where it has been a challenge for us. We've been able to scale to what we need. Having said that, we haven't deployed thousands of bots yet, but for the bots we have done we've been doing great. To scale from pilot to the number of bots we're currently using, took us between eight and 12 weeks. View full review »
Technical Lead at a manufacturing company with 10,001+ employees
We intentionally took a long time to scale up to our current number of bots because we focused on using large processes, instead of small ones. For us to grow to scale, it took us about a year and a half. However, we have been focusing on processes with tens of FTEs per year, instead of about processes that are one to two hours per day. View full review »
Developer at ITC Infotech
It's scalable. The analytics are very powerful. We can give the customer what has happened with the bot, how much time it ran, and how much time is ideal. All this information, we can easily show how successful it is, how much our productivity it is giving to them, and what ROI they're getting at the end of the year. It's pretty easy to go with Automation Anywhere. View full review »
Kumar Animesh
Senior Technical Consultant at Fujitsu India
The scalability is good. View full review »
Automation Architect at Tata Consultancy Services
We face issues when we need to increase volumes. Currently, it is failing for some reason, and we don't know the reason. It fails or stops, then we need to see what is going on. We have to fix that, then our developers need to rerun it. These are mostly practical challenges for our team who uses it on daily basis. View full review »
Saketha Krishna
RPA Architect at Sage IT
We are implementing complex solutions in health planning care, HR, and banking, so there are a lot of things that you have to consider when it concerns data and the information. Sometimes we get an error where the port will hang, or the solution will change over a period of time, but generally, the solution is scalable. I would rate scalability an eight out of ten. View full review »
RPA Developer at Accenture
There have been problems with scalability. It comes down to how we handle the code. It should be handled properly, then there shouldn't be any problems. View full review »
Dhaneel Shanthpure
Founder and CEO at Digigro
Technology for scalability is very powerful because we are using Amazon AWS. You can take scalability for granted if your algorithms are properly working. View full review »
Automation Lead at Accenture
Compared to other RPA tools, I think Automation Anywhere is very scalable. For example, we have written simple applications where they do one thing today, but tomorrow they may add something else to it. They're developing an additional, or expanded version of the bot, and it is always simple. In this way, the scalability is pretty good. The only problem we've had is when we need to expand the userbase. This is because of the ports attached to it. View full review »
Project Manager at ANZ Banking Group
We have been looking at processes which can easily transition into a large scale environment, where you can have cloud or hybrid model. However, being a bank, some of our processes are critical and we would like to hold those on-premise. This limits us with our usage of Automation Anywhere. View full review »
AI and RPA Practice Head at In2IT Technologies
Scalability is also great. You automate one process and replicate it again and again. For example, one of our clients has global operations. What we automated in one country, we were able to implement around the globe. We were also able to just keep on adding on new virtual machines in a given location, to have more and more processes automated. It's easy to scale. View full review »
Masaru Ogawa
Assistant to GM, IT & Business Transformation Division at a manufacturing company with 10,001+ employees
The capabilities for developing similar tasks are there and it's relatively easy to do. However, to accomplish that we’d need a group of IT engineers. That’s where we are not up to par. View full review »
Senior Manager IT Department / Corporate IT Planning at Konica Minolta
It is very scalable. The structure is a client server, so we can expand the environment quickly, if needed. View full review »
Chief Architect at a financial services firm with 10,001+ employees
The initial pilot was for two processes, which took us about four months. Then, the other processes were more extensive, so that took longer, only because we needed to do more with the process documentation, not so much in the bot creation. It just depends upon the complexity of the process, but also how well-documented your processes are. View full review »
Director Solution Architect at Ally Financial Inc.
We started out with three production bots last year. From the time that we were deploying them into production to being able to use them in a production mode, it took somewhere between four to six months. View full review »
Senior RPA Developer at Ernst & Young
Scalability is easy with Automation Anywhere if you are on a cloud platform. They have a built-in feature for queuing so you can scale your product. It's a workload management feature so if you have fewer volumes than you can run on one or two bots. If you have a larger volume, then you can scale up to any number of bots. Scaling up or down works in real-time. View full review »
Eric Dalton
Business Apps at New Jersey Resources Corporation
We are only running three bots, so we haven't had to worry about scalability yet. We built the tool to handle about 30 bots. So far, we haven't had any problems with scalability. It took about six months to scale from the pilot to the number of bots that we are currently using, but the majority of those months were wasted on our upgrade issue. View full review »
Associate Consultant at KPMG
It is very scalable. If we come to the point where we need to increase the number of bots in a process, for different countries or teams, we can add multiple bots and Bot Runners to the process, then we can execute. This gives a lot of scalability to the process. View full review »
Rahul Sualy
Director at a manufacturing company with 1,001-5,000 employees
Once we got the tool going and were fairly familiar with it, we were able to scale the solution. Our developers love it. It is fairly simple to use. Sometimes, we are able to even bring people on fairly quickly, like interns, and have them use the software. Then, we are able to see some real benefit out of it fairly quickly. At pilot, we had around four bots. Today, we have 85 bots, and that is over 12 to 13 months. View full review »
Project Manager -Learning and Development at Accenture
This is a scalable solution that is robust and will help to take us forward. View full review »
Manager - Finance at Sterlite Power
We quickly moved from one bot to 15 to 20 bots in about two or three months. I've seen other companies do even better and go to around 500 to 600 bots. So, scalability is something which is pro for Automation Anywhere always. View full review »
RPA Consultant at ITC Infotech
The IQ Bot is pretty good. We can run maximum 150 documents, save them, and automate that process. That's quite good for me. View full review »
Amrutabandhu Choudhury
RPA Consultant at Dell
This is a scalable solution. Cross-platform is the only problem. We have no plans to increase our usage at the moment. View full review »
Ravindra Kumar Muduli
Senior RPA Developer at ViS networks Pvt Lmt
I will give 8 out of 10 scale rate. View full review »
Prabir Roy
Manager at Eli Lilly and Company
Scalability is good, although it would be better if they supported more than just Windows machines. View full review »
Asif Hussain
Senior Project Manager / RPA Architect at Royal Cyber Inc.
Manually, I have worked on adding/scaling bots, but I need to work on cloud availability, possibly discussing scaling with cloud providers, like AWS. For different processes, the scaling time period is different. For some processes, we could develop bots in two weeks, then go to production with one or two bots. For other processes, it could take three months or more. It varies based on the process. View full review »
Sankarlal M
Consultant at Deloitte
The scalability is really good. View full review »
RPA Developer at a financial services firm with 201-500 employees
Our scalability has been increased with our new version. We do not see any issues. View full review »
RPA Developer at a pharma/biotech company with 10,001+ employees
Scaling is easy. We can have one Control Room with 10 bots working simultaneously, which is very good. View full review »
Luis Romero
CIO at Binary Technologies Inc
We have worked on several different projects, so far. From prototypes to production, on average, scaling our bots takes somewhere from three to six weeks. View full review »
Farid Karmadi
Site Operations Coordinator at a retailer with 5,001-10,000 employees
As of now, we have it limited to one process. However, we can scale the solution. It can cascade onto multiple processes, so that is a positive note for scalability. We are just in the initial phases. I personally have created about three to four bots. View full review »
Principal Analyst at a Consumer Goods with 10,001+ employees
I think the scalability of the solution is very good. We don't have any problems enhancing what we do except for the time in programming and troubleshooting. View full review »
RPA Program Manager at Agility
All the RPA solutions should be scalable, but I do see version 11.3 as a scalable solution that was provided. Most on the developer side don't have the knowledge on how to do the queue, as that is case management. Or, the scalability without touching the core. I do see that- So, I am expecting Automation Anywhere to share this type of knowledge with the people, then it will be a real, scalable solution. View full review »
Bruno Rocha
Workforce Coordinator at a mining and metals company with 10,001+ employees
It took us three months to scale from pilot to the number of bots that we are currently using. We started by experimenting with a very low number on the license: two Bot Runners and five Bot Creators. Now, we have 60 Bot Runners and 35 Bot Creators. We are improving as we are seeing new opportunities. View full review »
Punith Venkatesh
Consultant at a tech services company with 501-1,000 employees
It has very good scalability. We can implement across all domains. We have deployed bots in very few cases internally, like five to six bots. We mostly deploy bots for clients and their purposes. In these cases, we have deployed more than 500 bots from our ASD to the client. View full review »
Project Manager at a manufacturing company with 10,001+ employees
It has a scope for increasing which is what we are targeting. We are having sessions in our organization where people are coming up with more use cases. View full review »
IT Director at Extreme Networks
The architecture allows us to scale. We are still working to get it to a right level of scalability for our environment. View full review »
Tech Lead at a tech services company with 501-1,000 employees
As we have a small number of bits in production on version 10.5.4, we found it easy to scale. Version 11 will provide a load balancer, making it easier for us to run a pool of VMs to complete a task. We mostly use it for operations right now. We are looking at possible IT RPA use cases. View full review »
Chetankumar K
Lead Consultant at a tech services company with 501-1,000 employees
I have no issues with the scalability. For a current client, we have deployed easily around 100 to 120 bots which are running in production. View full review »
James Luxford
VP Automation at Genpact
Scalability is about the right approach. It's not just about the technology, it's about the people, understanding the processes, putting everything in place to make sure you monitor and govern your bots. Scalability is not a problem as long as you're approaching it correctly. We can scale from the bots to the pilot to the bots we're using very quickly. It can be a handful of weeks. Depends on the complexity of the process. We like to get things out there quickly because if it's going to take six months, then the business is going to go off and do other things. Our target is to get it done in a number of weeks. View full review »
Neethushree S
QA in RPA at a pharma/biotech company with 10,001+ employees
The processes that we have chosen in the initial phase are limited to certain regions. We have categorized them to phase one, two, and so on. Once phase one is good to go and we get good results out of it, we have plans to scale up to phase two, then so on. We have categorized the processes into regions, like Asia, US, EU, etc. Going forward, we will be implementing globally. View full review »
Sr Manager at Wipro Technologies
Scalability is one of the best things about most of the RPA bots. Once you create one, scalability is just about multiplying them. We've not had challenges with scalability, given we provide the right infrastructure. View full review »
Solution Manager at Deloitte
I would like to see improvement in its scalability. While workload management is a nice feature, from a practical usage and client usage standpoint, we would like to see improvement. We usually start a pilot automation with a single Bot Runner. Then, based on volume, we will increase it to two. Afterwards, we'll increase exponentially from there based on volume. View full review »
Senior Manager at a pharma/biotech company with 10,001+ employees
Every year we are improving, and the scalability is there to match. Our platform equally matches our skills. View full review »
Senior Associate, IT at a financial services firm with 201-500 employees
The scalability is pretty easy. It is pretty intuitive for any IT person to scale their environment. View full review »
RPA Developer at Verizon Communications
We have built many bots. It is good to use the best practices when developing them. For example, we add logs and error handling to each bot, so if it is not working, then we can see why. This helps our developers a lot. It took us two to three months to scale up from our pilot to the number of bots that we are currently using. What took time was our business people needed to be educated on bots and their capabilities. View full review »
Senior Vice President and Digital Leader at Genpact
The time it takes to scale bots depends process to process, how complex the process is and if you're talking about a specific process. It may takes anywhere from around three weeks to 15 weeks, depending upon the complexities, the number of bots which we are deploying, and the problem these bots are solving. View full review »
User at a tech services company with 10,001+ employees
We are currently scaling our bots and as a platform, it is very scalable. View full review »
RPA Developer at a manufacturing company with 10,001+ employees
Automation Anywhere is very scalable as to the costs and benefits to the company. I have already created 15 to 20 bots already. I think they're running well today. View full review »
Harish Bennalli
Senior App Developer at a financial services firm with 1,001-5,000 employees
It is scalable. Since we have only had it one year, we are still looking into the scalabilty factor. View full review »
Operations Leader at Ernst & Young
It is definitely scalable. What we found worked for us to make it scalable was it has to be programmed by an architect, as opposed to letting it just be in the hands of the masses trying to solve it. This has been our approach. It took us eight months to a year to scale from zero bots to 100. View full review »
Associate Manager at a pharma/biotech company with 10,001+ employees
This solution is scalable. View full review »
Manager, Administrator of Strategy Team at a software R&D company with 51-200 employees
We only have four machines for the development and actual work. Once we are done with the development, we will implement it in groups. At this point, we don’t know about its scalability yet. View full review »
Bvs Siva
Architect at Cognizant
This solution scales based on licenses and the number of processes. The bots, themselves, are very mature and can scale. The bots are plug-and-play. View full review »
AA is the easiest and the best when it comes to scalability. View full review »
Jayaraj Pachiyappan
Senior Analyst at EMC Corporation
Because I am using an older version, I am rating the scalability as a seven out of 10. I feel a lack of convenience when I try to scale it. When I use an upgrade version of Automation Anywhere and I don't feel this anymore, then I will rate the scalability better. View full review »
RPA Business Lead at World Bank
It provides high scalability. You can implement this across any industry, any sector. It took us about one year to scale from pilot to the number of bots we are currently using. View full review »
Payal Handiwala
Automation Architect at Moody's Corporation
With scalability, it is all about the frequency. I can have the bot run 24/7 or I could have the bot run on weekends. In terms of scalability, it definitely works faster and more than a human does. View full review »
Will Haskell
Supervisor at a energy/utilities company with 5,001-10,000 employees
It scales pretty well as long as you have enough developers to scale it with you. We can scale the bots in about a year. When we started, we went from a pilot of about 14 bots, which all got stripped away. Then, we ended up implementing 30 different bots about a year later. View full review »
Senior RPA Developer at Ernst & Young
It is a very scalable product. With the market, every time and every day, we can scale it. View full review »
Automation Developer at Schlumberger
It is scalable. In version 11, scalability has a limit, but with the upcoming version, it will be scalable because it is on the cloud now. View full review »
Chief IT Architect at a consultancy with 10,001+ employees
It took one to one and a years to scale to our current number of bots. View full review »
Manager, Business Process Integration at a manufacturing company with 501-1,000 employees
Our first bot took ten weeks to create. It took six months to create the number of bots that we are currently using. View full review »
Bhaskar R
Sr Site Operations Coordinator at a retailer with 5,001-10,000 employees
The scalability of this solution is really high. You don't think of it as a process, but rather, part of a process. Once you automate the individual parts, you tie everything together. View full review »
RPA Developer at Ernst & Young
It depends on the developer and how they have coded it with respect to scalability. However, it has the ability to be scalable. View full review »
Shreyas Natesh
RPA Developer at Merck KGaA
For the version that I have and what I'm using it for, the scalability is very good. View full review »
Business Technology Analyst at a consultancy with 5,001-10,000 employees
It is scalable. We try to build something on one system then repeat it on a client system. View full review »
Navinkumar Sadasivam
Quality Analyst at Accenture
The scalability is good. View full review »
Vikram Chitale
Process Leader Purchase to Pay at Eaton
It is pretty scalable within the functions that we have deployed. We have increased the number of transactions compared to what we started off with. We see its usability across functions as well. We can use the same bot across other functions if you have capacity. View full review »
Jian Chen
Systems Engineer at a insurance company with 1,001-5,000 employees
We went through the documentation, it looks pretty easy to scale. It took six months to scale from pilot to our current number of bots. View full review »
Jiajan Shen
Project Management Officer at FDA
So far, the bots run very stable and have little problems, we see the bots becoming more stable every day. View full review »
Consultant at Ernst & Young
This solution is very scalable. The bots do not depend on any specific system. We have more than one hundred bots in production. View full review »
Jeffery Gant
IT Business Partner at Lyondell Basel Industries
We have three bots in production. We are currently working on scaling up to 30 bots. View full review »
Senior Manager Development at a tech services company with 501-1,000 employees
The scalability is very good. I haven't had any issues. From pilot to our current number of bots, it took about two months. View full review »
Configuration Specialist at a energy/utilities company with 1,001-5,000 employees
We started with zero bots. In our first cycle, we developed around eight bots. In our second cycle, we created around five or six bots. Now, we are on our third bot cycle. View full review »
Process Improvement Manager at Bell Canada
Scaling is a big job, but it is completely scalable. A whole new team/department needs to be created in order to develop and monitor robotic process automation. View full review »
Infrastructure Manager at a financial services firm with 10,001+ employees
It is a powerful tool for scaling that sometimes makes the process seamless. It took one year to scale to the amount of bots that we are currently using. View full review »
Prabu Baskaran
RPA Specialist at a manufacturing company with 1-10 employees
Everyone uses it. View full review »
Digital Product Coordinator at a retailer with 5,001-10,000 employees
We need the solution to run without errors before we can scale more. View full review »
Siva Gangavarapu
RPA Developer at Qualcomm Incorporated
This value-add product is fast growing. We have 20 bots in production. View full review »
Technical Architect at Accenture
This is a scalable solution. For us, we will be scaling more into the future. View full review »
RPA Lead Architect at a manufacturing company with 10,001+ employees
It is very scalable. We have the solution implemented in North America and Asia. We are looking to expand the solution going forward by implementing it in South America. View full review »
Anantha Kancherla
AVP Solutions at CIGNEX Datamatics
We are scaling up, but I don't think that we are scaling correctly. View full review »
Arumugam Subramanyam
Solution Architect at a financial services firm with 10,001+ employees
Scalability is fantastic. We can build anything out of the application. Though in some places, there are limitations. Fixing those would be good. We are deployed in five different regions. View full review »
Yash Parikh
Project Manager at Nine A Business Connect
Scalability is good. There is no question about its scalability. View full review »
Vatsal Shah
Application Engineer at NineA business connect
This solution is scalable and works fine. I would rate the scalability a nine out of ten. View full review »
RPA Developer at Verizon Communications
The scalability is good. View full review »
Sreeraj Nadarajan
Service Intergration Expert at a pharma/biotech company with 10,001+ employees
It took us eight months to scale to our current number of bots. View full review »
Alexandre Dusseault
Technical Lead at a financial services firm with 10,001+ employees
With our current version, we are experiencing issues with the access of the Control Room. Therefore, at the moment, we cannot really scale. View full review »
Mohan Negi
Senior Consultant at PricewaterhouseCoopers
The scalability is good. We have five bots that we are currently scaling. We are looking to invest more in Automation Anywhere. View full review »
Aishwary Nigam
Senior RPA Analyst at TATA consultancy
Scalability is very good. View full review »
Senior Group Manager at a financial services firm with 1,001-5,000 employees
Our division took a couple of months to scale up our bots, when we were expecting it to take weeks. However, what we did was fairly complicated. View full review »
Surendra H
Head, Computer Science at Christ University
Scalability requires a lot of resources which needs a longer based goal. With a cloud-based platform, we can create bots and apply them to any system. View full review »
Robotic Process Automation Manager at Imerys
It is very scalable. We're in the process of scaling currently. We started off with two pilot automations, then we needed an engagement strategy to get people excited about it and get their ideas. Then, we needed to prioritize those ideas and go deeper into the processes. But, we plan to start on the next phase soon. View full review »
Manish Kumar
Software Engineer at a energy/utilities company with 10,001+ employees
This solution has scalability. We have more than forty bots running. View full review »
Vinay Sridhar
IT Team Lead at a manufacturing company with 1,001-5,000 employees
The product is scalable. View full review »
Software Developer at a insurance company with 10,001+ employees
We started with a complex process, so it has taken us over a year to scale our bots. View full review »
Product Manager at a university with 5,001-10,000 employees
The product can scale. It took us six months to scale to our current number of bots. View full review »
Application Lead at a financial services firm with 1,001-5,000 employees
It took a few months for us to scale from pilot to the number of bots that we are currently using. View full review »
Associate IT Developer at a healthcare company with 10,001+ employees
This is a scalable solution. We initially implemented small projects and then expanded them to a bigger level. View full review »
Manoj Baalebail
VP RPA Delivery at Genpact
Thumbs up both sides. Stability and scalability. I think these are the least spoken things with Automation Anywhere. It's been in the market for long and they have been proving this right from the start. View full review »
Director at a tech services company with 51-200 employees
It took one month to scale to the amount of bots which we are currently using. View full review »
André Scher
CEO at Auctus
While it depends on the customer, it generally takes about two to two and a half months to scale up bots for production. View full review »
Ajay Jeyaraman
Advisory at Ernst & Young
Scalability has been a pain point. The scalability is there, but there are ongoing operational issues with it. View full review »
Krishna Kishore Paraselli
Senior Architect at Verizon Communications
It is very scalable. View full review »
Vaibhav Jain
Senior Tech Advisor at Ernst & Young
It is pretty scalable, but it does depend on how you develop the bot. View full review »
Juan Polania
Specialist at Bancolombia
We are working on scaling it now. We use it with more than 17 applications. So, we work it on a very large scale. View full review »
Consultant at Deloitte
We have been able to scale ok. View full review »
Supply Chain Manager at a manufacturing company with 1,001-5,000 employees
The stability has been good, so far. It took us four months to scale up to our current number of bots. View full review »
Executive Director at a tech services company with 5,001-10,000 employees
The product is scalable. View full review »
Continuous Improvement Manager at a energy/utilities company with 10,001+ employees
The scalability is good. It took us a year and a half to scale from our pilot to the current number of bots that we have. View full review »
Find out what your peers are saying about Automation Anywhere, UiPath, Blue Prism and others in Robotic Process Automation (RPA). Updated: January 2020.
398,890 professionals have used our research since 2012.