Automation Anywhere Reviews

Most of our use cases have to do with Excel reconciliations, data entry or capturing data and entering it into a different portal or reconciling into Excel.

We have a lot of clients who have to track Excel work, or there may be data validation or reconciliation's to be done. In alignment with our primary use and because we are an audit firm, our primary purpose is basically to compare entered data and do data matching or verification. It is best for us to get quick output, and Automation Anywhere has been withstanding our benchmarks for performance. Whenever we have a goal or deadline to meet demands from clients in doing volume processing, it helps us to meet all those projections. We prefer the tool, and we are Automation Anywhere partners. 

The time from the installation to the execution of deployment is not very long, so it is a better solution for us than something else which would not allow us to provide results as quickly.

The most valuable feature would be that it is easy to use. Second, we have flexibility in terms of scalability on our support systems. The functionality of the product enables us in terms of the type of projects we can take and helps in advancing our business prospects.

Alert transition is happening in the Python space and on the front lines of AI and with other tools. You have the opportunity to use different data blending tools and data manipulation tools. It would be good if Automation Anywhere could make more plugins available to use with a greater variety of tools and additional options. I think it would be a better product if it had a greater capability for integration.

Stability-wise and from a security standpoint as well, the tool is very robust. I feel Automation Anywhere is better compared to other automation tools.

This product scales easily. You can just plug-and-play with whatever components you want to use. You can just add in things easily and you can scale it up.

Whenever we are stuck at any point where we don't know something about a feature, we just reach out to the support team. Their ability and knowledge have been very helpful to us.

I was not involved in the decision to adopt Automation Anywhere as that decision was made before I was part of the company. I came in during a phase where we were scaling up on the new deployment. They made the change to Automation Anywhere to more actively adopt the possibilities of automation.

One thing that's very good about the setup is that it is one-click. You just have to click to start the installation and then you configure everything as you go through the installation. One of the best parts of using the product for us is that it is easy to install and configure which fits in our business model.

We are resellers as well as implementation partners and channel partners. So we have been through and are involved in all the phases of implementation and deployment. We are the vendor team.

We have been able to witness a return on the investment. We have had clients where their scope was very broad and we have helped them reach their goals. The ROI that we see is not an instantaneous one because it occurs over time while you build out processes. Here and there you have greater success and the target for return on investment is made up over time.

As far as costs, it depends on your use. We started with a basic department pack, which is over 10K. The additional costs depend on the scale of the engagement and how it pans out. We customize to our needs on the go.

I have worked with Automation Anywhere on nine versions, including the 10.3 and 10.7 versions. It has been improving all along as they make further releases.

Considering that experience, on a scale of one to ten, with one being the worst and ten being the best, I would rate Automation Anywhere somewhere around 8.5. It is one of the market leaders in their market segment. They have obviously proven their success and adaptability to the market enough to be very good at what they do. But I am scoring in terms of flexibility and in being more open-ended towards developer plans and preferences. In order to score nine or ten, they still need to provide more flexibility and integration with other tools and options.

My advice to people who are considering Automation Anywhere as a solution, is that you have to approach a decision from the point of view of what you want to accomplish. You can just go out and pick up a tool, but you have to actually dig into it and work on it. Automation Anywhere is a very good tool because it helps you along the process. The kind of support that you get from the community, as well as the partner enablement team, is encouraging. You can take it step-by-step. There will be some handholding from Automation Anywhere team. Our status as members of the customer success team is in the future. That kind of support and community helps new partners, existing partner, or those who are looking forward to becoming a partner.

We have ITMS (IT Service Management) and there are a lot of support tickets which are coming into that service site. As an enterprise application, there are too many tickets to handle live. This system is being used by service desk employees to enable them to address all the issues that customers are facing which they are tasked to resolve. 

Because the number of tickets is huge, managing those services and change requests is complicated to handle manually. We use Automation Anywhere now to process these tasks wherever it is not necessary to use the API to process the handling of requests.

If, for example, I have an application which does not have an API, but there is one activity where a user may need to be registered in that particular application for it to function, we use Automation Anywhere for that to supply the access. We get the data from the source data and use an Automation Anywhere bot to do the registration of the user into that application. This was being done by the service desk manually in previous instances, now it is automated using Automation Anywhere.

We have had about 300+ live tickets at the end of every month before using Automation Anywhere. We just went live last month using Automation Anywhere bots to take care of processing some issues. The total number of tickets that remain live has come down to around 80 as of the end of this month. It might touch around a hundred at peak times right now. But over a short period of time, maybe around six months, these unresolved issues could become zero at the end of the month. We are just evaluating the numbers from the date when we went live, so it is not so accurate. Definitely, the goal is that the count will become zero, and that is the target. It seems to be working well so far.

The other use cases that we have are open-ended right now. There are a lot of potential uses. For example, if a request comes into the service now to create a VPN account, we can automate that using Automation Anywhere. That work is in progress. Today that is a manual task where the service desk people raise another ticket to another team who will go there and create the VPN accounts. 

We are in the process of identifying certain processes that can be automated through a bot, as there are other services for internal support functions, like HR or IT. We are trying to take some of those services to automate them. In terms of the extensiveness, we have just started with that. We have around 10 new sketches that we have automated right now but we have around 13 to 14 sketches that we wanted to automate through this process.

We are using the on-premise deployment model.

As far as how the product has helped us improve our organization, we may be a bit premature to just to say that it has already decreased the workload. But looking into the decrease in the ticket counts, it suggests that it is helping process customer service requests and that it definitely is going to help us more in the future as we utilize the solution better.

There is one user registration process in one application where there is no API which has been published by that framework. This is a very proprietary in one application by a third-party. So, there was a help desk, and whenever a call went to the help desk, they had a front-end where they created these user registrations. Now, this is completely automated for all employees who are onboarded. We receive the data, it is put it into Excel, and from Excel, it will update it into the particular tool where the registration happens.

On the service desk, they are using ServiceNow with a VPN connection. Now, they are logging using Automation Anywhere as a bot, which logs into a ServiceNow. It will then take that VPN request and create it on the server.

