The setup process is quite straightforward. With agentic AI, we can incorporate APIs, integrate normal automated processes, and third-party tools. The workflow integration process is simplified, offering options to use existing objects or create new ones.

Initial deployment is somewhat difficult because we have to get the framework in place. It is always difficult. The first three to four processes are challenging. Once the first three to four processes go into production, you have a framework and something around which you can work. I think this is the same for all tools because the first time we put a process to production on the client side, we might encounter surprises. We have a dev environment from which we move to UAT or pre-production environment, and then to the final production environment. Whatever tool you are using, I believe that when it comes to RPA, you will find some surprises when you go to production, and it takes time. The first three to four processes are a stabilization phase. Once the first three to four processes go live, you know what to expect in the production environment when you deploy it, and it becomes easy.

I can say the initial deployment of Automation Anywhere is between easy and complex because it takes time, but the vendor was helpful. We implemented it firstly through a partner, and then as time has gone on, we started deploying it on our own. The vendor team, the OEM team, and the Automation Anywhere team helped us whenever we found any issues. They are helpful.

The initial setup was relatively straightforward, especially compared to some other enterprise automation platforms I have worked with. Automation Anywhere's user-friendly interface and developer-friendly design made it easier for teams to get started quickly.

With Automation 360, the experience improved further because of its web-based, cloud-native architecture. There is less dependency on extensive local installations and configurations, which reduces setup effort and simplifies administration.

From an enterprise perspective, integration with tools such as Jenkins and other DevOps pipelines was also smooth, allowing us to align automation deployments with our existing development and release processes.

Like any enterprise platform, the complexity increases when setting up governance, security, credential vaults, environments, and production-grade infrastructure. However, these are standard considerations for large-scale implementations rather than platform-specific challenges.

Overall, I would describe the initial setup as straightforward for basic implementation and manageable for enterprise-scale deployments. The platform's ease of use, cloud capabilities, and integration options helped accelerate adoption and reduce onboarding time for developers and business users.

I find the initial setup for Automation Anywhere simple. I would rate the initial setup as nine.

The initial setup of Automation Anywhere A360 was moderately straightforward, but it required proper planning and coordination because it is an enterprise-level automation platform.

The basic installation and configuration were manageable, especially with the available documentation and support. However, the overall setup involved multiple activities such as configuring the Control Room, setting up user roles and permissions, creating bot runners and bot creator access, configuring credential vaults, setting up environments, and ensuring proper connectivity with applications like web systems, SAP, email, Excel, and databases.

Some complexity was involved in aligning the setup with our organization’s security policies, access controls, infrastructure requirements, and deployment standards. We also had to ensure that bot execution machines were properly configured with required packages, browser extensions, SAP access, database drivers, and other dependencies.

Once the platform was configured correctly, the development and deployment process became much smoother. Control Room helped us manage scheduling, monitoring, credentials, and bot execution from a centralized place.

Overall, I would say the initial setup was not very difficult, but it did require proper planning, environment readiness, access management, and coordination between RPA developers, infrastructure teams, and application teams. After the initial setup, Automation Anywhere A360 became easy to manage, scale, and maintain.

Initially, we started with server support and gradually migrated to utilizing Automation Anywhere's features when transitioning from AWS to the SaaS model, resulting in fixed authentication issues and a significant reduction of nearly 50% in costs, which has beneficially influenced our automation strategy.

We went directly through the license that we have. We work directly with them, and I was at the conference either last year or the year before, which would be 2024. It was in Austin, so I got to meet a lot of the technical people and see what the upcoming products were as well.

My experience with Automation Anywhere's pricing, setup cost, and licensing is pretty positive. The pricing is more on the enterprise side, so I would not consider it a low-cost solution, especially once you scale to many bots and users. However, for a process with enough volume, the time saving and reduction in manual effort can justify the cost. Initial setup took some planning, particularly around bot configuration and integration, but after that, it becomes fairly manageable. Licensing can be a little complex because the cost depends on the capabilities and scale you need.

I was trying to recollect when the most challenging experience I had was when deploying Automation Anywhere. One thing which is part of the design is that we can easily have a different environment with a clear-cut checklist defined for the development team. Some of these experiences can be avoided. We do have a staging environment where we do all kind of checks and balances before we move things into production. The consistency of the environment is very important because sometimes the version we have in development versus in production are not the same for the base platform, because of which our bot is not able to recognize some of the screen elements and that is where it fails. That is where the retake happens. I think if we had some checklist handy, these things could be avoided. I do not think these are platform limitations. This is more with respect to the way we use that platform. If we are using this tool perfectly, we will hardly experience this.

The initial setup process for Automation Anywhere is very simple.

The initial setup required planning around the automation environment, application access, credentials, and workflow requirements. Building a simple bot was relatively straightforward, but testing end-to-end processes and handling exceptions required more effort. Proper testing and monitoring were important for making the automations reliable enough for regular use.

The deployment of Automation Anywhere is not at all complex; it is very good. We deploy bots gracefully and we do not have to take down anything. Everything is done through our DevOps. We do it without disrupting the business. It is mostly a graceful method that we have adopted and we are continuing to do this because nothing has impacted us. There are some things one or two here and there, but overall, it is very good in terms of deployment and not disturbing the business.

The initial deployment of Automation Anywhere is user-friendly. If you have self-learning capability, the wizards are self-explanatory, making it not very difficult to navigate. It is a very low-code environment, allowing flexibility to explore based on the project's complexity. Overall, I believe Automation Anywhere is a very user-friendly tool.

The initial setup is pretty straightforward. From Automation Anywhere, I did not really face any issues. Whatever issues there were, those were majorly application-based, such as changing the environment or things of that nature. From Automation Anywhere side, the deployment was pretty easy. From the tool end, I have not really faced any issues. I have worked on the V11 to A360 migration as well. There were no major issues. Whatever issues we face during deployment are mostly from the system perspective, such as environment perspective or system perspective.

In deploying Automation Anywhere solutions, I have experienced significant evolution over the past eight years. Initially, it was a client-server model that made deployment challenging, but now we benefit from the first ever cloud-based RPA platform, which has greatly enhanced our flexibility in solution deployment.

The initial setup of Automation Anywhere is easy; since it is now cloud-based, we do not have to worry about setups, and we can set up the entire system as production in about 10 to 15 minutes.

I have not seen the upgrade process as I have not directly performed any upgrades. With the cloud, they notify us of scheduled upgrades, often without causing downtime, and inform us about any affected modules, allowing us to manage our processes accordingly.

In my experience, deploying Automation Anywhere is one of the easiest processes compared to other RPA tools. They call it Bot Lifecycle Management, where you build code with a no-code, low-code strategy, then place it in the version control of Automation Anywhere, known as the control room, and configure it as a package or extract and traverse between one environment to another. This is simple and easy for any new developer, and I find it to be a good feature.

Any organization has to think about what to buy, what to build, and how they will be able to leverage the existing infrastructure or bring new things in. For example, if I have a good number of resources and all the capabilities, I will definitely put focus on building. However, if there are some ten features, why should I reinvent the wheel when these features are commonly available in the market? I should go for those features which Automation Anywhere gives as a default part of the package and use them. The ability to bring your own model is very important because nobody wants to be stuck with one model. I am part of an AI team where I head the AI function, and I need to make models and machine learning models every day. I need to fine-tune them and have the flexibility to do research and development with the models and bring my own models. These features help a lot because I do not have any locking. I can bring my own models, use the native feature of Automation Anywhere, and stitch them together to get the outcome.

The decision process is simple. I need to first evaluate how many team members and how many processes are running today in the organization manually. It should not be that only two members are doing the whole process and I need to bring automation. I should be very careful if the number of people doing the same thing daily is high and the volume is high, then I need to bring this automation. Then I will be able to automate the things and convert manual processes to automated processes. I will be able to use agentic or simple RPA. However, these are the criteria which I would suggest everyone go by before deciding to implement automation.

If you ask me which are those top two to three products, Automation Anywhere definitely comes to mind. We have been working with it for the last couple of years now. It always comes to mind that this is something which we should use. It is easy to use and has a lot of a no-code approach, which is where we find it very useful because that is what customers are looking for. It is easy to get the skilled people or train them on these skills. With such a tool, it is always easy to get the right people. Implementations are also easy, and then we can manage it well post-implementation.

I use Automation Anywhere's Autopilot capability, but not extensively, because Autopilot sometimes gives a skeleton, and beyond that, substantial engineering goes into building the solution. Many times it has always involved building from scratch, but that is changing. The feature around using a cloud-like interface to start building code is going to definitely start saving some time.

The setup is easy. Regarding pricing and licensing, we are not directly paying for it since we use the product provided by the end customer, and I believe the pricing is somewhat justified.

I find the initial setup pretty easy to deploy and configure.

The initial setup and deployment of Automation Anywhere were straightforward, with no major challenges during the setup process.

The deployment experience has been good and seamless, as many things have improved over time, and we do not have many issues with deployment.

I was part of the initial setup of Automation Anywhere. When Automation Anywhere was introduced in our bank, I was part of the team. Initially, we hired a third-party vendor rather than directly contacting Automation Anywhere. We coordinated with this vendor who used Automation Anywhere tools to perform automation. After six months, we directly purchased the license from Automation Anywhere. I was part of that team, and my team leader was also part of the setup. We coordinated with Automation Anywhere project leaders and project managers to set up many projects and automate the processes.

I spend about two to three hours maintaining bots personally, but my team's efforts vary with complexity. The initial setup requires significant time, about eight to nine hours for monitoring workflow, but this can reduce to three to four hours daily after four months.

The initial setup for Automation Anywhere is something that can be improved. The starting process has been reported to have some challenges by my peers who have been around since it was onboarded.

The initial deployment and onboarding process was somewhat difficult, but once things stabilized, the experience became excellent.

From my perspective, the initial setup process was a bit simple because we were about to set it up, especially since the technical support team helped us greatly. We integrated our customer database and email system by connecting using app connectors such as Salesforce, Zoho Analytics, and Zoho Mail. After that, we started designing workflows, determining when bots should trigger actions based on connected data. Our first bot was set up for service requests, and generally, the setup was straightforward, particularly because of the assistance from the technical support team, especially in mitigating initial issues.

The initial deployment of Automation Anywhere was relatively easy for my team.

The initial setup required effort, especially for integrating with legacy banking systems. However, Automation Anywhere provided good documentation and local support, which made the process manageable.

Automation Anywhere has enhanced a lot since we first started using it. At the time, it had the client/server architecture. It was not on the cloud. We had to manually install Automation Anywhere on each and every desktop. In 2019, they shifted to the cloud, so we just have to install the bot agent on any computer we want to use as a device. It does not matter whether it is a bot creator or a bot runner. That has improved the installation setup and reduced the configuration time by 80%. Previously, we had to manually install the client and control room and configure them. That was a tedious task, whereas now, because of the cloud, its deployment is very simple and user-friendly, and it has reduced the earlier effort by 80%.

Almost all clients use cloud deployment, but a Korean client has an on-premises setup because they are very diligent about the data. Cloud deployment is easier than on-premise deployment.

Cloud deployments typically take a few hours, around four to five hours. On-premises deployments can take up to two or three business days due to customer environment restrictions and infrastructure limitations. If conditions are optimal, the setup can be completed in one day. For the cloud, deployment time is much shorter, taking only about four to five hours.

The updates happen automatically for cloud deployments, whereas for on-premises setups, we have to download the new release files from the portal and manually do the updates.

In terms of bot maintenance, currently, our team is working for three customers, and there are 105 bots. Our team of seven people is handling these 105 bots. We are doing 24/7 service and daily spend four to five hours on average for bot monitoring and support.

The learning curve of Automation Anywhere was a steep one. It was hard to get used to the software initially, but then after some time, I was okay with everything. Initially, the deployment was a little bit tricky to get used to, but with time, we are now okay. Initially, it was a little bit complex.

I have an estimate for how long it took to deploy it. I estimated around two to three months.

The decision for the software had already been made. I was only involved in meetings to discuss how we were going to deploy programs, design things, and create standards. 

I believe it took six months from deciding to go live with the software to deploying automations. It did not exceed six months to get everything up and running, though there might have been a year of planning. Once I was set for launch with everything in place, the transition from purchased to used tenants happened swiftly, possibly in less than six months.

It is straightforward. 

When it comes to bot deployment, a bot takes two minutes from one environment to another. Moving code between environments also takes only two minutes. However, there are sanity checks. These checks apply to all tools used in automation. Deploying code takes two minutes. We have automated this process, allowing code transfer from test to production with a single approval click. It is seamless.

Bot maintenance is not a tedious task. Once an update is done, we push that into a test or development to check whether it is impacting our automation. In more than 90% of scenarios, it does not impact. In a few cases, there is some impact with the update.

Straightforward, and we were able to apply all templates and best practices when we rolled out the solution internally

The deployment was not difficult. Automation Anywhere helped us. 

There is maintenance needed. You need to keep on updating it as it gets complicated from a security system standpoint. You have to make your software more resilient to handle hackers and to ensure that no vulnerabilities. That's a work in progress, always.

The deployment of Automation Anywhere went smoothly. They were very supportive with the migration of all of our existing automations and also being there and supportive with the development of the new automations. 

The team was fantastic. They're continuing to support and track not only migration, but encouraging us to bring on new automations as soon as possible. We're trying to keep up with them pushing us, which is great.

I was significantly involved in the deployment of Automation Anywhere, being the sole person from my company starting this automation journey, and we faced some initial challenges, particularly with hardware setup when we transitioned from on-premises to cloud, which eventually became smoother.

It requires a bit of technical background from the server and infrastructure standpoint. If someone knows middleware, it is pretty straightforward. There can be hiccups here and there. Especially in the earlier versions, there were a few challenges, but it is now streamlined in A360. Everything is pretty easy.

Upgrading Automation Anywhere can vary in difficulty, with package version upgrades being easier than transitioning from version 11.3 to A360, which is tougher and requires significant setup work, including roles, accesses, and schedules.

