Automation Anywhere Reviews

Our primary use of this product as a solution is developing bots to automate tasks and processing. For example, we have financial bots and we have IT bots. We have been involved in developing and monitoring the bots for about one and a half years, mostly for finance and IT. A majority of the tasks were done by other teams.

We have automated mainframe applications and integrated the tool with web-based applications and SAP. We have automated many SAP processes, including posting the entries and POs to SAP.

We are currently planning to migrate those bots into the current version (11.3.2) to make the bots more stable.

We are using the on-premise deployment model. We have multiple processes getting automated through this tool.

The major benefit for using Automation Anywhere is that it has provided a lot of FA (Finance Automation) benefits. That is a major plus point for using an RPA (Robotic Process Automation) tool. Any automation tool, for that matter, has its benefits. But because Automation Anywhere is easier to implement and learn, it is possible to move the bots to production faster. Speeding up that process helps in simplifying our workflow and productivity, and allows our people to do the most useful work we can do.

The basic Taskbot itself is the most valuable part of the product for what I do. The use of IQ Bot is still in a development stage. We are looking forward to August 2019 when we should be migrating to a newer version. That seems very promising. For now, we use Taskbot and Metabot with a variety of applications.

The ease of use is good. We had someone join the company who had no understanding of RPA. He was trained on it, getting his hands dirty, then he was able to develop and start automating processes quickly within a month. 

Resources are available online. A person can get certified and start automating right away.

The Bot Store is good. Although, we have not used the Bot Store much, there are some useful bots already built in it. We can just use them in our processes if feasible.

There are several things that would improve the product. I would like to see them include a group chatbot and make the IQ Bot more stable. Just those things would be great. Adding those kinds of features improves what we can do with the product. Using a client control room concept to ensure that everything is based on the web login, would also be great. Obviously we know that the development of new features will take some time.

We are expecting those kinds of features in the future. We expect more AI integration in our technology.

Automation Anywhere could use to be more stabilized. The product is becoming more stabilized with newer versions, but there are various things that still need to be stabilized. In the current version that we are using, we have a Control Room where the client will sometimes get disconnected. This will result in downtime. Therefore, we need some stabilization from the tool perspective. We don't have any other option than to raise a ticket to Automation Anywhere or get in touch with their support to get the issue resolved. So, we are having downtime. This can be improved.

We are not completely okay with the IQ Bot. We previously used version 5. The newest version does have more accurate results.

Technical skills are required to use the product. With these tools, technical programming is still required with the guidance of technical people. Business people can go ahead and try building a few smaller processes, then when they gain technical knowledge, they can use this tool to their full advantage.

Most of our processes are attended automation. It would be great if more processes were unattended automation, so we could release more FTEs.

We are currently using third-party Taskbots. We would like Taskbots directly integrated into the tool.

We have been using Automation Anywhere since version 9. Over that time the stability has improved a lot. We are expecting it to be even better in coming versions and this is why we are looking forward to our migration to 11.3.2 in August of 2019.

In program versions 10.3 and 10.7, what we were developing was okay. The stability was fine. In version 11.2, we had basic client login issues and database issues as well. When we have a better foundation as far as the stability, we are hopeful of getting better updates.

As far as being able to scale our usage of the product, until now, we have been doing well in diversifying. In the future, we expect to be able to get more from the tool. Our ultimate goal is to use the tool to automate most of our internal processing and reap the benefits of RPA.

Multiple users are currently using the product.

The technical support has been really good. Honestly, it is very good. We have been getting good support from the correct technical people quickly. One thing we would like to experience is that instead of waiting for a new version of the tool to resolve issues, that we could get immediate patch upgrades to cater to our requirements. That would be great. We are getting patches sometimes, but they do not perform as well as we might hope.

We have taken courses from Automation Anywhere University: version 11 and IQ Bot. We also attended training at the Automation Anywhere office for IQ Bot. The Automation Anywhere University courses are quite good. You can easily learn and get certified, which has some value in the market.

We were looking to Automation Anywhere as a solution in a relatively new concept. We believe it was our best choice and, currently, we are hopeful that the stability and the enhancements done to the tool will pay off. We are looking forward to using 11.3.

So far, the initial setup of versions has been straightforward and we expect it to be even smoother in the future.

