We just raised a $30M Series A: Read our story

Automation Anywhere (AA) OverviewUNIXBusinessApplication

Automation Anywhere (AA) is #2 ranked solution in best RPA tools. IT Central Station users give Automation Anywhere (AA) an average rating of 10 out of 10. Automation Anywhere (AA) is most commonly compared to UiPath:Automation Anywhere (AA) vs UiPath. Automation Anywhere (AA) is popular among the large enterprise segment, accounting for 67% of users researching this solution on IT Central Station. The top industry researching this solution are professionals from a computer software company, accounting for 31% of all views.
What is Automation Anywhere (AA)?

Automation Anywhere is a global leader in Robotic Process Automation (RPA), empowering customers to automate end-to-end business processes with intelligent software bots – AI-powered digital workers that perform repetitive and manual tasks, resulting in dramatic productivity gains, optimized customer experience and more engaged employees. The company offers the world’s only cloud-native and web-based automation platform combining RPA, artificial intelligence, machine learning and analytics, yielding significantly lower TCO, higher security, and faster scalability than legacy monolithic platforms. Its Bot Store is the world's first and largest marketplace with more than 1,200 pre-built, intelligent automation solutions. Automation Anywhere has deployed over 2.8 million bots to support some of the world’s largest enterprises across all industries in more than 90 countries. 

For additional information, visit www.automationanywhere.com.

Automation Anywhere (AA) was previously known as Automation Anywhere, Testing Anywhere, Automation Anywhere Enterprise.

Automation Anywhere (AA) Buyer's Guide

Download the Automation Anywhere (AA) Buyer's Guide including reviews and more. Updated: December 2021

Automation Anywhere (AA) Customers

Google, Linkedin, Cisco, Juniper Networks, DellEMC, Comcast, Mastercard, Quest Diagnostics

Automation Anywhere (AA) Video

Pricing Advice

What users are saying about Automation Anywhere (AA) pricing:
  • "Our pricing a year ago was $600 per license."
  • "Additional costs will be for the machines and the number of machines that you are using. You can deploy virtually as well as on physical machines. In both the situations, you do need to allocate a certain budget for securing the machines and where the software will be installed and running. The machines cannot be used for anything else, because only a certain bot can run at a certain time. You need to be very particular about your scheduling of running the bots, and while the bot is running nobody can use the machine. You cannot have an agent working on a machine and the bot running in the background. It has to be completely dedicated. Then there are the network bandwidth requirements and space requirements, which are additional costs apart from the licensing and software costs. The developer is also going to charge you for their coding time too."
  • "The pricing and licensing are definitely moderate to costly but easily recoverable by achieving ROI quickly."
  • "I really enjoy the pricing options with Automation Anywhere, as they are able to flex their ability to adapt to the needs of the customer really well."

Automation Anywhere (AA) Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Priya Batish
Business Advisory Manager (AVP) at a tech services company with 10,001+ employees
Real User
While the platform is feature-rich and easy to use, it is the skill of the coder that determines how well the platform is leveraged

Pros and Cons

  • "There are multiple levels of cloning. In case screen cloning doesn't work, you can do object-based cloning or keystroke-level cloning, depending upon what parameters are available to you and what is the level of information that you capture. You can traverse between object cloning, which is the lowest form of cloning to a stroke-based cloning, which is like taking care of each keystroke-level which is made by the agent."
  • "My experience has been that if the person who codes the bot is not very well-trained, then they might create unstable bots. So, it's not the platform. It is just how somebody has coded the bots which can bring lot of instability to them. I recommend that when you are using a coder that the person well-trained and have a good amount of experience already working on bots. They shouldn't be newbie or beginner who comes in to code because that will impact the quality of the code itself."

What is our primary use case?

Most of our automation happens on Automation Anywhere

While the automation is being done, we use it as a platform. Then, depending on the number of users/ bots needed, we apply  for the corresponding licenses.

The good thing about Automation Anywhere is that any process:

1. Which is repetitive, rule-based, and only requires you to do collect/ edit information on the application frontend can be automated. 

Therefore, Automation Anywhere makes for a good use case. 

2.Wherever the process is  deterministic, with no decisions to be made, you can use it. 

It can automate any processes where 

3. Process is well established, standard, or stable, and there are not many changes in the process. For example, a simple task, such as logging into a website, launching a website and doing systematic steps on the website, can easily be captured to Automation Anywhere.  I see lot of applications, especially in finance and accounting domain.

You might have a lot of steps where you need to either extract data, repeat data, or collect data. All of those processes can be automated through RPA, and especially Automation Anywhere. You can use even automation from the server side, not just websites. The only constraint is that the process should not require human intervention and decision making.

How has it helped my organization?

We see the application in the 

# BPO space, 

# Finance and accounting, 

# Health care in terms of claim processing.

E.g. in F&A, if you're doing invoice processing where the entire process is manual, and the analyst has to go through the invoice to determine invoice details, discount on the payment  or a penalty should be levied. In such cases, you can scan this information through an OCR, which is an optical character recognition tool. Then, the rest of the information can be pretty much retrieved by the RPA, which means the RPA will scan the information to classify this information and fill up the  web form. This will be sent to the ERP. This is how the workflow would look like. 

Wherever you can put

# a rule-based system, you can automate all of the processes. In our company, all these processes are manual and you might have 50 to 60 people supporting this process for a mid-size company. You can automate it and almost reduce the manual effort by almost 40 to 50 percent, depending upon how many techs are enrolled and what is the effort being spent in order to process transaction volumes.

I have been familiar with a couple of projects where this was implemented in cash applications or invoice processing, and they could automate these steps. So, I'm familiar with some of the back-end processes and where they are getting automated.

What is most valuable?

#1.You don't have to really code anything, as it gives you a good interface (UI), because the components are already preconfigured, you  have to just a drag and drop sequence in terms of how you want to execute the steps. 

#2. There are preconfigured APIs that can be used. E.g., if you want to interact with the mailbox solution, you can have the RPA fetch attachments or email body from the mail solution. You can process attachments via test file or PDF. You can even make Automation Anywhere work around PDF, which is typically not that easy to work with in terms of extracting information.

#3. Metabots/ IQ Bots: One of the features, which we have not used too much, but available, is the MetaBot feature. These preconfigured solutions are easily downloadable, and you can just plug-and-play with a bit of customization, which also means you do not have to keep recreating and can reuse existing functionality. Some of the typical uses are that you could be regularly logging into a website. You can just download a MetaBot, as a useful webpage interface and just run it. All you have to do is maybe replace the name of the website, and in case there is a certain authentication mechanism that is being used, then provide that information.

# 4.There are multiple levels of cloning. In case screen cloning doesn't work, you can do object-based cloning or keystroke-level cloning, depending upon what parameters are available to you and what is the level of information that you capture. You can traverse between object cloning, which is the lowest, most basic form of cloning to a stroke-based cloning, which is like taking care of each keystroke-level which is made by the agent.

What needs improvement?

