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. 

Specifically, we use the solution for SAP where we have particular SAP processes that need automation. 

There were multiple processes where implementing a bot allowed us to automate processes and allow it to perform backend tasks. For example, employee onboarding, or creating orders. 

We were able to remove manual tasks and we were able to justify the processes based on the ROI witnessed. 

We see opportunities to operationalize AI. We aren't using it yet, however, in the future, we are looking to it. At this time, we do not have any AI use cases. 

Being able to connect with third-party tools is the best feature.

All RPA tools we are using have the same benefits in terms of automation.

The learning curve is okay. Practicing it is the key thing. Doing it over and over will help a person get comfortable. We do not have a lab environment where we can use and test it. That makes it difficult for users. They need to spend time with it, to play with it, to have a hands-on approach.

It took me two weeks to learn how to do an implementation. Going from the lowest knowledge levels to more of an expert takes a month or two. 

We have a few different tools and operating systems. It works well with other application data or operational items. 

With respect to your use case, it's easy to use and easy to implement. However, sometimes if there are complex requirements, the automation of processes gets a bit more difficult. 

If you come across any process, it can be automated via Automation Anywhere. However, companies need to better justify the ROI before usage - otherwise, they might spend money on things unnecessarily. 

I've been using the solution for around three years. 

It's a stable product. 

The solution can provide automation at scale. 

Technical support is quite responsive. Very rarely do I need to connect with the team, however, if I need to reach out, they are very good in terms of their response. 

Positive

I also use UiPath and SAP IRP. We work with different tools according to requirements. 

The initial setup is easy. It has its own orchestration and you just need to deploy it.

Any maintenance would fall under your organization's contract. 

We have saved us both money and time. 

The pricing is reasonable. The money you spend will be worth it. 

We are an Automation Anywhere customer. 

I would recommend the solution to others, so long as they have some previous knowledge before setting out. 

I'd rate the solution nine out of ten. 

We use Automation Anywhere to automate all back-office manual tasks, including service case management, support cases, and financial reconciliations between multiple spreadsheets and source systems.

We faced challenges because we were running the on-premises version. It was too demanding on our physical system architecture. Last year, we moved to the cloud, which has improved our landscape. It's better now, but it was tough before. Anyone new to Automation Anywhere will find it much better now.

Before we implemented Automation Anywhere, all of our tasks were manual. Automating them has saved us a lot of time and eliminated a lot of risk. As of now, our run rate is around 15,000 manual hours saved per year.

Automation Anywhere helps eliminate our daily manual tasks, allowing our staff to focus on more valuable tasks.

We have integrated AA with Salesforce, our homegrown platform, ServiceNow, and PeopleSoft.

Our workflows, APIs, business applications, and document automation integration with AA are well-integrated and efficient.

AA has helped us save time.

The code automation platform is the most valuable feature.

Recently, Automation Anywhere acquired FortressIQ, a company that specializes in discovery automation. Discovery automation is the process of sitting down with businesses and documenting their processes and all related information. It is a very human-intensive process. Automation Anywhere acquired FortressIQ to do this work, but the two platforms are not yet seamlessly integrated. This is a pain point that we are currently working on.

I hope that Automation Anywhere can improve its capabilities in the areas of sophisticated unstructured data parsing, contextual routing, and long-running process orchestration. These are areas where AI can be especially helpful. For example, AA could use AI to suggest the next best action in a process and to configure everything in one shot. It should also be smart enough to adjust and move on.

The process discovery side needs improvement. Before we can automate, we must document the current process map and create a process design document. This is a time-consuming and painful process. We have to go to the line-of-business people who perform the operations, sometimes multiple times, to get an understanding of the problem. Automation Anywhere is improving in this area, but it's still not perfect. So, we're relying more on other reliable platforms. The platforms they acquired are not yet fully integrated into the core RPA design platform. This is a big gap. If they can close the gap between discovery and bot development, it would eliminate many manual hours of discovery, allowing the automation team, or COA team, to scale faster.

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

At first, we had issues with the stability, but it has significantly improved in the last six months after we migrated to the 360 version.

Automation Anywhere can scale vertically, but not horizontally. This means that it can add more resources to a single machine to handle increased load, but it cannot distribute the workload across multiple machines. This is a limitation for long-running, complex processes that require state maintenance. However, Automation Anywhere has a roadmap item to release a horizontal scaling solution in 2024.

In other words, Automation Anywhere can scale up, but not out. We can add as many small bots as we want to a single machine, but we cannot distribute the workload across multiple machines.

Technical support is decent. We were previously on a lower level of service support but realized we needed better support and were upgraded to top-level service. It's been better since then. We have a dedicated account customer success manager and architect assigned to us, so we can ping them anytime and they'll chase it for us internally.

Positive

