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, 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.

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. 

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 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. 

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. 

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 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.

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

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.

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.

The initial setup is easy. It has its own orchestration and you just need to deploy it.

Any maintenance would fall under your organization's contract. 

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.

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. 

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.

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. 

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 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 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.

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 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. 

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. 

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 initial setup is straightforward, except when setting up with cloud-based services, like Amazon. The cloud-based setup process is complex.

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

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.  

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 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.

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.

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 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.

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.

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.

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

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.

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

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

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.

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

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

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.

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.

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

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 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.

# 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.

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.

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 basic setup was straightforward. Deployment took two months. Our implementation strategy consisted of three servers, one for Dev, one for QA, and one Prod, as well as five bot runners: one for Dev, one for QA, and three for Prod. Finally, we have one administrator and one backup. AA provided the needed support to get the solution up and running quickly and smoothly.

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 initial setup requires some expertise. We formed a team to handle the preparation, installation, and configuration of the platform internally.

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.

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

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

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.

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 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.

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.

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.

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.

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.

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 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. 

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. 

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.

The initial installation is simple.

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.

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 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 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 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 pretty straightforward in terms of setting it up. It's not a lot of work, as compared to what you would do in Blue Prism, or even in or WorkFusion. I would say UiPath is the easiest to install and configure, while Automation Anywhere would be number two. Blue Prism would be way down because it's difficult installing and configuring it.

It doesn't take much time to deploy Automation Anywhere. We have built a script. We just run the script and within three or four minutes we are done. We don't really install Automation Anywhere by running it and then monitoring it, rather the script automatically installs it. That script lightens our load; we automate our own jobs as well.

In terms of implementation strategy, we have a set of requirements for the client's environment and hardware. For the environment, we need to look at the .NET framework, which version, the directory structure, folder structure, paths. And there are multiple items to be checked out regarding the hardware: We need to look at the RAM, the hard disk space, the connectivity. There's a lot of checking which must be done, but we do that through the script itself.

We have all the environments set up in one local place and once the script runs it goes and installs all the required software components. The .NET framework will be installed, the run-time engine will be installed, Automation Anywhere will be installed, and the policies will be set automatically for at least the end user, so that we can go and create more users.

Once we have the hardware, and once we are ready to install the environment, it takes us about 15 to 20 minutes.

For deployment of Automation Anywhere, we don't need a lot of staff. But when we are deploying the bots, we generally have an experienced guy who will look at the deployment of the bots within the Control Room. That's a different scenario altogether.

We don't require a lot of people for maintenance. What we do is, we transfer some of the load to the client's staff, in terms of monitoring and scheduling. Of course, we have one person keeping an eye on the entire thing. We have one person on a chargeable basis per client location. And this person also doesn't have a lot of work, so sometimes this person moves among the sites if there is no problem at all with the installation.

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.

The setup was straighforward.

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.

The initial setup was complex.

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

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.

The initial setup is pretty straightforward. The videos on the Automation Anywhere University are extremely helpful during this process.

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.

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.

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 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.

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

The initial setup is very 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.

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 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.

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.

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.

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, 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, 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.

When we went to version 11.2, which we set up brand new, if I had to do that myself, it would have been a bit complicated. I worked with an installation specialist from Automation who was awesome. He made it very simple. We had some of our own server and DBA personnel on the line, and he documented everything for us. At the end of the day, I had all of the information that I never had on our original 10.5 environment, which has made it a lot better.

The initial setup is a complex process that they make very straightforward. Their installation is very quick. It was relatively painless. Any pain that we experienced was on our side because we had to make sure we had the right permissions or direct privileges, or that we had a firewall that was configured properly. We had a relatively complex site where we had clustered Control Rooms and we're using load-balancing. Within a day or so, we definitely have it standing up and, typically, within the same day, we have it configured. That's assuming we don't come into any complications on our side where we have to go ask for permission to get access to something or for a new certification. Overall, their installation is fantastic.

It took about two days to stand it up, to configure it, and then to smoke-test it, and make it productive.

The setup was prior to my coming aboard, by a couple of months. Our company had talked with IBM and Automation Anywhere, so the strategy was definitely to go through the documentation and to have an Automation Anywhere expert help with the development environment. After having meetings and reading the documentation, they had a hand-holding approach in development. Then they documented the steps. They went into the next environment, ran through their documentation, updating it because there were some changes in the clustering as well and the load balancing. They got that standing up and documented that. By that time, they felt comfortable in production. They were able to go through and repeat the steps without having to go back to Automation Anywhere or IBM for support.