#1 Exception Management and Notification: When you are making a code, and there is a happy path and exception management mechanism, it would be nice if there was feedback in terms of whether this is the most appropriate way to code this. I'm not sure how this can be done, but that could be very insightful. It already gives you some screen tips, but this could be done in a better fashion, in case you are creating the workflow and then you believe a beta workflow is available or could be done. If a screen tip could be given to the coder for this sort of workflow, this would be a much better feature for Automation Anywhere. 

# 2 Type of Cloning: I've realized that sometimes when screen-level cloning is a better option, people still use object-based cloning. It would be useful if Automation Anyone could give you tips recommending fewer steps or fewer areas of exception management after you inputted your code. I'm not really sure if this is doable from a technical standpoint.

#3 Debugging: Currently, I believe the debugging of bot is a bit tricky and not very elegant, you might have to keep re-running the script to be able to identify the bug. This can be looked at, as a possible area of improvement. 

#4 Scheduling:There are two modules: the run module and the control center. In terms of scheduling and triggering, they could make it a bit more helpful and provide suggestions, e.g., if you are scheduling it, and there is a conflict, can you resolve it this way. Maybe you can get an upfront alert or something to that effect. 

#5: Stability, Workaround and fall back mechanism: When  bot breaks down, is there any of mechanisms or notifications that can be given? You can possibly choose to notify people, typically in organizations people are pretty much adverse to automation. If something breaks down, they would like to know at the earliest given opportunity that something is breaking down and piling up. They want to be able to resolve it quickly. If the resolution is going to take time, they want to be able to make some specific workaround mechanism kick in. If a bot breaks down, immediately the fallback mechanism should work too. If there could be information in terms of  when the process was out of range and somebody might need to take a look at what has happened. This is because most of these business processes that get automated are critical in nature and might have financial and operational impact. People need to know that there are working fine and not broken down. It can really have an adverse impact if they break down and nobody knows.

#6. Platform Training: My experience has been that if the person who codes the bot is not very well-trained, then they might create unstable bots. So, it's not the platform. It is just how somebody has coded the bots which can bring in lot of instability to them. I recommend that when you are using a coder that the person well-trained and have a good amount of experience already working on bots. They shouldn't be newbie or beginner who comes in to code because that will impact the quality of the code itself.

For how long have I used the solution?

I have been working with Automation Anywhere for the last three years at two different companies.

What do I think about the stability of the solution?

# Business process stability: Before robotic automation, the business process itself should be stable and very well-documented. Also, anytime a change is made to the process or subprocess ensure, that the RPA gets updated too. Typically, the entire process of automation might take some time, then by that time, the initial business process might have changed a bit. There could variations in terms of volume or in the process itself.

The most important thing is that before you automate something that you must make sure that it is stable, in its steady state for whatever changes might be upcoming over the next six month to year. Otherwise, you might create a bot, which will go into production,  and fail because the underlying process itself has changed.

# Monitoring and controllership: If there is no changes in the process, bots are pretty much stable and especially, if they have been well coded. In case there have been any changes anywhere in the process or subprocess, the bot can fail. This means you must have a review mechanism with monitoring in place. Once you put a bot into production, you have to monitor it and do regular sanity checks. Otherwise, you could have situations where bots have failed and you might not know, then the process comes to a standstill. In a nutshell monitoring and control is an important aspect of RPA in the run phase.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

I don't interact with the people from Automation Anywhere.

How was the initial setup?

Procurement of the license is easy, but depending upon what you want to automate and how you automate it that might take time. Setup is not at all difficult. You just take the license and install the application, then it's ready to go. However, in terms of what you're trying to automate, how you're trying to automate it, and the complexity of the problem, the entire automation process can take time.

# Implementation timelines:The time frame to implement depends on the complexities and number of the processes and subprocesses. In a typical process, the coding, testing, and deployment could range from a week to four weeks. However, I have seen it sometimes take longer because you have to continuously keep checking and testing it. Every time the code breaks down, you have to possibly start from the beginning.

My experience has been one to four weeks as the ideal time frame. However, depending on how well the process was understood and documented, there can be certain gaps which would only become evident during the testing phase, not otherwise.

# Resources: Depending on the number of bots that you have to create and the number of the complex processes along with the given budget and timelines that you have in mind, the number of developers range from one to multiple developers. The resources that you really need are developers because they are people who will be coding. Otherwise, from an ownership standpoint, we need some subject-matter expertise for the process. The people who are subject-matter experts will be needed on a part-time basis for the developer to be able to map the process well and be able to create their technical design. Then, you will need a technical master who creates the technical documentation of how it will be coded. The number of technical masters again depends upon the processes and complexity along with the corresponding number of developers.

The deployment team may not be very big. You need just the developers and a design architect, mostly two people. All the other people come and go per the requirement stage of the deployment. There might be people who are there only for consultation. Some people might be there only to approve the solution. Whenever you bring in automation, it has to be reviewed, monitored, and assessed from the organization's standpoint. There might be people who are just doing approvals for this process deployment in case it's a very complex project, and then there is a project manager. Otherwise, sometimes the technical design person doubles up as a project manager too.

What about the implementation team?

Before implementing, you do the assessment of why the organization wants to automate:

Imperatives for Robotic Automation 

  • What do they want to automate? 
  • What are the key objectives  the organization wants to achieve through robotic automation? 
  • Is it a process optimization or is it cost cutting? 
  • Who is driving the automation? Is it client-driven or is it vendor-driven? 

Then, you have to build the business case in terms of what you want to try to automate. E.g., how much can actually be automated? That assessment should be done. Even the cost and time of automation versus that benefits that you're going to get out of it needs to be done.

# Process Degeneration: When we start automating, we do a process desegregation. This means whatever processes are under scope that we try and understand the task level, activity level, and precedence details. We make activity diagrams, then try and assess out of all of these which one can be automated. So, if the automation index is pretty high, which means that most of the process can be automated, e.g., up to 80 percent, then it might make a better business case than if the automobility is only say 30 to 40 percent. Then, the cost of automation might be way higher.

# Setting the right expectations with the client: t is also important to set the right expectations with the organization. Are they new to automation or do they some prior experience with automation? Because this helps us set the right expectations in terms of the benefits which can be had. The customer might also want to understand what are the impacts if automation fails and the fallback mechanisms. For example:

  • How do you mitigate or remediate the impact of automation failure? 
  • What is a criticality of the process you're automating? 
  • What are your points of failure and choke points? 
  • What are your backup plans if things aren't going well?

The most important thing is the business case as to the cost versus the benefits of automation.

# Legal and Compliance Regulations: Also, are any legal or compliance regulations which are applicable because technically it might be feasible to automate, but legally or from a compliance point of view, it might not be good idea to automate. You might want to still have human intervention in terms of verification and validation.

# Criticality of the process: From a financial impact standpoint, things that require a bit of background investigation might be better kept as a manual process or require a human approval rather than automating it completely.

What was our ROI?

It all depends on the scale. In one project that I have worked on, we had a savings of $200,000 over a three-year period and a payback period of 6 months. The typical ratio is that one bot will replace two people.

