Automation Anywhere Reviews

The tool is used to automate any business process. Some examples are:

• If you want to download some data from a website or push some data onto a website.
• If you work with an Excel application and want to automate it, or any Windows-based application, you can automate it as long as you know what the business process is.
• If a person is doing a day-to-day activity and you want to automate that activity, you can use the Automation Anywhere tool to do it.

I have worked with the Windows, Excel, and web applications, along with some SAP automation and how to automate that SAP data. I use Automation Anywhere to determine automation for how to:

• Distribute the process. 
• Schedule the process. 
• Run the process. 
• Design the process.
• Distribute the data for 1000 to 10,000 data points (in Excel).

I have automated the invoicing in a finance department, where the finance department wanted to automate the invoicing process. They wanted to do the following:

• Invoice the data.
• Create the invoice.
• Mail the invoice.
• Download the invoice data.

If you have 10 operators currently performing these activities everyday, then you automate the process, by removing the 10 operators and having only one operator required, this will decrease costs. It will also increase the efficiency of your company.

In the automatic invoicing system, we created a file which pushes onto a shared folder. The bot will pick up the file automatically from the shared folder and process the invoice. Therefore, if tomorrow, another bot were to be created, we could just create a file and copy it to the shared folder, then it would pick up the file and process the invoice.

I utilize all the commands provided by Automation Anywhere, such as all the recorders. I use these commands to develop my processes and bots.

Automation Anywhere has a drag and drop process.

Automation Anywhere needs to improve Excel and its commands. In Excel, if you want to add a sheet, you cannot add a sheet. There is no command for adding a sheet. Also, if you want to rename something in Excel, you cannot rename it. You always must keep a list that you can rename through your keyboard, but there is no specific command in Automation Anywhere. 

The email automation command also needs to be improved. The email automation command sometimes is not working properly. When you connect the mail server, it is not being done properly.

The OCR feature is not that reliable.

With the PDF command, you can only read structured data. If your data is in an unstructured format, there is no command for it in Automation Anywhere. Then, people need to use Python coding if their data is in unstructured format. Therefore, Automation Anywhere needs to improve in the PDF area.

I have been using the product for the last two years.

I didn't have any stability issues. 

I haven't found any scalability issues with it. If the volume increases tomorrow, another bot can be added from the Control Room.

I worked with a single deployment model, which didn't have a load balancer requirement. Higher availability deployments require load balancers.

I haven't dealt with Automation Anywhere's technical support.

For the implementation, you just follow the proper process on how to deploy the proper hardware configuration on the production environment. The process does not take that much time as you push files to the Control Room, then from the Control Room, you can download the client. It does depend on how many bots you are implementing and how you are scheduling them.

Automation Anywhere is deployed from a deployment guideline in a step-by-step process. Automation Anywhere provides some deployment guidelines, which can be referred to.

Only one person is required for deployment: the Control Room administrator.

The number of people required for monitoring the solution depends on the amount of bots deployed.

It saves time and money. If a bot does the same work as nine out of 10 people, then you are saving money through wages. Also, a bot will work all hours without interruption, whereas FTEs may need time off or vacation. 

I believe it is $10,000 for Bot Creator. 

The Automation Anywhere automation tool is user-friendly, especially compared to UiPath and Blue Prism. Automation Anywhere's deployment is also easy compared to other RPA tools.

The solution is good for people who want to do their job quickly without any delay or problems. 

The future of IT will require every organization to need automation.

The Control Room is good in version 11, as compared to the previous versions of the Control Room.

We are an IT services firm. We use it for simple processes, but also for complex. We usually take up simple processes for manual tasks, which are easy to automate.

We have mostly done financial services: finance and accounting processes. That has been for the most part. We have also used it in HR and recruitment to find resumes online, and in other processes.

Its ease of deployment is the most valuable feature. We have found with many customers that it's quite easy to deploy. The other valuable feature, which is not from a technology perspective, is how Automation Anywhere collaborates with us. So, it has made our journey much easier than with other partners that we have.

Room for improvement is more on the IQ Bot side: How quickly we can adopt and deploy it? 

Another area which I feel would help is how the business can adopt it:

