Automation Anywhere Reviews

In Concentrix, my role is as an asset manager. It's very much focused on the RPA practice globally, which is why we come from enablement to delivery and support. End-to-end is something that is managed by me.

One thing I really like about Automation Anywhere is the product has actually taken leaps in the last three years. We started with the conventional RPA type of use cases. But, in the last two years, with the help of IQ Bot, and what I learned today about this Attended Automation 2.0, I think they are addressing vital key challenges that we have faced so far. The description on top of the description is what their model is. They're partnering with us in this journey of transformation. The type of technology advancement that they have done will certainly help us a lot.

They are constantly being in the BPO space and BPO and RPA are something which go hand in hand in technology. It is the right space for the utilization of this technology in the industry. While our customers are also asking for us for this technology benefit for the revenue benefit, productivity benefit, efficiency, etc. In the last two years, we have leveraged it for multiple clients, whether for telecom, healthcare or other spaces, it has been a very strong partnership that has really helped us.

RPA is something which was their best product. It was easy to config, easy to record, and deploy on the floor. With their IQ Bot, I am very much convinced that was the area where we started tapping unconventional use cases, like machine learning, artificial intelligence, and all those things bundled together. With this cognitive capability, we went from 30 to 40 percent use cases which we are able to address and have leaped over to a wider space of 50 to 60 percent with this cognitive bot.

There are many things which I have liked in the last couple of months that I have seen in Automation Anywhere. Something that really excites me is the new release of Attended Automation 2.2. It's a very lightweight solution. When I'm talking about the automation of the size from 2,000 to 20,000, and everyone is using the attended bot with this scale and thin client model, we can easily deploy and scale it out to the larger corporate size. So, this product is very unique and I have not seen it in any of Automation Anywhere's competitors. They came out with it.

The product is quite stable. I don't know how to code the the other products which we have used. One thing with the bot that we are always with struggling is the memory management. The Automation Anywhere product is quite stable in that perspective. Security and other things are very well managed by Automation Anywhere. The third piece is the architecture is very much centrally governed. This makes this product more robust.

In the last two years, one thing which Automation Anywhere has changed and they actually worked on is the support and enablement part. That will be the key game changer for them. Because if I compare them with other competitors who are in the space of Automation Anywhere, the customer experience (where we are the customer) is there when you need them. The support is available on time. That is where I think Automation Anywhere is wonderful.

It was very straightforward. I don't know if it was because of the training which was given or if it was because of the application itself, but it was very straightforward to start the journey of RPA using Automation Anywhere. Whether it's a complex use case or low complex use case, I think Automation Anywhere does give you that flexibility that you can start your journey seamlessly.

One thing that we are just changing now: When this automation journey started, everyone was talking about ROI. E.g., I'm investing X amount into the technology, and I'm now trying to cannibalize on efficiency. We are not leveraging automation just for cost reduction. The business is now leveraging automation to get it into this space where we were not able to get so far. So, the dimensions of ROI are not only cost reduction. The dimension of all ROI have been changed to scalability, compliance, some other new business go-to market strategies, etc. Those things are very much changed from the way it was here previously.

This is tricky. We all know who is in the quadrant and the leading there. In the last five years, we actually worked closely with them. Everyone does have their own pluses and minuses. But, if I talk about Automation Anywhere, their cognitive bot is one of their unique selling points.

We are able to sell it very easily compared to its competitors. Another piece is the stability part. The third piece is something which is the customer experience: The ease to work with it. The Automation Anywhere, as a partner, is very easy to work with. They are there when you need them, whether you are in the initial journey of automation, you are figuring out what is the right opportunity, or whether you are in the journey of deploying the bot or support. They are there with you at each of those stages.

These things really make them different compared to their competitors. I'm sure if they will continue focusing on these they will be leading in this space.

So far, it's a 10 (out of 10). If there's anything which will change, I will let you know. But so far, the experience with Automation Anywhere in the last two and a half years has been wonderful. My best wishes to the team.

