Automation Anywhere Reviews

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 use this solution for quality and GXP.

We are a pharmaceutical company and have marketed products that are about to be shipped into the market. Part of our process is a compliance check of those products. We have specifications ready, and we have the parameters with which it has been manufactured, and we have to compare those to ensure that they match. This compliance check is what we have automated using this solution.

The operational side of our business has become more civilized since we implemented this solution.

The most valuable feature of this solution is that the code can be made as complex as necessary because our processes are not simple.

This solution can be moved easily between platforms. We work on SAP as well as many other internal platforms, and this solution can very easily be moved between them.

There should be a meeting between the Automation Anywhere team and the end-users to understand whether the process can be made to work on the first attempt. This would save a lot of time, especially in cases where it doesn't work in the end. This introductory meeting would include what the processes are and what platforms are compatible with Automation Anywhere. 

I would say the product is stable, although sometimes we have connection issues and control room issues. Some of these issues are internal. Overall, the product is fine.

We had had issues with scalability. Recently, we had a use case which we were working on, but we could not do it because Automation Anywhere could not connect to the system. It was an older system, and perhaps the newer systems are more compatible with this solution. We have seen a few companies that use downgraded systems, and that is where we see that Automation Anywhere does not work. 

I would rate technical support an eight out of ten.

Usually, we have a very good response from technical support. However, we did have a case that we wanted to be resolved as soon as possible, and it took a very, very long time. Probably more than a month. They gave us a lot of solutions but nothing worked. Ultimately, it was our team who actually found a resolution for it. 

I think that the initial setup of this solution is good. Because we are a pharmaceutical company, it is a lengthy process because we have a lot of GXP, compliance issues, and quality issues. That considered, it did not take a very long time for deployment.

We have just deployed and are still in the validation process, so we have not seen a return on investment yet. It will take a little more time to see ROI. 

This solution costs approximately $3,500 USD per license. For a large company, this cost would not matter, although if I had a very small organization and I wanted to automate a small process then this would be a bit costly.

We looked into UiPath, but we felt that Automation Anywhere was the choice for us.

Initially, we actually wanted to use both. We looked into both but there are a lot of systems and a lot of complex steps to follow. The developers suggested that Automation Anywhere was a better processor to develop the code because when we wanted to look into the errors or when we have any issues it is easier to look into the Automation Anywhere line than UiPath.

This is definitely a solution that I recommend, but there are a few things that you need to look into. We actually started with a process and ended up thinking that it would not work. You have to ensure that the proper groundwork is done in order to understand whether the process can actually work. It will be possible to find solutions in any case, but it may take a very long time. The longer it takes to automate, the longer ROI will take.

I have been using this solution for a while now, and I think that it is a very good platform. 

I would rate this solution a nine out of ten.

Our use cases for this solution are all related to Telecommunication Companies (Telcos) because these are our prime customers. We also use this solution to automate the support system.

Some examples of use cases are service creation, service deletion, getting complaint details, ticket booking, and ticket updates. We have created unattended bots to handle these processes.

We have found that the automation bots we have developed give great savings in terms of higher productivity and efficiency. We are able to provide value-added to our customers because these processes were done manually, not automatically. It has improved our customer satisfaction.

This most valuable features of this solution are the drag-and-drop interface, and it is easy to code.

We have begun using the IQ Bot, and while we are not using as much of the document analysis functionality, I'm sure that we will be using these features for automating more processes for our customers.

Change management can be an issue because as applications change, the bots need to be modified.

There are some business areas for which this tool is not capable of doing, such as in the areas of graphically-based input. The image capturing of the network management systems is not up to date for all of our customers' processes. We are seeking some kind of improvement in this light. We have use cases that the tool does not currently support, and we will be able to do many more if this capability is also covered.

Technical support for this solution could be improved if they categorized according to severity. At the highest degree of severity, one dedicated person should work to resolve it as early as possible.

It would be helpful to have a repository of use cases that are created by different customers. They could be accessed from the Bot Store. For us, it would help if we had access to use cases specifically for Telcos.

We have a lot of problems installing for some customers. In particular, if it is a distributed environment then we face challenges. For example, the database should be installed in a network other than where the control is installed. It can be very time-consuming, and support for these situations is very important.

The stability of the bots is generally good. Sometimes, the applications get changed for business reasons, so we have to recapture the data that was used to develop the bot. For this reason, we do sill have some challenges.