We had to repeat the process here about two months ago and set up a new model and set up a new production environment and some more servers. That's where I get the couple-of-days timeline from. I was following their documentation with our internal guy who did it. Obviously, we had some guys that do database, some guys that do the Windows Servers, and then, myself; I was doing the actual client side. We're all on the phone at the same time taking care of it and it's less than a day.

In terms of the very initial setup, starting from the planning stage, I wasn't here at that time. I would say that it was about four to six weeks, but that's mainly because they had other stuff that was going on, so they were just having the weekly meetings until they got ready to try it. I do know they started talking in May and by the end of July, they had it done, but there were gaps where they weren't working on it in there.

The actual length of time may be about a week because we have to do a change request. We have to go through a procedure where we get approval from the business managers and the lines of business saying, "Okay, we're ready to go live. We're going to go ahead and push this into production," and we need to do backups and have a contingency plan. We then have a meeting and make sure everybody is okay with the current test results. Once all that's done, we can deploy in one night, have it smoke-tested, and have it running the next day.

For the actual deployment steps, you really only need one person but, typically, we will have the developer, a business person to do a smoke test, a Windows person and a database person; four people, only because we have separate roles here. Technically, it only takes one person, but developers don't have any permissions. But we need a developer in case something goes awry to help out the build person who's pushing it. If there's something they can't do, then they need the Windows person to handle any kind of Windows services. And if there's a database issue, you need a database person to run a script. Four would be max, but that's actually very typical in a lot of corporate deployments.

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.

Simple installation.

It was easy and straightforward.

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.

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.

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.

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 thought the initial setup was straightforward and easy.

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.

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.

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.

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.

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

Every tool has challenges. With Automation Anywhere, it took us a bit of time to stand it up initially. We tried to do it in a virtual environment, which caused us a bit of headache. It could have been smoother in this aspect.

The initial setup was pretty straightforward. It was just a normal on-premise setup for three environments.

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.

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.

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.

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.

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.

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.

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.

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 pretty straightforward. 

One of the things that we did was purchase the solution originally through IBM, as they had an value-added layer on top of it. Once we had another group come on, they purchased additional bots directly from Automation Anywhere, and they wouldn't integrate well. We had to uninstall the solution that we had purchased from IBM and reinstall those bots to move forward. 

Now, we purchase our bots directly from Automation Anywhere, because this other layer from IBM put us behind, and I don't know if IBM has resolve this issue or not. It was a bit disturbing and surprising, that during the sales cycle, we were told by Automation Anywhere that this layer/enrichment was not seamless to the upgrade process.

It was really straightforward and made sense to me. Put it this way: I have always been able to see where the product is going. It seems somewhat impressive the way it's designed, and that's why it made sense. Some of it might have been due to the fact that I took the classes at Automation Anywhere University. I got to talk to the developers, so I could see exactly what they were thinking, and it made sense.

The installation of version 11 is fairly straightforward. I do like the new server architecture based on Java, as it is very straightforward.

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.

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

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 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.

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.

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.

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 initial setup was pretty straightforward. The document was good. Everything went as expected.

The initial setup was very straightforward.

The initial setup was pretty complex. Everyone who offers this platform is still trying to find the right tools which go with it. Without an integrator, we would have had a lot of difficulty getting it set up ourselves. 

As this product matures, it will continue to get easier to set up.

Setting up Automation Anywhere was fairly straightforward. I personally did it. I had my team behind me. They set up the IIS side and the SQL side. But for installation of the product, I did it myself because I wanted to know. I'd still like to learn, even though I don't do the work.

To install here, on-prem, at the server level, only took two people a couple of hours; perhaps a total of eight man-hours.

Our implementation strategy was, "Let's try it." We had an objective to save FTEs as well as to introduce technology to get around our lack of a decent ERP. It was a matter of picking among the big three, and some third-world country type of RPA as well, and seeing which one hit the button. We figured out what the requirements were, and we have a pretty hefty on-prem hosting, so we spun up some servers and installed it.