To be very honest, I've not had the opportunity to go through all the features of Automation Anywhere. This feature where it can use a bot to go between a user and into other systems as a robot and do that work is very valuable. It can do whatever humans can do and still provide a level of security. That model is a good one. 

Developers don't have any challenges using it. We are still in the early stages of use, but it is working well. It is very easy to use for our developers.

One of the challenges that I think should be resolved — from what my team was telling me — is that Automation Anywhere is not able to connect to a database directly. I have not evaluated this myself. There may be good security reasons for this, but it should be possible.

For example, generally what we do now is to write scripts to push the data from the database and into the automation event. The direct access feature — which is not available according to my team — could solve the issue with the scripts. There's room for improvement in making more flexible solutions.

As of now, because I have not used the new version very extensively, I don't have any reference to say what features should be added to the next release of the product. My one thought is that I don't know about the possibility of reading from unstructured data and if Automation Anywhere has any features to access unstructured data sources. It would be good if it can read the data and build some intelligence over that to push data to the right application. We do have some requirements from clients in other organizations where invoices will come in to be scanned. Based on the analysis of the data, copies of the data can be sent to different, appropriate applications. We are using different tools to do this now. If this kind of feature for reading unstructured data is there, then it will be easier to incorporate in processes. That is good to add if it is not there already. 

There can be some options to connect to the database directly where we should be able to add some data. 

There was a limitation where we were supposed to login remotely to one server and carry out some actions. That integration was not possible.

In the Indian market, there are a lot of other service companies like us. In the market, there are other products competing with Automation Anywhere like UiPath. My team has technical experts in their technology and these experts also work with Automation Anywhere. When they are comparing the products, they say that the modules or the functionality in UiPath can do a better job overall compared to Automation Anywhere.

From a stability perspective, we run into an interesting issue. Somewhere in the licensing — especially for the Indian market — there should be some different pricing packages. For mid-size companies like us in our market situation, having multiple bots really costs a lot as a percentage of revenue. Instead of adding costs, we are trying to run with one or two bots which run about seven processes in all. It may not be the most efficient or optimal way to get the most from the product. From the cost perspective in the Indian market, if you want to grab the majority of the potential users, you will want to be considerate on the pricing side. A lower price may bring greater market share, user familiarity, and recognition.

Otherwise, stability seems to be good.

From the scalability standpoint, I don't think there will be any issues except for the increased costs which could prohibit some companies on a limited budget from scaling. So technically it is pretty good, but there may be some restrictions or interference in budget or integrations.

We are using one or two bots that are running continuously.

Support wise, I think the company is doing great. When we hired support staff to help us with the installation the support was very good.

Right now, we are just at the beginning of our implementation as far as what we envision it will be in the future. So far the support that we are getting is normal support. It is just okay. When we place a ticket, there is nothing bad, but also there is nothing extraordinary about the support like we were getting during implementation. What we receive now is just a normal support experience compared to the specialist who was very good.

We have not taken Automation Anywhere University courses.

One of the major reasons why we went with Automation Anywhere is that our company could have a global MSA (Master Service Agreement), where we could use this particular tool for our end customers also. As an organization, we had a global implementation with Automation Anywhere where the clients wanted to deliver this solution to the end customer also as part of their solutions. That's why — because that option was there — we just went with Automation Anywhere.

The initial setup for the program was not straightforward. It was definitely complex. As a layman who is unfamiliar with the product, I do not think people can implement it easily. Even people with a little bit of knowledge about the type of robotic engineering and applications are going to go through some challenges where they need help from Automation Anywhere.

So far in this installation, we have had to integrate with some internal processes. Also, we needed to incorporate solutions for the respective firewall openings to the internet. It has taken almost one-and-a-half months to do the basic installation of the software. It is not like pushing a button.

We initially deployed everything on server. However, the permission required Excel to also be a part of our process to be automated. So, we received some complaints on it this. This particular thing cannot be deployed on the server because of the license that we were holding. What I came to know is this feature is not available.

We hired a dedicated person from Automation Anywhere who supported us at the time of the initial installation. Because we were installing this on the cloud infrastructure, we had to go through a lot of challenges. Because we had a dedicated person helping us to do this insulation, it saved us a lot of trouble, experimentation, and effort.

We are still in the process of deploying and evaluating both the solutions and the benefits. However, I definitely think we will see a return on investment. Looking into the number of tickets and seeing that they have decreased now because of some implementation of the solutions we intend to deploy is a good sign. We have around 40+ such use cases that we still need to deploy. Definitely, we are going to see some ROI using this product. It will develop more over time.

In one of the use cases, we use to have around 300 tickets per month which has been reduced to almost zero now.

We evaluated Softomotive and UiPath. 

With Softmotive, the performance was a concerned. It was breaking in many places. That is what we observed. 

With UiPath, it was good. It has got a lot of integrations and can directly talk to the database as well. All those details are there. 

The major reason that we selected Automation Anywhere was the licensing model.

The primary advice which I would give to someone considering automation tools, in general, is don't just go for any RPA tool (Robotic Process Automation). You want to be sure that the tool you choose will solve some issues and resolve your problems. I've seen people just take any RPA tool just to say that they are using some RPA. It is not a status symbol, it is a tool for business. You need to define the problem and that RPA is the way to go to resolve the issue and improve business function.

If there is a process which cannot be completely automated using any scripts, and human intervention is very much required, consider going for this solution.

I will give an example. There was one use case where we had to read information from an Excel table and generate a report out of that. People might decide they need to start using Automation Anywhere or some RPA tool for this solution. But reading an Excel file is not really a commonly necessary use case for any of the RPA tools. Basically it can be taken care of in programming scripts or some small database script application. An easy solution would have given the proper output with less effort and they would still get what they were expecting as users. The point is to evaluate the problem and how complex it is before going to purchase any RPA tool which may be unnecessary. If it can be done through something else, it may be a more efficient process. 

Business users are not using the tool. They are just using the direct outcome.

We have not used IQ Bots, but might in the future.

We have not used the Bot Store. I would like to explore that in the future.