• Is it easier for the business to make changes to the tool once it's deployed? 
• How can the business take up roles in the man-machine continuum? 
• How can the business and machine work together, and how does the role change for the business stakeholder. 

It's more on the change management side, but includes all of the tool enabler.

It has been quite good in terms of making changes. As we are working on the process, it's much easier to make changes.

In terms of scaling up, we have not had issues with bots which are in production. In UAT, there have been scaling issues. But in production, as long as a solution is good, then it works.

It was a strategy from our company. We were looking to reduce the cost of operations for our existing clients. We were looking at different ways in which we could reduce our business, in a way, by reducing costs and get more business from the same clients. So this is where we started, by looking at automation as a major thing for Hexaware itself. It starts from our visions, which aligns very well with what Automation Anywhere provides, as a platform. That is where we started, then we have obviously grown and been able to automate many processes, which helped us to get many deals where we are upfront and able to tell clients how much optimization is possible. This is sort of my role, to showcase to the clients how much automation is feasible, in a particular process. We are quite good at that and have been able to do multiple engagements in this space.

We have automated one process, which was running with 109 people. We reduced it down to 69 with automation.

We looked at Blue Prism, UiPath, Automation Anywhere, and World Fusion, and we struggled. Initially, we worked with other firms, but we have seen a great synergy with how Automation Anywhere integrates with our team and how we are getting support from Automation Anywhere. When we are going to a client with Automation Anywhere, it's much easier. That collaboration with their support team, and their advice to us, is extremely good. That's why we end up referring Automation Anywhere.

I would like to use IQ Bot a little bit more and understand more about what is offered, as to what features are there. One of the key challenges that we have had, in implementation, is for complex processes, especially where the input is not standardized. So, IQ Bot seems to be a good tool to use there. Hopefully, it will address everything, but mostly on that.

I would rate the product around eight to eight and a half. Mainly, because there is always room for improvement, and we're happy with the tool. There are areas which we need to understand more, as well, like IQ Bot for instance. We did one engagement with IQ Bot, but we need to mature ourselves into how we can utilize it. As the product matures, I'm sure it will be easier for us.

My advice will be to get a partner who is wiling to work with you and is willing to collaborate. This will make your life easier in the automation journey. There will be initial hiccups when you are getting into this journey, and that's just part of any journey. You need to look internally as to how you can improve, and work with a strong team, to deploy the solution.

We use it for financial back-office functions, things like fee information, balance information, and account aggregation information.

It has been able to save us time in our processes from hours to minutes. Something that might have taken anywhere from two to eight hours now takes 20 minutes.

The general features, that we can automate a task that takes hours into minutes, are valuable. But as far as an individual product feature goes, there isn't anything more specific.

Operationally, there's room for improvement, especially in the area of high-availability and deployment.

In high-availability, we have two Control Rooms acting as a cluster so if one fails the other one will take over. But that's not our environment operationally, and the latest information we have is that they identified another product bug.

We have come through a number of issues with them and they've been very good at fixing them, but we've gone through four different patches to get things working, and currently, we're not working in a clustered environment.

We have had it in production since January of 2019, five months ago. We had it in beta for two months before that. We actually onboarded the product in September of 2018. That was when we started with the product but it was all PoC.

We're not really there yet, in terms of scaling, but based on the high-availability issue, right now I'm not too confident. From everything I've heard, though, it seems like people are running hundreds of processes on a Control Room, but we haven't really done enough to know about scalability.

Technical support is the one thing that has been fantastic. Initially, when we had all these issues, we had some issues trying to get to the right people. But since we escalated and got the right people involved, they've been fantastic. They've had people come out to our site. We submit tickets and let them know the error and they see and pretty much turn them around right away. Unfortunately we do have a number of issues, but support has been really great.

We haven't used any other RPA product.

In the initial setup, we had difficulty in our environment. We actually had to have them come onsite for two days to get us deployed, and even then it took another month before we were finally operational. I think our environment was a factor, but we also did find product failures.

We installed it but it was not operational. Everything from the way things were configured to our license not being set up accurately was an issue. So we had configuration setups such that we couldn't process and it took a while to get that figured out. To be honest, one of the issues was that it was around the holidays and the right people weren't available to help us out. It took us a week-and-a-half just to resolve the fact that there was a button that had to be un-clicked.