Bot creation process: 

1. We identify the process.
2. That process will be well-documented along with the operations people, who will develop the BRDs. 
3. After the BRD creation, we'll come to know whether the process is feasible to automate.
4. Concurrently, a solution design document will be developed.
5. Developers will create the bot. 
6. Once the Bot is developed, UAT will be given to the operations people telling them whether the bot is performing as per their requirements.
7. Once finalized, we'll get a UAT sign off and the code will be moved to production where the bot will go live.

Scaling bots to production depends on the process and how complicated it is. For a simple process, it will take two to three weeks. If the process is a bit complex, it may take close to one to two months. It also depends on how your internal compliance is organized in the company. We have a compliance check done at every phases of automation, so it will take us more time to get the process live even for a simpler process since we have to get compliance sign off during every phase.

We did not use an external resource for the implementation, but I was there when the initial setup was in progress.

As I am currently part of a team of developers and people who perform functions, we are not directly involved in the deliberation of assets or ROIs. However, it is apparent that there is a return on investment, and we are noticing it.

We have many benefits reaped from the automation work we have done. So, I don't have the exact information about the cost and what our return on investment is, but it is benefiting the organization in a much bigger way by channeling efforts away from wasting manual time on processing.

As our team size increases, we may get some more licenses for the tool.

We checked on Blue Prism and UiPath. UiPath was still developing. 

We opted for Automation Anywhere. The pricing was okay for us. Also, It was easier to learn the tool and implement within the team. It is easier to learn, implement, and get things done with Automation Anywhere compared to other tools on market right now. 

Before automating, understand the process:

• How big is the process?
• Is it of use to the organization?
• How repetitive or complex is the process?

This is important because automating tasks requires resources.

On a scale of one to ten with one being the worst and ten being the best, I would rate Automation Anywhere a seven. So far it has been good, but obviously there are opportunities to be so much better.

We expect more from Automation Anywhere based on the new technologies that we know exist concerning AI and also unstructured learning. There's a lot of room for improvement, so that's why I would not rate it higher. Other than that, for data structure, it has been good — apart from a few stability issues.

Ease of integration is good. We have automated a process in the current version. Automation Anywhere will tell us if it won't support this version anymore at this particular time, so we'll have to migrate that code to the currently released new version. At that time, we may face some challenges after moving the code. We may have to do some tweaks to the code. We can't directly run it as is, so we'll have to do some minor tweaks so that it is stabilized more, then it'll be better.

As far as recommending the software, that depends on what use case and what work requirements an organization has. For structured data and for simpler processes, it is fine. For unstructured data — which should be addressed by IQ Bot and additional features — I may not recommend it yet. But for dealing with automation of straightforward processes, Automation Anywhere is good.

RPA solutions are continuously improvement due to competition. Sometimes, it is worth waiting for the next version which is more stabilized to be released.

We are in the retirement industry. We use it for application-based automation. We are trying to mimic our operations to redundant business users' tasks, like clearing claims and loans.

We are using version 10.7. We are currently trying to upgrade to version 11.3.

We use Bot Insights. Business users utilize Bot Insight dashboards to get analysis.

In the 10.7 version, the back-end port for the MetaBot password has looping. This has been a type of limitation. Now, we are upgrading and integrating the Control Room, which is a validating feature.

I would like them to add OCR features. This would help us deal with unstructured data and we can get more data out of images.

I would like to see more features related to artificial intelligence. 

The latest version is more stable. We have mostly legacy applications. We do interact with Automation Anywhere support for patches and DLLs which are compatible with our legacy applications. Maybe after our upgrade, we can expect more stability.

In couple of months, we are looking to upgrade. We have set up our environment for integrating in AWS into our architecture. We are setting this up now and planning to install Automation Anywhere 11.3 to see how it is.

It is scalable. Since we have only had it one year, we are still looking into the scalabilty factor.

The technical support is good. They are knowledgeable and don't waste much of our time. They are quick in resolving things by identifying the exact root cause. 

We try to resolve the issue from our side first because we are trained in the product. It is only when we can't solve the issue that we contact support.

The initial setup is straightforward, except when setting up with cloud-based services, like Amazon. The cloud-based setup process is complex.