On a scale of one to ten where ten is the best, I would rate Automation Anywhere an eight. It is an eight because I'm seeing some results in the use case even early on whatever we are trying to automate. It has really helped our process so far and we will expand on that.

Our primary use case is for our shared service center that is located in Kuala Lumpur and Manila. These are our key target areas.

For a finance process, we are able to initially do it at segment level. We handle one section, then automate that section. We will then move onto the payroll side and automate that part of it. At a higher level, we are able to merge both processes. Now, we are able to do end-to-end automation: 

1. From creating a quotation.
2. To creating a purchase order.
3. To doing a payment to the vendor.
4. To payment to our employees. 

We are able to visualize the areas of automation as well as do the automation in a fast manner. That's one of the immediate contributions that we are having.

The turnaround time of building bots is quick. We are deploying around four bots per month. The turnaround time to get a design, build, and deploy is very fast. This is very good for us. It has helped us out when scaling up in a better manner.

We want them to have a clear roadmap on what they want to do and follow it. If they are moving to version 11, we want them to stay with that version. Now, I hear that they have a new version out there. I have to plan out every upgrade or movement from one landscape to another. This is a cost for us. I have to get buy-in from my leadership. That becomes a challenge for me. I need assurances that wherever you are going, you are clear on what you want to do. You don't end up with doing multiple upgrades every now and then. It's not a sustainable solution for us.

One of the things that I see in the forums is they are planning to build an ML platform on it soon, whereby we can use RPA as a starting point and have leverage on all the machine learning services available across multiple vendors: Azure, Google, and Amazon. I'm really interested to see how that works because we are already using those entities but in a different manner. We want to see how all of them work together as a platform. That's one of the requirements we are looking for.

I would like them to have more collaboration with SAP and Oracle, as those are our key products. This would provide more value for us.

The biggest challenge that I have with Automation Anywhere is the pace of upgrades that they do. We are not an IT company, we are a mining company. We are very conservative in doing our upgrades and moving from one platform to another. Upgrades are one of the challenges we are having with Automation Anywhere.

Stop upgrading, it's a pain for me. Or, make it easy. I would like a plan for it. Every time they upgrade, I have to upgrade my systems. I have to make sure that all the test bots are working fine, and this is a cost for us.

We are now scaling it up on the operations side for people literally sitting in the mines. They want to use Automation Anywhere for their day-to-day operations. That's the next scalable area that we're looking at.

We have developed a competency within the team as well as with our partners but we are at a juncture where we want to scale up. We are figuring out how we want to do it. One of the discussions that happened in today's forum was the different operating models we can have: a COE, business unit, or federated model. Today, I'm having calls with couple of Automation Anywhere guys to understand the best fit for us. That's how we will decide how we can scale up. We have the potential but we need to do it in a manner that can be sustainable over a period of time. 

The technical support is really good. The response time is good from the support team. When we reach out to them, it is only when we have a problem. Most of our team is a bit on the aggressive side if they feel the bots are not working well, but the language and communication that the operations team uses when dealing with us is very smooth. It helps us calm down and come to realistic expectations because we can't expect every problem to be solved in the first day. Their communication and interaction are really smooth. 

Our customer success manager has been really good at her job.

This was our first RPA solution.

When we started out initially out, we were told that the infrastructure we had would be supported by RPA. We were going to use Amazon as one of our platforms, but it did not happen, so we had an initial challenge. We were behind our schedule by around seven months because of this mistake. Both of us learnt from our mistakes. We now have a sustainable RPA. But, at the start, this was one of the big challenges, selecting the right infrastructure.

We have already seen ROI. We show ROI in terms of productivity. We are already clocking in around 7000 hours of savings per month

IQ Bots are very costly. It's not a sustainable bot for us as of now. We will look for better, alternate options for that.

We had two options: UiPath and Automation Anywhere. UiPath was the cheaper option for us but the cyber security standards of Automation Anywhere were better compared to UiPath. UiPath got rejected because of that. Automation Anywhere has passed our cybersecurity standards, and that is why it was our preferred option.

SAP is also launching its own RPA tool. Therefore, it will be tough to convince my management why I should stick with Automation Anywhere until they provide the intelligence part. Though, I think they are on the right track.

Learn from our mistakes. Choose the right RPA product and partner. The initial mistake that we did was that we wanted to do it on our own. If you are not an IT company, don't get into that. Learn from partners and use them. Use the right partner and learn from Automation Anywhere too, as they have done their own mistakes. Learn from them. Instead of assuming that you know everything and getting into the RPA world. That's the wrong choice.

Automation Anywhere is doing well compared to the market.

We've done a lot of automation with the product in the last two years. We started with accounts receivable processes in finance. I would say like AR function is one of the most mature functions in the product right now because we almost automated all the aspects of accounts receivable.

We have also started looking at automating the accounts payable process as well. I've only mentioned finance at this point, but we also have done a lot of automation with IT, as well as with procurement. Right now the penetration is higher with the support functions but we are also looking at different ways to automate. For example, we would like to use automation technology in core engineering. We also want to be expansive and do projects beyond our current boundaries — outside of just India. We've already done a small PoC (proof of concept) with a company in China and we also automated three small processes with a U.S. entity.

We use it daily and have done projects with the support functions, such as financial services, IT, and procurement support. We have 50 to 60 processes that have been automated using RPA in all three areas put together. This is the breadth and extent of what we have automated.

We are using the on-premise deployment model.

The product is improving our company in a number of different ways through the automation it helps us to create. I would say like the AR function is completely automated right now, but we are in the stages where we are looking beyond AR, beyond finance, and beyond support functions. 

All this time that we were using the product in the beginning, we chose to work on individual processes for automation. We are working in small pockets. We were identifying a project or a process as a small chunk of automation and we looked at opportunities within that particular function or a process and automated it step-by-step. 

For example, within the AR invoice process, there are different types of invoices that we do, like project invoices, manual invoices, past invoices, and other invoice variations. We had started building solutions for these things in isolation. We automated the SPA (Sales and Purchase Agreement) function first and then the project invoices. Then we saw an opportunity and made a change to bring all the invoices into the same platform. So now there is a bot which identifies what kind of invoice it is and it triggers a respective sub-rooting function what we have built-in. This is much more efficient. The AR function is something which we have automated end-to-end right now.

