Automation Anywhere Reviews

We work with partners to implement the application on several customer sites, typically banking, financial security, and insurance. We work as a service provider. It's used, for example, in the banking sector to handle processes and tasks. It helps automate. 

We've implemented more than 3,000 business processes for customers. 

It helps improve performance and helps companies save time and money. Customers have been very happy with the experience so far. We've saved about 10% to 15% of time and costs. One robot can help replace a portion of the workforce. 

The security on offer is very good. 

AI has big potential right now. We're trying to support organizations that want to integrate it. We're trying to increase AI capabilities.

It's a pretty easy solution to use for business users that are not technical. They can learn the tool very fast. In maybe six weeks, even with no previous experience, they can go to the market to implement the service for the client. After a while, they can become very proficient in using it. 

It's easy to integrate with other applications. We can integrate automation into workflow APIs, business applications, et cetera. 

The product has helped increase productivity. 

There could be more training provided by Automation Anywhere. 

We've faced some economic problems based on the exchange rate. 

A major impediment to using CoPilot is that many of our users cannot access the cloud. They need to work with the on-premises version. 

I've used the solution for five years, since 2019.

The solution is stable. 

The solution has been scalable. 

Technical support is good. 

I'm also familiar with UiPath and IBM RPA.

How easy or difficult the setup is depends on the customer's level of knowledge. Most of our clients are in banking and require on-premises deployments. Even government entities cannot use the cloud. We are comfortable with deployments and find the process to be straightforward.  Sometimes it is difficult to upgrade from older versions. 

We have five people out of a team of 13 that can handle any maintenance. Maybe 20% of our team would be involved in maintenance. 

The pricing of the solution is flexible. 

We did compare Automation Anywhere with UiPath. Automation Anywhere could offer more marketing and training. 

I'm aware of the CoPilot feature. However, we do not have clients using it. We're trying to introduce the tool to the market and to the customer. However, it has the potential to be a good application. 

I'd rate the solution ten out of ten.

As our business is a mortgage company that provides loans to borrowers, we use Automation Anywhere to automate business processes to help the end users process loans faster. 

The application's response time is slow when using your desktop and trying to process an application. However, when you apply automation, it can work overnight. You don't need to sit at a desk and watch what's happening. It's all automated. 

Prior to implementation, everything was manual. You couldn't inject other software, like APIs. However, with AA, you can bring in any number of tools that connect right into Automation Anywhere. This makes everything move faster. You save a lot of time and cost involved in processing the applications.

The recent update that included code analysis was very helpful. Previously, we had to go line by line. Now, inside the tool, it shows you which lines are hard-coded. 

We've saved a lot of time. How much time we save depends on the process. It's likely at least 50%. Sometimes, it's up to 70%.

We've saved on costs by about 30%.

It's reduced human error. Using Automation Anywhere, we can eliminate a lot of human error by adding exceptions and identifying what's going on quite easily.

For users who don't have technical skills, it's not that complicated. It defines what every command does. It may take a few months to understand the process; however, going through the documentation and using the community versions and forums will make it easier to learn. You can find answers to any aspect you want to understand. 

We did a POC with the automation copilot. It met some of our expectations. For some of the use cases, it will help in the future. 

The copilot's ability to integrate with our day-to-day is fine. It helps employees working with it. It helps them to make things faster. You just have to provide some information, and the background bots will run. It might help increase productivity in the future if we implement it at the enterprise level. Outside of the POC, it looks like it might help with productivity. 

The solution integrates well with other applications and third-party tools. 

There are great tools inside Automation Anywhere. 

With the automation copilot, if I have any internal tool or application and I want to pass on variables, I don't have it. Maybe the team can work on it to make it more efficient to make it work better across all automations.

I've been using the solution for four or more years. I started with version 10.x.

In the past two to three months, the support has gotten far better. Previously, we didn't have a live agent or live support, and now we do. It's great to have. They can respond immediately, and you can continue with what you are doing. You don't have to wait for support at all. 

Positive

We did not previously use a different solution. 

I was involved in the initial deployment. It took a couple of months.

It's relatively easy to upgrade. It depends on the organization. You need to add more variables and define the standards. However, it's not too complex. 

There is some maintenance needed. When you upgrade versions, devices may be disconnected. Sometimes you need to go and check if the device deployment is happening or not, or a deployment may fail. We have about two people handling the maintenance of the solution. You simply need to ensure the bots are deploying on the right schedules and check errors or disconnects. In some cases, you may need to redeploy the bot. The time spent maintaining bots maybe three to four hours per day per person. 

We also explored Microsoft's Power Automate. However, it wasn't as mature or up to an enterprise level at the time. Automation Anywhere had good standards and excellent support, in terms of architecture, design, and user interface, we chose Automation Anywhere. It also has good community support. Previously, we used to raise a ticket. Now, it's amazing - when you ask a question, people respond to it live. 

I'd rate the solution ten out of ten. 

Our journey started with a migration initiative with something that already existed in an RPA solution. Then we started expanding and we started going into finance and HR activities. We use it in different entities and have been working with Automation Anywhere to build automation. We're seeing a lot of very good use cases that help deliver very good ROI. 

