Automation Anywhere Reviews

Vale is one of the largest mining companies in the world and Automation Anywhere is our primary process automation tool. We're using it globally across several branches and locations. There are multiple processes involved in mining, transporting, and shipping iron ore that benefit from process automation. We can also automate our corporate use cases, such as finance, HR, and back office processes. Automation Anywhere is integrated with our core company systems, including SAP solutions and some in-house applications we've built. 

Automation Anywhere enables us to standardize and replicate operations and processes. We have a lot of repetitive processes that are time-consuming to perform manually. We aim to increase productivity and save time for our business users. Over five years, we've saved about 68,000 hours. Automation Anywhere integrates well with our workflows and business applications. We haven't had any issues.

We see some cost savings, but we also tend to think of cost avoidance. We have some compliance and regulatory processes that need to be completed in a timely fashion to avoid fines and taxation on top of that. Our CoE is responsible for a critical portion of the automation. In addition to thinking of how we can automate existing processes, we create new processes. When you automate something that isn't optimized, the results aren't as good. 

We like Automation Anywhere's Citizen Developer program. We've been doing this for a while now. It helps to expand platform adoption within our company and encourage more people to use it. It has been good to see the engagement. We've done some events and hackathons and hope to do another one in November.  We like having an easy tool to share with our business users. 

It isn't hard for business users without technical skills to use Automation Anywhere. We've received positive feedback from them, saying it was an easy tool to learn, especially with the latest version. We set up a training program, and new developers can learn the basics in around a week and start programming bots in three weeks to a month. 

We are currently doing some PoCs for generative AI and trying to see if it fits, but we're also concerned about the safety of our users and information security, so our approach is always conservative. We don't want to do anything that creates unnecessary risk for the company. 

Our users would like more online community forums where they can exchange information. I would also like a better way to monitor and manage all the automations we have running within our systems because our CoE governance must be robust so we are always aware of what's happening.  

We have used Automation Anywhere since 2018.

There have been some changes in personnel over the years, but they have always been great people who provide excellent service and solve problems quickly.

We previously used Microsoft Power Automate.

The platform was not hard to deploy, but each company has its own security protocols to deal with. Once we worked through all the security requirements, it was straightforward. Automation Anywhere requires some maintenance. 

In the first year, we needed to adjust the size of the machines and optimize the bots. However, it hasn't required much maintenance since then. We developed some better processes in CoE governance to develop and track the bots, so it's much easier now. We set up alerts that send us messages when the bots have errors. 

In 2018, we looked at some other products on the market, but Automation Anywhere was a perfect fit. We didn't have any issues that Automation Anywhere couldn't solve. The critical factor for us was its ease of use. We liked the drag-and-drop interface and the low-code capabilities.

I rate Automation Anywhere eight out of 10. 

Our use cases are around finance processes and one business function that we have a lot of automation. We're an agriculture and supply chain company, so we also have a lot of processes that would deal more with order processing, order management, customer service, and those types of processes.

We also have a use case from a document processing standpoint. We have a use case where farmers in Asia, in the APAC region, would handwrite inventory of that particular product, send a photo of it, and then someone would manually take that information and put it into the system or put it into a spreadsheet. We've been able to automate that. It not only saves time, but the data is 85% to 90% accurate versus it used to be about 60% beforehand.

We're finding time savings as a benefit. One example would be a customer service rep might get a question about an order, usually through email. It can take a good three to seven business days to answer a customer's question about their order. When we automate it, it takes hours, if not minutes.

We also are building out a new model for our metrics. Our biggest challenge is because Cargill is an international traditional company, we work with many different regions that have to abide by certain local rules and regulations.

We don't have just one order management process at Cargill. We have over one hundred and trying to simplify those processes first before we automate it is our biggest challenge. 

We're in conversations with Automation Anywhere now about process discovery. We've just kicked off. We are installing a tool with process discovery that we still haven't figured out what the best practice for utilizing it with Automation Anywhere will be.

We have a federated model. We are a center of excellence. We own the platform, and we build out the governance framework. We also provide training and updated communications to all of the users.

The learning curve is small. It takes only about four hours to learn it, but hands-on experience is different. That's what takes a little bit longer. Some users sit within IT, and some of the users sit within the business. It's fairly easy to teach others to leverage it. They have to have an interest in learning it, but it's fairly easy. 

Overall, Automation Anywhere has helped us save time. But we're also looking at customer satisfaction. We track sustainability numbers, if that comes into place. So we have a lot of different metrics that we look at versus just time.

One of the reasons that we chose Automation Anywhere years ago was because of the security because we need to secure both our customer and our vendor data. 

We have a lot of confidential data that we work with every day. 

Automation Anywhere has an audit tracker feature. When you build a bot, it has a trail of how you went about developing that particular bot.

We integrate other tools within Automation Anywhere. Overall, it's fairly easy. We have about 265 bots in production today. We see bigger challenges on the business side if they change a template and then fail to tell us that we need to change the bot.

We leverage IQ BOT. We have another tool that we leverage as well for document processing called Intelligent Document Processing (IDP). 

I want to learn more about CoPilot and then the process discovery tool. 

We are part of the Pathfinder program. It's more of a program versus a tool, but we're working with people to learn how we can scale our whole program using Pathfinder.