When we started Automation Anywhere, it was a rule-based automation. All the rule-based used cases we could automate. Now, with the upcoming version, it includes AI and Python, so we can go ahead in our roadmap and start automating dynamic used cases too.

We started on the 10.5 version of Automation Anywhere. The Control Room had some limitations. With version 11, they removed all those limitations. In version 11, we do not have the Python support or AI machine learning support. But, with the A2019 version, we will have the AI machine learning libraries in the support. So, we can easily use those libraries now.

The main thing is the simple UI, easy to use commands, and it's very easy to learn compared to other tools in the market.

With the upcoming version, they have addressed all the issues of the clients. They have AI and ML. The GUI is good. The cloud has been included. So, it's promising that they have now included these. We have to see how much we can get used to it.

Version 10.5 has been the most stable version that we have used. With version 11, we are still getting some updates, so it will take some time for version 11 to get stable.

It is scalable. In version 11, scalability has a limit, but with the upcoming version, it will be scalable because it is on the cloud now.

AA has good support. Suppose we have any queries, they are there to help us. They have a support portal where we can raise a request and they will immediately reply on the basis of the priority level that they have set. So, it's very good.

If we go through the client setup, its very easy. But, if we are going through the high availability in the IQ Bot setup, it's a bit complex.

We have more than 50 bots in the company. The FTE and ROI are very good. In the future, we have many projects in pipeline that we are about to implement. So, definitely there is a good ROI and FTE savings for us.

I will rate version 10.5 as a nine (out of 10) and version 11 as an eight (out of 10). Let us wait and see about the upcoming version.

Processes which have a decision making and do not have any required rule-based are considered for automation.

All the features that we have different from each other. Most of the time, we go for object cloning and IQ Bot, which will be used in the coming years. That feature, people are looking forward to, as it will help us read and extract data from unstructured formats.

Although, IQ Bot has data being extracted from it. It can improve with more features, like handwritten copies that are readable. Anyway, the IQ Bot is coming out in a bit, and I'm sure we will go with it.

For most of the cases that we have worked on, the application has been stable. Automating applications has brought a huge change to the automations which we have carried forward.

It depends on the developer and how they have coded it with respect to scalability. However, it has the ability to be scalable.

The main point to go for Automation Anywhere is because we have worked with other tools than Automation Anywhere and the support team which Automation Anywhere has takes time to try understanding the issue, then give the feedback. That is something we learn along with the Automation Anywhere guys. I would go for Automation Anywhere because of the support team.

Version 10 that we had was a little complex to set up. However, version 11 is pretty easy.

We use multiple tools, but most of the time, it is Automation Anywhere which we go for because of our clients who are looking forward to working with Automation Anywhere. It's sort of easy to use. Also with respect to the client as well as the developers, it gives quick results. With other tools, we need to perform a lot of tasks. This tool is a bit quicker. The ROI also comes into picture.

I have in fact told all my friends and colleagues who are in the RPA domain to work with Automation Anywhere because it's easier to run as well as to implement. Overall, the deployment is easier. I mostly prefer Automation Anywhere over the other RPA tools.

I would rate the product a nine to nine point five (out of ten).

We'll be discussing our implementations for Salesforce and using Automation Anywhere to automate sales for processes within the organization. We focus mainly on sales and BFSI.

A very important piece within sales is that we've noticed most of the salespeople hesitate from updating their Salesforce at a frequent interval. You jump on a call, you have multiple calls with your customer, and you hesitate to keep dealing these updates within Salesforce. The idea behind this implementation, or this specific solution, is that we take care of all the updating of Salesforce processes. We take care of all lead conversions, lead updates, lead generations, etc. through our RPA. All you need to do is have a conversation with your bot, and say, "Hey, I just had a conversation with Nick. He seems good with all the implementations. We should convert him from Level 1 to Level 2." These basic implementations have been taken care of.