When bots start interacting successfully with each other, that is when we will see a true enterprise RPA (Robotic Process Automation) evolving out of using this solution. So we have benefitted a lot now, but expect that we will benefit even more in the future as we get better at using intelligence.

When we automate, we deliberately kept some manual toll gates. This was a very informed decision that we made. It's a conscious decision that we don't want to leave everything to the bot to do from start until the end because the accountability will not be there with any of the team members. This is one of the reasons why we have kept a manual toll gate in all our processes.

I would say the entire Automation Anywhere RPA functionality is the most valuable part of the product because it helps me to automate the mundane interpretative task. That is where most of my team members, who are part of the support team for product function, spend a lot of their time.

The IQ Bot is good. The pilot that we have done with one of our U.S. entities went well. Our accuracy has increased tremendously over the last two to three months. We have increased FTE efficiency. It's definitely a success for us. 

You spend some time trying to automate using RPA and then once a solution is created, they will gain back the time that they spent in development and then have more time to think about how they can further improvise and improve the process. That is all possible with the RPA. That is what we have been doing successfully in the last two years. The opportunity to customize and build out the platform makes it more useful and valuable.

We found it very comfortable because we are all functional experts. Nobody had any programming experience earlier. We all were able to learn Automation Anywhere in a four day classroom session that we had with one of the trainers from Automation Anywhere. With that, we started our own development. 

At least for our requirements, whatever version we have been using till now —  I think the current version 11.3.2 — is fantastic and more than we could use as we grew with the product. Any additional functionality I'm going to get in the upcoming version is a bonus for us as users. 

No product is perfect, so there is always some room for improvement. Right now we are most interested in cloud functionality. It could give us an additional option for managing everything in on-premises or in the cloud.

My experience and knowledge with respect to our initial deployment of Automation Anywhere were very limited. Had we had more experience, we probably would not have used the Intel landscape. We would have used something more relevant to our process and function. This compatibility might be improved.

I would definitely say Citrix automation is one area we have continued to struggle with for the last two months. If that can be an improvement in design for the next release it would be welcome. I know that a Citrix plugin has been already introduced by Automation Anywhere. If that can be made seamlessly integrated and easy to use, then I would definitely be very, very happy with that as an enhancement. The Citrix automation plugin that they have come out with until now has not been working for us. We are still in the process of figuring out how we can make that work. So, we are collaborating with the technical team from AA. There is an alternate solution where you can just move the system or application out of the Citrix environment and made it a standalone system. That will work. We know the workaround, but we still haven't figured out a solution to making it work in a Citrix environment. Hopefully, they will figure a solution in a month's time.

Any customer would look for advantages and changes in pricing. I won't say Automation Anywhere pricing is not good or not competitive. It is definitely competitive. But there are additional players in the market that they need to compete with and working on pricing could help. I believe there are competitors who do not charge anything for what is the AA Control Room (used for Bot creation). They charge only for the runners (Bot execution).

So there are other options available where you don't need to pay extra costs that may be more attractive depending on your usage. With Automation Anywhere I'm the creator as well as the Control Room. If Automation Anywhere could get a little more competitive on those aspects of pricing, I think it would be like heaven.

I would like them to combine a BPM solution with RPA. Sometimes you need to have BPM in place so your process orchestration will be smooth. It'll go through a standard process. On top of that, you are doing some manual activities that will be replaced with RPA. Automation Anywhere already has RPA, if they would allow us to create a simple BPM solution on top of it to use RPA that is the best resolution. It would solve most of my problems in my processing unit.

I have been using the solution for about 18 to 19 months.

I would rate the stability of the RPA as much higher than the stability of an individual manually handling processes. Because stability is pretty good, the machine will outperform an individual. With respect to individuals, there will be always some attrition — there will be some learning time and people will tend to do mistakes. That is not the case with respect to the RPA. So while that is not directly about the product, it does add stability to our processing.

Beyond that, whenever there is any change to your applications or environment where you have automated a function, that is when your processes or RPA can stop functioning. So it requires a little bit of customization, and again you upload it into the control group. Because the RPA is so flexible and so convenient to work with and easy to use, I don't think that is where the major bottleneck occurs at these junctures.

Beyond that, we developed a fallback plan. We test the fallback plan once a quarter by stopping all the bots in operations and then we invoke the fallback plan. We have this mapped out in a document where we ask the respective processors to do the processes and simulate a stability failure.

There will be always risk associated with anything that you do. It's all up to an individual to make plans as to how they deal with bottlenecks, how to structure plans for potential stability issues, how they mitigate these potential issues by having a proper solution and proper process in place. To me, that is where the secret of stability really lies. It is not really correct to blame the stability of the product when it is the fault of the process. It's all up to an individual better manage how to look at things.

I would say that scalability is a critical aspect of using RPA and maximizing efficiency. When you develop one bot. You can just use it for N number of ports with the same source code. So it doesn't require any retooling. Scalability is very high. There will be some process deviations or some nonstandard aspects associated with any process that may require rethinking and interaction.

For example, maybe because of the ERP (Enterprise Resource Planning) or the different systems that we use or integrate at the time of taking over those processes, scaling may be influenced. The classic example for our company, I would say, is that we have grown manyfold by acquiring lots of companies in the last three decades.

Every time we acquired new divisions or companies, it is not only about the revenue or products. We also get legacy systems or along with those entities, there will be some processes and practices which are nonstandard for our organization. We'll need to incorporate these different systems in the ERP.

But scalability is always possible. With the RPA only those areas where there are differences need to be fine-tuned in your RP source code. Then you can redeploy it successfully. Beyond that, we also take this as an opportunity to evaluate processes because we don't look at the RPA project as an isolated project. It is an opportunity to grow and improve automation in various ways and not just this one project alone.

