What is our primary use case?
Our use case is mainly finance related. We've used Automation Anywhere to automate a couple of applications with respect to statement analysis and daily manual processes.
We check if the process is automate-able, meaning there is no human interaction needed, no judgments to be made, etc. If the process is a candidate, we then move forward and start automating. We also look into the systems involved, because some systems have restrictions with respect to automation.
How has it helped my organization?
Overall, we've saved a lot of time. There's a recent process that we automated, which saves around 200 to 300 hours each month, depending on the number of accounts that come in.
What is most valuable?
Automate Anywhere can just mimic what a human does. That is the overall feature I can talk about. With respect to specific features, my main focus is with IQ bots, because they can learn by themselves, which is very helpful in a finance background where we're looking at statements and the like. There's a little bit of coding that you need to do and then you can just start teaching it.
This solution is very easy to use since it's a pseudo-code based language rather than workflows. It's very easy to analyze, especially when it comes to getting back to your code, making changes, or resolving an issue. It's not only the development that you need to look into. You also need to look into the maintenance point of view. You need a little bit of a technological background, but that's really just an add on. Even if you don't have it, you can really mimic a manual process that you're doing for simple use cases, so it really helps.
What needs improvement?
One aspect of the solution that needs improvement is with respect to its stability. There are a lot of issues in the tool. There are a lot of breakdowns. We report these issues to Automation Anywhere and they come back with a fix, but it takes some time. At least the fact that we know those errors up front really helps us to design the code. However, with respect to some features, we've finished designing and then we realize that it's not going to work, so all our effort goes wasted.
What do I think about the stability of the solution?
Stability has yet to get there. There are issues with the tool such as breaking down. When we have the bots run on our local system together, we might need to restart on the second or third day. There are a few limitations, which I'm sure they'll overcome with time, but until then, we have to modify our code to withstand that drawback.
How was the initial setup?
If you have coding background, it's very simple. There will be no effort at all. For a non technical background person, it might seem a little complicated at the start, but with all the drop-downs and pulls for loops and ifs, it gets really easy.
What other advice do I have?
The course is wonderful. The module is really amazing. I tell my peers to take the course. Certification I wouldn't emphasize as much, because the questions asked in the certification versus the module do not sync with each other very well. However, if you finish the module, when you get a use case up front, you will know what feature is best to use. After doing the course, I know all the easiest ways to do stuff. So this course will really help a person.