Automation Anywhere Reviews

Automation Anywhere is used by our customers for automation support.

Developers can easily utilize Automation Anywhere. For individuals with no prior knowledge, there is a university website available for training, and I also provide assistance in training my customers.

Automation Anywhere has a short learning curve. It takes five days to train new users.

We have seen the benefits of Automation Anywhere right from the start.

Automation Anywhere ability to provide automation at scale is good.

Automation Anywhere can quickly and easily integrate with RPA bots, APIs, and business applications.

It has helped our organization increase automation consumption.

The dashboards are excellent.

The regional distribution in Turkey can be improved.

I have been using Automation Anywhere for six years.

We have two customers who use Automation Anywhere on the cloud and two customers who use it on-premises.

Automation Anywhere is highly stable.

Scaling Automation Anywhere on-premises is difficult, but in the cloud, it becomes easier.

The technical support team is extremely responsive.

Positive

The initial setup is straightforward. The deployment can be completed by one person within an hour.

The implementation is completed in-house.

The cost of Automation Anywhere is high in Turkey due to the weak economy.

I rate Automation Anywhere a ten out of ten. I recommend Automation Anywhere to others.

APIs are easy to connect, and I highly recommend integrating APIs over robot process automation.

Automation Anywhere is easy to maintain and update.

We maintain 50 bots, and each of them requires five minutes to install.

We're using Automation Anywhere (AA) for the financial departments of a lot of civil engineering companies here in Greece. There's also one pharmaceutical company that uses it in their financial department.

I find Automation Anywhere (AA) to be really fast on the development side. They are also using a good engine. They have an efficient and intelligent system, e.g. it's IBM's, so it's one of the best. The connectors in Automation Anywhere (AA) are also good, and they're working fine. These are all the features I found most valuable in the tool.

One area for improvement in Automation Anywhere (AA) is its monitoring system. It's not that good.

The scalability of the tool also needs improvement, because when you set up another machine to run the process, the system would become full.

We've been using Automation Anywhere (AA) for three years.

My impression on the stability of Automation Anywhere (AA) is that there's still room for improvement there. A lot of times during the day, one or two out of 20 cases lose their elements, or lose a window, and that should be improved.

The scalability of Automation Anywhere (AA) needs to be improved.

Setting up Automation Anywhere (AA) was not that hard, but I can't say that it was easy. I don't know if I did something wrong in the configuration when I first installed the tool. You have to configure the database yourself, and I believe that the tool should configure itself.

Licensing for Automation Anywhere (AA) is paid on a yearly basis. Out of all the RPA tools, it has the most value for money, e.g. what you pay is what you get.

On a scale of one to five, with one being cheap and five being expensive, I'm rating the price of Automation Anywhere (AA) a three. It's not as expensive, but it's not that cheap, too. If you'll use it long term, then it's better, but the company that you're selling it to, they have to trust you, and you should also have knowledge about the sales.

We're now using version 16 of Automation Anywhere (AA), and that is the latest version. Previously, I was able to use version 11.

I have not contacted the technical support team for Automation Anywhere (AA), because we are partners with IBM who are partners of Automation Anywhere (AA), so I'm working with IBM and talking with IBM support, instead of the support team for the tool.

If somebody wanted to use Automation Anywhere (AA) for the first time, the advice I would give that person is that it's the only tool that's easy to learn in terms of how to develop, but you have to read the manual about the monitoring system and the control room, especially about the control room, because it's really complicated. I found the control room complicated.

Overall, I'm rating Automation Anywhere (AA) eight out of ten. I'm giving it an eight, just because of the cases that you are losing according to the spying or monitoring system. You're losing a lot, and your customer is not really happy about that.

I've used Automation Anywhere RPA as one of the RPA platforms to automate business processes within the company. It started as attended automation initially and then moved to unattended mode. We're using the on-prem version with Runners on virtual desktop. 

We have used/are using the AA360 Platform for automating the business processes in HR, Finance, and telecom operations.  

IQBOT is also used for purchase order processing to capture the semi-structured data and process it in ERPs to achieve straight-through processing of these documents.

Implementation of Automation Anywhere (AA) allows us to automate business processes and has brought productivity gains, error reduction, and speed of execution in multiple HR and Finance operations. 

This automation has also helped in achieving better compliance and standardization of the processes. A number of processes were able to be digitalized 100% without much human interaction required. The only exceptions are managed by humans although the RPA bots are doing the majority of the work. 

Implementation of IQBOT has helped in capturing the semi-structure data from pdfs and doing the straight-through processing of these documents.