My experience with deployment was smooth.

The deployment is very easy. We just need to export the bots and deploy those bots into production. It's very easy with import, export buttons. It's like five minutes. It's very easy to export into Android environments from dev to test and test to prod. It's very easy to move.

The setup process is pretty seamless. Recently, we have introduced the API capability, the code migration utility, which we are using to deploy the bots from one environment to another. It is helping a lot.

We could have a better integration. We have our development environment, and then we need to export that and then import it to the client. So this is a manual process. We would like to have a more automated process, integrated process, where we could have a pipeline where we could, from the production environment, push the version that we want to deploy to production. 

In terms of version control, there are some improvements that can be done there. It would be nice to have more actions and more tools that allow us to have a better release control and showing all the features that were launched on it. 

Having AI right now, it would be nice if we could also automate part of the documentation process. That's something that is possible. Nowadays, we can send a quote to AI and just ask it to explain this or build me a document explaining this code. There is some work that can be done there that can improve the deployment that we are doing through production to ensure that we have everything documented, and have all the version control in place. 

We have an on-prem primary setup, however, we also have cloud-based integrations for some of their advanced features, like document automation. We are currently in the process of going full cloud via migration. That's on our roadmap. And once we get there, since we know the strategy and vision with agentic, we want to prioritize as a firm to get to that model quickly and then just have one pattern to support.

The initial setup was easy. It took me about a week or two to understand how to use it, and that's being generous. The concepts are straightforward and it's very similar to UiPath, beyond a few differences.

We haven't needed to update to a new version. The major update from on-prem to cloud was done before I came. 

The more minor upgrades were painful, yet not at all due to Automation Anywhere. ERP updates and things like that required us to test every bot. None of that was a fault or a problem with our Automation Anywhere. The rest was relatively smooth and straightforward, and the control room updates were relatively smooth and straightforward. This last update, we had a little bit of a hiccup. However, working through support, we got a workaround until the fix can get into place.

There is some maintenance needed on the bots. That's not the software's fault. The maintenance effort is quite low compared to what I was used to. 

Currently, we have two control rooms. One is an on-prem control room, and the other one is a SaaS or cloud control room. We are using both.

The SaaS option is evidently easier because we do not need to manage servers, issues, or restart services. We prefer SaaS for these reasons.

In terms of maintenance, the platform upgrade from one version to another version is not difficult. We started with version 21 of A360, and we are currently on version 35. Most of the updates in the SaaS environment are automatic and happen during the night hours. Most of the time, we have not seen any issues. They went smoothly, but sometimes, there were some terminations and other issues. If those issues are also taken care of, it will be very smooth.

For the SaaS control room, there is not much maintenance. We are doing maintenance only in terms of the code. In terms of platform, we do not need any maintenance for the SaaS control room. For the on-prem control room, there is a lot of maintenance. Sometimes, the services go down, or the communication between the application and database server has problems.

My experience with deployment is positive, as we need to deploy into several servers; for production or testing environments, there is a feature called export that allows us to export our bot file as a ZIP file for easy import.

It was already deployed when I joined the company. 

The upgrade was extremely challenging. Moving from version 11 to Cloud took considerable time. The migration from V10 to V11 was difficult, and V11 to Cloud was even more challenging. We hope the Cloud version will make future transitions easier since it's not on-premises.

With the cloud platform, we don’t require much maintenance. However, the bots we create do need significant maintenance. The time required for maintenance varies. Some automations are very stable, while others may not be due to issues with the developer’s execution or the quality of the target application. It's not Automation Anywhere's fault, but the platform itself isn't very adept at performing self-maintenance.

My experience with the deployment of the solution is positive; it's fast, and we have not encountered any problems related to that.

My experience with the deployment of Automation Anywhere was good. I have no complaints there. It was very straightforward.

Its deployment is complex on-premises. We need to have our own database. Cloud deployment is straightforward. Everything is handled by Automation Anywhere, so you don't need to worry at all. 

On-premises setup requires maintenance, whereas cloud deployments don't require maintenance. You don't have to worry about upgrades with cloud deployments, whereas an on-premises setup requires a few things. You need to consider hardware maintenance, especially if it's a bare metal infrastructure. In cloud scenarios, you only need to consider licensing and database maintenance.

Bot maintenance depends on the changes in the process.

The initial deployment of Automation Anywhere is straightforward and can be completed in one week, assuming prompt support from the infrastructure team. The only potential delays stem from internal bureaucracy, not the tool's limitations.

The deployment process was a bit difficult in the beginning, but after we passed it, we got a clearer picture. If we were going to do it again, it would be much easier. It was a bit difficult in the beginning, but later on, when we figured out how to make it work, it became much easier.

We did not encounter any issues with maintenance yet.

There are two approaches for the initial setup of Automation Anywhere. The first one is the cloud approach and the second is the enterprise one, which is basically on-premises. On-premises is very easy as we have to set up the SQL database and the application, following all the steps. For the cloud, you do not have to set anything; just the proper configuration of the system is required to use Automation Anywhere.

The deployment was fine. We had to get some servers set up to deploy some service accounts created to have the bot runner licenses and set up some users in the control room. It really wasn't that complicated.

The setup is easy because all updates and upgrades are synchronized with the newer versions.

The initial deployment of Automation Anywhere is straightforward, conducted through the Control Room, where understanding task scheduling is vital for effectiveness. While verifying production readiness takes one day, the actual transition to production is a simple switch.

The deployment is ongoing. It's not difficult. You have all of the information you need to implement successfully. 

Standing up the service itself had no significant challenges. There were a few small challenges, however, nothing significant that were nonstarters for us. Our teams were able to work around any issues. The biggest thing we had was was enabling SAML authentication to work with our identity management services. 

Other than that, standing up the service, connecting the host controller to our local VMs, etc., that was easy. There was a little bit of network stuff, and some of DevOps stuff. Thankfully, we have a great DevOps team. Working with Automation Anywhere is largely straightforward and seamless.

It's been great. It's been flawless. We've had great integrations into Genesys and ServiceNow. Deployment has been wonderful.

We have a separate team that handles the integration and setup. We are still on the on-premises version of Automation Anywhere. We are not using the cloud version. We have virtual machines running for us developers. We have a development environment where we use our own dedicated VMs. We develop automation on these VMs, and then we push it through the UAT and the last life cycle for production.

As far as I have heard from our team, they said it was easy to implement.

We started with version 11 of Automation Anywhere back in 2019. When I joined the team in 2022, we were migrating from version 11 to A360. I directly started in the migration phase where I could help with my fresh knowledge, because I was one of the first ones certified in A360.

If you are deploying the client on a virtual machine, it is very simple and straightforward. If you are going to do it on a common machine for normal development purposes, it can be a bit complex if you are using other software on the same machine. 

Upgrading is easy. I have migrated some processes from versions 10 to 11, but the newer version requires some time and cost because sometimes the processes designed in the older versions cannot be migrated to the newer version. Instead of migrating, you can redesign the same process in the newer version. That would be better.

Usually, all developers are involved in the bot maintenance at a later stage. If only considering support and maintenance, you will require two people there. If your team has around ten to fifteen people, you will require two people for support.

The deployment is on the cloud. The process depends on how straightforward it is. It depends on the number of steps. The deployment time doesn't take too long, however, they could improve a bit on the scheduling. It could be a bit more user-friendly if there is a new person coming in and using the solution for the first time.

Deployments tend to take a few days once all the approvals are in place.

The solution does require maintenance. Once you have developed and deployed a bot, there could be many things that may break the bot. We need to maintain them to keep them running as expected.

The initial deployment of Automation Anywhere was easy. Our team, which included eight to nine people, assisted with the implementation and deployment process. It took about 1.5 weeks to complete everything.

Automation Anywhere does not require any maintenance on my end.

It was already in place when I got to my company.

Its deployment is easy. Usually, we sign up for the cloud and choose a subscription plan. We then set up our control room and configure our bots. We develop and deploy them directly from the cloud. It is easy for us.

Automation Anywhere does not require any maintenance from our side, but the bots require a little bit of maintenance. We spend almost an hour on bot maintenance. We see how it is working. If anything goes wrong, we get informed and we then check it out. If there are any errors, we might have to spend more time, but in general, one hour per week or 15-20 minutes daily is enough.

It is deployed in the cloud. 

The initial setup was handled by the system team in my current company. In my previous company, I manually set up the system, assigning roles like bot runner and creator through the control board. The process is easy. You just need to remember the steps.

In terms of bot deployment, you can deploy a fully functional bot in less than 15 minutes if you have a clear understanding of which machine is the bot runner, which machine is free, and which machine is already logged in. You also have to take care of the credentials. After deployment, you also need to test the bot.

For a non-technical person, it can be a little bit complex, but it gets easier with time. A couple of days are enough to learn and deploy it.

We have five to six people involved in its deployment.

During our deployment of Automation Anywhere, the first and most important thing that we did was to make sure that we got everyone trained. We spent a lot of upfront time training our developers, and that really paid off in the long term. We ran them all through Automation Anywhere's university, so they did all the online training, and then we brought Automation Anywhere in and did classroom training for our developers. That really paid off in dividends, and we were able to end up with a good developer base.

When we started with Automation Anywhere, we were on-prem with version eleven, and then we migrated to the cloud with A360. We saw a tremendous increase in productivity by going to the cloud. We currently aren't using any other cloud providers.

The deployment is seamless. 

When bringing Automation Anywhere, we were trying to solve the time taken in these processes for hospitals. We aim to ensure we can improve how fast they can charge their insurance or patients, making sure the revenue part is properly managed as that is what we are ensuring they hit.

It was pretty easy. I took a proof of concept that took nine months to build. Since I could not copy it from the proof of concept environment to our brand-new tenant or control room, we had to reprogram it. The reprogramming and testing took three months. Now, if you put all those numbers together, you probably could say it took us a year to build that first application.

It requires operation execution maintenance by my company and my IT group, but it does not take any Automation Anywhere resources to maintain it now. They maintain it at the cloud level and do a good job.

The deployment depends on the processes being put in place. Normally, it is straightforward. 

Before selecting Automation Anywhere, we conduct a feasibility study according to the process use case to ensure that the process we want to automate is viable.

My experience deploying Automation Anywhere has been good, especially since we started with standard support, but now that we have platinum support, it's a game changer, allowing for better collaboration with Automation Anywhere, who understands our requirements and provides quick solutions whenever we encounter any issues.

The deployment process was quite straightforward and smooth since it is cloud-based. We deployed it on Microsoft Azure, starting small and gradually scaling up. 

The Control Room feature made it easy to manage multiple bots in one place, allowing for effective monitoring. In the beginning, it took about two to three weeks to implement because we encountered several issues and system failures. However, our team did a great job, and we managed to overcome these challenges.

My experience with the deployment has been very good. 

The deployment experience with Automation Anywhere was great. It was smooth, and it was helpful that we had somebody already set up the way.

It was already deployed when I got here.

In terms of maintenance, the updates happen monthly. I do not have to do anything, but there is some maintenance when users want to get connected to run bots. There is a little bit of upkeep that happens there. Other developers sometimes do not have the necessary permissions. That process is not particularly painstaking. It is usually painless. There are two or three of us involved in the maintenance. We spend very little time on maintenance. It does not happen too often.

The initial deployment is not difficult at all for someone doing it for the first time.

Usually, one person or maybe two is required for deployment; while the automation can be built by one person, working with an internal application Microsoft CE or HubSpot through API calls typically requires at least two people to integrate effectively.

Maintenance is not required on the end-user's part, though if it is an attended setup, some monitoring may be necessary because VMs can become unavailable if used for other reasons, leading to a single-threaded heavy load process that runs for an hour but sits idle the remaining 23 hours.

I have not installed Automation Anywhere.

The deployment of automated tasks is easy. I can do it in two minutes. I have used both on-premises and cloud models. In terms of maintenance, the bots usually require updates when there is an issue or there is an update from Automation Anywhere. It is usually once every three months.

The deployment is fine. It is very easy. 

It is completely on the web. We have our own licensing management tool. Anyone who has done internal training can request the license. A dedicated license is generated for you for a few hours or if needed, permanently. We have a dedicated portal for deploying our projects.

The upgrades are also easy. It does not require much maintenance.

I have participated in the initial setup of Automation Anywhere as they are providing a SaaS cloud model, so the setup is quite easy now. 

In the initial setup, you don't have to invest much effort because they now have a complete AI SaaS module, and even the A360 has a SaaS module. You can subscribe to it and just have things connected. There could be some plugins or certain settings for the local studio, or another local robot which might require certain add-ons and dependency packages. But it's more of an initial effort investment; once you set things up, it works fine.

They offer both on-prem and SaaS cloud solutions, but on-prem may require more effort in setup. SaaS cloud is easier to utilize and configure. Nowadays, most customers are migrating to cloud options, which come with various benefits and ease of setup, including commitments in provisioning servers. Multiple benefits are available, and many customers, including those in the Middle East, are migrating towards cloud setups.

Its deployment is easy. The deployment time for Automation Anywhere cloud depends on factors such as infrastructure complexity. For a standard cloud deployment, if using a basic setup, the time required is between thirty minutes to two hours.

Ongoing maintenance is required, especially if bots interact with a dynamic application, cloud service, or AI model. We are using cloud services, so regular updates are required. If the UI of an application changes, we may need to update it.

Given its web-based architecture, the initial setup is genuinely straightforward. The hardest thing is a hybrid setup because you have to remember the rules for each one. Depending on the web browser, you have to have a certain amount of power and bandwidth at your disposal. I don't know that I would manage the environment myself. I'd rather have hybrid to cloud so that AA could manage the upgrades for me.

 Larger, multi-tenant deployments typically take three to five weeks, while a single device on a VM can be set up in two to three days. When we sell it and do it for infrastructure, we use senior consultants, so it's 1.5 resources. Depending on how complex the configuration is, we may need more senior consultants, but one architect plus a consultant is usually enough to get it done. 

