Automation Anywhere Reviews

As a financial services company, we have a variety of use cases for different areas of our business, as well as some of our IT partners. We have automations that help perform payment extensions on customer accounts. We have automations that track email communications on accounts that are in collections. For our IT partners, we have bots that perform password resets for applications that our IT team supports, as well as the provisioning automations that we use to grant access or change access for team members at our company.

They have been informative in terms of new features, components, and capabilities that are available to us as their customer. We have a regular cadence set up with our account manager and our support manager to ensure that we are able to leverage some of those new components. We have had the opportunity to test or play around with some of the new features being rolled out to see if it is something that we would be able to introduce into any of our use cases at GM Financial.

During the development and the discovery phase for the use cases, while walking through a use case with the process owner, we were able to identify some opportunities that could have helped them before the process was automated. By seeing where they were struggling with manually performing the process and automating the process, we have been able to give them a lot of time back with the use of some of the features.

It is fairly easy to understand. The courses that Automation Anywhere University offers, especially for citizen development, and even for those who are getting into development, have pretty simple course content. It is not overly complex or too technical where somebody could get lost in the instruction. It is fairly easy for anybody who does not have that technical background to pick up and use. If anything, it would probably give them an opportunity in terms of what background they want to understand more to supplement or complement what they learn from Automation Anywhere University.

For a first-time user of Automation Anywhere, there is not a huge learning curve. The content and the instructions through Automation Anywhere University are comprehensible. It is easy for somebody to practice, learn, and build on top of what they have learned. As different use cases come around, there are different opportunities to use some of the different features or variables in development. It will help strengthen how they learn or map out how to use the tool.

We have dependent environments that our automation will log into or interact with. There are applications that our automations interact with or are integrated with. We have automations that are using Salesforce and SharePoint. We have an FIS platform for automations servicing customer accounts. We have various applications and third-party websites that our automations interact with daily.

We have automated processes that were heavy with human interaction. Through automation, we have been able to allow those human resources to be reallocated to other areas of the company, doing different processes manually. These automations are working daily beyond normal business hours, on weekends and holidays. Business partners that are benefiting from the automations have been able to distribute those resources to other areas.

Automation Anywhere has most definitely saved us time and costs through automation. Our business partners are able to receive the benefits of automation and distribute those human resources to other areas of their business. By saving time and costs associated with those human resources, less overtime is being paid. Especially for processes that are dependent and have time-sensitive SLAs, we are not accruing any penalties or anything like that. We are able to leverage automation to avoid those costs. It is not only from a time and cost perspective but also risk avoidance. Risk avoidance is something that is not necessarily highlighted when it comes to automation, but I feel that we have also been able to avoid risk.

We are looking at the different programs that Automation Anywhere offers. We are engaged with our account manager on Pathfinder, and we are able to leverage the ability to map where our program currently is and where we want it to go. We are putting some key ideas, thoughts, and time frames around where we want to be when it comes to building our automation program at GM Financial.

Right now, when I look at the platform for Automation Anywhere, the ease of use for the control room from a production support standpoint for our L1 and L2 team members has been amazing. With our conversion from v11 to A360, there has been better ease of development of components within the control room for our development teams. Obviously, it is apples to oranges, but the experience since going to A360 has been amazing. We have been able to establish some reasonable components, which has made our delivery efforts a lot easier since we have been in A360. From a support perspective, the ease of use with the control room and being able to manage those devices in the control room has been easy for us as well. 

If I look across the use cases that we have, there is more opportunity for us to collaborate with Automation Anywhere to see or maybe explore some potential opportunities for new capabilities within the platform. Off the top of my head, I cannot think of anything that they would need to improve on, but there are probably opportunities to explore some potential use cases where maybe there is a feature that is not yet available. We can discover and pioneer something together.

At GM Financial, our journey began in January of 2020. I have been supporting the development team that has been building bots in Automation Anywhere since 2020.

On a scale of one to ten, I would rate my experience with the support of Automation Anywhere a ten.

They are very responsive when our platform admins or our developers need to open up any cases. We have a weekly support cadence with them as well as an account cadence with them. In the different areas that we receive support from Automation Anywhere, they are very responsive and very attentive to our needs.

Positive

When we started our RPA journey in 2018, we had a third party. It was outsourced to a third party that had a proprietary tool. We managed to do that for a few years, but being able to host, support, and build internally was a key factor for us. When the company decided to look at possible solutions to deliver these services, Automation Anywhere was what they selected. When we moved to A360, we took those automations that were hosted externally and brought them into our portfolio as well.

Deploying Automation Anywhere was definitely a learning experience for us, especially when we stood up the platform and tried to understand the deployment flow internally for the team. Our platform admins who do the actual deployment got their system before the support team that helps with the checklist of activities before the deployment takes place. That is where we had to learn and set up our framework to get it deployed.

Prior to actual automation deployments and getting the environment set up, we had to work with our infrastructure team. We had to make sure that we had the right resources in place and that those resources were working adequately before we launched our first automation onto the platform. Internally, we learned some lessons along the way. That is a part of the course for anybody who is deploying a new solution in their infrastructure. Overall, it did help us learn the importance of having a good framework in place so that if we need to build, expand, or change anything, we would be able to accommodate that appropriately.

We have most definitely seen an ROI internally with our development and production support teams. Even our business partners are receiving that return on investment because we have been able to help them realize the benefits that they are getting by automating their business processes. That return is not only to the IT team; that return is tenfold to the business.

I am not engaged in that portion of it; my leader is, which is good because then I do not have to have many discussions.

During the exploration phase for finding the tool for GM Financial, we looked at other tools like UiPath. I believe Blue Prism was another one that was being evaluated. Automation Anywhere was also in the mix. They were also trying to determine if they wanted to continue to host externally, but all in all, Automation Anywhere was where they went.

We are starting to get into an Automation Co-Pilot use case where we can showcase or pilot that with the business. One of the things with technology is that it is a journey, especially for an older financial services company like GM Financial. It involves adapting, understanding, and educating on new technologies and features. Before we can deploy things, we have to prove them. We have to show them. We have to help them understand what the benefit of using it is going to be. We are getting ready to pilot our first co-pilot using Automation Anywhere, and that is for our customer service or customer experience department.

My favorite aspect of the Imagine event is the opportunity to network and also to see Automation Anywhere showcase any new capabilities and enablements that are available to Automation Anywhere customers. At the keynote session yesterday, it was really nice to see how somebody is recognizing that a lot of times, departments within IT are siloed. They are working through challenges to be more collaborative and engaging to improve the services that we deliver when it comes to automation. Learning and hearing those things and listening to different breakout sessions confirms that we are not alone on our journey when it comes to our RPA program and other things because Automation Anywhere is not just RPA. It is good to know that we are not alone, and it is good to network with people who are experiencing the same challenges or opportunities that we have. All the information and the networking are my favorite things of all the Imagine conferences.

The Imagine experience is fun. It is exciting just because of the fact that we all have these opportunities within our grasp. It is just how we choose to go after it or how we choose to engage. There is the excitement of brainstorming or sharing ideas with people across different companies or services. You feed on that energy, take it back home, and work with your teams to continue to deliver and support.

Three reasons that I would highlight for colleagues and fellow team members to come to an Imagine event are:

• The content that Automation Anywhere shares about upcoming enablement and capabilities that are going to be made available to them.
• The information shared and networking is done with people from other companies across the globe.
• The events in breakout sessions are hosted at different times during the day.

I would rate Automation Anywhere a ten out of ten. I have not had any negative experiences with Automation Anywhere.

I am the manager of our intelligent automation COE within HR. We operate in a federated model. I lead the HR team, and there are similar teams that exist across the company in five or six other areas.

We have plenty of use cases within HR specifically. We have automation for candidate-facing opportunities before people join the company. We especially have a lot of automation opportunities for our recruiting. The human capital management platform that we use is an SAP product. We use SAP SuccessFactors, so naturally, a lot of our automation opportunities come through that platform. There are a lot of emails and notifications to managers for talent management, talent acquisition, and all the way through to payroll, or anything that falls underneath the HR function. Nothing is off limits, and we have pretty much touched most of the functional areas within the department.

In terms of comparing the processes and tasks automated using Automation Anywhere versus how they were done prior to implementation, a lot of the processes had remained the same, especially in the early years. A lot of people were leveraging RPA platforms to recreate processes the way a human was doing them, so the look and feel were very similar to how a human was doing a process, going across applications over the UI, whereas now, there is a heavy focus on process improvement. A lot of people are leaning into process improvement or re-engineering a process before it is automated and making sure that we are automating the right thing. 

