Automation Anywhere Reviews

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.

My company' objective in using this tool is to automate every rule-based operation possible. We're looking forward to automating anything that does not need a human to make a judgment call. We have automated most operations in several applications, including mainframe, Linux, web-based URLs, Citrix automation, and in Excel extensively. We have done a variety of projects but we are looking forward to growing more into other areas that we have not yet explored.

The biggest value that I see from the product is the way it works in general. The unattended mode that Automation Anywhere promotes, works great. That is the best thing, I would say. It runs code that performs on a virtual machine unattended. No one gets involved in the triggers because the bot controls the tasks. When you use a person to manually monitor a task, such as getting a quality check done, automating the task to work unattended eliminates all the human effort. It's a solution that is quite simple and straightforward to implement and is available 24/7, 365 days. No disaster recovery is required as the server is always intact because processes run to assure uptime, security, etcetera.

We are aiming to have 100% unattended runs. We don't want attended runs because it increases bandwidth which is not great for support guys and clogs the system. Also, you can have some unattended InfoSec (Information Security) breaches and things. We constantly aim to have the best. At the moment performance is not 100% but I would say it is constantly improving.

Automation Anywhere has helped our organization to operate by working on AA-level development without all the trouble of having VMs set up, setting up ports for it, having the environment so that the developers can work on it, etcetera. With Automation Anywhere, I don't think we need a technical guy, an IT guy, or specifically a specialist engineer to accomplish things. Automation Anywhere is that good. A layman who has a keen interest or even a little bit of curiosity can learn the product end-to-end, sustain himself if he wants, learn how the VM is developed down by the ports. The product and support make it easy to learn. The knowledge is readily available.

The whole package that Automation Anywhere offers is really good. The variety of commands that it offers made to play well with other integrations. It could be using a C# module, code on JSM, the APIs — I want to use database XM. Ultimately, I want to use anything that makes it friendly for me to accomplish what I need to. That is a help because it often will be something I have already learned, it will be easy to access, easy to build, easy to sustain — as long as the commands work as expected.

Unattended Automation is the best feature for me. Because I use it extensively, it is also one feature I am very familiar with and so it is also one of the areas that I would like to see more improvements on. Any time I speak with people who promote automation and say that it is unattended, they may have a machine perform an operation. Very few understand that each unattended operation packet is unattended at all times. No matter what time of the day, if you just click Run once and it operates to get something done. You don't continuously relaunch it.

In my current role, the only thing that I focus on is how sustainable the code is. It has to run for a long time — years. I am expected to run extensive testing. So, in this position, I'm working on the current stability of all the commands and how that can play into the future. I'm not looking for new features. Really the opportunity for automation is already offering this opportunity to create your own features. Adding new features is almost too much. If I've got enough tools to use, I should learn to utilize them first. Use them and then maybe get something new once I have exhausted the possibilities. There are already enough options that AA provides to use. The commands that it offers out of the box are okay for people to begin to work with it. If you don't know it, all you have to do is ask. 

It is not an end-to-end solution for everything, but it is very good at what it does with allowing automation and freeing up other resources — both human and hardware. It is not an end-to-end solution for everything.

The only area for me that I would consider as an improvement is sustainability in areas I face every day. On CSM (Central Management System), for the most part, it works every time, but those areas exist where it does not perform as expected. For example, we had a problem with our ticketing system. What we do is we have a ticket open so that the issues stay open for a week even if we have it fixed. It is supposed to stay in the system continuously for a week — a hyper-care period — so that the issue stays open and we are sure the issue is fixed. That hyper-care period never seemed to end in the application. The problem was it extends a week, to two weeks, to three weeks, but we did not achieve that four-week period of no error of the full runs for the solution.

We worked at resolving the issue and thought we fixed it permanently. We locked in the solution. We were happy. We almost won. Then in a week, we had a reversion to the same problem without making a change. It was not possible to explain. It is my only concern that some things get handled erroneously or changed. 

Without question, Automation Anywhere is generally a stable product. It's not like I can bank on it always performing. I know a few bots we created are not perfect, but I also know that most of them — 60% of my bots — are good. No one calls me about them from the time they're deployed. I haven't had a single escalation or a single error reported about them. This is great.

I still have the other 40%. I think some things go wrong in situations you face unexpectedly or an error occurs. This is not the way it is supposed to be. It's supposed to be really easy: just plug it in and you have the service. But it doesn't work sometimes.