We've been using Automation Anywhere for about five to six years and continue to scale about 50 bots per year.

I'm very comfortable with being able to scale, especially now that it's moving into the cloud.

We've had really good support with Automation Anywhere. 

We have weekly tech meetings with Automation Anywhere. I also have strategic meetings every week and quarterly strategy planning meetings. We have a really good support system.

Positive

UiPath was one of the competitors, and we did bring on UiPath specifically for the Chinese language. That program has not scaled as we expected so we really are an Automation Anywhere shop.

We're going through the 360 migration right now. The bots that we have in production are fairly complex. It hasn't been an easy migration. We're getting through it, and we have a lot of support to get through the migration. But it's really more of the complexity of our organization.

We wanted to put together a streamlined platform versus having puzzle pieces and taping them together using different vendors. 

I wanted us to be more streamlined so that we don't have glitches down the road with upgrades and version updates. That's one reason that I wanted to stay with Automation Anywhere. 

Overall, I would rate the solution a seven out of ten. The only reason I wouldn't rate it higher is because a COE Manager still not getting the full benefit from it and because the premium is a little bit expensive. We don't necessarily have the budget to bring on a full new feature. Also, the process discovery tool is taking a little bit longer to implement than I thought it would.  

It helps to free up our staff to work on value-add projects. It has saved their effort. With the automation of their project, a task that would have previously taken ten hours can now be done within four hours. We can then have them on other projects where more resources are required. They can utilize that time.

Automation Anywhere has helped our organization increase its automation consumption. In the last three years, we have used Automation Anywhere excessively, and in terms of cost, we have saved up to 50,000 to 60,000 dollars in three years.

I have used Automation Anywhere, UiPath, and Blue Prism. The licensing cost of Automation Anywhere is better than UiPath and Blue Prism.

Features such as MetaBot and IQ Bot are very advanced and capable as compared to reading PDFs using OCR.

It is very easy for me to use, but for non-technical users, Automation Anywhere is a little bit challenging. If you have previously worked with any other tool, such as Blue Prism, it is a little bit difficult to understand because the nomenclature and terminologies are a little bit tricky. After you have hands-on experience with it for six to seven months, it is quite easy to understand. 

Automation Anywhere's UI is difficult. Its user interface can be improved.

They can improve their community so that if any help is required or if we face any issues, we can easily go there and get the help needed. In the case of both UiPath and Blue Prism, the community is very good. Everything is mentioned in the community. We just need to type a keyword, and we get the solution we need. It would be great if Automation Anywhere could improve their community.

In terms of additional features, there could be support for the cloud-based technology so that, similar to Orchestrator, we can use the control center from the cloud. It should be on-premises because a lot of financial institutes use automation, and they cannot upload their data or transfer their data to a third-party cloud. It would be good if they could host the system on the organization's premises.

I have been using this solution for the last five to six years. I am not using its latest version.

It is not as stable as UiPath and Blue Prism. There are some software crashes.

It is scalable but they need to enhance their product so that when any huge load of data comes, it does not crash. If we have to work on a million records of Excel data, it would crash.

They have a support channel where we can raise our concerns. If we cannot understand something or we do not have a solution for something, we can raise our concerns and requests in their support channel, and they provide the response or solution. We just need to create a ticket. I would rate their support an eight out of ten. Their support is good.

Positive

I have been working in the automation field for the last 11 years. I started my journey with Automation Anywhere, version 10.7. After that, I started working with UiPath and Blue Prism. I work with all three RPA solutions. I am an expert in all these three solutions, and I am also certified in these three solutions.

We utilize a solution as per the requirement or process. UiPath and Blue Prism are easier to learn than Automation Anywhere. In terms of performance, if you use heavy logic or complex logic, Automation Anywhere isn't as stable as compared to UiPath and Blue Prism. Blue Prism is very stable if you build any process or do automation of any process, whereas in the case of Automation Anywhere, your application or your process can break. However, Automation Anywhere is quite fast. The setup is quite easy. You can easily set it up on your system. The UI is very fast. There is no lag.

I installed it on my personal laptop, and it was straightforward, but for the production environment, the Infra team takes care of the installation. It takes them a maximum of two to three hours.

It is on a cloud. It is hosted in the Citrix environment, and it is being used by multiple departments. We need to log in to Citrix to utilize it.

Its maintenance is handled by our Infra team. If there is a patch release with a feature or fix that we need, the Infra team updates its version. Otherwise, we keep utilizing the same version. Our Infra team has access to the Citrix environment. They can create and close the Citrix environment, and that is why they do the maintenance. Any maintenance activities are done over weekends so that none of the in-progress processes get affected. Generally, they happen over weekends. They usually start on Saturday and then the activities are complete by Monday morning.

We are investing a lot in the licensing cost. If there was no ROI, our organization would not invest in it. We calculate the efficiency in terms of the effort saved by our full-time employees, which could vary depending on the processes. There could be 2% or 5% savings monthly, and based on that, we calculate the annual savings. Overall, there could be a 10% to 12% improvement in efficiency.

Automation Anywhere's licensing cost is better than UiPath and Blue Prism. The licensing cost is a big factor because you might have 50 or more bots, and the per-bot license cost is about $5,000. That is the amount that you need to invest.

