What is your primary use case for Automic Workload Automation?

We have many different use cases. One use case is to back up all our servers. This is a big usage. The next one is to schedule things on SAP systems. We have SAP reports. We have processes where different SAP systems are involved and we can build up dependencies. We create business process flows. This is a big use case. We use Automic Automation for managing databases, such as SQL databases, Oracle databases, and SAP databases. We have customers who use UC4 for general monitoring, system jobs, and other things. These are the main use cases. We have some business-critical processes. For example, if a file is there, then the file has to be loaded to SAP. The customers can then, for example, print the papers to transport the goods. If our UC4 process does not happen, the papers cannot be printed and the goods cannot be shipped to a customer. Some departments use it to handle the databases. If the process is stuck, then perhaps for Oracle databases, the archive files will not be moved to another folder, and the folder will grow and grow. There would be no space on the file system, and the application that is using the database cannot work anymore. We have some very critical processes and also many processes that are not so critical.

We use the solution across every business area for site switches, backups, batch scheduling, and other tasks.

It is an automation tool. We build the workflows and Linux and Windows servers with it, particularly for running client jobs and databases. We use it with a lot of big data ecosystem tools, such as Hadoop or HDFS. We have automated regular ETL processes such as data transformation. They are loading data into databases and the HDFS file system. We use it for data transfer jobs between servers. It is being used for SFTP-type jobs, and we run a lot of Python-based things with Automic. It deals with business-critical processes. It is an important tool for us. For a lot of backend work, we use Automic Automation to run all kinds of jobs. We have some very complex jobs, but we also use it for some basic jobs. It is being used for very critical or high-priority jobs and complicated workflows with hundreds of jobs.

We primarily use the solution for automation. It's used mostly to automate plant activity and billing and finance tasks. It's also used for job applications.

We use the solution for our finance and service desk teams. We're a retail company.

In the past, I had used Automic Workload Automation during the time when it was called UC4 for month-end close automation since we were running a shared business service involving an institution related to national healthcare. Our company used to support around 130 to 140 odd hospitals, causing a peak demand for the tool Oracle E-Business Suite, which became tedious for us. Later on, we introduced Automic Workload Automation and automated the organization's entire processes, after which there were only two people required to monitor the month-end close automation since everything else had been automated. In the beginning, it was called Appworx, and then UC4. The areas of automation I had worked on in the past were successful. At present, I might have an opportunity to again work with Automic Workload Automation.

Automic Workload Automation is a workload automation tool. Automic Workload Automation's use cases are primarily focused on large enterprise users. With over 3,500 customers, the tool is well-suited for core automation tasks in various sectors, especially in the banking industry where Automic has a strong presence. The platform offers largest number of out-of-the-box integrations which sets it apart from other workload automation solutions. This integration capability is a key area where Automic Workload Automation excels.

I primarily use Workload Automation for financial technology feedback.

We don't use it in my company. We implement for our customers. They primarily use the solution for workflow automation and work close with oracle.

Our company uses the solution to run scripts for customers. For each use case, we create a description and use it with the agent to schedule run times. Our team size ranges from 40 to 50 people and varies across clients or use cases.

I use Automic Workload Automation for SAP-related use cases. They are primarily functional and nonfunctional job executions for SAP Windows Unique. So, mainly for a business process or business functions, job execution, and creating dependencies related to retail like Oracle and SAP jobs execution.

We used Automic for a multinational pharmaceutical client.

I mainly use this solution for batch job processing.

It is basically for workload automation. Automic has also got other features, but we are not using them. We are just sticking to workload automation. We basically do batch processing through automation. We mostly have nightly batches and cyclical batches during the daytime.

We are an insurance company, so we are using Automic Workload Automation to control all of the night processes, the batch processes, and also the EDW. It is for controlling the other databases that we are using. We take all the data from the S400 and move it to other databases in order to do queries and gather other information. We also use it to control between a lot of other systems because we do a lot of workflow between other computers, so we can control the time and flow and other things.

This solution has many use cases because it's automation, so the sky is the limit. It can be useful for any workloads—DD operation, disaster recovery, data center automation—required by the customer. This solution is deployed on-prem.

