Automation Anywhere Reviews

We use Automation Anywhere to process our collections. 

We couldn't hire more people, but we had some information stored in Excel that we needed to distribute. The sales information was centralized in one area, so we automated the process of putting the information into Excel so everyone could help themselves. The benefit we get from this is increased efficiency. The bot performs the tasks four times faster than a human. Our goal is efficiency, not replacing bots humans with bots. We wanted to do more with the eight people we had and allow people to focus on what was important.

We got what we wanted, but the implementation took slightly longer than expected because we changed our methods and partners. We had some issues with our partner at the beginning, but we implemented the software in one or two months. It was fast.

I think the person in charge over there has the same mentality now, but we wanted to automate everything that is transactional or everything that impacts the client at the end of the day. We were looking to use AI to make development or programming more efficient, like finding some codes. I know Automation Anywhere has some kind of AI incorporated in it that can read PDFs and stuff. That would be nice to use, but I haven't had a chance to implement it.

We were working on a system called AS 400. Automation Anywhere performed well on that old system. It handled complicated processes. I had to review different menus and screens and give resources, storage, and databases. That's complicated.

We found a local Automation Anywhere expert and then trained someone inside the company to be a developer. This person had technical skills, so it was easy for him to understand the things in Automation Anywhere. The learning part was kind of quick, but I don't think that would be easy for a normal business user. I think it would be more complicated for a normal business user. I won't say that I learned all about Automation Anywhere, but I know how to automate simple tasks I learned by watching some videos and checking the community forums.

The Insight feature could be improved. I don't think there's a lot of information about how to use Insight, so you have to try different scenarios to understand that feature better.  

If I compare Automation Anywhere with UiPath, which has something cool that lets you automate a workflow. We have no positive response when we try to use it with Automation Anywhere. We are doing everything by code and the drag-and-drop component.

I don't think it's easy because Automation Anywhere is marketed as a low-code solution, but it isn't low-code at all. It requires some programming skills, and I don't think it would be easy for a non-technical user to program something on Automation Anywhere. 

One challenge the company faced while integrating Automation Anywhere was people. The IT department is big and has been divided into different areas, including databases, infrastructure, and support. To adopt automation anywhere, you have to put everything on the table and see what you want to do.  I also require resources with the capabilities and technical skills to program in Automation Anywhere.

We have used Automation Anywhere for four years.

I rate Automation Anywhere support nine out of 10. The support is good. The team from Colombia responsible for selling in Latin America can provide whatever you need. I don't have any complaints about that. They are always willing to offer you proof of concept in case you have to use it. I talked to somebody in Colombia because we wanted to do something in terms of proof of concept about document automation because we had so many processes that included PDFs. 

Positive

Automation Anywhere is deployed on the cloud, so I think it was very straightforward and fast. It took around one to two weeks.

Automation Anywhere is somewhat expensive. The prices are slightly higher, but if you need something, you must pay for it.

We also evaluated Blue Prism.

I rate Automation Anywhere 10 out of 10. I would recommend It for a medium-sized or enterprise business. Because of the cost, it isn't appropriate for a small business. The solution itself is good, but it isn't a low-code product.

I use Automation Anywhere for SAP, email, Excel, and web automation. We first try to understand the process and check whether it can be automated. Some processes require human intelligence and a human touch. If it's a completely goal-based process, you can consider it as a potential use case. After that, we conduct a complete analysis, based on which we set up the modules and proceed to development. 

Automation Anywhere helps us save time by replicating manual processes so our users can focus on other areas and perform meaningful work. It helps us automate repetitive tasks. We started with version 11. After that, they upgraded to 2019, and now there is Automation 360. Clients were frustrated with version 11, but 360 has a lot of good features. When 360 came out, the clients needed to spend money on the migration because they had to do some testing. 

It has saved the clients time. I would say reduces the time spent on these processes by about 30 percent. I can't say how much they save because I'm a developer and not involved in the business side of things. I don't even know what the license costs.

In one of our client's use cases, the user needed to log in at 6 a.m. because there is a trigger in Salesforce that happens around 9 a.m. Before 9, they have to do all the manipulations and place the files into a particular location. She had to start early in the morning to get all this work done. Now, with Automation Anywhere the bot handles all of this. Her job is so much easier.