Even before we automate something, we look at processes to scrutinize what are the nonstandard activities we do. We look to see if there are ways we can make the process more lean, simple and straightforward. This can actually make the process that I'm trying to automate more efficient. Then it is also easier to accomplish the development, easier to integrate with other processes, and more adaptable when you automate the process. Working this way, I know for sure that what I am automating is going to be an efficient process. 

So scalability is very easy and very simple to achieve especially compared training individuals in a process. A bot needs no training. Making tweakings to the source code and deploying successfully in production is much faster and easier. Because of these reasons, I would say scalability is pretty efficient and easy to achieve using RPA.

We plan to increase usage in the future both in our current departments and new divisions of the business.

I would rate Automation Anywhere as one of the best in the world when it comes to customer service. I've had the opportunity to gain specific experience with certain members of their team and the service is consistent and excellent.

Initially, when we started with the IQ Bot project, we had some issues and experienced a bit of a learning curve. So we immediately raised those concerns. Our first issue took less than 24 hours to get fixed, and without adding any additional cost to the customer. That type of service and support of a product is an important thing.

I would say the customer service team, the project team, and even the aftermarket customer success manager are all fantastic guys. I know that the organization has people with strong capabilities and excellent talent. It is very, very evident when you interact with them.

I would definitely say Automation Anywhere is aggressive when it comes to driving success for the customers. They are very passionate about customer success and their focus on the customer.

Some of my team members have taken courses with Automation Anywhere. They still need to complete a few more assessments before they get their certifications. The courses are pretty good, the assessment is very cumbersome and complex (from what I understand). It's too technical for them. Maybe it is easy for technical guys, but not for functional people. I assume that this is the way it should be, because it's an assessment before you get a certification. It has to be tedious and cumbersome to crack it.

The best person in our organization to speak to the complexity of the initial setup is an IT guy from my team. He was responsible for a series of calls to the tech support team and he was involved in a lot of discussion with the Automation Anywhere team initially. Obviously we had contact with technical support so it may not have been so easy to do the initial setup, but I think that is quite acceptable or understandable. Anything which is new will probably be something you need to spend extra time on during the initial phase-in of a new product.

Beyond that initial setup and normal learning curve, I haven't seen any problem with respect to adapting the RPA technology in our company. It has been pretty smooth. The technical support team was great in terms of supporting anything we experienced in the way of technical issues. The only issues we experienced after that have been some issues with respect to using a Citrix environment. We are finding it difficult to automate on Citrix efficiently.

We have been continuously on calls and meetings with the technical support team. They have been coming up with a lot of innovative ways as to how they can fix that problem with Citrix. Of course, we are still in the midst of finding a solution to the issues. But I know for sure with the support that I get from the support team that we will definitely have a solution in the near future.

We did our own implementation with assistance directly from Automation Anywhere's technical support team.

There was a bit of a hand-holding in the beginning because Automation Anywhere developers came and developed a few bots for us. Beyond that, it is all on our own. We have been very independent. We hardly got support from the Automation Anywhere team after that. From our own experience, the tool is pretty easy to understand and start using.

The bot creation process has different processes depending on what we automate, e.g., accounts payable, IT, and procurement. These are miles apart. The complexity would differ based on the different applications that we trying to integrate using RPA.

We try to check the different applications involved for automation and whether they are compatible with Automation Anywhere. Then, we understand the process. We do a value stream mapping, e.g., what are the non-value-added activities that we are currently doing to make it lean, simple, and re-engineer the process. We identify the activities that can be automated using RPA, or any tool.

There'll be the extensive workshop conducted before we conclude what we want to automate, how we want to automate, and how long it is going to take to automate. We do an extensive study to determine:

• What'll be the return on investment? 
• What type of a return that you'll get by automating the process?

We document it and prepare it as a business case. We send it to the sponsor for approval. Once it is been approved, then we will kick-start our development. Once the development is completed, there will be UAT and we will roll it out to go live.

There will be a burn-in period where we will be providing the support. It's like a normal SDLC. It's the same model. However, we analyze the process in detail and a BRD will be prepared, then we will start the development.

A simple process might take somewhere around four weeks from start until the end. Something which is very complex in nature might take up to 12 weeks. Anything which is very complex, we would like to break into small pieces, then automate it step-by-step. We don't try to take the entire thing and digest it. We would rather try to break it into small portions, then move on. 

Calculating ROI for us is pretty simple. We identify efficiency at the beginning, then based on that we will just move the headcount out of the process. We try to compare with the cost spent versus the quote of the money that we have saved on the fully loaded employee cost. That's a simple comparison of what we do. This is a very crude way of calculating our return on investment because there are other benefits that are derived by doing an automation. Other benefits include:

• Improving the quality of the process.
• Eliminating some of the duplicate payments to save some dollars. 
• Making timely payments to the vendor to have better negotiation skills with them. 

These are some of the other overall business benefits that you can derive out of it, but they are too tedious to take into consideration when you're trying to do an archive. That's why we keep it very simple by comparing the labor cost saved versus the cost spent on the technology.

They are already coming out with a community license, which is really good. That's something that I wish to have.

We had looked at a lot of prominent players in the market and examined the different options as well, like Blue Prism and UiPath. Automation Anywhere was the one company who was flexible in terms of offering a PoC. We find this very comfortable. They were very approachable and aggressive, in terms of getting things done. This helped us make a decision in favor of Automation Anywhere. Also, Blue Prism doesn't have the functionality with attended automation that we would like to have. We are looking for the flexibility and convenience that comes with attended automation where you can still run your show.

We ended up choosing Automation Anywhere based heavily on their highly-approachable team. We thought of doing a PoC and Automation Anywhere was the first vendor to volunteer and say they would do PoC for us. That was not the case with the other vendors. They were very reluctant for whatever reason.

In terms of product, almost all the products are good. The differences are insignificant from the product standpoint. What makes Automation Anywhere a little different from the other players in the market is their presence in India. They have a very strong presence in India. They've an excellence sales team, very approachable solutions team, and technical team.

They are very approachable. They come and help you out in terms of creating a PoC, which is not the case with the other companies. The other companies are not that aggressive. They normally don't show that level of interest in terms of getting things done with the customer. They all come and approach for new business, but when it comes to going the extra mile to making something happen, that is where they are lacking. That is the difference for our decision of going in favor of Automation Anywhere.