It is frustrating at times to experience this instability, but we do find a solution and we are working on it to be better. With the new version and features that AA is proposing, it looks promising that we can achieve that goal. It looks like the new version will be really stable compared to the version I am currently in, but I will never be sure until I use those new versions.

Another form of stability is in upgrades. Currently one of the pain-point areas on my to-do list is migration to 11.3.2. We have been working on it for almost a month now. We haven't reached the deployment stage. When I migrated to 10, I had some bots that no longer worked after the upgrade. It was not expected. We got on a call to support to explore the problem and had to resolve them.

Right now, I'm not really sure when to migrate. We have 50 bots and every fortnight, there's a part that goes wrong. If I have to take the action and migrate into a new platform — 11.3 2019 A — there is something of a leap of faith. I'm really not sure that I can take that leap now considering the relative stability that I'm experiencing at the moment.

Working with Automation Anywhere, I have been taking steps to use more of the functionality in the product. In a migration, I will want to use the new version as extensively as I have used the current version. At each step, the newer versions were better than what I have used in the past and I have used version 8, version 9, and now version 10. I've used these three versions and there have been improvements each time. We're seeing improvements to come, which I'm looking forward to exploring. But we have to be sure the migration point is realistic.

A lot of times that I have raised issues with support, the command in question is simply not performing. Object learning may not be working as expected, an action's not executing or it is not connecting to the database at all. The simplest solution is often to copy basic commands and replace them and it works. With the number of calls I made to Automation Anywhere, the guys know me now because I have so many issues. They work with me on it. We try to find solutions. At the end of the day, we find some way or other — a shortcut, say, or copy and paste — and get the code to work. We may not be able to figure out the root cause as an answer so that it doesn't happen again. The bottom line may be that the code might be corrupted, my part of the implementation is corrupted, the ATMX (Automation Anywhere Task Files) part is corrupted, etcetera. But the patches are not a perfect solution when I'm in charge. It's a lot to know a process well enough to fix the root cause of an issue. But these concerns remind me that Automation Anywhere as a tool is great, but there are areas to improve.

Automation Anywhere is definitely scalable in several ways. It's easy and accessible. It's designed the best — almost perfect. It has many more usable components than I was familiar with, and I had so much to learn. Now, with some experience, it is not foreign, and we just don't need to build to get what we want. But to get that you need to start at the design phase, you should not start at development at all. People try — even me — when you're starting, just to aim at building usable components. We can ask a developer to do that, but then the developer will not design to build a reusable component. It will only be specific to his assignment, the development, his process, and he will get it done to complete the job.

Scalability starts with a designer who is the one who makes the call. They need to know what to standardize or how to do things by thinking globally to make sure that a resolution is usable and adaptable if desired. That is the standard we adopted. Other big companies have more bots compared to our 50. They may think what they have is a lot more scalable than it is.

We have ongoing support from AA. I appreciate Automation Anywhere support when I talk to them. There are quite a few hiccups as we go along. At times I don't get straight to the support people when you need them as they are busy supporting other users. But the response has been great.

The setup is a bit complex but it is not so bad if you are a little interested and a little curious in learning about the product. It helps to have a little background knowledge on how it works, what are the features that you need to look for, what logs you need, etcetera.

Some basic guidelines will help you along in the initial setup — a basic brush-up on what to do and expect can suffice. Of course, there is the AA's guide that you can follow if you don't know what to do. Initially, when we didn't know the server, we didn't know what are the application calls were, the documentation did help. It was not that complex to do the installation, but the IT guys did not support it. They were surprised I wanted to learn about everything and work with another product when they had resources to accomplish what was needed.

If you choose to try it out, when you need to know more, ask for help. If you're ready to set up deployment, start from some base and set a restore point.

For those who are considering Automation Anywhere as a solution, I would ask how good their team was already. To take on a new product and take a chance that people will try to enhance their skills by learning it may not be the best course of action. Many will have to learn something new and do better than they did with previous solutions by learning and using AA. If the response is that they have hardcore developers, web designers, C# developers, etcetera. They may be looking for quick resolutions, hardcore development and coding bit. They will want any other product or UI that appears to give you far more than AA. AA does all of that — it is not that it isn't able to do it — but it's easy and it is different. With other solutions, you will need someone with that knowledge and ability to code in a particular language. But AA is a platform that can be used as an opportunity for people to up-skill themselves. That's something that is different compared to any other code.