We have explored various RPA solutions such as Kofax. We generally go for solutions like Automation Anywhere, UiPath, and Blue Prism because of their capabilities. Our clients also want the best and the most cost-effective technology.

I would recommend Automation Anywhere, but it also depends on the cost. If you get a good discount on the license, go for it.

Automation Anywhere is easy to learn if you have experience with automation tools. If you are starting from the beginning, you will have to invest more time compared to the other RPA tools. It could be a bit difficult for non-technical users. You at least need to know what data variables do and what strings do. All these things are technical. You would also need to write VB or C# code, so non-technical people cannot work on these things.

Any integration completely depends on the application support. We have integrated ServiceNow API with Automation Anywhere. If the API is already provided by the organization or the development team, it is quite easy, but if we have to design the API or it is not available, it is a little bit difficult to integrate the application with the automation tool.

To someone who wants to use API integration instead of an RPA solution, I would say that based on my understanding, API integration is completely different from RPA. RPA is an end-to-end solution. It can automate your desktop applications. It can automate your browser-based application. API and web services are also included in RPA, so RPA is a complete ecosystem. API is just one part of it. Only through API, you cannot do automation. Through API, you can get values, and you can put values. You can modify values. You can generate a request or an incident, but creating a report via that data and replacing that data is not possible through API. You have to do it manually, or you have to open it in Tableau or Power BI and create a dashboard. By using an RPA tool, you can download data. You can change the request. You can get the request. You can modify those values and manipulate them according to your requirement. You can then create a dashboard. 

Overall, I would rate Automation Anywhere a seven out of ten because of the stability and the terminology used in the product. The terminology they use is not for the layman. If I have to showcase it to my leadership, they would not be able to understand what MetaBot and IQ Bot are and why we use them. I have to make them understand in layman's language.

When I started working with Automation Anywhere, I automated mutual fund statements. Later, I switched to a financial services company, so that involved a lot of monotonous rule-based work that we had to automate. Then, I started working for this oil and gas company. We focus on finance, procurement, IT, legal, and refining processes. 

I've seen business users doing this kind of repetitive work for 20 years, and they feel that there is a better use of their labor, so I wanted to automate things for them. For example, in the oil and gas industry, we need to extract information from purchase orders that we must pay out on invoices to various contractors. It's possible to improve efficiency by as much as 20 to 30 percent by automating those processes. We can do even better by asking the right questions to the business stakeholders. There's potential to automate and improve on things they've done manually in the past. 

We see opportunities to operationalize AI for HR use cases. For example, we need to gather documentation for work travel, including a visa if an employee plans to travel abroad. Instead of having an employee ask HR folks about the process, we can set up something with generative AI. AI would also be helpful in some finance use cases. We still need to do some PoCs for generative AI before moving forward. Our data science team is working with something similar, but I haven't used it yet, so we need to try some smaller PoCs before trying it at a larger scale. 

Automation Anywhere saves money. At my previous employer, we achieved $1.3 million in cost avoidance over two years. I expect to realize that much savings in my current role, but we are still in the enabling phase of our CoE. Next year, we'll complete large-scale automation. That's our goal.

UI and document automation are two features I like. Document automation is helpful because it simplifies extracting and putting data into different ERP systems. I have three or four use cases for document automation. I also like the recorder objects feature, which was called object learning in the previous version, and screen scraping. 

It's easier for business users to work with Automation Anywhere A360. My previous employer used Automation Anywhere version 11, which was sometimes a little difficult. A360 is much more interactive. We have several users in our organization who have a business background, so it takes some time with some of the use cases. A business user might take two months to build more challenging use cases, whereas a developer could do it in three or four weeks. Though it takes longer, we want them to learn and implement Automation Anywhere. 

Automation Anywhere is interactive, and my experience with my coworkers has been positive so far. I'm on the CoE team, and we've been working to enable various functions involving the HR, IT, finance, and refining teams. They are using it. On average, it takes a month or so to train them, build their use cases, and put them into production. 

The solution is currently integrated with PeopleSoft, ServiceNow, and SAP. The document integration gives us about 70-80 percent accuracy. We're mostly working on purchase orders, but I want to implement it for financial use cases, too. I'm trying to determine what the most efficient one is. 

When we need to upgrade the bot version for various applications like SAP, the compatibility issues could be easier to resolve. The financial team is using version 5 or 6, but the automation engineer recommends only version 6 because it is more compatible. I think Automation Anywhere could handle these compatibility issues better. 

I have used Automation Anywhere for nearly seven years now.

Automation Anywhere is scalable, but it depends on what you do during the design phase. You must consider the opportunities for scaling up while you're planning. It's easy to scale if done correctly. 

I rate Automation Anywhere support nine out of 10. It's excellent. We have premium support. Our account manager is very nice. If we raise an issue, it will be resolved the next day. 

Positive

We also have Power Automate, but we do not use it at the enterprise level. We only use Power Automate for two use cases. A different team uses Power Automate, but they are not associated with the CoE. They are only using it for personal automation. 

Deployment is easy, but the testing takes time. It also takes some effort to migrate the bots from version to version, like v11 to the cloud version of A360.   We learned it the hard way, but once we moved to A360, that took care of many of the infrastructure issues we faced with the on-prem version. It was mostly some technical challenges, not infrastructure-related changes. The cloud version is much better than the on-prem. 