The initial deployment was straightforward. It took six months to deploy ten bots.

The pricing of AA is similar to UiPath.

We evaluated UiPath but AA is more resource friendly and has a shorter learning curve.

I would rate Automation Anywhere eight out of ten.

Our organization's approach and strategy will be to accelerate cross-cutting capability across all technology solutions, including automation. We expect vendors like Automation Anywhere to step up their game to compete. If they cannot compete in the United States, they will not be able to compete in the rest of the world and will be left behind.

We tried to get business users to build bots. We have reports of business users who have built bots. It is easy to get them started, but it is very difficult to get them to build production-quality bots. I am sure that this is a common challenge with any tool or platform. All the solution developers and concepts are theoretical. In reality, they do not work. Business users can build whatever they want, but their bots will not withstand the production infrastructure. Therefore, we need to step in and do the job properly. I do not believe in the concept of business users building bots. It just creates more problems down the line.

The learning curve is around two weeks.

We are starting a POC for Co-Pilot which was formally ARI. At the time when it was ARI, it was not a good feature.

Runners in our local landscape require maintenance.

The use cases I use Automation Anywhere for are for healthcare and revenue.

From the customer's perspective, the biggest benefits are automation of the security and monitoring systems. Our automation consumption has increased considerably since we began using Automation Anywhere. Initially, we were using two or three bots. Now, we have almost 25. In terms of revenue, we can save around $10 million through automation. We still have room to expand, and we're looking to implement more bots, especially IQ bots, but we have some concerns about the accuracy level. 

Automation Anywhere is easy to learn for business users without technical knowledge. For example, I don't have much technical knowledge, but I learned how to use the solution from Automation Anywhere University. It's a user-friendly solution everyone can understand and implement in their business with the help of Automation Anywhere University. The university is more than enough to develop a small bot. It's a comfortable platform. Even the new employees who don't know about automation can gain experience. It only took me about one month to learn the solution. 

The IQ Bots have a lot of room for improvement in terms of accuracy level. We need to improvise a lot. I'm facing another big challenge with one of the use cases. We raised a ticket and did multiple follow-ups with support, but the accuracy still isn't up to the mark. 

We've been exploring FortressIQ and tools that use AI/ML in the past three or four months. We're looking at ways to implement those tools in new areas, but there is a gap because Automation Anywhere University doesn't have much information about them yet. 

We have web recording applications, so we need something like AI to be involved where we can give a verbal command, and the bot can learn to do an automated process. That's the kind of technology or innovation required from the business perspective. If a business consultant can interact with a generative AI or some other advanced AI that can act as a developer, the development cost will come down drastically. 

I have used Automation Anywhere for more than six years.

I rate Automation Anywhere support seven out of 10.

Neutral

I don't deal with purchasing, but I know that Automation Anywhere is more cost-effective than Blue Prism. I won't say the cost is low, but I can say that it's cost-effective. 

I rate Automation Anywhere seven out of 10 overall.

We have automated PO processing, PO-to-order booking, and various website flows, such as ticket generation, timely uploads of files on the website, and report generation. We have also automated report delivery to all end-users.

Manual efforts have been reduced and the accuracy has increased. In the processes I have done, the accuracy has reached 100 percent, and manual load and time has been reduced.

Object cloning and Excel operations are what we use most.

The ability of Automation Anywhere to provide automation at scale, on a scale of one to 10, is a nine. Integration of its RPA bots using APIs is an eight out of 10.

More and more innovation is going on, and they'll have to keep adding features to keep up with the market. They have generative AI on their platform, but that's a new part. They are working on it. It's not 100 percent foolproof, but eventually it will get better. They need to work on their AI capabilities.

I have been using Automation Anywhere for four years.

The new version is stable now. When we first started, the platform was not stable, but it became stable when we shifted to A360.

If we are stuck anywhere, their technical team is always available. We have raised one or two issues with them and they were able to help us out and turn them around.

We haven't required them very much, but they are available if we need them.

Positive

I've worked with Microsoft Power Automate, but at a very basic level.

The initial deployment is easy. The documentation is clear. Implementing A360 on-premises, a complete end-to-end installation, takes four hours. We just need the server team for administrator passwords.

I had already tested and tried it on a development server, so I had all the steps written that I had to follow for deployment to production. It didn't take much time. I read the installation guidelines and documentation from Automation Anywhere and it was easy for me to do it.

We have about 25 end-users of the solution in our organization, and three of us take care of maintenance. In terms of bot maintenance, not much time is spent unless and until there's a change in the process or the environment.

For business users who do not have technical skills, it is easy to use the product. They understand what is possible with the tool over time. Within a year, they understood what needed to be automated and what not. Training non-technical employees on Automation Anywhere usage takes three to six months.

I did it myself.