AA commands are not the same as other languages. It has its own dictionary, its own library, its own way of working. I see that this is the same thing mentioned by others as to what they think about the product. It is possible to learn it by just using the Q&A.

We are using it in all departments: management, sales, human resources, IT, and customer service.

These are some of the benefits that we have seen using RPA:

• We saw a 70 percent decrease in manual steps. If something took 10 steps to do, we are doing it in three steps today. 
• We see 100 percent accuracy in whatever we do, which wasn't something we could expect from a human worker. 
• We see a reduction in turnaround times. Something that used to take two hours to do, today takes 20 minutes to do. There is a 40 to 50 percent reduction in whatever is being automated in comparison with a human doing it. 
  

Three features that came up when we chose the product:

1. The user interface.
2. The Bot Store.
3. IQ Bot, which other RPA don't have.

We would like a better coding interface for developers. We would also like to have a user interface which reduces the time to learn the product so more people in the organization can use software, like Automation Anywhere, quickly automating processes.

As an organization, we feel the exception and error handling could be way better.

We would like the software not to change as often. Architectures were radically reinvented without informing the customer. This wasn't something we appreciated. 

Some of the stuff being used internally in the product, like Elasticsearch or open source, did not pass vulnerability ability assessment. This is another issue. 

We hope Automation Anywhere takes internal component security seriously as we are looking forward to the Automation Anyway A2019 launch. We hope it addresses some of these issues with error handling as well as component security.

Scalability works fine. 

One of the key features that we chose, the bot as a service or the BotFarm, when they launched version 11.3, they decided not to have the BotFarm anymore. This put us in a situation because we expected to have bots on demand, just like our cloud software. This would have been cost efficient for us to use. We hope to see this again being realized with A2019. I hope the scalability from an on demand basis improves.

A lot of the technical support is done by my teams. I do not have great visibility. As far as what my team has told me, it was a tedious process before. They have relaunched the entire support portal. It seems to be a lot more user-friendly to log tickets and reach out to people there.

Their customer success team are a great bunch of folks who try to support and get things done for you.

I have personally used RPA before. It is just the buzzword now. 

At the time, we were looking at or looking at replacing our complex, legacy platform which had a lot of steps. Our multiple, previous software tools that had a lot of Python, Perl-based scripting, and Perl website scrapping plugins.

The initial setup was extremely complex. Version 11.3 came with multi-forest Active Directory support and version 11.10 did not have that support. We had multi-forest Active Directory and it took us one month to resolve when we started implementing it. Again, this information wasn't communicated to us.

I hope going forward I see Automation Anywhere being faster, more transparent, and communicating more in advance than right now.

We had a terrible experience with a local integrator. I don't think that they were ready for the integration/deployment process. We spoke to Automation Anywhere who has implemented more stringent partner qualification schemes to take care of this issues.

We have not seen ROI at the present moment.

Our costs are approximately between $5,000 to $10,000 per license.

They have a ridiculously expensive bot licensing structure, especially for the Asian region.

Currently, we use Automation Anywhere, Blue Prism, and UiPath in my organization.

Start small. Conduct proof of concepts, then choose a process with a quick return on investment.

There are product issues. They have a reckless product roadmap. 

We use Automation Anywhere for product SLAs on the finance team. We are also using it for a difficult automation project. 

We have automated a lot of processes, e.g., claim processing and payments.

It is currently deployed on-premise.

We are helping to automate some of the manual tasks and help to achieve the SLA.

We have some products, like Clubcard, which is a shopper's card that we're using in the Star Market. We are using Automation Anywhere for that validation, raising requests, tracking the Clubcard, and when users get new Clubcards. All these things are done through Automation Anywhere. We use the API to get the status of card numbers. 

IQ Bot is great. We recently implemented two IQ Bots in our finance sector. Manually, we had one person doing a task that took five minutes minimum. With IQ Bot, we are able to do that one particular task in one and a half minutes. That is a huge time savings.

We have done some Citrix automation with MetaBots for claim processing. We use it for validation. It is working well.

We have a credential manager. We have the ability to store in an encrypted way. Whenever we create any bots, we also have bot IDs. Without the bot ID, we are not going to deploy in production. We have the option for the support team only to get access and share their screen with users. If there is a critical password, the user will only put down the password. If we have the bot ID and password, then our support team can directly get that from the application IT team. That support center of excellence team will put in the ID password and credential and see the bot ID and password.