Automation Anywhere came in and helped set up the tool for us since it was initially new when we onboarded it.

It has saved us a lot of hours, manual effort, and we can focus on more important tasks, which helps us with our ROI.

We purchase on a bot basis. Our costs are approximately $5,000.

There are a lot of vendors out there, like Blue Prism and UiPath. However, A2019 offers cross platform and single point, which is why I would recommend Automation Anywhere.

I have been very impressed with the A2019 version. This version is phenomenal. 

Primary use case of Automation Anywhere is financial accounting reporting use cases.

We use unattended bots for all the financial reporting. We have also done some use cases in master data management (MDM). These are the things that we did early last year.

For the next year, we will be primarily focused on cognitive automation. We've already started with IQ Bot exploration. We will be looking into the new version of IQ Bot.

We released ERP, improving our workload balancing. For example, for each of our employees, we have release almost 400 hours of critical repeated efforts.

Automation Anywhere is very good for rapid development. It has all the capabilities in terms of giving a stable automation framework. It has very cool technical capabilities, like MetaBots, dev controls, and object cloning. 

We encountered issues during the upgrade of the framework. We were using the older framework of version 10.3.5. When we were upgrading, we were having a few issues in terms of getting the proper hardware and software prerequisites. For some things, like getting the controls of some of the application's tools, we were getting Automation Anywhere's help.

The operation happened both in hardware and software. There was some amount of friction in terms of technical and hardware operations. In terms handling capturing the controls, that's where we used the help of tech support.

We are looking forward to the release of cloud/web automation, which has yet to be released.

We having most of the use cases rely on Automation Anywhere. However, we face some challenges in terms of RPA implementation with Citrix.

Whatever use case we have deployed in production, we have found nil in terms of stability issues. 

For scalability, we are still working on the bot utilization framework and have created additional frameworks apart from the existing automation framework.

Tech support is one of its primary features, far better than the other RPA tools. We have been able to fix some big technical issues that we came across.

Initially, we were having a few challenges in terms of getting the approval from InfoSec since we wanted some Veracode reportt from our CSM. That took some time. Initially, we were having open issues with the older version, in terms of the Veracode code report. These were high-end critical. Eventually, we were able to get the final report after the approval from Infosec. Then, we were able to install all of the software to our Olam framework.

We started with an integrator, then went directly with Automation Anywhere. Our experience was good. They started by helping us work with the software and understand Automation Anywhere's capabilities.

We have released at least $400 to $500 a month during our peak period, so we have really seen ROI with the product.

I think it's $5,500 per license.

We had some RPA tool implementation strategies. We looked at all the tools and their features. We did a brainstorm session with all the tools and found out the nuances between them. We identified Automation Anywhere as the tool that we should implement in Olam.

We compared Automation Anywhere with UiPath, Blue Prism, OpenSpan, and WorkFushion.

Automation Anywhere is one of the easiest tools that developers can use for development. It takes them only a small amount of time. It has good stability in terms of implementing the automation use cases. We also found Automation Anywhere as a pioneer in terms of RPA implementation.

Automation Anywhere is a pioneer in RPA tools. I would recommend Automation Anywhere. Automation use cases will be rapidly implemented through it. It has a good amount of stability and cool features that can be robustly developed with the help of developers as well as business people.

We are looking forward to using IQ Bot as well as attended automation in the coming year. These are features that are available, but have not used yet. We are trying to do a PoC to start and implement them into our daily use cases.

Currently, we are focusing more on finance, shared services, and interpretive related ideas. For accounting and finance statistic, we have reconciliation specific processes, such as rates uploads into systems. The majority of our development is on SAP and Excel. We are focusing on the financial services area, so our use cases are more related to finance and accounting. These are the use cases developed by the development team.

We are using an on-premise deployment model.

The main agenda for using the RPA is to see how we can get the benefit from reducing human capacity as well as quality output. These two are the major focus for us and what we are achieving.

Timeline-wise, it normally takes a long time to develop. With the AA and RPA concepts and their ready-to-use components, we can deliver a bot within couple of days or within a week time frame based on the use case.