Automation Anywhere requires some maintenance. We provide managed services to our clients for break-fix and business or system exceptions, but Automation Anywhere handles all the upgrades, patches, etc., as long as it's in the cloud. 

 It's difficult to say how much maintenance Automation Anywhere needs because it varies based on your environment. Sometimes, your environment isn't set up correctly, so the service crashes a lot, and you spend a lot of time resetting services and restarting processes.  

It also depends on the configuration and the number of automations. My largest client has 400 automations in production, so it's a full-time job. They say one person can manage that many, but I don't think that's a healthy number. It's more like 140, depending on the SLAs and use cases. An IT resource can fix most system exceptions, but business exceptions require somebody who's at least minimally basic-certified and ideally advanced-certified. 

In other cases, the automation wasn't built with the best practices in mind, so the process will time out and take longer than a human. Many things can cause maintenance and uptime to increase. Ideally, you want to do load management with the bot, so you're sharing the work. You want a utility available if the workload increases or a bot goes down. Lastly, you should ensure enough onboard memory and bandwidth for the automation to run.

We are using it as a SaaS solution. If we choose an on-premises solution, we receive a bundle that we need to install. This installation can be done on Azure, any cloud service, or on our own server machines. On the other hand, when we opt for a SaaS solution, they create control rooms and set everything up for us. We are only given an access key, or what could be referred to as a license key. By entering this license key, we can directly access the system. We can typically receive the license key quickly, often within a minute, for their cloud version. That's what I know about these solutions.

It requires some maintenance, but they are actively addressing it. They install patches and provide updates for the package versions. As a user of the SaaS solution, we don’t need to worry about these details. However, for the on-premises version, I believe users need to manually implement the solutions. Whenever there are updates or new package versions available, they deliver them to us, and we must install them in the control room.

Upgrading Automation Anywhere is very straightforward. It requires just clicking a button to upgrade multiple components including packages, solutions, control rooms, and the bot engine.

Regarding bot maintenance, if there are no changes in the web application or desktop application and no machine issues, bots can run for three to four years without human intervention.

For others who are looking for an RPA solution and considering Automation Anywhere, I would encourage you to choose Automation Anywhere if you are hoping to have any level of citizen development involved. 

They make it very easy for anyone to learn and pick up the skills required to develop bots. Beyond citizen development, I think that they have a very reliable platform that is very robust in functionality. 

They can integrate with many applications, and they make it very easy to create automations that scale and are able to automate a wide array of business processes.

What I appreciate the most about Automation Anywhere is that it's pretty flexible in terms of standing it up. You don't have to have a whole lot of infrastructure setup that's required for it.

For the most part, it's been fairly seamless. The biggest struggle on our end seemed to be with just the technical connections. It's just how we have the infrastructure set up. We're housing an on-prem solution. We're exploring the cloud and shifting there because I know it'll be easier management from our side. There'll be fewer technical issues. It will be a lot easier to get newer updates from the tool itself. That's one thing that we're looking into now.

I would say setup is straightforward as long as full access to prerequisites and features is available. We don't have access to spin up databases or servers, relying on different teams, which delays deployment or upgrades. For companies where the COE has full control, setup is straightforward.

It is generally easy to deploy. We use Automation Anywhere with both AWS and Azure.

Maintenance is indeed required for Automation Anywhere; you have to follow the vendor's product patches and version upgrades to keep it maintained.

Upgrading Automation Anywhere follows a standard process that they provide detailed instructions for, and we adhere to those guidelines. The upgrade process feels similar to any other software platform; I don't find anything particularly complex or different about it.

There is a separate team for bot maintenance, and if the bots are stable, maintenance needs tend to be low. However, if issues arise, maintenance efforts can significantly increase.

The setup can be pretty easy unless there are multiple components integrated or organization-specific standards. 

For a single server in a regular control room, it may take a couple of hours. When implementing a control room and IQ Bot, it may take approximately five hours.

My experience with the bot deployment is pretty straightforward. I have an RPA admin who takes care of the deployment. While I cannot speak on his behalf, I would say that the deployment process, from what I know, is pretty straightforward. It is not anything too complicated or complex.

The initial setup was easy and took about a week. Two to three people were involved in the deployment.

The deployment is very easy for me. 

It takes only two to three minutes to deploy a bot from the dev environment to the UAT and then to the prod environment. It's quite easy to develop the bot. 

Currently, in my organization, we have about four departments using Automation Anywhere. Automation Anywhere doesn't require any maintenance. I purchased Automation Anywhere through a direct purchase.

The setup varies with the deployment type. Cloud deployment is straightforward with only a few steps. Dealing with on-premises can be more complex due to customization for specific organizational needs.

The upgrades are quite easy. You just need to select the appropriate version suitable for your business. You need to contact Automation Anywhere, and they will do it for you. There are no hidden charges.

It requires maintenance. If you update your basic application, you also need to update Automation Anywhere to that level. If your application is old or not compatible with Automation Anywhere, they can create some sort of patch to link those applications together.

The deployment has been pretty smooth. We haven't had an issue with anything. Mostly, it's getting all of our internal security and things like that locked in so that we can go through.

The initial setup took about a day, and while it was initially a bit complex, it eventually became easier.

The deployment of Automation Anywhere is very easy. 

We have three environments: development, testing, and production. We build the bot in the development environment and after building, exporting the bot is simple—just a few clicks to download the zip file. You can import that file into any other environment, including production, by clicking on the import button, and your bot is deployed. You can also schedule and run the bot in both attended and unattended modes, which adds to its ease of deployment.

Automation Anywhere does require maintenance on my end. The platform provides updates and package management. For instance, for browser automation, if you are using browser package version 1.1, you must use the same version across all environments; otherwise, the bot won't run. While it's possible to download and deploy the bot without adhering to package updates for production setup, managing package versions can still require attention. Thus, maintenance can be neither too simple nor too difficult, but it is necessary when developing with Automation Anywhere.

For me at the very beginning when I started working with that, the technical setup was extremely complicated and extremely problematic, and we spent half a year to really make the software work. At that time, we were not happy with the support of Automation Anywhere. But now if everything is already set up, it's quite easy to learn how to do it and to make easy automations quite fast.

The installation is easy. It's not too difficult. There is a provisioning of the control room where we have a customer portal. We can go there, put our licenses, provision our control room, and they can provision within fifteen minutes. After that, we can use the automation engine. The installation part is just installing a small EXE, and we can start the automation.

The initial setup is somewhere in the middle, neither very complex nor very straightforward.

It was deployed before I joined. In terms of the deployment model, it is probably fully on the cloud, but I am not too sure. When I joined two years ago, we were on version 11 on-prem. One of the biggest things I had to do was migrate us from version 11 to the cloud version.

We use a mix of on-prem and cloud devices. We are exploring Microsoft Azure to go to it soon, but we are not using it today.

The deployment experience was a little bit frustrating at first, but I was not the one involved. Our architects were having issues, but we engaged with the Automation Anywhere solutions engineers. We were on the phone for maybe an hour or two hours and they fixed it. The deployment was great.

Setup for us was probably the longest lead time. We're a bank, so we always have to scan the code base. We want to jump in, understand the connectivity, and understand how things are going to happen. There are a lot of planning-type activities before the install. We started in 2017 with version seven of Automation Anywhere. We went through version ten, then moved on to the A360. Each experience became better and better.

We have a PCI-compliant installation as well as our normal normal network.

Our experience deploying Automation Anywhere was seamless. From a server perspective, we run about a dozen servers in four dev IT QB production environments. We'll continue to do the first servers in dev and move to migrate them all the way through production. For any issues that we have along the way, customer service is right there with us to troubleshoot.

The initial setup for the initial version, version eleven, is not too complex, medium. The latest version is easier because it requires less infrastructure.

Initially, we found it a bit complex, but after learning about it, it served us well. For complex tasks, deployment takes about two to three days.

The deployment process in Automation Anywhere is relatively straightforward. We export the package from one environment and import it into another. However, each organization has its own unique deployment standards, often involving processes like change advisory board approvals. Therefore, the actual deployment method will vary depending on the specific organization's guidelines and procedures.

The overall deployment time for a robot is five minutes. A team was involved in this process. As the developer, I was responsible for obtaining the necessary approvals and moving the robot code from enrolment to deployment. Other organizations may have specific teams dedicated to these tasks. For example, they might have their own Centre of Excellence team that handles all deployments. Therefore, the deployment process can vary depending on the automation and the specific organization. In my current organization, we handle deployments ourselves, while in my previous organization, there was a separate team dedicated to this task. Prior to that, a support engineer typically performed these duties.

It was on-prem before, and then we migrated to A360. It was already deployed when I joined, so I do not know about it, but migration took 4 to 5 months.

There were 4 people mainly focusing on migration. It was a bit complex because it was new, and there was not a lot of material available online. It was a little complex, but later, it became smooth. We reported a lot of bugs, and other people also reported them. It was very smooth.

Having used Process Studio, the initial deployment for Automation Anywhere was not difficult for me. I referred to YouTube videos for guidance. The only challenge was figuring out how to input my device name, which took one to two days until colleagues helped. If some data could populate automatically after installation, it would be beneficial.

Although I wasn't involved in deploying Automation Anywhere, I recall the process being straightforward and immediately successful for the company.

While I wasn't involved in the initial deployment, I contributed to the migration from version A11 to A360. This was a major undertaking, spanning six months and presenting numerous challenges. Despite encountering various issues, we ultimately achieved a successful migration.

Cloud deployment is straightforward, while on-premises setup requiring server configuration can be challenging. A cloud deployment typically takes no more than one business day.

We have two teams: the operations team and the development team. The operations team handles deployment and typically consists of one or two people. The development team's size varies depending on the number of processes requiring automation. For fewer processes, one developer may suffice; however, we may engage five or even six developers for numerous processes.

The platform was not hard to deploy, but each company has its own security protocols to deal with. Once we worked through all the security requirements, it was straightforward. Automation Anywhere requires some maintenance. 

In the first year, we needed to adjust the size of the machines and optimize the bots. However, it hasn't required much maintenance since then. We developed some better processes in CoE governance to develop and track the bots, so it's much easier now. We set up alerts that send us messages when the bots have errors. 

The initial setup of Automation Anywhere was straightforward and completed within a day, primarily due to our accreditations and existing understanding of other technology tools.

For the initial deployment of Automation Anywhere, it was a new thing to learn. For about a month, I found it difficult because I did not know about the various actions available in Automation Anywhere or other RPA tools. Now most things are clear. Whether using Power Automate or Automation Anywhere, I know which actions to use for specific tasks.

We have more customers on the cloud than on-premises. I am personally not involved in the deployment, but the initial setup is straightforward. It is not complex. Upgrading Automation Anywhere is easy.

The number of people required for maintenance depends on the number of automated processes. For 20 automated processes, you might need one person full-time per month. This can vary a lot on the type of process that you have automated.

The deployment complexity largely depends on the integration process. If integration is straightforward, a citizen developer can acquire the necessary skills within one to seven days and begin developing. For complex analyses, prior knowledge of external environments, such as C# or Python programming languages, can significantly reduce the required code length within the Automation Anywhere platform. While Automation Anywhere doesn't offer a traditional coding structure, it supports integrating other languages and components, enabling activities with fewer lines of code.

Deploying Automation Anywhere was definitely a learning experience for us, especially when we stood up the platform and tried to understand the deployment flow internally for the team. Our platform admins who do the actual deployment got their system before the support team that helps with the checklist of activities before the deployment takes place. That is where we had to learn and set up our framework to get it deployed.

Prior to actual automation deployments and getting the environment set up, we had to work with our infrastructure team. We had to make sure that we had the right resources in place and that those resources were working adequately before we launched our first automation onto the platform. Internally, we learned some lessons along the way. That is a part of the course for anybody who is deploying a new solution in their infrastructure. Overall, it did help us learn the importance of having a good framework in place so that if we need to build, expand, or change anything, we would be able to accommodate that appropriately.

Getting started is easy - the initial deployment follows standard procedures and can be completed in as little as two days for a simple use case. Complex setups may take up to a month, and the number of personnel required varies from two to ten people depending on the specific needs of each project.

The initial deployment took three months, but it took a year to change the legacy bots to Automation Anywhere. We decided to automate new projects that would yield more ROI before finishing the migration of our legacy bots. 

The initial deployment was complex, requiring determining the bot type, attended or unattended and bundle handling strategies for multiple bot deployments. This process, driven mainly by configuration and orchestration, can be time-consuming for those without a technical background. Familiarity with the system streamlines deployment, while newcomers or those with limited technical expertise may find it more challenging.

It's easy to deploy, install, and learn Automation Anywhere. We deployed it ourselves without the help of any integrators.

Deploying Automation Anywhere was relatively seamless. I've been using Automation Anywhere since version 10 and was a solution architect for version 10 and version 11. An on-prem deployment requires a computer science degree to understand because there are so many factors involved. With a cloud deployment, everything was done for me. The only thing I had to do was provisioning and configuration. It made life a lot easier. I could complete it on my own in about two weeks.

We need to install a client into our machine to use Automation Anywhere.

Implementing Automation Anywhere proved challenging due to platform-specific intricacies. Each platform, like Google Cloud and AWS, requires unique implementation techniques. Fortunately, once these variations are understood, the process becomes streamlined – it only took me two days to grasp it on Google's platform.

The deployment process was successful thanks to the contributions of the third-party implementation team.

The full deployment took eight months to complete.

Deploying cloud solutions can be relatively straightforward. Therefore, I don't anticipate the initial deployment of Automation Anywhere being particularly complex. It seems the Automation Anywhere salespeople provided excellent information to facilitate the implementation process. In total, three people were involved in the deployment.