The API feature is the most valuable feature for some process, especially for the Clubcard. It helps us with validation of databases.

We are able to do a lot of things with MetaBots.

The management works well.

One of the great things about Automation Anywhere is that it is a developer friendly. If someone doesn't know the technology, but is logically strong, they can easily learn the tool. This is very good for us. We can train anyone in a short amount of time. 

If someone is not technical, they can also easily learn the tool. You do not have to write in syntax.

We have a situation where the system is not capturing data properly. It is clicking on the UI but it is not able to expand.

We have trouble with large volumes of data in Excel and are not getting good results. I want all the functionalities that they have in the Excel added to our existing version or an upcoming version of the product, e.g., Macros and VLOOKUP.

We have had connectivity issues, such as the reporting of a bad gateway.

We have integrated Automation Anywhere with our SQL database. I heard in version A2019 that we can easily integrate Python too, which is great news. Up until now, I have not been able to implement Python in our Automation Anywhere task bots. Though, we can integrate with other applications, like artificial intelligence, and this is better.

We have not implemented this tool with our AI. We have AI and IBM Watson. We would like to get information (or services) from the Automation Anywhere team on how to connect and implement the AI, as this is a great thing in the market. I'm looking for what to do.

Sometimes, we are facing issue in unattended. If unattended mode is not working, sometimes it will work in attended mode. However, I don't want anything in attended mode. The process is rule-based and logic-based. We just have to schedule, then if the user wants to run from the Control Room, they can. To run attended mode, we have to login into the VM to start it and human activity is required.

The version we started with is not as stable as the current version. We are trying to move to version 11. We are also in touch with our CSM regarding the A2019 version, which Automation Anywhere should release in the next year

We have 50 bots live in our organization.

We have three environments: staging, pilot, and production. In staging, the developer creates and tests their bot for internal testing. After that, we deploy into the pilot environment. That is hypercare which is for User Acceptance Testing (UAT). It is there that we run the bot in unattended mode for one and a half weeks at least with huge volumes. If we have no issues nor errors, then we create a ticket to deploy into production, our center of excellence. This is what our support team does. They will deploy into the production environments. We keep an eye out for at least 10 to 12 days as hypercare. At 12 days in hypercare mode, if we are not getting errors, then we run it in unattended mode as much as we can.

We are using Automation Anywhere in our business units. We have plans to increase the level of the tool's use.

We are planning to move onto the cloud, but first, we have to see if it will work with our business SLAs. If it is good, we will move over. We need to do a test first to determine whether the bots work well or not, which will take about three to six months. Then, we will make a decision on whether to move over to the cloud, the A2019 version. My team is excited for this version.

We would move over to Microsoft Azure because our company is already using it.

The technical support team is supporting us well.

We needed a support guide from Automation Anywhere for the initial setup because we had standalone and a lot of clusters. We needed help from a support guy during our setup to determine whether to go with a standalone or cluster setup.

For the bot creation process, we first check the requirement. Then, we check with each application, whether it is applicable through the Automation Anywhere tool or not. Some applications, like Oracle, do not work correctly. We make a feasibility report and advise the developer to use certain commands only. We provide a process map, e.g., how to create the bot according to Automation Anywhere guidance and what are the coding standards provided. We deliver everything. Then, the developer will start building our bot.

In our organization, we are focusing on continuous improvement through this tool. We are improving day by day, but not focusing on the elimination of any employees. We are just focusing in our improvements and accuracy in our SLAs. Therefore, there are three things that we are focusing on:

1. Implementing our SLAs on time. 
2. Focusing on accuracy.
3. Focusing on our continuous improvement.

Automation Anywhere is profitable for us. As volumes increase and we have a lot of data, this takes time to complete manually. Bots can complete the work without impacting the business. 

We are saving time. Some processes that have taken 24 hours for our guys to do, now take seven to eight hours for our bots. That's our achievement. It also brings accuracy.

We save money indirectly. We are also improving the accuracy of our SLAs. 

I am using that Automation Anywhere Master Certification for version 11. Recently, this has been updated in Automation Anywhere University. Until this month, it's free to use. There are no charges. That's why I would like to complete it this month.

We are waiting for them to release version A2019 version of Automation Anywhere University.

Use the standard guideline that Automation Anywhere provided. Build a dry model for each bot. This will be useful for debugging. I give these diagrams to my developers.

When automating Citrix, we can install on the client. It can easily access objects, we can click anywhere and it can take data from anywhere.