It allows for more reliable dynamic automations if you can leverage something out of the UI. You can leverage a database or an API versus automating something similar to how a human would click through a screen. There is definitely a heavy emphasis on design requirements or completely changing a process from a functional perspective, which takes a lot of work, but your automation is easier to create and maintain in the long run.

Before Automation Anywhere, I have used other RPA platforms. From comparing it to others, it is very intuitive. I do not have a development background, but I lead a team of developers. I am trying to manage and teach them how to use the tool as well. I find that it comes across as very easy to use. I have seen a handful of new developers pick it up within a couple of days. They are able to understand the UI and create their first couple of automations within a few weeks and then they get running with very complex things within the first year. It is very intuitive to use. There are definitely a lot more capabilities coming out, but it is all within the same platform. If you know how to go through the platform, they make it very easy to deploy technical solutions.

Automation Anywhere is one of the easier platforms to learn. There are a lot of online resources, and they also have a community forum. If there is not a video on how to do something explicitly and you have a question, in their developer community, people are quick to respond. You can also simply Google something or look at their website, and you will be able to find an answer for it. Especially after you go through the first couple of days of their university's online training through the community version or get your hands on automation, it clicks pretty quickly. When you see it once and learn everything that is in the platform, everything comes pretty quickly after that, so the learning curve is pretty shallow. 

In terms of the tools that are integrated with Automation Anywhere, we are doing a lot of work within ServiceNow. I just became aware they have a thing called Connector Builder, which basically allows us to build connections right there within Automation Anywhere with ServiceNow. There are other integrations with SAP or Active Directory right there in the developer's toolkit so that they can build automations with it. This makes integrating with your system of records or whatever systems you are automating a lot easier.

We have not done any integrations with document automation. That is a big use case that we are looking at. I know intelligent document processing has come a long way, so I am very interested to see how seamless that integration works out. In terms of being able to integrate and leverage any of our SaaS platforms or on-prem applications that we are automating, we have not seen any limitations to it. We have been able to automate everything. Being able to use API task paths or just expose more endpoints from an API perspective makes the developers' lives a lot easier. It is technically a little bit harder, but if you are able to use APIs, then integrating that way will alleviate future maintenance for automation. It is definitely useful to have that in the platform.

Automation Anywhere has had a big impact on the business. I can speak mostly from an HR perspective. All of our automations that are currently running in production save about 2 million dollars annually, both from a cost savings and cost avoidance perspective. Certain things have a dollar amount. There is a dollar amount associated with a transaction that we can automate, and then we can also inject that time back into our employees' days. Freeing up that capacity allows them to go use their human decision-making skills on more advanced and complex projects and allows automations to do that manual, repetitive, and mundane work. Hours-wise, I do not have a metric, but we are able to save 2 million dollars with our portfolio. We are continuing to add new automations, which makes that number go up and up. 

In terms of time savings, it has been super helpful. We are able to give employees their time back.

We have not had any issues with scalability. Everything from our licensing structure and being able to deploy bots across the enterprise is pretty efficient. Being able to get the most out of our bot runners and start looking at bot performance and utilization across those machines has enabled us to get the most out of it. We are able to deploy everything that at least HR needs right now. I know some of the other companies or departments might need more bot runners to keep up with that scalability. When it comes to end-to-end automation and working across COEs in a federated model, that is a different story. We have not tackled that yet, but in terms of being able to deliver work for HR at our company, Automation Anywhere has been a huge help, and there were no issues in terms of getting the job done.

Automation Anywhere offers a lot of programs to get involved. I recently became involved in their MVP, the Most Valuable Pathfinder program. That is a smaller group in the Pathfinder community that allows us to see early access to what is coming and things that will be showcased at Imagine or the products clubs. We sometimes will be able to get early access to dev environments to go poke around and see what is coming. That helps leadership also see what is coming and be able to make a decision on whether or not to buy new features or capabilities. It gives us a little bit more time to go out to our business stakeholders and the people we are automating processes for and say that there is a use case here. Could we apply some new technologies? 

Four or five years ago, we looked at everything in terms of whether we could automate a functional process, but now, there is a lot more coming with Generative AI and intelligent document processing. There are product clubs and community forums to see how others are leveraging the same tools. It is super helpful to see how other people are applying the same technology. It may spark some interest throughout our company.

The most valuable feature of the platform right now for us is just getting the most out of the tool. When I first joined the company, we were on version 11, which is the on-premise version of Automation Anywhere. Getting over to the new cloud platform A360 has enabled us to get the most out of general RPA or robotic process automation. There are plenty more tools that we are looking at, but just being able to automate functional processes, whether through the UI or APIs, to alleviate that manual work from the department has been really our bread and butter. That is where we see a lot of the value for the company right now.

From a platform perspective, our model has been getting operational data back out to our automation owners. We are a pretty small team. We have about 70 automations in production. Everything that we automate, we naturally own a fraction of that just from a technical perspective. Having a team of developers, you want them focused on building new things. We are at an inflection point where we have automated so much that just keeping the lights on certainly takes 20% to 50% of the time, depending on the time of year. Being able to enable the stakeholders is one of my main focuses. If we are automating their process, I want them to continue owning that as much as possible. We are just expanding on the bot insights. From a security perspective, there have been some challenges for us getting our customers in there from a role-level security perspective and making sure that they have full access to the control room and their automation after it is automated. Being able to manage a digital worker has been a big focus. That is what I am looking to get the most out of the tool right now.

I have been in automation for about seven years now. This is my second or third year with Automation Anywhere, specifically. I just went over my two-year mark. This is the beginning of the third year using the platform.

The stability of Automation Anywhere is fantastic. The platform itself is very reliable. Automation, in general, can be finicky sometimes, and it will break. That is business as usual, but in terms of the platform, reliability, and uptime, it is good. If there are patches, by being on the cloud, we get them faster. Fixes and new features are constantly available to us. We have no complaints there. It has been a great journey.

I have not had any issues being able to deploy solutions for all of HR. The platform has everything to offer that we would need to automate for our company.

Their customer support is very good. There are very few times when we have to go out and open up a ticket, but every time we do, we get very timely support. We seem to be getting connected to the same reps, which is super helpful to build that relationship. If we cannot find a knowledge article or something online, they point us in the right direction or let us know if there is a patch or something else coming that will fix it for us.

I have used a competitor. I worked with UiPath for about four years before Automation Anywhere. There are a lot of similarities in terms of conceptual robotic process automation and similar trends in terms of intelligent document processing, process mining, and task mining. I am sure they all have features around Generative AI.

It was deployed before I joined. In terms of the deployment model, it is probably fully on the cloud, but I am not too sure. When I joined two years ago, we were on version 11 on-prem. One of the biggest things I had to do was migrate us from version 11 to the cloud version.

Even if we do not automate anything and just keep the automations that we have running, that is going to save around 2 million dollars year over year for our HR group. Continuing to expand into new automations will drive higher ROI. So, year over year, even if we do not continue to automate anything, those savings and those hours continually go back into the business.

I do not have any experience with pricing and licensing. We have an admin team and IT team that handles a lot of the infrastructure and technology, so I would not be able to speak too much about that.

Automation Anywhere was evaluated before I joined my current company, so I cannot speak much about that. I know they worked with an implementation partner, and that Automation Anywhere was obviously the chosen one.

We do not use Automation Co-Pilot. It is definitely one of the items or features that I am very interested in. I was excited to get my hands on it during the bot games today at the Imagine event and see how it works. You can give it a string of text, and it will generate code for you right there in the control room. That is super helpful. I am looking to see how my developers react to that as well. I am sure that would save some time from the developer aspect. There is another aspect for business users. I certainly think there are some use cases there that they would be interested in looking at.

My favorite aspect of the Imagine event has been connecting with everyone in person. I work remotely, so it is nice to see people in person. We get to sit in a room and do the bot games again. We get to see some cool new features and everything around Generative AI. I do not hear the term RPA so much. The big focus in the world is Generative AI. There are a lot of keynotes, and we are able to see how people are starting to apply it early. There is a lot of excitement. It is an exciting time, and I am very interested to see how we will be able to leverage Automation Anywhere with the new technologies.

The Imagine experience is energetic. The world of Gen AI feels like a bit of a playground. It is generating a lot of buzz all the way up at our executive level, and I am sure it is the same for a lot of people. I see the wheels spinning for everyone. There are ideas, and it is good to see everyone saying to start small. It felt a little bit daunting how we are going to apply this, but it is nice to see everyone reiterating the same thing, "It is coming, and you have to be careful. Start small, and it is a journey." It is nice. It is a good pivot.

