We use it for P2P, AP, O2C, AR, inventory management, finance and general ledger, and HR.

Moving forward, we see opportunities to operationalize AI within our organization for loss cash discounts, payment term mismatch, credit blocks for vendors, duplicate invoices, accounting entries, and invoicing in SAP.

By implementing Automation Anywhere, we wanted to achieve productivity and decrease the complexity of the processes. The key issue has been the complexity. RPA is not meant for complex processes. When a process becomes complex, we face a lot of errors. That creates slowness of processing, some interactions at critical moments, and frustration in the business because the job is not done. As an alternative, we have to work manually.

We built many complex bots, and that was not the best strategy. It is better to simplify and then automate, and not automate to avoid simplification. When you take this wrong approach, you have to deal with many technical issues, and you are not able to leverage and benefit from the other tools as part of the automation itself. In the business roadmap of an RPA project, there should be some reporting or dashboards of bots' portfolio so that you can see the percentage of successful processing, the rate of failures per bot, and the rate of exceptions. There should also be something to measure the return on investment to be able to say that this bot is meeting expectations and productivity. It was worth it to invest in this bot, and it costs less than manual work. If the bot is always facing issues, it will be better to come back to manual processing. We should not move from manual to automation without thinking about simplification. We need to simplify first and then automate.

We have a centralized infrastructure, but we have a decentralized business strategy. We gained 60% productivity, which is at a high level.

Automation Anywhere is easy to use for business users who do not have tech skills, but first, they need to be able to play the role of business analyst. You should not have many points of contact. You should have a single point of contact, which we call SPOC, and this person should be a business analyst. This single point of contact should collect all the requirements and needs and be able to communicate them in a structured way in order to enable the solution team to tackle the points. It is easy if the person who is supposed to do it follows the learning of the business analyst and is able to speak English. We have English speakers because we are in a multinational group. They should also have a minimum level of experience in IT or in general business. If the training is intensive, it takes three months to train non-technical employees on Automation Anywhere usage.

The RPA automation itself is valuable. We are not using the other components that are part of the platform much because we want to first stabilize the platform, the environment, and the infra.

It could be improved in terms of the global analysis of all the issues caused by the dependency components. For example, if bots are running on virtual machines on Microsoft Windows 2019, sometimes an issue might come from the virtual machine. Automation Anywhere should work closely with Microsoft or any other editor with which there are some issues occurring and stopping the bots from running properly. They need to collaborate together to enhance and improve the platform and the dependencies. It should not be that because the problem comes from Microsoft, Automation Anywhere does not tackle the issue. They should tackle the issue even when they are not responsible 100%. Microsoft or any other editor should work with Automation Anywhere.

I would like them to include process mining.

I have been using Automation Anywhere for three years, and I have been using UiPath for two years.

I would rate it a five out of ten in terms of stability because of the issue of dependency components, such as Microsoft components.

I would rate it a seven out of ten in terms of scalability.

Their support can be improved in terms of understanding the issue more deeply and involving enough resources based on the criticality or urgency of the issue. They should involve the right resources and the right number of resources. If we need an architect, they should bring us an architect. If we need an engineer, we should have an engineer in front of us. They should provide the right person at the right time.

I have worked with UiPath. The move to Automation Anywhere was not my choice. It was a group choice.

We have a hybrid cloud. The implementation is easy if you are business-oriented, you first tackle simple use cases, and you involve all the teams. The complexity is always there, but to have less complexity, it is important to ensure these three elements.

We include people from development, monitoring, management of development and monitoring, central IT management, and central business management.

In terms of upgrades, it is difficult to upgrade Automation Anywhere. The upgrades of Automation Anywhere are sometimes not adapted to the clients. They sometimes choose to upgrade the platform during a critical period, such as accounting month-end closing. It is definitely not the right moment to launch the upgrade. Automation Anywhere sometimes pushes general upgrades during critical periods. The best will be to take into account the constraints of the clients in order to not make it difficult for them.

In terms of maintenance, if the bots are running 24 hours a day, you need three people or at least two people for monitoring. The upgrade of bots requires one developer.

You get a return on investment only after 18 months. You can get 50% savings.

It depends. For example, for my group, we are centralizing the infrastructure in Paris. Our contract is signed with Automation Anywhere in France. The currency and the pricing of Automation Anywhere in France can appear beneficial and interesting for Germany and Scandinavian countries, but when we share our infra and are internally charging other countries such as Poland, Brazil, or some other country with a lower currency value as compared to Euro, it becomes less beneficial. They would prefer to sign the contract directly with Automation Anywhere because they will benefit from a price that is as per their local market.

The price works well for France, but it becomes a bit complex when you centralize it for all the countries or groups. In the international context, you have to propose something a little bit tailored for some countries, such as Romania or Brazil.

When it comes to automation and AI, I always think about being business-oriented. Always start with the needs of the business and do not automate just for automation. You have to think about relevant use cases and also scalable use cases. In a multinational group, it is important to not think individually. This way you can collaborate more and reuse more things. You can reuse the components that have already been built. It is also economical.

Each center of automation should have a governance plan. The governance plan should be very precise, and it should expand the roles. Each stakeholder should know what to do, when to do it, and how to do it at each cycle or phase. After that, you should come to the functional and technical aspects. Without a governance plan, nothing is possible.