And we've been continuing to have issues along the way. They had actually settled down quite a bit until we hit this high-availability issue.

In terms of our implementation strategy, we used a development partner, professional services, that had knowledge of Automation Anywhere. This is a brand-new program for us, our first foray into RPA, so we had a professional services partner who took us all the way from business process through implementation. We don't have technical resources here who did the implementation. We totally relied on them, initially.

Our strategy was to have an experienced professional services partner help us get onboarded and develop bots for us as a PoC. Then, after the PoC and we declared complete, we would move them into production. Our longer-term strategy would be to start building some in-house talent that could do some of the bots as well.

The partner we used was independent of Automation Anywhere. They did a really good job in the upfront work, telling us what RPA can provide and about the process for determining if something should be automated or not. 

Where we struggled a bit is when it came to implementing. We implemented what the business did but we didn't implement what was needed from an operational point of view. In other words, what happens when there's an issue? What happens when there's a scenario that the bot can't handle? How will people get notified? Things like that weren't factored in initially. Some of that might have been because it was a pilot, but ultimately the vendor said, "Yeah, we're going to productionize this." But we've had delays in getting our bots into production because that aspect of usability wasn't factored in.

We're in the process of trying to get our last bot into production, and then we'll start trying, in 2019, to develop some more bots. But it has delayed our bot development. We're tracking about two months behind what we expected.

Our biggest lesson learned is that we need to factor in usability right from the beginning, not only that the business does these ten steps, but what happens if those steps fail?

It's too early for a return on investment.

On a yearly basis, our licensing costs are about $80,000. We bought a package and when we tried to get this high-availability to work we bought some extra Bot Runners. I know that if we buy IQ Bot there's an additional cost for that but we haven't gotten there yet.

We evaluated Blue Prism and UiPath. We chose Automation Anywhere - both our technology and business sides, as a partnership - because the business and technology agreed with them. They felt that it was something they could more easily understand with some of their tech-savvy people. They felt they would ultimately be able to use the product, once it got rolled out. Whereas, with some of the other products, they didn't feel they were as easy to adopt.

Make sure that you not only look at what the business needs are, but how the business will use the product when it becomes operational. It's relatively easy to get a bot developed to do what the business wants, as long as they have a good process laid out. But what is more difficult is that when you go into production you have to understand how you can schedule it if it's attended. Our three bots are unattended. You have to understand the scheduling aspect, you have to understand what happens if it's not happy path and there's an issue. Who does it go to? How is it going to get monitored? And you have to understand how your infrastructure is supported. Our infrastructure is kind of complex which is, I think, why we're running into some of the issues we are.

The users of Automation Anywhere in our company are all business users who support our clients in the back-office, whether that's trying to do fee calculations or account calculations. We only have three bots and the number of business users is probably less than 20, in total, who will be using it once we go live. It may be more as we get further along but right now it's less than 20, probably closer to 15.

We're trying to get it out to different departments, so ultimately there could be 50 users, maybe even 100, but that's more long-term. We might get up to 20, but I think that's as far as we'll get this year, unless we start having a lot better success.

Part of our problem is that for maintenance we require at least two people. Deployment is actually pretty straightforward, but we need about two people for that as well. The people involved would be CM, configuration management, our technology architect, our operations infrastructure, and our database team.

As a partner, we've been serving a lot of customers with primary use cases in BFSI, healthcare, and oil and gas. 

We have automated some 30 or 40 processes including ERP, Financials, manual data scraping from various websites, offloading data from Excel into an application, etc. We've done quite a few.

It improves productivity, it improves efficiency. But most of our customers are automating processes which were taking way too long for them to execute. In some of these cases, as a result of what we have done, they are saving more than 40 hours per person, for multiple people. That's been great.

Among the most valuable features that we've been able to utilize are the screen scraping and object cloning. These are two features we have used so far. We are also utilizing the API integrations.

We are excited about the solution's cognitive document processing, IQ Bot. That's an interesting one and we have at least a couple of customers who are looking for those features.

There have been a lot of nuances in the technologies that are missing. Being a tech company, where the technology is moving forward, I'm excited to see what is coming in the near future.

At this point in time, the installation is one of the biggest challenges in terms of being on a particular instance.