What's my experience with pricing, setup cost, and licensing?

# Licensing: One of the components of key drivers for us to renew our contract is AI or automation. As an organization, we are moving toward smarter operations.

Our pricing a year ago was $600 per license, but I am not sure of our current licensing cost.

# Set up cost: Additional costs will be for the machines and the number of machines that you are using. You can deploy virtually as well as on physical machines. In both the situations, you do need to allocate a certain budget for securing the machines and where the software will be installed and running. 

# Dedicated Machines: The machines cannot be used for anything else, because only a certain bot can run at a certain time. You need to be very particular about your scheduling of running the bots, and while the bot is running nobody can use the machine. You cannot have an agent working on a machine and the bot running in the background. The machine  has to be completely dedicated. 

# Network Bandwidth and Disk Space: Then there are the network bandwidth requirements and  disk space requirements, which are additional costs apart from the licensing and software costs. The developer is also going to charge you for their coding time too.

Which other solutions did I evaluate?

There are two or three more tools in the market such as Blue Prism, UI Path, but I think the preference was given to Automation Anywhere.

I have only worked with Automation Anywhere.

Understand why you are choosing Automation Anywhere, as the platforms are pretty on the same level except for certain functionalities. Also, in some scenarios, one platform could be better than another. Pick a platform and stick with it.

What other advice do I have?

It is easy to use, but I realize that the effectiveness of the platform depends on the coder and how he is doing the coding. This is my experience, because I have seen that the quality of the automation is as good as the person who is using it. In Automation Anywhere, the skill set of the coder really determines how good the automation is, which is why I am making it a eight (out of 10), not 10 (out of 10). Because while the platform is feature-rich and easy to use, it is the skill of the coder that determines how well the platform is leveraged.

I' am now mainly driving AI at my company. RPA has become a bit secondary in the sense that it is a part of my solution, but most of the time, it is AI-driven. RPA sort of helps in the execution of some of the components of that overall solution. From the organization's standpoint, automation is already a part of all our solutions. E.g., our organization is moving toward automation where almost 30 percent of any deal will be allocated to automation. It will be a ratio of 70:30, where out of $100, a total of $30 dollars will be allocated toward automation and AI.

I did my certification on version 10.4.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Radhaprem Ramaraj
Group Head IT at a tech services company with 1,001-5,000 employees
MSP
Top 10
Reduces complexity, provides a good user experience, and allows us to integrate it with our in-house solutions through APIs

Pros and Cons

  • "The ease of use for the end user and the very low complexity in trying to build a bot are the big factors for us. We are able to work on a project, identify a use case, come up with a design spec, and execute and build a bot within a span of six to eight weeks. In nine to ten weeks, we are able to go live, which reduced complexity. Once we go live, the user interface and the user experience are extremely good."
  • "Their bot runners could be made to handle multiple payloads at the same time because if I want to run multiple parallel operations, the number of bot runners that I have to buy just keeps increasing. It is adding to the cost. However, there is a possibility that we don't need that many bot runners, and we can run multiple operations in a bot runner. This would be a great addition to have."

What is our primary use case?

We are currently working on a vendor bill reconciliation process. It is in production now. We are also working on an incident management process for customer service. Within the customer services, there are four or five different processes that we are working on. All of them are incident management but for different categories at different levels. The next use case that we will be working on is bank reconciliation, and then we are planning to expand into HR for onboarding and recruitment. These are unattended robots. 

How has it helped my organization?

We are able to integrate it with other products through APIs, which we may not have thought about. For example, there are some in-house solutions that we have for which we have built APIs, and we're able to integrate those APIs with Automation Anywhere. We didn't expect that we'll be working on that but it happened.

What is most valuable?

The ease of use for the end user and the very low complexity in trying to build a bot are the big factors for us. We are able to work on a project, identify a use case, come up with a design spec, and execute and build a bot within a span of six to eight weeks. In nine to ten weeks, we are able to go live, which reduced complexity. Once we go live, the user interface and the user experience are extremely good.

What needs improvement?

Their bot runners could be made to handle multiple payloads at the same time because if I want to run multiple parallel operations, the number of bot runners that I have to buy just keeps increasing. It is adding to the cost. However, there is a possibility that we don't need that many bot runners, and we can run multiple operations in a bot runner. This would be a great addition to have.

For how long have I used the solution?

I have been using this solution for six months.

What do I think about the stability of the solution?

You get what you paid for. What it says on the tin is what you'll get inside. As a customer, you will not be disappointed. If you're thinking that you want to build rockets using Automation Anywhere, then you will be disappointed. As long as you know your business needs, the automation that you want to focus on, and you understand the product's functionalities in a good way, you will not be disappointed.

What do I think about the scalability of the solution?

Scalability depends on how many parallel processes you want to run. A bot runner basically runs a bot. How many bots can it run? How many of these need to run in serial? How many of these need to run in parallel? This information will determine how much you have to scale. Now, if you're willing to pay a lot of money and have multiple bot runners, that means for each and every bot runner, you can have multiple processes running at the same time. So, if you are willing to pay, yes, you can scale. It depends on your budget. The product works whether you're on 1 bot or 20 bots. The product just goes off and does its thing. That's not a problem.

If it is 1 bot that you're running once a day at 10:00 in the morning, then you need one bot runner. If you have 20 processes that you're automating and these 20 things have to run throughout the day at different points in time at 10:00, 12:00, or 2:00, you can still run them with one bot runner. In those use cases, scalability is not a problem. Scalability becomes an issue when you have multiple processes. If a reconciliation process needs to run along with the general ledger balancing, month-end closing, and everything else, and all of them need to run at the same time, then you're looking at about 10 bot runners running 10 different bots at the same time. If you're willing to pay, you can get what you want, but it becomes a very expensive affair.

We have 15 to 20 people who are touching the application for various purposes. We have business analysts, developers, testers, and the external implementation team. We also have business users.

Which solution did I use previously and why did I switch?

I have used both UiPath and BluePrism in my previous organizations. Automation Anywhere gives me the flexibility for both on-prem and SaaS, and the difference is not huge for me in terms of performance, security, and all that stuff. It gives me the flexibility, but honestly, on paper, all these three products pretty much do the same. There is a plus or minus 5% difference here or there, but you'll not go wrong with any of these products.

How was the initial setup?

The initial setup was very straightforward. There are specific things that they ask in terms of the environments that we need to build in our typical Windows server, that is, what kind of memory and what kind of processing capability we require. I can't talk from the SaaS perspective because we have an on-prem deployment, but giving on-prem equipment based on the defined specs is pretty much child's play. There is nothing complex about it. It is very easy for developers who understand the platform. You can quickly roll out something and get it live, but you need to understand a lot of logic and the complexity behind the applications such as ServiceNow, Workday, Salesforce, etc. 

What about the implementation team?

We started off with an implementation partner, and our experience with them was good. They had about three people in their team, and we had our business people who were giving the requirements. We also had our technology people who were basically acting as the bridge between our business people and their developers.

What was our ROI?