After deploying, our developers then took control. We had a team of three developers. In terms of maintenance, we usually set up our environment where we install updates monthly. That should take a couple of hours per server. I don't recall Automation Anywhere standing out as a "problem child." So maintenance on the infrastructure side might be about two hours a month.

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.

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 initial setup was difficult but later, it gets easier in each progressive version released by Automation Anywhere.

The initial setup was straightforward.

The initial setup is of medium complexity.

The initial setup is not complicated.

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.

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."

It is very 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.

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.

I was not part of the setup process.

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.

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.

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.

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.

And we've been continuing to have issues along the way. They had actually settled down quite a bit until we hit this high-availability issue.

The setup has been okay. We haven't seen many challenges.

The initial setup was in-house.

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

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

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.

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.

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 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 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.

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.

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

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

The initial setup was complex. However, Automation Anywhere came onsite and helped us with our architecture, then it was fine.

The initial setup is complex.

The initial setup is pretty straightforward. I've actually done installations of Automation Anywhere and I have no IT background. I've been able to set it up on a server and some virtual machines and get everything working.

The deployment took some time for us, but that was due to a lack of a good environment on our side. To do a clean install would take some three or four hours to get everything up and running, depending on what kind of machines you have. If you have all the accesses you're supposed to have it can take a very short time. But, if you're installing it in an enterprise environment, it can take longer because you might not have all the accesses. At least for me, coming from the business side, I don't have all the administration accesses that I would need, but that's not Automation Anywhere. Overall, it's pretty straightforward and doesn't take a lot of time.

For our implementation strategy, we started out with a pilot, together with a consulting partner. We automated two processes and created a proposal for an operating model, governance, and a framework. After that, we just tried to pump out new automations as fast as possible to prove the value to upper management. After a while, we got some traction and we went from being just me in 2015 to between 12 and 15 people now. Some of them are not working full-time on it but we have at least 12 full-time employees working on RPA across our organization. We started out in Norway, but now we also have operations in Sweden, Denmark, and Finland, with people working full-time on automation in all of those countries.

All the developers are doing some maintenance. We don't have anyone who is assigned to doing only maintenance because we all find that a bit boring. We share the responsibility among all the developers so that everyone has the chance to do new processes and maintenance when needed.

We have a two-pronged approach there. The processes that are important for business continuity, the business-critical processes, are often maintained proactively. We are notified that a change is coming to the system, so we need to test it out and make a new version that will work when the upgrade of the system is live. So we're proactive in those kinds of processes. Non-business-critical processes are maintained reactively. We try to do it in the most sensible way possible, but there's always room for improvement, obviously.

We put a lot of responsibility on the process owners. They're responsible for notifying the RPA team in case of any changes in the graphic user interface or changes to the process, because of new rules and regulations or any other reason. The process owner or someone in his or her team will always know if there is a change in the user interface or the process.

If there is an error in the code, it is the RPA team's responsibility to fix it and we do most of that ad-hoc, when it happens. We always have some resources available to do those kinds of things and that's taken into account when estimating how long we will spend on creating a new process. We know that something might happen during that week or those weeks, so we add some padding.

In addition to the developers, we have a lot more people using the Control Room to schedule the processes.

So we tried to run fast and then we took a step back and re-evaluated. We built an even better framework, redid the infrastructure, put more thought into the security aspect, and we have industrialized our implementation. We still have some issues when it comes to our operating environment, but that's not Automation Anywhere's fault; that's more in our IT department's hands.

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 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 quite straightforward

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

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 was quite easy, and they will provide setup documents.

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.

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 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.

Version 10 that we had was a little complex to set up. However, version 11 is pretty 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.

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).

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. 

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

The initial setup was straightforward.

The initial setup was straightforward. However, integrating the application was not easy. The first setup was very easy, but building the infrastructure to support the application was complex. I am unsure if the problem was my company or the application, since my company has a lot of bureaucracy when raising new VMs and installing new applications. There are a lot of problems regarding security, which is stopping us to move forward and becoming agile.

The setup was straightforward. Understanding what we wanted to do the tool, that was more complex.

The setup is usually straightforward, not complex. If you're doing a basic installation, it takes around one hour. If you're installing MetaBots or any plugins, it will take some more time.

The team we work on develops on the weekend. We have Control Room access so we deploy from there. It doesn't require a team though, an individual person who is working on a given project can also install it.

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

The deployment took one week and required two people.