If I were to invite people to the Imagine event, I would say that it feels like a tight-knit community. There are probably a couple of thousand people here. Seeing familiar faces and being able to meet everyone and talk about some of the same struggles that we might be seeing is good. We get to know how others are thinking through it. Being able to see the new technologies is awesome. That was one of the main reasons I wanted to come. It forces you to take a look at what is coming next and how others are applying it and start thinking so that you can make a decision on where you can help your customers with it.

I would rate Automation Anywhere a solid eight out of ten. It is not perfect. There are probably a couple of little things, but being with the tool for two years, I have seen so much being changed. It is a playground. There are plenty of features and capabilities. We are just scratching the surface, so I am excited to see what is next. It is very good.

We have varied use cases and have worked in different business areas. Customer service is one of our biggest business areas, along with investments and finance. We also have some risk compliance, legal, and HR use cases involving about 50 different applications.

Automation Anywhere has freed people's time and effort to do more useful things. Some smaller teams have a lot to work on during the holidays. The solution has improved error reduction and work-life balance. It was all the more useful during COVID-19 when we worked from home for four years. RPA was a godsend. People could do things more easily. We continue to grow our program through this year because of the benefits it provides.

We really like all the features of the solution. The solution's most valuable feature is its ease of use. In 2018, we assessed four different products available on the market. We chose Automation Anywhere because it seemed to be the easiest and most intuitive to use for non-technical people. That has always been our model. We are a very citizen developer-focused organization in terms of RPA and intelligent automation.

The integration of Automation Anywhere with our business applications is excellent. We haven't yet encountered an application with which it doesn't integrate. That's the point of Automation Anywhere or RPA. You use the applications as is. It sits as a bridge or a layer on top of your existing application and does a fabulous job.

We have integrated very few use cases into our workflow. We hope to do that a bit more with attended automation and Copilot. We have no complaints so far regarding documents, but we hope to do a little more with that. From what I've heard, you have a lot more API integrations available now than before. We would like to assess them and use them.

Automation Anywhere has definitely improved work-life balance and error reduction. Our audit and compliance team regularly advocates for the RPA team. They reach out to different business areas when they're auditing them. They are absolutely one of our biggest advocates. We have seen an overall improvement in employee morale with the various benefits we have gotten apart from the obvious time-saving.

The biggest metric that we use is annualized automated hours. I think we have saved about 50,000 annualized hours. In addition, we have saved another 50,000 hours for automated monitoring where people aren't needed. It has saved us a lot of time.

Automation Anywhere is excellent at providing automation at scale.

Through my sessions yesterday, I'm absolutely very interested in the benchmarking process that comes as a part of the Pathfinder program. We are also hoping to use Copilot very, very soon.

We haven't used Professional Service Accelerators yet because of how our program is structured. We started five years ago. We do everything in-house, including training and development. Our citizen developer program is quite robust. We have been able to do all our migrations and development ourselves.

My favorite aspect of the Imagine event is connecting with many different people. I've been coming to the Imagine event since 2019. Every time I come here, listening to all the keynote speakers on the first day makes me realize that the world is moving at such a fast pace, and we are so behind.

You meet people and realize that these are all possibilities and opportunities for us to be a part of this revolution. It's amazing, and it always feels great to come to the Imagine event.

The most important part of the Imagine event is the people. We have worked with Automation Anywhere all the time. We have worked with excellent people, whether it's the customer success team, the accounts team, or all the leaders at Automation Anywhere. It is wonderful to meet all of these people and hear and see what their vision is and what their thoughts are.

The highlight of every Imagine event is all the products and services that are coming in the near future that we could use or leverage. It's really exciting. It's just me this time, but we usually have more people at Imagine. People are generally very excited to come and be part of it.

With Automation Anywhere or RPA, the way we automate things now is different from traditional automation. The focus of our organization has been to help nontechnical business people automate their own processes. It makes it so much easier for them to learn to automate their own work as opposed to traditional automation, which was mainly done by IT.

It is extremely easy for business users who do not have technical skills to use Automation Anywhere. We use the Automation Anywhere training. We train our own citizen developers within the organization, but the training program is based on what Automation Anywhere provided us at the beginning.

While we have to teach business users how to use basic technical things, we also have to teach technical people how to approach business and business processes. That's a part of our training program. Apart from that, it's very intuitive and straightforward. It's equivalent to a six-month-old who can operate an iPhone.

We take our cues for the solution's learning curve from the Automation Anywhere initial training. We think it takes about six weeks for people to learn to use Automation Anywhere effectively, and we build that into our training program. We cover the basics in week one. We take a use case and work with that in week two. People continue working on their use cases in the third, fourth, and fifth weeks.

In week six, we target to put the use cases into production and cover more advanced topics. We have continued collaboration with our developers to learn new skills. I think six weeks is the amount of time needed for people to be comfortable using the tool on their own for their own use cases.

On our platform, we have about 50 other applications integrated with Automation Anywhere. We have expanded our program from RPA to intelligent automation. Intelligent document processing, Alteryx, Power Automate, and Automation Anywhere actually work hand in hand. While Automation Anywhere is still our main automation orchestration program, we integrate these other automating applications along with it.

I could personally use automated testing, which we currently do not have in Automation Anywhere. When we looked at the document processing IQ Bot, it didn't work for our documents. Since I haven't looked at it recently, I don't know if it needs improvement now. I'm sure the current version is much better.

We started using Automation Anywhere at the end of 2018, so, it's been five years and counting.

We have no complaints about the solution's technical support. I rate the entire customer success team a solid 11 out of 10. That's my comparison scale. Over the last five years, we have had five customer success managers, and all of them have been excellent. They had different personalities and different ways of working, but all of them were excellent. The last four are personal friends now.

Positive

We started seeing a return on investment after the first year and a half of using Automation Anywhere. The growth has been a little bit slow but steady during the time we were all working from home, but I'm hoping for it to grow again over the next 12 months. We'll probably have bigger and better stories to share at the next Imagine event.

I think the solution's pricing is reasonable. Setup cost is what you expect in the industry so far, and the licensing is at par. However, I like the ease of licensing and the flexibility in scaling up or down. We have done that over the last few years. I am looking forward to moving to the cloud between now and the end of August. That will change the licensing model a little bit.

We do not have Dev Stage licenses. From what I understand, it's going to be a pool that we pull out of. It'll be different, but I think it'll give us more flexibility.

We did not use a different RPA solution before using this. We assessed four different products, starting at the end of 2017 through 2018, and realized that Automation Anywhere is the best fit for us. We still think the same because it works great, and we have no reason to complain. We haven't had the need for any other product just yet.

For our current setup, Automation Anywhere is set up on a private cloud on-premises. However, we are working to move to the Automation Anywhere cloud. We are assessing and going through the initial steps. We hope to be on the Automation Anywhere cloud by the end of this year.

Overall, I rate the solution ten out of ten.

Most of our automation happens on Automation Anywhere. 

While the automation is being done, we use it as a platform. Then, depending on the number of users/ bots needed, we apply  for the corresponding licenses.

The good thing about Automation Anywhere is that any process:

1. Which is repetitive, rule-based, and only requires you to do collect/ edit information on the application frontend can be automated. 

Therefore, Automation Anywhere makes for a good use case. 

2.Wherever the process is  deterministic, with no decisions to be made, you can use it. 

It can automate any processes where 

3. Process is well established, standard, or stable, and there are not many changes in the process. For example, a simple task, such as logging into a website, launching a website and doing systematic steps on the website, can easily be captured to Automation Anywhere.  I see lot of applications, especially in finance and accounting domain.

You might have a lot of steps where you need to either extract data, repeat data, or collect data. All of those processes can be automated through RPA, and especially Automation Anywhere. You can use even automation from the server side, not just websites. The only constraint is that the process should not require human intervention and decision making.

We see the application in the 

# BPO space, 

# Finance and accounting, 

# Health care in terms of claim processing.

E.g. in F&A, if you're doing invoice processing where the entire process is manual, and the analyst has to go through the invoice to determine invoice details, discount on the payment  or a penalty should be levied. In such cases, you can scan this information through an OCR, which is an optical character recognition tool. Then, the rest of the information can be pretty much retrieved by the RPA, which means the RPA will scan the information to classify this information and fill up the  web form. This will be sent to the ERP. This is how the workflow would look like. 