Deploying Automation Anywhere was relatively easy. We implemented our first bot last year as a proof of concept. We tried various things to give us a bit of a different flavor. Whether we're using an API, UI, or doing a physical task within a third-party application. Our first bot took 10 weeks to deploy, and the rest took between eight to 10 weeks. The development time is about half of that. Most of our use cases were simple, but it took time to coordinate with various teams, like infrastructure, security team, risk management, and other IT departments. 

My role is in the center of excellence. We're on the business side, not the IT side. The company is a little different in how it sets up its CoE programs. We focus on business processes and engineering. I rely on our technology and security partners for those other pieces. There's a little bit of trial and error. We have to think of security first and foremost. We're protecting our data and our client's data.  

We needed to figure out how it fits into our ecosystem because we had never done it before. We needed to set up virtual desktops, servers, and those sorts of things. We needed to create an Active Directory account for our robots to interact, receive email, use Excel, etc. Early on, we had to learn the nuances because we would need to replicate the processes going forward. We created some reusable runbooks and IDs to set access to the system with different privileges for employees and contractors.

There is some maintenance for bots that utilize UIs, but not those that use APIs. We face more challenges when working with third-party applications because they have scheduled updates. If the bot is scheduled to run on Thursday at 2 pm, but suddenly, a pop-up window appears to run the update. We've mitigated a lot of that. If we don't have APIs, those use cases require a little bit more handholding. 

The deployment is easy. We are not implementing huge ERPs, but rather automation technology so it is easier than traditional huge systems. It is more flexible and we can use it to automate any task we desire.

The time it takes to deploy depends on the tasks. When automating critical operations we need to be careful in the assessment but it should not take more than six months to complete. We can complete an easy deployment in two weeks. 

Automation Anywhere is easy to deploy. Some processes can be deployed in a week, while the more complex processes may take four to six weeks. We have release controls in place, so everything is streamlined. All the deployment testing is handled before the automations go live. 

Upgrading is simple because we're on the cloud platform. We don't need to upgrade anything. Maintenance takes place on the partner's side because the bot engine is installed and maintained there. We only need to install the latest packages to test the new features when they are released. That takes a little time. 

We're going through the 360 migration right now. The bots that we have in production are fairly complex. It hasn't been an easy migration. We're getting through it, and we have a lot of support to get through the migration. But it's really more of the complexity of our organization.

The deployment was good.

The deployment is straightforward. 

Process Automation takes from one week to six weeks depending upon the complexities of the process to be automated. In terms of maintenance, whenever the interface of any product or website changes, it is a nightmare for the developer. When you automate your tasks, there should be a maintenance activity at least every month so that no complaints come from the business users.

Deployment is easy, but the testing takes time. It also takes some effort to migrate the bots from version to version, like v11 to the cloud version of A360.   We learned it the hard way, but once we moved to A360, that took care of many of the infrastructure issues we faced with the on-prem version. It was mostly some technical challenges, not infrastructure-related changes. The cloud version is much better than the on-prem. 

Automation Anywhere requires maintenance, but how you develop the processes also matters. We try to implement best practices, like using wildcards instead of URL names. That's why we try to find ways to make API calls instead and get the data from there. We are currently doing a PoC that involves retrieving the data from third-party websites, and they told us that they could build an API that would make it easier to maintain. The APIs work better than redirects. 

I was mostly involved in the infrastructure, so I was not directly involved in the deployment. My understanding is that it is not difficult. However, when we upgraded it, we had challenges. 

There is some maintenance required. Normally, it works fine. Sometimes, there may be migrations or updates required. Only one or two people need to handle maintenance. We don't maintain bots. However, we just deploy them. Maintenance can be completed by the customer, and it might take five to six hours or one day at a maximum. 

It took us a month to deploy. We set up a few runners or virtual machines to be able to do that work with our IT team who configured some of the runners and made sure that we embedded applications that were gonna be useful and practical for the actual automation itself. We then walked through a few test automation and were able to deploy our first automation within a month.

Our setup is hybrid. Our control rooms are on the cloud. We are on A360, so our control rooms are on the cloud, but our bots runners are on-premises.

I was involved in its deployment. When we did this at the initial stage in 2018, it was pretty straightforward. They provided great support. We started out by doing eight processes as a pilot. 

Their team provided the developers because I had no developers on my end at that time. Their team did it remotely. They were probably doing it from India. They gave us the requirements. They educated us on what was needed and how we needed to set it up so that they could connect to whatever systems they needed for the eight processes or use cases that I had chosen. They did deliver all those processes within two weeks, so it was pretty straightforward.

Their professional services team was top-grade. They knew what they were talking about, and the people that they gave me in Singapore at that time were very good.

In terms of maintenance, it does not require any maintenance from my end. They do a quarterly patch of it. They announce that they are doing a patch, and it gets done. There is no maintenance on my end for the tool. What I need to maintain are the bots that we have built for the business. That is where the maintenance is, but that is more on our end. That is mostly because the bots break because of the change in third-party applications. 

The setup process was easy. We were able to leverage some time savings during the deployment. We didn't have too much downtime.

You only give instructions to them regarding what is required. You explain to them.

We've been able to deploy the solution easily. We've been able to integrate it with our systems of record and other tools. 

The experience has been good. It's important to do it with the proper partner and proper team. When we merge product and project teams, it helps make the deployment process seamless.

The deployment was good, but the migration to the cloud was a bit tedious. It was an extensive engagement.

The upgrades are quite seamless now because it is now in the cloud, so the effort is quite less. We have a team set up for maintenance.

It was easy. The full deployment of Automation Anywhere took approximately three to four weeks.

Updates are done automatically, so maintenance is not hard to handle. 

We use the SaaS model of Automation Anywhere, so the deployment was easy. We set up the infrastructure in under a week. We worked closely with the Automation Anywhere folks because we wanted a clean slate. We didn't want to migrate from the older version to the SaaS edition and took it as an opportunity to clean up the bots. It didn't require much effort, and only two people were involved. The upgrade process was simple. Maintenance is minimal. It only takes a couple of people to maintain 75 bots. 

The initial deployment is straightforward.

Automation Anywhere is deployed on the cloud, so I think it was very straightforward and fast. It took around one to two weeks.

The initial deployment is straightforward.

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. 

The initial deployment is simple, especially for the cloud version. Just create an account, log in, and install the local connector or bot. Then, connect it to our device and access the website. One technical person can complete the deployment in five minutes.

We clear up any issues in the testing phase, so once we are ready to deploy it is straightforward.

The deployment time depends on the number of processes being automated.

The setup process in Automation Anywhere is really easy. While I haven't worked extensively on moving from development to production in Power Automate, with Automation Anywhere, we just need to import the bot and export it into the production environment. The process typically takes 10 to 15 minutes.

If we opt for the cloud version, the process is very easy and won't require much effort. In contrast, going with the on-premises option entails some additional requirements that the IT team needs to manage, but it's still manageable. It's straightforward, and there is documentation available that you can refer to in order to complete the setup.

From start to finish, installing the cloud version takes only about fifteen minutes.

I have worked with both the cloud as well as on-prem versions. In Automation Anywhere, setting up an on-premise environment is quite straightforward, similar to installing MS Office or MS Excel on your system. You simply need to specify the location where the software will reside and configure the database connection. The installation process takes care of everything else, including registry keys, making it quite simple to set up. In contrast, if you're opting for a cloud-based solution, there’s no setup required on your part. Automation Anywhere provides a URL that allows you to access the control panel. All the enterprise-level configurations are managed on their side. You only need to connect to a bot agent, which is also available for on-premise setups, from your local machine. Overall, the cloud option is much easier to manage, as everything is handled by Automation Anywhere.

After setup, Automation Anywhere's cloud version does not require any maintenance. Upgrades and patches are managed on their side, only notifying us beforehand of any scheduled downtimes. However, if you use the on-premise version, you need to uninstall the older version and reinstall the new release yourself. 

Bot maintenance in Automation Anywhere is minimal because the packages can be easily selected and handled within the bot creator. Once in production, changes in logic or UI are the only things requiring attention, which typically involves checking components rather than extensive maintenance effort. If you undergo the upgrade phase, you need to check the packages to ensure they are all set to default. This process takes around 10 to 15 minutes. If any packages are not set to default, you must adjust them accordingly before running the upgrade. Overall, it doesn’t take much time.

In Automation Anywhere, upgrading is similar to reinstalling the Control Room. You need to stop the services, then uninstall and reinstall the software. Since the database is already established, when you install a newer version, it automatically creates new tables in the SQL database, which then run smoothly on their own. Therefore, the upgrade process is essentially just a reinstallation.

Currently, we are using it for one client, and for that client, it is deployed on-premises. The initial setup was quite straightforward, but I was not responsible for the deployment. My role is focused on bot development and testing, while other team members handle deployment and maintenance.

I have not worked a lot with earlier versions or migrations of Automation Anywhere, but I have experience in migrating a bot, which was easy. I could easily migrate a bot from version 11 to Automation 360.

We have the cloud as well as on-prem deployments. We now have something like a robot as a service. It is a hybrid with the cloud and on-premises setups.

It is quite easy to install it and connect it to the databases. The deployment is very easy.

The deployment duration usually depends on the client. It can take two or three days to set it up properly.

It took about four weeks to deploy Automation Anywhere on-prem, do the basic settings, and do all kinds of installation.

Currently, we have to upgrade our license. Previously, we had the enterprise version with a limited license. We are now expanding the license. 

Previously, it was on-premises, but now, everything is on the cloud.

Its deployment is very easy. Because it is a cloud platform, you just need to install a single file. It does not take more than two minutes to download. Within two minutes, the cloud license will appear. One person is enough for the deployment.

It gets updated automatically because it is a cloud version. There is no need to update it manually. Everything is done automatically. If auto-update is not working, we can update it manually, but that also does not take more than five minutes.

In terms of maintenance, regular maintenance is required because there are issues related to stability and tasks failing at the runtime because of unknown reasons. These things need to be fixed, so regular management is required for Automation Anywhere at the backend.

I found the setup process to be somewhat complex because I don't come from a technical background. 

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. 

The deployment process is fairly straightforward. Deployment of Automation Anywhere typically requires just one person. If you are familiar with the entire workflow, one person can manage the deployment effectively. Maintenance for Automation Anywhere is minimal. However, due to recent use, aspects like patching and version upgrades are not entirely clear, and occasional manual intervention is needed for tasks like access management.

I was involved in the initial setup. 

If you start out pretty simple, the challenges that cause delays are more from change management and security and clearance. That's outside of the platform itself. That takes 80% of the time.

You can stand it up in a couple of days, however, it can sometimes take a month for reasons outside of the platform.

You can get things going within a week, which you can iterate on pretty quickly. 

Maintenance depends on usage. There are tools where you can build automation to provide alerts. You need someone who's at least slightly dedicated to that. Once you get bigger, you'll need a dedicated team, and then you have to figure out how to prioritize your time, in terms of evangelizing it, making more automation, et cetera. 

I was involved in the initial deployment. It took a couple of months.

It's relatively easy to upgrade. It depends on the organization. You need to add more variables and define the standards. However, it's not too complex. 

There is some maintenance needed. When you upgrade versions, devices may be disconnected. Sometimes you need to go and check if the device deployment is happening or not, or a deployment may fail. We have about two people handling the maintenance of the solution. You simply need to ensure the bots are deploying on the right schedules and check errors or disconnects. In some cases, you may need to redeploy the bot. The time spent maintaining bots maybe three to four hours per day per person. 

The initial deployment of Automation Anywhere is straightforward. We use the bot model and deploy bot runners through the Automation Anywhere cloud, simplifying the process. While using the Automation Anywhere cloud is convenient, we've also deployed an instance in a private cloud environment like Azure or AWS, which works well. However, deploying in a private cloud requires knowledge of clustering and related concepts, so it's not suitable for everyone.

We faced challenges while implementing the solution because we were probably among the first to do it in the R2R space. However, we were able to work through and overcome those challenges.

It is deployed on-premises, and its deployment is straightforward.

The deployment of a bot used to take about three days. There were some steps for approval, and we used to manually deploy, but now, my company has CI/CD integration. We run the pipeline to automatically deploy. It is very fast now. It just takes an hour. We just need some approvals and we need to review the package. It is straightforward. One person is enough for deployment.

It is also easy to upgrade Automation Anywhere. It is not difficult. In terms of maintenance, one or two people are enough to maintain the bots. If there is any issue with the bot, we can resolve that within 5 days.

Automation Anywhere requires limited maintenance, and at the time, three individuals were involved in maintenance and implementation. As the applications expanded, there was a need for a gradual increase in the team for ongoing support and enhancements.

Deploying it is very straightforward, although I am not too involved in the nitty-gritty of implementation. My job is to prospect customers and work with them until the deal has closed. After that, I let my delivery team handle it.

We have a maximum of two people involved in deploying it. There is not much maintenance involved.

For technical employees, it takes about six weeks, and not more than that, to be trained to use Automation Anywhere. For a person without a tech background, it takes a couple of months, max. The learning curve is pretty steep for Automation Anywhere.

I installed it on my personal laptop, and it was straightforward, but for the production environment, the Infra team takes care of the installation. It takes them a maximum of two to three hours.

It is on a cloud. It is hosted in the Citrix environment, and it is being used by multiple departments. We need to log in to Citrix to utilize it.

Its maintenance is handled by our Infra team. If there is a patch release with a feature or fix that we need, the Infra team updates its version. Otherwise, we keep utilizing the same version. Our Infra team has access to the Citrix environment. They can create and close the Citrix environment, and that is why they do the maintenance. Any maintenance activities are done over weekends so that none of the in-progress processes get affected. Generally, they happen over weekends. They usually start on Saturday and then the activities are complete by Monday morning.

The initial setup was straightforward. Although I was involved in the deployment project, the actual installation was carried out by those responsible for implementing the Windows servers.

We needed to acquire the hardware because we had an internal cloud at that time, so we still have it. I would say that we managed to allocate the servers. It didn't take long. We provided training for the people who would deploy and customize the product with the assistance of Automation Anywhere in France. The global deployment infrastructure was ready to be used within a few weeks.

