We are not using the AI tools from Automation Anywhere, but we have created some of our own modules, which we are triggering in combination with Automation Anywhere in Python scripting language. We are using this combination for text analysis and problem descriptions from our customers. We are getting the sentiment score to categorize these service requests so that our agents can handle them better. We will, for sure, investigate if we can use Automation Anywhere's AI capabilities in the future.
I am responsible for showing and teaching new joiners how to work with Automation Anywhere. We also have some new citizen developers. We have asked different departments if they have some people on their team who are interested in this. They are not professional developers like me, but I teach them the basics. I also recommend they join the citizen developer training provided by the Automation Anywhere University. They take that training first, and then we do in-depth training tailored to the RICOH processes. It takes them three to six months, but it also depends on how much time they can spend on the training because they also have their regular work.
If you start using Automation Anywhere I highly recommend the Automation Anywhere University platform to start with the learning trails.
These are focused on three roles: Automation Lead, Automation Developer and Citizen Developer.
Also, great content on the Skill Boosters which will give you in depth training on a particular topic.
To scale your automation journey, good practice is building central tasks like “switching a responsibility” in Oracle with proper error handling that not every developer needs to implement these by his own. With these generic central tasks, it will also save time in terms of maintenance.
For any questions you might have, you can ask them in the Pathfinder Community where you get answers from Automation Anywhere’s global community of Pathfinders.
For companies starting new process automation implementation, I would advise not to tackle the largest processes at the beginning. Start with small ones to track benefits and demonstrate to the board what process automation has achieved in a short time. In the past, we tackled larger problems first and spent one or two years getting them to work end to end as expected. This was not the best strategy.
I would rate Automation Anywhere an eight out of ten.