Automation Anywhere Reviews

Automation Anywhere is similar to Blue Prism. We do a lot of process mining and RPA tasks. We've used it in some very large companies. It's for automating activities in large service centers like home loan originations, insurance claims, or for service desks for utilities for telephone companies.

Companies were trying to eliminate a lot of manual processes that were being handled by people at keyboards and some of the repetitive nature. A lot of it is the front-end handling of incoming phone calls or incoming service requests that might be sent via email or text. Rather than having people look at the request on a green screen or on a website, the robots would actually handle some of the routing of the requests or the routing of the documents. For example, for a home loan application or some kind of claim. A lot of the time, most of the companies have people sitting in a service center, receiving those requests and reviewing them. However, now, a lot of the inputting of the data can be handled by the robot.

The solution is easy to deploy. It scales. It's easy to configure. They are pretty generic. There's not a lot of difference between any of the three big RPAs. 

Automation Anywhere is very focused on the Microsoft world. They don't do anything other than Windows and Microsoft, whereas Blue Prism and UiPath compete with other platforms.

The learning curve is low. It's faster to learn than the others.

Some people in my company have used the Co-Pilot functionality. Right now, they use Salesforce, although they have their own RPA now and they are going to replace it with MuleSoft's automation.

Automation Anywhere's ability to provide automation at scale for Microsoft is excellent. 

The integration of RPA bots, APIs, or business applications and documents is pretty robust.

They should consider being more multi-platform.

I've used the solution since 2018. I've used it for about five years. 

I've never used technical support.

I've also used Blue Prism in the past.

My understanding is that the initial setup is pretty straightforward.

The project would dictate how long it would take to deploy. It could take a couple of days to a couple of months. There's a question of governance proliferation and compliance that needs to be considered in RPA. The internal policies would affect the overall setup. 

There is maintenance in the form of updates. It doesn't take much maintenance. We don't use bots and therefore do not need to maintain them.

I don't have any thoughts on pricing or licensing. 

For someone who wants to use an API integration instead of a robust process automation solution, I'd advise it depends on the culture of the company, and the complexity of the integration that one wants to do. Depending on the culture, on average, it's a 50/50 split. There are some environments where RPA is the right thing to do since it's quicker. It's faster. It's easier to manage them from the perspective of just configuring the conformance and compliance with internal policy. However, in other parts of the same organization, you might need API integration depending on what you're integrating.

I'd rate the solution seven out of ten. Nobody gets a ten. Nobody's perfect.

We use it for processes related to IT operations in the manufacturing industry.

There are hectic IT processes, jobs that run overnight, weekly, and monthly. We can optimize, rewrite, and automate them. They represent the most important use cases that I have been involved with: IT operations and software for manufacturing.

It has helped our organization increase automation consumption by 20 to 30 percent.

The most valuable feature is the Control Room.

Also, the integration of RPA bots with other processes and documents is good. We don't have any issues there. We could have more connectors, but it's fine. I have used it for SAP and for direct API-to-API, and that went well.

It is good for standard procedures with an SOP. For those, it works well. But there are processes that are tricky and need human intervention and intelligence. In those cases, the process gets stuck. Something that is a straight-ahead process—you do A, B, C, and D—is fine. But when you do A and then have to decide whether to do B or C, where there is a need for logical thinking and human intervention, we find it difficult to automate those cases. We have to break down those processes and do that tweaking.

We would like to see a more seamless UI, and we would like AI help. Wherever we are stuck or there is a logical error, AI help, with prompting and suggestions on what to do, would be good. If I have dragged and dropped something in the wrong logical sequence and it fails during execution, there should be automated AI help.

We use NetBeans IDE where we get something like automated help, but that's a platform for doing standard Java and PHP development. Automated help is coming up more and more in many tools. For example, Microsoft is providing it. We would like to have something like that in Automation Anywhere, with automated debugging and self-help.

I have been using Automation Anywhere for two years.

Overall, the product is stable for SOP-based use cases. It is not very stable for complex use cases.