Wherever you can put

# a rule-based system, you can automate all of the processes. In our company, all these processes are manual and you might have 50 to 60 people supporting this process for a mid-size company. You can automate it and reduce the manual effort by almost 40 to 50 percent, depending upon how many techs are enrolled and what is the effort being spent in order to process transaction volumes.

I have been familiar with a couple of projects where this was implemented in cash applications or invoice processing, and they could automate these steps. So, I'm familiar with some of the back-end processes and where they are getting automated.

#1.You don't have to really code anything, as it gives you a good interface (UI), because the components are already preconfigured, you  have to just a drag and drop sequence in terms of how you want to execute the steps. 

#2. There are preconfigured APIs that can be used. E.g., if you want to interact with the mailbox solution, you can have the RPA fetch attachments or email body from the mail solution. You can process attachments via test file or PDF. You can even make Automation Anywhere work around PDF, which is typically not that easy to work with in terms of extracting information.

#3. Metabots/ IQ Bots: One of the features, which we have not used too much, but available, is the MetaBot feature. These preconfigured solutions are easily downloadable, and you can just plug-and-play with a bit of customization, which also means you do not have to keep recreating and can reuse existing functionality. Some of the typical uses are that you could be regularly logging into a website. You can just download a MetaBot, as a useful webpage interface and just run it. All you have to do is maybe replace the name of the website, and in case there is a certain authentication mechanism that is being used, then provide that information.

# 4.There are multiple levels of cloning. In case screen cloning doesn't work, you can do object-based cloning or keystroke-level cloning, depending upon what parameters are available to you and what is the level of information that you capture. You can traverse between object cloning, which is the lowest, most basic form of cloning to a stroke-based cloning, which is like taking care of each keystroke-level which is made by the agent.

#1 Exception Management and Notification: When you are making a code, and there is a happy path and exception management mechanism, it would be nice if there was feedback in terms of whether this is the most appropriate way to code this. I'm not sure how this can be done, but that could be very insightful. It already gives you some screen tips, but this could be done in a better fashion, in case you are creating the workflow and then you believe a beta workflow is available or could be done. If a screen tip could be given to the coder for this sort of workflow, this would be a much better feature for Automation Anywhere. 

# 2 Type of Cloning: I've realized that sometimes when screen-level cloning is a better option, people still use object-based cloning. It would be useful if Automation Anyone could give you tips recommending fewer steps or fewer areas of exception management after you inputted your code. I'm not really sure if this is doable from a technical standpoint.

#3 Debugging: Currently, I believe the debugging of bot is a bit tricky and not very elegant, you might have to keep re-running the script to be able to identify the bug. This can be looked at, as a possible area of improvement. 

#4 Scheduling:There are two modules: the run module and the control center. In terms of scheduling and triggering, they could make it a bit more helpful and provide suggestions, e.g., if you are scheduling it, and there is a conflict, can you resolve it this way. Maybe you can get an upfront alert or something to that effect. 

#5: Stability, Workaround and fall back mechanism: When  bot breaks down, is there any of mechanisms or notifications that can be given? You can possibly choose to notify people, typically in organizations people are pretty much adverse to automation. If something breaks down, they would like to know at the earliest given opportunity that something is breaking down and piling up. They want to be able to resolve it quickly. If the resolution is going to take time, they want to be able to make some specific workaround mechanism kick in. If a bot breaks down, immediately the fallback mechanism should work too. If there could be information in terms of  when the process was out of range and somebody might need to take a look at what has happened. This is because most of these business processes that get automated are critical in nature and might have financial and operational impact. People need to know that there are working fine and not broken down. It can really have an adverse impact if they break down and nobody knows.

#6. Platform Training: My experience has been that if the person who codes the bot is not very well-trained, then they might create unstable bots. So, it's not the platform. It is just how somebody has coded the bots which can bring in lot of instability to them. I recommend that when you are using a coder that the person well-trained and have a good amount of experience already working on bots. They shouldn't be newbie or beginner who comes in to code because that will impact the quality of the code itself.

I have been working with Automation Anywhere for the last three years at two different companies.

# Business process stability: Before robotic automation, the business process itself should be stable and very well-documented. Also, anytime a change is made to the process or subprocess ensure, that the RPA gets updated too. Typically, the entire process of automation might take some time, then by that time, the initial business process might have changed a bit. There could variations in terms of volume or in the process itself.

The most important thing is that before you automate something that you must make sure that it is stable, in its steady state for whatever changes might be upcoming over the next six month to year. Otherwise, you might create a bot, which will go into production,  and fail because the underlying process itself has changed.

# Monitoring and controllership: If there is no changes in the process, bots are pretty much stable and especially, if they have been well coded. In case there have been any changes anywhere in the process or subprocess, the bot can fail. This means you must have a review mechanism with monitoring in place. Once you put a bot into production, you have to monitor it and do regular sanity checks. Otherwise, you could have situations where bots have failed and you might not know, then the process comes to a standstill. In a nutshell monitoring and control is an important aspect of RPA in the run phase.

Scalability is just scaling up the number of bots, so scalability is not a problem. You can increase the number of machines and number of bots to scale up the solution, but it can be sometimes very cost prohibitive. E.g., typically, it requires a dedicated machine, and it can't be a shared environment. This can be a bit of a constraint in terms of the number of machines being used. Otherwise, the solution is completely scalable. In case the process requires more throughput, you can just increase the number of bots which are working. Also, if you are doing this properly, then you have to make sure that there are not multiple bots running at the same time which might be at cross purposes.

I don't interact with the people from Automation Anywhere.

# Procurement of the license is easy, but depending upon what you want to automate and how you automate it that might take time. Setup is not at all difficult. You just take the license and install the application, then it's ready to go. However, in terms of what you're trying to automate, how you're trying to automate it, and the complexity of the problem, the entire automation process can take time.

# Implementation timelines:The time frame to implement depends on the complexities and number of the processes and subprocesses. In a typical process, the coding, testing, and deployment could range from a week to four weeks. However, I have seen it sometimes take longer because you have to continuously keep checking and testing it. Every time the code breaks down, you have to possibly start from the beginning.

My experience has been one to four weeks as the ideal time frame. However, depending on how well the process was understood and documented, there can be certain gaps which would only become evident during the testing phase, not otherwise.

# Resources: Depending on the number of bots that you have to create and the number of the complex processes along with the given budget and timelines that you have in mind, the number of developers range from one to multiple developers. The resources that you really need are developers because they are people who will be coding. Otherwise, from an ownership standpoint, we need some subject-matter expertise for the process. The people who are subject-matter experts will be needed on a part-time basis for the developer to be able to map the process well and be able to create their technical design. Then, you will need a technical master who creates the technical documentation of how it will be coded. The number of technical masters again depends upon the processes and complexity along with the corresponding number of developers.

The deployment team may not be very big. You need just the developers and a design architect, mostly two people. All the other people come and go per the requirement stage of the deployment. There might be people who are there only for consultation. Some people might be there only to approve the solution. Whenever you bring in automation, it has to be reviewed, monitored, and assessed from the organization's standpoint. There might be people who are just doing approvals for this process deployment in case it's a very complex project, and then there is a project manager. Otherwise, sometimes the technical design person doubles up as a project manager too.

Before implementing, you do the assessment of why the organization wants to automate:

Imperatives for Robotic Automation 

• What do they want to automate? 
• What are the key objectives  the organization wants to achieve through robotic automation? 
• Is it a process optimization or is it cost cutting? 
• Who is driving the automation? Is it client-driven or is it vendor-driven? 

Then, you have to build the business case in terms of what you want to try to automate. E.g., how much can actually be automated? That assessment should be done. Even the cost and time of automation versus that benefits that you're going to get out of it needs to be done.

# Process Degeneration: When we start automating, we do a process desegregation. This means whatever processes are under scope that we try and understand the task level, activity level, and precedence details. We make activity diagrams, then try and assess out of all of these which one can be automated. So, if the automation index is pretty high, which means that most of the process can be automated, e.g., up to 80 percent, then it might make a better business case than if the automobility is only say 30 to 40 percent. Then, the cost of automation might be way higher.

# Setting the right expectations with the client: t is also important to set the right expectations with the organization. Are they new to automation or do they some prior experience with automation? Because this helps us set the right expectations in terms of the benefits which can be had. The customer might also want to understand what are the impacts if automation fails and the fallback mechanisms. For example:

• How do you mitigate or remediate the impact of automation failure? 
• What is a criticality of the process you're automating? 
• What are your points of failure and choke points? 
• What are your backup plans if things aren't going well?