Automation Anywhere requires maintenance, but how you develop the processes also matters. We try to implement best practices, like using wildcards instead of URL names. That's why we try to find ways to make API calls instead and get the data from there. We are currently doing a PoC that involves retrieving the data from third-party websites, and they told us that they could build an API that would make it easier to maintain. The APIs work better than redirects. 

I tried UiPath, but I didn't like it as much for our current use case. Automation Anywhere is a better fit, but I have used UiPath at three organizations as a contractor, consultant, and full-time employee. 

I rate Automation Anywhere 10 out of 10. 

Automation Anywhere is an RPA tool. The use case is the same for all automation tools. In my most recent project, I've used it for three-way invoice matching and sending it to the accounts for verifications. The process was a mixture of IQ bot, which is an OCR from Automation Anywhere, and then other RPA bots. 

I've used it in health care, where people apply for insurance applications to the insurance companies. 

I have implemented more than five hundred use cases as of now.

It's helped manage repetitive processes. If there's a repetitive process, that is our best use case, and we can pitch to the customer that we can make it shorter. Then we save them man hours and increase their efficiency and accuracy. 

For example, mostly in finance, when companies are preparing the salaries and have to prepare 1,500 payments for employees, sometimes they make mistakes, and they have to spend time on that. 

We can instead provide a fixed format for the robot that they have to follow every month, and it saves a lot of time, a lot of man hours. One of our customers here in the Middle East has saved around 10,000 man-hours for a telecom company with the help of 50 to 60 robots initially, and now the same company is using around 4,000 robots now. 

It helps save time on manual tasks. Compared to manual input, the results are much better, faster, and more accurate. For example, we have clients that can now easily process 10,000 invoices in one day. They have around 55 employees for that. We can augment the workload with a root, and if an employee wants to take a holiday or needs sick leave, other employees don't have to pick up the slack. Robots can input information into the system. 

The era of automation has changed. It's time for hyper-automation now. RPA is moving from just handling repetitive tasks to allowing for AI and offering automation plus conversational AI. It will help me. Soon I will be able to use it in WhatsApp, and all of the information can be entered, and you can initiate appointments, et cetera. RPA plus conversational AI plus AI-enabled OCR systems will be the future. 

There are a lot of great features, especially the IQ bot. It has very good accuracy on invoices. Previously, we were dependent on different software, and now, we can build in Automation Anywhere only.

It's easy to use for non-technical people. It's not rocket science. A business user might take a few weeks or a month to learn it, and then they will be quite capable of doing things themselves. A technical person may learn it in 15 days. Everything needs time; however, the learning curve is not so bad. A lot of things are available to help with learning. If someone spends one or two hours a day, they will pick it up. You can Google information or watch YouTube videos. There are hundreds of demos, materials, and more free of cost.

We do use CoPilot. We try to build a center of excellence with all customers, and we're giving them training around any bottlenecks they have.

The solution has helped us increase productivity. How much of an increase differs from customer to customer. Usually, it improves by 20% to 30%.

There's lots of integration possible. We've integrated with business tools like Oracle, SAP, and Salesforce. We can integrate easily into various workflows and APIs. We can access APIs with just a few clicks. We can also build out a UI-based integration.

It's helped us save time. Every customer saves a different amount of time, percentage-wise. Some can save hundreds of hours.  I've had a client save 30% of their time over the past few years thanks to automation. 

There is a dependency issue around the control room. If the control room is not working, the bots will not work. When that happens, we have to wait for the control room to go back up. Other tools in the market do not have this issue. If something is down, it means everything is down.

I've been using the solution for three years now. However, I've worked with automation in general for six years. 

The solution is stable. It's good software. It works well. 

The product scales well. 

Technical support is good; however, sometimes it takes a while to solve problems.

Positive

I previously was using UiPath. It's quite easy to use. They are both very similar solutions. 

I was mostly involved in the infrastructure, so I was not directly involved in the deployment. My understanding is that it is not difficult. However, when we upgraded it, we had challenges. 

There is some maintenance required. Normally, it works fine. Sometimes, there may be migrations or updates required. Only one or two people need to handle maintenance. We don't maintain bots. However, we just deploy them. Maintenance can be completed by the customer, and it might take five to six hours or one day at a maximum. 

Compared to Microsoft, the solution is expensive. However, compared to UiPath, it's fairly low - maybe 25% less. Generally, within the market, the price is average. It's competitive.

I'd rate the solution eight out of ten. 

We're a reseller. 

I am working with an integrated resort. It is a hotel with a casino in Singapore. There are about 130 manual processes that we have automated touching the front office, call center, back of the house, finance, facilities, and casino areas as well. We have automated scheduling and workforce planning. 

My business is divided into what we call gaming and non-gaming space. It is an integrated resort. We started out by automating use cases from the non-gaming area. In the third year, we started venturing out a little bit into the gaming area. We did not go into the heavy gaming areas such as on the casino floor. We went for support processes at the back of the house, which included scheduling and things like that. We are also doing reporting. 