It is not very scalable for complex use cases.

Their technical support is good overall, not excellent. They can improve the response time and on-call support. We have SLAs, so we need support to be immediate.

Neutral

We did not have a previous solution.

Recently, automation has gone to the cloud, and that has been most beneficial because installation was quite hectic before. On-prem was quite difficult, but the moment they launched the cloud version, it became easy.

With on-prem, there were issues with installation over production as well as the setup of the Control Room. Often, the Control Room would go down or hang, and we would have to do restarts. It was not seamless.

The licensing cost could be improved. It costs a lot. At the very least, the developer licenses and the control panels should be made free to enterprises, and the production environment licensed. Production should bear the cost; we would be okay with that, but not the development side.

Business users didn't find it that easy to use, but for developers who are building the use cases, it's quite easy. For the business users, the issues were standard ones, such as navigation, user friendliness, and the terminologies that they needed to understand. They often require training before using it, and not just one training session, but training and retraining. On a scale where 10 represents a low learning curve and one is a large learning curve, Automation Anywhere is a seven. For non-technical people, it's difficult. For them, the learning curve is a four or five. It usually takes four to five months for them to be able to really use it on their own.

We have developed solutions for IT back-end processes, so there are no end-users. These jobs run weekly, fortnightly, and monthly. There are two or three people involved with it, but it's the jobs that we have automated.

We need three to four people to maintain the solutions, but that doesn't take a lot of time—about four hours a week. It's not something that needs to be done every day. Before the jobs run, they check to make sure everything is okay, that no errors or notifications are coming up. The maintenance is very low.

Automation Anywhere is good but not exceptional. It's good because, for simple use cases, we use it with different technologies. For complex processes, automations should perform better.

We have automated some data entry scenarios. We also have automation for system monitoring. It is being used for data entry, system monitoring, and data exchange with other systems.

We found a lot of processes to automate. We currently have about 80 processes that we have automated. 

Automation Anywhere has helped our organization increase its automation consumption, but we are a little short of RPA developers. We are acquiring new talent and new resources for that group, and we are on the right path. We have a lot of work. 

Workbench, which is a development tool, is very friendly. It is complete. Compared to Power Automate, Automation Anywhere is much more comprehensive and easy to understand.

We use APIs for some bots. It is not too common, but we use APIs in some processes. The integration at the moment is easy.

We work with version 11, and we have some problems with some applications. Automation Anywhere's software does not recognize them properly. The recognition of web applications is not good. The software does not consistently recognize all the controls and objects. We are in the process of migrating to a new version. We are migrating to Automation Anywhere 360, and I hope that in the latest version, the recognition model can be better. On the Internet and various forums, many people say that Automation Anywhere 360 appears to be much better, but we have not implemented it yet. I hope it is better and consistent. The main problem is consistency. If I make a bot today and tomorrow if the application changes, the bot stops working.

Similarly, in terms of the ability to provide automation at scale, the new version is more focused on that. The version that we have is not that capable. The development is not too easy. We need to put in too much effort, but Automation 360 appears to be easier. Development takes less time.

Automation Anywhere is a technical application. It is not so easy for a regular user. It requires technical knowledge. The new version is more user-friendly from an ease-of-use perspective. 

I have been using this solution for three to four years.

I would rate their technical support a nine out of ten.

Positive

We are still using Power Automate, but we are not using their RPA model. We only use Power Automate for other automations. When we chose our RPA tool, Microsoft had not released the RPA tool for Power Automate. Microsoft released it a year or two years later.

We have some processes to analyze the ROI, but right now, we are not focusing on knowing that information. Our main need is automation. ROI is important, but it is not critical at the moment. We are still automating projects in the company.

It is expensive. I would rate Automation Anywhere an eight out of ten in terms of pricing. 

They bill for every IQ bot that you have. We do not use IQ Bot, but we have a license, and they bill for every thousand pages. 

We evaluated one or two other options, but I was not a part of the evaluation.

We did a little bit of research, and we found that Automation Anywhere was recommended at that time. It had better reviews on the Gartner website, so we decided to go with it.