It's an ongoing process. I have done more than 400 processes for our client over a four-year period. The time a process takes to automate depends on the complexity of the process. Within three or four weeks, a process is generally completely done, from development to production.

We tried UiPath at the time, but Automation Anywhere was more promising. It was easy to scale the bots in Automation Anywhere, and the implementation using Automation Anywhere was simpler compared to UiPath. However, I've heard from people working with UiPath that it's faster compared to Automation Anywhere. The execution time for Automation Anywhere might be 10 seconds, whereas with UiPath it might take six seconds.

If someone is considering an API integration instead of an RPA solution, that means the API has to be available. Using Automation Anywhere, you can automate any process completely, end-to-end. It doesn't need an API. We can automate front-end, Excel, Word—anything. That is more helpful compared to an API integration.

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.

We use Automation Anywhere to automate websites and extract data from them.

Automation Anywhere helped us automate human tasks.

The learning curve is quite shallow.

Automation Anywhere has helped our organization by working around the clock, allowing us to rely on robots instead of humans. We no longer have errors, or if we do have some problems, we are informed. It is easy to implement and monitor the processing part of the software.

Cloud-based Automation Anywhere provides automation at scale with ease.

The integration of RPA bots, APIs, business applications, and documents in Automation Anywhere is good.

Automation Anywhere has helped our organization increase our automation consumption.

The best features are the ease of use, the short learning curve, and the good support from our local partner.

The quality and speed of Automation Anywhere's support needs significant improvement. We are not satisfied with the quality of support.

I have been using Automation Anywhere for two years.

It is stable.

Automation Anywhere is scalable.

The technical support is not good. They are slow and the level of support is poor.

Neutral

We tried using Blue Prism for one of our projects but ran into a lot of complications when we tried to implement it ourselves. We found Automation Anywhere much easier to implement.

We had an enablement package, which we could start using because Automation Anywhere turned it on automatically. We did not need to set it up ourselves, as it was only for bots running in our environment. It was not difficult.

The price for Automation Anywhere is reasonable.

We also evaluated UiPath, which has similar quality and features to Automation Anywhere. However, we chose Automation Anywhere because we had someone in our organization who was familiar with it. Blue Prism is significantly inferior to both UiPath and Automation Anywhere.

I would give Automation Anywhere an eight out of ten.

API is our first choice whenever possible, but it is not always feasible, depending on the use case. Sometimes, we need to perform additional process steps beyond simply calling an API. In such cases, we may consider using an RPA tool, such as Automation Anywhere, especially if we do not have an API.

Typical maintenance is required. If we get new versions of bots, we need to update Automation Anywhere. However, the cloud services are maintained by Automation Anywhere itself, so we don't have to worry about that.

I recommend looking at IQ Bots, a very good and easy-to-use intelligent document-processing feature. I also advise taking the quick training available online and trying to build a simple but real process on their own. There is also a community edition that anyone can use, so it's easy to start with that to try out Automation Anywhere.

We are a biotechnology company. We are in healthcare. We receive samples, and we need to do some of the entries. We did a PoC through Automation Anywhere. Our objective was to improve accuracy and reduce manpower.

We were able to 100% achieve our objectives. There was an increase in accuracy, and there was also a reduction in manpower. The bot reduced the manpower required. We could reduce nearly 40 members through this project in Automation Anywhere.

Automation Anywhere has helped our organization increase its automation consumption. Earlier, we did not have any automation for the labs to increase accuracy and reduce manpower. We have now achieved the same with Automation Anywhere. We have done about 60% automation. We have used it only for the lab. We are planning to use it for the marketing team, call center, and all other departments.

It improves accuracy and reduces manpower. It is easy to learn. We trained our lab people, and they were able to achieve accuracy with the technical knowledge. 

I would like it to have AI and ML capabilities.

The support can also be better. It can be faster.

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

There is 99.5% stability. It is very stable.

It is scalable. With a robust infrastructure, if the sample size increases, we can scale on an on-demand basis.

We plan to increase its usage. We are planning for the lab expansion. During the lab expansion, we will also increase the licenses.

After the execution, we need to have service and support. Sometimes, there is a lag in the support. We are running labs 24/7, but when we raise a ticket, they are able to call and fix the same only on the next business day. For this reason, we have planned high availability for the RPA bots in the case of any incident. We are managing through that, and we have also highlighted the concern about the service and support. They also plan to work on it.

Neutral

We did not use any other solution.

The initial setup was handled by the business owner and IT. It was done by our partner. It requires technical skills. We need to have a workflow. If we have a clear workflow, we can easily implement the same with the partner.

We provided hands-on training for Automation Anywhere through our partner. In the first phase, it took us at least three months to train the lab operations team and other teams supporting the project. We parallelly created a document for the initial phase. All the people who are now being onboarded use that document. They are able to support the bots without any additional training.

