What is our primary use case?
With my experience on RPA solutions specifically, I have completed projects on Automation Anywhere, and my enterprise company has now moved to Blue Prism; so we are currently using Blue Prism for RPA. I can provide a brief of what we accomplished with Automation Anywhere.
Our use of Automation Anywhere was to handle a test case where a ticket came in each day, possibly overnight. There was a job that we ran specifically on our Linux machines to upload the assumption files, which was a repetitive task. Although we had a script on the Linux box, someone had to come in and process the Jira workflow manually by approving the ticket. The ticket came in from the outsource party with a data set and a zip file. We created a workflow in Automation Anywhere where it would open the web page, access the vault, get access to Jira, and input the Jira credentials. If the ticket was in an approved state, it would start pulling the zip file and download it on the Windows machine. The bot would perform validation checks on the zip file and then open PuTTY on the same Windows machine to obtain the credentials, log into the system, and run the shell script for assumption load, passing the data set coming in from the Jira API. The data set was downloaded to the Linux box. After we obtained the data set, we ran the script execution on Automation Anywhere, which loaded the file on the system. If the validation was approved, it would open the browser again, use the Jira ticket, close it with specific comments that the task was complete, and send a notification to the end user. This was one test case; we had modules for Jira and Linux that consumed most tasks. Different scenarios required changing the scripts for different purposes such as loading assumptions or restarting applications. We scheduled tasks on Automation Anywhere to run daily and check the Jira API, running only if the workflow was open.
What is most valuable?
The initial deployment of Automation Anywhere is user-friendly. If you have self-learning capability, the wizards are self-explanatory, making it not very difficult to navigate. It is a very low-code environment, allowing flexibility to explore based on the project's complexity. Overall, I believe Automation Anywhere is a very user-friendly tool.
In terms of user-friendliness for non-technical users, the wizard is self-explanatory. Non-technical users, such as those involved in Excel automations or HR roles, can handle their tasks easily. Some tutorials available through YouTube can help guide them, and I find that the terminologies used in Automation Anywhere, such as Control Room, are also self-explanatory. Users can simply take an Excel file and run the rules without much difficulty.
What needs improvement?
One thing I dislike about Automation Anywhere is that our process is time-consuming. Since the bot is utilized by that machine and if a long-running task is happening, then another bot may not run and the machine is locked. We had to provision multiple machines to avoid deadlocks. This might be an issue with all RPA solutions, but it could have better handling if an existing lock allowed a second bot to provision and take requests. Because our infrastructure is idle in that case, we must bring up more infrastructure, and if there's a bottleneck, the bot is idle, waiting for the Linux process to complete. This is a challenge we faced, particularly during peak load.
Cost is another concern since we moved to Blue Prism, which is more expensive due to needing more VMs, bots, and capacity, which led us to procure more licensing. While Automation Anywhere was used efficiently and was cloud-based, software installation on Windows VMs was an overhead. Moving to the cloud for a web-based solution would allow for no software requirement on the system, which is a more modern approach compared to installing software on machines that require maintenance and consistent configuration.
One area for improvement would be the licensing, making it more cost-effective. The other issue involves security, particularly with password flags. I faced challenges in troubleshooting when providing passwords through the vault, as I could not secure a valid log to see whether the password was correct or incorrect. Log management could be enhanced, and regarding troubleshooting, since I utilized API calls with Jira and a PuTTY session, tracking failures in one of the processes was difficult. The log management needs to improve to identify the root cause of failures.
Regarding the duration it takes to train non-technical employees on using Automation Anywhere, we provided documentation and instructions. Employees reviewed them along with YouTube or external links to start automation, beginning without needing technical support from our team. There were sessions around it, but I do not believe they required much assistance apart from the provided instructions and tutorial guides.
For how long have I used the solution?
I have used Automation Anywhere on projects throughout my experience with RPA solutions.
What do I think about the stability of the solution?
Concerning stability, while I have not seen substantial lagging, crashing, or downtime, performance could be an issue, especially since our jobs take longer. It might be a performance issue on our system or possibly Automation Anywhere not being lightweight. I do not believe the tool itself is heavy; it primarily acts as an orchestrator while the actual jobs run on the machines. However, the tool does block the VM, hindering the utilization of CPU and memory when the bot runs a job. If another job tries to come in at the same time, it complicates the situation.
What do I think about the scalability of the solution?
Automation Anywhere should be resilient enough to provide automation at scale. I know there is an AI bot that we have not leveraged yet, but it should be efficient for capacity jobs. For example, if I receive multiple tickets for loading assumptions simultaneously, I would not want a single bot to complete the task in six hours. The AI bot could recognize multiple pending jobs and scale up the bots to execute them efficiently in parallel.
One thing I dislike about Automation Anywhere is that our process is time-consuming. Since the bot is utilized by that machine and if a long-running task is happening, then another bot may not run and the machine is locked. We had to provision multiple machines to avoid deadlocks. This might be an issue with all RPA solutions, but it could have better handling if an existing lock allowed a second bot to provision and take requests. Because our infrastructure is idle in that case, we must bring up more infrastructure, and if there is a bottleneck, the bot is idle, waiting for the Linux process to complete. This is a challenge we faced, particularly during peak load.
How are customer service and support?
I have not had to contact technical support personally, as we managed to handle most things independently. Although we experienced Jira API issues, it was not related to the tool itself; we utilized a different token authentication and did not face significant issues.
Which solution did I use previously and why did I switch?
I have used Blue Prism as one of the major RPA giants and an alternative to Automation Anywhere.
When comparing them, I find that Blue Prism has more complexities. It depends on the use case; for a very complex architecture or hardcore coding, Blue Prism is preferable. Otherwise, in a low-coding environment where a developer is not needed, I prefer Automation Anywhere because it enables non-IT users to leverage it effectively.
How was the initial setup?
The initial deployment of Automation Anywhere is user-friendly. If you have self-learning capability, the wizards are self-explanatory, making it not very difficult to navigate. It is a very low-code environment, allowing flexibility to explore based on the project's complexity. Overall, I believe Automation Anywhere is a very user-friendly tool.
What's my experience with pricing, setup cost, and licensing?
Cost is a concern since we moved to Blue Prism, which is more expensive due to needing more VMs, bots, and capacity, which led us to procure more licensing.
Which other solutions did I evaluate?
I have used Blue Prism as one of the major RPA giants and an alternative to Automation Anywhere.
When comparing them, I find that Blue Prism has more complexities. It depends on the use case; for a very complex architecture or hardcore coding, Blue Prism is preferable. Otherwise, in a low-coding environment where a developer is not needed, I prefer Automation Anywhere because it enables non-IT users to leverage it effectively.
What other advice do I have?
As for the overall learning curve for Automation Anywhere, I think it is not difficult. However, when adding more complexity, there is a limitation. In a low-code environment, if you need to incorporate more complex logic, you require a coding environment to run some code against it.
I have not used what is called Automation Co-Pilot, previously known as ARI. However, I have utilized GitHub Co-Pilot and I assume that the Co-Pilot would be a self-learning AI bot. It would learn from inputs and make better decisions with each learning curve, similar to how we use GitHub Co-Pilot, which prompts based on our codebase.
Overall, I would give Automation Anywhere a score of eight. I find that an eight is a fair representation of the experience.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.