Most of what we have is for attended and unattended bots. We have just started to use Co-Pilot or what used to be known as AARI. It is something new for us, and we have only one process using that. It is a pilot project. It is something new that we started now in our fifth year.

Automation Anywhere has helped our organization increase its automation consumption. It has helped the business address some of the pain points. It has helped the business understand that there are other ways of doing things and getting out of the manual processing. We come from a heavily people-oriented industry. We are into hospitality where you need the human touch for our business. We are not a bank. We are not a financial institution. The mindset change that I have seen with my business stakeholders because of the automations that we are doing for them is a plus. It is a game changer. In our first year of doing this, we started out very small. I had a team of myself and one developer, and now, in our fifth year, we have over 130 bots touching over 40 business units. I now have a team of four people, so we have grown. We now have a culture or ecosystem where the business stakeholders know that if they are still doing something heavily manual and highly repetitive, and it is not adding any real value to the time of the team member, there is a team within the organization that they can approach. This team will help with whatever pain point they have or take that task out of their day-to-day work so that they can concentrate on higher-value activities. This whole mindset or this whole culture or ecosystem is now there in the company. Automation Anywhere has helped elevate the consciousness of the organization by realizing that there is an automation world out there, and we can bring solutions to the table for their problems and use cases.

When it comes to integration, we have been lucky so far. We use many applications. The processes that we have automated touch 30 to 40 applications that we have in-house. It is seamless. It is fine, but some of the third-party applications that we are trying to integrate with are not necessarily very automation-friendly. The objects of those third-party applications are always changing, and therefore, we constantly have to rescript, but that is not necessarily Automation Anywhere's problem. That is just the nature of the other third-party applications that may not necessarily want you to be automating or layering on top of their systems and get behind their applications. I have been lucky so far. We have not had to go back to a business and say that we cannot automate their process because Automation Anywhere cannot integrate with a particular application. I have not had that experience as of now.

The learning curve of Automation Anywhere for my own team was pretty good. If you are a full-on developer, it is one of the easier tools to learn in the market. It is pretty good as long as this is something that you are using regularly. If you are a dedicated person doing the development and working with the tool, it is very easy to use. As far as my developers are concerned, it is very easy. We are able to turn around projects or use cases in three to four weeks. For even complex ones, there is a fairly good turnaround time in terms of delivering to our stakeholders. We do not train nontechnical people on its use. Businesses only receive automation from us, so they are not trained on it. If they are going to be trained on it, it is only on how to run their bots, and that is a part of our production development checklist or lifecycle that we give them. It just takes a day or two because we only teach them how to run their bots. It is delivered to them. We do all the installation on their machines. We set up their machines, and then we teach them how to run the bots.

When we first engaged with them, we thought that we could easily go into what we refer to as a citizen developer type of framework, but that did not go too well. We rely heavily on the CoE team, which is my team, to do automation. We have a build and support model for our business users. Business users are only taught how to run their bots. We do not teach our business users how to build a bot. We tried that and did some training with some key business stakeholders. It was a three-day training, but it did not prove to be too successful. After the training, they go back to their business units, and if it is not the core or what they do on a day-to-day basis, it is very hard to sustain, so the main building and the heavy lifting came back to the CoE team. Our team delivers to business units. From that perspective, I would rate Automation Anywhere a three out of five. Business users cannot just go ahead and build their own bots without really learning and understanding the tool.

The whole suite of RPA modules that they have is very good. They have three environments in which you can do your automation. You have development, staging, and production environments. These are run by licenses as well, which is very good. There are a lot of ways of automating processes with this application. I am not a developer. I run the RPA CoE team. I have a team that does the actual development, so I cannot speak of features per se, but the whole RPA module that they have is one of the best in class.

It is easy to use. When you need to make changes to your automation, it is quite quick. You do not need to go through the whole script. You can do it in modules or subtasks.

There are several things. They can improve their billing. I have had issues with their billing.

Their license model needs to be improved. The biggest issue for me is that the license is tied to a person, and it is not something that I can pass if I want to use it for the first five hours and pass it on to you for the next five hours and so on. When we automate, the license is tied to me, and if you or somebody else needs to use that license, as a COE administrator, I need to transfer the license from person A to person B. This is something that I have always told them that should not be this way because you want to utilize your licenses effectively. You want to ensure that your utilization of licenses is maximized throughout the organization because you are paying on a per-license basis. If it is tied to a person or to an AD account, how can you pass on that license to others to use if they are from other departments? If there is one big thing that they could change in terms of the subscription model for a license, it would be that it should be concurrent and not tied to a user.

In terms of the product, they can improve the upgrades. They are in A360, which is the cloud version. They went from version 11 to A360, and there are new updates and features all the time. Sometimes, these upgrades break other things that were working previously. We have found out that there are some bugs that are going on with the updates. Because they are on the cloud now, they do every quarter some kind of upgrade or patch.

I have been using Automation Anywhere for the past five years. We started out in 2018. I was scouting around the market for an RPA vendor. I am based in Singapore, and after doing a study of top vendors at that time, I decided to go with Automation Anywhere. We are now in our fifth year of engagement with them.