I don't think that we will have any challenges with scalability. We started in a small way and I'm sure when we really require it, we will be able to scale.

Technical support for this solution is good, and they have provided us with resolutions to our problems. We are partners, so naturally, our support systems are connected.

Normally we need to wait for a message from the technical support team, and then we have to capture screenshots and do some monitoring. We also need to do some analysis. This makes for a huge gap in resolving an issue.

We do have a customer with a technical issue that was taking quite a long time because of their Oracle integration. There was a very long gap in time before resolution, so the customer was a little bit unhappy about it. They have to be able to foresee these types of use cases and ensure that they have a stable tool that is able to cater to my new ones.

There are some complexities with the initial setup of this solution. Most of our installations are done in our client's network environment, and there are challenges because there are two or three parties involved. Our IT team, the customer's IT team, and Automation Anywhere are involved. With the different stakeholders, we have to ensure that all of them are in sync and able to complete the installation on time.

We have seen ROI. In fact, before starting automation we performed an initial feasibility analysis which resulted in our proceeding with the implementation. Most of our deployments see ROI between six and nine months.

I will be focusing more on the artificial intelligence and analytics part of this tool that they are bringing in.

For anybody considering this type of solution, I would first suggest that they look at what kinds of processes they are trying to automate, and then look at the right tool. It depends a lot on what the process is. For standard ones, this is a mature tool so they can use it. However, for a very mixed set of processes then you look at the specific tools for those types of automation.

This solution is good, but there are still more features to add. There are some use cases that I cannot handle, otherwise, the solution would be perfect.

I would rate this solution an eight out of ten.

The primary use case is data extraction: How to extract the data and run the components alongside it.

I have been using version 11 Community Edition, which is good. After coming to Bangalore and this morning session, they showed an example of A2019, which is the latest version. That is a game changer. What we did not have in the previous version has included in this version. I had a little preview of all the changes, and I'm pretty impressed by it.

Automation Anywhere has a Bot Store. E.g., you can download the bot from the Bot Store and utilize it's data extraction capabilities. You can extract unstructured data through IQ Bot. Getting unstructured data is not difficult. I once obtained an 84 page PDF file using an IQ Bot. This was just the trial version, and it was really good. I was able to get all the circuit IDs and properties that wanted in a simple CSV format. I had not seen anything like this before. When compared to other platforms, such as UiPath, they don't have these capabilities right now. They have activities like PDF extraction, but that's not good enough. That is a reason I'm referring Automation Anywhere as a game changer.

I would like more cognitive abilities, artificial intelligence, and machine learning. E.g., if I see you, your facial recognition has to be there. If I send your picture, it should tell me your name, where you are from, and when I met you because we forget people. It should have these type of capabilities. 

Stability is a key factor. It is pretty stable. After they launch the cloud version, whether you are in my country or I'm in your country, it won't matter. You can access it anywhere. You won't need a version to download or install. 

Right now, I have it on my laptop, but when it is on the cloud, it will be more stable. Anybody will be able to access it. That's the beauty of it.

The scalability is pretty impressive. You can scale it from one computer to hundreds of computers. You don't even need Citrix. Once it is on the cloud, you can access it from anywhere. 

Automation Anywhere technical support is pretty good. I would rate them as an eight out of 10. I'm giving them an eight out of 10 because this community is still developing right now. I will not say it's fully developed. We are in a market where other contenders are also there. It is a very neck and neck competition between UiPath, Blue Prism. and Automation Anywhere. Between them, somebody is good at some things, and somebody is good at others. That is why I cannot give the support a 10 out of 10. However, because of this product's features, I would rate Automation Anywhere as a 10 out of 10.

My sales team did the decision-making. We are in negotiations for some other clients, as well.

Our previous programs have run successfully with it.

I've used UiPath as a developer. Now, I'm using Automation Anywhere as well. When I compare both, the biggest point is cognitive abilities. The IQ Bot is the best in class. You won't find that even in UiPath. 

All the available versions of competing automation tools are available, UiPath or Automation Anywhere. Download them and think about it, then decide for yourself. 

Cost cutting is the primary reason to look at getting an RPA solution. Humans are not intended to do just manual work. If I give that manual work of 14 minutes, 30 minutes. or one hour to some bot, and it can do the work without any problems. That time is now yours, and you can do something else. You can build relationships, you can have a friendship with somebody, or you can do something nice. This is what we humans were intended to do.