We're also looking at mobile transcription. So, if you are on a call with XYZ, you say, "Hey, I'm jumping on a call with XYZ, just transcribe what I'm talking about." So, you transcribe those calls and update them in your total documentation. That's the idea.

Automation Anywhere has been an integral part of this product's evolution in general. A hindrance that we were faced with was companies who did not have API integrations for Salesforce. This is where RPA and Automation Anywhere came in and helped us with integrating solutions which did not have API integrations within themselves. That's how we've evolved in the past two to three months.

IQ Bot seems to be a good solution that Automation Anywhere has come up with. It sets them apart from the other solutions. I want Automation Anywhere to work on IQ Bot further to help evolve the tool more and create a certain set of solutions using IQ Bot. They can maybe use better machine learning algorithms to come up with better accuracy for OCR extractions. This is an area that I want them to work on.

It is absolutely robust. Automation Anywhere as a solution, as well as our implementation, have been robust in nature with thorough testing and UAT processes being involved. Automation Anywhere can be considered as one of the most stable RPA tools in the industry, according to the perspective of the limited amount of tools that I've used. But, Automation Anywhere seems to be the most stable one.

We initially started off with a customer who had just three bots. We've now scaled them to 15 bots. It didn't take us more than an hour to scale. Automation Anywhere helped us scale from one bot to 100 bots within a period of hours, if not minutes. Unless you're scaling from 10s to 1000s, I think Automation Anywhere has it covered.

Support is five (out of five). The technical support is better than any other automation tool that I've seen. The ticketing resolution that they provide not only for paid customers, but for PoCs that we conduct, IQ Bot, and other scenarios wherein the product might not be functioning properly. The support is top-notch. There are scenarios wherein we need to be able to identify the best possible solution, and there is support for that as well.

We started off about one and a half years back initially. In those days, Automation Anywhere hadn't picked up so much. The initial setup was difficult, but as they have moved from on-premise to cloud, the setup has become much easier. Now, we are hands-on with the setup and can do it within hours.

With another client, we are saving about 20 hours. However, we are not able to justify that return on investment by just saving time. There are other parameters that we would have to look at for justifying the ROI.

The return on investment for most of our clients depends from scenario to scenario. Some of them look at it on a long-term basis and some of them look at it from the amount of time saved. For example, we are currently working on a solution for a CIO. We are saving about four hours of his time during a particular week. The return on investment for that particular person is humongous.

We evaluated all the solutions. We had different RPA tools. Looking at the feedback from the market and the type of technical support that we had received, we went ahead with Automation Anywhere. The major reason for going with Automation Anywhere was the technical support that developers have.

I'd rate it an eight point five to nine because there's still always room for improvement.

We mostly use it on engineering processes. We also use it for finances in SAP — uploading, invoice creation, etc. But we have mostly focused on our engineering processes.

An example from the finance area is when we need to invoice a customer. We open our SAP account and upload all the data into SAP, create an invoice, and send a notice to the finance team that the process has been completed. They then move the process further along. It's a daily type of operation, whenever such requests come.

We are using the on-premise version because the cloud version (A2019) is not out yet.

One of the ways it has improved our organization is regarding working on Saturdays and Sundays. Obviously, employees don't like to come in on those days. When a user is not there and we want certain processes to be done, we don't expect the engineers to sit there and do them. We can schedule things via email so a bot runs on Saturdays and Sundays. That results in a reduction of man-hours. 

It automates all the processes which do not require human intervention, things which are very repetitive. That means we can give more important work to the engineers now, rather than asking them to do repetitive tasks.

We have these invoices which gets generated every month. We have to enter these invoice details into the stacks. It is a tedious task that is done by our finance team. We have automated the process of entering the details into the stack, and t reduces a lot of manual work.

The best feature of AA is the scheduling and the triggering part of it. Whenever an email comes in we can just use Automation Anywhere. We don't have to sit there. The unattended bots of Automation Anywhere are something which we find very useful.