Automation Anywhere is very good at providing automation at scale. We have about 130 bots. They absolutely have the ability to scale for me. Their platform is geared towards that. It is all license-driven, and it is quite easy to scale using this tool. The infrastructure is dependent on us as a company, and making sure that our environment is ready for all the builds that we need to do, the development that we need to do, and the rollouts that we need to do, so there is a handshake between the company and the tool. It is not very complicated once you get the rhythm and once you get your governance going. It is quite good.

I contacted their technical support when some of the functionality broke because of an upgrade or the functionality did not seem correct. In some of those cases, as a client, we were the ones who told them about an issue or a bug in a particular feature. We appreciate that they came back and said that it is correct, they are aware of it, and it is going to be fixed in the next release. We have had a couple of those kinds of instances.

I would rate their support a seven out of ten because we had issues with them in terms of response and in terms of trying to get to the root cause of a problem. We had just migrated to A360. We were on version 11, and we had to switch over because it was going to be end-of-life or end-of-support. They were pushing all their clients to move to A360. In the beginning, my team had to tell their team that these are some of the issues that their A360 tool has and these are some of the bugs. They were a bit slow to react and get to a resolution or root cause.

Also, in the beginning, we were communicating with so many people. There was no continuity in terms of the person handling the ticket. They might have been changing shifts, but when you leave clients to repeat themselves to a new set of people they are talking to overseas, it gets a little bit annoying. I did highlight this point to their management team, and ever since I did that, their support team started handling the account a little bit better, but that is the reason why I am giving them a seven out of ten.

Neutral

We were not using any other solution previously. It was our first foray into robotic space. We have been with Automation Anywhere ever since.

Our setup is hybrid. Our control rooms are on the cloud. We are on A360, so our control rooms are on the cloud, but our bots runners are on-premises.

I was involved in its deployment. When we did this at the initial stage in 2018, it was pretty straightforward. They provided great support. We started out by doing eight processes as a pilot. 

Their team provided the developers because I had no developers on my end at that time. Their team did it remotely. They were probably doing it from India. They gave us the requirements. They educated us on what was needed and how we needed to set it up so that they could connect to whatever systems they needed for the eight processes or use cases that I had chosen. They did deliver all those processes within two weeks, so it was pretty straightforward.

Their professional services team was top-grade. They knew what they were talking about, and the people that they gave me in Singapore at that time were very good.

In terms of maintenance, it does not require any maintenance from my end. They do a quarterly patch of it. They announce that they are doing a patch, and it gets done. There is no maintenance on my end for the tool. What I need to maintain are the bots that we have built for the business. That is where the maintenance is, but that is more on our end. That is mostly because the bots break because of the change in third-party applications. 

They had about two or three developers doing the work remotely. There was a salesperson who was based in Singapore, and then they had sent two people from India to come over to Singapore to handle the account in terms of education. We had a program manager as well as a solution architect.

Five years ago, we looked at UiPath, Blue Prism, Automation Anywhere, and WorkFusion. We did the scoping in terms of SWOT analysis, and we found Automation Anywhere to be a better partner to work with and a more stable one in 2018. 

To those evaluating Automation Anywhere, I would say that make sure they give you somebody who really knows the tool and they explain the RDLC and the delivery method to you clearly in terms of what you need to set up within your company before you engage. You need to ask the questions because it sounds simple, but it is not that simple, so you need to ask what are the things that you need to have in place in your own organization so that it is a successful rollout.

I was sold on the idea that it is an easy tool to use. Anybody can do it. They do not need to be full-stack developers. Our regular team members can pick it up, but as I got into it, I realized that is not true. Not everybody can do this. You need to have a developer mindset. You need to know how to code. It is not something that anyone can do. That was one thing that I had to learn the hard way. I realized that this model is not going to work for my company, so you need to ask questions. Understand the tool, and make them do a deeper demo in terms of how to build a bot or a complicated process. Do not go with a simple and easy process. If it is of medium complexity, find out how a regular person would do that. Ask them, for instance, what would you need to get this going. Understand the tool and spend more time with the tool before committing.

To someone who wants to use an API integration instead of a robotic process automation (RPA) solution, I would say that if you are doing it through API calls, it is a better way to go. It is more stable because you are doing it from the backend. You are getting connections there rather than using RPA from a front-end perspective.

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

Our clients' use cases for Automation Anywhere are primarily finance and accounting, including accounts receivable, payable, reconciliation, and invoice processing. They also use it for supply chain and HR processes, IT, and contact center functions, among others.

Four or five years back, clients were looking to gain more accuracy and efficiency. Later on, they became more informed and educated about RPA technologies, and in the past couple of years, they have wanted one-stop solutions. They do not want multiple technologies or to deal with multiple vendors. They want a vendor or an OEM that can provide multiple technologies. That means not only RPA but something to handle integration document processing. They also want analytics and contact center solutions. 

It started with a technology through which a customer would gain efficiency and accuracy. Later on, the paradigm shifted and they wanted to deal with vendors who could provide all sorts of solutions to them.

The number-one feature is that Automation Anywhere can interact or integrate with all sorts of business applications.

The next most important feature is the cloud. That has been a game-changer. Currently, everyone wants to experiment more and more with cloud offerings. They don't want to spend money on setting up their internal hardware infrastructure. Automation Anywhere is the only tool that provides a pure cloud to customers. That is one of the key features. In the past couple of years, 70 to 80 percent of the deals I have closed have been for the cloud.

