Automation Anywhere Reviews

We mainly use Automation Anywhere for pod development, to automate repetitive tasks by replicating them into bots. We conduct tests and POCs with other tools that Automation Anywhere offers. We try to see what's the best fit for our company. Because of the large offering of different tools, we see how we can leverage them and identify if they are the best solution for our teams. Mainly, we use Automation Anywhere for RPA bots for automation.

We wanted a tool that was easy to use and to implement, that we could leverage to then do the applications, and it was quick enough in our trial that we could just take our opportunity, design, and develop the requirements, and then build the solution from there and help the business with tasks that didn't add value to their processes.

We currently are looking at different use cases for AI such as document automation, process automation, product automation, communication, and many others. So we are looking at different platforms, including Automation Anywhere. Now that Automation Anywhere is offering the AI capability we want to see how we can best feed to our company and leverage AI to help us implement processes, and projects faster and automate processes in a way that will help our business.

When it comes to generative AI, the technology is here, and it's open to people to use. We wanna make sure that we leverage fully, to continue being a leader in the market. Generative AI is here to stay. We wanna make sure that we get the best use of it while maintaining quality and transparency, and making sure that we have all the security in place to leverage generative AI.

I did not have a technical background and I was able to build my first bot using Automation Anywhere after just one course. The learning curve is simple. Automation Anywhere has prebuilt blocks so we don't have to code. It is user-friendly and simply a matter of understanding best practices because we can build blocks and create with 50 steps, but we can also create with five steps if we are using best practices. When we start using the solution we look at different ways to approach the same problem and best practices so it gets better. It is a straightforward and user-friendly platform to start our journey with RPA and automation.

We are trying to start using Automation Co-Pilot but we have not fully deployed it yet because we are still trying to create the connectors. We do see the value of Automation Co-Pilot for our business. We want to be able to add humans into the loop and trigger bots. This way businesses can review the processes and even make changes. It is a better interface with fewer clicks and added value for the business user.

We touch every application in our business with Automation Anywhere. We connect to some using APIs and others through the UI depending on the applicability of the solution we are building.

Automation Anywhere is easy to implement and integrate with workflows, APIs, and applications.

We do have savings with Automation Anywhere. When we implement, we look at how much time we are saving the person and how much we can save by reducing the repetitive manual work for a business user. We have a good amount of bots that we have developed that help save the business time.

Even though we haven't used all of their features for some of our use cases, because they look at the end-to-end process, it's very useful for businesses that are starting their journey. They can build an end-to-end solution with Automation Anywhere. In our case, we leverage the automation RPA solution, but we do see other use cases to leverage other tools and applications that they prefer.

My background lies in continuous improvement, and as a black belt, I think we always have the opportunity to improve. Automation Anywhere is always looking for what is next. Even though they may have implemented something today, they are still looking at what can help our clients in the future. That is a great way to have the right offerings for clients and more of an opportunity to build a bigger community on the automation group and leverage that with the lessons learned and the challenges. Automation Anywhere is headed in the right direction but they still have a good way to go.

I have been using Automation Anywhere for one year.

I appreciate the technical support of Automation Anywhere. They are knowledgeable, senior, and jump to help us find the right solution and assess from our business case what would be the best way to approach it.

Positive

I would rate Automation Anywhere eight out of ten. It is a great tool that is easy to implement and they are always looking for what is next.

The time it takes to learn Automation Anywhere depends on what the user wants to do with it. Do they want to be a developer, a business analyst, or help businesses understand processes and identify opportunities? If a person has a good understanding of processes it can take anywhere from a few months to a few years. For a developer, it can take a bit longer.

When we analyze a problem, we consider the most effective solution, which may not always be automation or RPA. We employ other tools when appropriate, but Automation Anywhere is frequently used in our process improvements.

When there is a version change we have to conduct maintenance. It is a fair amount of time but not so much that it would impact the quality of our services.

We have a group of close to ten people who have a relationship with Automation Anywhere and deal with the maintenance.

We have a bot support group for our full portfolio because we have attended and unattended bots. This group supports the bots 24/7.

Our journey started with the migration initiative. We had to migrate some processes from our legacy RPA solutions. Next, we started expanding to finance and HR, including integration with other platforms like ServiceNow and Salesforce. There are multiple teams within Paramount, like CBS News, CBS Studios, and Paramount Plus, so we've worked with them to find opportunities to build automation. We've explored multiple use cases that deliver a solid ROI, with a focus on low-code and now-code solutions. 

We have hundreds of application systems at Paramount, including legacy platforms. The merger required us to consolidate many of these systems, so there were many opportunities to use automation. One challenge we faced was that this process required someone to integrate the systems manually. It involved a lot of repetitive, mundane tasks to bridge those gaps. Automation Anywhere helped us accomplish those tasks. 

The framework that previously existed was an on-prem solution. The transition to the cloud was a huge change. The second change was redesigning and refining existing processes. While we were undergoing migration, we talked to various customer groups and decided to revisit the processes and maybe remove some things that were unnecessary. We optimized processes and took the opportunity to revise what was on the existing legacy platforms.

There's a lot of buzz around generative AI, so we are considering that on an organizational level. At the same time, we are focusing on orchestrating end-to-end processes, not just the AI. We are having conversations with tech and business groups about solving enterprise-wide problems, and we can add AI into the mix when necessary. 

I think there are many opportunities to add AI to existing use cases like legal, corporate, finance, and AI. Hopefully, we will start bringing more AI use cases to production, but we are still in the review and proof of concept stage. Still, the leadership is interested, and they've done a lot of research on AI, and we have a separate InfoSec team that must review everything. The VMware team also must review the technology. All of these AI technologies must undergo a stringent vetting process. I'm not part of that, but we share ideas and try to understand what's happening. Data analysis is a critical part. We must ensure that our data doesn't go outside the model, but we're open to any opportunity to improve our solutions and test out what makes sense. We'll try that and see how the end users respond.