Overall, I would rate Automation Anywhere a seven out of ten.

We use Automation Anywhere to track the travel and locking of our devices.

We implemented Automation Anywhere because we needed a way to track our devices and ensure they were not going beyond their boundaries.

Before Automation Anywhere we were manually tracking our devices and now it is done automatically.

Automation Anywhere helps to save a full day. Automation Anywhere helps save costs by allowing remote work and not requiring a person to be at the machine.

The efficiency we get with Automation Anywhere is valuable.

The Automation Anywhere calibrating needs to be more user-friendly to avoid human error.

Non-technical people can not use Automation Anywhere.

I have been using Automation Anywhere for one year.

The stability of Automation Anywhere depends on the environment it is used in. For example, in hot environments, there can be deviations.

The technical support is good.

The initial setup was a little complex until we became familiar with the process.

The deployment took one week and required two people.

Automation Anywhere is reasonably priced because it can sustain us for a long period.

I would rate Automation Anywhere eight out of ten. The technology is improving every day.

With the right tools, it is easy to upgrade Automation Anywhere.

Maintenance is required for Automation Anywhere to ensure proper functionality daily. Two people for 20 minutes each day is enough to oversee the maintenance.

I recommend completing some courses and shadowing experienced Automation Anywhere users to gain hands-on experience with the automation process.

We use Automation Anywhere to process data entry from our government website.

We implemented Automation Anywhere to reduce human effort and cut costs.

Automation Anywhere offers a complete solution, encompassing both development tools and a control room for managing automation.

Automation Anywhere's front end is designed to be user-friendly for non-technical individuals, while the back end remains under the management of IT.

Several of our projects incorporate generative AI, and while we are new to this field, it has proven beneficial thus far.

The integration of APIs in Automation Anywhere is easy and works well.

We integrated Automation Anywhere with some of the business applications which was straightforward.

Automation Anywhere has helped save time.

The license cost is high and needs improvement.

I have been using Automation Anywhere for over two years.

Automation Anywhere is stable.

Automation Anywhere is scalable.

The technical support is good. The few times I called them they were able to promptly address my issues.

We switched from Automation Anywhere to Power Automate because of the price and more functionality with other Microsoft products.

We were not able to migrate from Automation Anywhere to Power Automate. We had to recreate everything from scratch.

I prefer Automation Anywhere to Power Automate because it offers a more comprehensive set of features, performs reliably, and provides deeper insights.

The licensing cost for Automation Anywhere is high.

I rate Automation Anywhere nine out of ten.

While Automation Anywhere offers training and community versions for learning and experimentation, it is not user-friendly for non-technical users.

No maintenance is required.

I use Automation Anywhere for SAP, email, Excel, and web automation. We first try to understand the process and check whether it can be automated. Some processes require human intelligence and a human touch. If it's a completely goal-based process, you can consider it as a potential use case. After that, we conduct a complete analysis, based on which we set up the modules and proceed to development.

Automation Anywhere helps us save time by replicating manual processes so our users can focus on other areas and perform meaningful work. It helps us automate repetitive tasks. We started with version 11. After that, they upgraded to 2019, and now there is Automation 360. Clients were frustrated with version 11, but 360 has a lot of good features. When 360 came out, the clients needed to spend money on the migration because they had to do some testing.

It has saved the clients time. I would say reduces the time spent on these processes by about 30 percent. I can't say how much they save because I'm a developer and not involved in the business side of things. I don't even know what the license costs.

In one of our client's use cases, the user needed to log in at 6 a.m. because there is a trigger in Salesforce that happens around 9 a.m. Before 9, they have to do all the manipulations and place the files into a particular location. She had to start early in the morning to get all this work done. Now, with Automation Anywhere the bot handles all of this. Her job is so much easier.

I like Automation Anywhere's document automation. It can distill or scan documents and convert the information into a structured format. The solution doesn't require much of a technical background. I'm from a mechanical engineering background and don't have any prior experience with coding. I only know the basics of SQL. Even a business user who is willing to put in some hard work can learn and do some small things. The learning curve depends on the complexity of what you're trying to do. For me, one month was enough to understand the solution.

We have begun exploring Automation Anywhere's AI features, but we have some limitations. We need to adopt rule-based automation, and there are still some use cases we cannot do. With AI, we can do some more use cases. We have done some POCs, but haven't done any projects where we integrated ChatGPT because we cannot put some of the things as a rule.

It's easy to integrate automation into workflows and APIs. We just need to know where to pass the parameters or the details. If you have that knowledge, it will be easy.

Automation Anywhere's stability could improve. It isn't completely stable, but it's getting better daily.

I have used Automation Anywhere for four years.

I rate Automation Anywhere seven out of 10 for stability.

I rate Automation Anywhere support nine out of 10. I have raised multiple tickets with Automation Anywhere, and they usually respond within hours.

I previously worked with AutoIQ and Blue Prism, but it was a while ago.

The deployment time depends on the process. If the processes don't have any dependencies, we just need to move the code to public and schedule it with the necessary configuration. The configuration is related to the process, not to automation anywhere. The processes require some maintenance after deployment. The number necessary to maintain them depends on the client.

I rate Automation Anywhere nine out of 10. It only requires scripting for complicated jobs, but non-technical users can handle simple processes or those that are moderately difficult.