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.
Agentic Process Automation System (Now Certified for WorkSpaces)
Automation Anywhere, Inc.External reviews
External reviews are not included in the AWS star rating for the product.
Automation Anywhere product great for setting up workflow with bots that automate tasks
Automation Anywhere is the ideal tool for process automation and information extraction
Powerful RPA so that all processes are easily automated
Automation Anywhere handles all PDFs and its pretty decent and works well
Integration with core banking systems is very good, as is OCR
What is our primary use case?
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Automation Anywhere for four years.
What do I think about the stability of the solution?
It's a very good platform in terms of stability.
What do I think about the scalability of the solution?
Automation Anywhere has very good scalability when you want to scale an existing bot.
How are customer service and support?
It is very easy to contact them and receive support from them.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We were working with a local system.
How was the initial setup?
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.
What about the implementation team?
My team did the setup.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Very Easy To Use Automation Too With Accuracy Issues.
Easy to use RPA platform with good features and good user interface
Automation Anywhere Process discovery helps in scaling and improving the process steps
Monitors all our bots from a centralized place and is easy to configure templates, but the UI is not intuitive
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Automation Anywhere for three and a half years.
What do I think about the stability of the solution?
I give the stability of Automation Anywhere a six out of ten.
What do I think about the scalability of the solution?
I give the scalability of Automation Anywhere an eight out of ten.
What was our ROI?
We saw a return on investment with 50 percent of our automation processes.
What other advice do I have?
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.
Improved process performance for us with fewer employees, saving us hours of time
What is our primary use case?
We were looking to replace employees with a robot for repetitive and tedious tasks, to save time.
How has it helped my organization?
Automation Anywhere is saving hours and hours of employees' time. We can do the same tasks with fewer employees.
We have increased the automation of processes in our organization. It is really obvious how automation has improved the performance of our processes. We have two tracks of automation. We do traditional automation using application management and integration, and that is done by a big team. But we can compare our small RPA automation team to that big team. Both are increasing automation in our organization, each accounting for about 50 percent of our automation.
There is definitely another business benefit from using it: Processes have been re-engineered after being reviewed.
What is most valuable?
There are ready plugins and connectors to integrate with APIs for common systems like Oracle or Microsoft.
What needs improvement?
There could be improvement in the reporting and insights into the ROI. The ROI tool that shows the performance and the return on investment is not very accurate. I have developed my own tool to do that instead of using the native tool that comes with Automation Anywhere.
For how long have I used the solution?
I have been using Automation Anywhere for four years.
What do I think about the stability of the solution?
It is a stable product.
What do I think about the scalability of the solution?
The system can be expanded easily if you scale up the team or the process itself. It's the perfect product for that. It's definitely scalable.
Which solution did I use previously and why did I switch?
We didn't have a previous solution.
How was the initial setup?
There were some difficulties regarding the connection of the servers and performance issues, but we overcame them by reading about the product and seeing how things can be done. We also opened tickets with Automation Anywhere but it took them a long time to respond. There was a ticket that never closed during six months. But with an upgrade to the new release, it disappeared automatically.
Automation Anywhere has a learning curve, but it's not that hard and it's not very easy. Someone without tech skills can learn it by taking courses. When you try, you get into some problems, but in the end, it's nice and not hard. I haven't tried training non-tech people to use it, but in general, it may take people without a tech background about three months to learn it.
From time to time we need to do some maintenance of the infrastructure servers and make sure that the CPU and memory utilization is optimized. Occasionally, we need to increase the memory. There are two or three people involved in the maintenance from our organization's application support team.
What's my experience with pricing, setup cost, and licensing?
The solution is quite expensive. Not every organization can consider this option. That's one reason they might go with real integration via API.
There are additional support costs. We didn't buy the support because we have a capable team that is doing the job.
Which other solutions did I evaluate?
We have seen options from the competitors, and we decide to go with this one. There were many aspects to our decision, but the main ones were the cost of the solution and the support available in our country.
What other advice do I have?
I would recommend Automation Anywhere as a serious option. You will find it easy to use, overall, making it a very good choice.
When it comes to deciding between an API integration and RPA, integration is the best option, not automation. If API integration is available and ready to use, it's better to go with that option. However, sometimes, based on my experience, there are cases where you don't have control of those things and you have to think of other solutions. For us, the alternative was automation using RPA. But when an API integration is possible, I prefer to go with that option, rather than going with the RPA. When that is not possible or easy to do, we go with RPA.