It's also very easy to use for non-technical business users.

Automation co-pilot integrates pretty seamlessly with day-to-day applications. The Automation Anywhere folks have added some advancements to that technology. I'm currently working on a couple of deals and we are using it as a solid unique selling proposition against other tools. For large organizations such as contact centers, automation co-pilot is going to fly for sure. It has already helped organizations increase productivity in the range of 30 to 40 percent, as a bare minimum.

Automation co-pilot has definitely helped to free up staff to work on other projects. That's one of the focus areas: Let computers do what they are supposed to do and what they are good at doing so that employees, associates, and analysts can focus on the things that they are good at doing.

In addition, the integration of RPA bots, APIs, business applications and documents in Automation Anywhere is seamless; it's very smooth.

They are already working on this: The boom of generative AI, the next-gen technologies, including advanced AI and ML technologies, are in the roadmap. I would like to see more and more AI integration and a bit more analytics. That would be great.

I have been working with Automation Anywhere for about six years. I am a reseller of the solution now, but prior to that, I was with Automation Anywhere.

The stability is a 10 out of 10.

It is definitely a very good technology. Automation Anywhere is a fantastic tool. But you need to have the right skill sets or the right partners to scale the journey. It's like having a Rolls Royce or a Mercedes. If you know how to drive it, of course, it is very easy to use it, but having an expert partner is crucial.

In terms of providing automation at scale, back in 2018 or 2019, the top five or top 10 customers of Automation Anywhere had more than 3,000 to 4,000 bots running in production. I don't think any other OEM had that sort of success story. Scaling up the journey with Automation Anywhere is pretty robust and a tested and proven technology.

Our customers deploy it in multiple locations and multiple departments. There are all sorts of models. I would rate its scalability at nine out of 10.

Their technical support is good.

Positive

I have worked on UiPath, Blue Prism, and a couple of projects on Power Automate as well. The number-one advantage of Automation Anywhere is ease of use. Number two is the success stories. Number three is that it is a mature overall ecosystem.

Deploying it is very straightforward, although I am not too involved in the nitty-gritty of implementation. My job is to prospect customers and work with them until the deal has closed. After that, I let my delivery team handle it.

We have a maximum of two people involved in deploying it. There is not much maintenance involved.

For technical employees, it takes about six weeks, and not more than that, to be trained to use Automation Anywhere. For a person without a tech background, it takes a couple of months, max. The learning curve is pretty steep for Automation Anywhere.

I have dealt with all sorts of customers, from small and medium-scale enterprises to large conglomerates. Across all of them, one commonality is that after the first year, they have all doubled their license count. 

They get a return on their investment very quickly, probably within six months the majority of customers get their ROI. After that, it is just a mushrooming effect. 

It is not only about cost savings. This technology impacts the top line as well as the bottom line of a company's P&L and balance sheets. Once they also realize its value, they come up with more asks and we scale up the journey.

Initially, they charged a premium, but now the rest of the vendors have increased their overall pricing and Automation Anywhere is not that high at this time. It's pretty viable.

I work in APAC, India and Asia Pacific countries, and customers here are very price-conscious. Every time I get a chance to work with Automation Anywhere, I tell them that I want a starter pack at a relatively low cost so that the customer can get started. But for customers based in Europe, The Middle East, or North America, Automation Anywhere is pretty competitive.

A couple of hours ago, I had a meeting with the group CEO of a multi-national corporation and he asked why he should use RPA when he can do automation using APIs and Python. That can definitely be done. If a customer has only a couple of processes to automate, I'll be the first person to tell them they don't have to invest in RPA. They can use scripting technology or API integration. But when we talk about scale, API automation with Python or any other type of scripting automation will not be the right choice. The reason is that it consumes a lot of time and is not that agile. That approach also becomes "person-dependent", meaning you have to keep the guy who developed that script around. If he is gone, your automation journey goes for a toss. When a customer wants to scale, they need a mature, solid, RPA platform such as Automation Anywhere.

There are many use cases for Automation Anywhere. One of these involved reconciling numerous financial reports in the company I work for, which deals in consumer products and goods. Specifically, we handle credit notes and debit notes from various customers. These notes serve as certifications of transactions, indicating whether we owe something to the customers or they owe something to us. The challenge is that these notes come in different formats, all in PDFs. Consequently, someone has to manually go through each of them, input the data into Excel, and compare it with an existing Excel report. After verifying the information and ensuring it matches, we input the data into the SAP system. This process is a part of our monthly activities and involves a considerable volume of documents, given that we are a multinational company focusing on AMEA markets. 

To streamline this process, we utilized Automation Anywhere, making use of OCR technology to extract data from the PDFs. Another use case for the automation tool involved generating aging reports. As a company, we deal with numerous customers who haven't made payments yet, and we need to monitor the time they have left to pay or identify if they have exceeded the due dates. This information is available on our SAP system and needs to be created daily and distributed to all our sales teams.

If someone without technical skills wants to learn to use Automation Anywhere, it's not very difficult. However, if we simply want to use the solution without any prior experience, it may not be possible, but with proper training, someone can learn it in a month.