We did the implementation with the help of our partner. They first understood the workflow of the healthcare sector and our architecture. After that, they planned the solution for us. It took them a minimum of one month to understand all those things, and then we did the PoC.

They have also done the integration with the lab software. It took them nearly four to six months for integration and report generation.

In the first year, we got 20% to 30% ROI. In the second or third year, we got the complete amount that we invested. There is also an improvement in the business because of data accuracy.

It is not cheap, but we are able to get an ROI. I would rate it a seven out of ten in terms of pricing.

There are no costs in addition to licensing, but we had to pay our partner for one-time implementation.

We also did a PoC with UiPath and other solutions. We chose Automation Anywhere because we could get significant ROI with Automation Anywhere. Its accuracy and costs were better than others. We have purchased the bot with Orchestrator.

You need to have a good partner to assess the performance and get the best solution. 

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

We are the implementer and sales partner of Automation Anywhere. We have implemented hundreds of business processes for clients in the banking, insurance, and manufacturing sectors. We use Automation Anywhere to help our clients automate routine tasks.

Automation Anywhere can be deployed on the cloud or on-premises based on the client's requirements.

Programmers with good logical thinking will find the learning curve of Automation Anywhere to be relatively easy. Non-programmers can also learn to automate parameter configurations with relative ease, but they may find it more difficult to automate tasks that require customization or workflows.

Automation Anywhere has helped our clients' organizations during the lockdown period in the last two years, from 2020 to 2021. Our clients who were using automation were very happy because the bots could run while the people were away. We were able to control the bots remotely and scale their businesses. In fact, there are several use cases where we implemented solutions solely for scaling purposes. Our clients used to receive millions of records that needed to be processed within a defined time frame, which was not possible manually. This is where the RPA solution using Automation Anywhere came in. It allowed them to scale up their businesses. One particular use case that I still remember is the insurance for farmers' crops. Farmers need to be issued crop insurance policies within a given time frame, as the crop cycle is typically three to six months. This needs to be done well in advance, and India is a large agricultural industry with millions of partners. The scale of this process is huge. There were some complications involved in this process. For example, we had to connect to bank accounts to verify whether payments had been received, and then connect to the insurance system to issue the policies. Even though I am simplifying it, there were many complexities involved.

It can provide our clients with scalable automation to a certain extent. However, as the processes become larger, the optimization decreases and the performance suffers. This is because of the scaling and the processing that needs to be done. To address this, we also use open-source programming to do the processing outside of the RPA tool and then call those libraries from within Automation Anywhere.

It has many connectors, so we can easily integrate with other applications.

Automation Anywhere has helped our clients increase their automation consumption. For one of our banking clients, we automated 85 percent of their processes, significantly reducing the amount of human involvement and only requiring human interaction in the approval process.

Automation Anywhere is fully configurable. It has several commands that can be used to configure the parameters, and it is easy to use.

Novice users are able to automate basic applications using Automation Anywhere. Business processes are more complex and require experts to be brought in to automate. The automation process can be made more user-friendly.

I have been using Automation Anywhere for eight years.

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

I give the scalability of Automation Anywhere a nine out of ten.

The technical support is good. They stay within their SLAs.

Positive

We have used Automation Anywhere and UiPath, and in one place, we have also used Power Automate. We find Automation Anywhere and UiPath to be very easy to implement. Both products have a lot of features and are configurable. We can connect to any specific data source, such as Oracle Finance or Salesforce, through an API, or we can do desktop automation using either tool. Power Automate also allows us to connect to various data sources for automation. However, it is mostly cloud-based, which is not ideal for our banking and insurance clients. They prefer on-premise solutions. Power Automate does offer an on-premise solution, but it only supports desktop automation. For workflows, we need to use the cloud-based solution. This is a limitation of Power Automate. In terms of cost, Power Automate is much cheaper than Automation Anywhere and UiPath.

Assuming that the infrastructure is in place, the deployment of the Automation Anywhere components, which include the controller, parts, and studios, can be completed within a maximum of five days.

Automation Anywhere is generally more expensive than Power Automate, but they may offer a better price for large volume consumption. 

On a scale of one to ten with ten being the most expensive, I rate the price of Automation Anywhere an eight out of ten.

I would rate Automation Anywhere ten out of ten.

API integration is a good thing. However, it takes longer to implement than RPA. Once implemented, API integration can execute tasks faster. The cost of API automation is higher than RPA because it requires specific programming by experts.

Automation Anywhere itself does not require maintenance. Only the processes need to be maintained, as they may need to be updated to reflect changes in compliance requirements, government regulations, or the underlying systems. Additionally, patches to the Automation Anywhere software may sometimes cause changes to the processes, which may require maintenance. We currently have 150 processes, and two experts are able to maintain all of them.