But we got a lot of support from the company and they have always been willing to go the extra mile in terms of supporting the customer and making solutions happen. So that really influenced our decision, and that is one of the reasons why we want to go with the Automation Anywhere compared to other players in the market.

If I were to rate this product on a scale of one to ten where ten is the best, I would definitely rate them nine. It is not a ten because of what may be my ignorance of the entire Automation Anywhere platform. Probably I'm not aware or don't know the complete suite of assets. I'm not in a position to rate it a ten. To rate Automation Anywhere a ten means I should have complete knowledge of the product and I am sure there are things I have not yet explored. 

As far as advice, the normal tendency — and the mistake often made by organizations — would be to commit at the time of vendor selection by volume of features. They pay too much attention and focus on the product landscape. They think about one solution that has got 200 different functionalities rather than one which has got 210 different functionalities as being inferior just based on a number. But in reality, the users may probably not even be using even 10% of what is available in the tool or the platform. So they tend to give more weight to the product landscape. 

In our case, we made an effort to look at more than just features, but the qualities of the companies and vendors as well. For example, we learned about the leadership journey for each vendor, how long ago they started in this business, how much focus they put into coming up with the product development — the R&D. It is also important who the venture partners are and who the people are who are associated with the company and product.

We have done a lot of automation with our ERP systems. We also have some in-house applications which are on .NET that we have integrated with RPA. This should be the minimum expectation when you're signing for an RPA contract with any vendor. You would expect the RPA solution or tool to work seamlessly with any system. Automation Anywhere works well with no problems except for the Citrix environment. This is where we have had a bit of a challenge. Beyond that, we have never had issues with Automation Anywhere.

These details are relevant and important when you go to make a decision or when you take on a partner as an RPA solution provider. You are not just investing in a partnership for the next six months or a year. Probably some of the bots you are developing today you'll want to be using even after ten years. It's a long-term association what you're trying to make with an entity, the product, and with a company. So it's important that you go through all these checkpoints rigorously.

I've not used anything from the Bot Store.

Every technology has pros and cons with some limitations. There is no point in just harping on the limitations alone. You need to look at how you can make that technology work and solve your problems. This is where the human intelligence comes into the picture.

This technology is an enabler. It will solve most of my problems. It is up to individuals on how to make it work. That is where the trick of the trade lies. If you know how to work with RPA, you will not complain. I've seen many people complaining saying, "RPA doesn't work. It doesn't give you ROI." It's not the technology's problem. It's the people's problem. It's your mindset which is stopping you from getting automated and start using the technology. 

Biggest lesson learnt: You'll understand existing processes in a different dimension. You'll understand your people problems with the process in a better manner. It should not be just be looked at as an opportunity to automate it. If you look at the overall process to revamp and re-engineer it, then you can make your process efficient by making it lean, simple, and straightforward. On top of that, when you try to automate it, the overall process efficiency should increase tremendously. 

if you just look at RPA as a tool to automate everything, that is not a good approach. There are some things which can be automated efficiently using simple VBA Macros. Sometimes you might require a simple .NET solution to automate your end process, which is more efficient. You can make automation in the existing ERP, and that might work better. You have to look at different ways of automating things based on the process and complexity. You have to look at what is the ideal solution, then you have to pick and choose what you want to automate.

Don't look at RPA to solve all your problems. You need to use the right technology to automate, simplify, and minimize your problems.

My day-to-day activity was to take data from invoices and put it into an Oracle DB. I have already automated banking uses, which deal with some of the invoices. The second case solution which I had worked with was multi-bot architecture.

We have certain kinds of applications spread across our organization and the data coming into that organization is common. We made a solution as a multiBot: one Bot is working on one application and we have hundreds of applications. So a hundred Bots work together on the same set of data to integrate it.

The applications are different. Say one is Oracle, one is SAP (System Analysis and Program Development) and one is Salesforce. In the way we implemented this, we segregated the workload into parts: part as a master Bot, part as a worker Bot and part as the closure Bot. The master Bot will work on the input part of the data set, the worker Bot will work with the individual (designated) applications, and the closure Bot will consolidate all the data and feed it back to the designated user. This was the plan for our architecture.

The Automation Anywhere product has improved our organization with the speed of processing. It is very fast in execution time, it requires less support time, and it is a good value for the money.

The most valuable features I see right now pertain to dealing with the servers. That has become a distant concern. Because data is already on the cloud, I can use a controller and my client as one unit. That is the best thing. I can use Automation Anywhere in my mobile, I can run my Bot through an Android app. This flexibility and centralization without worrying about availability is a good thing.

I think that all the expectations I had for the new release of the product are covered in the coming version A 2019. I'm very happy about what I hear about it. I think once I use this A 2019 release, I'll come to know what the things are that I'll want in the future. We have access now to a community edition version, which I have to download and will be testing out shortly.

The first of the new features that I believe will do me the best is the customization of the commands. I can build my own package as per my convenience. Let's say we have a variable command. We already have the ability to use XML commands and we have some Excel commands that are provided by Automation Anywhere. Now Automation Anywhere is allowing us the opportunity to build something of my own in their environment and deploy that in production. Before I could imagine that component and not build or deploy it. I can build it now and that an important new feature for our progress.

As far as the stability of the product, it's doing well. My experience over the two years I have worked with it as a developer, going to the cloud has been good for reliability and accessibility.

We have not experienced downtime from the Automation Anywhere setup. When our infrastructure is down it definitely impacts my accessibility to Automation Anywhere. This is not actually the fault of the product as far as I have experienced.

I feel the one thing which I can tap to enhance the scalability of the system is the AI component of Automation Anywhere — that is IQ Bot. I think this is something which can really grow into a massive Bot solution with great advantages. I heard recently that the accuracy of that data reading for invoice processing is something like 70% accurate currently. I think they are trying for 90 or 90 % plus as a goal now.