We have several corporate solutions that need to be integrated with our ITSM products. Automic facilitates integration to ensure the correct execution of ITIL process workflows. The first was to create service offerings for provisioning virtual machines in both private and public cloud environments. The creation of virtual machines would have to contemplate the current process of changes, releases, and configurations. Our service catalog should make service offerings available; these involved diverse operating systems, different hardware configurations, and some functioning web services. An approval process would also be contemplated, where the main steps would be the registration and closing of the change tickets, as well as the registration and deactivation of the generated configuration items.

We have many clients in financial services. We install, implement, and configure this solution for them. They use this solution to automate financial processes. We have roughly 100 users, using this solution. We expect to increase the number of users of this solution.

We are working with telecoms to automate workloads. The use cases include automation from inception to activation. Some use cases also deal with professional services. Our use cases are reflected in the cloud-based Workload Automation.

We are a system integrator and Automic is one of the workload automation products that we implement for our clients. This tool provides a great versatility of options for effective digital business automation. Integration with different platforms, ERP systems, business application, microservices, big data. We are supporting multiple customers and their environments. Some of the most common uses are : SAP, SAP BW, Avaloq, FileTransfers, FTP/SFTP, Datastage, Informatica

We are a reseller and solution provider, and this is one of the products that we provide for our customers. This is a conversion product, and we use this solution to assist customers who are converting from another product. Our primary focus is one-for-one migration, bringing it up to the next level and getting it ready for the next phase.

We use it for assisted process change, and we are using it for basic operating system-level UPROCs or jobs, and there are certain jobs that it runs for the net backup.

We are currently doing a migration from Dollar U to ONE Automation for 815 applications for one of our clients.

* Workload and system automation * We run our batch schedules through the system and have also automated very complex processes to allow Operations perform tasks that were previously done by Sys Admins.

We want to automate our processes. Before, we used to execute more than more than 250 jobs manually, along with a number of things related to backups, and putting files on FTP.

We use it for multiple system automation and file transfers to secure POS networks.

The primary use case is workload automation in our SAP area. The performance is fine.

Right now, we are working with version 10 of the product, it is very good. We are very happy with it. However, we have to upgrade to a different version and there are a lot of things that are different, and we are not completely convinced how it will work. Our normal functions, what we had in version 10, are lost or not there. So, we will have to see how it will work in the future. As a company and as a product, though, we are ready to upgrade.

We use Workload Automation to control all our processes and the batch control. We are working with version 10, and need to upgrade to version 12.2.

Our customers use it for scheduling. It performs quite well. It depends on the customer. Some customers do not use it with all the features that the product offers. They only use a small set of what the product can do.

Primary use case is to automate our SAP job workflows and all the job workflows that we work with. Thus, to get better performance in our company by automating everything that we are working on. So far, it has been working well.

We use Automic Workload Automation (AWA) for different things in the company, e.g., batch-bookings, archiving, virus scans, flight plans, etc. It is used for everything in the travel business which has IT. We do a lot of batch things within the industry, as it is a wide field.

We use it for the following: * Automation * Server positioning * File transfer solutions * Daily business processes * Different processes.

We use it for batch processing. It is performing well.

The primary use case for using Workload Automation is the automation of applications in different cases for business or data warehouses, controlling programs, and ERP systems (like SAP). We have also began to use it for data center automation for provisioning of virtual infrastructure.

The production controls the test environment and test batches. The performance is very good.

The primary use case is scheduling business automation. Its performance is good.

We use it to automate our business. While we have had some issues, it is mostly perfect. If it is set up, it is running.

Work Automation is a worldwide product which has a lot of utilities. It can be very helpful for use with customers' data, and it is very quick with utilizations, customizations, etc, so we can meet the customers' needs.

We have different applications. We can schedule our pickup or applications (mainly MFT for financial services) and provide file transfers only to customers.

We use it for simple job scheduling, mainly for SAP. Two to three parts are for SAP, job scheduling, and smaller and larger workflows. It performs well.

Our objective is to sell this product in the name of CA, as we are a CA partner. We are trying to develop this new solution and provide it to our customers.

Currently, we build self-service for our customers. This means they come to us and ask for special solutions, then we build a generic self-service which can be used for this customer. This solution is like the action pack from the Atomic marketplace.

We use it to automate infrastructure and business. We do quite a lot of different stuff: sometimes orchestration, sometimes more automation.

We use it to automate our business processes. It is just for automation and scheduling.

We are using mainly Workload Automation for all types of jobs over different servers and operating systems.