I like Automation Anywhere's document automation. It can distill or scan documents and convert the information into a structured format. The solution doesn't require much of a technical background. I'm from a mechanical engineering background and don't have any prior experience with coding. I only know the basics of SQL. Even a business user who is willing to put in some hard work can learn and do some small things. The learning curve depends on the complexity of what you're trying to do. For me, one month was enough to understand the solution. 

We have begun exploring Automation Anywhere's AI features, but we have some limitations. We need to adopt rule-based automation, and there are still some use cases we cannot do. With AI, we can do some more use cases. We have done some POCs, but haven't done any projects where we integrated ChatGPT because we cannot put some of the things as a rule. 

It's easy to integrate automation into workflows and APIs. We just need to know where to pass the parameters or the details. If you have that knowledge, it will be easy.

Automation Anywhere's stability could improve. It isn't completely stable, but it's getting better daily. 

I have used Automation Anywhere for four years.

I rate Automation Anywhere seven out of 10 for stability. 

I rate Automation Anywhere support nine out of 10. I have raised multiple tickets with Automation Anywhere, and they usually respond within hours.

Positive

I previously worked with AutoIQ and Blue Prism, but it was a while ago. 

The deployment time depends on the process. If the processes don't have any dependencies, we just need to move the code to public and schedule it with the necessary configuration. The configuration is related to the process, not to automation anywhere. The processes require some maintenance after deployment. The number necessary to maintain them depends on the client. 

I rate Automation Anywhere nine out of 10. It only requires scripting for complicated jobs, but non-technical users can handle simple processes or those that are moderately difficult. 

I am striving to provide individuals with more time to focus on value-add tasks due to widespread headcount reductions. For instance, in finance and accounting activities, we use Automation Anywhere to replace individuals in maintenance tasks or those that were previously unknown to be time-consuming. This is where we witness the greatest utilization of bots. 

Moreover, we employ bots to handle fines associated with individuals driving company cars. With hundreds of fines occurring each month, it used to be a nearly full-time responsibility for one person to receive the fine, identify the driver at the time of the incident, and ensure the fine was directed to the appropriate person for payment. Such activities lacked significant value and consumed a considerable amount of time for someone, but now the bot handles these tasks on our behalf. I believe that finance is the primary area where we extensively utilize Automation Anywhere.

When we began deploying the bots, we established Key Performance Indicators to assess the return on investment. For instance, if a bot could save one-third of an individual's time, we would evaluate the amount of time saved and dedicate it to value-add tasks. However, evaluating the exact monetary savings facilitated by the bots is challenging because the funds are not directly spent on low-value activities. Instead, they can be utilized differently. 

It is important to note that the bots never completely replaced human workers. No job was entirely taken over by a bot. Rather, it was an assessment of how effectively we spent money with the assistance of bots, as they enabled individuals to perform tasks more efficiently. Although I don't recall the exact details since it was in the past, we would reassign the equivalent of full-time employees to these value-added tasks instead of low-value ones. At the time of my departure from the RPA topic, we had 150 bots in production, and we had a clear understanding of how many full-time employees would be dedicated to higher-value tasks as a result.

The ability of Automation Anywhere to provide automation at scale is commendable. We have indeed achieved tangible business benefits. That is certain. I am no longer aware of the metric used to evaluate this, except for the fact that we have eliminated various mundane activities from the workday of numerous individuals.

Automation Anywhere has helped our organization increase its automation consumption.

From what I recall of the type of issue we had to deal with when we started implementing Automation Anywhere, it was the integration with the identity and access management system that the company might use. This is because Automation Anywhere has a vault where we store all the information related to the bot, including the password it will use to connect to the system. The feature, which might be interesting for companies that don't already have an identity management system, was a bit tricky because I would have preferred the system to directly rely on our corporate identity and access management system to manage the bot's credentials. This way, we wouldn't have to store this information in the bot as well. It's something to consider in terms of integrating with an existing IT landscape.

I have been using Automation Anywhere for almost six years.

We did not encounter any stability issues with Automation Anywhere during the time I worked with the solution.