We have a scenario where one process is working, but in another case, it is not able to capture everything.

This is a good product. This platform is great, but there are a lot of issues to resolve, including the Excel features.

My advice for anybody who is implementing this solution is to follow the instructions and the standards that are specified.

I would rate this solution an eight out of ten.

Our primary use of this product as a solution is developing bots to automate tasks and processing. For example, we have financial bots and we have IT bots. We have been involved in developing and monitoring the bots for about one and a half years, mostly for finance and IT. A majority of the tasks were done by other teams.

We have automated mainframe applications and integrated the tool with web-based applications and SAP. We have automated many SAP processes, including posting the entries and POs to SAP.

We are currently planning to migrate those bots into the current version (11.3.2) to make the bots more stable.

We are using the on-premise deployment model. We have multiple processes getting automated through this tool.

The major benefit for using Automation Anywhere is that it has provided a lot of FA (Finance Automation) benefits. That is a major plus point for using an RPA (Robotic Process Automation) tool. Any automation tool, for that matter, has its benefits. But because Automation Anywhere is easier to implement and learn, it is possible to move the bots to production faster. Speeding up that process helps in simplifying our workflow and productivity, and allows our people to do the most useful work we can do.

The basic Taskbot itself is the most valuable part of the product for what I do. The use of IQ Bot is still in a development stage. We are looking forward to August 2019 when we should be migrating to a newer version. That seems very promising. For now, we use Taskbot and Metabot with a variety of applications.

The ease of use is good. We had someone join the company who had no understanding of RPA. He was trained on it, getting his hands dirty, then he was able to develop and start automating processes quickly within a month. 

Resources are available online. A person can get certified and start automating right away.

The Bot Store is good. Although, we have not used the Bot Store much, there are some useful bots already built in it. We can just use them in our processes if feasible.

There are several things that would improve the product. I would like to see them include a group chatbot and make the IQ Bot more stable. Just those things would be great. Adding those kinds of features improves what we can do with the product. Using a client control room concept to ensure that everything is based on the web login, would also be great. Obviously we know that the development of new features will take some time.

We are expecting those kinds of features in the future. We expect more AI integration in our technology.

Automation Anywhere could use to be more stabilized. The product is becoming more stabilized with newer versions, but there are various things that still need to be stabilized. In the current version that we are using, we have a Control Room where the client will sometimes get disconnected. This will result in downtime. Therefore, we need some stabilization from the tool perspective. We don't have any other option than to raise a ticket to Automation Anywhere or get in touch with their support to get the issue resolved. So, we are having downtime. This can be improved.

We are not completely okay with the IQ Bot. We previously used version 5. The newest version does have more accurate results.

Technical skills are required to use the product. With these tools, technical programming is still required with the guidance of technical people. Business people can go ahead and try building a few smaller processes, then when they gain technical knowledge, they can use this tool to their full advantage.

Most of our processes are attended automation. It would be great if more processes were unattended automation, so we could release more FTEs.

We are currently using third-party Taskbots. We would like Taskbots directly integrated into the tool.

We have been using Automation Anywhere since version 9. Over that time the stability has improved a lot. We are expecting it to be even better in coming versions and this is why we are looking forward to our migration to 11.3.2 in August of 2019.

In program versions 10.3 and 10.7, what we were developing was okay. The stability was fine. In version 11.2, we had basic client login issues and database issues as well. When we have a better foundation as far as the stability, we are hopeful of getting better updates.

As far as being able to scale our usage of the product, until now, we have been doing well in diversifying. In the future, we expect to be able to get more from the tool. Our ultimate goal is to use the tool to automate most of our internal processing and reap the benefits of RPA.

Multiple users are currently using the product.

The technical support has been really good. Honestly, it is very good. We have been getting good support from the correct technical people quickly. One thing we would like to experience is that instead of waiting for a new version of the tool to resolve issues, that we could get immediate patch upgrades to cater to our requirements. That would be great. We are getting patches sometimes, but they do not perform as well as we might hope.

We have taken courses from Automation Anywhere University: version 11 and IQ Bot. We also attended training at the Automation Anywhere office for IQ Bot. The Automation Anywhere University courses are quite good. You can easily learn and get certified, which has some value in the market.

We were looking to Automation Anywhere as a solution in a relatively new concept. We believe it was our best choice and, currently, we are hopeful that the stability and the enhancements done to the tool will pay off. We are looking forward to using 11.3.