It is easy to use and developer-friendly. The development time is very short. If any system needs to be changed or any functionality needs to be incorporated to any of the technology, it usually will be a long process, like months. With this innovative tool's automation, it is very dynamic, easy to develop, and deliver results quickly. With some of our use cases, we were able to deliver within the time frame of two to three weeks, which is the biggest plus with this tool.

There are good MetaBots available in the Bot Store. We were able to leverage them, as well as established our own reusable components. Considering that, it is easy to add on any software or applications that sits in the system.

We would like to have the Excel plug-in. We have a challenge with unattended bots in development which will be deployed on virtual machines. End users ask, "Why can't we run the bots whenever we need?" The new concept for getting attended bots as well as the Excel plug-in will solve this problem, but we'll wait for 2019 version, which may be a better solution for the business.

More structured and unstructured data collection will be a challenge. While we have the IQ  Bot tool, the success rate at the beginning will be lower. It will be around 20 to 30 percent at the start because you need to train the bot at regular intervals. Of course, this depends on the data. This area could use be improvement.

The marketing strategy is directed toward end users. These leads to confusion in the organization regarding, "Who needs to develop?" Is it IT or the business? This causes friction within the business. Whatever the approach, it is important to show how to get the most benefit out of the tool. There should be a clear roles for IT and the business when using the tool. This way teams and structure can be better established in a business.

For attended automation, there are still questions to be answered: How it is going to maintain the queue? E.g., there are 20 users who want to process their own processes, and when they trigger things, how will the Control Room react? How will bot work distribution happen? These things still need to be looked into, but conceptual-wise, attended automation is really good.

It is confusing: Who needs to develop the bot? The business or IT. At the basic level, the bots can be created. However, once they are moved into production, you have to make sure that the bot is stable and running 24/7 without any issues. Therefore, a lot of care is required due to the amount of controlling mechanisms required.

There are a few problems with deployment and maintenance. When it moves to other systems, the consistency will be somewhat lost.

RPA is decently established and stable as the market is coming up with new features. However, the unstable area is more the IT part of it where a lot of research still needs to be done, especially in the case of artificial intelligence. 

When we run bots, sometimes the systems will go down. Maybe it is because the same functionality worked once or even regularly, but then all of a sudden there will be an issue. It might be a network, latency, or some other issues. Still bot stability needs improvement. These are very rare situations. It works most the time, but one time it will fail and we don't know why.

When I talk about RPAs, it is to say, "Can this problem be solved with RPA?" Scalability-wise, we are in good shape. 

In terms of AI incorporation, this type of scalable incorporation would be benefit everyone. The trend looks like we are going to reach to this point in a good manner.

We were able to put more than 40 bots into production. There are around 20 more in progress. On average, we were able to save around 25,000 hours of manual efforts.

The technical support's response is very good. They gave back solutions quickly. We haven't face many challenges when using the tool. So, we haven't interacted much with the technical team, maybe two or three instances. 

We looked into moving into RPA because it was the trend in the industry.

We do regular acquisitions which leads to a lot of duplicate roles and resources along with similar activities. With this approach, we can streamline our processes and bring uniform processes across the organization. We have been able to establish this. If we use the bots on a lot of manual efforts, it will reduces effort. Going forward, we can use the bots in a better manner by using them for the strategy of delivery and appointments.

We started this journey with a PoC. For three months, we tried understanding the tool and its capabilities. 

The initial setup is not complex for the tool setup. The struggle points are establishing the right mechanisms to identify the candidates and prioritizing things. 

In April, we started the pilot. By July, we had the software as well as the use cases that we needed. We got the licenses in July or August. It took us at least a quarter to establish systems and resources. Then, we started delivering the bots from December 2018. It took six to eight months' time frame from PoC to first bot deployment.

For our bot creation process:

A business user, whoever is doing the manual process currently, will send their request with the details of the use case. Those details will be assessed by IT and the business functional groups to measure what will be the man-hour savings. Also, is it a possible candidate for RPA?Based on those measurements, we identify candidates for RPA, then we determine if they meet the current threshold of 500 hours. If it is more than 500 hours, we consider that a candidate for RPA. Based on that criteria, we identify and prioritize it. Afterward, it comes to the development team for development.

If we had been alone during the initial setup, might not have been that successful. However, when we partnered with the other groups, like consulting firms, then we were able to get the right mechanisms in place within a short time.

