AutoSys Workload Automation Reviews

The core purpose is for enterprise batch scheduling. For example, it involves the scheduling process and automation between multiple business units.

Autosys is one of the oldest products in the market, and it has been around for quite a long time, close to 20 to 25 years. It is quite well-designed from a very initial level. Although it is a basic application, it can support achieving the functionality of Enterprise Batch at a fundamental level. 

The product is very robust and offers multiple conditions and parameters for configuration based on my requirements. It integrates dependent applications or modules of a particular business unit, handling process sequences with Autosys. For instance, end-of-day operations require a sequence of steps that Autosys manages.

AutoSys is the default non-mainframe scheduling tool used across the bank.

AutoSys Workload Automation was implemented to centralize the control of all our diverse business and infrastructure processes at the bank.

We rely on AutoSys Workload Automation to manage hundreds of diverse processes, ranging from IT-based backups and maintenance tasks to a wide variety of customer service applications used by the bank. Most of the processes we automate using AutoSys are complex.

It is easy to manage complex workloads using AutoSys Workload Automation.

AutoSys Workload Automation has helped reduce our workload failure rates across multiple cloud environments. While it's difficult to quantify the exact percentage reduction, a system outage would cause significant issues for hundreds of application teams and incur billions in costs. Automation levels vary by area, ranging from 100 percent to 50 or 20 percent. Overall, we've achieved a significant improvement in workload reliability.

It enables our staff to save time to focus on other tasks. It's running on tens of thousands of servers. So the hours we save are in the thousands.

It helps us improve our compliance processes. For example, it ensures the bank meets its obligations for tasks like backups and timely processing of market-critical activities.

The tasks we have automated would require hundreds of people to complete manually, resulting in significant operational cost savings.

We use AutoSys Workload Automation for automating and orchestration processes across legacy and modern systems. Our ability to observe the automation across multiple cloud environments using AutoSys is adequate and continually improving.

Over time we have found that if there are any issues with communication between the various components [ scheduler (eventor) ,app server (as_server) , database (event server), the agents, etc ] that when connectivity is restored, jobs start executing as desired and anything that is stuck or is in an ‘strange state’ is easily found and rectified using the tools provided by autosys.

We have found that most of the time the WorkLoadAutomationAE software requires very little maintenance and has achieved an almost 100% uptime in all the instances we have running in our DEV/TEST/and PROD environments.

IOW – Although there are many components involved, once things are setup correctly, the application performs solidly, is extremely redundant (again, if setup correctly) and has very little maintenance overhead.

We've just recently upgraded to the 11.3.6 Workload Automation platform. We're still implementing the pieces, but what we found is, there's a lot more reporting with it. It's a lot more stable. There are a lot more features available, that we've yet to even take advantage of.

I use AutoSys to manage thousands of interfaces, which are essentially scheduled jobs, across different regions like Europe, Asia Pacific, and Latin America. These interfaces fetch data from source systems and load it into target databases. I also use AutoSys to configure jobs as interfaces to automate these processes.

AutoSys significantly reduces manual effort. If I have ten or fifteen jobs, a manual process is feasible. However, with thousands of jobs, AutoSys offers immense value by allowing reusable configurations until modifications are needed. The user-friendly UI facilitates ease of use even for new users, permitting them to understand and modify configurations with ease. Moreover, AutoSys provides excellent security features to define user roles for reading, writing, and administration.

Currently, we're just giving support to the client environment. They already have the AutoSys setup there.

Our client uses the solution for insurance purposes. Most of the jobs are command jobs, FTP jobs. This is the current use case. In the systems, they use some of the task applications, so in some of the SAP applications, for example, they use AutoSys.

The solution has been stable. 

There are no issues with scaling. 

Most of all it automates the processes we need to get done at night. We've grown into it. We have several thousand jobs in our production environment right now, about 40,000 altogether, and that number's going to be growing because with the success that we're seeing with certain applications that have submitted jobs to the workload automation, other groups in our company are saying "Hey, we want to get onboard too and automated our processes, too."

The benefits are that it's automated, reporting facilities are terrific, also when there is, let's say, a failure of a job, it's very, very easy to report that incident, that event, and we can certainly notify the appropriate personnel who need to be notified of that, very, very quickly.

In our organization we have more than 30,000 automations we are running in this product. From an admin perspective, we have around seven to eight people working with the solution, managing it and dealing with the volume. We are a customer of AutoSys and I'm a company manager. 

I think one of the valuable features of AutoSys is the easy configuration and integration of this tool with SAP. It's a critical part of managing the solution. In terms of the basic functionality, I found this to be a really excellent tool to work with. There are minimal issues and minimal maintenance.

I use AutoSys Workload Automation for enterprise batch scheduling, so for banking and retail values, I have multiple modules of applications. AutoSys Workload Automation is used to schedule and process jobs or automated triggers 24/7. The tool is for cross-functional and cross-application dependency management purposes.

To me, what's most valuable in AutoSys Workload Automation is its robustness and quickness. The tool can trigger jobs within a few milliseconds, and it can handle large volumes of jobs.