A Scheduler You Can Trust
Overall Satisfaction with AutoSys Workload Automation
AutoSys Workload Automation is very easy to use for scheduling and monitoring batch jobs over multiple applications and platforms and also over the cloud as well. All our ETL pipelines in Informatica, Azure Data Factory, SQL jobs are triggered using AutoSys Workload Automation. Emails are triggered in case of any job delays or failures so that our incident response time is improved . Before automation, batch jobs are required to run manually but AutoSys Workload Automation has reduced the human intervention to run the jobs.
Pros
- AutoSys Workload Automation is our scheduler that automates and monitors workflows across all our system reducing manual runs
- Applications which run over multiples systems(cloud, on premise) are coordinated using AutoSys Workload Automation
- AutoSys Workload Automation clustering or failover ensures that workloads continue without any issue.
- AutoSys Workload Automation maintains execution logs and job history, which helps in compliance, audit trails, and root-cause analysis.
Cons
- In AutoSys Workload Automation, Workflow and job dependencies are shown in a static way, which makes user difficult to visualize more complex job chains or debug failures in a graphical view.
- Latest schedulers (like Control-M, Airflow) allow more easy workflow design makes user to understand it better, but AutoSys Workload Automation relies heavily on JIL scripts and text-based job definitions.
- AutoSys Workload Automation interface is very slow when searching or filtering over thousand of jobs
- Critical job process consistently complete on time without delays
- Significant reduction in team effort due to this resources for available for higher-value tasks. Human intervention is reduced due to this incident costs are also reduced.
- Faster incident resolution, improved productivity, and lower downtime.
In AutoSys Workload Automation, strong legacy presence, proven reliability, slightly simpler for basic scheduling if user already have in-house AutoSys Workload Automation expertise. so we already had investments in AutoSys Workload Automation, trained team, and large numbers of jobs running thus making AutoSys Workload Automation more cost-effective to continue rather than migrate to use AutoSys Workload Automation over Control-M. All our workloads are heavily batch-driven (SAP, ETL) real-time pipelines. AutoSys Workload Automation provides the robustness and enterprise support that Airflow lacks without heavy internal engineering overhead.
Do you think AutoSys Workload Automation delivers good value for the price?
Yes
Are you happy with AutoSys Workload Automation's feature set?
Yes
Did AutoSys Workload Automation live up to sales and marketing promises?
Yes
Did implementation of AutoSys Workload Automation go as expected?
Yes
Would you buy AutoSys Workload Automation again?
Yes

Comments
Please log in to join the conversation