Automation Anywhere is scalable.

The technical support was helpful and responsive.

Positive

We had previously been using UiPath, and in late 2017, we acquired an organization that was already using Automation Anywhere, which belonged to a much larger organization. Consequently, we began to explore that tool and benefited from our colleagues' positive experiences with Automation Anywhere.

They were able to provide suggestions on the setup and deployment of the solution. As a result, we ultimately decided to discontinue the use of UiPath and transitioned to Automation Anywhere. Without the acquisition, we might not have implemented Automation Anywhere and instead would have continued with UiPath or explored other alternatives. Due to the acquisition, we were able to recognize that Automation Anywhere was one of the market leaders and swiftly create a proof of concept.

The initial setup was straightforward. Although I was involved in the deployment project, the actual installation was carried out by those responsible for implementing the Windows servers.

We needed to acquire the hardware because we had an internal cloud at that time, so we still have it. I would say that we managed to allocate the servers. It didn't take long. We provided training for the people who would deploy and customize the product with the assistance of Automation Anywhere in France. The global deployment infrastructure was ready to be used within a few weeks.

The implementation was completed in-house with the help of the Automation Anywhere team.

We obtained benefits from the original price prior to the acquisition and had to engage in negotiations due to the expansion of the usage scope. We were required to purchase licenses and bot runners, which determined the permissible run times for the bots. We successfully achieved a fair price worldwide. 

I rate Automation Anywhere an eight out of ten. 

We primarily utilize an attended bot, meaning they are not created by users. We have made efforts to retain control over IT in bot creation to prevent it from becoming a new avenue for shadow IT. When we started in 2018, the final department had a dedicated team responsible for bot development. However, they eventually hired contractors who developed C-Sharp programs that interacted with SAP through APIs. The bot would simply launch these programs, which is not the ideal method for automation, as we believe the bot should directly interact with the application instead of relying on a separate program to communicate with SAP through an API. I believe the team responsible for this no longer exists. Presently, we have a process in place to identify relevant use cases, and we are collaborating with a subcontractor who creates the bots for us based on specifications provided by the business.

We utilize Automation Anywhere with an attended bot. This implies that after receiving the specifications from the business and creating the purchase, we establish an agreement on the bot's scheduling for execution. However, the user never directly interacts with the bot; they only observe the results of its actions. Therefore, there is no need to provide training for users to utilize Automation Anywhere. We maintain IT control over it, while the development itself is outsourced. Consequently, the issue of the learning curve is not applicable to our situation.

We didn't use a lot of APIs with Automation Anywhere. Instead, we simulated the user's actions on the application's user interface. I can't recall any instances where we relied on APIs to initiate actions in the systems we were connecting to. However, I am aware that APIs can be utilized. There was a point when we wanted to employ APIs to retrieve the password or the bot from our identity and access the financial system just before the bot was about to commence its task. Additionally, we intended to trigger an API to reset the password once the bot had completed its job to ensure that there were no potential security threats associated with the user IDs used for the bots.

For those who prefer using API integration instead of a comprehensive process automation solution, I would like to emphasize that it's not exactly the same approach. Integrated APIs require developing a program for them to interact with. In my opinion, RPA offers a more straightforward approach as it simply replicates user actions within an application. We already have a ready-to-use bot. However, I wouldn't recommend using bots for everything, especially when we encounter use cases that resemble interfaces. 

Essentially, it involves manipulating the user interface of an application to extract data and then sending that data to another application on a daily basis. This approach doesn't seem logical. I'm not sure about the usage of APIs in the context of actual IT program development, where we need to retrieve data from various source systems that provide APIs. In such cases, we genuinely desire bots that faithfully mimic the actions of real users within an application. Our intention was never to replace any kind of deployment with bots, which is why we wanted Information and Communication Technology to be involved in the decision-making process. We wanted to ensure that the distinction was made between tasks that should be handled by bots and those that should be treated as interfaces or programs, aligning with our understanding of process automation.

We have a team of three people in Spain who are in charge of the daily operation of the Automation Anywhere platform. However, deploying our new bot is a quick process. There is a test environment where the bot is validated, after which it is transferred to the production control room and the bot's schedule is updated.