Our company is quite large. We have several hundred applications and systems, including legacy systems. As part of a recent merger, part of our work is consolidating these systems. There are a lot of challenges. Someone has to manually perform activities, for example, to be an integrator between two systems. We use Automation Anywhere to bridge the gap. Wherever we can find and remove the human from repetitive tasks, we use Automation Anywhere. 

This is a cloud solution. The framework we had before was on-premises. We wanted to move to the cloud, and that was a huge change. We're also able to redesign and refine processes that may have already been in place.

During our migration initiative, we were able to talk to different customer groups and revisit aspects to make things better and do things that may be needed. We were able to effectively optimize the processes and redo what was already in the existing platforms.

There is a lot of interest in operationalizing AI. There's a lot of buzz around generative AI. We've been reviewing different AI services. However, our focus has been more on orchestrating an entire end-to-end process, not just the AI. When we're talking with all the groups, we try to identify which steps can be automated, and add AI into the mix, if it is needed and it makes sense. We've had a lot of opportunities to work within legal, corporate, finance, HR, et cetera, and we're working to bring more use cases into production. Right now, it's all in proof of concept. 

The leadership is very invested in generative AI and doing a lot of research. There's a separate team that does InfoSec reviews. We're undergoing a stringent vetting process. We're in the analysis phase to ensure the data stays within the model and doesn't go outside the LLM for training. 

We are finding opportunities to implement some hyper-automation options. 

Automation Anywhere and even previous versions, which I've worked on, have good core functionality. The core functionality of being able to automate and build a solution that is local and low code is one of the key differentiators that's allowed us to find success. 

It's easy for business users who don't have technical skills. We try to build and help users build automation quicker. We've built a framework around it that's made it easier for everyone to build automation. 

The learner curve for users is okay. The curves are different for end users. We have a large footprint of citizen developers, and some take quicker or longer depending on prior project commitments. It depends on the amount of time they can commit to it.

We've used the automation copilot, which is quite useful.

We have a lot of internal tools. A lot of finance and HR, for example, have specific apps and platforms. We've established a lot of connectivity with other apps. If there's an interest that business users want to start building, we already have the framework in place, which makes integrations fast.

We get a seamless experience when using the packages. There are constant upgrades. It doesn't stay stagnant; there are new features added to it. The consistent growth of the packages has remained seamless.

We save time and money. I can't share exact details, however, we do have good ROI. We track time, compliance, cost avoidance, et cetera. Everything is heavily tracked, and we make it available for leadership to review. 

The improvements have already been rolled into recent releases, like better governance models. From a GenAI perspective, there are good releases like automation pilot and copilot that are already part of the product's release agenda. 

They need to improve the stability of the core functionality. If they keep the core constant and constant, they will continue to thrive. It needs to stay consistent. 

I have a long history with the solution. With my current company, we've been using it since 2021. However, in my previous roles, I've worked with it as well. 

The platform is highly scalable. That's one of the key advantages. We build at first on a smaller scale, and build it up over time. The scaling part has been really seamless. It's been good so far. 

We've had a great experience with technical support. They've partnered with us in terms of the challenges we face. We have a collaborative relationship and have had a positive experience. 

As the product evolves, it would be great to have more support and have them up to date on the latest and greatest. The teams should be constantly upgraded to ensure that if something goes wrong, they can handle anything - that will be important for the future.

Positive

We do use other tools that are low code/no code, such as ServiceNow, SalesForce, et cetera.

Everyone tries to improve their opportunities. This competitiveness has helped the product evolve. 

We've deployed processes within a week, while others might take four or six weeks, depending on the complexity. We have release schedules and release controls in place. Everything is streamlined, and we test before the automation goes live. 

We're on the cloud, so we do not have to upgrade anything. 

Maintenance is more on the partner-owner and device side. There might also be work upgrading and testing packages and new features. We do spend some time when a new feature comes out to test it before we actually upgrade our packages.

The licensing isn't an area I can discuss in great detail. 

I'd rate the product eight out of ten. They have been an industry-leading automation solution provider. They have a lot of experience, and the core functionality is great. Keeping up with the market and putting in new competence into the product - the constant innovation - makes the product impressive. 

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

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

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

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

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

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

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

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

They should consider being more multi-platform.

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

I've never used technical support.

I've also used Blue Prism in the past.

My understanding is that the initial setup is pretty straightforward.

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

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

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

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

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

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

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

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

The most valuable feature is the Control Room.

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

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

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

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

I have been using Automation Anywhere for two years.

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

It is not very scalable for complex use cases.

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

Neutral

We did not have a previous solution.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Positive

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

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

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

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

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

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

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

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

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

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

I would rate Automation Anywhere a seven out of ten.

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

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

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

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

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

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

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

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

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

I can rely on it. 

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

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

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

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

Positive

I did not use any other solution previously.

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

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

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

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

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

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

Our company uses the solution for automations. 