We did the deployment in-house.

We have a good dashboard to measure ROI. Whatever investment, licensing, and resource costs together are put in for development and delivery, we are still at an ROI of 250 percent.

To measure ROI, whenever we get a use case from the business when we do an assessment, one of the factor that we capture is the time saving. We try to measure and apply the country rates for the locations where they are doing manual efforts. We measure the time savings by applying the country rates and deriving the hours and value.

The time that it takes to develop and deliver is within two to three weeks.

It has good licensing costs which are average for the market.

We did try out UiPath, which is a good solution. 

We also look at Blue Prism.

We like Automation Anywhere's end user experience. We thought Automation Anywhere was the better solution for developing bots in the long run. It is a centralized tool because of its Control Room. It makes sense to have a solution where everything is in a centralized repository. AA has a more future-looking perspective which will help them in the long run.

We currently are not evaluating any other vendors.

When we saw the tool capabilities, we were so excited. We tried to start using them but we needed to have the right structure and mechanisms in place from the beginning to identify the use case for prioritizing. This plays a major role. 

If you are a big organization with a center of excellence, you need to bring all the people together. The establishment will play a bigger role than just developing and delivering bots. Developing and delivering bots is a very small portion, which is doable by any individual who has a basic technical background. To be successful in your journey, having the right structure upfront will help.

We experimented a little bit with IQ Bots, but we didn't see much use cases in this line currently.

A lot of people interact with RPA and the industry is really excited about it. However, you need to pick the right candidate to be successful in your journey, along with the right framework for the development. This will give you a good output. This is what the business needs to test. Pick a solution based on the organization's needs as well as the right approach. Have an assessment with an approach framework will help.

Automation Anywhere is removing the boring, repetitive tasks from the workforce.

I've worked on different models over different frameworks. 

I do the coding as well as the deployment side. I prepare documents and the user ID. Sometimes, if the user ID is not prepared, then I jump into the process to get it done. With the technical feasibility of the document, I take the technical feasibility and do an estimation to code the bot. I configure the bot, then code it according to the entity and get it reviewed from the client. Then, I run the bot through the Hapi port, as well as different scenarios which might come up.

Once the client is happy, we have a couple of rounds of testing. We have a "You Ready" phase where we code for a few days and the client provides data. We run through the data and this give them the technical results. When they're happy, then we finally move the code over.

One of the clients that I worked with to automate their process received invoices from 12 different companies and different regions. These are the process steps that we automated:

1. We could get the data from PDFs (the invoices were in a PDF format).
2. We accepted the data, uploaded it, and filtered out some of the data. 
3. Once we extracted the data, we use it to search data on particular websites for a particular invoice number to be processed. 
   
4. We used the invoice number to process the invoice.
5. We got approval for the invoice. 

I worked on another process where it generated offer letters for different people with templates. We would get the data in a dump. We would take that data put it into a template, and then into a Word file.

With another client, we used to receive around a million files. Per day, we would have to process around 70,000 to 80,000 records, uploading data where the volume was huge. We deployed the process in multiple bots, using about 20 bots to get the process done. For this client, every second used mattered. We had to code the bot in such a way that we could save every second for them. We had to figure out how much time the bot took and the cost savings for any particular data. We used the workload feature of Automation Anywhere get it done. The manual process took around 30 to 40 people around five to six hours a day, where the bot finishes between one to one a half hours. This was a huge time savings for the client.

For the client with 70,000 to 80,000, we created an SQL database to maintain all their records using bots. E.g., if a bot failed, then another bot would retry using the same information. In the "You Ready" phase, this process was 95 to 98 percent successful. When we finally moved it to production, we had between 99 to 100 percent accuracy. This took us around one and a half months to set up. Two development levels were involved along with an architect who was guiding us.

The most valuable feature is the object cloning. If you compare it to the other RPA tools, object cloning in Automation Anywhere is the most valuable. Mainly for web application, object cloning comes in very handy. Most processes are built as either a website or as a desktop application. Out of 800 commands, around 150 to 200 will be cloned through object cloning. In Automation Anywhere object cloning, there is a special feature called DOMXPATH, where we can customize it to any level. If IDs getting changed, which happens in some cases, then we find out the pattern. Based on the pattern, we come to the particular text box and button. Then, we can use bots along with parent-sibling relationships to get things done. 