We have definitely had the opportunity to use technical support and I evaluate them as very good. If I have any data stuck somewhere, I query to the Automation Anywhere support guys. If I have some problem with the 11.x version, they'll admit that there's a bug in that version for a particular process or function and they will develop a patch for it in a new upgraded version. We definitely feel confident going accordingly with that and patch the update as a solution.

Our reason for adopting the product and why most of our clients prefer it as a solution is that we talk with them honestly about what capabilities they will need and why this product fills the purpose. Everyone can choose to do their tasks in a different way and other solutions could work to develop automation. What matters for me is the way the product allows users to easily develop the Bots. I do believe that Automation Anywhere is giving me the opportunity to quickly and easily develop stable Bots and it is better at that than other competitors you might want to compare it to.

It is definitely not a simple setup. It is at a medium-complex level. It depends on what actually gets put into the brackets.

When there is a level of complexity, it's all related to the server, where I'm hosting my applications and my client. In the 11.x version, we control one server from another server. When we have to use many servers, the complexity of the setup begins to become more involved.

We developed our architecture on our own by our own, designed to fit with our needs and purposes. We have also done the initial setup now for a number of different customers.

In some ways, we have seen a return on investment. For example, we have one customer who is aware of the FTE reduction (Full-Time Employee) on the repeated Bot creation jobs. They have scaled up by having their workers work in a different way. We are actually automating the repetitive Bot creation jobs and reducing the FTE where that human effort is not actually required. The company resources can spend more time focusing on the creative part of the work rather than creating the Bots.

I don't know exactly what the pricing schemes are for the product as this type of negotiation is not my responsibility, but I think the basic pricing comes to $15,000. We have many employees and perhaps not so many doing Bot development and deployment. The Bots can service a lot of people and I think the rest of the pricing is based on usage.

For people looking for my recommendation for an automation product, I definitely would recommend Automation Anywhere instead of going for a more orthodox or older technology. With older tools, you are just doing the same things and not improving processes. With RPA a digital transformation is actually required for an organization to adopt a better way so they scale up and create an enormous amount of new opportunities for their organization to grow. It is a step to go in the direction where AI is going in. You cannot see the destination yet, but somewhere you have to start up using an RPA that is right for you. That is what I would recommend to my colleagues.

If you start talking about innovation as streamlining day-to-day processes, that is where to start from. It is where we started. We give clients various approaches, but we recommend that RPA is one thing which has stability and which is a good, long-term return on investment.

Once you invest you don't get the returns immediately. You have to wait some time while you work at creating the solutions by scaling the number of Bots you have and the processes you simplify and improve. After a time, your efforts will improve results. That is what we communicate with our customers. When we have them interested, then we come to a conclusion as to how we will go about implementing it.

On a scale from one to ten where ten is the best. I would rate this product as a ten-out-of-ten because the company and product have done everything to meet my expectations.

We used to expect new things in the A 2019 version and the company delivered on that. So, once I use this release of the product for some time again, I will probably have some new expectations. By 2020, I think we will send them feedback again.

There is not one specific use case in the sense of what we use the product for. In the broader scope, it would be automation. But right now we have several applications. We started our journey with the tool in 2017, and we have automated several processes in finance, IT, and engineering. 

In finance, for example, we have automated cash application, billing processes, reporting, payment processing, and we are using IQ Bots to automate our invoice processing. We completed the pilot, which provided us with phenomenal results. So we tested with a small entity with 30000 invoices and around 300 suppliers with a high level of success.

The character extraction capability of IQ Bot is much, much better than the other OCR (Optical Character Recognition) engines that you have in the market today. So we are completely pleased with that, and we are planning to upscale our invoice automation processing.

Today while we look at the opportunities in front of us, our customers are expecting us to be more productive and execute with greater speed to be relevant and competitive in the market. The expectation as far as the accuracy is really very high, and we need to be compliant. We have experienced that the more manual and hands-on that we are that there is a higher risk of being non-compliant.

There are skilled companies who are spending more time on transactional activities. For example in the engineering field, there are engineers who are spending time on transactional activities and there are finance guys who are spending time on transactional activities that could be automated. 

We can use intelligent automation with great value in helping these people upskill themselves into newer areas of analytics, new roles in reporting, and project accounting in finance. We're trying to eliminate these transactional activities, be faster over time. We started by looking at specific activities and we looked at the processes. Now, we are looking at a complete value chain. When you look at the complete value chain, that's when you actually begin driving positive change in business results. That is our projected approach for the next couple of years. We'll be looking at the complete value chain and see how bots can help us make our process more efficient.

The most valuable feature is the IQ Bot's ability to extract information accurately. It can do things like process table-level information, line-item level information, etcetera, and the accuracy is really very high. All of our users are accountants rather than programmers or anybody with an IT background. The accounting people can easily learn Automation Anywhere. We tried a few other tools but our folks were more comfortable using Automation Anywhere. They felt that it is easy to learn, and it was easy to train them as to how to use it.

In the next release, I think it has to be more compatible when deployed with the Citrix environment. That's one bottleneck that we have seen. Technically when we used the IQ Bots, we couldn't work directly through the Citrix environment. With our ERP (Enterprise Resource Planning) setup, we needed to access it through the Citrix environment. Because we were not able to do that, we had to have a workaround. We are currently working with Automation Anywhere to have that fixed. They have given us confidence that it can be done.

When looking at stability, we have to remain ready for any surprise even if we have not experienced any stability issues. We don't know what that kind of surprise will be, but we have backup plans in place.

In case the tool fails, we may not be as fast as the bots, but we have a BCP (Business Continuity Plan) but we know we can't be specific on what challenges will come, because we don't know.

In two years, I think once in one process where a bank changed its user interface on the bank website, a bot failed. We had to go and correct it. It was a fairly quick fix because to create it doesn't take much time. Changes like this are not predictable.

If you look at our shared services, we are growing and we need to keep our costs flat. This means I cannot hire more people. This need for greater efficiency is made up by what I have been able to gain out of the automation. We are actually using automation to move more processes into our shared services. Ours is a private business and we create big cement plants. One project could last for five years. When we land a big deal our volume spikes. It's a very cyclical business. It has been very easy for us to deploy scalable solutions now.