The setup takes a good amount of time because you have to develop an infrastructure that includes servers and compliance. A lot of time is spent framing those requirements and signing contracts that are quite detailed. 

I rate the setup a five out of ten because it is not that easy.

The initial setup was fairly straightforward. Our team did not find it to be difficult. our deployment team was pretty small. We only had four or five people working on it. It was easy to upgrade as well. There is some maintenance needed, including the need to take logs. However, it doesn't take too much time.

The initial setup is straightforward. If you have knowledge about it, it does not take much time. Within 15 to 20 minutes, it can be installed on a machine.

Its maintenance is easy.

The initial deployment is straightforward. We move code from private to public in a zip file and provide it to the developers. It takes approximately ten minutes.

The initial setup was complex, but upgrading the automations was easy. The bots require some monitoring. It isn't more than an hour daily. We check to see if there are any issues or whether a process has gotten stuck. That's rare. 

I was not involved in the deployment of Automation Anywhere. I work with the RPA team.

The deployment environment varies. It is dependent on the client's environment. It depends on where your data is and where you are doing the automation. If you are doing automation on the data fabric for reporting purposes and you are deploying a bot to gather the data from specific tables, you might put it onto a data fabric or a data lake. If you are working on PR to PO, that information is going to be on a system of record. It might be on the server itself. It is truly use-case-dependent in my view.

In terms of maintenance, customers typically buy the licenses, but these days, I see that customers prefer to use one main partner for all their licenses because it is easy to manage that one main partner. It could be the largest partner they have in their set of vendors who are supporting them for all IT-related activities. If they buy it from them, they do not need to do maintenance, but if they buy the licenses themselves, they may need maintenance. It depends on whom they are engaging with and what is the purchasing model of licenses.

How easy or difficult the setup is depends on the customer's level of knowledge. Most of our clients are in banking and require on-premises deployments. Even government entities cannot use the cloud. We are comfortable with deployments and find the process to be straightforward.  Sometimes it is difficult to upgrade from older versions. 

We have five people out of a team of 13 that can handle any maintenance. Maybe 20% of our team would be involved in maintenance. 

We've deployed processes within a week, while others might take four or six weeks, depending on the complexity. We have release schedules and release controls in place. Everything is streamlined, and we test before the automation goes live. 

We're on the cloud, so we do not have to upgrade anything. 

Maintenance is more on the partner-owner and device side. There might also be work upgrading and testing packages and new features. We do spend some time when a new feature comes out to test it before we actually upgrade our packages.

The initial deployment took us less than one hour. If everything is prepared, all infrastructures are in place, and all the relevant people, definitions, and Active Directory are available, it can be deployed in less than one hour.

Automation Anywhere’s implementation is a click-through process. Mostly, it's a decision process within the system. There is a built-in bot distribution system if we need to scale up. We define the servers, and the system fires out the add-ons to the servers. Since it's a web-based system, we don't need to install almost anything. Just install the control rooms, and then everything else is done through the browsers.

The defense sector customers prefer to deploy the product on-premises. Half of our customers are on the cloud, and half are on-premises. The customers do not care what cloud provider we use since it’s a SaaS application. It is very transparent for the customer.

The initial setup is easy. The deployment usually only requires me and one programmer from the client's end.

It takes 30 minutes to an hour for the initial deployment of the platform.

It's very easy to deploy the tool. We just have to export it from the development control room and import it to another control room. We can select the files we need and export or import them. It is very simple, like a file upload or download.

The time taken for deployment depends upon the number of files or packages since we use multiple workflows and tasks. It depends on the file size. However, it should not take more than three minutes. Even if it is complex, the deployment is completed within three minutes. If it is simple or moderately complex, depending on the file size, it uploads within 30 seconds. While deploying the product, we can see the progress in the control room.

I wasn't involved in the deployment of the solution. 

We do not really have any maintenance. 

It is mostly in the cloud, and it is mostly deployed on the Microsoft cloud. They also have their own cloud.

In terms of maintenance, every software needs to be updated. Before upgrades, you should do stress testing and be aware of the changes. You might have to update the robots as per the changes.

It is a private server farm where we have implemented AWS because the governments do not allow hosting on the cloud in most countries. This is a restriction from the government side.

We have two teams. One is the technical team, which is involved in network security and the server side. I am from the functional team where we are involved in all the services, all the applications, and all the databases. The technical team takes care of the software installation, maintenance, patches, and upgrades. We are only working on the application side.

The initial deployment was straightforward. It took six months to deploy ten bots.

The initial deployment is easy. The documentation is clear. Implementing A360 on-premises, a complete end-to-end installation, takes four hours. We just need the server team for administrator passwords.

I had already tested and tried it on a development server, so I had all the steps written that I had to follow for deployment to production. It didn't take much time. I read the installation guidelines and documentation from Automation Anywhere and it was easy for me to do it.

We have about 25 end-users of the solution in our organization, and three of us take care of maintenance. In terms of bot maintenance, not much time is spent unless and until there's a change in the process or the environment.

For business users who do not have technical skills, it is easy to use the product. They understand what is possible with the tool over time. Within a year, they understood what needed to be automated and what not. Training non-technical employees on Automation Anywhere usage takes three to six months.

We had an enablement package, which we could start using because Automation Anywhere turned it on automatically. We did not need to set it up ourselves, as it was only for bots running in our environment. It was not difficult.

The initial setup was handled by the business owner and IT. It was done by our partner. It requires technical skills. We need to have a workflow. If we have a clear workflow, we can easily implement the same with the partner.

We provided hands-on training for Automation Anywhere through our partner. In the first phase, it took us at least three months to train the lab operations team and other teams supporting the project. We parallelly created a document for the initial phase. All the people who are now being onboarded use that document. They are able to support the bots without any additional training.

Assuming that the infrastructure is in place, the deployment of the Automation Anywhere components, which include the controller, parts, and studios, can be completed within a maximum of five days.

The solution's initial setup is easy and not very complex.

We migrated to a gateway situation. It was challenging as the architecture was different. We faced a lot of issues and it took time to migrate. There were a few functionalities that were not working and we needed to recreate the workflows. When we started, most of the ports were not working. The migration did not go as expected. Then, there was a new version of my initial VPN. It took more than a year to migrate.

The solution does require some maintenance. You do need to maintain the bots. 

The initial setup is straightforward. The complexity lies within the interfaces. Our development team handles the internal implementation for our customers.

The initial setup was complex. The vendor was unfamiliar with the process, and there was no guidance from Automation Anywhere regarding the requirements. According to Automation Anywhere, we were supposed to simply follow the onscreen instructions and click "next," which should have taken a maximum of one hour. However, due to an error and misunderstanding, it took us around three days instead.

The deployment started at the control room, then the client, and finally the developer.

One person, who was an Automation Anywhere specialist with infrastructure knowledge, was used for the deployment.

We typically deploy to Automation Anywhere's public cloud. We haven't used the private cloud option because it's expensive. I'm the project delivery manager, so I was involved in the deployment. It doesn't require any infrastructure because it's in the cloud. 

The deployment time depends on the complexity of the processes. Simple processes can be configured in a couple of weeks, but complex projects might take up to three months. 

The number of people involved also depends on the client's needs and the licenses purchased. You need a developer license for each engineer. Automation Anywhere licensing is based on the individual users, not the partners. For example, let's say a project will take one engineer three months, but the client wants it done in 45 days. You would need to double the number of engineers and pay for an additional license. 

Automation solutions require some maintenance and change management because no process remains constant. You will need to update and optimize the bot as the process mechanism changes. 

The initial setup is complex, primarily because of the time required for the first deployment. The deployment takes one hour. First, we need to ensure that the infrastructure is correct, install the automation workflow, and then implement each of the workflows on them. Afterward, it should be run for one to two days before handing it over to the employees. Two DevOps administrators are needed for the deployment.

The initial setup requires some expertise. We formed a team to handle the preparation, installation, and configuration of the platform internally.

My manager completed the initial setup, but I believe it was complex. The deployment required one person from Automation Anywhere and four people from our technical office, including my manager.

The deployment is straightforward and can be completed within one and two weeks.

Before implementing, we want to ensure we have all the support and collaboration.

Deploying Automation Anywhere is straightforward. It doesn't take much time. All of the processes need some maintenance because the processes running in the system sometimes don't work. We need to rerun the processes or change the elements. We have a 17-person team, and three of us are responsible for maintaining. The time spent maintaining bots varies. Sometimes, the issue is easy to fix, but if you need to change the flows or do some development, it may take two or three days. 

My understanding is that the initial setup is pretty straightforward.

The project would dictate how long it would take to deploy. It could take a couple of days to a couple of months. There's a question of governance proliferation and compliance that needs to be considered in RPA. The internal policies would affect the overall setup. 

There is maintenance in the form of updates. It doesn't take much maintenance. We don't use bots and therefore do not need to maintain them.

Recently, automation has gone to the cloud, and that has been most beneficial because installation was quite hectic before. On-prem was quite difficult, but the moment they launched the cloud version, it became easy.

With on-prem, there were issues with installation over production as well as the setup of the Control Room. Often, the Control Room would go down or hang, and we would have to do restarts. It was not seamless.

I was not involved in its deployment. For its maintenance, the platform team is there, and they are doing the maintenance activity.

It's very easy. They have changed it in the latest update. The latest update does not need any kind of preparation. There are just basic requirements of RAM that should be met. You just need to log in on the web browser, and it gets installed. It isn't an issue.

The initial setup is pretty simple and if any issues are noted, the vendor can assist.

The platform can be set up in two to three months. I have not seen clients directly start on the cloud version. Usually, people have had on-prem which they have migrated to the cloud. Basically, the on-prem setup took two to three months. Maybe if there are new clients who are starting directly with cloud, it could be lesser, maybe a month or so. 

From then on, subsequent automation of processes can take anywhere between two to four months, depending on the complexity. If you have a simple business process, for example, invoice processing or claims payment, that can take one to two months. If you have something more complex, that can take anywhere between two to three months.

In terms of the amount of maintenance, it depends on how many processes have been automated. Usually for a small-scale setup, if there are 50 bots or there are 50 automation, there could be maybe 5 FTEs required to maintain it. If the operations are large, with thousands of bots, the team size can vary anywhere between 30 to 50 FTEs. The larger the operations are and the larger number of processes that have been automated, the bigger the support team requirements are. On average, 1% should be able to support 6 to maybe 10 automations.

It was pretty straightforward. We originally thought we could do it with internal resources, but we had to bring a third party in to do it. So, it is straightforward if you have experience and training. Our tech team can do it now. 

We started out with a simple invoicing, and the bulk of it took about three weeks or so. Testing everything probably took closer to six weeks. We finally got it going in two months.

Setting up Automation Anywhere is a bit complex. When I entered into the RPA industry, Automation Anywhere had just been launched. Automation Anywhere was first released in 2014 or thereabouts, and I started working on it in 2017. I was just a novice when I began my journey with RPA, and it was a whole new concept in my organization as well. When we were setting up the control room server and the client, it was a bit daunting. We had to do so much in the background database and then the client. It is pretty complicated to set up the Automation Anywhere control room and the high availability clusters. 

Straightforward for unattended, for attended, it took few rounds of fails as our environment is highly restrictive

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

The deployment took one week and required two people.

In the last year, the cloud has become bigger, but before that, it was implemented more on-prem only. 

From our side, the number of staff needed for an implementation depends on the number of processes we need to deploy. For the initial configuration, we may not need many people. But, for one of our customers, there are 70 processes that need to be developed over the next 18 months. Obviously, the number of people involved will be much greater than in a project where we're looking at 10 or 15 processes to be implemented. But on average, each process takes at least two to three resources, depending on the complexity.

Once you have deployed an application, you need to maintain it. Compared to other products, it takes slightly fewer people. Maintenance on the admin side requires one to two people. We always assign one FTE for this, at a minimum. Depending on other factors, we might go for two.

There were some difficulties regarding the connection of the servers and performance issues, but we overcame them by reading about the product and seeing how things can be done. We also opened tickets with Automation Anywhere but it took them a long time to respond. There was a ticket that never closed during six months. But with an upgrade to the new release, it disappeared automatically.

Automation Anywhere has a learning curve, but it's not that hard and it's not very easy. Someone without tech skills can learn it by taking courses. When you try, you get into some problems, but in the end, it's nice and not hard. I haven't tried training non-tech people to use it, but in general, it may take people without a tech background about three months to learn it.

From time to time we need to do some maintenance of the infrastructure servers and make sure that the CPU and memory utilization is optimized. Occasionally, we need to increase the memory. There are two or three people involved in the maintenance from our organization's application support team.

The initial setup is very easy. If you are not setting it up in a virtual environment, it takes between half an hour and one hour, maximum.

We have deployed it on the cloud, using AWS.

There is no maintenance of the solution on our side.

The initial setup is straightforward. The deployment can be completed by one person within an hour.

I was around for the deployment, but I didn't set Automation Anywhere up. The deployment only required one engineer and took a day to complete. The solution hasn't required any maintenance in the short time that we've used it. 

Setting up Automation Anywhere (AA) was not that hard, but I can't say that it was easy. I don't know if I did something wrong in the configuration when I first installed the tool. You have to configure the database yourself, and I believe that the tool should configure itself.

The setup is a bit complex and was done by the AA team.

Initial setup, after cloud, is fine. It was complicated earlier, but it's fine now. When you sign up for a cloud subscription, then it's plug and play, but it's a little more complicated in the case of on-premises.

Installing Automation Anywhere (AA) is not a complicated process. How long the installation takes will depend on the client environment. For the cloud version of this solution, you just need to configure it to the use cases of the customers. For the on-premises version, you have to set it up within the client data center environment, and even that doesn't take time. Installation is straightforward.

The installation is quite straightforward. At first I was having an issue with the password that was supposed to be sent to my email, but then it came in. Aside from that, I didn't have any issues with installing it.