The learning curve is relatively easy, and it just takes time. Getting comfortable with the tool is, in my opinion, quite feasible; it can be done. The other aspect of the problem is understanding the use case and how to design it. How will we design our system? How will we design our process? Because it's never just one process that someone wants to automate; it's usually a bundle of processes. When we obtain a bot from automation anywhere, we cannot get just a fraction of a bot. We have to get a full bot. And if we have a process that does not consume all of that, then our cost-benefit ratio doesn't work. So we need to have a bunch of processes and then figure out how to schedule each bot, and how to process it. There are multiple ways of designing the flow of a bot. We should look for the optimum way considering the context, it depends on our context. The templates keep changing, and the sales keep changing, so we would have to define it in a different way where we have templates that can be replaceable. But if we are dealing with something related to compliance, then we would prioritize reliability and robustness, and we may have to compromise on flexibility while designing a solution with robustness in mind. 

All of that comes with expertise, and all of that comes with experience. However, just understanding the product and the tool to a good, fairly okay level where a business user can create a small automation and do something with it even if they don't fully maximize its value can be achieved in a couple of months. But becoming a true expert and being able to call ourselves an RPA expert will take a lot of time and further exposure to various use cases.

By using Automation Anywhere, we observed a reduction in paperwork costs and the implementation of a reliable bot. When we require manual report generation, workflow execution, and other tasks. Its efficiency is contingent upon the availability of the person overseeing the process. With Automation Anywhere, the reporting, workflow executions, and other tasks are automated and thereby enhancing overall reliability. Additionally, a notable advantage is the development of a digital mindset within the company. Exposure to automation fosters a digital way of thinking among employees, leading them to identify opportunities that can be automated. These benefits are just a few among several others, including financial gains and improved compliance.

The benefits are seen typically after three to four months per process, depending on its complexity. For processes of low to medium complexity, it usually takes about three to four months for the board to start functioning correctly. The payback ratio varies depending on the number of products or processes we have and their complexity. If we have many low-complexity processes that can be completed within six months, we will see returns on our investment within that time frame. However, it's important to note that the payback period ultimately depends on the complexity of the process. I have observed instances where processes have not yielded returns even after several months, as changes were required at three or six-month intervals, leading to additional expenses. So, the success of the process is contingent on its specific characteristics.

Automation Anywhere is able to provide automation at scale.

Integration is truly beneficial; it serves as a significant advantage of Automation Anywhere. The level of integration is highly commendable.

Automation Anywhere has helped our organization increase its automation consumption by around 50 percent.

The way templates can be configured is quite simple - it's a matter of drag and drop. Within the console, which is easy to navigate if we've seen it before, we can understand how things work. This allows business folks to join calls if needed, and I comprehend what happens within the console. 

The Board Control room is a centralized place where we can monitor all our bots and see how they are running when they are scheduled to run, and how our CPU and CB usage are looking - basically, the entire orchestration. 

I noticed that they opened up to other service providers like Accenture and Avaya, which is not a platform feature, but it was very helpful for us. Automation Anywhere, being a product company, might not excel in service, so partnering with companies like Avaya or Accenture provided us with a reliable service operation. 

The capability of understanding and extracting documents is not very good. Therefore, automating unstructured documents or any structured documents that we want to automate on Automation Anywhere is not a good idea.

The UI is not intuitive and doesn't come across as smooth.

I would like the licenses to be transferable. Currently, we are unable to transfer a user license.

I have been using Automation Anywhere for three and a half years.

I give the stability of Automation Anywhere a six out of ten.

I give the scalability of Automation Anywhere an eight out of ten.

We saw a return on investment with 50 percent of our automation processes. 

I give Automation Anywhere a six out of ten.

It depends on the specific capabilities you require. When we started out as a team at Mondelez we were setting up all the necessary components. At that time, we were primarily focused on basic capabilities such as having a good service partner, efficient bot operations, and a manageable console. Figuring out the licenses was crucial, as some companies were unwilling to share their licenses with others. So, if you had the license, you were the one responsible for using it, and it couldn't be transferred to someone else. Certain software had this complexity, and we were also not considering advanced features like OCR back then. 

Our focus was on basic RPA without many complexities. About four years ago, we believed Automation Anywhere was a well-established player in the market, so we chose them. However, later on, we realized that automation had much more to offer than simply configuring and automating certain processes. We discovered the concept of hyper-automation, which includes low-code and no-code applications that business users can build themselves. Document-related automation became crucial, and we found that Automation Anywhere lacked proper support for structured documentation and didn't leverage artificial intelligence or natural language processing effectively. Consequently, we had to explore other software options. As time progressed, we recognized the need for more capabilities. Therefore, we adopted two approaches to address this. Firstly, we sought a solution that offered modular usability. Consequently, we included Power Platform and are currently exploring the UI part. Additionally, we ventured into using newer technologies like Blue Prism, experimenting with various possibilities. Ultimately, our aim is to stay on top of advancements and adopt the best-suited tools for our needs.

The preference for API integration over a robust process automation solution depends on the capabilities of our in-house tech team. If we have an in-house tech team, then API solutions are significantly better than an automated bot. Additionally, our cost-benefit analysis, in terms of tech capabilities, also plays a crucial role in the decision-making process.

We did not perform any maintenance on Automation Anywhere.