The initial setup was very easy. For setup, out-of-the-box APIs were there for our leverage which automatically had all your concurrent jobs, and everything was available by default in the tool because of which putting it into a chain, thread, or flowchart was very easy.

The solution was deployed on-premises.

The ease of setup depends on the person who handles it. The setup is a bit different because it includes four or five components that require separate installations. There are various steps and processes to follow. If you have knowledge of the solution, then setup is easy. 

Typical setups take 14 to 16 hours for server and data installations. 

Initially, deploying Automic Workload Automation was challenging, but it has become much simpler. However, if you want to set it up in a distributed environment, it may take a day or two due to critical sites and firewall requirements. For a single box installation, it hardly takes thirty minutes to set up.

The initial setup was straightforward, but it gets complex when you start using it. It will only be complex if you're a new user. The total deployment time for the original and web version was about three months. That includes installation and testing. During the testing, we found missing features, so it took three months to set the solution up, configure it correctly, and test it. 

The personnel needed to manage and maintain the solution depends on staffing and scheduling. For example, If you are providing 24-hour support 365 days a year, you need six at the most. We need one person per shift, and we have three eight-hour shifts. Including backups, that's three to six people. 

The installation of Automic Workload Automation is complex due to the lack of full automation in both the installation and distribution processes.

We do help our customers implement the product. The implementation's level of difficulty depends on what has to be automated. The tool itself isn't rocket science; however, complex automation may exist. If there's a big ETL or data warehouse with thousands of jobs, it can get complex. 

There is a bit of maintenance needed, for example, around security updates. 

I handled the initial setup, including handling the requirements and infrastructure.

When we installed the solution two years ago, we installed the latest versions - whatever was available at that time. 

The implementation wasn't easy. However, I had local partners from a local company to assist with the setup. It would be difficult for inexperienced people to install it alone. They have to understand the concept. They have to understand the architecture and be able to manage the credentials required to authenticate. I had these problems, for example, when I set up the UC port.

I handled the implementation by myself.

The initial setup was complex because we have multiple endings running in every country that we manage. We also have an active-active setup and two instances running on one machine. We use it to widen our range so that we can have two engines running on the same machine. 

It is currently deployed on a private cloud and on-premises. We have around ten people to maintain this solution.

I was not involved in the initial setup.

They work with a partner to help you with implementation and migration. The partner had tools for migration from ESP to Automic, which was helpful.

The initial setup is straightforward. It hardly takes half an hour or one hour, but small components like agents must be installed later. The initial fresh installation will take about one hour.

The people involved in the initial setup were convinced that they had the right product and absolutely satisfied with the setup in 2001.

The initial setup of Automic is simple and easy. As long as it can talk to what it needs to talk to, there are no issues with the installation.

The setup is pretty straightforward. I'd rate it eight out of ten in terms of ease of implementation. 

Deploying the solution only takes about one day. You simply have to install and configure, and you are ready to go. The process is fast. 

We have a team of five that can handle deployment and maintenance tasks. 

I believe it's pretty straightforward. It's a complex thing by nature so it's not going to be super simple, but it's not like you can't do it either.

I believe experience helps. And in our case, we had a lot of help from the vendor, so while we, per se, didn't have the experience, there were people helping to get us going that did have the experience. So maybe I'm underestimating how much that was important, because it was available, even though it wasn't coming from me or one of my team members, but somebody else was providing it.

During our PoC, I was the guy who was implementing and installing the product. I thought with the help of a consultant that it was an easy installation. 

I wasn't involved in the initial setup. I actually used it from an operator's standpoint. I did not start maintaining the system until about a year and a half after we brought this system in.

The initial setup was very straightforward. The consulting team for implementation was great to work with and taught us the system very well.

We have using Automic for long time. From the first step, you need to have time to install it. When you want to use the entirety of Automic, it is heavy. In the beginning, our administration chief told us to use 10 percent of your time for Automic administration. Now, we are using 100 percent (our entire job); it is a full-time job.

Our systems are not that big. When we have trouble or have updates, it is a full-time job. We must talk with other teams. We must see that the hotfixes are updated. This cannot be done in ten minutes as some modules and add-ons come together, and we must see how to orchestrate it within our company. We must look at these things, which are part of the company, see how they can be used. We spend a lot of time of this.

I was told that it took over six months and was difficult.

The initial setup was complex.

The implementation was not straightforward, though it is not that complex. During installation, some database elective issues popped up. These took some time to fix, but after some back and forth communication, these issues were resolved.

In the beginning, it is hard. We did not know how to deal with things. However, when the process is ongoing, it is very easy to set up and build infrastructure on Automic.

The complexity of the initial setup depends on the person who is performing it. It was okay for me, but I have some colleagues who have had some problems with it.