Web-based ID for development is helping developers to use any machine (laptop, VDI, etc.) to access the environment and develop it.

Enabling collaborative development where multiple developers can work together is great.

The flow view is helping us to view the overall flow of the activities and is helping the functional review faster without jumping to the code level, ensuring all the exceptions are handled accordingly and there are no exceptions that are not handled.

The addition of multiple drag and drop functions in the development of IDE helps ease the development work.

Queue management is still missing from the latest version which is a barrier to using the platform to start implementing complex cases where you have parent and child transactions going through multiple stages.

Without queue management, it is not possible to manage the multiple-step work item processing. For example, task automation instead of process automation is where hands-off is required in between the workflow steps.  

Simplification in managing multiple environments for dev, test, and production would be useful.

There needs to be more stability in the platforms.

I've been using Autoamtion anywhere for the last five years. I've used a different version and now have migrated to AA 360 for the last year.

The stability is an improvement area for the product. We still have issues sometimes where bots hang up.

It's a scalable solution. We didn't face any issue in that regard.

There is good technical support available from the AA team.

Positive

We started with AA for more attended automation.

The setup is a bit complex and was done by the AA team.

We implemented the solution using an internal team and external partner.

We say an ROI after six to nine months.

The solution is cost-effective in comparison to others. However, you need to pay for the control room for each environment. You also need developer licenses and even runners are required for test and pre-production environments.

We evaluated UiPath.

Parts of Automation Anywhere (AA) that we are using include IQ BOT, RPA products, and a human in the loop attended Bots as well.

Automation Anywhere (AA) is useful for our customers.

Automation Anywhere IQ Bot is very strong in comparison to other vendors because Automation introduced this intelligent document processing product a long time ago, which is one of its unique features. 

When compared to UiPath and Blue Prism, the rest of the products are the same. They are distinct in comparison to the IQ Bot, but other than that, they share many of the same features as other products.

Automation Anywhere has a uniqueness with respect to the IQ Bot.

There is room for improvement; with the overall architecture as it is tightly coupled. Everything is coupled with the Control Room of the overall product architecture.

When I look at the UiPath product, where they have a mostly combined architecture and development environments. It should be more loosely coupled, but both products have advantages and disadvantages. 

The overall product in Automation Anywhere is good, but they need to improve a little bit on the overall architecture side.

Integrations should be included with the analytics platforms and third-party SAP, enterprise-level applications, as well as if there are any built-in connectors where you can connect with the ERPs to automate the required teams. 

There are ready-made connectors available, which will help to democratize automation across the enterprise with various customers across the globe.

They should include integration with not only analytics but also analytics and enterprise applications, as well as advanced AI/ML features. It's not just about the IdP; some AI/ML features should be available. Aside from computer vision, NLP, NLU, and NLG, as well as a variety of other advanced features, should be included.

I have been working with Automation Anywhere (AA) for six years.

For the last two years, Automation Anywhere (AA) has been deployed on the cloud, and prior to that, it was on-premises.

There are several versions of Automation Anywhere. They have version 11, as well as Automation 360 and Enterprise 360.

Version 11 is considered stable. You will also notice that Automation 360 is attempting to stabilize the overall product.

The scalability of Automation Anywhere's cloud version is excellent, but the on-premise version is a waste of time and money.

I'm familiar with both Automation Anywhere (AA) and UiPath.

Initial setup, after cloud, is fine. It was complicated earlier, but it's fine now. When you sign up for a cloud subscription, then it's plug and play, but it's a little more complicated in the case of on-premises.

I compared Automation Anywhere to UiPath and Blue Prism.

We are resale local partners.

I would rate Automation Anywhere (AA) an eight out of ten.

Here's a use case of Automation Anywhere (AA): In a bank, you have an account opening process. The customers go into the bank, then apply for account opening. They will go to a portal, fill out the form, then put their documents. All the data that had been entered and all the documents that are being uploaded will go into a document repository.

With Automation Anywhere (AA), you have a data capture solution that extracts the data, and will put the data extracted into a case management solution, instead of having somebody just taking data and doing manual data entry into the CRM platform or core banking platform. This solution can take the data extracted from the upload, log into the CRM platform, and key in the data one after the other, in that same order on the CRM or the core banking platform, instead of having a human doing that repetitive task of data entry. You can use this RPA solution to handle the document repository, extract the data from it, log into the CRM portal automatically, then key in the data as an automated data entry into the CRM.