The team responsible for the data operations of the platform, taking everything into account, including the intrusion of the new bot into the production environment. They also handle the platform's maintenance. I believe we have three individuals dedicated to these tasks.

I use Automation 360 as an RPA developer to automate BPS processes. I have developed over 12 to 15 bots that handle back-office tasks. 

My current project is a UK-based water project. Previously, they would take the meter readings and send them to us for quarterly billings. We used to manually enter them in the system, whereas now, we have a bot to help us enter meter readings.

We have also developed a bot to open accounts for new customers. The bot takes all the input from the customer, creates an account, and sends a welcome letter.

Automation Anywhere has significantly helped my organization by automating tasks that were previously done manually by the back-office staff, resulting in increased efficiency.

A technical user can see the benefits of Automation Anywhere within a few days. After developing a bot, there might be some issues that need to be fixed in the bot. After resolving those issues, the benefits are immediate.

In terms of integration, I have integrated Automation Anywhere with some desktop-based applications, web-based applications, CRM applications, and Excel. I have also integrated Outlook where the bot sends an email through Outlook.

The recorder capture tools, specifically the AISense Recorder and Universal Recorder, are valuable. We use these tools in almost every automation. These tools are very effective in capturing data from various applications. We can get data from a web page or an application.

The integration of Generative AI is promising, though I have not yet developed bots using this new capability. It will be helpful for us in the future.

Automation Anywhere is a simple and easy-to-use solution with drag-and-drop activities. Automation Anywhere is easier to learn than any other tool. They also have Automation Anywhere University for learning. They upload all the videos there. They also have a good community.

Automation Anywhere has newly integrated the Generative AI feature. It should be more customizable. Currently, we can change certain parameters, but we would like to have the ability to do modifications within the LLM for better outputs. We would like the ability to fine-tune it. It would be better if Automation Anywhere could add some extra features for us to use the Generative AI feature.

I have been using Automation Anywhere for two years.

We are not facing any issues related to stability, lagging, or downtime.

Automation Anywhere handles scalability well with features like workload management, which helps in distributing tasks across different machines and bots. With workload management features, we can manage and distribute our workloads.

We have been facing an issue with the bots for the last two weeks. We have developed 15 to 20 bots for a client. After making any changes, when we push a bot in production and run it, the bot gives a preprocessing error. We were not able to find the reasons for that error, so we contacted their support and created a ticket. They got back requesting the log files. We need to take those log files from the client and provide those log files to Automation Anywhere support. They have been responsive so far and are working on resolving our issues.

Positive

I have used other tools such as Selenium, UiPath, and Power Automate to automate processes but have not extensively worked with them. I primarily work with Automation Anywhere.

Currently, we are using it for one client, and for that client, it is deployed on-premises. The initial setup was quite straightforward, but I was not responsible for the deployment. My role is focused on bot development and testing, while other team members handle deployment and maintenance.

I have not worked a lot with earlier versions or migrations of Automation Anywhere, but I have experience in migrating a bot, which was easy. I could easily migrate a bot from version 11 to Automation 360.

I recommend learning one RPA tool thoroughly before moving to another. With advancements in AI and ML, it is crucial to look into how to integrate these technologies into your automation.

A person without any technical knowledge can learn Automation Anywhere within one or two months. When a new employee joins our organization, our internal trainer gives them training for four to five weeks. Every week, there are two to three sessions of two hours duration. After about 15 sessions, our employees are ready to use Automation Anywhere to develop bots.

I would rate Automation Anywhere an eight out of ten.

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 are currently using it for a lot of projects, like repetitive or manual tasks. We are building bots to free human beings from boring jobs/tasks. We are working daily on Automation Anywhere to automate our processes.

We are using it on-premise. We are not using cloud for deployment. As of now, we are running it on our client machines. We develop automation on our desktops, then deploy our automation on our physical desktop using Automation Anywhere.

We have automated web scripting, downloading documents from particular websites, scraping data from websites, and extracting the data from PDF files. We are also updating the application with some user inputs. E.g., if you have an Excel sheet to update into a particular application, we can use Automation Anywhere tool and automate the process.

We have built some Java applications in Automation Anywhere. I have also coded macros and Python scripts to include in our Automation Anywhere tool.