I was heavily involved in the initial setup. It was December 2015 that we had to migrate our entire workload automation suite of 1000s of jobs. We are publishing petabytes worth of data into this big relational data warehouse, publishings, all these different applications. We probably received 2000 files per week, and probably had 5000 jobs per week. Therefore, we had to migrate all that from one solution to another solution in 60 days. It was a contract thing that was going on, so we had to do it and I was heavily involved. We had some professional services people come down and we found out about it in mid-December and we were done by the first week of February. So, it was a heroic effort, but we did it.

Initial setup is quite simple. Also all required documentation is available as well as support is available from vendor.

Complexity only exists when installing high availability. Support from the manufacturer was required.

We spun it up during a weekend.

The installation is very straightforward. The time it will take depends on the implementation and the size of the project—it can range from one day to five days. A team of one to three people could be enough for deployment. 

The initial setup is relatively straightforward. There is an awful lot of planning because it is such a critical application for us. We have to test everything before we go ahead. It could take us up to three months doing all of the testing, maybe putting the infrastructure in place for an upgrade. The actual day when we upgrade only takes about an hour or so. It is very fast, and we have never had an issues.

The initial setup was straightforward. The installation took two days. We did not have any difficulties. You just click, click, and click.

The initial setup, installation, and configuration are very straightforward.

The initial setup required us to do an analysis of the Dollar U environment for conversion to ONE Automation. We have special tools for converting the session and the UPROCs from Dollar U to jobs and workflow in ONE Automation. We have developed macros with VBA to convert all the information in Dollar U to ONE Automation.

When we start an integration for the first time, we create the client and we attach the agent for the application, because every application is a "client" for us. We use Red Hat Servers for this. Of course, we use Windows servers, but 80 percent are Red Hat as well as iX and HPE servers.

Each application takes a different amount of time. For example, there are applications for factoring or financial applications. We need one year for their implementation. Smaller applications take a few months. We start with the small applications and then move to the more difficult applications. We have a team working on this and every person has ten or 15 applications to do.

The initial setup was 10 years ago, so it was easy at the time. With each upgrade, it will probably have more complexity, but it has been a little hidden because it is a step-by-step process. Though, the complexity is okay with the setup.

I'd say complex from the side that I don't know, where they have to set up, from our operations group, the servers and all that. That's beyond me.

When I'm saying they care and were very focused on the issues, in three months, the implementation of the system was running right. Instead of going through all the processes and trying to upgrade all of them, or change the way we work in a rapid movement of things during the implementation, once the system and the change model was up and running, we did two things:

• Good mapping process of the pain points
• Good mapping process on new projects.

Then we stared to just transfer new projects to this platform. Then, in parallel, we took all staff for the scheduling, which is the simplest way, and in two to three months, we upgraded most of the scheduling items that we needed to handle. Then, the organization saw that we rapidly changed the way we were experiencing a problem, integration, etc.

From the implementation point of view, it was straightforward, very simple, and not complicated. Of course, you always have issues with creating various servers and SQL licenses. You must handle the server optimization because you have a lot of traffic, so you need to do an optimization of the right resources. We have a private cloud on our site, so it's easier for us to do the optimization of resources in the process, which is great. Then, you eliminate more issues when you're implementing a new platform. It's tricky and complicated, but we are an organization that works with a lot of legacy systems, which has very big systems, which usually has a lot of troubles and issues in transforming between platforms, between different applications with a legacy code. So, when you have the opportunity to work on a shelf platform, on an advanced platform, then it's very easy.

It's very important to see who does the delivery for you, and what's their approach. If the approach is simple and easy, not too rushed, then you can manage the process to receive the best results. It's important because this is what made the implementation very easy at the end of the day for us.

Once again, from a technical point of view, there were no issues.

I was not involved in the initial setup, but I have been involved in the current upgrade process.

The current upgrade process is straightforward. They have made the process much simpler. After we get to version 12 and any subsequent versions going forward, it should not require any downtime at all. It should not require any system reboots for the upgrade of other components outside of the engine itself, such as the agents.

The initial setup was very straightforward and quick.

Initially, is it hard to set up? I don't really think so. I've been working with it for a while now. Once you understand how something works, it becomes pretty easy. 

I'll say this, support team there have been really great, very enthusiastic. Will answer your questions, and that helps a lot. A lot of it is, you don't know what you don't know. Once you do, you've got it figured out.

In terms of upgrading, it's very database-driven. You have to upgrade the database, and then just replace binaries, new software.

I was involved in the initial setup. The software itself was pretty straightforward. We converted from the Application Manager Platform to the One Automation Platform, and it was a little complex to get our jobs migrated over. Once they were migrated over, it was pretty straightforward. The software itself was pretty straightforward to install and get going.