The company is very service friendly and willing to work with us when we need it. I would give them high marks for attention to customer service.

Our decision to go with an RPA solution was one that I made. One of the reasons I was hired into this organization was to drive automation. There was a specific goal for that which I was tasked with.

When looking at other options in the market Automation Anywhere seemed to be the company for us for a couple of reasons. One is that when we had our first engagement with Automation Anywhere we felt that they were very customer-focused. We did not see that with the other service providers. They really came prepared when they first met with us. They had all their books, IT, operations, delivery plans and such, so they were able to answer all our questions. They were very flexible in meeting our requirements and needs.

They were willing to go out of their way to support us and to ensure that we would succeed in the journey. Some of the service providers even refused to create POC's for us. But Automation Anywhere said they would and they went ahead and created them.

I thought the initial setup was straightforward and easy.

We did not use any consultants for our deployment. We worked directly with Automation Anywhere. Our belief is that we know our business better than anybody so we opted for maximum direct involvement.

Before deciding to go with Automation Anywhere we looked at other products for comparison like UiPath. We looked at the desktop automation tool, I currently don't even remember their name. The choice seemed obvious from the first impressions.

If I have any advice to give to people who are considering this product as a solution to their automation needs, I would say don't waste time thinking too much about adopting it and just go ahead and start.

On a scale of one to ten, with ten being the best, I would rate Automation Anywhere as an eight.

If you look at the first year we had the product, we had a 6% efficiency gain. This year we are looking at 10% in finance and 12% in IT. The more we discover ways to use it, the more efficient we will become.

Being a bank, we have a lot of processes which we have automated. I am a Project Manager for HR functions. The majority of my processes are in terms of income and skills processing. Those are all automated.

We were one of the few to start up this journey with Automation Anywhere. Interestingly, the majority of our processes were determined to be boring. People did not find them to be very interesting. Those processes have been automated. Being a bank, we have some sensitive processes which we cannot automate. Those processes have been given to human intellectuals. Otherwise, the majority of our processes are automated.

It has boosted our processing time by seven times. Typically, something that has taken eight to 10 minutes now can be done in two to three minutes. So, we have seen some value-add there. 

Resources are being processed earlier and involved in a different type of a governing kind of role. This sort of builds a layer for them to move and scale up. The solution is fast and easy to deploy. Our use cases lasts for two to three sprints and we can churn out solutions very fast.

We do not have a server type of an environment. We use a desktop version of Automation Anywhere which is easily customizable and quickly built-in. We do not have to go through major security iOS applications, etc. These are all enterprise applications that we have onboarded. Each of our functions take their responsibility of building their bot and deploying it. 

It is fast and reliable. 

Older versions of Automation Anywhere required specific skill sets to use it. It is no longer like that.

The version A2019 GUI allows you to drop and drop.

As far as version 10.1 is concerned, we have been using it for the last two years. It is okay. As an organization, we look forward to next version. However, being a bank, we have certain processes that we have to follow. We are happy with the version that we are using and haven't experience downtime.

We have been looking at processes which can easily transition into a large scale environment, where you can have cloud or hybrid model. However, being a bank, some of our processes are critical and we would like to hold those on-premise. This limits us with our usage of Automation Anywhere.

The support that we receive from Automation Anywhere is really good.

We have specific customer success managers as a platinum partner. We have support extended to us when we have any type of concerns and issues. 

The initial setup was very straightforward. It didn't really affect our processes at any levels, which really helped. The process was fast and easy.

The support team kept our team calm.

We have an in-house Automation Anywhere team who supports us.

It saves us man-hours, headcount, and processing time.

We have automated the equivalent headcount of 500 FTEs since we started. Those people haven't been laid off. They are just doing different types of work activities.

We did not evaluate other vendors beside Automation Anywhere. 

Automation Anywhere was a pioneer in the market at the time that we were evaluating vendors. It was a good match.

Explore the new version A2019 that is coming out. It is user-friendly and can be onboarded quickly.

I would love to use the next version A2019 that is coming out.

We use this solution to assist us in the collection of data. We have patients who fill out an application that contains information based on the affliction that they have. For example, a migraine patient or a diabetic patient will have different sorts of information contained in the application.

It starts with them giving us information. There are no regulations that govern the format of what they give us. Based on what they give us, we provide them with our application. Our overall goal is to give them a better quality of life.

We use MetaBots to ensure that the data goes into the proper channel and in the proper pattern.

Before we implemented this solution, we had to manually deal with a lot of emails. People would send us unstructured data in the form of Notepad or Wordpad. We spent a lot of time manually entering the information.

With Automation Anywhere, what used to take us two days now takes us twenty minutes.

The most valuable feature of this solution is automation using MetaBots.

We would like to see support for macOS, rather than just Windows machines.

Whenever you start Automation Anywhere it opens the IE browser to notify you. It would be really great if you had the option to not open IE when it starts.

If you want to use Chrome then there are three or four additional steps that need to be completed.

This solution is pretty stable.

Scalability is good, although it would be better if they supported more than just Windows machines.

The technical support for this solution is pretty good. The turnaround time is good, as well as the response. The technical support people are well trained and we appreciate it.

We have in-house people who have been trained and handle this for us.

We have certainly seen ROI when it now only takes twenty minutes to perform a job that use to take us two days.

I am involved in making the decision as to whether we use Automation Anywhere or Blue Prism in our upcoming projects.

For each of our projects, we do a POC that lasts three months for each of the tools. Out of that, we come up with the best solution that we can offer for a particular project.

My advice for anybody researching this solution is to first identify all of the use cases around your project. If you don't do your due diligence then I don't recommend this solution. You need to have the use cases identified.

We wanted to use IQ Bot to assist with unstructured data, but we were not able to do it. Our next step is to create a workload to handle our information processing.

This solution saves us time but there are some things that make it clumsy for the end-users. When we have to tell them that there is no macOS version then we put our heads down and tell them that we have to wait for that. Also, if you want to use Chrome then there are three or four additional steps that need to be done.

I would rate this solution a seven out of ten.