The Automation Anywhere tool is very handy to use since I have some programming background, like I previously worked on Java. It's very easy to use Automation Anywhere because there is not much of coding involved. We just need to drag and drop the commands, then we can do the job.

Automation Anywhere is good for integrating other programming languages and other tools. The ease of use is very good, as we can directly code other programming languages, like Java or JavaScript, into our application and get output.

I have done work using a VPN, connecting via a remote desktop. The good thing about Automation Anywhere is if a client works without Internet, e.g., if we deploy on a client mission and the network is off, then a bot will still run offline.

If we want to read a scanned PDF, we use IQ Bot. Using the cognitive detail of IQ Bot and some machine learning abilities, we can train the IQ Bot to process all scanned PDF documents and give the results in an Excel file. This is a very good feature introduced by Automation Anywhere. IQ Bot is doing well.

The Bot Store is like a marketplace for bot developers. We already have some utility bots that are simple bots from there. We can download the bots from the Bot Store and use them in our current process. That's very helpful for the bot developers, especially for beginners who have just started with Automation Anywhere developing bots. There are a lot of bots deployed in the Bot Store. If you find any interesting bots, we can also upload bots to the Bot Store, making them available for everyone to download and use.

With attended automation, we need human intervention to provide input for bots. We make sure files are presented in a particular folder to pick up those files and feed it to the bot. Attended automation sometimes might go into exceptions, thus we need to monitor it in-between, then check whether it is working properly. This way, we ensure the bot is working properly.

Currently, I have developed between 20 to 25 bots. From when I started, we have deployed as a team between 30 to 40 bots. Their status is as fully running on our client machines.

We collaborate as a team if any face roadblocks or issues, discussing among our colleagues. Then, we involve the Automation Anywhere support team. They are very good. We can raise a ticket and get knowledge from their team. They help us resolve any issues.

The bot creation workflow is pretty simple. We check for feasibility, and if it is feasible, then we go about creating bots for the task. We have some measurements for ROI. We check the return on Investment to determine if it's feasible or not. We check the typical measurements, then go for Bot creation. After creating the bot, we don't have a production environment after creating the bot. We just deploy and run that bot.

If the process is huge and involves 10 to 20 steps, then it might take from creation to production three to four weeks of time. If it is a simple bot, it involves just launching a website and scraping data from the PDF, then putting it in Excel. For that type of bot, we can build it in one week and deploy it in seven to 10 days.

The return of investment on Automation Anywhere very good because I have automated some processes, like scraping the data from websites and updating some applications, and if we deployed full-time employees on these tasks, it would take more than a year and a half. However, if we automate the process and deploy a bot, it can be completed in just a month of time. The ROI is very good because the output is very accurate and the speed is very fast.

Our company is investing a lot of money in Automation Anywhere. They have saved money wherever humans are working. They invest a lot of money in FTEs and other logistics, so the money saving is very pretty good with Automation Anywhere. While I don't know the exact figure, the tool is saving us millions of dollars as well as saving about 40,000 hours in the last year. 

Currently, we are using attended automation. We do have unattended bots but are in the process of procuring some other licenses. In future, we will make a few bots unattended as well.

I did the Advanced Certification on Automation Anywhere University. I have also done IQ Bot learning. I am currently doing a Masters Certification. The courses are very clear. Any user can understand the content. If you are a beginner, go with Automation Anywhere. If you have some basic programming knowledge, that is enough. You can easily learn Automation Anywhere. It is not a big deal, and you can learn with the certification.

If a person doesn't have a programming background or skills, they can use Automation Anywhere and build bots. It's not a big deal. It's easy for business users to use. You just need some basic programming skills, like Ethernet and loops. 

I heard from Automation Anywhere that version A2019 will be released in either November or December. It is completely cloud-based and contains two IDs. One ID is a flowchart diagram and another ID has some commands. Therefore, any business user who has some basic knowledge can develop bots as well.

Version A2019 will be adding a lot of new features.

I haven't had a chance to work on Citrix automation.

We use Automation Anywhere for product SLAs on the finance team. We are also using it for a difficult automation project. 