We are expecting a significant ROI by the end of the year. 

What other advice do I have?

From a business angle, understand what is it that you need. Where do you see inefficiencies? If you're going to fix inefficiencies that are going to be fixed as part of a larger company-wide transformation program, then use the transformation program and fix those inefficiencies as part of the existing solution. If you think that that larger transformation program is not going to touch some places or if that larger transformation program will touch some of these inefficient areas but not in the near future, and you want some immediate wins, then going in for an RPA tool is a good decision.

At the end of the day, the business needs to be aligned with why you're making the decision, and where and what is your priority? What is your sense of urgency with respect to the places where you're implementing it. For example, in my office, we are working on customer service. There is a massive transformation program going on right now, but that transformation program is touching sales, marketing, finance, and all those areas. It is not touching customer service at all, but customer service has its own inefficiencies. So, we introduced automation in customer service because it's not being touched by the transformation program, and we don't want to keep waiting to gain the ROI of whatever we can get or the reduced cost we'll get from customer service. For example, if I'm going to implement a massive cloud ERP like Oracle or SAP, then I will fix the process as part of that cloud ERP implementation and not wait for a bot to be developed.

From a technical perspective or an integration perspective, use an API to directly communicate between the apps, if you can. You don't need a bot or an RPA to do what an API can do.

I would rate Automation Anywhere an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about Automation Anywhere (AA). Get advice and tips from experienced pros sharing their opinions. Updated: December 2021.
554,873 professionals have used our research since 2012.
PrachiYadav
Senior Consultant at a financial services firm with 10,001+ employees
Real User
Non-technical people can swiftly code on it easily

Pros and Cons

  • "We have improved on IQ Bot collectively with the normal Taskbot that we use. How it got started was that we have a lot of scanned documents to input for our solution. So, I used to get a lot of scanned documents, and extracting or reading the data from those has always been a pain area. We always used to bring a manual person in to do it. Once a manual person did that activity, it was brought into Excel where I could run the bot. With the entry of IQ Bot, it now takes care of my scanned documents, which means IQ Bot does the OCR extraction and gives my data to the Automation Anywhere Taskbot. This means no manual intervention and end-to-end bot processing, along with a happy customer at the end of the day. We provide these services to multiple clients, so we have been doing this for all of our clients."
  • "I would like a couple more features where I can talk and the line comes up automatically. I can just put on a mic, like in "Ok Google". With "Ok Google", I can tell it to please open an Excel spreadsheet with the header read. If this is there, then I don't even need to sit on a computer, I can just dictate my commands and it will automatically come up."

What is our primary use case?

I have worked across many different type of RPA use cases that we have done, starting with finance, manufacturing, and banking. The use cases are tremendous. There are many. 

Thankfully, being a technical person, I've also learnt a lot about business processes. Personally, in my career, I have not just developed my technical expertise, but also using RPA and the Automation Anywhere tool, I have engaged a lot of vision as to how the business and the finances process work across different direct industries so far.

How has it helped my organization?

I can talk about a use case that we have submitted. We have a Bot Genius entry that we have where the bot reviews your bot. So, it's a bot on top of a bot to check whether the bot that you have created is up to standards or not. So it is an interesting concept that we try to bring in where we identify pain areas, because a lot of time is been taken up by the reviewer team to identify what's wrong with the code and whether the code is per the coding standards or not. So, we thought of automating and trying removing one layer so a bot can check whether all the coding standards, proper guidelines, and naming conventions of variables are being sorted out. So, we brought along this bot as a finalist to see if it can take home a prize.

We have improved on IQ Bot collectively with the normal Taskbot that we use. How it got started was that we have a lot of scanned documents to input for our solution. So, I used to get a lot of scanned documents, and extracting or reading the data from those has always been a pain area. We always used to bring a manual person in to do it. Once a manual person did that activity, it was brought into Excel where I could run the bot. With the entry of IQ Bot, it now takes care of my scanned documents, which means IQ Bot does the OCR extraction and gives my data to the Automation Anywhere Taskbot. This means no manual intervention and end-to-end bot processing, along with a happy customer at the end of the day. We provide these services to multiple clients, so we have been doing this for all of our clients.

What is most valuable?

There are many valuable features of Automation Anywhere. It is very easy to work on this automation tool on a day-to-day basis. I've seen that people, even from a non-technical background, can code it swiftly and at ease. 

We have IQ Bot which is very interesting and unique. I really like IQ Bot and the concept of A2019 that we have just seen. I really hope to get to work on that. A2019 seems to be very interesting and easier than what we are doing here now. It is a service available on the cloud, which is even better.

What needs improvement?

I would like a couple more features where I can talk and the line comes up automatically. I can just put on a mic, like in "Ok Google". With "Ok Google", I can tell it to please open an Excel spreadsheet with the header read. If this is there, then I don't even need to sit on a computer, I can just dictate my commands and it will automatically come up.

Right now, it's more sequential, where it works in a sequential manner. If they have something dynamically, where it run parallels, I'm not sure if it's out there yet, but It would be a plus point if we could have that.

With A2019 will get both options (writing lines of code and dragging and dropping). So far, we are just doing sequential coding. I'm just writing line-by-line code. But, there is a pain area if I want to go back and have to understand where the issue started, it becomes a little cumbersome to identify. That's where A2019 comes into the picture, you can drag and drop start to make a flow. This will be a useful feature.

For how long have I used the solution?

I've been working with RPA for the last six years, starting with Automation Anywhere.

What do I think about the stability of the solution?

Over the year, I have seen that Automation Anywhere as a solution that has improved a lot. Wherever we have identified bugs, timely resolution, and the interaction with other applications, we have seen a difference from our original solution where we started off. Now, it's completely dynamic and very stable.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

The technical support team has been always very helpful. I write to them and they reply back to me usually in an hour or two. That's a good response that I see as compared to other RPA vendors that we work with.

We have clients who have dedicated CSM managers at Automation Anywhere in case something is a very high priority, which is always the case. So, the customer support team is always there to help us out.

Which solution did I use previously and why did I switch?

One of our primary jobs is to consult our clients. We look at the use case and base it on their use case. We do recommend which tool and special functionalities of the tool that they can go for. There have been many times when we have found the use cases to be very complex and the applications very different and a bit complex, but then we have suggested the Automation Anywhere solution and that has worked as well.

The criteria of deciding whether RPA should be used goes from the old story that your process should be rule-based, input/output should be structured, and it should be logically described. If it falls into these three simple buckets, then RPA is there.

How was the initial setup?

We do have an infrastructure team who supports us with the installation. If you have the basic requirements for the infrastructure, hardware and software, the installation process is pretty smooth. We have user manuals that are pretty well prepared where I can read them, then install it. That's good for the setup or for the person who is installing it from their end. It's sort of easy. You would require a bit expertise from someone at work; a person to help you out.

Which other solutions did I evaluate?

I have worked on other RPA tools as well. Mentioning some of them: Automation Anywhere, UiPath, Blue Prism, and AutomationEdge. In day-to-day life, since the RPA has evolved so much, right from the beginning, we had many different tools. We keep fluctuating from one tool to another trying our hands out in other domains as well. However, Automation Anywhere is one of my favorites.