The solution can be installed by yourself.

There is no technical team needed for deployment and maintenance.

The initial setup for Automation Anywhere (AA) was straightforward, but the current deployments we are working on are a bit complicated because these are switch solutions, and they are not straightforward.

We have multiple systems communicating with each other, e.g. the SaaS systems we need to interface with, then we have other data that we need to introduce to these systems. Because Automation Anywhere (AA) is an on-premises platform, we are looking into whether implementing or deploying it will be safe, but I believe it is safe. In most cases, when it comes to switch solutions where you want to switch your RPA on top of other automation or other technologies, it can be complicated, depending on the technology you're with. It can be complicated when you want to integrate with other systems.

The initial implementation of Automation Anywhere regarding the elastic search and database set connection can be a little difficult. However, I am skilled enough to get through it. There were some balancing issues that my other team members had to manage. They are having difficulty in balancing when I checked the architecture properly. We determined later that there was no need for a load balance to be done on the servers. We didn't do any load balancing and then the elastic search was not done.

The first time we did the implementation took us some time because we had to set up the server based on the minimum server requirements that were sent to us. Then we had some load balancing issues which took some days because we did not have all the knowledge.

If we had all the information we would have been able to do it faster. When we were applying the certification to the servers it was a different approach because it's a Java-based solution. In the first instance, we had a challenge doing the implementation. After the initial problems were resolved I did not have any problems implementing Automation Anywhere. It took approximately two hours to get it all done.

The initial setup is straightforward. The Automation Anywhere company supported us for the installation process. They are good supporters.

In terms of how long it took, that part will be taken care of by our admin team. We are not part of that process at all.

The initial setup for cloud-based solutions are all straightforward.

The initial implementation is straightforward. Most people are using the orchestrator on the cloud or the control room and when it comes to the creator and bot runner, it will always be on the on-premise. The cloud implementation is easy, you do not have to install anything, and when we use it in the Automation Anywhere Cloud, it becomes even easier.

The time it takes for the implementation depends on the environmental requirements. For example, if it is single or multi-node architecture. If it is a single node, it is straightforward.  If it is a multi-node architecture, then it will take a little time. You just have to understand the other component that is present, such as any secondary server.

The initial setup was very straightforward. There are specific things that they ask in terms of the environments that we need to build in our typical Windows server, that is, what kind of memory and what kind of processing capability we require. I can't talk from the SaaS perspective because we have an on-prem deployment, but giving on-prem equipment based on the defined specs is pretty much child's play. There is nothing complex about it. It is very easy for developers who understand the platform. You can quickly roll out something and get it live, but you need to understand a lot of logic and the complexity behind the applications such as ServiceNow, Workday, Salesforce, etc. 

Simple installation.

The initial setup was easy, as per the guidelines shared by AA, including the minimum system requirements such as OS level, RAM requirement, SQL Server, and .NET requirement. This information was shared via the documentation.

When finding any problem, their support team is very fast and cooperative in helping to resolve the issue ASAP.

The initial setup is straightforward, as this is a cloud-based deployment.

Straight Forward

The initial setup is straightforward and does not necessarily requires technical knowledge.

Other than the CR set up with the database will take little time. Client installation and configuration was straightforward.

Not quite straightforward. Required support from Automation Anywhere Support team but that was made available at no cost.

It was easy and straightforward.

The initial setup is very simple and straight forward.

The initial setup is average in terms of difficulty.

Initial setup was a breeze and fairly straightforward with all the great support from Automation Anywhere customer service and various technical teams.

The A2019 setup was straightforward for the applications themselves. The environments in which they are set up is a different story but, that again is on a per-company basis and often lends itself to the expertise of the DevOps teams. Sometimes, those folks are not familiar with RPA or A2019.  

I found the initial setup to straight forward. Automation Anywhere has been a great partner through the entire process.

The initial setup was provided with installation documentation which was detailed. It posed no problems and in case of queries the support team was there to help.

Automation anywhere is very easy to set up. We have to download the product from the Automation Anywhere website and run it. We can set up the file in two ways either in Express mode or custom mode.

The initial setup is easier than the migration. We have to follow the steps given by Automation Anywhere for the initial setup. If we have any issues with the setup, Automation Anywhere provides support.

The initial setup was extremely complex as no assistance or guidance could be found online for my system.

A2019 has zero installation required.

Since the IT team and Infosec looked up for the setup, I don't have much idea about this.

It is the same as how enterprise applications should have in terms of complexity.

The initial setup was complex because of the confusion with the Pure cloud version. 

The setup was a bit complex. There were many IT approvals that I needed to take.

At the initial project commencement in 2018, it was still complex. With the experience of AA projects, it became easier for us to start them.

It was straightforward.

For me, the setup was quite straightforward. Yes, I did take some online help to get some issues resolved, however, the overall process was pretty easy.

Setup is straightforward.

The initial setup is of medium complexity.

The initial setup is very easy.

The initial setup was a bit complex as the control room was maintained by our clients and we had to approach them for each and every thing whenever there was an error/issue.

The setup was so straightforward for me as I was from a technical background. 

The setup was good. I wouldn't say straightforward but the process and steps were laid down clean so for us, it seemed to be cool.

The initial setup was easy.

The initial setup was quite easy, and they will provide setup documents.

The initial setup is straightforward and if there is any difficulty, the AA support team will come to your rescue.

The initial setup was straightforward. Automation Anywhere has descriptive documents to guide in installing the application on the server. Initially, I was the only person starting the RPA journey in my organization. I needed to set up the infrastructure, develop the bots, and give support as well.

Installing the application on the server was very easy. All credit goes to excellent documentation.

The initial setup is straightforward if it is done in express installation mode.

Custom mode installation and installations involving SSO and AD authentication are more complicated.

IQ Bot installation requires expertise.

The initial setup is straightforward and takes one or two days to deploy.

In general, when you set up the cloud solution, it's very, very easy. It's not overly complex. The on-premises version does take a bit more work. It's a bit more complex. That said, it's not too hard to handle either. 

The deployment is pretty fast. You're looking at maybe a 15-minute setup.

The deployment of Automation Anywhere is much easier as compared to any other RPA tool in the market. The solution itself is browser-based. So, we don't have to install complex software.

It's difficult to set up Automation Anywhere (AA) on the on-premises environment. It's also difficult to make preparations for it. You have to be ready so it can support the automation process. That was what people experienced in the on-premises deployment, but I'm unsure how it is when it's set up on cloud. Setup could be easier if it's done on the Cloud.

If you have a person who knows the utilities of this solution, setup will take one to two weeks.

The initial installation is simple.

The initial setup is difficult because Automation Anywhere does not have a GitHub integration. They need to build a patch for that. From the end point users' point of view, it leaves a bad impression.

The installation is straightforward. It usually takes under two to three hours. Full deployment can take anywhere between four to twelve weeks for one process automation. For deployment and maintenance, we have a team of roughly three to four: one project lead, one solution architect, one BA, and one developer.  

The initial setup was straightforward.

# Procurement of the license is easy, but depending upon what you want to automate and how you automate it that might take time. Setup is not at all difficult. You just take the license and install the application, then it's ready to go. However, in terms of what you're trying to automate, how you're trying to automate it, and the complexity of the problem, the entire automation process can take time.

# Implementation timelines:The time frame to implement depends on the complexities and number of the processes and subprocesses. In a typical process, the coding, testing, and deployment could range from a week to four weeks. However, I have seen it sometimes take longer because you have to continuously keep checking and testing it. Every time the code breaks down, you have to possibly start from the beginning.

My experience has been one to four weeks as the ideal time frame. However, depending on how well the process was understood and documented, there can be certain gaps which would only become evident during the testing phase, not otherwise.

# Resources: Depending on the number of bots that you have to create and the number of the complex processes along with the given budget and timelines that you have in mind, the number of developers range from one to multiple developers. The resources that you really need are developers because they are people who will be coding. Otherwise, from an ownership standpoint, we need some subject-matter expertise for the process. The people who are subject-matter experts will be needed on a part-time basis for the developer to be able to map the process well and be able to create their technical design. Then, you will need a technical master who creates the technical documentation of how it will be coded. The number of technical masters again depends upon the processes and complexity along with the corresponding number of developers.

The deployment team may not be very big. You need just the developers and a design architect, mostly two people. All the other people come and go per the requirement stage of the deployment. There might be people who are there only for consultation. Some people might be there only to approve the solution. Whenever you bring in automation, it has to be reviewed, monitored, and assessed from the organization's standpoint. There might be people who are just doing approvals for this process deployment in case it's a very complex project, and then there is a project manager. Otherwise, sometimes the technical design person doubles up as a project manager too.

Back in 2014 (at my previous organization), I wouldn't say the initial setup was smooth. There were a few roadblocks. Both Automation Anywhere and my previous organization worked on them. Eventually, everything got sorted out. Nowadays, everything is much better than what I saw back then.

The initial setup is straightforward. The Control Room and client are simple to set up, too.

The initial setup is straightforward.

The initial setup is straightforward.

Relatively the installation is complex compared to other competing technologies. Lot of things has to be worked around for Control room setup and for starting the bot development like user creation and specific roles getting assigned etc... 

It was very easy to install since it automatically validates if all required files are installed in the machine or not.

The initial setup was straightforward.

The initial setup was straightforward, we had all the pre-requisites in place.

Straightforward.

The initial setup was difficult but later, it gets easier in each progressive version released by Automation Anywhere.

The initial setup is very user-friendly, making it easy to install and ready to use software.

It was completely easy and we didn't face any issues in setting up the software for the first time.

The setup was straighforward.

To install the application is easy, but you need to prepare a few accounts during the initial setup. These include a Creator account for developers, a Bot Runner, a server, and a database.

The initial setup is quite straightforward

The initial setup was straightforward. With help of the Automation Anywhere technical support team, it is easy to set up.

The initial setup was straightforward.

Complex, since there are multiple applications involved, SAP, EMail through Gmail suite. Setting up an application in remote desktop with access to SAP and emails. 

The Express mode installation is pretty straight forward. However, the SSO (Single sign-on) enablement, which is a requirement for many customers, is a bit complicated because the certificate needs to be installed.

The initial setup was easy with the help of Automation Anywhere team support.

The initials steps are quite straightforward and the support desk has been helpful.

The initial setup was straightforward and the instructions were easy to follow.

We had an expert team who helped with the installation and set up of the infrastructure, without any major issues. Hence, the initial setup didn't require much effort and was easier to implement.

The initial setup was straightforward.

The set up was easy and straightforward, and the support was also good.

The initial setup is a little complex when it comes to dealing with installing certificates and the bot agent.

The initial setup was straightforward. The technical team from Automation Anywhere has helped us in installing. They were able to answer our questions wherever required.

The initial setup is not complicated.

The initial setup is not complex. It's also not straightforward.

If someone is an automation novice, for him to set everything up, he must be very clear and aware of the ports. It's advisable to meet the system requirements. If the system requirements fail, there may be challenges on the system and some features may not work or could potentially work if some adjustments also get made. There needs to be a mastery of the technical network like ports and servers.

If I implement it now, if I just install the automation in my server, then it's a one one-time installation

The deployment time isn't too long. It may just take two or three hours if someone is completely aware of what we are doing.

In order to deploy the solution, one person is enough. You don't need a whole big team.

The initial setup is quite long and full of different phases. It would take only one official AA installation guide with the most detailed step-by-step description and one image per step, without the need to consult more than one guide.

The setup is good but the control room setup takes some time.

The installation is quite straightforward as they provide us with an installer package that guides you through using wizards. But the pre and post-installation process can be quite complex and laborious depending on what features you need to enable. In some cases, these feature configurations require the underlying services to be restarted from the server backend. When using virtualized environments in the cloud connecting on an internal network domain, there would be extra care needed on the network configurations to ensure communication channels between the machines are properly connected.

The setup is straightforward.

The initial setup was a bit hectic, but later on the with the help of the wonderful support team, it went smoothly.

Straightforward, installation with disaster recovery approaches. 

The initial setup is straightforward.

Setup is very straightforward and there is a complete guideline provided.

The initial setup is straightforward.

The initial setup is mostly straightforward, although there was some initial confusion with the right version of the tool to be used.

The initial setup was pretty straight forward, and the installation is easy.

It was very easy. The Automation Anywhere community is extremely helpful with answering any questions that we had throughout the process, or any sort of concerns that we had. So, it really wasn't difficult at all.

The initial setup was straightforward, even a complex setup can be set up in 20 mins if you have all prerequisites.setup can be complex if there is a HA , DR implementation, as a architects we need to factor in lot of variables. some are target application access,  MFA for the application or windows authentication, credential management, data accessibility, network reachability , underlaying hardware, PaaS offering in cloud(depends on the cloud) , VDI or VM template to choose (Makes huge difference in performance and costing), citrix or native application . Overall simple install, but huge planning to figure out the overall feasibility and effectiveness of implementation

The setup is easy but it is better to have AA support person during that activity.

The initial setup was straightforward.

We do have an infrastructure team who supports us with the installation. If you have the basic requirements for the infrastructure, hardware and software, the installation process is pretty smooth. We have user manuals that are pretty well prepared where I can read them, then install it. That's good for the setup or for the person who is installing it from their end. It's sort of easy. You would require a bit expertise from someone at work; a person to help you out.

Straight forward

It is not a one click installation. We need to need to install the SQL Server, then we need to connect them all. This is where I think a normal agent wouldn't be able to do that. We need to deploy senior engineers to do this since it is slightly difficult. We had to train our IT guys on this.

Compared to the competitors who have a fast, swift installation, Automation Anywhere's installation is hard and needs work.

The documentation is very clear in respect to the installation and migration. If there are any bugs or anything goes wrong, the technical support team helps. The installation and setup are very straightforward. It was very easy for us.

It was very easy and anyone can do it. If they are doing for lab or personal setup. For the client AA teams are helping.