It does not require much onboarding skills. It's easy to train anyone. We just ask them to apply logic.

One very important thing would be more support for Citrix automation. We want something to support Cisco. Citrix automation is not a very good tool. We are not able to use it properly. Even if we go through a remote desktop connection, it goes along only with the keystrokes and image recognition.

Also, when we are moving from one version to another version, it's very difficult because most of the features stop working. They should first test everything and then release the new version. For example, there's a system variable known as the Excel Cell Row. It gives you the current row of the inner loop. When going from version 11.1 to 11.3, this variable was suddenly not supported, and most of our bots were dependent on that. Everything went down and we had to start from scratch. If you do not have a developer who has done this, it's going to be a big problem in terms of the time it will take.

We need the migration from version 11 to A2019 to go smoothly. Our developers cannot be expected to enter the code again.

I'm not sure about the stability because there are a lot of upgrades all the time. Whenever we move from version to version, like 11.1 to 11.3, if we have ten bots we have to go around and test all ten bots. And in case something is not working, we have to make changes. If they support a migration utility properly, I think it's a great tool.

The scalability is great. Nearly a 100 bots have been deployed in finance, HR, and mostly engineering. We will be implementing bots going forward in procurement.

It has taken us two years to scale to our current number of bots because we spent a lot of time on training at first.

Technical support from Automation Anywhere is great. I have written to Automation Anywhere support many times and there is a great response from them. Even if they do not have the exact answer, they always say, "You can try this option or you can try this option."

We started with Automation Anywhere. The biggest reason our company chose Automation Anywhere was because we found it more reliable for our operations than any other. Also, the response from Automation Anywhere is really good.

We started with version 10.7. When we started, initially downloading the Control Room and those types of things was a bit complex. We had the user manual, but I don't think it's very good. It misses many points. When we missed something, we needed to contact Automation Anywhere support, so there were some delays in the process. 

Then we moved to version 11.1, which was more complex and requires more of your system space.

Overall, the other process is a bit complex. They have said they're coming out with the cloud version. I think that will be a bit easier. 

The development process took us about six months.

We have a team in our company which is responsible for RPA. It's something which we do internally for our company.

There has been a great return on investment. We are interested in saving manual engineer man-hours. So far, we have saved $100,000.

We also evaluated UiPath and Blue Prism. We chose Automation Anywhere because of how well it suited it our office.

Automation Anywhere is easier to use. With drag and drop, we don't need the uploading skills, etc. Everything is just there. You can just drag and drop, then just go ahead and do it. With UiPath, it was a little difficult to understand the process. Also Automation Anywhere has email automation.

I would rate the solution at seven out of ten. One main drawback is that migration issue. Another thing I would like to see is support for all the other scripting languages, like Python, JavaScript and all.

Go through the Automation Anywhere courses properly to be aware of all the system variables and all the features it has. Then proceed with the development phase. Until you're clear on the basic things you cannot do anything in the tool. You need to know those things.

I have done the Masters course on Automation Anywhere University. I have a Masters Certification from them. Their courses are pretty interesting. At the end of the Masters course, we had an interview on the course itself. There were a lot of informative things and it was a great experience.

Next year, we should be moving into cognitive document processing.

We are currently using it for a lot of projects, like repetitive or manual tasks. We are building bots to free human beings from boring jobs/tasks. We are working daily on Automation Anywhere to automate our processes.

We are using it on-premise. We are not using cloud for deployment. As of now, we are running it on our client machines. We develop automation on our desktops, then deploy our automation on our physical desktop using Automation Anywhere.

We have automated web scripting, downloading documents from particular websites, scraping data from websites, and extracting the data from PDF files. We are also updating the application with some user inputs. E.g., if you have an Excel sheet to update into a particular application, we can use Automation Anywhere tool and automate the process.

We have built some Java applications in Automation Anywhere. I have also coded macros and Python scripts to include in our Automation Anywhere tool.