The main use case at the moment is to automate workloads. We have more than one automation tool, but the workload automation tool was chosen to do automatic manual workloads. That is why it is called workload automation. We are automating very manual, robust tasks, which are very time consuming and not error-free. This is our first main use case, and we do this also to glue some holes. For example, we orchestrate backups, where we take one system down to start a backup, etc. In addition, we are processing big data from the Hadoop platform and Informatica systems, and we orchestrate using scripts. We call it simple scheduling services, where we simply schedule batch jobs from scripts.

We do many basic things with it for the SAP system on Windows. We also use it with many with other communication systems. For example, we sell it as an iPhone 5. As a system, you can examine many pictures from the company. I must catalog these pictures with the names and architects, therefore we have many file transfers. For example, we take information from the SAP system and send it to Azure from the automation engine.

We use the CA Automic solution for our complete business batch. We have several use cases, depending on the subcompany. We have an ABS system with a great batch and the lean system, therefore we have three different main batches with approximately 900,000 objects in the CA system. We have mostly connected our complete systems on the web front-end for the customer, so they can choose their products, manage their contracts, and get a new contract. This is all put into the automation system and handled there until, at the end, we have the output for printing, then we send it back to the customer.

We are using it for batch automation and protection. We can control and check it, which is the main thing. When the batches must be run, we need a perfect system for it to run. It must run 24 hours, seven days a week, with no interruptions.

We build jobs and transfer data from A to B, then start SQL jobs and customize them for our customers, etc. We automate the system for our business.

Our primary use case is the SAP area, but we do provide Workload Automation services for other applications as well.

The primary use case is automation of our business processes within the bank along with several areas of process automation. We have been using the product for 10 years now and have built it up from scratch. We do a lot of stuff with it, of which, we are mostly satisfied, though there will always be problems with it.

In our company, we use it for the following: * Scheduling of SAP and ERP jobs. * Backing up most of our servers. * ITSM and scheduling using the automation agent. * Running our non-ERP jobs, or for some other applications. * File transfer and automation services.

Our customers use it to control executions of jobs on different platforms, systems, applications, and technologies. There is a huge variety.

We have many systems, like SAP, Linux, and Windows systems. We use it for crossover and production, beginning from Host to SAP to Windows, to make a print page for all our users and customers. It is not possible do our jobs without automation software. Automic is a great help to us. We have been using automation since 2003 (version 263.G). Today, we are at version 10 and looking to upgrade. However, we do not what version will to upgrade to due to our hardware requirements. We must check if what we have is okay, or if we must buy some more servers, laptops, and screens. Therefore, we are checking out versions 11 and 12, or we deciding if we should wait for 12.2. We are seeing what other are doing and determining what the problems for a migration might be.

The primary use case is for automation in the area of SAP, as a specific solution in time management and access control systems. We are providing for this for any of our customers who use the automation engine. It is performing well.

Our primary use case is release automation. We did a PoC last month, and are planning on probably implementing the product.

We primarily use it for job scheduling and business automation.

We use Automic Workload Automation to schedule the batch processes for all systems within the University of Colorado. We use file transfer jobs to send or receive files with each incoming file authenticated through Automic. We code Automic jobs to update PeopleSoft run controls automatically, continuously run processes for real-time results, bounce application servers, and we notify all process failures through text and email.

We have many use cases for automating different systems. In most cases, we use it to automate database application servers. We have over 2000 servers, so we need to synchronize jobs on various platforms, which is our most common use case. So far, the performance has been okay.

The primary use case is to automate jobs which run at night on SAP, Unix jobs, and Windows. It has performed well.

We use it for scheduling of our production and development.

We use it for batch automation and site switching. It has performed great for us, and we have had very few problems. We have done a full upgrade in the last 12 months where we went from an AIX to a Linux platform, and this was a massive change for us. We are a big organization. We have 7000 employees. We are spread across Ireland and the UK, with operations elsewhere. Therefore, it is about where can we use Automic to create efficiencies. We know there are a lot of things that we are doing which are time and resource intensive. We would like to leverage Automic for these tasks. We have been using Automic for more than 10 years.

Our primary use case would just be our production batch processing. It's been great. We've had a few bumps in years past but it's been rock solid since the last couple versions. We also perform all internal file transfers and many of our company's external file transfers.