The initial setup was straightforward. The new version of A2019, which they have introduced, is much easier than what we are doing now. It's all cloud-based and very easy to install. The whole experience is better.

The initial setup was not that great. The road was very up and down. We struggled. A lot of the features were not compatible with applications which we are using. That was the reason. This was the initial days, we are talking about 2016 to 2017. The buzz was not as much as we are having now. 

From that time until now, Automation Anywhere has upgraded their systems. They are at a good pace now. But, at the initial stage, we struggled in terms of getting things sorted. We also needed support, so the Automation Anywhere team sent some support to us who helped the developers in terms of coding and finding solutions.

Some of the features were not very well identified at that time. The Automation Anywhere team provided the support for that. Initially, it was like a rollercoaster for us.

The initial setup was quite complex. We have faced an issue. During the initial implementation stages, it took longer than we expected. It affected our timelines to a certain extent. Once that was done, it was quite seamless. I think now that they are coming out with a cloud solution, this will help a lot in reducing the implementation duration. It will help future clients get results even sooner.

A tedious task, they have reduced it to a normal task. So, I feel comfortable because Automation Anywhere (the company) is working toward minimizing our efforts, and we are happy with that.

It was quite straightforward, considering that people are able to understand what they need. The need is clear, so it's a pretty straightforward solution.

It's getting simpler day-by-day. The innovation that Automation Anywhere is taking up in terms of getting started in setting up their environment, is making it simpler. I see no problems. It's only going to be better and better. It gives a perfect platform to jumpstart. 

More than that, the initial training that we are being provided also helps us in getting a good, smooth start.

We are facing some issues when installing the software because of the antivirus. It won’t allow us to install it. We need to disable some features during the installation of it. Sometimes if the bot is running, we need to disable it. This feature needs to be made available, but made better than this.

It depends on how professional you are. If you are good, pro user, it will be easy for you. Even if you are a new user, there is an express version of installation that you can use and install it very quickly. If you are a pro user, you can always go with the custom mode and the installation is still very easy.

The initial setup is easy. As a first step, it will ask for the location. As a second step, if you want to add an SSL certificate or database. There are just four steps of installation. It's very usable. Anybody can easily install Automation Anywhere, if they want.

We are currently developing the bots. Once, we are done with our development, then production will finally start.

It is very straightforward and easy to install. They are going to introduce version A2019 online without a need to to install. There will be just one click of the URL to start developing within a minute or two, and it will start. There's nothing easier than that.

The installation piece was sort of complicated because we are new to the business. We are new to installing Automation Anywhere services and the services that they are providing. So, we are sort of expected some kind of installation engineer to come onto our premises and provide the support, rather than remotely.

We have IT people. So, if people are coming, IT and the installation engineers sit together and install everything. People are supportive, but IT is in a different location from the installation engineers. Connecting everyone together is sort of hard. However, the installation piece is very straightforward. Though, at the enterprise level, making it work takes a long time.

In this forum, we have come to know that they're also coming out with a browser version. Today, we have to install the software on a PC, desktop, or server. What they are coming out with now is like a browser version, which quickly can be applied instead of an installation. That is amazing. That will be disruptive. You can now deploy hundreds of bots at a very fast pace, and that's an amazing thing to look forward to.

When you are not aware of RPA solutions, it definitely looks more complex. But once you are done with your first implementation, then it becomes very straightforward. Going forward, this will be even more straight forward, because I learned from the Automation Anywhere guys that going forward all these bots or engines can be created with very user-friendly drag and drop functions. This would become more of a plug and play solution for everyone, maybe for the people who are non-technical as well. So, to begin with, it is really complex because of the knowledge that people do not have. But, later on, after the first implementation, it becomes very straightforward.

We have two models: 

1. With many clients, we actually go and have them implement Automation Anywhere in their own premises.
2. The second model has actually proven more beneficial to lot of our clients. It is where we have set up the bots in our own EY private cloud on Microsoft Azure where we have implemented certain standard tax processes. So, we only get clients to migrate their processes onto our platform. There, we just take out the pain around the whole implementation, because it is not really relevant to our clients. They just start to get outcomes, and don't have to worry about it.

The initial setup actually came before my time at the organization. I think it is a little bit of an ongoing struggle, because we don't deal with the infrastructure. We have a separate infrastructure team that sorts all that out. So, sometimes there are communication issues just trying to get our internal IT team onboard to run through the installs and that sort of thing. But, definitely with the new cloud version coming onboard, we'll be looking toward going to that. Hopefully it'll resolve some of that friction that comes about through the install process and complexity.

Obviously, the easiest way to create a bot would be using things like keystrokes. It's very intuitive, simply entering the database and what you would see on a keyboard. However, it doesn't really relate to what you're seeing on the screen. So, quite often, you'll be entering data in the wrong field if there's a performance issue with the system. While if you use object cloning, which is another function within the software, it's more dynamic. It'll wait for certain fields to appear, then you will lower the risk of breakages of code.

It's certainly straightforward. For us, it was a bit of a test and learn approach. There are certainly guidelines published by Automation Anywhere for the recommended infrastructure. We found that they weren't completely applicable for us, and we've had to tinker with the infrastructures as we've got along. Without getting into the technicalities of it, the out-of-the-box approach that was suggested to us didn't suit our environment. So, we did need to be a bit more creative about how we did the deploy.

Again, this is why I'm excited for A2019 because I think that we will just overcome all those problems and it will allow us to really drive through and scale a lot quicker. Infrastructure is probably our biggest challenge at the moment.

The initial setup of this solution is easy, although sometimes you have service problems.

For example, we have a server set up as a load balancer, and sometimes these two systems have a problem where the nodes are not synching. I think that it is an issue with Automation Anywhere having a bug in the system. This is a problem when you are selling it to the customer because you have to make sure that it is reliable, and will stay that way for some time. You cannot expect companies to change their products every now and then, or continually upgrade versions. We need things to be stable for at least one or two years at a time.

There are quick user manuals clearly available. We can easily install the product and start working immediately. There are very big eLearning resource contents available. With the help of Automation Anywhere team in India, they are providing a lot, just to support student and faculties in universities. There is a quick learning process with the help of eLearning resources.

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

Now, it is a big complex to download the product and install it, then again to install the patches. So, it takes a lot of time to download it. But, the newest version that they are coming out with is web-based so it will be quicker on the cloud. As the CEO said, "Booking an Uber takes more time than downloading Automation Anywhere and even making the first bot."

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

I was partially involved, not fully involved, when they were doing the IT Bot setup and migrating to latest version. It went well because the Automation Anywhere team was there. They helped us migrate from the older version to the latest version. Whatever code that we had written in the older version, that needed to be migrated to latest version. With all these things, they helped us out.

It is very straightforward.

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

It is very straightforward. Today, in the learning track, I was looking at the latest feature which is coming in A2019, which is very nice, because it is a web-based. So, we can do our development while sitting from anywhere. We don't need any type of installation. It's a web-based. Nowadays, everyone has the Internet. So, it is very easy.

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

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

It's a bit straightforward. If you go through the user manual of Automation Anywhere, the stuff with automation there is quite easy. A layman or common man, who is new to the Automation Anywhere can install it quickly. So, it's easy.

I've seen different versions of Automation Anywhere. They have evolved the setup, so even a newbie who comes to RPA or Automation Anywhere with the setup installation document that they provide, it's straightforward because all the steps are mentioned in the document. I've seen that even a newbie can install Automation Anywhere. So, the document that they provide is top notch for installation.

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

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

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

The development process took us about six months.

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

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

One thing that's very good about the setup is that it is one-click. You just have to click to start the installation and then you configure everything as you go through the installation. One of the best parts of using the product for us is that it is easy to install and configure which fits in our business model.

The initial setup for the program was not straightforward. It was definitely complex. As a layman who is unfamiliar with the product, I do not think people can implement it easily. Even people with a little bit of knowledge about the type of robotic engineering and applications are going to go through some challenges where they need help from Automation Anywhere.

So far in this installation, we have had to integrate with some internal processes. Also, we needed to incorporate solutions for the respective firewall openings to the internet. It has taken almost one-and-a-half months to do the basic installation of the software. It is not like pushing a button.

We initially deployed everything on server. However, the permission required Excel to also be a part of our process to be automated. So, we received some complaints on it this. This particular thing cannot be deployed on the server because of the license that we were holding. What I came to know is this feature is not available.

When we started out initially out, we were told that the infrastructure we had would be supported by RPA. We were going to use Amazon as one of our platforms, but it did not happen, so we had an initial challenge. We were behind our schedule by around seven months because of this mistake. Both of us learnt from our mistakes. We now have a sustainable RPA. But, at the start, this was one of the big challenges, selecting the right infrastructure.

The initial setup is good.

The initial setup is straightforward. I don't see any complexity involved.

The initial setup was straightforward.

Approvals are taking us more time than development. For the bigger products, it takes four to six months to scale. If it is a smaller product, then it can take 45 days.

The best person in our organization to speak to the complexity of the initial setup is an IT guy from my team. He was responsible for a series of calls to the tech support team and he was involved in a lot of discussion with the Automation Anywhere team initially. Obviously we had contact with technical support so it may not have been so easy to do the initial setup, but I think that is quite acceptable or understandable. Anything which is new will probably be something you need to spend extra time on during the initial phase-in of a new product.

Beyond that initial setup and normal learning curve, I haven't seen any problem with respect to adapting the RPA technology in our company. It has been pretty smooth. The technical support team was great in terms of supporting anything we experienced in the way of technical issues. The only issues we experienced after that have been some issues with respect to using a Citrix environment. We are finding it difficult to automate on Citrix efficiently.

We have been continuously on calls and meetings with the technical support team. They have been coming up with a lot of innovative ways as to how they can fix that problem with Citrix. Of course, we are still in the midst of finding a solution to the issues. But I know for sure with the support that I get from the support team that we will definitely have a solution in the near future.

We had different people come in and set up the process for us, initially. After that, I started putting in the automation myself, and it is becoming faster and pretty easy for me.

In the beginning, it was a little bit complex and difficult for us to understand how to get things running. We reached out to technical support for help.

Initially, we had planned on going simple. Then, we wanted to be centralized and have a cloud-based environment, which is where we were facing a lot of challenges. One of the challenges was DB connectivity for accessing SAP, which was a security issue. We also had some trouble automating web pages.

The initial setup was complex.

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.

The initial setup was complex. Because we are in the finance industry, the initial strategy had to take a lot of data into account which needs not to be secured and not exposed to the outside world. So we struggled a little with how that has to be implemented. For example, passwords are critical data. We came up with a cyber bot at that point in time to deal with the potential password issues. 

The business team has a lot of doubts about how Automation Anywhere is being implemented and the processes it affects.  Because of this, it was really a huge effort to make them understand what we are doing. Any time we would have to make changes to infrastructure, even a small change on the infrastructure side could make an application unstable or make a bot come down.

We have got to put in more hours at this point to make the implementation stable and further deployment possible.

Bot creation process:

1. We have a PDD document available once the use case is identified. 
2. Once the PDD is available, if it is a legal/security issue, then we go for the next stage: development. 
3. We develop the SDD. 
4. Based on the SDD, the bot is developed. 
5. Once it is all developed and the UAT testing is done, we'll show it again to the legal/security.
6. Then we go for the approval across the business teams. There will be lot of approvals required. 
7. Once it is approved, then it goes to production. 

We'll create a bot ID in-between once the use case is good.

Based on the complexity of the bots, it takes six to 16 weeks for us to create bots (pilot to completion).

Automation Anywhere is installed with a VM, then it will be handed over to us. That's how it works.

It's easy to set up.

It was complex to begin with because we are all so new to it. Getting the business come up with use cases was initially difficult because everybody was new to it. Over a period of time, we got to know what has to be done.

I thought the initial setup was straightforward and easy.

We have a high-availability setup, so it was not a straightforward one. 

I was not involved in the initial setup of this solution, but I have been responsible for some of the updates. The update process is not complex. 

The initial setup of this solution was straightforward.

The initial setup was very straightforward. It didn't really affect our processes at any levels, which really helped. The process was fast and easy.

The support team kept our team calm.

The initial setup was complex.

The IT team wasn't involved directly at the start, so the business sort of started it on their own. Then, the product over came to IT, and we were blindsided by the requests. That was when it became complicated.

It is easy to set up.

The deployment was easy and straightforward, and the POC was easy to perform.

The initial setup of this solution is very easy.

The initial setup of this solution is simple. We had the required support and the materials were all delivered, so we were able to do it easily. 

The setup was straightforward. However, the reinstall was not straightforward, but it wasn't complicated either. There was an issue with configuring the database once.

The bot for monitoring applications did not take too long to create, about two weeks went into it. After that, there was some back and forth for changes. Then, we created another bot for scanning clients' mailbox. It creates a front office ticket, depending upon what's in the mail. 

The setup wasn't easy nor was it difficult. After one or two times, the setup became easier.

The setup and onboarding processes were easy and straightforward. It was very easy to onboard because it was more about the data. We learned how to streamline the process during that time, which was good.

The initial setup was straightforward. I updated the license files after we got them. I needed to update them in the Control Room. I think a non-technical person would be able to do this.

The setup is complex because there is a lot of customization. The availability of the deployment was not really fast because of the amount of work we had to do. It is not so difficult but it is time-consuming. It might be an area where the product can improve.

I do not think it is straightforward to start working with this product. It's a little complex to start out working in the database. After this when you gain a little experience with the product, then you will understand it and be able to smooth out your processes and how you approach development and it will be easier.

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.

With our current knowledge, the initial setup process is fine. The setup was easy for me.

I was not involved in the initial setup.

For the bot creation process, we have a solution architecture team. They will analyze the process and check for feasibility before proceeding to next level. They'll check whether the process can be automated, then prepare a document which will come to me. Then, I'll try to make the SDLC. I'll check whether the process is possible, then we'll go for development. This is the structure:

1. Analysis and feasibility study.
2. Documents preparation.
3. Development.
4. UAT.
5. Deployment.

There's a process requirement. If I get request today, it will take some two to three months to develop and close the incident.

The initial setup was really straightforward. We spoke with AA about what kind of architecture it needs, and they have created it in a way that is very robust.

When we first started with this solution it took about ten days to learn how it works. Afterward, it was quite straightforward to work with it.

I was not part of the setup process.

The initial setup is straightforward with no hassles. 

For the implementation, almost everything was a little complicated. We faced issues actually but everything was manageable and then we addressed the issues and the initial setup was fully completed.

Mostly the issues had to do with security. The product was new to us and we had to set everything up for the first time so we had to learn about some things, like how to deploy the security features correctly. That is the kind of issue we faced as a learning curve.

During our onboarding, we had some issues and during integrations, we were having various small issues. But the reason for all of that is this was a new technology for us and we had to learn something about it. We learned by working with the product and all the integration issues and security things have all been resolved.

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 scaled up pretty fast. Initially, it took a couple of months for our pilot, then we were up and running pretty fast.

We follow the same standard methodology which Automation Anywhere recommends for creating bots. When going through the process, we try to optimize it before we start doing development, then making sure the process is suitable for automation. It's a standard process that we follow across the board.

We still do not have a setup in place. We do have licenses, but we are trying to have more bot programmer licenses in place. As such, the deployment is still in progress, but from what I understand it is simple and straightforward. I expect that it will be completed within the next week or two.

Most of the team who were working on Automation Anywhere had a little programming background, such as VBA or Java. Initially, we struggled a bit to use the rich commands but Automation Anywhere provided initial training when we got our licenses. Somebody came and gave us training for three to four days. Then, it took about three to four months to transition from the PoC to using the bots.

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.

The initial setup of this solution is a little bit complex, but if from the start you know where to go, what to click, and exactly what each button does then it will be very useful. If you have somebody to guide you then it will be much easier.

The initial setup of this solution is pretty simple.

It takes approximately a week and a half to set up automation. We have already had some examples and demos, so setting up is very easy. Learning will take some time after that.

The initial setup of this solution was sort of complex for us. We are at the initial state of it, and it is quite challenging because we didn't know what the technology was all about. Each and every day we learn new things, where it is not the same thing that we had learned before and already implemented.

The initial setup was straightforward. Our processes are not largely complex, so we understood the background of how it was being set up.

Initially, I found the setup of this solution to be complex.

Before getting started we had to install the SQL server and perform the migration. Then, it involved user accounts. You have to create a new user and add the details, which is quite complex. Then, whenever you are installing the Enterprise Edition, you have to perform setup that includes the IIS settings. Overall, it was quite hectic, and some of the people were not able to do it.

We installed this on a cloud infrastructure and had a lot of challenges. However, there was a dedicated support person who was helping us to do the installation.

The initial setup was definitely complex. Layman people cannot do it. People with a bit of knowledge need some help from Automation Anywhere.

It took a month and a half to do the basic installation of this software along with some internal processes related to our firewalls.

It was a little complex due to the IIS Manager and a lot of other features but with version 11 and beyond it is much easier to install and configure.

The initial setup is not straightforward, but it's not complex. if somebody knows how to do it with an SOP, they can do it. The setup is tedious, but it's doable. 

When we started, we were not aware of the entire architecture of Automation Anywhere. It was like a new technology. I have a partial technical background, so I could easily understand the tool and its architecture. However, I observed that non-technical team members could also easily understand Automation Anywhere's commands. They way that the bots are built makes it very easy for non-technical people to understand the logic pieces if they have logic skills. They can develop bots. Compared to other tools, where users should have some technical knowledge, this is an excellent differentiator for Automation Anywhere.

We had a major issue when it came to single sign-on. We couldn't get it working. There was a bug in Automation Anywhere that eventually got solved just a few weeks back. However, we have not implemented it. We have had hiccups with the single sign-on, but otherwise it was a smooth setup. We are not using single sign-on because of this bug.

The initial setup is very straightforward. It did not take more than a few minutes.

It is easy to set up. You can do it from anywhere using the Control Room. It is not a tedious process. 

I am used to these types of setups as an SQL engineer.

The initial setup was fairly straightforward. Automation Anywhere did a lot of hand-holding through it

Initially, the implementation was tough. When we started, we were trying to do too much at one time. When we started just playing with small, bite-size pieces, rather than working with big chunks, we started to make more progress. That change in scope kind of helped us to scale things up faster.

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.

The implementation process is complex, as there is integration with other applications. We need to understand the other applications' requirements. It requires us to convert their business logic into automation. That is where the complexity is.

Our onboarding process was pretty good. We got access to all software that we needed to learn and utilize. The Automation Anywhere University is really good. In our business, the person who was onboarding us helped us to understand how to create a center of excellence and what verticals we needed to improve. So, the support was there. We are gradually becoming a center of excellence ourselves.

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

I was not there when the solution was initially set up, but I assisted with the upgrade.

There was a misunderstanding between the infrastructure team, our team, and the Automation Anywhere team, which was a major issue. It was unclear how the servers were going to be set up and who was going to install. Nobody knew what the requirements were, and as a result, things took longer than they should have.

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.

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.

The initial setup of this solution was a little difficult. When we had trouble, we started calling the technical support team and they solved it. It was a little messy in the beginning.

I did not perform the initial setup of this solution, but I have been responsible for one of the upgrades. It was ok. They gave us support and gave us the manuals to do it. I found that it wasn't a problem.

It took us two months to scale from PoC to our current number of bots. 

I wasn't involved in the initial setup. I just use the tool.

The initial setup is a little difficult in the beginning to develop an entire infrastructure that the IT will support, but as you grow, you find a way to develop the whole architecture.

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.

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.

The initial setup was good.

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.

The initial setup was a simple process. 

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.

The initial setup is not complex. It is pretty simple. We started with small processes. then we moved onto complex types of environments. The implementation in terms of technicalities, it was not complex. In terms of getting into the nitty-gritties of what, where, when, and how it would come all together, that is the challenging part. It is the understanding the entire process of transforming the requirements into something technical. 

The initial setup was definitely complex. It took us and our IT teams quite some time to get everything set up the way we needed it, with our three environments. Part of that was getting the Control Room installed and set up, as well as making sure that the client was running properly on all of our machines. It definitely took us some time to get that all running smoothly, a few months to get everything deployed.

We're a global company and our U.S. offices have been running this as a pilot for global. We've been sitting with different departments and stakeholders to try and understand what processes might be right for automation and for this kind of solution. We've been compiling that list, prioritizing, and trying to get the buy-in of the people who will be most impacted by it. We've also been trying to get some early, big wins as far as ROI is concerned, and as far as demonstrating the value of the technology, so that we can continue to roll out more, here in the U.S. and, hopefully, more broadly later on.

The original setup was easy. What was difficult was adding licenses. I went a month where I was paying for licenses that I couldn't use, for various reasons. That was painful.

I'm not familiar with how long it took to stand up the environments. It was pretty simple from a PoC point of view, with the free trial licenses that were made available to us by AA in conjunction with their preferred systems integrator. That was fairly painless. Standing up the production environment was relatively painless as well. We had no problems whatsoever there. However, as we scale and add licenses, we have challenges.

The initial setup is pretty simple and fast. It can be done from the web Control Room, which can be done easily.

For coding, we are keeping the information in XLS or XML files. We use MetaBot to retrieve the data. We keep our URLs in an Excel file, so when we go to our production environment that it will automatically take the URLs and implement them.

For the implementation, you just follow the proper process on how to deploy the proper hardware configuration on the production environment. The process does not take that much time as you push files to the Control Room, then from the Control Room, you can download the client. It does depend on how many bots you are implementing and how you are scheduling them.

Automation Anywhere is deployed from a deployment guideline in a step-by-step process. Automation Anywhere provides some deployment guidelines, which can be referred to.

The initial channel setup for was quite easy. However, we had to configure the control room. With that, we had to be very careful.

It took me half a day to deploy. I installed the SQL Server, the control room, etc.

It is quite straightforward doing an initial setup of Automation Anywhere. This is because it has a well-defined installation guide which talks about how to install Automation Anywhere software. However, automation only works when IT support is quite adequate. So, if the IT and infrastructure teams at the client site are not supportive, for example, then I'm not able to provide admin rights or open security ports. That is when the entire installation moves into a messy state. There is a way to cater to such issues. Because this is a new technology coming, if you meet with the IT support team along with the CISO of that particular organization and set the right context and objective that company wants to achieve with automation, this roadblock can be fixed.

Otherwise, I haven't faced any issues with the setup.

This initial setup was straightforward. The documentation that was provided was thorough.

The initial setup wasn't complex, but it wasn't straightforward. It was somewhere in the middle.

The installation and setup of Automation Anywhere are quite simple. Most of the time that I've worked with customers setting up Automation Anywhere, it's gone off without a hitch. It's pretty much as simple as once your infrastructure is in place, you install the client and Control Room, then you can be ready to go building users and getting your automation started very quickly.

It was a straightforward setup. There are definitely some hurdles that we had to go through. 

From two perspectives:

1. The initial setup, as a partner, was very straightforward.
2. The initial set up from a technology point of view, although it was unfamiliar to us when we started, was also pretty straightforward.

The initial setup was somewhere right in the middle. It wasn't super simple. We could've probably done things a little better than we did, but it also wasn't horribly complex.

We have seen both straightforward and complex initial setups. If you are behind a firewall, it is relatively easy to setup. When you are hosting the application, that is when it is a little more complicated (we actually host applications for people). You need to talk to the IT department, as you are actually outside of their firewall, then you are coming back inside their cloud. 

Depending on the architecture, it can be relatively straightforward, and it can be put up in just a day or two. Whereas, if you are hosting it and coming back in, it is a little more complicated.

We have had the solution for a long time. As you go to cloud-based solutions, there are some nuances, which is less about the initial setup and more about when you have a version that you need to migrate or update. This is an area where we have faced some hiccups, but we were able to get around them.

The initial setup was pretty straightforward. I did it myself and I'm not an IT guy, so it wasn't super-difficult. It took me a couple of hours, including configuration. Our IT team set up the actual virtual machines themselves, but the installation was done completely by me.

Our implementation strategy was that we started super-small. At that time, we started with five bots and the Control Room. It wasn't overly difficult. I just followed the documentation provided to install the service and configure everything.

It's straightforward, easy going. Anybody can start that. Only thing is that the people should have common sense.

The initial setup, at times, has been a little undefined, in terms of requirements, just because people don't know the process, nor what they're going to need, as a result of putting something into production. On the other hand, I think those were growing pains that we experienced probably two or three years ago less than we experience today.

If you have coding background, it's very simple. There will be no effort at all. For a non technical background person, it might seem a little complicated at the start, but with all the drop-downs and pulls for loops and ifs, it gets really easy.

In terms of onboarding, we step back and think about how to leverage this technology. We have created some IP around this and leverage our deep learnings from several implementations. We apply the process and domain expertise and determine which process needs to be automated by leveraging what technology and what ROI will you get out of it.

We leverage the process insights technology, we bring that to the table, we understand what processes need to be automated and we apply the relevant technologies. Automation Anywhere is one of the many we apply in transforming across automating the entire process end to end.

The initial setup is straightforward. It's a great environment to use.

The setup was a pretty complex undertaking. We're a global company. We have our virtual IT management done in Switzerland, while our hardware is in New Jersey. So to get the different stakeholders of Automation Anywhere within our company working together to iron out the Control Room stuff and the virtual side of things, as well as the on-prem software side of things - to have it all connecting properly - was a pretty complex implementation.

The setup of just the developer environment and the actual Bot Runners took about three weeks. As far as building the bots goes, we haven't scaled as far as we can, yet.

We didn't really have a deployment strategy, per se. We just followed the action items that we were given to do by Automation Anywhere. We're still working on how to implement it across our organization. We have Automation Anywhere coming in with some Professional Services people in a few weeks. We still have to work on getting things moving with the managers, teaching them what are good processes to automate, etc.

The setup is straightforward. Automation Anywhere provides customer success managers to help with the setup.

It took six months for us to start our bot process because of issues, like security and setting up servers.

The initial setup was complex because we had to make sure all the security aspects were approved by our leadership.

We are having issues with setting up the newest version. It doesn't install, and there are not a lot of things to do with it.

The initial setup was straightforward. It is a very guided experience: out-of-the-box with Automation Anywhere University training.

The initial setup was straightforward.

The initial setup was easy. First, we create a bot. Then, we send the business an approval. Once they have verified everything, then we need to open a ticket. Finally, the bot is deployed to production.

The initial setup is straightforward, but the scaling was an issue.

The initial setup is a little complex. For a person with a technical background, it is doable.

The setup is mostly straightforward.

The initial setup of the software takes time.

The setup was very difficult. It recognizes the correct fields that you put into it, but it resulted in complex scripts.

The initial setup was straightforward.

The initial setup is pretty straightforward, especially as a PoC. With the controls, it could be a bit more complex.

While the initial setup is fine, the servers have caused us a few headaches.

Our first bot was complicated, and probably not the best thing to start with. However, as we learned from that experience and more of Automation Anywhere's features, we can now push bots out fairly quickly. The process is a lot smoother. Our infrastructure and design have improved tremendously.

The initial setup was not complex, but we did need assistance to get it up and running.

The initial setup was straightforward. We have a center of excellence that does a lot of this stuff.

In the initial setup, we had difficulty in our environment. We actually had to have them come onsite for two days to get us deployed, and even then it took another month before we were finally operational. I think our environment was a factor, but we also did find product failures.

We installed it but it was not operational. Everything from the way things were configured to our license not being set up accurately was an issue. So we had configuration setups such that we couldn't process and it took a while to get that figured out. To be honest, one of the issues was that it was around the holidays and the right people weren't available to help us out. It took us a week-and-a-half just to resolve the fact that there was a button that had to be un-clicked.