So far, the initial setup of versions has been straightforward and we expect it to be even smoother in the future.

Bot creation process: 

1. We identify the process.
2. That process will be well-documented along with the operations people, who will develop the BRDs. 
3. After the BRD creation, we'll come to know whether the process is feasible to automate.
4. Concurrently, a solution design document will be developed.
5. Developers will create the bot. 
6. Once the Bot is developed, UAT will be given to the operations people telling them whether the bot is performing as per their requirements.
7. Once finalized, we'll get a UAT sign off and the code will be moved to production where the bot will go live.

Scaling bots to production depends on the process and how complicated it is. For a simple process, it will take two to three weeks. If the process is a bit complex, it may take close to one to two months. It also depends on how your internal compliance is organized in the company. We have a compliance check done at every phases of automation, so it will take us more time to get the process live even for a simpler process since we have to get compliance sign off during every phase.

We did not use an external resource for the implementation, but I was there when the initial setup was in progress.

As I am currently part of a team of developers and people who perform functions, we are not directly involved in the deliberation of assets or ROIs. However, it is apparent that there is a return on investment, and we are noticing it.

We have many benefits reaped from the automation work we have done. So, I don't have the exact information about the cost and what our return on investment is, but it is benefiting the organization in a much bigger way by channeling efforts away from wasting manual time on processing.

As our team size increases, we may get some more licenses for the tool.

We checked on Blue Prism and UiPath. UiPath was still developing. 

We opted for Automation Anywhere. The pricing was okay for us. Also, It was easier to learn the tool and implement within the team. It is easier to learn, implement, and get things done with Automation Anywhere compared to other tools on market right now. 

Before automating, understand the process:

• How big is the process?
• Is it of use to the organization?
• How repetitive or complex is the process?

This is important because automating tasks requires resources.

On a scale of one to ten with one being the worst and ten being the best, I would rate Automation Anywhere a seven. So far it has been good, but obviously there are opportunities to be so much better.

We expect more from Automation Anywhere based on the new technologies that we know exist concerning AI and also unstructured learning. There's a lot of room for improvement, so that's why I would not rate it higher. Other than that, for data structure, it has been good — apart from a few stability issues.

Ease of integration is good. We have automated a process in the current version. Automation Anywhere will tell us if it won't support this version anymore at this particular time, so we'll have to migrate that code to the currently released new version. At that time, we may face some challenges after moving the code. We may have to do some tweaks to the code. We can't directly run it as is, so we'll have to do some minor tweaks so that it is stabilized more, then it'll be better.

As far as recommending the software, that depends on what use case and what work requirements an organization has. For structured data and for simpler processes, it is fine. For unstructured data — which should be addressed by IQ Bot and additional features — I may not recommend it yet. But for dealing with automation of straightforward processes, Automation Anywhere is good.

RPA solutions are continuously improvement due to competition. Sometimes, it is worth waiting for the next version which is more stabilized to be released.

We are in the retirement industry. We use it for application-based automation. We are trying to mimic our operations to redundant business users' tasks, like clearing claims and loans.

We are using version 10.7. We are currently trying to upgrade to version 11.3.

We use Bot Insights. Business users utilize Bot Insight dashboards to get analysis.

In the 10.7 version, the back-end port for the MetaBot password has looping. This has been a type of limitation. Now, we are upgrading and integrating the Control Room, which is a validating feature.

I would like them to add OCR features. This would help us deal with unstructured data and we can get more data out of images.

I would like to see more features related to artificial intelligence. 

The latest version is more stable. We have mostly legacy applications. We do interact with Automation Anywhere support for patches and DLLs which are compatible with our legacy applications. Maybe after our upgrade, we can expect more stability.

In couple of months, we are looking to upgrade. We have set up our environment for integrating in AWS into our architecture. We are setting this up now and planning to install Automation Anywhere 11.3 to see how it is.

It is scalable. Since we have only had it one year, we are still looking into the scalabilty factor.

The technical support is good. They are knowledgeable and don't waste much of our time. They are quick in resolving things by identifying the exact root cause. 

We try to resolve the issue from our side first because we are trained in the product. It is only when we can't solve the issue that we contact support.

The initial setup is straightforward, except when setting up with cloud-based services, like Amazon. The cloud-based setup process is complex.

Automation Anywhere came in and helped set up the tool for us since it was initially new when we onboarded it.

It has saved us a lot of hours, manual effort, and we can focus on more important tasks, which helps us with our ROI.