The most important thing is the business case as to the cost versus the benefits of automation.

# Legal and Compliance Regulations: Also, are any legal or compliance regulations which are applicable because technically it might be feasible to automate, but legally or from a compliance point of view, it might not be good idea to automate. You might want to still have human intervention in terms of verification and validation.

# Criticality of the process: From a financial impact standpoint, things that require a bit of background investigation might be better kept as a manual process or require a human approval rather than automating it completely.

It all depends on the scale. In one project that I have worked on, we had a savings of $200,000 over a three-year period and a payback period of 6 months. The typical ratio is that one bot will replace two people.

# Licensing: One of the components of key drivers for us to renew our contract is AI or automation. As an organization, we are moving toward smarter operations.

Our pricing a year ago was $600 per license, but I am not sure of our current licensing cost.

# Set up cost: Additional costs will be for the machines and the number of machines that you are using. You can deploy virtually as well as on physical machines. In both the situations, you do need to allocate a certain budget for securing the machines and where the software will be installed and running. 

# Dedicated Machines: The machines cannot be used for anything else, because only a certain bot can run at a certain time. You need to be very particular about your scheduling of running the bots, and while the bot is running nobody can use the machine. You cannot have an agent working on a machine and the bot running in the background. The machine  has to be completely dedicated. 

# Network Bandwidth and Disk Space: Then there are the network bandwidth requirements and  disk space requirements, which are additional costs apart from the licensing and software costs. The developer is also going to charge you for their coding time too.

There are two or three more tools in the market such as Blue Prism, UI Path, but I think the preference was given to Automation Anywhere.

I have only worked with Automation Anywhere.

Understand why you are choosing Automation Anywhere, as the platforms are pretty on the same level except for certain functionalities. Also, in some scenarios, one platform could be better than another. Pick a platform and stick with it.

It is easy to use, but I realize that the effectiveness of the platform depends on the coder and how he is doing the coding. This is my experience, because I have seen that the quality of the automation is as good as the person who is using it. In Automation Anywhere, the skill set of the coder really determines how good the automation is, which is why I am making it a eight (out of 10), not 10 (out of 10). Because while the platform is feature-rich and easy to use, it is the skill of the coder that determines how well the platform is leveraged.

I' am now mainly driving AI at my company. RPA has become a bit secondary in the sense that it is a part of my solution, but most of the time, it is AI-driven. RPA sort of helps in the execution of some of the components of that overall solution. From the organization's standpoint, automation is already a part of all our solutions. E.g., our organization is moving toward automation where almost 30 percent of any deal will be allocated to automation. It will be a ratio of 70:30, where out of $100, a total of $30 dollars will be allocated toward automation and AI.

I did my certification on version 10.4.

Automation Anywhere is an RPA tool we use to automate common workflows that interact with various enterprise applications. These workflows can involve tasks like data generation, sending emails, or completing transactions within those enterprise systems.

We implemented Automation Anywhere to automate our workflows and save time.

In the past, these tasks were handled manually, leading to a lot of repetition. Automation Anywhere has eliminated that burden, making these same tasks much easier and significantly faster to complete.

We implemented AI-based automation that combines documents using intelligent document processing. This involved integrating generative AI to automatically create responses based on the data extracted from the documents. This automation streamlines the process and delivers the desired business output to end users.

Automation Anywhere caters to business users with its user-friendly interface, allowing them to build automation with minimal technical expertise. Our large business user community exemplifies this – after a five-day training program with hands-on exercises, they're empowered to independently develop their own automation within three to four days. This highlights the platform's ease of use from a business user perspective.

To ensure our business users can leverage RPA, we provide training through Automation Anywhere University. This platform offers in-depth coverage of both use cases and technical aspects, along with customized training that helps users directly connect their daily tasks to RPA methods. This blended approach has proven to be very effective.

Non-technical users can overcome the learning curve in four to five days.

While Automation Co-Pilot is a strong solution overall and integrates well with web applications, integrating it with legacy systems may require some effort on our part. However, this effort is typically minimal, taking just a few days to achieve successful integration. We're currently testing Automation Co-Pilot and exploring its potential for AI integration, which reinforces our belief in its overall value.

Based on our POCs, we project that Automation Co-Pilot will add value to our projects.

Automation Co-Pilot helps free up our staff's time on projects.

Automation Anywhere's service and customer support are improving. Their management prioritizes strong relationships with customers, evidenced by frequent collaborative meetings. This focus on customer solutions, along with other efforts, contributes to a clear upward trend in their overall support effectiveness. They've been a valuable asset to our organization.

Generative AI has the potential to revolutionize how we implement automation. Our organization sees a significant opportunity to leverage generative AI within the Automation Anywhere landscape. As a bot-focused organization, we have achieved a 30 percent automation feasibility rate. By combining automation with AI, we can achieve a 70 percent rate. This represents the kind of scalability we envision for our organization.

Our organization is expanding its use of Automation Anywhere. We have two main approaches: governance is handled through a dedicated platform integrated with Automation Anywhere, while bot deployment utilizes a separate web platform built with XTML or Java that interacts with Automation Anywhere for bot execution and deployment.

Integrating automation and APIs with Automation Anywhere streamlines workflows significantly. Users save time and effort since most integrations come with clear documentation readily available before the standard setup process, ensuring immediate functionality. Automation Anywhere's documentation serves as the primary resource for all integrations, and users can find most information there. For any remaining questions, support channels are readily available for further assistance.

Automation Anywhere has significantly reduced our operational costs and freed up employee time. With thousands of automated processes running on our platform, we're saving thousands of hours of work every month.  

Automation Anywhere offers a complete suite of development tools to empower developers for various enterprise automation needs. These tools include packages specifically designed for SAP integrations and other commonly used enterprise applications, making them highly efficient for building automation across different use cases within large organizations. Additionally, the web-based nature of the platform adds further value by enabling easy access and collaboration.

Automation Anywhere risks falling behind by focusing solely on Robotic Process Automation when competitors offer more versatile and adaptable solutions that integrate AI for a more intelligent automation experience.

I have been using Automation Anywhere for three years.

Automation Anywhere offers a 99 percent uptime, ensuring a reliable and stable platform for its users.

Automation Anywhere is capable of automation at scale.

The technical support team is knowledgeable and efficient, readily guiding users toward automated solutions. While some complex issues may require additional data validation, they consistently deliver resolutions within established timeframes.

Positive

Getting started is easy - the initial deployment follows standard procedures and can be completed in as little as two days for a simple use case. Complex setups may take up to a month, and the number of personnel required varies from two to ten people depending on the specific needs of each project.

Automation Anywhere falls within a mid-range price point when compared to other RPA tools on the market.

After considering UiPath, Microsoft Power Automate, and Automation Anywhere, we chose Automation Anywhere due to its ability to handle growth in our automation needs and its strong data security measures.

I would rate Automation Anywhere nine out of ten.

Upgrading Automation Anywhere can be challenging, especially when migrating from a client-server architecture to Microsoft's. However, within the Microsoft architecture itself, upgrades are significantly smoother and can be completed within a four to five-hour downtime window.

While Automation Anywhere itself doesn't require application-specific maintenance, we still need to perform regular maintenance on the server it's running on. One person is enough for the maintenance.

The time to maintain bots varies depending on their purpose but typically ranges from one to four days on average. 

Automation Anywhere is best suited for enterprise-level deployments due to its robust features. However, for smaller-scale needs, other options might be more efficient. If you're dealing with a large organization, Automation Anywhere is a strong choice. I recommend trying it to experience its microservice architecture, which allows for scalability and agility, as well as its integrated AI capabilities. These features provide a powerful and user-friendly platform for automating tasks.

We have many use cases for Automation Anywhere including HR and finance processes, and for the code in our production.

Before implementing Automation Anywhere we had complex data that was huge. For example, with the insurance, banking, and health sector domains. We were able to solve this problem with Automation Anywhere.

As a partner and system integrator, we have access to a vast database of applications. However, there is no direct connection between the upstream and downstream systems, resulting in scattered data across these applications. Automation Anywhere is effectively connecting all the applications, providing a seamless end-to-end workflow that has helped us.

Moving forward we see opportunities to operationalize AI within our organization. We support 15-plus industries and almost 182 clients across the globe. We have different use cases. One of which is for a client for criminal verification automation. This process is complex because we need to get the information from various systems to authenticate the staff. Another is in the healthcare sector where HIPAA compliance is present. So we ensure that we are not touching the customer data. We are using Automation Co-Pilot to solve some of the problems.

