Automation Anywhere (AA) Review

The Bot Store has helped tremendously with accelerating integration from other applications


What is our primary use case?

The primary use cases are for card and HR automation.

How has it helped my organization?

For our interorganizational processes, it has automated some of those processes.

The Bot Store has helped tremendously with accelerating integration from other applications. Especially with Workday, which is one of the main applications that we look to integrate.

What is most valuable?

It automates forms for our customers and our analysts.

What needs improvement?

They could improve around continuous integration, e.g., Jenkins and GitHub, stating how you could use those products and integrating them into Automation Anywhere. This is one area that we need to see more improvement on. We had to learn a lot of this on our own, as it is unavailable and not documented. I would like for them to be more verbose in putting this in the documentation.

In the next release, we would like to see more error handling functions for the bots, the ability to kill an errant bot, and have more visibility into a lot of the process flows going on in a more automated fashion.

There is a lot guesswork in areas.

What do I think about the scalability of the solution?

The initial pilot was for two processes, which took us about four months. Then, the other processes were more extensive, so that took longer, only because we needed to do more with the process documentation, not so much in the bot creation. It just depends upon the complexity of the process, but also how well-documented your processes are.

How are customer service and technical support?

The technical support is good, but I would like to see improvement with the documentation. 

Which solution did I use previously and why did I switch?

We did not previously use another solution.

How was the initial setup?

The initial setup was complex, only because of the process that was selected. That took us longer than usual, because it had a lot of cognitive decisions in it. Part of our new process is to evaluate if a process should be automated or not, and does it have more repetitive tasks than a lot of decision making. This has greatly increased how we are able to put a process into play for bot creation.

What about the implementation team?

We leveraged a third-party, as far as our bot creation, initially. That is how we did it. We have worked with partners to create bots.

What was our ROI?

Before the automation, it used to take about two to three hours. Now, with automation, it takes about 40 minutes. We measure ROI with time.

Which other solutions did I evaluate?

We also evaluated UiPath.

What other advice do I have?

Take into account your processes. As part of the automation journey, don't look at just the technology part. This is where a lot of people make a mistake. They focus so much on the technology that they forget about "process" of RPA. They need to take a longer look at this and break down the process at its task level to see if it is worth going the RPA route. Once you do this, look at the vendors to see which one provides more in the way of bot creation and scalability, especially if you are in a cloud environment. Then, with the continuous integration, you will need to have a lot of this as you are putting things into production from development.

For ease of use, version 11.3 was an improvement compared to version 10.5. I am looking forward to seeing what 2019 provides for developers.

I would rate version 10.5 as a six out of ten and version 11.3 as an eight out of ten. I would rate version 11.3 higher because there have been changes made to how the bot creation is now done, the interfaces, the ability to utilize the VDI environment, and multitenancy.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email