We purchase on a bot basis. Our costs are approximately $5,000.

There are a lot of vendors out there, like Blue Prism and UiPath. However, A2019 offers cross platform and single point, which is why I would recommend Automation Anywhere.

I have been very impressed with the A2019 version. This version is phenomenal. 

We work in a very complex type of environment. We do a lot of data analytics and strategy consulting work. The work that we have automated so far is our legacy suite of applications, doing all the reporting, data extraction from different web sources, and collating the information, then publishing to websites.

We use RPA or the Automation Anywhere tool to orchestrate the whole process. We combine it and integrate it with other API and Python solutions to help get the data from a particular source, whether it be an FTP source or AWS environment. Then, we make those validations using Excel. After that, we do our QCs and validations, then publish or submit the reports.

We partner with a few other vendors as well for different use cases based on the type of clients that we are working with.

We feel our team is more involved in the whole process to give better ideas and give new use cases to help automate things. Things that were very repetitive and manual, such as creating daily checklists and reports, those have been reduced considerably. Our team is very happy about that.

Automation Anywhere has a very rich and easy to use interface. This makes it very intuitive. As an organization, we give training to business users to help them automate themselves. It is an easy to go, create your own scripts, and logic. The typical commands which they have in the workbench are very helpful for us.

New versions keep coming up. The challenge for us is to have the downtime to do the migrations. This could be improved upon. We would like fewer version changes and upgrades happening to the application. While the downtime is not that much, depending on the business processes, there are times few critical processes are running on a daily or hourly basis. We would expect the downtime to be even less for them.

There are a few internal applications that we have where Automation Anywhere needs to be added. We need to get those applications embedded so the integration process between those applications is smooth. E.g., With a Citrix type of environment or VDI environment, we have not been able to get the right information. We have to use the coordinates. Recently. we attended a session and realized that they have come up with an IQ Bot and computer vision technology. Therefore, we have some use cases which we want to leverage.

Our focus would be for them to keep innovating for more intelligent solutions which can merge your text to speech. These types of solutions, along with other ML and AI capabilities, can solve for the larger objective and typically RPA platforms are not able to do. The type of applications that we use are very large and different. They are not the typical ERP systems or systems which normal organizations would have. If they could bring AI and ML capabilities onboard, this would help me rate them even higher.

The stability is great. We have very few issues. 

We just migrated to version 11. Though, I don't know the exact version. It was a seamless experience. The whole integration and migration has been very smooth for us.

Scalability is an important aspect of it. We believe they have been doing it pretty well. Earlier, we were doing everything as an on-premise implementation. Later, we moved to an AWS environment, hosting everything on our cloud machine. This helped us scale the whole solution and reach our multiple clients in projects that we were engaged in very quickly.

We believe the A2019 version is meant to scale the tool to a larger audience.

If we have issues, the Automation Anywhere team is always available to support us, as there are account managers and customer support managers.

We use the technical support a lot. We have our own dedicated tech support. Whenever an issue arises, we raise a ticket and it gets resolved based on criticality - within a few hours to 24 hours is usually the turnaround time. They are very helpful in terms of setting up conversations and meetings to understand an issue, then take it forward for resolution.

We already had a process excellence transformation team doing the typical operation excellence type of work process improvement and process re-engineering. We decided that it would be better to help us take the leap of automation and go from the third or fourt-generation improvements we were doing since those were long-time deployments and bring a change. We were looking for faster adoption, an easy to deploy solution, and achieve a quick ROI. This is also sellable to our leadership and makes sense to take to a larger scale. That was the whole idea.

We first thought of implementing internal system automations, legacy application automations, and Excels automations. However, when we realized the potential of this technology, and how it integrates along with its seamless environment setup. That was the go ahead for us, and we started our journey.

Initially, because we started everything in-house (did not partner with a consulting firm or the typical technology integrators), it was difficult. Then, we started learning the architecture and environment. Automation Anywhere gave us a dedicated support to set up the whole journey for us in the initial few years. It went from strength to strength after that.

We built up the whole capability in-house. Automation Anywhere helped us with the setup.

From the second year onward, ROI is achieved, which is a great thing because year-over-year you are accruing those benefits.

We have deployed it across multiple processes: reporting, data management, or sales strategy work. We have achieved a scale where we are in a position to close $1M of benefits.