We have automated a lot of processes, e.g., claim processing and payments.

It is currently deployed on-premise.

We are helping to automate some of the manual tasks and help to achieve the SLA.

We have some products, like Clubcard, which is a shopper's card that we're using in the Star Market. We are using Automation Anywhere for that validation, raising requests, tracking the Clubcard, and when users get new Clubcards. All these things are done through Automation Anywhere. We use the API to get the status of card numbers. 

IQ Bot is great. We recently implemented two IQ Bots in our finance sector. Manually, we had one person doing a task that took five minutes minimum. With IQ Bot, we are able to do that one particular task in one and a half minutes. That is a huge time savings.

We have done some Citrix automation with MetaBots for claim processing. We use it for validation. It is working well.

We have a credential manager. We have the ability to store in an encrypted way. Whenever we create any bots, we also have bot IDs. Without the bot ID, we are not going to deploy in production. We have the option for the support team only to get access and share their screen with users. If there is a critical password, the user will only put down the password. If we have the bot ID and password, then our support team can directly get that from the application IT team. That support center of excellence team will put in the ID password and credential and see the bot ID and password.

The API feature is the most valuable feature for some process, especially for the Clubcard. It helps us with validation of databases.

We are able to do a lot of things with MetaBots.

The management works well.

One of the great things about Automation Anywhere is that it is a developer friendly. If someone doesn't know the technology, but is logically strong, they can easily learn the tool. This is very good for us. We can train anyone in a short amount of time. 

If someone is not technical, they can also easily learn the tool. You do not have to write in syntax.

We have a situation where the system is not capturing data properly. It is clicking on the UI but it is not able to expand.

We have trouble with large volumes of data in Excel and are not getting good results. I want all the functionalities that they have in the Excel added to our existing version or an upcoming version of the product, e.g., Macros and VLOOKUP.

We have had connectivity issues, such as the reporting of a bad gateway.

We have integrated Automation Anywhere with our SQL database. I heard in version A2019 that we can easily integrate Python too, which is great news. Up until now, I have not been able to implement Python in our Automation Anywhere task bots. Though, we can integrate with other applications, like artificial intelligence, and this is better.

We have not implemented this tool with our AI. We have AI and IBM Watson. We would like to get information (or services) from the Automation Anywhere team on how to connect and implement the AI, as this is a great thing in the market. I'm looking for what to do.

Sometimes, we are facing issue in unattended. If unattended mode is not working, sometimes it will work in attended mode. However, I don't want anything in attended mode. The process is rule-based and logic-based. We just have to schedule, then if the user wants to run from the Control Room, they can. To run attended mode, we have to login into the VM to start it and human activity is required.

The version we started with is not as stable as the current version. We are trying to move to version 11. We are also in touch with our CSM regarding the A2019 version, which Automation Anywhere should release in the next year

We have 50 bots live in our organization.

We have three environments: staging, pilot, and production. In staging, the developer creates and tests their bot for internal testing. After that, we deploy into the pilot environment. That is hypercare which is for User Acceptance Testing (UAT). It is there that we run the bot in unattended mode for one and a half weeks at least with huge volumes. If we have no issues nor errors, then we create a ticket to deploy into production, our center of excellence. This is what our support team does. They will deploy into the production environments. We keep an eye out for at least 10 to 12 days as hypercare. At 12 days in hypercare mode, if we are not getting errors, then we run it in unattended mode as much as we can.

We are using Automation Anywhere in our business units. We have plans to increase the level of the tool's use.

We are planning to move onto the cloud, but first, we have to see if it will work with our business SLAs. If it is good, we will move over. We need to do a test first to determine whether the bots work well or not, which will take about three to six months. Then, we will make a decision on whether to move over to the cloud, the A2019 version. My team is excited for this version.

We would move over to Microsoft Azure because our company is already using it.

The technical support team is supporting us well.

We needed a support guide from Automation Anywhere for the initial setup because we had standalone and a lot of clusters. We needed help from a support guy during our setup to determine whether to go with a standalone or cluster setup.