Also, we've been working very closely with Automation Anywhere on some of the integrations. There are some workarounds we have had to do, but I think in the newest features of version 11.3 there are things like callback, especially for the API integrations. We are looking forward to that.

There is room for improvement in that it is still on Windows and there is no self-service. Even though the product is easy to use, there are some challenges when we move across different environments; there's a lot of setup needed.

There is room for improvement in the stability of this product.

In terms of scalability, we haven't been in a situation where it has been a challenge for us. We've been able to scale to what we need. Having said that, we haven't deployed thousands of bots yet, but for the bots we have done we've been doing great.

To scale from pilot to the number of bots we're currently using, took us between eight and 12 weeks.

Technical support is pretty good. They are reachable and they've been able to solve the problems.

We work exclusively with Automation Anywhere.

The setup has been okay. We haven't seen many challenges.

We do automation ROI using three dimensions:

• absolute time-savings
• efficiency improvement 
• reduction in manual labor.

In some cases, we see savings on the order of $100,000 and, in the newer processes that we are trying to do, it may be up to $1,000,000.

The cost is anywhere between $10,000 and $100,000.

I invested a lot of time in evaluating the different vendors but because of our relationship with Automation Anywhere, it was a clear winner.

My advice is to go for Automation Anywhere.

In terms of the bot creation process, it depends on what you're trying to do. The simple bots are easy, the complex bots have their challenges. The biggest challenge is when the settings change between environments. That's when we have faced a lot of challenges with things as simple as screen resolution.

I've taken courses at the Automation Anywhere University and they have been pretty good. It's been really impressive.

I would rate Automation Anywhere at about seven out of ten.

We use it for every aspect of our company: Financials, purchasing, HR, etc. 

It has taken a lot of manual Excel manipulation that we have previously did, and removed that work away from people who did that for ten hours a day, five days a week. We now have a robot doing this manual work, allowing us to refocus those our resources into more value-add activities, simplifying our landscape.

The flexibility: If there is anything the tool cannot do, we have the ability to make a MetaBot to achieve that functionality. The overall flexibility of the tool makes it very useful for us in our landscape.

We have integrated it with everything from standard off-the-shelf products, like SAP and Oracle, to custom apps that we built within our landscape. The integration to other applications is very good and easy.

I would like more integration into the entire Microsoft Suite of products, not just Excel. Companies use all of Microsoft products at the same time, and being good at just one Microsoft tool is a limiting factor. Being able to use Microsoft Excel, Access, and Outlook together and have them integrated (as standard) into the tool would be very useful, especially when you go into attended automation.

They keep rolling out more features in selected areas. They should broaden their scope.

We intentionally took a long time to scale up to our current number of bots because we focused on using large processes, instead of small ones. For us to grow to scale, it took us about a year and a half. However, we have been focusing on processes with tens of FTEs per year, instead of about processes that are one to two hours per day.

The technical support is good. Whenever we have issues with the product, the support team gets back to us normally within half a day, or sometimes even sooner, with direct answers of how we can solve our issues. If they don't have documentation for it, they have somebody call us, and we have the issue resolved in a day or two.

We did not have a previous solution.

The initial setup was in-house.

We did the deployment in-house.

Do your homework on your use cases. Knowing which use cases are really good for RPA is crucial in getting the program started. If you don't have your use cases identified, or have your functional processes identified, that want to automate, then it makes the scaling aspects more challenging.

I am RPA professionally certified through Automation Anywhere and have taken multiple classes through the Automation Anywhere University. The courses are good. They are just like any other online training courses, which I have taken through other vendors, like Microsoft or SAP. It is on par with those vendors who have been doing this for a long time.

As long as a person has a semi-technical mindset, the product is very simple to use. Even for the traditional business user, with just a little training, we are able to bring them up to speed on how to use the tool fairly easily. The tool is very good, as far as ease of use.

As long as you have a technical mindset or are able to think in a certain manner, the creation of a bot is very intuitive, especially since the tool is drag and drop. For example, I am able to take any of the commands that I need and put them in the right sequence of orders. This makes it very intuitive to create a bot from start to finish.

We are evaluating the cognitive document processing as something to use in the future, but are not currently using it.

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.

Private Cloud

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.

Public Cloud

Microsoft Azure