I like that it has PGP Command and it is able to connect to a Citrix environment. 

We have the MetaBot feature, which is valuable because we can read reusable components in the MetaBot, then use them as a framework.

The training and resources for this tool are very good. They are so simple that anyone can easily learn it. One of the tool values is its ease of use.

The Excel part needs improvement because we use it as a database. Right now, we are using UiPath for this feature, as that RPA tool allows us to sort, search, and filter in Excel databases. 

The IQ Bot is pretty immature, in regards to AI and machine learning. I would like them to add additional logic.

I have been using it for almost two years now.

Automation Anywhere is quite reliable and stable, especially compared to the other RPA tools. E.g., with UiPath, code that was working yesterday might not work today.

We have experience minor issues with Automation Anywhere, such as with the object cloning, where it required us to restart the machine. Once the machine was rebooted, the solution worked fine.

It takes one or two people to handle the daily maintenance of this solution.

We code our bots with tasks and subtasks in such a way that we can easily combine them when new features come up.

The initial setup is pretty simple and fast. It can be done from the web Control Room, which can be done easily.

For coding, we are keeping the information in XLS or XML files. We use MetaBot to retrieve the data. We keep our URLs in an Excel file, so when we go to our production environment that it will automatically take the URLs and implement them.

One or two people can deploy the solution easily if they understand the requirements.

In most of the cases, the product value is very good. If the infrastructure, implementation, and framework are good, then generally, the client can get a good return on investment. However, getting good resources is tough since most people have limited experience in RPA products who struggle a lot to use these tools.

The coding for Automation Anywhere is a lot easier than for UiPath and Blue Prism. I have about a year and half of experience with UiPath. Compared to UiPath, Automation Anywhere is easy to use and bot development is faster. If you try to develop the same bots in UiPath, development of the same bots in Automation Anywhere will be faster. If the client wants the bots to be developed very quickly, we will do it Automation Anywhere. However, if they give us time, then we will us UiPath. If the process is huge and complex, then we go with Blue Prism.

Another key advantage of Automation Anywhere is the object drawing feature. This comes in very handy. Whereas, if we use UiPath, we have to use the .NET code and commands versus Automation Anywhere where can use scripts or create MetaBots. 

Companies need to do feasibility testing to avoid trying to automate processes which are not right for automation. Then, they should examine which vendor is the right one for the automation process, e.g., Automation Anywhere or UiPath. They need to establish the proper infrastructure for the RPA product, like licenses and an RPA team. The RPA can be a mixture of trained professionals and people who are learning as they go from the training provided by the tool.

Version 11.3 updated a lot of features that were previously not there, like workload automation and analytics dashboards.

I am always learning new things with this tool.

We use it for backoffice processes. We are part of a shared service, so we do billing, credit, collections, and those types of processes.

We have done close to 50 projects in the last three years. AA improves our speed as far as moving files goes. It also helps in getting people prepared to work on a daily basis. We have a lot of jobs that run at night so that when people come in in the morning, everything's ready to go for them.

For example, we have two very separate systems which need to talk to each other. It sounds very simple, but we have a job that takes a file from one system and loads it into another. But it has to do that close to 1,500 times in the middle of the night. It's a job that used to be done manually by 150 people in 150 different markets. Now, it's something that's done during the night, and when they come in it's all completed. So it was a very simple task, but there was a lot of volume. It has saved everybody a lot of time and it has saved a huge amount of manpower. It saves us thousands of hours a month.

It's also very useful as far as interacting with employees. Employees can kick off jobs on an as-needed basis rather than scheduling them. It's always very helpful to have a tool that's interactive with the employees.

One of the most valuable features is object cloning, the ability to get into websites and do things faster.

I also like its usability. It's pretty easy to learn, pretty quick to get things taken care of with it. Our average developer is up within 30 days. We have our own training program. We don't use anything from AA for training. We've been doing it long enough that we created our own.

In addition, the user interface is easy to use. It's fairly user-friendly when you don't know anything about it and open it up for the first time.

The scheduling is a little difficult at times. Rather than setting up individual instances, it would be really nice if we had the ability to set repetitive jobs easily. Right now, if you want a job to run every 15 minutes, you have to schedule it a lot of times. I'd rather have the ability to just say 'run every 15 minutes.'

