Right now, we have two business units which use it for automation, mostly for:
- Back office
- Shared services automation
- Accounts payable
- Accounts receivable
- Most finance functions.
Right now, we have two business units which use it for automation, mostly for:
We have two different business units which have already begun their journey. One has been doing it for two years, and another one for one year. We have another two business units which will be beginning their journeys this Summer. Certainly, the value of it has been proven already in the business units which have already started their journeys. They have seen the value in terms of automating some of their redundant, important processes. This has allowed some of their users to move onto more value-added activities.
The most valuable feature is that it is intuitive. It is designed so business users can use it with a drag and drop functionality to develop automation of business processes. Since they are the experts on business processes, there are probably the best ones to create the automation.
They designed the bot creation process where we can drag and drop and all of the commands are available to us on the left side of the screen, but in some ways, it can be overwhelming. There is a lot at a developer's fingertips to do their development process.
I would like the ability to extract the code. You can go line by line, then open up each line of code and dig into the details, but it would be nice to extract all of the lines of code and all of the details into a document so we could read through everything. Right now, there is no way to really consume all of the code at once, except line by line, which can be fairly time consuming if we don't really know what we are looking for.
As we deploy more solutions and take advantage of some of the features, like the Credential Vault, where we are introducing new administrative processes, we continue to have to go in and change passwords on a monthly basis. Tools that would make these administrative tasks more streamlined is an area where Automation Anywhere could really add value.
I love the new features that they're offering and the direction that they're going. We've tried to deploy some of them. Sometimes, we're running into some bugs in different things, so they haven't worked out all of the kinks yet. Hopefully, they can get some of these things resolved and continue introducing new features like they have been.
Our first business unit who started their journey two years ago went from one bot initially to about 55 over a two-year period. Typically, they were averaging a new bot about every two to three weeks. That was with a team of five to six people sort of dedicated to the process. We have had consistent growth with our numbers over that time.
We have been pleased with the technical support. Their response times, capabilities, and patience when working with us, taking the time to understand the issues, and helping us to resolve them. This has improved over time. We are encouraging our users to use them as a resource when they do have questions or problems.
I was involved in setting up our upgraded environment for the new version. The documentation that they provided us was very thorough. We chose to go back to our integrator (our consulting company) to help us build our new environment, just so we would have ready resources available if we ran into questions. However, in this situation, we were able, from start to finish, to build the new environment without many problems, by just following the documentation.
We did initially use an integrator (consulting company) to do our training. That was a very important part of the process, and it helped us be successful.
Automation Anywhere is a great tool. I have been in IT for 30 years, and am amazed at how far we have come with technology and tools to help us do our jobs. The ease of use and the power which the product offers you in a matter of minutes, if not just an hour, and what you can create with it.
It integrations really well with other applications, as long as you have access from the same computer which you're running the software on to your other systems. Then, it can interact with those other systems just as if you were any user who is on that same computer. From this aspect, it is more powerful than other tools which I am familiar with.
We are just starting to look into the solution's cognitive document processing by doing a proof of concept.
Early on, I did try a few of the Automation Anywhere University courses, mainly to get familiar with what was available, so I could guide others to the website for training. At this point, there hadn't been much there that I needed for myself. However, we have looked at the courses, and we are encouraging a lot of our business users to take advantage of the tools.
The important thing about any RPA tool is it has to be a collaborative effort between IT and the business. It needs to be driven by the business, or it won't be successful. An important overall goal or strategy to have as you start your journey: Have good buy-in and ownership from the business. They have to want to do this and take advantage of this new tool.
We use it enterprise-wide for HR, IT, and in the front-end of our transfer agency. The bot helps organizes certain HR classes, letting the organization know when classes have not been completed. We have uploaded certain fund model data to third-party portals. We can set up new accounts in less than a week, where it use to take months.
At a very high level, because of how we've implemented it and how we work with our business partners, they are now looking for ways to help do the automation. Additionally, we've adopted a bit of a federated model, where once we start working with business partners, we start training them on how to use the tool. Therefore, the tool has more of a widespread use around the organization, helping people rethink their jobs.
It integrates with different types of applications, so we can automate our business partners' redundant, repetitive tasks.
It is very simple to use. We have people that we trained who had absolutely no development background at all and are now using RPA. They are using it and developing their own solutions.
We've had people who already had a development background. They self-trained and got certified in about three days, so it's pretty easy to use.
While the Automation Anywhere University is good, the estimates of the time that it takes to complete it are a little low, especially when you start watching all the videos thoroughly. One of the courses that they said would take six or eight hours was closer to 16 to 20 hours.
I noticed that from version 10.5 to 11.3 the number of clicks to start a bot through the Control Room and Schedule Manager have increased. In certain cases, I would like to see that become simpler, faster, and easier.
I would love to be able to schedule things based on business case. Right now, the Schedule Manager is either once a day or pick days of the week with times. However, in the financial industry, I sometimes need to run something on the third business day of every month. At the moment, I don't really have a way to set that up in the Schedule Manager.
I would like to see some improvement in error handling. That would be great. Sometimes, the errors that you get back are awfully generic. It is like you have to do a lot of research to figure out what the issue is.
I would love to see a little smoother integration with some different types of platforms, technologies, and user interfaces.
The stability is getting better. We had some issues, especially because when we went onto version 11.2, there were some scheduling issues. So, very recently, we upgraded to version 11.3.1.2, and it seems to be a lot better.
The scalability is good. It is very easy to scale. It doesn't take us hardly any time at all if we need to spin up a new Control Room or Bot Runner. The slowest part is probably on our end, getting the hardware.
It took us two years to scale from pilot to the number of bots that we are currently using. I wasn't involved in the early days of the PoC. I came into the group a little later after that, but now, we use a federated model. We were sort of the center of excellence for it, working with our business partners. In a number of cases, our business partners are now developing their own bots. We have developed some, where the business partners didn't have much of an interest to doing the development. They wanted to be involved in the creation, so they understood it, but they didn't want to do any of the coding in the background, so we do it for them. We do all the production support.
I like to go by actual executions, not number of bots, because we have some bots that need to be executed multiple times during the day. Last time I looked, we were well over a 100 different executions in a week.
The technical support is great. I have worked with a couple of different people who have been absolutely phenomenal, helpful, and have solved so many of our problems.
When I have a serious production support issue, if I need to escalate it, I usually receive a lot of good help from some great people to get our problem resolved. Sometimes, it takes a while, but I get it. Everyone's environment is different, and it's hard to know everything about how everyone has their architecture setup.
They've started up a user community recently. I haven't investigated that much. I really want to do that, but I always thought that a user community where the users of the product always get together, talk, sort of brainstorm, and come up with other suggestions for the tool would be great. However, I believe that has just been started. I just haven't had a chance to go look at it yet.
We weren't using a different solution before this. Automation Anywhere was our first RPA tool.
We wanted to remove a lot of the drudgery out of people's lives. Someone copying files from one platform to another or taking data and manually entering it from one system to another was not a good value savings. A human should be doing stuff that is more creative and requires human thought process. We wanted to enable our organization to improve overall. So, we figured an RPA solution was a good way to start on that journey.
When we went to version 11.2, which we set up brand new, if I had to do that myself, it would have been a bit complicated. I worked with an installation specialist from Automation who was awesome. He made it very simple. We had some of our own server and DBA personnel on the line, and he documented everything for us. At the end of the day, I had all of the information that I never had on our original 10.5 environment, which has made it a lot better.
Originally, we used HCL Technologies. At a high level, the original implementation went pretty well. Our problems were other things. We started having more issues around coding and our expectations on thought leadership from the vendor, because they were the ones originally doing the coding. We were the business partners to them. As we began to get certified and do some of the coding, we started to realize that there were things that we just didn't know and had a hard time getting some answers. Then, we ended up starting to work with a different vendor. As far as the systems administration work for Automation Anywhere goes, we took that over, and that's what I do.
For time savings, we do time and motion studies with our business partners, so we truly know how long it takes them to do a process and calculate that in.
Depending on the area and department, we use different rates of pay to calculate dollar savings. We also break that down, whether it's actual realized dollar savings or just a dollar savings that's not realized to the department.
There's also risk reduction, which is a lot harder to quantify, so we've taken that to more of a high, medium, and low type of deal, because there's a number of cases where we're eliminating manual keystroke entry. That has created huge risk reduction from our standpoint.
If we count the integrations that we have done with Appian, which is where a lot of our savings is from, we are well over a million dollars in savings. This is from only doing development for about a year and a half.
We have seen a return on investment in a lot of ways. We seen dollar and time savings. There was a department that was going to have to hire somebody to just copy files from one platform to another every day. Because of this automation solution, they didn't have to hire anyone to do that. That was a good cost avoidance there.
One of the biggest things for us is getting the whole enterprise to start learning about RPA and about different ways to think about how they do processes, whether you can improve a process first manually, then make it automated, or if it's even ready for an automated solution. This type of thinking and mindset throughout our business partners has started to make a lot of improvements throughout the corporation, not just in RPA, but in processes.
We're just starting to renew our license, and we were quoted $115,000 without the IQ Bot.
The IQ Bot is another $30,000. This is with very limited pages, as we go through our first projects. The majority of the cost was for ten days of onsite training.
The shortlist would have probably been Automation Anywhere and Blue Prism, at the time. We went with Automation Anywhere because Blue Prism is really good on the back-end, but that's all that they specialize in. We knew that we had to do a lot of front-end type of RPA work with some third-party vendors, which we weren't going to get API calls to. We had to be able to operate with their graphical user interface. Once we made those realizations, Automation Anywhere became our choice.
Make sure you understand what your needs are:
Understand what the different tools from the different vendor do, because they are becoming more similar, but they are still designed for specific areas of a technology, whether it's the back-end, front end, or somewhere in the middle. You need to understand your own needs. Once you understand that, research the various tools thoroughly and make the best choice.
The product functions well.
The integration with other application works really well. We have used it with Appian more than once, and that integration has been very easy to do.
The cognitive document processing is good. We have done a proof of concept. We just purchased IQ Bot, got it installed, and will be starting our first project soon. One of the things that we did learn is reading the imaging was tough because of the DPI needed for the IQ Bot. It's 300. Most imaging systems don't save them that high. They are at 200 or 250, so we ran into issues there. However, as long as we can get electronic documents, it's been awesome.
I have taken some Automation Anywhere University courses. I took the online classes and got certified in 2018, but there are some other courses that I wanted to take that I saw in there. The content is really good.
The bot creation process is easy. It does require more thought if you truly want to incorporate some good error handling in the process. With some of our bots, this is absolutely critical. We have some bots which have very strict SLAs because we are in the financial industry. It is a bit trickier and requires more thought. You can do it and do it well. It's just that it requires more forethought than a typical user would know.
We don't use Citrix.
The primary use cases are for card and HR automation.
For our interorganizational processes, it has automated some of those processes.
The Bot Store has helped tremendously with accelerating integration from other applications. Especially with Workday, which is one of the main applications that we look to integrate.
It automates forms for our customers and our analysts.
They could improve around continuous integration, e.g., Jenkins and GitHub, stating how you could use those products and integrating them into Automation Anywhere. This is one area that we need to see more improvement on. We had to learn a lot of this on our own, as it is unavailable and not documented. I would like for them to be more verbose in putting this in the documentation.
In the next release, we would like to see more error handling functions for the bots, the ability to kill an errant bot, and have more visibility into a lot of the process flows going on in a more automated fashion.
There is a lot guesswork in areas.
The initial pilot was for two processes, which took us about four months. Then, the other processes were more extensive, so that took longer, only because we needed to do more with the process documentation, not so much in the bot creation. It just depends upon the complexity of the process, but also how well-documented your processes are.
The technical support is good, but I would like to see improvement with the documentation.
We did not previously use another solution.
The initial setup was complex, only because of the process that was selected. That took us longer than usual, because it had a lot of cognitive decisions in it. Part of our new process is to evaluate if a process should be automated or not, and does it have more repetitive tasks than a lot of decision making. This has greatly increased how we are able to put a process into play for bot creation.
We leveraged a third-party, as far as our bot creation, initially. That is how we did it. We have worked with partners to create bots.
Before the automation, it used to take about two to three hours. Now, with automation, it takes about 40 minutes. We measure ROI with time.
We also evaluated UiPath.
Take into account your processes. As part of the automation journey, don't look at just the technology part. This is where a lot of people make a mistake. They focus so much on the technology that they forget about "process" of RPA. They need to take a longer look at this and break down the process at its task level to see if it is worth going the RPA route. Once you do this, look at the vendors to see which one provides more in the way of bot creation and scalability, especially if you are in a cloud environment. Then, with the continuous integration, you will need to have a lot of this as you are putting things into production from development.
For ease of use, version 11.3 was an improvement compared to version 10.5. I am looking forward to seeing what 2019 provides for developers.
I would rate version 10.5 as a six out of ten and version 11.3 as an eight out of ten. I would rate version 11.3 higher because there have been changes made to how the bot creation is now done, the interfaces, the ability to utilize the VDI environment, and multitenancy.
It is primarily used for accounting apps. So far, it has been okay. It's for a small implementation.
We have automated account reconciliations.
The most valuable feature is its ease of development.
It's pretty easy for people who don't have a tech background to use. It is one of the easiest tools for them to use. We are using it for scripting, and it is end user based with screen captures. It is a bit easier to use than any of the other tools out there.
There are a few things that could be done better, so we can monitor properly. They need to improve in terms of development and enhancements. We need to get the right feature sets in place as an enterprise.
We would like to use Citrix going forward. We use Bot Runners to scale up, and it gets to be expensive. Using Citrix, it can mitigate costs.
We went through the documentation, it looks pretty easy to scale.
It took six months to scale from pilot to our current number of bots.
The technical support is good.
The initial setup was pretty straightforward. The document was good. Everything went as expected.
The deployment was done in-house.
We don't have an ROI in any of our processes. We are just trying it out now to see if it works.
We haven't had any savings yet. We have been putting more time in than saving time at this point.
Our annual licensing costs are around $100,000 a year.
We chose Automation Anywhere through a process of elimination. We evaluated all the RPA products out there and decided on Automation Anywhere mainly based on ease of use.
We also looked at Blue Prism.
We looked at the Bot Store initially and didn't find much. We looked a year ago, so maybe we will take a look again.
I don't have much experience with attended automation.
We are automating internal processes, mostly at the task level. We are going in and looking for manual work which can be reduced through the use of automation.
Primarily, we have automated finance and cost control related expenses.
We are still in the proof of concept and pilot stages.
We have had some moderate, qualified success, so far. We are just starting out, but we have been able to take an accounting task and clear a very large backlog. Therefore, being completely up-to-date of the task since implementing a bot on it.
The ability to automate low decision, highly repetitive tasks and clear large backlogs of tasks that we could not do with our human staff.
We have had some difficulty with ease of use. As far as getting the overall architecture setup, we had a lot of difficulties ensuring the control room was installed correctly and that we were setting up our runner machines correctly, as well. Some of that was due to our own IT not being fully up-to-date on the process and being properly informed. We also just found the install procedures somewhat cumbersome to use. In addition, we have had some difficulties getting it to interact in predictable ways with our in-house software.
We would like a smoother process for moving bots and tasks between the different development environments, from development to testing to production. We find this to be pretty cumbersome to work through.
We have had some issues with stability. However, we think this is as much on our end as on Automation Anywhere's side. They have been very helpful with their customer service on resolving these issues.
The initial setup is complex.
We are doing everything in-house.
We look at ROI in a couple of different ways: FTE reduction, hours saved of human work, or errors caught. We are also looking at finding errors in our invoicing for our accounts payable team to be able to reduce those errors.
We spoke with a number of vendors.
Look into what the requirements are from an IT standpoint and involve the IT team in ensuring that the installation and setup are handled smoothly. Make sure that the IT team is onboard and invested in a way that makes them a close partner in the automation process.
The bot creation process is pretty user friendly for a lot of tasks, such as the object cloning. I know a number of our developers have felt that it is a bit cumbersome with its logic and variable manipulation. A lot of us want to be able to start typing in directly rather than having to click and drag things, but as far as the core automation functionality, we found that pretty easy to use.
We have not used the IQ Bot.
I have not taken any course on Automation Anywhere University.
The primary use case is process automation. We have automated our reconciliation process.
So far, it has performed okay.
We have automated our processes.
The most valuable feature is its Excel integration.
We have business users who are developing bots using this solution.
It does not easily integrate with customized solutions.
I would like to see more Excel functionality, especially around the copy and paste functions. A lot of our business users utilize the copy/paste special values. We are currently not getting any formatting, etc. It is just a raw data set. To fix this, there are some workarounds that Automation Anywhere needs to build into the app. This would make it a lot easier for us.
Automation Anywhere should better vet their partners and resellers for their packs.
It is pretty stable. Once the upgrades were put in for the latest release, it has been running pretty smoothly in our environment. The key things that Automation Anywhere needs to address is the changes which are in the Microsoft environment going forward and how they are going to address not having Explorer there.
The scalability is pretty easy. It is pretty intuitive for any IT person to scale their environment.
Automation Anywhere technical support has been great. Some of their partner support is less than to be desired.
We did not use a previous solution.
The initial setup was straightforward. There was no need for a reseller or partner to do anything, if they were just going to click the "Next" button.
From pilot to production, we did a three bot pilot, but we did not put those bots into production. We pretty much cut down that environment and started everything back up from scratch.
Now, we have those three bots out in production. They are programmed to be easier and more affordable. Then, we have the rest of our processes that we have identified to take to production for automation that seem pretty easy for the next stage.
We purchased a partner pack. I would not recommend it. The Automation Anywhere support is far superior.
With the bots that we have in production, we have two of them that are time savers. We have a third bot which takes longer being automated than it did with the human process.
At the moment, it is about even time. We are not using it as a money saver.
Start slow. Ensure you have enough processes in the pipeline to keep moving forward. There will be a hurdle to get over, and once you get over that hurdle (learning curve), it will be a lot easier going down that slope.
Attended automation is great. Unattended automation is a bit of a struggle.
We use it for multiple internal processes across multiple functions.
We work with good people who have very defined goals and very defined approaches of how to execute and achieve their goals.
Automation Anywhere takes a lot of mundane, competitive work out of the hands of people, increasing the quality, because it is consistent. It also enables us to have patience with these manual processes.
It has the ability to tag different components within the automation. We built it to track the ROI and stability of the product.
I find attended automation useful.
The product is not the best that it could be. There is always room to improve it a bit more. They are heading in the right direction with their innovations.
It is very stable. The stability of the solution also has to do with how good the developers are from Automation Anywhere and on the user side. So, we've seen an increase in stability, not from the tool, but from the level of the people which are working on it. As our people work with Automation Anywhere, they learn from past mistakes. They have been able to configure the bots better, which then fail less, making them more stable.
It is definitely scalable. What we found worked for us to make it scalable was it has to be programmed by an architect, as opposed to letting it just be in the hands of the masses trying to solve it. This has been our approach.
It took us eight months to a year to scale from zero bots to 100.
We mostly use our own technical support.
When we do escalate issues to Automation Anywhere, we have a good relationship with them.
We did not switch from what we previously had.
The initial setup is straightforward.
We did the deployment.
We measure our ROI through money and time saved. That's how we measure the product's value. We look at the hours performed by humans, and those hours have a cost associated with them. We multiply our transactions by the number of hours it used to take by humans.
Time-wise: We have saved hundreds of thousands of hours.
We chose Automation Anywhere because they are best in class.
Do your research thoroughly.
We are still using people who can figure our bots as their profession. We have not release the product from the ground up.
We don't use the Bot Store.
We use it for our refund department. We use it to initialize payments and everything else that is a repetitive process.
We use Automation Anywhere to automate financial processes, invoices, billing, etc.
Because it reduced the time duration of our processes, our costs went down.
Right now, we have Automation Anywhere integrated with artificial intelligence (AI).
I am certified in the Automation Anywhere University as a developer. It is a good tool. It goes topic-by-topic with real-time examples.
The product has a lot of options and visibility.
I just came to understand that there is a cloud attached to it. I would like to see how the cloud is going to work, because every application is coming out with a cloud version. If you are not on-premise, then you will need to have Citrix automation.
It took one month to scale to the amount of bots which we are currently using.
Initially, the setup is not complex; it is straightforward.
We used a consultant for the deployment.
This product is really useful for me. I recommend Automation Anywhere as a solution.
The bot creation process is good, though it depends on the use case.
I don't use Citrix.
It is our RPA platform. It is the main platform that we use for backups.
It has helped us a lot with our digitized work.
We have automated a lot of the bank's processes.
My team has taken courses through the Automation Anywhere University. The courses have been good. They have helped us, but it could improve some things, like how the courses are designed.
It is pretty stable, but we have experience issues.
We are working on scaling it now.
We use it with more than 17 applications. So, we work it on a very large scale.
The technical support is good.
It took us two years to scale it from the pilot it to our current number of bots. The process was too much work.
We have saved 53 minutes through automation.
It is a very good product.
It is for my partner development. We primarily work in the insurance business. So, we do a lot of insurance back office operations. These are the types of processes that we have automated.
We previously had a lot of manual processes. With the bot, we were able to automate them. Therefore, we are able to see the real-time value in our business area.
We have multiple developers on our team. With its user-friendly user interface, our developers are able to quickly pick it up. The ease of use is really good.
Bot creation is a cool feature. It allows the developer to do complex things.
There are some places where Automation Anywhere needs improve a lot, especially from an integration perspective. We have had to build our own scripts to make this happen, building a bot in Automation Anywhere, along with some scripts. However, we have not yet implemented the Automation Anywhere MetaBots. So, once the MetaBots are implemented in our area, we should be able to achieve more.
If the bots become more stable, we can completely avoid using our additional scripts.
I would like to see the record management, data tracking, and database feature. Some of these have been implemented in the version 11. I have not used the latest release, version 11. Also, if some various cable features which come out with it, that will be really helpful.
I would not give stability good marks. There are a lot of negative things stability-wise. These things need to be improved, especially regarding reliability. When we have a huge end user process or need to automate a a huge volume, the failures are high.
The product is more stable versus older versions.
We face issues when we need to increase volumes. Currently, it is failing for some reason, and we don't know the reason. It fails or stops, then we need to see what is going on. We have to fix that, then our developers need to rerun it. These are mostly practical challenges for our team who uses it on daily basis.
Timing is a problem with the technical support. A person will be assigned, but that tech support person may only be available during our morning hours. In the morning, we might be in a meeting, not able to respond when the tech support reaches us, then when we try to reach them back, the tech support person may be on a call or not in the office. This is a challenge.
The initial setup was complex.
To scale from pilot to production takes a long time because the initial setup process is complex.
I am the consultant who does the deployments.
The ROI is really good. We have saved time and money.
We evaluated Automation, Kryon, and Blue Prism. Of those, we felt Automation Anywhere was more user-friendly. On the developer side, we received feedback that development was quick in Automation Anywhere, which is why we shortlisted them.
Since using Automation Anywhere, I might be inclined towards using another product.
Automation Anywhere is currently a good product. The RPA market is growing.
The integration with other applications is good. There are some complications. With some specific applications, it may not work. We are facing some specific issues, but we have found workarounds.
I am certified in Automation Anywhere University.
I have not personally used the IQ Bot nor have I used any trial version, but the features look really good.
I do not use Citrix automation.