I did it 13 years ago at different companies. In the past, we did not use the wizard. We set up the components standalone, then combined them in configuration. It was easy and well documented. 

Presently, there is a problem with the translation. It is some type of hybrid. We have some parts in German and some in English. It should be completely in German and completely in English. It should be better in the future.

It was straightforward. We made it difficult on ourselves at the time. We have recently changed and made it simpler. As regards to a mixed environment, it was fine.

Straightforward.

If the environment is straightforward, then the initial setup will be straightforward.

The initial setup was quite simple because they have a manual which tells you in a simple way of how to install it step-by-step. Therefore, I didn't have any problems. You do need to have a background in operating systems, then it is not so difficult to install.

We changed out from Chronicle to Automic in 90 days, without a single outage to our business. That has never been done with Automic. The Automic people were even saying, "How the heck did y'all do that?"

But we had some people from Automic, this was before CA bought them out. Some guys from Automic came over to our site, stayed in Cincinnati for a couple weeks, to help us with this initial setup, because it was such a time crunch. We had 90 days to get it in, and we had to pull the switch on Chronicle, or else it was going to cost us $1.5 million. It was a big time crunch, and they helped us get it in, get it working. We did not have any outage, we did not miss any Loyal Customer campaigns. Nobody missed the coupons because of our switch to Automic.

It was good. We had customer support who came onsite to install it and to train everybody and I was right there. It's mainly a product for our department, and then, as an administrator, we assign everybody, all the users and train them.

I was responsible to design and build the system. The project was an agile project, which was a pilot, because our company was not very agile. 

While we are a public institution, we are very old school. This was a first attempt at doing new things. I was the only technical resource that had the proper knowledge and skills. Therefore, I was the one who designed the system and build it.

The initial setup was complex, because of our specific requirements.

Implementing the solution in 2009, the setup was easy (straightforward).

Other parts, meaning implementation of all the processes, this was very complex. We had to think about steps, like name conventions, standards to introduce, common objects the users should use, and the training that users should receive about how to use the product.

The initial setup was straightforward. With outsourcing, it made it simple.

The application is straightforward to setup. What is sometimes challenging is making the application fit into the customers' environment. They may have some restrictions and restraints that we need to consider and also need to understand how to prepare. Therefore, it is rather an organizational challenge rather than a technical one.

Sometimes it was simple, and other times, it was very difficult. However, we had good technical support from Automic designing our system.

If I work with a customer (as a consultant), they do not want a straightforward setup. Therefore, I have not seen an out-of-the-box setup, because I have not seen a normal implementation.

I haven't done the initial setup, but I think it's pretty straightforward from what I have seen in the documents. My feeling is it should not take more than an hour or two to get it up and running. If everything is ready, your database is there, and you have the right amount of resources on the server, it shouldn't take more than an hour or two hours.

In terms of an implementation strategy: 

1. You should have a database. 
2. You need to figure out what components you're going to go for.
3. You need an estimation of the number of jobs you are looking for to plan out the resources on the server. 
4. Finally, you need to think about how you will roll out access to the users: a thick client or a web console. 

Those are the things that need to be factored in before beginning the installation. The accessibility part can be dealt with later, but the resourcing of the database on the server and the management server have to be spec'd out before.

The initial setup is easy and straightforward. I did it over 20 years ago.

The initial setup was complicated and difficult.

I was not involved with the initial setup.

Setup was complex due to the complexity of the tool.

The initial setup is straightforward. It is pretty easy to install this product anywhere, regardless of whether it is an on-premises or cloud-based deployment. Usually, deployment takes four hours at the most.

The initial setup was very complex. This company and the one that I worked at before found the very first migration from whole systems, like TWS, to the Automic product challenging. They were not used to all the features that it had. Though, I did not hear a lot of complaints about it.

I was initial in the initial setup. It was complex. We had a person come in from CA and assist us with the setup. It went smoothly. It took us about a week to get it up and running. However, it has been up and running, and we have not had any real issues with it since. 

We still actually have not implemented this version as it is in its test phase.

The initial setup is easy.

The first time we installed it, the process took between 30 and 45 minutes. After that, we replicated the installation and to deploy it takes no more than 10 minutes.

The initial setup was easy. We have used it for 20 years, so we set it up in a special way. We were installation number 30 for this product. We have been working with it for a long time.

With respect to migration or conversion projects, the compilation is done with a conversion factory. This is done on-site, and after that, there is testing and production. The deployment time for a project is between three and six months.

The initial setup was straightforward.

It is straightforward for me. Those new to this business find the initial setup complex. 

It is a complex product, so you can't do the setup with a click.

Our migration from a previous system was not easy. However, when we did a new implementation that was easy.

I was not involved in the initial setup.