It takes about three to four months to learn it. Some of the things are easy, but because we are trying to do automations, we need to make sure that we understand the application properly. We need to know how it works internally in the structure of the code because sometimes, we make a programming change that works today but stops working tomorrow. That is because the application can change, so we need to understand how the controls work between the changes and have the logic that allows a bot to run smoothly irrespective of the application changes. It is challenging to analyze the changes in the application and find a way to program the bot to recognize the changes.

To someone who wants to use API integration instead of an RPA solution, I would say that API integration is more recommended, but sometimes there are issues with this type of integration, so we have to finish the project in Automation Anywhere. The first option that we always try is to create our own integration between the systems with APIs. The RPA tool is the last option for integration.

In terms of maintenance, we need to install the updates or patches. Our infrastructure team is in charge of that. We have technicians to install patches. We have people with different roles. They are technical leaders or system administrators. We also have an information security team, and we have a network team, as well as an operating system team. Every department makes a little contribution to the whole environment.

For managing the bots, we have only three people. Maintenance of bots is different because we have bots scheduled all day, so we still need to monitor them on a daily basis, but the update process is monthly. We verify what is pending. Overall, the maintenance takes about eight hours a month.

I would rate Automation Anywhere a seven out of ten.

We are using Automation Anywhere for the automation of supply chain management, logistics, and procurement processes. We are automating invoices and supply chain processes.

By implementing Automation Anywhere, we wanted to automate repetitive tasks. Because of this solution, my business is able to complete the work quickly. It saves a lot of effort and hours. It is time-efficient and cost-efficient. It reduces human error and manual effort.

It takes three to six months to realize its benefits because businesses need some time to understand what is the difference, but going forward, with the enhancements, there is a reduction in the cost and errors.

The integration of RPA bots, APIs, business applications, and documents is easy in Automation Anywhere. It is not difficult to get the details from the Automation Anywhere University, learn it, and do it. There is training for everything. For the APIs or document processing, there is limited material, but anyone can still learn it on the go. We have a portal where we can ask questions and get answers or suggestions.

Automation Anywhere has helped our organization increase its automation consumption, but I do not have the metrics.

I use SAP connectors, and I use Excel operations and Windows operations. I also use the OCR functionality and the functionality for sending emails. 

It is easy to learn. There is an assistant in Automation Anywhere, so even a layman can access it, utilize it, and quickly learn it. It is not a problem. It takes a week for a new person to start working on it. It is straightforward. 

There are not many areas for improvement. As compared to V11, A360 is more user-friendly and flexible. It is fine. They have even included support for ChatGPT, Azure, and other things in the latest version. They have incorporated many latest technologies, such as AI, and there is always scope to improve the processes and have more stability.

I have been working with Automation Anywhere for the past six years.

I can rely on it. 

Going forward, I can do more and more automations to save time. I can improve the business processes with the latest technologies as well, so from the scaling perspective, it is good.

I know our team is using Automation Anywhere, but I am not sure whether any other team is also using it. There might be more teams using it. 

We have plans to increase its usage. We are getting more projects.

For me, it is easy. Generally, if I am not able to understand something, I go through the documentation, and I am able to find the information quickly. In case of any issues, I inform the platform team, and they raise a ticket and get in touch with the Automation Anywhere team. They involve me in the issue description, but it is completely owned by the platform team because they do the first level of testing and go ahead with ticket creation and other things. The problem always gets resolved. In terms of time, the duration depends on the availability of the platform team. 

Positive

I did not use any other solution previously.

I was not involved in its deployment. For its maintenance, the platform team is there, and they are doing the maintenance activity.

It is an easy tool and easy technology. It is quick to learn. You can use Automation Anywhere University for learning.

Excel advanced operations are very good. Document processing is also very good. Handling of the web forms and sites is also good. Before using this solution, I thought it would take me time to automate all the processes, but I was able to use it easily.