What other advice do I have?

I would rate it a nine (out of 10). I will keep one out for my feature to get voice converted into the command.

Which deployment model are you using for this solution?

Hybrid Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner.
Prakasha S
Solution Architect at Accenture
Real User
Top 20
Helps in increasing productivity, reduces the cost of the whole operation, and makes fewer errors

Pros and Cons

  • "I implemented AA in different environments, the AA installation is the smoothest compared to other RPA software installs."
  • "Bringing a DevOps model for bot implementation integrated through private bot store might be a good idea to improve the tool."

What is our primary use case?

I am a platform architect for the RPA so I deal with all 3 major RPA vendors. I build the Infra for all big setups. I have immense experience plan, design, and building the setup on cloud, on-prem and with different configurations.

I implemented AA in different environments, the AA installation is the smoothest compared to other RPA software installs.

Migration is a little challenging since it requires direct integration with DB, credential vault and all that. Since multiple credentials are involved, it is a challenge to get all the credentials, it should be easier if only the control room credential was required. Versioning migration is still a challenge.

How has it helped my organization?

My company uses AA extensively for internal BPO work as well as we refer and deploy it to the customer as a RPaaS model. It helps in increasing productivity, reducing the cost of the whole operation. It makes fewer errors and in the COVID situation proves to be a reliable workhorse.

We implemented a lot of new environments recently. v10 expiry and COVID situation accelerated the implementations. Compared to older days now all implementation of infra bot happened pretty quickly.

Bot with Citrix integration may require a lot of improvement but having any extra feature really helps in complex implementation.

The cloud templates for implementation helped greatly and it helps us in pushing the software fast.

What is most valuable?

  • The OCR integration came a long way. They have intelligence inbuilt into it.
  • Ease of deploying and the KB article really help people to just read and deploy different 3rd part components as well(svn, DB, LB, etc) .
  • Nowadays, the screen scraping techniques evolved in RPA and it is good to see they are in play which was not the case couple of years ago.
  • HBC is most suitable for COVID times. 
  • The RPaas offering will help customer to use it for less number of bots.
  • AD security group integration is a good feature
  • AI sense is good too.

What needs improvement?

They need to concentrate lot on a nonpersistent RPA model. Integrate IQ bot with AA instead of making it as a separate component, since nowadays intelligent bots need to be integrated into RPA core. Instead of bot agents getting installed on the machines, concentrate on making it independent of the system and only as a plugin in the browser.

It doesn't have an independent small install for developers and always requires to be fully installed.

Bringing a DevOps model for bot implementation integrated through private bot store might be a good idea to improve the tool.

For how long have I used the solution?

I being using it since couple of years, i am impressed by the transformation from v10 to v11 and v11 to A2019. 

What do I think about the stability of the solution?

The solution is pretty stable, we didn't face many issues. Once the instalation is done the control room core architecture wont face many issues.there are quick fixes like service restart if anything goes off. but most of the time we hear AA support suggesting us to reinstall with the new version of software for performance issues, but with my experiance i hardly see that making huge differnce in fixing the actual issue.

 Monitoring can be done through email alerts for the core infrastructure. Issues mainly in HA(High Availability) with cluster sync issues still not monitored at the dashboard level, which might be a concern if the cluster goes out of sync. At the bot implementation lot of things are dependent on the way we code so it's additional work for the developer to get the code keeping in mind all the events which might happen. I would have been impressed if the solution had framework at the control room level to keep track of the overal execution and transactions, hope they can bring that feature in future releases

What do I think about the scalability of the solution?

We never faced any issues with scalability for AA. sometime it takes high CPU on CR, but that is expected. one of the frequent questions we encouter with HA setups is the single point failure of repository storages, i understand that this needs to be taken care by storage fault tolerance, however most organization might not use cloud for RPA and if we are doing on prem install they might not have a high resillenace storage. SQL availability group still needs a SQL expert to get that right and DR solution totally depends on the underlaying infra we work on (there may be lot of alternative solution and its a big discussion to be honest :-)   )

Hence HA and DR solution really require a expert like us who have extensive knowledge on RPA, cloud, infra, windows and SQL  

How are customer service and technical support?

They offer excellent customer service. No complaints except that every time they ask for a software upgrade as soon as they hear about an issue, which is not actually a good solution. Otherwise, they have very good knowledge of most of the issues. 

Which solution did I use previously and why did I switch?

We keep switching between RPA software for a number of reasons. We prefer AA for the following reasons:

  • Low cost for run licenses compare to other RPA solutions
  • A high number of certified developers help in bring efficient automation compared to others, they in turn promote the RPA software that they know of.
  • Easy to program, no prior experience of programming required.
  • Easy to use compared to other RPA.

How was the initial setup?

The initial setup was straightforward, even a complex setup can be set up in 20 mins if you have all prerequisites.setup can be complex if there is a HA , DR implementation, as a architects we need to factor in lot of variables. some are target application access,  MFA for the application or windows authentication, credential management, data accessibility, network reachability , underlaying hardware, PaaS offering in cloud(depends on the cloud) , VDI or VM template to choose (Makes huge difference in performance and costing), citrix or native application . Overall simple install, but huge planning to figure out the overall feasibility and effectiveness of implementation

What about the implementation team?

We implemented in-house. I implement it within Accenture and for customers as well. I rate my self pretty high for implementation. I have solid experiance (AA master) as well as cloud certification. I have 12 years experiance in infra, so expect a good solid backgroup on both AA and infra.

What was our ROI?

ROI is important for the business case. ROI is good if you are going for long run, year on year. i never stayed on a project till we start getting the actual values, i see nowadays ROI is shrinking due to RPA vendors raising thier license costs , additional cost added to get the complex RPA solutions to be implemented

What's my experience with pricing, setup cost, and licensing?

The setup cost for AA is always fixed since the configuration won't change much for the different number of bots, the license cost is lower in AA,

Which other solutions did I evaluate?

We usually evaluate Blue Prism and UiPath along with AA for implementation. We decide based on the requirements.

Which deployment model are you using for this solution?

On-premises

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
TT
Senior Consultant at Capgemini
Real User
Top 20
The versioning concept increases the security and tracking mechanisms

Pros and Cons

  • "Instead of packages like other RPA tools, I think the repo check-in and check-out feature enables the same in AA."
  • "When comparing the code under version checks, although there is a change done, it doesn't say so because the change is done at the variable level and not in the line of code."

What is our primary use case?

We have applied AA to our customers. KPMG another solution they use. 

Streams like HR, payroll are reasons that AA may have been chosen in an environment.

Use cases like report extractions, SAP interactions, HR data, and many payroll automations have been put into use.

We used UiPath and Automic before AA and I feel the difference very clearly and I am sure there's a long way ahead.

Sensitive data handling departments are usually not allowed or exposed to automation but I do not see such limitations when it comes to AA.

How has it helped my organization?