The initial setup was straightforward.

The initial setup is average in terms of difficulty.

Straightforward.

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 is a little complex when it comes to dealing with installing certificates and the bot agent.

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.

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 setup was straightforward.

In version 11.3, the setup changed. So far, it has been simpler. Also, in version 11, they have changed the design into a Java Jetty architecture, which is more stable. However, we were not familiar with it, so we had some issues with it. Thankfully, Automation Anywhere diligently answered our calls and helped us through the installation. It wasn't easy to install on our own using the guide. We needed support from a technical entity from the support site to be able to do it.

It needs a lot of coordination between the DBAs, which is a separate team within our organization, the infrastructure team, our team, and the Automation Anywhere teams to execute the deployment. Getting them all together was a good three hours exercise just to install.

Two people from my team worked on the deployment, one of them being a DBA.

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. 

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. 

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.

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. 

The initial setup is straightforward.

Straight Forward

The initial setup was straightforward.

The initial setup was easy.

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.

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. 

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.

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 is very simple. It's Windows-based and it's a straightforward installation. We used to say they need to come up with a silent installation option, with the previous version. But now, with version 11, they have introduced, even at the server level, a silent installation. That means we can make it automated instead of manually installing it.

The setup process is not easy compared to the competition, and this can be a barrier to entry.

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. 

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 setup is straightforward.

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

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.

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.

The initial setup is good.

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.

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.

I was involved in setting up our upgraded environment for the new version. The documentation that they provided us was very thorough. We chose to go back to our integrator (our consulting company) to help us build our new environment, just so we would have ready resources available if we ran into questions. However, in this situation, we were able, from start to finish, to build the new environment without many problems, by just following the documentation.

The setup was complex because we didn't want to just start making bots immediately. We needed to build the infrastructure around it so that, in the future, it would be a lot easier for us. Once we had a process for how to build bots, it was a lot easier for us, and we had proper standards.

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.

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.

A2019 has zero installation required.

Straightforward, installation with disaster recovery approaches. 

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 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.

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

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.

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

It is easy to set up.

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.

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

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

The initial setup was straightforward.

The initial setup was complex, only because of the process that was selected. That took us longer than usual, because it had a lot of cognitive decisions in it. Part of our new process is to evaluate if a process should be automated or not, and does it have more repetitive tasks than a lot of decision making. This has greatly increased how we are able to put a process into play for bot creation.

The initial setup was complex.

Certain aspects of the initial setup were complex, but that's a given when you're talking about technical architecture and getting the infrastructure you need in place for a successful rollout. Though, some aspects of the initial setup were simpler. 

The simpler aspects are designating roles for people based on what it is they want to provide to the center of excellence for RPA and how they see their fit in the organization. The more complex piece of it is working with all the stakeholders, internally and externally, to get all the infrastructure in place that you need in order to develop, deploy, test, and run bots in production. 

The initial setup is straightforward. They have a guidebook to help our IT infrastructure team to set it up. It was very easy. Anybody who does not come from a software background could read it and would be able to install the application and start using it. I have done it myself and I don't have a technical background. It's like downloading Microsoft Word and using it. It's very simple.

Our deployment took three months.

Our implementation strategy is PDCA: Plan, Do, Check, Act. We planned this implementation, and then did it. We then checked whatever was not done correctly in the first instance and acted on it to complete the implementation. We believe in having a very simple approach. We planned to do automation using Automation Anywhere and then we acted on it. Then we checked that out of, say, ten milestones, we were able to close seven of them. We acted on completing the other three milestones.

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. 

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 initial setup is straightforward, as this is a cloud-based deployment.

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

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

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

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

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.

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

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

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.

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.

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

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.

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

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 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.

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.

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.

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.

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 complex.

The initial setup is straightforward.

The initial setup was complex.

To scale from pilot to production takes a long time because the initial setup process is complex.

When we decided to implement an RPA solution, it was our goal to be able to set it up ourselves from the beginning. As we had no knowledge on this product, we asked Deloitte to help us create a manual which suited our needs. The systems being used are different from company to company, so we needed to make it so it work for our company. Generally, product manuals are written in a way that says this command does something. While ours does say this, e.g., to activate this system, use this command. We worked closely with Deloitte to standardize our manual. Deloitte also taught us how to build it as we attempted the skill transfer. 