Automation Anywhere is at the number one position now. That itself proves how good it is and how well it is doing. From the time I started using it, it has been going up. It never went down. There are more features and more technologies coming in.

To someone who wants to use API integration instead of an RPA solution, I would say that you can utilize the API integration in RPA as well. It might be a little faster in the API, but for certain business processes, you need user intervention or user clearance. In such cases, RPA is required.

Overall, I would rate Automation Anywhere an eight out of ten.

We use it for automating Excel sheets and for uploading some data.

By implementing Automation Anywhere, we minimize the manual work and improve workflows. 

The benefits depend on how you use it. When standard automation is not supported, you sometimes need to use robots to eliminate the human interface or human interference in the processes.

We integrated Automation Anywhere with ERP. We had Oracle EBS. There are always challenges, but we can overcome all the challenges. We have the technical expertise to do that. Overall, it works fine. It is good.

Automation Anywhere has saved us time, especially in distributing Excel sheets to multiple users and sending emails. The consolidation of these Excel sheets used to take a lot of time. It would take us a day to consolidate them. In case of errors, it would take one and a half days. With a tool like Automation Anywhere, we can do the consolidation within hours. If we have everything in the portal, it will do that quickly.

I am happy with most of the features. Notifications and triggers are especially good.

You can learn it quickly. All resources are available on the web. It is a matter of time. If you want to learn more, there are enough resources available online. You can log in and learn. 

It is user-friendly as compared to the other products. The time it takes to train non-technical employees varies. Simple training will take a week. 

It is a cloud solution. It is a good platform.

It is constantly improving. It is AI-embedded. They can further improve the AI. It is already at a certain level, but it can be improved.

I have been using Automation Anywhere for three to four years.

I have not worked with any other solution. I have a little idea about UiPath, but I have not worked with it. 

It is mostly in the cloud, and it is mostly deployed on the Microsoft cloud. They also have their own cloud.

In terms of maintenance, every software needs to be updated. Before upgrades, you should do stress testing and be aware of the changes. You might have to update the robots as per the changes.

It is subscription-based. They have different schemes. The price depends on how you negotiate with the local partner or local representative in your country.

It is a good product, but it also depends on how you use it. It is all about how you educate and train people. It also depends on your approach and training. 

Automation and AI, especially Generative AI (GenAI), is a trend. Everyone is looking for automation. So far, I have not worked on it. In the future, I might work on such a project.

In the beginning, automation is a bit difficult because you need to understand the requirements and other things, but later on, it gets easier. Once you have a deep understanding of requirements, it is easy to do automation. It is just a tool. Before using it, you need to have a good understanding of the process. You need to understand where the gap is, what you want to do with it, and how Automation Anywhere can help you. 

It takes time to implement automation. For example, if you are using Automation Anywhere OCR, it takes time to understand different kinds of documents or invoices. It will sometimes fail. In one or two cases, it might fail. There might be a failure rate of 2% to 3%. In such scenarios, some users might have a negative impression. You should be able to address such challenges. It is a matter of time. You need to have patience and a little bit of tolerance. It is not perfect. Nothing is perfect in the world. The users need to be educated on it.

Overall, I would rate Automation Anywhere an eight out of ten. 

My business Analysis team describes the cases, and my architect team works based on that. I look into how this architect team is working to fulfill the requirements of my client.

Our use cases mainly are for the financial domain. We are working for an international organization. The automation that we are building is going to be utilized in various projects for tracking the expenditures of projects, managing the budget, and maintaining the planning. The information is then returned to the core finance providers. 

We have integrated it with TMX and the public finance model. Government Resource Planning or GRP is integrated. We have implemented a lot of triggers to give all the information to various points.

We have our own architecture. It is able to take the information from the core engine, API engine, or triggers from databases or data pipelines and execute the process based on the defined logic. It is able to give information to various process owners using the workflow.

In most places, the processes are scheduled automatically, so it saves time because we are not executing any process manually. For example, we are able to get information about the utilization of the funds given to a particular country for a specific purpose. It triggers an alert if the funds are being spent in a particular area that is not allowed based on the business logic.