AA definitely did improve the scope of our organization but tools like Automic and UiPath still take a slightly upper hand in terms of business and market.

We have been trying our best to sell AA as our best tool and we are getting projects one by one eventually.

Not all tools give us the clear utilization of the infrastructure in place but this does and trust me, this has been proved far better than other RPA tools and that is why I see AA booming day by day.

We are pretty positive about AA.

What is most valuable?

Live executions on the prod machine with the player options is good.

I have been using tools like Automic and UiPath that has either an engine to run for Automic and Orchestrator for UiPath.

The versioning concept is pretty nice and increases the security and tracking mechanism.

Instead of packages like other RPA tools, I think the repo check-in and check-out feature enables the same in AA. 

Although it does the same, the ease of usage is fantastic in AA from my experience.

The line compare feature is another feature that I personally like the most but there is an anomaly as well.

What needs improvement?

Maybe not improved but I heard that the 2019 version is going to look more like UiPath, which is not ideal for a typical/classic developer.

The feel of parsing at the code is different from viewing object images for sure.

When comparing the code under version checks, although there is a change done, it doesn't say so because the change is done at the variable level and not in the line of code.

This is logically wrong, a line would contain n number of variables including object clonings, screen images, variables, etc so any change to any of these has to be captured and shown as a change done in the version history.

For how long have I used the solution?

I have been using and working with AA for 1.5 years. 

I started with initial training, they gave me a project and then a certification as well.

I am AA Master certified, I did it around the start of 2020. Ever since I got certified I am working on the solution building for major clients, client proposals and enhancements for the existing bots on production.

Not all developers use a full fledged tool and that is where I am being considered to propose better solutions. 

We took new clients since April 2020 where AA is the only prime RPA tool being used and we have been enriching it since then day in day out.

What do I think about the stability of the solution?

I am sure AA is pretty stable.

Now that it's on its own framework, I am positive about the stability. At any point in time, I would preferably suggest sticking to the initial platform and framework that people like the most providing an overall package.

What do I think about the scalability of the solution?

Scalability is always a sensitive topic when it comes to RPA.

For me, I look at it as availability in simple terms. The scalability factor has to be stretched to an extent where availability is never compromised.

How are customer service and technical support?

I have personally had interaction only twice along with my onshore peers.

1st was with Mae Chang about v11 environment setup &

2nd was with one of the support engineers who helped solve the control room blank screen error.

So far so good.

Which solution did I use previously and why did I switch?

I used ITPA tools like Automic (CA Technologies product, now Broadcom product) & RPA tools like UiPath and BluePrism.

For a classical and typical developer, we like code to be seen, written, and parsed but not objects. More importantly, security features like parsing, code versioning, ease of use, live executions, etc made us chose AA.

We haven't moved completely to AA for now but talks are in place with customers.

So, for multiple valid reasons, AA takes the first place when it comes to automation.

How was the initial setup?

The setup was good. I wouldn't say straightforward but the process and steps were laid down clean so for us, it seemed to be cool.

What about the implementation team?

It was in-house for the POC project and the customer himself for the account we hold.

Our setup was pretty clean and neat.

I would rate the customer level a 70/100. They haven't defined the scope, networks, security properly, and there is too much of JUST red tape. The process definitely takes priority but not at the cost of providing solutions. The optimal path has to be chosen.

What was our ROI?

I shouldn't be projecting this out but would say there is a grace ROI with our current clients.

I am not 100% sure. Revenue is nominal as of now. The business model defines it more in order to sustain a customer but I am sure it's doing well.

What's my experience with pricing, setup cost, and licensing?

So far so good.

When it comes to 2019 and the AA cloud I think many are skeptical about the pricing and support model.

For example, we are already on our own cloud, AWS and azure so as a cost-effective solution we would obviously want to choose our own platform for hosting. Be it IAAS, PAAS, SAAS etc.

Now that AA is proposing a cloud as well, we are still in the thinking phase of the costing model to see if this fits us better in terms of revenue and margins.

We are looking forward to experiencing the AA cloud soon.

Which other solutions did I evaluate?

Like mentioned, we have been using Automic, UiPath, and BluePrism to a pretty good extent for about 2+yrs and it was good until we realized there is a better product in the market and who doesn't want the best.

It was not a one day's decision to chose AA. A big set of people, the cream of the project, were deployed to learn and explore AA to the maximum extent possible.

I lead the operations part of the existing automation project and so was I leading this POC project under AA as well. So all possible test cases, comparisons, ease of use, security, and many other factors were considered before we opted for AA and so is the product now.

What other advice do I have?

My request would be to keep a little lower pricing for services like on call support, cloud, and other key services. Otherwise, the rest all seems to be very much feasible in AA.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Dhiraj Dedhia
Sr. RPA Consultant at Thirdware Solution Ltd.
Real User
Top 20
Good security and bot visibility, and it supports many different platforms

Pros and Cons

  • "Simply tagging variables used in the bot, can provide automated real-time dashboards that are presentable to management showing them a complete view of how the bots are performing."
  • "The quality and response time of the support, even on Sev-1 tickets, is not satisfactory."

What is our primary use case?

The primary usage of this solution is for the development of software bots using this RPA solution for various customers, and also for in-house process automation.

Bots have been developed for various domains like Automotive, Banking and Finance, HR, Housing, etc, and across various end-user software like Oracle, SAP, QAD, Terminal applications, etc.

As a first step towards having companies direction move towards emerging technologies, getting the right skillset available for adding Machine Learning, Artificial Intelligence, NLP, etc, so that we could provide a complete end-to-end solution to the customers.

How has it helped my organization?

We internally host v11 and A2019 Web CR of this solution for in-house development and training/learning purposes.

RPA was introduced as an emerging technology in our company and Automation Anywhere was chosen as the RPA Solution. Thirdware became an AA partner for reselling AA licenses. Thirdware performs bot development as a vendor using this solution and has automated more than 60 processes to date in various domains.

The Automation Anywhere RPA solution has opened gates for Thirdware to step into providing an end-to-end solution to customers by implementing emerging technologies like Machine learning, Artificial intelligence, NLP, etc.

AA has brought a completely new skill set for entering a completely new domain and being versatile as a service/solution provider.

What is most valuable?

  1. Bank-grade security provided by AA with Credential Vault and Lockers. With the level of security provided by AA, it is a global leader and it becomes easy to convince prospects and turn them into customers.
  2. Bot Insights provide visibility. Simply tagging variables used in the bot, can provide automated real-time dashboards that are presentable to management showing them a complete view of how the bots are performing.
  3. Platform support is very good. AA supports on-premise and all major Cloud providers for the installation of the software.
  4. The solution is very scalable.
  5. After learning other RPA tools, I can say that AA provides one of the best user experiences with the user-friendliness of the UI.
  6. The role-based access controls (RBAC) provided by AA are simple to define and provide clear distinction and segregation of duties and roles, and they help to maintain security.
  7. The A2019 bot agent and development on browser means that there is no need to install a thin client like v11 or other RPA tools. The automation development of bots can be performed right from the browser itself.
  8. The Flow view and List view for development mean that development becomes much easier, even for newbie users. The flow view and the drag and drop command flexibility is very helpful. The list view is generally preferred by the developers.
  9. Workload management and Queues are valuable components. With the WLM module, multiple bot runners can be utilized to perform a single task more quickly and thus help achieve SLAs. Multiple bot runners can be used optimally to divide and perform tasks simultaneously on different machines.
  10. Inline Python scripting support with A2019 is possible, which reduces a lot of lines of code for programmers. 