We are talking about a powerful tool in Automation Anywhere. They have been in the industry for 20 years and have learning systems such as IQ Bot, Document Automation, and CoE Manager. We are using this powerful tool and getting the best out of the generative AI. We have used the generative AI to solve complex problems for our clients. In one instance, a project that would have typically taken over a year to complete was successfully delivered within just three days using Automation Anywhere and generative AI. We can also extract data faster including clinical data and audio-enabled data for our clients. Our clients want everything as a package and immediately. Before Automation Anywhere and generative AI this was not possible. Now we can provide a solution to our clients within four to eight hours.

Automation Anywhere uses a GUI which is drag and drop. This means even a nontechnical person can use it. There is no need for a developer. With a subject matter expert, in a logistics or health care process, Automation Anywhere can perform miracles. Automation Anywhere is user-friendly and that has enabled us as a partner to help more customers with their digital transformation. A nontechnical person can be trained to use Automation Anywhere in just five days as long as they have an aptitude to learn.

We have used Co-Pilot to enable the digital gate for one of our banking clients with over 30,000 users.

We have used CoE Manager for one of our large clients which easily provides them with a ROI and allows them to see how the BOT is performing. The CEOs, CFOs, and CROs are all able to see how it is impacting their business much easier. CFOs and CROs are now recommending automation to their organizations for the ROI and the scalability it can offer.

Integrating Co-Pilot is a no-brainer. If we are talking about the day-to-day operations, the digital workforce, having a competitive advantage, and scalability, then we have to implement Co-Pilot. It is mandatory and not optional.

Automation Co-Pilot has saved our clients a lot of time. For example, one of our use cases involved a client with 20,000 users where they used to spend 20 to 30 minutes addressing each user's query. With Automation Co-Pilot that time is now fractions of a second. Having to put customers on hold to check information in multiple systems or not responding to emails can result in unnecessary escalation. With the implementation of Automation Co-Pilot the people that used to work on those things are now happy and no longer stressed out because they can now focus on more meaningful work. Automation Co-Pilot improves the employee and customer experience as well as the overall company benefits from it.

Automation Anywhere product catalog has APIs. The API can integrate with any system in the world. It can be SAP, Oracle, Workday, or any complex core banking application. In the cases where Automation Anywhere is deployed on-premises because the organization is regulated, we can go with Automation Co-Pilot which helps connect internal systems without compromising other aspects of data or privacy. The usage of Automation Anywhere is based on each client's needs and the nature of their business.

I have been an Automation Anywhere partner since 2018 and they are always surprising me. Automation Anywhere is customer-centric and on top of the market demand. Automation Anywhere's document automation solution has a 90 percent accuracy rate with handwritten documents. This is a challenge that no other solution has been able to effectively address.

Co-Pilot is a valuable feature. We have a large client with over 30,000 users. A project that size would normally take two to three years but with Co-Pilot we can solve it in two weeks. Not only is it unbelievable to us as a system integrator but also to our clients. 

Automation Anywhere is a powerful tool. The generative AI, hyper scaler with Google and Amazon gives us the power to solve complex problems.

We have learned a lot about how to leverage more of Automation Anywhere on the NLM side.

Automation Anywhere needs to have more testing tools to improve the testing portion of the solution. That would help us do a lot of testing and move on.

The Process Discovery, CoE Manager, and Data Analytics are only available on the enterprise edition. They should be made available for general use and the community edition as well.

I have been using Automation Anywhere for almost ten years.

We have not required the use of technical support for Automation Anywhere yet. When we use new products such as Automation Co-Pilot, CoE Manager, and Process Discovery we use the support. They have a good concept of Orange and Gold support for the enterprise clients. We can get support in two hours with good response times. We can also find a lot of support from the Automation Anywhere Community.

I would rate Automation Anywhere nine out of ten. As a heavy consumer of Automation Anywhere, I highly recommend the solution to many of our clients. The product catalog is simple and the technology upgrades are frequent.

Automation Anywhere is customer-centric and partner-friendly. As a system integrator, we have a hundred-plus resources across the globe to support almost 182 clients. We prefer Automation Anywhere because of what we get from their partner team,  pre-sales team, and customer support manager team. When we are stuck on something and give them a call, they immediately respond to us. This is why we promote Automation Anywhere the most. Automation Anywhere is coming out with new products every six months that are needed in the market. This also challenges us when we meet our clients to tell them we have something new and ask them to test it. Compared to the old version, the performance has phenomenally improved. Automation Anywhere is also helping with year-over-year return on investment. Product wise it is not overwhelming and it has tools such as Automation Co-Pilot, CoE Manager, and Document Automation. Those are the only tools we need and it is easy to understand, utilize, and integrate with any LLMs. With a click of a button, we can integrate with any tool that is available like ChatGPT, Google, or Azure.

Regarding maintenance, for instance, we automated the statutory complaints process for one of the largest organizations in India, which had 65,000 employees in 2020. They have not required any maintenance since then, except for when the government changed their portal and that process only took us three hours to complete. This is because the process we developed is still functioning effectively. The product is stable, so unless enhancements to the existing portal are necessary, there is no need for maintenance.

When upgrading from V11 to A360 we faced some hiccups initially, and after that, we never encountered any problems. We migrated almost 5,000 bots from V11 to A360. We initially estimated six months to complete the migration but we did it in two months. 99 percent of our clients are using A360 which helps us move faster. We initially had pushback from the clients not to migrate because they were happy with what they were doing. After we demonstrated the benefits of cloud-native architecture, including a 15-fold increase in performance, and conducted a successful proof-of-concept, they were happy to migrate to the cloud.

Migrating from other OEMs to Automation Anywhere is seamless. Two of our clients wanted to migrate from their OEMs to Automation Anywhere and we were able to migrate 1,500 bots in two weeks.

We use it to automate all kinds of business processes. The primary use case is the RPA platform, even though they have the cognitive platform and the analytics platform. We use it for so many different things it's hard to focus on one, but it's automating business processes in our banking system.

We're interfacing a lot with Excel, our ERP systems, some legacy systems, the databases, file folders, text files, CSVs. It's hard to pin down one.

Through the software, we have been able to reduce the time that we spend on manual, repetitive tasks, so that we can focus on activities that add value to the business or to our partners and customers. The most important things are saving time, increasing control, and increasing automation.

If you ask our CFO, I think he would say that the most important thing is that we saved some money, with more efficient operations, etc. But I feel the ability to change from doing non-value-added tasks into work with added value is important.

We have saved the equivalent of about $40,000 to $50,000 by using it, during my time here. That's a lot. We recently did a large migration that saved us a lot of time on things that were going to be done manually. We were able to automate it and we saved around $15,000 to $20,000 on just that migration. That's quite substantial.

One of the features that we have used the most is an action in the Workbench called Object Cloning. We find that very reliable and very useful for implementing different business processes.

In general, the security and role-based access control - credentials security - are also important. We have a high focus on security in the bank. It's obviously a very highly regulated environment, so security is a top priority for us. To be allowed to automate different processes, we need to have a good set of controls around who is allowed to do what, and what credentials people can and can't use. It allows us to manage access to make sure that we have full control.

Other things that I also find very useful are the Bot Store and the Apeople community. If we run into troubles, we can always ask the forum and get an answer. People know if there is a pre-existing bot in the Bot Store that we can use to solve a problem. It's very useful to take advantage of the community. When they launched the Bot Store, it was a unique thing in the RPA market and it is providing tremendous value to a lot of businesses.

Also, their MetaBot tool is a very useful building block. We call it Lego bricks, here in the Nordic region. So if you build a wheel for your car, you don't have to build three more, you just use the same wheel over again. That's very useful and it makes the development phase even quicker. I hear other people talking about how they're spending three months on one process and that's a bit crazy. We deliver new processes every week and we estimate a process should not take a lot more than two weeks. But on average, we're spending two weeks per process, to get from idea to production.

The main things I've found that could be better are small things that can be annoying when you're using them a lot. I would recommend they add a feature where, if you mark the start of an "If" sentence it will highlight the end of the "If" sentence. That would make it easier to get a better overview. The small things are the most important in our day-to-day work with their software. Incremental improvements for a better overview or better user experience would help.

Also, we would like to see more options for merging and un-merging PDFs. More flexibility there would be good. We've figured out ways around this and, using their software, we've been able to do everything we wanted to do. It just took a bit more time to do it. We were on version 10.5 and in their Bot Store they actually had a bot that did exactly what we wanted to do, but it was for Version 11.0.