As a portfolio manager, the key responsibility is to determine how to use our latest technologies for use cases. We identify use cases in various functions and buy software licenses for them. 

Once we buy licenses, we use the solution for end-to-end discovery of use cases, onboarding in-house technical staff for ongoing management, and collaborations for training or licenses. 

Our licenses are used by our technical team within our Center of Excellence. The team handles the end-to-end work that includes development, testing, quality assurance, and production. We are using the solution to its full capacity. Bots are at an optimum because we want to extract maximum value from our licenses. 

We plan to increase usage once we finish migrating from on-premises to the cloud. 

The solution has helped us embrace more of a digital transformation footprint, bring in efficiencies, and create an internal infrastructure.  

The solution's architecture is very nice. The three components are a bot, a control room, and a bot developer. 

The control room is quite a good feature. It is easy to use and gives you the power to manage your digital workforce. It gives you a sense of understanding in terms of how the audit trail happens. 

The solution should include an analytics dashboard. As the space is maturing, many vendors sell functionalities as separate components so this is not unique to the solution. If I am buying a license, I should at least get a flavor of my analytics with a dashboard related to operational KPIs. Right now, if you want detailed analytics, you need to buy the dashboard separately. This licensing structure adds to the overall cost. 

The solution should include bot insights instead of selling it as a separate license. From the bot and business perspectives, insights are important for operational agility metrics and managing KPIs. For example, I want to how many hours in a day or month a bot runs for human resources when it performs A, B, C, D, and E and gives benefits across D, E, and F. 

I have been using the solution for three years. 

The solution is stable so I rate stability an eight out of ten. 

The solution is somewhat scalable so I rate scalability a six out of ten. 

We get the right support when we ask for it. Sometimes though, service requests are not handled within the timeframe we expect. Issues move in circles until they are placed with the proper technician. 

There is definitely an opportunity to lessen the response time so I rate support a seven out of ten. 

Neutral

I have prior experience with UiPath to a certain extent. 

The setup takes a good amount of time because you have to develop an infrastructure that includes servers and compliance. A lot of time is spent framing those requirements and signing contracts that are quite detailed. 

I rate the setup a five out of ten because it is not that easy.

We worked with technicians from the solution to implement.

There are some difficulties in migrating to a new platform. There are a lot of internal governance forms or approvals that can delay the process. Lots of things need to be reworked as you go through the process. 

For about four to six months, you can take on the fixed paper side to get all the needed approvals. In some cases, the process might even take eight months because everything takes time and other business activities may take priority. Separate contracts need to be created for automations and they are usually handled by another team. Many approvals are needed at all levels of the organization. 

We currently use the solution on-premises but are migrating to the cloud. This process is also not that smooth and requires nudging. We are going back to the drawing board to take another look at things and rework if needed. Most components should be scalable and reusable but we are having a few issues on that front. 

Ongoing maintenance includes our internal team working with two or three of the solution's technicians to resolve issues. The solution's team routes or allocates the right technician to handle our service request. Our internal team supports and helps their technicians to understand our unique scenario. 

The solution is definitely worth the money. It is up to you to add quality use cases and utilize the digital workforce along with the human workforce. The tools are there, but the actual metrics derived are your baby. There are many benefits to automation solutions. 

I won't give 100% credit to the solution. Perhaps UiPath would have given us the same results. The way you use a solution makes all the difference in ROI. 

Similar to how competing products are priced, the solution has separate licenses for features that should be included in a bundle package. For example, the analytics dashboard and bot insights are sold as separate licenses. 

No one wants to buy a product that is too complex because components are sold separately. Give longstanding customers these benefits as icing on the cake. 

The solution is not the least or most expensive. Pricing is good and in the middle so I rate pricing a five out of ten. 

The options were evaluated before I joined the team, but I believe the company also looked at UiPath, Info Sales, and XCL. 

No tool, product, or technology is 100% foolproof. Each has its own set of pros and cons, including the solution. 

The common sales approach across the solution and other vendors is misleading. They make it look like a utopia where you will increase productivity by 200% in six weeks. This is not possible because organizations can't do magic in six weeks. Some of the claims being made by developers or content providers are creating a false impression in terms of senior management. There is no magic wand. There has to be automation. It looks and sounds simple, but implementation is not that easy. Your program, team, and communications management need to move in tandem to give you the inputs or outputs for sensitivities around people, roles, responsibilities, and training. 

It is important to be realistic when launching a new product or partnering with a player in the market. Be open and honest with customers. Don't make things too glamorous because it will be difficult to achieve that expectation. Stop overselling it and just be natural. A lot of consolidation is happening in the space and customers are aware because they read Forrester and Gartner. You can't fool customers so be honest and let them know that the solution needs to be managed by human beings. 

The biggest lesson is to understand the functionalities you need before you buy the solution. Determine if the solution passes the litmus test. Be cautious about overselling it and instead set the right expectations. 

Ask upfront if some additional features can be bundled because that will really help with your automation journey. 

I rate the solution a seven out of ten. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The approval process needs improvement.

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

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

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

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

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

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

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

I would rate it an eight out of ten.