There could be some improvements made in the Control Room. I really like the concept of the application that they've got, so you can now access the Control Room from a mobile device, but there's only a lot of potential, there's not a lot of functionality there yet. That would be a great place for it to be able to expand, so you could have full functionality of the Control Room through a mobile device.

And in general, I would like to the solution to get into more machine-learning/AI. I know that the IQ Bots are looking to go there, but there's definitely a lot more potential there as well.

We haven't had any problems with the actual application going down. We really haven't had any issues. We have issues with third-party products going up and down, but we've never had AA just stop.

We're a small user, so we haven't had any problem with scalability. We've talked to a lot of people who have used it on a much larger scale. For us, it's very easy to add TaskBots. We're more than satisfied with the scalability.

We're always looking for expansion of the solution within our company. We use most of the commands available. There are very few that aren't applicable to what we're doing. We're always trying to get the solution into other departments within the organization itself. We use it a lot within the shared services, the area which we own. But outside of the company, we have several projects that are not within the shared service and we're always looking to talk to the other departments and get them involved.

We have 25 bots, meaning 25 licenses. Our core team that does development has four people plus a project manager.

Tech support has greatly improved. Three years ago we didn't necessarily have the best experience, but over the years they've gotten better.

As a side note, we go through a third-party first, through ISG. That's through how our service model works. Then ISG gets AA involved if they can't answer the question. We don't necessarily directly contact AA. Most of it's through the third-party provider, and then AA eventually.

ISG is great. We really haven't had a lot of problems. When we implemented version 11.3, we went so quickly - we went with it right when it came out - that there were a few questions that ISG wasn't aware of yet because it was so new. We went to AA through ISG and they were able to answer the questions right away. But for the most part, ISG is very on top of it, and we don't need to engage AA.

This is our first go in the RPA world. We had an internal resource, somebody within the company who had seen Automation Anywhere used in other companies. That person introduced us to the concept and, from there, we did some research and saw that that's where the market was going.

The initial setup was pretty straightforward. I did it myself and I'm not an IT guy, so it wasn't super-difficult. It took me a couple of hours, including configuration. Our IT team set up the actual virtual machines themselves, but the installation was done completely by me.

Our implementation strategy was that we started super-small. At that time, we started with five bots and the Control Room. It wasn't overly difficult. I just followed the documentation provided to install the service and configure everything.

Our initial project had to have an ROI, and that's why we started small. We have never not had a yearly ROI. We've always greatly exceeded the cost of, or the investment in, the tool. In terms of how much it's saving us, I don't want to be quoted on the exact amount, but it's more than millions of dollars a year.

We purchased AA through ISG and have done both annual renewals and a multi-year renewal, the latter recently. It has been very easy to add bots on an as-needed basis.

There are no additional costs from Automation Anywhere, but there is obviously the infrastructure costs for the VMs.

We definitely evaluated lots of different options at the time. Of course, it came down to Blue Prism or to AA. We went with AA because of the feature set, the way that the development was laid out. And support was also a factor. We were much more interested in States-side support.

Any company in today's environment would be foolish not to implement RPA. There are definitely different types of use cases where you could spread it out amongst the organizations and let them do their own thing. We have chosen to keep it centralized and have been pretty successful in doing it. But everybody should be using an RPA in some capacity.

I would absolutely recommend specifically Automation Anywhere.

Our experience with the solution has been a ten out of ten. I can't speak to the other tools because we haven't used them, but we're very satisfied with what we have.

We primarily use the solution for business process automation. We use it to help us with background processes.

It's a very stable solution.

We have found the solution to be very scalable. 

The solution, in particular, is simple to set up.

There are quite a few very strong features available to users.

I haven't really used it long enough to critique too heavily. I need some more time to do a deep dive into its functionality, which I haven't done yet. 

The solution should have a more robust forum to help users navigate the solution, learn about it, and get help when they need it.

It should have a better marketplace where you can gather various workflows, et cetera. It would be an ideal place to find pre-built workflows, for example. 

I've been using the solution for maybe one year.

The stability of the product is quite good. It's reliable and offers good performance There are no bugs or glitches. It doesn't crash or freeze.