I find that they are making a lot of improvements that we are able to take advantage of with every release. I can't really think of something large that's missing.

It's been very stable. I can't really put my finger on things that haven't been stable that are under Automation Anywhere's control.

There have been some troubles for us when it comes to doing monthly Windows updates. That always turns off the Bot Runner machines and we have to do a complete, new log-on once a month on those machines. But we are aware of it and it's on our side, not Automation Anywhere's side.

Other than that, the runtime might differ. Sometimes it goes very fast, sometimes it can go a bit slower but I think that's also due to the speed of internet access as well as the computers we're running it on. Some of them have less computing power. We don't have the perfect virtual environment yet, so we're still working on improving that. But we can't blame Automation Anywhere for our having a legacy infrastructure.

In general, it works very well and we're really happy with the stability.

The scalability is good. I think we haven't really used the Bot Farm product yet, but that looks very exciting. We're planning on moving the infrastructure into the cloud and it's then a very interesting prospect to be able to scale up from 100 bots to 1,000 bots with just the click of a button. To my knowledge, it's probably the most scalable RPA software out there. We haven't really met any major challenges when it comes to scaling up, other than our own computers. But that's an in-house problem, not an Automation Anywhere problem.

I've talked to people using other RPA vendors and they have said they face some major issues once they pass 40 automated processes, but we haven't really faced those kinds of challenges. It has been running smoothly.

It's very scalable and it's easy to have control. There is a good audit log in the Control Room. And there is the ability to create your own roles and have strict, role-based access control where you say: This role is able to run this bot on this machine but it's not able to run another bot on the same machine. That's good from a security standpoint.

Technical support is really eager to close tickets as fast as possible, which is good. But as with any support, it can sometimes feel like it's slow because they have to do these standard checks to rule things out. Even though I say I've done them, they have to do them anyway. They have to be able to say, "Okay, this is checked off, this is checked off, this is checked off. Alright, now we can move to the actual issue." It can be a bit slow at the start, but they're always able to resolve our issues.

In general, I'm very happy with it and I can understand why they have to do those checks because if it's a stupid error, it's good to identify that early.

The initial setup is pretty straightforward. I've actually done installations of Automation Anywhere and I have no IT background. I've been able to set it up on a server and some virtual machines and get everything working.

The deployment took some time for us, but that was due to a lack of a good environment on our side. To do a clean install would take some three or four hours to get everything up and running, depending on what kind of machines you have. If you have all the accesses you're supposed to have it can take a very short time. But, if you're installing it in an enterprise environment, it can take longer because you might not have all the accesses. At least for me, coming from the business side, I don't have all the administration accesses that I would need, but that's not Automation Anywhere. Overall, it's pretty straightforward and doesn't take a lot of time.

For our implementation strategy, we started out with a pilot, together with a consulting partner. We automated two processes and created a proposal for an operating model, governance, and a framework. After that, we just tried to pump out new automations as fast as possible to prove the value to upper management. After a while, we got some traction and we went from being just me in 2015 to between 12 and 15 people now. Some of them are not working full-time on it but we have at least 12 full-time employees working on RPA across our organization. We started out in Norway, but now we also have operations in Sweden, Denmark, and Finland, with people working full-time on automation in all of those countries.

All the developers are doing some maintenance. We don't have anyone who is assigned to doing only maintenance because we all find that a bit boring. We share the responsibility among all the developers so that everyone has the chance to do new processes and maintenance when needed.

We have a two-pronged approach there. The processes that are important for business continuity, the business-critical processes, are often maintained proactively. We are notified that a change is coming to the system, so we need to test it out and make a new version that will work when the upgrade of the system is live. So we're proactive in those kinds of processes. Non-business-critical processes are maintained reactively. We try to do it in the most sensible way possible, but there's always room for improvement, obviously.

We put a lot of responsibility on the process owners. They're responsible for notifying the RPA team in case of any changes in the graphic user interface or changes to the process, because of new rules and regulations or any other reason. The process owner or someone in his or her team will always know if there is a change in the user interface or the process.

If there is an error in the code, it is the RPA team's responsibility to fix it and we do most of that ad-hoc, when it happens. We always have some resources available to do those kinds of things and that's taken into account when estimating how long we will spend on creating a new process. We know that something might happen during that week or those weeks, so we add some padding.

In addition to the developers, we have a lot more people using the Control Room to schedule the processes.

So we tried to run fast and then we took a step back and re-evaluated. We built an even better framework, redid the infrastructure, put more thought into the security aspect, and we have industrialized our implementation. We still have some issues when it comes to our operating environment, but that's not Automation Anywhere's fault; that's more in our IT department's hands.

We used Accenture, they're our technology partner in Norway. We had good experiences with them, but I think it could have been better planned on both sides. We were not able to mirror their organization as we should. Ideally, we would have been more self-sufficient after those ten weeks, and it was only by chance that I had the time to be present during all ten weeks, every day, in the project. If we didn't have the people learning how to develop, how to do the business analysis side, and working closely with them, we would have been in some trouble going forward.

The project was a success either way, given where we're at right now. But they should have been a bit clearer on how much time people would need to spend and what was expected of us. It's always better to make the customer self-sufficient.

I think they also proposed a bit too-ambitious operating model with a bit too many people from the get-go. That was not that well received by our management. We're a larger organization right now than what they proposed, but I don't think that our management would ever have accepted or have had the guts to do the leap of faith and say, "Okay, we will have six people working full-time with RPA from today," in 2016. They didn't know the potential and didn't really see that we had that many manual processes.

These are small things. In general, we're happy with what they did. It's just that if I were to point my finger at something that could have been done better, those are the things that could have been done better.

Regarding the number of people involved in the deployment, from Accenture's side there were two developers, two business analysts, and one project leader. On our side, we had a project leader and seven or eight other people, but eventually, it was just me and the project leader who spent our full time on the project, while it was going on. Everyone else was also doing their day-to-day jobs. And with all those people, it was still too few.

We have triple-digit returns, in percentage. I feel it's worth every dollar we paid for it. We have seen a lot of the returns in operations and back office because we had so many manual tasks there.

A good example is a process that we automated where, on that specific process, the return on investment is above 30,000 percent. The total cost of ownership is around $1,000 and the return is something like $400,000 in direct cost savings. And that's still increasing. It's an ad-hoc cleaning job that we're doing, but for every contract we change, we save about half-a-dollar per month, per letter we're sending. It amounts to a lot.

We spent one day creating that process and four days running it so the cost of ownership is really low. Those kinds of processes are unicorns. You won't find them in every business and you have to have the right people and the best ideas. But we were lucky to find that process and, by itself, it has paid for a lot of the license cost.

We just did a round of price comparison on a global scale and found it's so hard to compare the license prices. But, Automation Anywhere, in general, is on the same price level as the other vendors, a bit lower in some cases. 

If we're thinking about the list prices, the Enterprise platform license fee is quite high. If you have five Bot Runner licenses, five bot creator licenses, a Control Room, and an Enterprise License fee, Automation Anywhere is much more expensive than the others. But if you have a global agreement with them, the Enterprise platform fee is shared between all the entities that are using Automation Anywhere. In that scenario, it would be a lot cheaper. The prices are quite okay.

We evaluated Blue Prism at the time.

We did the assessment together with Accenture and I think they actually recommended Blue Prism vs Automation Anywhere. I find that a lot of the consultants in our region are recommending Blue Prism or UiPath because they have generous compensation and incentive packages for the consultants who sell their products. I'm not sure if Accenture would recommend Blue Prism if they didn't have some interest in it. If they were totally agnostic, I'm not sure if they would have done the assessment the same way. But it's hard for me to say.

If I were going to do a new evaluation today, I would evaluate Automation Anywhere vs UiPath, but I would still choose Automation Anywhere. I've seen demos of both Blue Prism and UiPath and I think the basic capabilities are the same - they're all based on the .NET framework and you can kind of do a lot of the same things with them. But when it comes to the scalability, security, etc., I think Automation Anywhere is superior.

Another major factor that played a role in why we chose Automation Anywhere was their prompt replies to any questions or issues.

I'm not sure how this part is with the other main providers, but Automation Anywhere has a really good customer success program. I have a customer success manager that I'm in contact with daily. He helps us elevate our issues to the correct people and makes sure that, if we have any action points that are pending on someone at Automation Anywhere, they are resolved as quickly as possible. The follow-up from Automation Anywhere's side has been fantastic. They give us information about what's in the roadmap and what's to come, and if we need any additional information for our IT teams or our management team - anything to would help us with information - they are available to do calls and presentations.