There are other competitive solutions, e.g. Blue Prism and IBM Robotic Process Automation (RPA), and those are very good ones, but if you asked me, Automation Anywhere (AA) really, really stands out.

One of the things I like about this solution is its functionality. It's highly functional, aside from it being stable and scalable.

I also like that the Automation Anywhere (AA) team is always innovating, e.g. they're always coming up with new features that would speak to various operational use cases.

Improving on the ease of use and user experience of Automation Anywhere (AA) could help.

We've been providing Automation Anywhere (AA) to our customers for 10 years now.

Automation Anywhere (AA) is a stable solution.

Automation Anywhere (AA) is scalable. It's one of the best you can have in the market.

Automation Anywhere (AA) has very good technical support.

Installing Automation Anywhere (AA) is not a complicated process. How long the installation takes will depend on the client environment. For the cloud version of this solution, you just need to configure it to the use cases of the customers. For the on-premises version, you have to set it up within the client data center environment, and even that doesn't take time. Installation is straightforward.

Our customers pay for the Automation Anywhere (AA) license yearly, for the cloud version.

We were able to evaluate Blue Prism and IBM RPA.

We currently have three customers using Automation Anywhere (AA). We have three people handling the deployment and maintenance of this solution: the system administrator, the developer, and the solution architect.

The advice I would give to other people who want to start using Automation Anywhere (AA) is that the most important thing is for them to understand their use cases before even embarking on the journey, so they can be sure their use cases are RPA related and can be taken cared of by this solution. Automation Anywhere (AA) cannot cater to all automation use cases, as it's mainly focused on clearly defined manual repetitive tasks.

The customers can decide whether they want to have this solution deployed on cloud or on-premises.

I'll give Automation Anywhere (AA) a rating of eight out of ten.

We are currently using Automation Anywhere for a Master Card customer complaint bot that will log tickets on our top priority websites. When customers complain it can be logged directly or the agent logs it on one of our databases. The bot goes to the database and can pick up the ticket that was logged on a top priority website. It then becomes a role ID number to us for verification that has been locked properly. Third parties can take notes, then once locked, they can give the ticket to us.

We did this procedure manually before the use of Automation Anywhere.

Automation Anywhere is very simple to use. The features are very simple and the application light. Overall I love it.

I have been using Automation Anywhere(AA) for approximately five months.

Automation Anywhere is a very stable solution.

The scalability of Automation Anywhere is perfect.

I am the only one using the solution. However, I am going to create a team that can use it optimally.

The challenge we face is the response time of the Automation Anywhere support teams. They could be quicker to give support. However, the problem could be because of the time difference. When we do get in contact with the support their knowledge is very good.

I have used other BPM solutions previously, such as Optimus.

We decided to take processes away from Optimus and we now are using Automation Anywhere.

The initial implementation of Automation Anywhere regarding the elastic search and database set connection can be a little difficult. However, I am skilled enough to get through it. There were some balancing issues that my other team members had to manage. They are having difficulty in balancing when I checked the architecture properly. We determined later that there was no need for a load balance to be done on the servers. We didn't do any load balancing and then the elastic search was not done.

The first time we did the implementation took us some time because we had to set up the server based on the minimum server requirements that were sent to us. Then we had some load balancing issues which took some days because we did not have all the knowledge.

If we had all the information we would have been able to do it faster. When we were applying the certification to the servers it was a different approach because it's a Java-based solution. In the first instance, we had a challenge doing the implementation. After the initial problems were resolved I did not have any problems implementing Automation Anywhere. It took approximately two hours to get it all done.

The deployments only need approximately five to ten people.

We don't have a lot of processes. If we want to expand we can change the license to allow it. Currently our license, we can only have 10,000 bots, on all processes. If we have approximately 10,000 bot processes on the control we'll be able to manage the processes in the control room. Five and ten people should be able to manage 10,000 bots.

There is an annual license to use the solution.

I would recommend this solution to any organization or individual.

I rate Automation Anywhere an eight 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.

We are currently working on a vendor bill reconciliation process. It is in production now. We are also working on an incident management process for customer service. Within the customer services, there are four or five different processes that we are working on. All of them are incident management but for different categories at different levels. The next use case that we will be working on is bank reconciliation, and then we are planning to expand into HR for onboarding and recruitment. These are unattended robots. 

We are able to integrate it with other products through APIs, which we may not have thought about. For example, there are some in-house solutions that we have for which we have built APIs, and we're able to integrate those APIs with Automation Anywhere. We didn't expect that we'll be working on that but it happened.