It's quite scalable. We have many users on the solution. 

I'm not sure if I have ever actually contacted technical support. I can't recall dealing with them directly, and therefore would not be able to comment on their services. 

I'm also familiar with UiPath.

In general, when you set up the cloud solution, it's very, very easy. It's not overly complex. The on-premises version does take a bit more work. It's a bit more complex. That said, it's not too hard to handle either. 

The deployment is pretty fast. You're looking at maybe a 15-minute setup.

There is a community version, which is free. they also have a yearly paid license. 

I would recommend the solution to other users and companies. 

Overall, I would give it a rating of eight out of ten.

We are an integrator. We are selling RPA products to various customers. They have different use cases. 

We have cloud as well as on-premise deployments of this solution.

It is an easy product. It is easier and less complex than any other RPA tool in the market. It is a popular product.

Some of the machine learning (ML) components are still in development. They deployed many of them, but they are doing some improvements on the machine learning part.

I have been using this solution for one year.

It is stable.

It is scalable. It is suitable for enterprises.

Their technical support is good. I get very quick support whenever I face an issue. I raise a ticket, and the Automation Anywhere support team is available.

The deployment of Automation Anywhere is much easier as compared to any other RPA tool in the market. The solution itself is browser-based. So, we don't have to install complex software.

Its price is competitive with all other products in the market.

I would rate it an eight out of 10.

We do the implementation of Automation Anywhere.

It is easy to use. It helps to reduce your man-hours and manual effort.

Excel automation or the activities for Excel is an area of improvement.

It has been about three years.

It is quite stable.

It is quite scalable.

We have definitely seen a return on investment with this product.

It is a great product. Automation is the key, and Automation Anywhere is a good tool to use. It is great to have it.

I would rate it an eight out of 10.

We are a factory and supplier corporation, e.g. we focus on the financial and automation niche, but mostly financial. Our service is implementing automation, e.g. we implement Automation Anywhere (AA) for customers. It's a tool for automating processes.

Automation Anywhere (AA) is easy to use and understand, even if the user didn't have previous experience with RPA (robotic process automation) software before. This solution has many tools for automation. It's good even if you're just starting with RPA software, e.g. we don't have to decide on the whole productivity process, so we can put in the costs step by step first, then put in the details after.

Other solutions require you to know the codes first and make decisions on the whole process. This means that with other RPA solutions, if the user doesn't have the experience, it will be difficult for them to use and decide on those automation programs, which is not the case with Automation Anywhere (AA).

An area for improvement for Automation Anywhere (AA) is its organization or utilization, because if it's your first time to initiate automation, you have to convert it properly, and you have to develop the amendment path through the automation path, but you have to pay a subscription for it first. The first part is difficult because if you buy the full package without having much experience with the product, it could be difficult to utilize the process from manual to automation.

There are some limitations in the migration from the manual process to automation, because currently, Automation Anywhere (AA) is trying to develop transfer from on-premises to cloud. There's a limitation in migration.

The setup and deployment processes for this product also need to be improved, e.g. made easier.

I worked with Automation Anywhere (AA) before, and I helped a developer team provide it to the customer, and that was last year. We implemented it. I've been dealing with the solution in the last two years, but changed my focus to analytic solutions for a year.

Automation Anywhere (AA) is a stable tool.

Scalability for this tool is good.

It's difficult to set up Automation Anywhere (AA) on the on-premises environment. It's also difficult to make preparations for it. You have to be ready so it can support the automation process. That was what people experienced in the on-premises deployment, but I'm unsure how it is when it's set up on cloud. Setup could be easier if it's done on the Cloud.

If you have a person who knows the utilities of this solution, setup will take one to two weeks.

Our clients are paying for a yearly subscription of Automation Anywhere (AA).

Automation Anywhere (AA) is very easy to understand, but automation is something new here in Thailand.

We have 20 clients using this solution. For deployment and maintenance, we have a technical team made up of 10 people, with one vision analyst.

We have an automation hypercare team responsible for supporting customers after we've deployed Automation Anywhere (AA).

I would recommend this tool to others who want to start using it, because it's a good tool.

I'm giving Automation Anywhere (AA) a score of eight out of ten.