AutoSys Workload Automation Reviews

I do not have experience with Rocket Zeke, but I know that Rocket Zeke is basically a CA7 scheduler used for mainframe. I have colleagues and friends who used to work on Zeke. It is mostly for the mainframe solutions that we use. I have seen it within IT batch solutions, supporting the IT infrastructure services.

I have worked for several solutions including Broadcom AutoSys Workload Automation, ESP, D series, and I also worked for Atomics, Atomic Workload Automation. I know a little about Appworx Workload Automation and OzRaf Dollar Universe.

We are trusted partners. I was a trusted partner. Cognizant was a trusted partner, retailer partner, and technology partner while we were working as a workload automation center of excellence. We used to work with system integrators from Broadcom and ensured that we managed customer licenses and optimized and transformed the workload solutions from 2015 to 2019. Currently, I have moved back to workload automation solutions and I am working forward with AI-based workloads and data pipelines.

AutoSys Workload Automation is a very scalable system where you can run even a million jobs in a second; it can scale.

AutoSys Workload Automation is very much scalable compared to any other tools with the solution that they have created. AutoSys Workload Automation is using version 20.4. I still need to look into the capabilities of it so that I can make best use of the tools and the capabilities.

From a CA or Broadcom product perspective, if we look at integration capabilities with systems such as ERP and CRMs, AutoSys Workload Automation is not as integrated as Control-M. Control-M is more integration-focused and it takes customer value from small to large customers. CA does not approach the market in this way; it goes in a different model. CA typically has captive clients who need a specific solution and will create that solution only if there is a budget. For example, while Apache Spark was on the market, Control-M was quick to create the integration. AutoSys Workload Automation is not as quick; it only develops based on customer requests and is said to be working on it, but it integrates closely with ERPs. It is not integrated with the full stack and falls behind current trends. The product life cycle, the integration life cycle with market advancements, is a little slow compared to some other tools. However, scalability, durability, and reliability of the tool are very high which is why most banks and Fortune companies use it, but cost is the intrusive factor.

The benefits I have seen from AutoSys Workload Automation are significant; I would say it is about ease of administration. The advantages I would mention are that AutoSys Workload Automation is a very simple tool. Ease of administration is easy; it is simple to manage, scalable, reliable, and robust. It is great for simple batch solutioning and also for service-oriented architecture frameworks. It is also very effective for new-age workloads.

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.

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.

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.

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. 

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.

AutoSys Workload Automation can be deployed on the cloud and on-premise. We have some file storage in the cloud.

AutoSys Workload Automation could improve the integration.

It is being used for all the ETL processing and batch processing that we have in the enterprise. It is being used for automated file processing. We get the file from the mainframe.

It gives a real-time view of all the batch processing that we have. Monitoring-wise, it is really good. 

It also gives us the ability to connect different software processes.