Being able to implement automation is valuable. We take the business logic and provide a solution to the client. Defining the intelligence pipeline is the most interesting and challenging aspect for me.

For us, nothing is complicated. It is quite easy. We have a competency and learning team that gives training to clients. It does not seem very difficult for them.

The approval process needs improvement.

We have been using this solution for approximately one and a half years. I do not directly use it, but my team uses it.

It is a private server farm where we have implemented AWS because the governments do not allow hosting on the cloud in most countries. This is a restriction from the government side.

We have two teams. One is the technical team, which is involved in network security and the server side. I am from the functional team where we are involved in all the services, all the applications, and all the databases. The technical team takes care of the software installation, maintenance, patches, and upgrades. We are only working on the application side.

I did not evaluate any other solution. I got the instructions from my company to use it.

We have a full-fledged deployment of automation in our organization, and we have a number of projects in the pipeline. There are definitely a lot of possibilities inside the organization, not only for me but also for my team members.

The main challenge currently is that we do not have proper resources, and the requirement of the client is very specific. Apart from that, I have not felt any problem with my team in deploying any of the solutions at the client site, so at this point in time, I cannot say that a specific technology is the best technology or that Automation Anywhere is the best. We are facing some challenges, and we are working on that. We are getting references of some of the other solutions, and we are working. We are doing the research every day and providing the solution to the client. Every day, it is a new challenge, and we are implementing the solution on the client site and understanding how to overcome those challenges.

At the moment, a person like me who is only working on one particular technology cannot compare it with other available alternatives in the market.

I would rate it an eight out of ten.

We use Automation Anywhere to automate tasks in our organization.

We needed to connect with multiple bank websites to retrieve payment confirmations. However, banks, being banks, did not provide direct API access or placed significant restrictions on such access. Therefore, we decided to utilize Automation Anywhere to collect the data and integrate it with our automated system.

At the time, all of our automation goals centered on connecting to these sites, which required a great deal of manual effort. Despite the low cost of labor, it was error-prone and highly subjective. As a result, using Automation Anywhere helped us automate this process, eliminating the need for human intervention. We were able to achieve all of our initial objectives using Automation Anywhere.

The learning curve for our non-technical users was a couple of days.

We aim to automate our activities that currently require human intervention, which is susceptible to errors and inconsistencies. This approach is similar to how others have successfully employed AI or RPA tools. Our primary objective is to ensure that our processes are scalable and repeatable.

We successfully integrated Automation Anywhere with our local database. Like any implementation, we faced some challenges with change management, understanding, and other issues, but ultimately, it was a success.

Automation Anywhere helped save the organization time and money.

The overall usefulness of Automation Anywhere is the most valuable aspect of the solution.

The price has room for improvement.

I have been using Automation Anywhere for four years.

Automation Anywhere is scalable, but scaling it can be costly, making it a matter of economic viability for many organizations.

The support is good.

Positive

The implementation was completed by the Automation Anywhere team.

Automation Anywhere is expensive.

We also evaluated UiPath and Selenium, but we ultimately selected Automation Anywhere because they had more experience in this area, which gave us greater confidence that the project would be successful.

I would rate Automation Anywhere eight out of ten. Automation Anywhere is a versatile and powerful platform, but it exceeded our organization's budget.

Maintenance requires three or four team members because the target systems tend to change.

Our clients use it for different things. One uses it for invoice processing and another for the aggregation of documents based on certain characters. Another uses it to automate processes for the admin department. That company has seasonal workers, and they have to create passes for those seasonal workers. Most of the document uploading and validation is done by Automation Anywhere. Most of those documents are issued by the federal government, and they have a standard format.

One thing I really like is the recorder where you can connect with multiple systems. The OCR is also good. In one case, we used a different OCR than Automation Anywhere, but in document processing, using the OCR engine is good.