The Automation Anywhere tool is very handy to use since I have some programming background, like I previously worked on Java. It's very easy to use Automation Anywhere because there is not much of coding involved. We just need to drag and drop the commands, then we can do the job.

Automation Anywhere is good for integrating other programming languages and other tools. The ease of use is very good, as we can directly code other programming languages, like Java or JavaScript, into our application and get output.

I have done work using a VPN, connecting via a remote desktop. The good thing about Automation Anywhere is if a client works without Internet, e.g., if we deploy on a client mission and the network is off, then a bot will still run offline.

If we want to read a scanned PDF, we use IQ Bot. Using the cognitive detail of IQ Bot and some machine learning abilities, we can train the IQ Bot to process all scanned PDF documents and give the results in an Excel file. This is a very good feature introduced by Automation Anywhere. IQ Bot is doing well.

The Bot Store is like a marketplace for bot developers. We already have some utility bots that are simple bots from there. We can download the bots from the Bot Store and use them in our current process. That's very helpful for the bot developers, especially for beginners who have just started with Automation Anywhere developing bots. There are a lot of bots deployed in the Bot Store. If you find any interesting bots, we can also upload bots to the Bot Store, making them available for everyone to download and use.

With attended automation, we need human intervention to provide input for bots. We make sure files are presented in a particular folder to pick up those files and feed it to the bot. Attended automation sometimes might go into exceptions, thus we need to monitor it in-between, then check whether it is working properly. This way, we ensure the bot is working properly.

Currently, I have developed between 20 to 25 bots. From when I started, we have deployed as a team between 30 to 40 bots. Their status is as fully running on our client machines.

We collaborate as a team if any face roadblocks or issues, discussing among our colleagues. Then, we involve the Automation Anywhere support team. They are very good. We can raise a ticket and get knowledge from their team. They help us resolve any issues.

The bot creation workflow is pretty simple. We check for feasibility, and if it is feasible, then we go about creating bots for the task. We have some measurements for ROI. We check the return on Investment to determine if it's feasible or not. We check the typical measurements, then go for Bot creation. After creating the bot, we don't have a production environment after creating the bot. We just deploy and run that bot.

If the process is huge and involves 10 to 20 steps, then it might take from creation to production three to four weeks of time. If it is a simple bot, it involves just launching a website and scraping data from the PDF, then putting it in Excel. For that type of bot, we can build it in one week and deploy it in seven to 10 days.

The return of investment on Automation Anywhere very good because I have automated some processes, like scraping the data from websites and updating some applications, and if we deployed full-time employees on these tasks, it would take more than a year and a half. However, if we automate the process and deploy a bot, it can be completed in just a month of time. The ROI is very good because the output is very accurate and the speed is very fast.

Our company is investing a lot of money in Automation Anywhere. They have saved money wherever humans are working. They invest a lot of money in FTEs and other logistics, so the money saving is very pretty good with Automation Anywhere. While I don't know the exact figure, the tool is saving us millions of dollars as well as saving about 40,000 hours in the last year. 

Currently, we are using attended automation. We do have unattended bots but are in the process of procuring some other licenses. In future, we will make a few bots unattended as well.

I did the Advanced Certification on Automation Anywhere University. I have also done IQ Bot learning. I am currently doing a Masters Certification. The courses are very clear. Any user can understand the content. If you are a beginner, go with Automation Anywhere. If you have some basic programming knowledge, that is enough. You can easily learn Automation Anywhere. It is not a big deal, and you can learn with the certification.

If a person doesn't have a programming background or skills, they can use Automation Anywhere and build bots. It's not a big deal. It's easy for business users to use. You just need some basic programming skills, like Ethernet and loops. 

I heard from Automation Anywhere that version A2019 will be released in either November or December. It is completely cloud-based and contains two IDs. One ID is a flowchart diagram and another ID has some commands. Therefore, any business user who has some basic knowledge can develop bots as well.

Version A2019 will be adding a lot of new features.

I haven't had a chance to work on Citrix automation.

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.