What needs improvement?

Technical support provided by Automation Anywhere is not up to the mark and needs a lot of improvements. Solutions or details provided by L1 support are contradicted by L2 and/or L3 support persons, thus leading to confusion.

The quality and response time of the support, even on Sev-1 tickets, is not satisfactory.

Enhancements or product issues/bugs are not fixed quickly and no ETA is provided for the same.

Working of triggers (email file, etc) in A2019 in unattended mode is a feature that was available in v11 but missing in A2019. I would like to see this feature in A2019.

In v11, RDP-based deployment and auto-login both were possible but with A2019, only the RDP-based approach is possible. Due to this, there is no way to maintain any application open inside the RDP, as each and every time Web CR connects to RDP to run the bot and disconnects, it closes all of the open apps inside RDP and terminates. I need a way where open apps inside RDP must be left open if they are open already.

For how long have I used the solution?

I have been using Automation Anywhere for more than three years, right from v10, v11 until the latest A2019 release.

What do I think about the stability of the solution?

All of the bots deployed by our company are working quite stably in production with minimal support required. Unless there are some changes/enhancements to the bot logic suggested by business users, there are no changes or modifications required to the bot to work.

There was a bug in A2019.14 version which did not allow proper bot deployment intermittently. this had led to a major issue on PROD where schedules were running but bot was not getting deployed on PROD runner machine leading to instability. We had raised the concern with AA team and they have addressed the same in A2019.15 release.

What do I think about the scalability of the solution?

The solution is highly scalable, which is a USP of this solution. Adding more creators and runners is a quick task.

How are customer service and technical support?

I would rate my experience with technical support as four out of ten, due to a lack of responsiveness and the quality of support provided.

Which solution did I use previously and why did I switch?

This was the first RPA solution that was introduced in our company.

However, personally, I have learned UiPath and found the Automation Anywhere solution better in all the aspects (Features, Releases, User-Friendliness, Cost).

Customers do ask for a comparison of this solution with the competitors in the market but it is always seen that Automation Anywhere is a clear winner.

How was the initial setup?

The initial setup is straightforward if it is done in express installation mode.

Custom mode installation and installations involving SSO and AD authentication are more complicated.

IQ Bot installation requires expertise.

What about the implementation team?

All installations and implementations are done in-house in our company.

What was our ROI?

ROI achievement for most of the customers is observed from four to eight months from the time of implementation.

What's my experience with pricing, setup cost, and licensing?

The one-time setup cost can be fully recovered with the ROI achievement within six months, provided the implementation of bots is planned properly.

The pricing and licensing are definitely moderate to costly but easily recoverable by achieving ROI quickly.

Our setup cost was only procuring AWS instances but installations are performed in-house.

Which other solutions did I evaluate?

UiPath was evaluated but it was found that Automation Anywhere is a clear winner and a market leader globally.

What other advice do I have?

AA is a global market leader and the best RPA software to go with, in all aspects. If the AA support improves then this definitely deserves a rating of nine and a half out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: Thirdware is a Partner with Automation Anywhere and develops bots for customers on this platform.
reviewer1464705
Manager, Robotic Process Automation at Celerity
Real User
Top 20
Good support, improves process efficiency, and the ROI is significant

Pros and Cons

  • "I'd say the most impactful and heavily or commonly used ability of v11 and A2019 has been the ability to integrate other code types and operations within the process."
  • "Having fewer connection instances would make it more secure, more simple to troubleshoot, and possibly more flexible with the type of applications in use."

What is our primary use case?

We have used AA for telecom industry repetitive processes, public retirement firms processes, and financial bank processes. The development has been with local developer desktops, remote VDIs, EC2s, as well as RDP clients of sorts for the individual company preferences.

We are currently building an Azure environment for our A2019 solution internally, with a VDI as our developer/UAT environment. Production will be a separate VDI operating from our main control room instance, as we create Bot Runner agents out of those VDIs for production.

I also deal with many federated lines of business, as they often develop locally and use attended automation as their source of RPA for their lines of business. Others utilize EC2s as their developer and UAT environments and have a separate production import process that keeps the separation of duties intact. Though this is not as productive as that team expected, they use it temporarily until their control room can be migrated and upgraded into A2019 instance as part of another line of business currently building out a sandbox environment for the remainder of 2020.

How has it helped my organization?

I am a consultant and our RPA practice on a personal level has improved the efficiency of the payroll, PTO, and timecard submission process within our company. It has taken time-consuming daily mundane tasks off the plates of our talented finance teams and allowed them to dedicate more productive time to working with more thought-heavy and human-centric activities.

Outside of our company, as we work with clientele, several improvement instances have been evident for those. One company had a very tedious process of monitoring an email inbox for several business units to send emails notifying that their daily database update process was completed. This took many hours of monitoring after hours, but in place of that, the RPA bot was able to perform the monitoring for them of that inbox, perform the necessary follow-up or escalation emails needed, and finalize the process once all was complete. This was unattended automation, saving them precious time, improving morale, and accurately informing everyone of the completion. 

What is most valuable?

Both v11 and A2019 have their strengths but the cloud-based forms with Excel, Microsoft applications, scripts integration, and functionality of A2019 have really stood out above the way v11 can do those things.

It takes far less code to work with A2019 than v11 for the tasks we have in place. In v11, the Metabot features have proven a tremendous help to work with smaller tasks such as file and folder operations, datetime operations, as well as credential management operations.

I'd say the most impactful and heavily or commonly used ability of v11 and A2019 has been the ability to integrate other code types and operations within the process. For example, if someone needed a heavy data comparison process to take place, utilizing AA could work but often takes a good bit of time to work through a large Excel or CSV file. Instead, activating a pre-developed or partner-developed Python script would be my choice because of the speed and efficiency of that language. I currently use this method and it's a major time saver.

What needs improvement?

In terms of improvement, usually, I have found is not as general as people think. Specifically, as a use case, I am excited to see improvements in having an A2019 cloud control room working and improved on the Lenox environments. A good bit of our finance infrastructure for web-based applications is built in that environment.

There is a good bit of dashboard-type development going on in this type of environment already, so the ability to integrate some of the functionality, as well as keep the synchronicity of everything within it, would be a major benefit.

Having fewer connection instances would make it more secure, more simple to troubleshoot, and possibly more flexible with the type of applications in use.  

For how long have I used the solution?

I have been using the AA desktop application versions since 2014 (v09-v11), approximately six years, and A2019 for about four months.

What do I think about the stability of the solution?