I'm certified in a UiPath, and now I'm going to gain my certification in Automation Anywhere.

We have processes in our company that are manual and redundant. We need to reduce the time and improve the efficiency simultaneously. These will be the best use cases for automation.

We picking processes that are more manual and consume more time. We pick a case where it consumes more time when an individual does it. When an automation platform with a bot does it, less time is needed and it is more efficient. This way we have reduced manpower on these manual tasks. Individual workers can then pick up other work instead.

It is very user-friendly. Nobody has to sit down and work on coding. We have a drag and drop option where anybody can understand it. That is the advantage of Automation Anywhere.

We don't foresee any issues with the stability. The support team has given us their guarantee.

The processes that we have chosen in the initial phase are limited to certain regions. We have categorized them to phase one, two, and so on. Once phase one is good to go and we get good results out of it, we have plans to scale up to phase two, then so on. We have categorized the processes into regions, like Asia, US, EU, etc. Going forward, we will be implementing globally.

We are getting good support from the Automation Anywhere team. We have not found any cases or issues until now. They have been implementing and supporting us is in a very good way. 

As of now, we have developers who are supporting us from Automation Anywhere. They are very knowledgeable enough to understand our process requirements and build a solution for us. They interact with our SMEs on a regular basis. Once we implement the process into production, we will need continuous support from the technical team. We look forward to working with the same support going forward.

The initial setup was straightforward.

Giving access to our internal websites was not simple during the initial setup, but we could track the issue. After sometime, everything was streamlined. We now know for our next automation project with Automation Anywhere what has to be done because we have better clarity.

We have seen ROI in terms of cost and time with a couple of our projects.

We have a couple of projects with UiPath and Blue Prism. We also took Automation Anywhere as an option. When we compare other projects on other platforms versus Automation Anywhere, the technical support we are receiving in terms of efficiency, and even that they are giving us good price. This is what we are looking for. Therefore, we have plans to move our other projects, which are on UiPath and Blue Prism, onto Automation Anywhere.

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.

Currently, we are focusing more on finance, shared services, and interpretive related ideas. For accounting and finance statistic, we have reconciliation specific processes, such as rates uploads into systems. The majority of our development is on SAP and Excel. We are focusing on the financial services area, so our use cases are more related to finance and accounting. These are the use cases developed by the development team.

We are using an on-premise deployment model.

The main agenda for using the RPA is to see how we can get the benefit from reducing human capacity as well as quality output. These two are the major focus for us and what we are achieving.

Timeline-wise, it normally takes a long time to develop. With the AA and RPA concepts and their ready-to-use components, we can deliver a bot within couple of days or within a week time frame based on the use case.

It is easy to use and developer-friendly. The development time is very short. If any system needs to be changed or any functionality needs to be incorporated to any of the technology, it usually will be a long process, like months. With this innovative tool's automation, it is very dynamic, easy to develop, and deliver results quickly. With some of our use cases, we were able to deliver within the time frame of two to three weeks, which is the biggest plus with this tool.

There are good MetaBots available in the Bot Store. We were able to leverage them, as well as established our own reusable components. Considering that, it is easy to add on any software or applications that sits in the system.

We would like to have the Excel plug-in. We have a challenge with unattended bots in development which will be deployed on virtual machines. End users ask, "Why can't we run the bots whenever we need?" The new concept for getting attended bots as well as the Excel plug-in will solve this problem, but we'll wait for 2019 version, which may be a better solution for the business.

More structured and unstructured data collection will be a challenge. While we have the IQ  Bot tool, the success rate at the beginning will be lower. It will be around 20 to 30 percent at the start because you need to train the bot at regular intervals. Of course, this depends on the data. This area could use be improvement.

The marketing strategy is directed toward end users. These leads to confusion in the organization regarding, "Who needs to develop?" Is it IT or the business? This causes friction within the business. Whatever the approach, it is important to show how to get the most benefit out of the tool. There should be a clear roles for IT and the business when using the tool. This way teams and structure can be better established in a business.

For attended automation, there are still questions to be answered: How it is going to maintain the queue? E.g., there are 20 users who want to process their own processes, and when they trigger things, how will the Control Room react? How will bot work distribution happen? These things still need to be looked into, but conceptual-wise, attended automation is really good.