For the bot creation process, we first check the requirement. Then, we check with each application, whether it is applicable through the Automation Anywhere tool or not. Some applications, like Oracle, do not work correctly. We make a feasibility report and advise the developer to use certain commands only. We provide a process map, e.g., how to create the bot according to Automation Anywhere guidance and what are the coding standards provided. We deliver everything. Then, the developer will start building our bot.

In our organization, we are focusing on continuous improvement through this tool. We are improving day by day, but not focusing on the elimination of any employees. We are just focusing in our improvements and accuracy in our SLAs. Therefore, there are three things that we are focusing on:

1. Implementing our SLAs on time. 
2. Focusing on accuracy.
3. Focusing on our continuous improvement.

Automation Anywhere is profitable for us. As volumes increase and we have a lot of data, this takes time to complete manually. Bots can complete the work without impacting the business. 

We are saving time. Some processes that have taken 24 hours for our guys to do, now take seven to eight hours for our bots. That's our achievement. It also brings accuracy.

We save money indirectly. We are also improving the accuracy of our SLAs. 

I am using that Automation Anywhere Master Certification for version 11. Recently, this has been updated in Automation Anywhere University. Until this month, it's free to use. There are no charges. That's why I would like to complete it this month.

We are waiting for them to release version A2019 version of Automation Anywhere University.

Use the standard guideline that Automation Anywhere provided. Build a dry model for each bot. This will be useful for debugging. I give these diagrams to my developers.

When automating Citrix, we can install on the client. It can easily access objects, we can click anywhere and it can take data from anywhere.

We have a scenario where one process is working, but in another case, it is not able to capture everything.

This is a good product. This platform is great, but there are a lot of issues to resolve, including the Excel features.

My advice for anybody who is implementing this solution is to follow the instructions and the standards that are specified.

I would rate this solution an eight out of ten.

The primary use case is hard to say. We have used it in a number of different areas in our company. We've used it for HR, IT, and our business partners on the front lines using the application. Therefore, our primary use case is hard to say, but basically what we try to do is automate the drudgery out of our business partners' lives.

We have automated some of our HR applications, where there are certain courses. Because we're in a financial industry, we have to maintain certain certifications, etc. Some of that is automated where we help generate reports back to HR. In some cases, there are some very front-end, which are CSRs. We have processes automated for them so they have a less manual work effort. 

We have worked with our compliance area. Some of the things that we have automated there, because we are a financial industry, are political contributions where we have to be very careful. There are a pay-to-play laws in the US, so we've actually automated, which were very difficult because you had to go to all 50 states to download all the information. Trying to do it manually was probably over 8000 hours a year, and now, we're doing it with automation.

What is important to us is continues improvement and learning. We want everyone to be able to look at what they do with a critical eye towards how can improve and get things better? By introducing the solution and working closely with our business partners every time, we create a bot, then their mindset shifts. 

Now, they are looking at everything else they do, and saying, "Hey, wait a minute. Maybe I can do this in a different way." Whether it's using a bot, some other solution, or sometimes even just improving the process as it is without automation, the company in different parts of organization is really starting to adopt the idea of continuous learning.

Probably ease of use has been its most valuable feature. It's been very easy for us to use. We like to operate in a sort of a federated model. So, when we originally started, it was just our vendor partners who were doing the development. Now, we have our own set of core developers at my company. Since 2017, we now have about 23 different people, most of whom are certified developers, a lot of them didn't have a developer background when we started.

With the user interface, a lot of the parts of it I really like, but there are some things that could be made a little simpler. A little less clicking around here and dragging over there to use.

My impressions of the Bot Store are I really love the idea of it. We've actually downloaded a couple of them and used them. One of the more recent ones was interesting. It required a license key, which kind of confused us. If it's freeware, why do you need a license key? But we got around it.

What has also been nice, with the most recent bot from the Bot Store that we downloaded, it was developed by a vendor partner who we are partners with as well. So, when we had some issues with it, we were just put in contact with the developer at that same firm, then we were able to work through any issues. Subsequently, they have made updates to it and uploaded it back to the Bot Store, so it's actually great.

The stability is pretty good. In all fairness, I know we went from version 10.5, where we thought we were fairly stable, and we did have some issues. Then, we migrated to version 11.2 and encountered some other stability issues around scheduling things. But, after talking with some Automation Anywhere techs who were extremely helpful, we have recently, as of last week, upgraded to version 11.3.2.1, and that seems to have solved some of our problems.