I've not had any instability issues but only environmental stability issues that come down to the company that created the environment. 

What do I think about the scalability of the solution?

I find it very scalable, especially with smaller automations, as they can often grow once proven to businesses that the processes work. 

How are customer service and technical support?

The technical support was very knowledgeable, very easy to understand mostly, their ability to work with us to meet the needs and being patient was a huge help. 

Which solution did I use previously and why did I switch?

I did not previously use different versions but currently use both. I do know that going forward with v11 sunsetting in 2021, we are migrating and going through a learning phase of A2019 to fully adapt to that application. 

How was the initial setup?

The A2019 setup was straightforward for the applications themselves. The environments in which they are set up is a different story but, that again is on a per-company basis and often lends itself to the expertise of the DevOps teams. Sometimes, those folks are not familiar with RPA or A2019.  

What about the implementation team?

We implemented through AA directly. The availability of their support was very good. Several meetings and work with their folks went well. 

What was our ROI?

Our ROI has ranged from thousands to hundreds of thousands, depending on the type of process being automated.

What's my experience with pricing, setup cost, and licensing?

I really enjoy the pricing options with Automation Anywhere, as they are able to flex their ability to adapt to the needs of the customer really well. I am sure the specifics for some pricing are on a partner-by-partner basis but providing the ability to scale the licenses, setup, and pricing to the customer is a huge benefit with Automation Anywhere.

Their technical support system and response times directly to a partner are really good.

Which other solutions did I evaluate?

We did review UiPath, Blue Prism, and Power Automate. 

What other advice do I have?

I'd say, fully go headfirst into learning the A2019 platform and all it can do for a business. There is something for everyone in that platform. Large or small scale automations, migration processes from v11 is already in place and tested, and there is no more need for Metabots because they are now "packages" that can be made or modified by a seasoned developer, and a plethora of other benefits are evident. Just jump in!! 

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: Not only do I run the RPA practice and communicate as a partner with Automation Anywhere, I am an RPA developer as well utilizing the product within our company and building out solutions and automations directly for and with our clients as a developer.
reviewer1457211
Business Operations Associate Consultant at ZS Associates
Real User
Top 20
Easy to learn, tweak, and implement in our day-to-day tasks

Pros and Cons

  • "The best part about A2019 is its ease of use. You don't need to be a coding champ or an expert to use and implement A2019 in automating tasks. It's very easy to learn, tweak, and implement in your day-to-day tasks, especially features like capture/record is completely marvelous."
  • "One of the challenges that I face every now and then while working with A2019, is around the bot agent updates. Every week/alternate weeK, I receive an error while running my bots, that asks me to update the bot agent."

What is our primary use case?

I have been using A2019 for validating IC reports and scorecards that we publish every month for the client on a portal. As the reports are around 200, it used to take a lot of manual efforts previously to get this done, however now, A2019 has helped in automating the complete validation part. 

Apart from this, the other major use case is validating the child level reports with the parent. Though the underlying reports are generated from the parent itself, validating individual reports just to add another level of the quality check was a tedious task initially, however, A2019 has made it very easy in comparing the two excel based reports end-to-end

How has it helped my organization?

Automation Anywhere, specifically A2019, has helped me and my organization in automating the tasks related to quality checks and assurances. As a consulting firm, it is really important to provide correct insights, reports, and deliverables to the client and it involves a lot of QC checks and validations. A2019 has helped us in automating a major chunk of such tasks, thus helped in saving a lot of time, effort, and revenue. There are trainings going on every now and then, to spread the knowledge and access of this tool to other folks in the organization, so that more number of people would be able to implement this in their projects

What is most valuable?

The best part about A2019 is its ease of use. You don't need to be a coding champ or an expert to use and implement A2019 in automating tasks. It's very easy to learn, tweak, and implement in your day-to-day tasks, especially features like capture/record is completely marvelous. Apart from these, the Excel basic and Excel advanced features are really handy and easy to use. I personally have used them frequently in all my bots as most of my work is related to excel and stuff. Last, but not least, using A2019 for automating the tasks even on the virtual machines, which is one of my favorites.

What needs improvement?

One of the challenges that I face every now and then while working with A2019, is around the bot agent updates. Every week/alternate weeK, I receive an error while running my bots, that asks me to update the bot agent. I have to download the bot agent every time and reinstall it, in order to get the work done. This thing has also created an issue for me in the past, where I need to present something to my US counterparts, and then the bot was unable to run because the bot agent update notification came few minutes before the meeting. This was really frustrating at that point in time, however, fortunately, I got that resolved within minutes during the meeting by updating the bot agent. Hence, I believe, there should be some facility available, which can help me in running my previously implemented bots, even if there are some updates in the bot agent

For how long have I used the solution?

I recently got involved in A2019 training organized within my organization as part of motivating folks for Automation. It's been around six months that I have been using this as a part of my day-to-day work.

What do I think about the stability of the solution?

I have been using this for the past six months and have been already utilizing this for my day-to-day work. The level of involvement of A2019 for me is increasing as time passes, as now, I see things from a point of view, where I try to automate major chunk of my work using this.

What do I think about the scalability of the solution?

This can be used to any level of tasks/processes as it allows the bots to communicate within. This helps in automating major tasks into smaller bots and then coordinating them together to automate the complete process.

How are customer service and technical support?

I used to have connections with Automation Anywhere folks every week/alternate week and I must say that they were highly professional and learned people. They always guided me before even implementing something and made me aware of all the nuances. Overall, I am really happy to get in contact with such folks, who not even helped me in shaping my imagination for automation, but also showed directions by demonstrating their example bots.

Which solution did I use previously and why did I switch?

I have a little experience of working on Blue Prism in my previous organization. However, Automation Anywhere is far better it in terms of features and ease of use and implementation.

How was the initial setup?

For me, the setup was quite straightforward. Yes, I did take some online help to get some issues resolved, however, the overall process was pretty easy.

What about the implementation team?

I implemented it in an in-house setup. This has really become a part of my organization's work as the Business Operations vertical is using it very frequently.

What was our ROI?

I invested around 2-3 weeks in learning this and creating my first bot. Then it took me a week to use it for targeting parts of my day-to-day work. And now, I am using it for the past 6-7 months without any investments and saving a lot of effort on a weekly basis.

What's my experience with pricing, setup cost, and licensing?

The costs are just a one-time cost, but the amount of savings it will generate is uncountable. So it's better to invest in something now, learn and start saving your time, effort, and money in the future.

Which other solutions did I evaluate?

One of the options was the level of features present in Automation Anywhere. It allows both back-office and front-office bots to automate. However, in the other case, only back-office bots can be automation. I personally like the UI and the overall features present in A2019 and level of ease, with which this can be implemented to any application.

What other advice do I have?

The only con is the frequent updates in the bot agent every now and then. This annoys the user at times and (s)he may land up in some trouble due to this, as the bot would be able to run without installing the updated bot agent.

Which deployment model are you using for this solution?

On-premises

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Automation Anywhere (AA) Report and get advice and tips from experienced pros sharing their opinions.