And providing automation at scale is something I feel is a strength of Automation Anywhere compared to most tools. It depends on the segment we are dealing with. There are small organizations that might not need robust applications, but for mid-sized and large customers, we usually propose automation anywhere. It's quite robust, and the performance is good. When we are proposing a solution, the automation at scale makes it much easier for us, post-sales and post-implementation.

Also, the integration of the solution's bots with APIs and business applications is good. There are certain prebuilt integration APIs in Automation Anywhere. That's especially true when you're connecting with SAP. There are issues with SAP, but in general, they have connectors with most of the popular CRM tools. The API connectivity is much easier.

We only faced some problems when integrating it with SAP, and Oracle integration was a bit challenging, especially with Oracle Fusion. We had some issues when we were trying to connect some of the applications on the API level. But, in general, integration using Automation Anywhere is fine.

I have been working with Automation Anywhere since 2019, or about four years.

In the last year, the cloud has become bigger, but before that, it was implemented more on-prem only. 

From our side, the number of staff needed for an implementation depends on the number of processes we need to deploy. For the initial configuration, we may not need many people. But, for one of our customers, there are 70 processes that need to be developed over the next 18 months. Obviously, the number of people involved will be much greater than in a project where we're looking at 10 or 15 processes to be implemented. But on average, each process takes at least two to three resources, depending on the complexity.

Once you have deployed an application, you need to maintain it. Compared to other products, it takes slightly fewer people. Maintenance on the admin side requires one to two people. We always assign one FTE for this, at a minimum. Depending on other factors, we might go for two.

Automation Anywhere is more stable compared to some of the other tools on the market. And, post-implementation, we have very few issues with it compared to others. For me, it's all about post-implementation and why customers are happier with Automation Anywhere.

For small and medium-sized customers, we may not suggest Automation Anywhere because of the cost difference.

UiPath has gotten much better in the last two years. They have really grown in terms of overall performance and bot capabilities. There has been a huge improvement there.

As for non-technical users, it's not a low-code type of solution where you draw and drag and drop. Still, it's okay, to some extent, if they at least have some understanding of technology. Generally, it's easy to learn. If you have access to Automation Anywhere University, you can really learn it. But because I am from a technology background, it was much easier for me. We give our customers 13 or 14 sessions to bring them up to speed, and that might span over the period of a month to two months.

In the discussion about RPA versus API integration, one definite advantage of automation is that scheduling, bot management, and those kinds of things are automated. It's more about the customer and their perspective. With automation, you already have something cooked up, and you don't have to worry about much at a later stage. That makes automation much easier for them than using an API integration. You have to maintain an API integration, and there is the cost of maintaining it. With all those factors, automation becomes much easier for the customer.

We have been proposing Automation Anywhere to multiple customers. It's good. It's robust. But it's a bit expensive compared to other RPA tools on the market. Sometimes, it's too heavy for customers, especially if it's on-prem. Also, maintenance is slightly higher.

I worked for a call center company and most of the use cases were related to developing automation for our clients. We also created some automation for internal processes.

The integrations of Automation Anywhere with the mainframe application for banking companies are among the most valuable features. Banking companies have a black screen (a text-based user interface) used in some banking core systems. In our case, we were able to create very good solutions integrated with that kind of platform using Automation Anywhere. 

Also, if you need to use OCR automation to process standard invoices and send the information to another platform, that is also a very good feature.

The goal of any automation is to provide efficiencies. I would like a way, within the platform, to track the benefits. If you are the center of excellence manager, you need to show to the C level the value that you are adding to the company. The unique way to show that to the C level is how much money you are bringing into the company or how much money you are saving the company in costs. I would like a default feature where each bot gives us data on all the benefits it provides from its process.

They also need to improve and work very hard on the user experience to democratize automation.

I have been using Automation Anywhere for four years.

It's a very good platform in terms of stability.

Automation Anywhere has very good scalability when you want to scale an existing bot.

It is very easy to contact them and receive support from them.

Positive

We were working with a local system.

The initial setup is very easy. If you are not setting it up in a virtual environment, it takes between half an hour and one hour, maximum.

We have deployed it on the cloud, using AWS.