My advice is to get started and get help. It's very useful to have consultants come in to help you get started. That will kick-start your implementation journey. Also, look at it as a journey. You won't get to an end-state where you will say, "Alright, now I'm done," because you will have to improve your implementation at all times, keep progressing, moving towards AI.

In my opinion, the vendor you choose in the first year is kind of irrelevant. But when you come to a point where you're about to scale up, then it's important to be associated with the best vendors out there. For us, being a customer of Automation Anywhere puts us in a really good place to keep progressing and keep scaling up.

It's important to remember that we are not doing a full integration here, we are doing RPA. It's okay to do 80 percent of a process - the high volumes - and then do all the exceptions manually. You won't necessarily get a good enough return on spending an extra month to do all the exceptions. You want to go live with the volume that represents the 70 or 80 or 90 percent, as soon as possible. Then see if it makes sense to handle all the exceptions, the last ten to 30 percent. It's important for us to be able to deliver fast, as well as securely and controlled, and with the MetaBot and the other tools that we have through Automation Anywhere we are able to do that.

We have automated in excess of 60 processes running on 17 Bot Runners, which are like machines we can operate 24/7. We have 15 bot developers and we are closing in on capacity so we would have to expand the number of licenses soon. 

Our plans for ramping up are about pumping out new processes every other week. We're working Agile with the RPA so we try to do short sprints and deliver something every week. The usage increases every week actually. I'm not sure if we are planning to have even more developers because we don't want to be in a position where people don't have things to do. We would rather have some backlog rather than having to fire five developers.

We are planning to continue on the same pace and ramp up the number of bots, rather than the number of developers. We did a proof of concept last year with Automation Anywhere's IQ Bot which was very successful. We did not, however, have time or resources available to implement that last year. Hopefully, this year we will have time and we will make the purchase of the IQ Bot license and start using their cognitive platform. We're thinking about implementing their analytics platform as well, because that's very useful for keeping track of our progress.

I would rate Automation Anywhere at nine out of ten. There's always room for improvement and, of course, we would want cheaper licenses and would want them to add even more things that we haven't thought about to their product. Still, we're really happy with the software provider that we're using.

I train new analysts and developers how to use Automation Anywhere, so my use cases are rudimentary. We automate many internal processes, such as our monthly reports, employee onboarding, and time cards. On the client side, we focus on finance and accounting use cases, such as order to cash, procure to pay, record to report, etc. I do a lot with revenue ops and revenue cycle automation.

You can create synthetic data to test automation capabilities without using real data. For every RPA delivery lifecycle, you can use synthetic data instead of production-grade data. If you need to beef up your artifacts or documentation, you can use Generative AI to have more complete or comprehensive artifacts as a part of your delivery artifacts.

Document Processing has been a higher priority for our clients this year. Automation Anywhere can meet that need in two areas: FortressIQ transactions and the IQ bot capability.

Automation Anywhere has significantly improved efficiency within my organization. For instance, we reduced the time to enter orders from five to ten minutes to less than a minute in one use case. This has given full-time employees significant time and enabled us to process more orders. We save a ton of time using automation to onboard folks and for our time cards.  

Automation Anywhere's most valuable features include its end-to-end capabilities within a single platform. It offers desktop automation, unattended automation, a recorder for tasks, and advanced IDP capability, which means that I can handle everything from basic cutting and pasting to advanced use cases. With Automation Anywhere, I don't need multiple other tools to automate end-to-end processes. I only need one additional chatbot tool, assuming conversational AI is part of the solution. If I don't have chatbots, all the capabilities are built into the platform.

It's the second-easiest platform we use. Blue Prism is the easiest for non-technical users, but Automation Anywhere is also straightforward. It has a drag-and-drop interface that helps people who have used visual tools and a recorder for rudimentary task automation. If you're not a professional developer and haven't gone through the process yet, it's pretty easy to build a bot without much training.

When I took the training, I did 40 hours of basic and 100 hours of advanced. If I had learned it from scratch, my experience would be different. It was the last platform I learned out of the three. I had Blue Prism and UiPath under my belt before I learned it.

It takes 40 hours to train a non-technical user in basic automation. A process analyst only needs eight hours, but if you use the platform outside of Bot Insight, you need 40 hours to be proficient. 

Automation Anywhere is easy to integrate for all the standard use cases if you have an API. Otherwise, you'll need to build a custom plugin or use computer vision. You can integrate workflows, APIs, business applications, and documents. 

The IQ Bots need more out-of-the-box models to lessen the time required for model training. Their competitors provide more built-in models, which enhance capabilities in document processing.

Automation Anywhere white-labels the Shibumi platform and calls it COE Manager. They could expand on that platform to reduce the development time and manage robots in production. The COE tool could do more. I think that's another place where they can expand their capabilities.

I started using Automation Anywhere in 2019, so I'm on my fourth year.

Stability issues are typically avoidable. Proper infrastructure setup and understanding are crucial for robot processing speeds. Infrastructure is critical, and you must ensure you design these bots to identify all business exceptions In the bot hardening process and the RPA delivery lifecycle. System exceptions are unavoidable, so you need to fix them. But outside of that, there isn't an inherent latency based on legacy software or anything else.

Automation Anywhere’s ability to provide automation at scale is on par with its competitors.

I rate Automation Anywhere eight out of 10. It's on par with competitors, especially if you get the enterprise version. They're a leader in the cloud, with more cloud clients than any of their competitors. 

Positive

I have used UiPath, Blue Prism, and Automation Anywhere. Blue Prism and Automation Anywhere are similarly easy to use. Automation Anywhere comes with all the digital capabilities you need right out of the box. They added those capabilities through acquisitions, but they own them outright. Blue Prism is easier to use but doesn't have all the same features.  They were late to market with their RDA capability, And I would say their IDP capability isn't as accurate, so it's not as highly rated.

Given its web-based architecture, the initial setup is genuinely straightforward. The hardest thing is a hybrid setup because you have to remember the rules for each one. Depending on the web browser, you have to have a certain amount of power and bandwidth at your disposal. I don't know that I would manage the environment myself. I'd rather have hybrid to cloud so that AA could manage the upgrades for me.

 Larger, multi-tenant deployments typically take three to five weeks, while a single device on a VM can be set up in two to three days. When we sell it and do it for infrastructure, we use senior consultants, so it's 1.5 resources. Depending on how complex the configuration is, we may need more senior consultants, but one architect plus a consultant is usually enough to get it done. 

Automation Anywhere requires some maintenance. We provide managed services to our clients for break-fix and business or system exceptions, but Automation Anywhere handles all the upgrades, patches, etc., as long as it's in the cloud. 

 It's difficult to say how much maintenance Automation Anywhere needs because it varies based on your environment. Sometimes, your environment isn't set up correctly, so the service crashes a lot, and you spend a lot of time resetting services and restarting processes.  

It also depends on the configuration and the number of automations. My largest client has 400 automations in production, so it's a full-time job. They say one person can manage that many, but I don't think that's a healthy number. It's more like 140, depending on the SLAs and use cases. An IT resource can fix most system exceptions, but business exceptions require somebody who's at least minimally basic-certified and ideally advanced-certified. 

In other cases, the automation wasn't built with the best practices in mind, so the process will time out and take longer than a human. Many things can cause maintenance and uptime to increase. Ideally, you want to do load management with the bot, so you're sharing the work. You want a utility available if the workload increases or a bot goes down. Lastly, you should ensure enough onboard memory and bandwidth for the automation to run.

The time to value varies depending on the size of your project and its objectives. It takes four to six weeks to produce a viable project if your goal is to prove that you can automate a process in your environment and realize value. Medium-to-large high-value automations might take six to 10 weeks or more. Once you have 10 processes in production, you'll see a return of two to five times the investment.

Complaints are generally about the cost of IQ Bot, which is higher than its competitors. The base model’s pricing is comparable to other platforms with attended, unattended, and IDP capabilities as well.

I rate Automation Anywhere eight out of 10. They're one of the leaders. I don't want to give a bad score, but no one is a 10 because there's always room for improvement. While the market share doesn't reflect it, they're tied for first place, in my opinion. 

I recommend doing the training before you purchase Automation Anywhere so you can understand the terminology, components, capabilities, and best practices. You should also get a partner to help you avoid all the hang-ups and pitfalls of adopting and monetizing new technology. About 70 percent of solo implementations fail.