We are still testing it. I still need to do some checkups. Obviously, I'm here this week, so I'm not doing it right now. Generally speaking, it is stable. Knowing what it's trying to do, I think 100 percent stability with everybody will be different. Architecture and environment are going to be pretty difficult, but they do a good job.

The scalability is easy. Installing license keys, bringing up new Bot Runners, and all that stuff from the Automation Anywhere side of it are easy. It's very easy. I've had little-to-no difficulty doing any of that. I have to go through the paperwork of hardware, VDIs, etc, and that's all on our side. But, from an Automation Anywhere standpoint, it's been very quick and easy to scale.

The technical support, from my experience, has been very good. Granted, sometimes there has been a little slowness, but if I deemed it critical, or whatever, then I've had conversations with our customer service manager, or anyone, and they've been able to get me with somebody in architect, which has been phenomenal.

When we did the upgrade to version 11.2, it was sort of complicated, because we had to start all over. We had to bring in new hardware and a new set of new databases, but the gentleman who helped me out was great. He fully documented the process for us, which was awesome, because I didn't have that from the original installs of version 10.5. Because he documented it, I was able to go through the upgrade from versions 11.2 to 11.3 very simply and fast. I would say the technical support is very good.

Why did we want to invest in an RPA solution? This was our first solution, so we weren't with someone else first. We did do some evaluation, looking at how and what we wanted to do with bots. Did we want to just use it purely on the back-end? Did we want to use it on the front-end? 

Some of the leaders at the time in the strategy and innovation team at our company just saw the need for it. We knew there was a lot of manual redundant processes that were just right for automation, so we said, "Hey, let's bring it on." The PoC sort of proved the concept, then we just brought it in-house and kept going from there.

The initial setup was somewhere right in the middle. It wasn't super simple. We could've probably done things a little better than we did, but it also wasn't horribly complex.

We used an integrator and reseller for the deployment, originally. We worked with HCL Technologies, but we found some gaps in our knowledge because of this. We didn't fully understand the architecture and how it was built. 

During all the process of the installs, we didn't get all the documentation. This made some things a little difficult for us, especially when we ended up parting ways with HCL. 

Then, we signed with a different vendor for both development and reselling, OPTIMIX. So, going through with the Automation Anywhere architects and getting it installed was great.

One of the first steps that we do before automating anything is we determine if it is a process where there is enough ROI involved to dedicate development resources or a bot to? Sometimes, in all honesty, the use case is we want to learn something, so we do it anyway. But, generally, we do a time and motion study, so we understand how much time we are saving somebody. We measure that. Additionally, we measure cost. That varies depending on the department that we're doing the automation for. But, we can measure that, and usually that is a straight hourly rate times the time saved.

Cost avoidance is something that we do, too. In other words, there was a process that we automated where a department was considering hiring someone just to do some file transfers and copies, etc. We automated that process, and they just didn't have to hire somebody.

It definitely saves us a lot of time and money.

It looks like it will be right around $115,000, not counting IQ Bot, which we won't renew until later.

We looked at Blue Prism and UiPath, but we felt that Automation Anywhere was a good mix of both the front-end and back-end, whereas UiPath seems very front-end only and Blue Prism is very back end only. We needed a mix for what we wanted to do.

We don't use it as attended as much. We have had a few cases where we were going to use attended, then just decided that for the rarity of those types of uses that we didn't want to have a Bot Runner just sitting and waiting for someone to chime in five times a day. Instead, we've created more scheduled. Right now, all of our bots are running unattended.

It's really easy to use. Again, going back to something that I mentioned earlier, we have a number of people at our firm who are now certified RPA developers that had no development background. They did that just by the online training in some cases. In some cases, it was the online training, as well as a three day class that we brought in-house and had taught. However, the only part where you want to get experience and learning are around error handling.

I've been in software for a long time. I've never seen a perfect piece of software, yet. I've seen some that are very good. With everything this is trying to do and the complexities of the environment, I'm going to give it an eight (out of ten) because it's very good. I think me giving something an eight is pretty high in this space.