There is no maintenance of the solution on our side.

My team did the setup.

These types of companies, in automation, need to evaluate their business models. They sell it by license, but if they could charge by case or by interaction, that might be better. Right now, it's expensive when you want to scale or use them for simple processes.

I know my Automation Anywhere, UiPath, Blue Prism and, now, Microsoft Power Automate. If you want to automate a simple process, these solutions are very good. But if you need to integrate different platforms or systems using an API, or if you want to widen the scope of automation to create an automated process, end to end, that is going to be difficult for any user. You need to be a developer with very good programming skills. If you are going to automate, for example, downloading emails, Automation Anywhere is okay for non-technical users. But the license is very expensive, so you have to weigh the benefit that you are going to receive.

For me and my team of around 150 developers who are engineers, the learning curve was very easy. For them, it took two or three months because they were already familiar with the logic. Automation Anywhere has good information on the web where the guys can access material and forums to learn about creating different types of automation.

The benefits, for us, from Automation Anywhere are more related to the business case than the tool. You need to have a very good approach from the business analyst's perspective to understand the added value that an automated process can bring to the company.

The most important thing is to train the business analysts in your company to identify what the best processes are to automate, to get the most benefit from the tool.

Overall, this is a very good tool if you have all the permissions and accesses, and you can work without any virtual environment, like VDI or Citrix.

We typically use Automation Anywhere for backend operations and financial processes, such as APR.

The biggest benefit of Automation Anywhere is that it makes our processes error-free. Accuracy is how you build efficiency within the system and increase productivity.

Document Automation, one of Automation Anywhere's core features, is excellent. All the other features are also useful, and their cloud solution is pretty seamless. 

Automation Anywhere is relatively accessible to non-technical business users. It's about 60:40. Around 60 percent of the solution is intuitive, but you still need to do some work to learn the platform. The company offers strong learning resources. Most people can easily learn Automation Anywhere in a couple of months using tutorials.  

Automation Anywhere works with POST and REST APIs, so it's easy to integrate with any platform or application. Automation Anywhere is applicable to any industry or department where there are large volumes of processes that are straightforward and require no manual human intervention. 

I have used Automation Anywhere for nearly four years.

I rate Automation Anywhere 10 out of 10 for stability. 

I rate Automation Anywhere 10 out of 10 for scalability. We usually optimize one or two processes until we can achieve an ROI and scale them up for the entire organization.

I rate Automation Anywhere support 10 out of 10. They have a solid team to address any issues or glitches as they arise. 

Positive

We typically deploy to Automation Anywhere's public cloud. We haven't used the private cloud option because it's expensive. I'm the project delivery manager, so I was involved in the deployment. It doesn't require any infrastructure because it's in the cloud. 

The deployment time depends on the complexity of the processes. Simple processes can be configured in a couple of weeks, but complex projects might take up to three months. 

The number of people involved also depends on the client's needs and the licenses purchased. You need a developer license for each engineer. Automation Anywhere licensing is based on the individual users, not the partners. For example, let's say a project will take one engineer three months, but the client wants it done in 45 days. You would need to double the number of engineers and pay for an additional license. 

Automation solutions require some maintenance and change management because no process remains constant. You will need to update and optimize the bot as the process mechanism changes. 

We have seen an ROI. It's hard to give a solid metric because every organization has a different way of calculating it and it varies between processes. However, I can say that Automation Anywhere reduces costs while increasing productivity and accuracy. By automating repetitive tasks, we can shift our human employees to more productive work that requires imagination and creativity. 

Automation Anywhere is expensive. They should consider lowering the price to make Automation Anywhere more affordable to SMEs, which comprise a huge segment. The license is annual, not monthly. You need to pay for some of the advanced features, such as document automation, which doesn't come with the base package.

I rate Automation Anywhere nine out of 10. RPA can be integrated with API and integrated on top of any application. However, it's always better to go with API if you have that option. It's steadier, more scalable, and more robust. The best part about RPA is you can create a hybrid model, so you can use API when available or RPA when that isn't the case.