It is confusing: Who needs to develop the bot? The business or IT. At the basic level, the bots can be created. However, once they are moved into production, you have to make sure that the bot is stable and running 24/7 without any issues. Therefore, a lot of care is required due to the amount of controlling mechanisms required.

There are a few problems with deployment and maintenance. When it moves to other systems, the consistency will be somewhat lost.

RPA is decently established and stable as the market is coming up with new features. However, the unstable area is more the IT part of it where a lot of research still needs to be done, especially in the case of artificial intelligence. 

When we run bots, sometimes the systems will go down. Maybe it is because the same functionality worked once or even regularly, but then all of a sudden there will be an issue. It might be a network, latency, or some other issues. Still bot stability needs improvement. These are very rare situations. It works most the time, but one time it will fail and we don't know why.

When I talk about RPAs, it is to say, "Can this problem be solved with RPA?" Scalability-wise, we are in good shape. 

In terms of AI incorporation, this type of scalable incorporation would be benefit everyone. The trend looks like we are going to reach to this point in a good manner.

We were able to put more than 40 bots into production. There are around 20 more in progress. On average, we were able to save around 25,000 hours of manual efforts.

The technical support's response is very good. They gave back solutions quickly. We haven't face many challenges when using the tool. So, we haven't interacted much with the technical team, maybe two or three instances. 

We looked into moving into RPA because it was the trend in the industry.

We do regular acquisitions which leads to a lot of duplicate roles and resources along with similar activities. With this approach, we can streamline our processes and bring uniform processes across the organization. We have been able to establish this. If we use the bots on a lot of manual efforts, it will reduces effort. Going forward, we can use the bots in a better manner by using them for the strategy of delivery and appointments.

We started this journey with a PoC. For three months, we tried understanding the tool and its capabilities. 

The initial setup is not complex for the tool setup. The struggle points are establishing the right mechanisms to identify the candidates and prioritizing things. 

In April, we started the pilot. By July, we had the software as well as the use cases that we needed. We got the licenses in July or August. It took us at least a quarter to establish systems and resources. Then, we started delivering the bots from December 2018. It took six to eight months' time frame from PoC to first bot deployment.

For our bot creation process:

A business user, whoever is doing the manual process currently, will send their request with the details of the use case. Those details will be assessed by IT and the business functional groups to measure what will be the man-hour savings. Also, is it a possible candidate for RPA?Based on those measurements, we identify candidates for RPA, then we determine if they meet the current threshold of 500 hours. If it is more than 500 hours, we consider that a candidate for RPA. Based on that criteria, we identify and prioritize it. Afterward, it comes to the development team for development.

If we had been alone during the initial setup, might not have been that successful. However, when we partnered with the other groups, like consulting firms, then we were able to get the right mechanisms in place within a short time.

We did the deployment in-house.

We have a good dashboard to measure ROI. Whatever investment, licensing, and resource costs together are put in for development and delivery, we are still at an ROI of 250 percent.

To measure ROI, whenever we get a use case from the business when we do an assessment, one of the factor that we capture is the time saving. We try to measure and apply the country rates for the locations where they are doing manual efforts. We measure the time savings by applying the country rates and deriving the hours and value.

The time that it takes to develop and deliver is within two to three weeks.

It has good licensing costs which are average for the market.

We did try out UiPath, which is a good solution. 

We also look at Blue Prism.

We like Automation Anywhere's end user experience. We thought Automation Anywhere was the better solution for developing bots in the long run. It is a centralized tool because of its Control Room. It makes sense to have a solution where everything is in a centralized repository. AA has a more future-looking perspective which will help them in the long run.

We currently are not evaluating any other vendors.

When we saw the tool capabilities, we were so excited. We tried to start using them but we needed to have the right structure and mechanisms in place from the beginning to identify the use case for prioritizing. This plays a major role. 

If you are a big organization with a center of excellence, you need to bring all the people together. The establishment will play a bigger role than just developing and delivering bots. Developing and delivering bots is a very small portion, which is doable by any individual who has a basic technical background. To be successful in your journey, having the right structure upfront will help.

We experimented a little bit with IQ Bots, but we didn't see much use cases in this line currently.

A lot of people interact with RPA and the industry is really excited about it. However, you need to pick the right candidate to be successful in your journey, along with the right framework for the development. This will give you a good output. This is what the business needs to test. Pick a solution based on the organization's needs as well as the right approach. Have an assessment with an approach framework will help.