Before switching to the cloud version of Automation Anywhere, I worked with v10 and v10, so I appreciate the core functionality and the fact that it's a low-code solution. That is one of the key elements that differentiates Automation Anywhere from other platforms and one of the reasons we have been able to achieve success. 

It's accessible to business users with few technical skills. We've been able to add on to our current framework and build on our existing library of reusable components, allowing developers to build their automations quicker.

The time needed to learn Automation Anywhere has varied, depending on the user. We've taken on a large number of Cylance and Cisco developers. Some can pick it up quicker, but others take a little longer because of their prior project commitments. It's all over the place. It depends on how much time they can devote to learning the solution.

Many requested improvements are already on Automation Anywhere's roadmap, like a better governance model for AI systems. We also want to see more releases for autopilot/co-pilot from a generative AI perspective. We're expecting Automation Anywhere to release those in future updates, and as long as they maintain consistent improvement in their core functionality, I believe that will lead to success.

We have established connectivity with so many applications, so we build reusable components. We identify an application that business users might want to build, so we have a framework ready by the time they're ready to get onboarded and start developing. Automation Anywhere provides a seamless experience for utilizing those packages. They need to keep adding features so the solution doesn't stagnate. One example is email automation. There need to be multiple options for authentication available. 

Automation Anywhere could add more tools to track the processes and ROI, so we can get a better understanding of the cost savings and compliance. We heavily track those metrics and make them available to the leadership for review. 

I have used the cloud version of Automation Anywhere since 2021, but I worked on the previous versions before that in past roles as a consultant. 

Automation Anywhere is highly scalable. That's one of the most significant advantages. We usually build a process on a smaller scale and then extend the capabilities. The scaling is relatively seamless.

I rate Automation Anywhere support eight out of 10. We've had a great experience with tech support. They've helped us with significant challenges we've faced and worked with us on feature requests and bugs. We've had lots of collaborative discussions.

Positive

Automation Anywhere is easy to deploy. Some processes can be deployed in a week, while the more complex processes may take four to six weeks. We have release controls in place, so everything is streamlined. All the deployment testing is handled before the automations go live. 

Upgrading is simple because we're on the cloud platform. We don't need to upgrade anything. Maintenance takes place on the partner's side because the bot engine is installed and maintained there. We only need to install the latest packages to test the new features when they are released. That takes a little time. 

I rate Automation Anywhere eight out of 10. They have a lot of expertise with ERP solutions, and the core features are keeping pace with the market. Automation Anywhere is incorporating new components like generative AI and planning to release a new governance model, so there is constant innovation and the company is working to make things better for business users and developers. It's a competitive product that's easy to deploy and maintain. 

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.

As a financial institution, a lot of collections activity processing, invoices, and billing related to our collections activities is my primary use case for Automation Anywhere. That's really where I've been focused for these past few weeks. We're expanding into very ground-level things, consolidating reports from multiple systems, doing these basic use cases to start.

The features of Automation Anywhere improve my company by making deployment and maintenance of our automations a smoother process overall. We can make changes much quicker when we need to and it's definitely simpler for other affiliated people in the company to understand, including those who might not be working in the systems daily. It's put together efficiently enough that it's user-friendly for non-professional developers to handle.

The thing I appreciate most about Automation Anywhere is how integrated the aspects of it are. I also worked with another platform in a different company for two years and it wasn't nearly as integrated, and it required a lot of effort and time trying to get everything to communicate together, from version controlling and deployment. The simple act of engaging was more complex. 

Regarding the development environment, I'm really pleased with Automation Anywhere and enjoy using it. One place I find regular struggles is with basic documentation, including details about different commands or applications that are natively in the system. I tend to have to do test development on my own to find answers that should probably be in the documentation. That does slow things down, but once I get the information I need, it's really great to use overall.

To make it a ten, I would suggest more access to basic information, maybe more distributed use of it on the web. I don't find a lot outside of the internal community forum. It doesn't get much attention or use on Stack Overflow or other public community platforms. The responsiveness and amount of community engagement needs improvement. When I post questions, I seldom get answers fast.  When I do, I am usually just directed to the standard documentation, which I have already reviewed and found to be lacking the answers to my questions.

I've been using the solution for two years at my current role, and a total of about four years altogether.

The deployment has been pretty smooth. We haven't had an issue with anything. Mostly, it's getting all of our internal security and things like that locked in so that we can go through.

I don't have any specifics about the pricing. It's not in my area.

We are not using Automation Anywhere AI feature set at the moment. We just took the training courses in the past few weeks and are learning about it, and I'm hoping to get hands-on sessions to get experience using the tools.  Right now, we're looking forward to developing some use cases that we can start engaging.

The biggest challenges for me and my company in the age of AI stem from being a financial institution and credit union, which creates a particularly conservative environment. This takes more evangelism to get adopted, as financial institutions tend to have more regulatory compliance issues that we must be very conscientious of, so we have to proceed slower on that front.

AI governance is definitely getting attention and discussion in my company. Everyone has accepted that it's going to be a huge part of the landscape in the very near future, so it's important to ensure we have everything managed and planned within compliance for protecting private, personal information.

With our department structure, I personally don't utilize the Automation Anywhere COE, or Center of Excellence manager. I believe our managers and business analysts do, but that's not something as a developer I get involved with.

We haven't deployed any document automation in our current processes. We've done extensive exploration and have paid contracts for a certain number of documents, but we haven't had a beneficial, deployable use case yet. We know they're there, but we have easier tasks to tackle first.

Overall, I'd give Automation Anywhere probably an eight on a scale from one to ten.

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.