The number of licenses that required when evaluating a solution was not a hundred bot licenses or Bot Runner machines. At that time, we were not looking at scale and that is where Automation Anywhere helped us.

Including the AWS setup and everything per license, it costs us around $10,000 on an annual basis. I believe that is pretty reasonable considering the teams that we have. 

We evaluated the top four vendors: Automation Anywhere, Blue Prism, UiPath, or Kryon. But, we realized the type of use cases that we had and wanted to try first to deploy them. Those vendors had enterprise large-scale license models in place, but we wanted a use-per-license type of system and support structure with its communities. Automation Anywhere reached out to us, and said, “We will do a free PoC and pilots for you. If you feel the solution is suiting your set of use cases, then go ahead and purchase.”

We set up the whole team and evaluated a few vendors. What prompted us to go with Automation Anywhere was our typical use case that we cater to. They were not run-of-the-mill, large volume, highly repeatable work. We have processes where only two to three people are doing the work and not many volumes coming in that.

We wanted our vendor to understand our challenges. We had multiple meetings before Automation Anywhere could understand what work we do. Then, it was like, "Aha." So, it took us time to reach where we are, but we have now partnered with them, and it's going great for us.

1. See how your use case fits with the solution. A few uses cases may be good for you.
2. Take a look at the cost model. Do you want to go for a big bang approach or large-scale implementation?
3. Customer support: Organizations fail to understand when you have deployed bots in the production systems, and they are up and running, that you need a very robust, strong support system. This way if any issues come up regarding the application/solution, teams are there to support you.

Primary use case of Automation Anywhere is financial accounting reporting use cases.

We use unattended bots for all the financial reporting. We have also done some use cases in master data management (MDM). These are the things that we did early last year.

For the next year, we will be primarily focused on cognitive automation. We've already started with IQ Bot exploration. We will be looking into the new version of IQ Bot.

We released ERP, improving our workload balancing. For example, for each of our employees, we have release almost 400 hours of critical repeated efforts.

Automation Anywhere is very good for rapid development. It has all the capabilities in terms of giving a stable automation framework. It has very cool technical capabilities, like MetaBots, dev controls, and object cloning. 

We encountered issues during the upgrade of the framework. We were using the older framework of version 10.3.5. When we were upgrading, we were having a few issues in terms of getting the proper hardware and software prerequisites. For some things, like getting the controls of some of the application's tools, we were getting Automation Anywhere's help.

The operation happened both in hardware and software. There was some amount of friction in terms of technical and hardware operations. In terms handling capturing the controls, that's where we used the help of tech support.

We are looking forward to the release of cloud/web automation, which has yet to be released.

We having most of the use cases rely on Automation Anywhere. However, we face some challenges in terms of RPA implementation with Citrix.

Whatever use case we have deployed in production, we have found nil in terms of stability issues. 

For scalability, we are still working on the bot utilization framework and have created additional frameworks apart from the existing automation framework.

Tech support is one of its primary features, far better than the other RPA tools. We have been able to fix some big technical issues that we came across.

Initially, we were having a few challenges in terms of getting the approval from InfoSec since we wanted some Veracode reportt from our CSM. That took some time. Initially, we were having open issues with the older version, in terms of the Veracode code report. These were high-end critical. Eventually, we were able to get the final report after the approval from Infosec. Then, we were able to install all of the software to our Olam framework.

We started with an integrator, then went directly with Automation Anywhere. Our experience was good. They started by helping us work with the software and understand Automation Anywhere's capabilities.

We have released at least $400 to $500 a month during our peak period, so we have really seen ROI with the product.

I think it's $5,500 per license.

We had some RPA tool implementation strategies. We looked at all the tools and their features. We did a brainstorm session with all the tools and found out the nuances between them. We identified Automation Anywhere as the tool that we should implement in Olam.

We compared Automation Anywhere with UiPath, Blue Prism, OpenSpan, and WorkFushion.

Automation Anywhere is one of the easiest tools that developers can use for development. It takes them only a small amount of time. It has good stability in terms of implementing the automation use cases. We also found Automation Anywhere as a pioneer in terms of RPA implementation.

Automation Anywhere is a pioneer in RPA tools. I would recommend Automation Anywhere. Automation use cases will be rapidly implemented through it. It has a good amount of stability and cool features that can be robustly developed with the help of developers as well as business people.

We are looking forward to using IQ Bot as well as attended automation in the coming year. These are features that are available, but have not used yet. We are trying to do a PoC to start and implement them into our daily use cases.