We had some challenges in the beginning. However, if you have experience with Excel macros with End User Computing (EUC) or have used Access, it’s an easy transition. If you have not done any EUC, you will have to learn from scratch. So, it may take some time. In general, it is much easier than programming.

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

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. 

The initial setup is very simple and straight forward.

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

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

Setup is straightforward.

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 is easy but it is better to have AA support person during that activity.

The initial setup was straightforward.

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.

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.

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

The initial setup is straightforward with no hassles. 

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

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

The setup is mostly straightforward.

It does take a lot of space to install. However, you are installing a very powerful application which has very powerful components in it.

It took us two years to scale it from the pilot it to our current number of bots. The process was too much work.

We were not involved, so I’m not sure. I heard that it was fairly easy. 

We are right in the process of it. We are leaving it to the external IT partner who we used because they are the ones who programmed the previous bots. They would do the best job for migration.  

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 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.

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... 

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 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

Straight forward

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.

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 was a simple process. 

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

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

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 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.

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.

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

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 straightforward.

The initial setup is more straightforward compared to other solutions like UiPath. Initially, it is relatively difficult. If you have a very simple straight linear process then Automation Anywhere is easy to implement and to deploy but as soon as you get into complexities or where you have more rules like finance or accounting where I deployed specifically at times, there are a lot of variances in the process. That's where Automation Anywhere actually becomes a headache to manage.

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.  

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

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

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 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.

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.

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.

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 initial setup of this solution is very easy.

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.

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

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

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

It was very easy and simple.

I found the initial setup rather easy and straight forward. I think coming from a programming background made it that much easier but others that I have worked with that did not have a programming background have not had much difficulty either.

The initial setup is 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 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.

It's easy to set up.

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.

It was a bit complex. You can contact support, and they will help you through it.

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 was straightforward and the instructions were easy to follow.

The initial setup is straightforward.

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. 

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 good.

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

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.

The initial setup was pretty simple. We got the minimum requirements for all of our environments, and we had a technician, a technical expert from Automation Anywhere, who walked us through the setup. That was actually the easiest part.

From a software installation standpoint, it was roughly a couple of hours. But from the infrastructure side, there were some setups on our end that we needed to carry out. That took a little while longer.

Three people were required for the deployment. One to coordinate resources, another from our side, and one technical expert from the Automation Anywhere side. In terms of people involved in managing the solution, for the entire software, we have roughly one stakeholder for each department that we have automations in. The solution affects many people, but the number of people who are actually involved in designing and maintaining it, is between five and ten.

The initial setup was straightforward. There was no need for a reseller or partner to do anything, if they were just going to click the "Next" button.

From pilot to production, we did a three bot pilot, but we did not put those bots into production. We pretty much cut down that environment and started everything back up from scratch. 

Now, we have those three bots out in production. They are programmed to be easier and more affordable. Then, we have the rest of our processes that we have identified to take to production for automation that seem pretty easy for the next stage.

The initial setup was very complex. We had several issues when trying to connect the different components, due to our firewalls. They were eventually solved by our internal IT and the AA technical team.

Deployment took three months.

Our implementation strategy was teamwork among our IT, the end users, and the software provider's technical team.

We received the manual, so our IT department set it up. I believe it was relatively easy.

We were given the manuals, so we did it ourselves. It was not hard or challenging. We
did receive support, but there were no issues. 

It was straightforward.

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

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

The initial setup was straightforward.

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

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

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

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.

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.

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 initial setup of the software takes time.

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

The initial setup was straightforward.

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

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 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.

The setup itself did not take that much time and effort. In general, members of our IT staff do the actual setup, so we had no issues with it.

The initial setup of this solution was straightforward.

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.

Initially, the setup is not complex; it is straightforward.

The initial setup was straightforward.

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.

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

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.

I wasn't part of the original PoC team who completed the initial setup. 

After joining the team, we engaged in two upgrades to deal with stability issues. We found this a painful process as we were early adopters. This meant that the install wasn't stable. To resolve this, we decided on an approach where we would only upgrade to a major release six months after its release.

The deployment is quick. You could complete this in a weekend. Realistically, you need a week to prep and another week to triage unexpected issues.

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

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 straightforward.

The initial setup was straightforward.

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 setup was very difficult. It recognizes the correct fields that you put into it, but it resulted in complex scripts.

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