The ease of use for the end user and the very low complexity in trying to build a bot are the big factors for us. We are able to work on a project, identify a use case, come up with a design spec, and execute and build a bot within a span of six to eight weeks. In nine to ten weeks, we are able to go live, which reduced complexity. Once we go live, the user interface and the user experience are extremely good.

Their bot runners could be made to handle multiple payloads at the same time because if I want to run multiple parallel operations, the number of bot runners that I have to buy just keeps increasing. It is adding to the cost. However, there is a possibility that we don't need that many bot runners, and we can run multiple operations in a bot runner. This would be a great addition to have.

I have been using this solution for six months.

You get what you paid for. What it says on the tin is what you'll get inside. As a customer, you will not be disappointed. If you're thinking that you want to build rockets using Automation Anywhere, then you will be disappointed. As long as you know your business needs, the automation that you want to focus on, and you understand the product's functionalities in a good way, you will not be disappointed.

Scalability depends on how many parallel processes you want to run. A bot runner basically runs a bot. How many bots can it run? How many of these need to run in serial? How many of these need to run in parallel? This information will determine how much you have to scale. Now, if you're willing to pay a lot of money and have multiple bot runners, that means for each and every bot runner, you can have multiple processes running at the same time. So, if you are willing to pay, yes, you can scale. It depends on your budget. The product works whether you're on 1 bot or 20 bots. The product just goes off and does its thing. That's not a problem.

If it is 1 bot that you're running once a day at 10:00 in the morning, then you need one bot runner. If you have 20 processes that you're automating and these 20 things have to run throughout the day at different points in time at 10:00, 12:00, or 2:00, you can still run them with one bot runner. In those use cases, scalability is not a problem. Scalability becomes an issue when you have multiple processes. If a reconciliation process needs to run along with the general ledger balancing, month-end closing, and everything else, and all of them need to run at the same time, then you're looking at about 10 bot runners running 10 different bots at the same time. If you're willing to pay, you can get what you want, but it becomes a very expensive affair.

We have 15 to 20 people who are touching the application for various purposes. We have business analysts, developers, testers, and the external implementation team. We also have business users.

I have used both UiPath and BluePrism in my previous organizations. Automation Anywhere gives me the flexibility for both on-prem and SaaS, and the difference is not huge for me in terms of performance, security, and all that stuff. It gives me the flexibility, but honestly, on paper, all these three products pretty much do the same. There is a plus or minus 5% difference here or there, but you'll not go wrong with any of these products.

The initial setup was very straightforward. There are specific things that they ask in terms of the environments that we need to build in our typical Windows server, that is, what kind of memory and what kind of processing capability we require. I can't talk from the SaaS perspective because we have an on-prem deployment, but giving on-prem equipment based on the defined specs is pretty much child's play. There is nothing complex about it. It is very easy for developers who understand the platform. You can quickly roll out something and get it live, but you need to understand a lot of logic and the complexity behind the applications such as ServiceNow, Workday, Salesforce, etc. 

We started off with an implementation partner, and our experience with them was good. They had about three people in their team, and we had our business people who were giving the requirements. We also had our technology people who were basically acting as the bridge between our business people and their developers.

We are expecting a significant ROI by the end of the year. 

From a business angle, understand what is it that you need. Where do you see inefficiencies? If you're going to fix inefficiencies that are going to be fixed as part of a larger company-wide transformation program, then use the transformation program and fix those inefficiencies as part of the existing solution. If you think that that larger transformation program is not going to touch some places or if that larger transformation program will touch some of these inefficient areas but not in the near future, and you want some immediate wins, then going in for an RPA tool is a good decision.

At the end of the day, the business needs to be aligned with why you're making the decision, and where and what is your priority? What is your sense of urgency with respect to the places where you're implementing it. For example, in my office, we are working on customer service. There is a massive transformation program going on right now, but that transformation program is touching sales, marketing, finance, and all those areas. It is not touching customer service at all, but customer service has its own inefficiencies. So, we introduced automation in customer service because it's not being touched by the transformation program, and we don't want to keep waiting to gain the ROI of whatever we can get or the reduced cost we'll get from customer service. For example, if I'm going to implement a massive cloud ERP like Oracle or SAP, then I will fix the process as part of that cloud ERP implementation and not wait for a bot to be developed.

From a technical perspective or an integration perspective, use an API to directly communicate between the apps, if you can. You don't need a bot or an RPA to do what an API can do.

I would rate Automation Anywhere an eight out of ten.