ActiveBatch Workload Automation vs. AutoSys Workload Automation

Any large business or organisation that wants to manage their workload effectively and with the least amount of room for error might choose the ActiveBatch Automation tool. Being a consultant I feel that It aids in task automation and has the flexibility to change in response to varying company requirements. It helps to save huge time by doing all the repetitive tasks on daily basis. During the patching activity the schedulers can be stopped. It also help by alerting us if any system/job is down so that SLA can be saved. Overall ActiveBatch Automation stands as a dependable cornerstone for ensuring the seamless operation of our tasks.

Incentivized

In Informatica or Spark ETL jobs loading data into a Data Warehouse using AutoSys Workload Automation triggers ETL pipelines, monitors completion of jobs and also triggers the power bi report refresh. AutoSys Workload Automation can schedule jobs based on file arrival, and provide alerts if any data loads get failed. A small data team managing greater than 100 jobs. Buying and maintaining AutoSys Workload Automation is overkill in terms of cost, complexity and maintenance does not justify the value

Incentivized

• Makes scheduling easy to understand, follow, and rerun jobs when necessary.
• Allows for cross-team coordination of scheduled tasks which reduces errors.
• Makes stopping jobs easy when needed for server/database downtime.
• Scripting enables us to easily change email addresses for failed job alerts.
• Nested plans/jobs make creating and changing dependencies simple.

Incentivized

• 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.

Incentivized

• String handling / parsing. I find myself using PowerShell to do a fair amount of text parsing (particularly if manipulations are needed) - not necessarily a bad thing, but certainly a place where ActiveBatch could be improved.
• Debugging - or lack of it! With no stepping debugger, it can be a longer process than many other programming / scripting environments: rather than simply stepping through and observing state changes, I find myself inserting logging steps to excess, then having to clean them up once the error is found.
• The perennial - Documentation! While a near-universal complaint for *any* software, ActiveBatch's developer documentation is somewhat spotty - just where I need detail, I find summary-level info. There is lots of documentation (as there should be for a tool with such a wide range of applications), but it is in mixed formats (some PDF, some CHM), and the descriptions of specific fields within job steps is often little more than I can get in a tool-tip in the GUI. Allowable ranges, expected formats for string data, and similar helpful details are inconsistent.
• The KnowledgeBase at ASCI's web site often has examples which answer the questions I have, but not always - and not always under the search terms one would think to use.

• 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

Incentivized

We can easily add new plans/jobs in our batch schedules. Also, coordination with reporting and QA jobs is simple to do. Building schedules, restarting jobs, triggering dependencies is easy to understand. The system is very stable and allows us to easily see overall processing times.

Incentivized

AutoSys Workload Automation is a place to schedule, monitor, and manage thousands of jobs. Time, file arrival, dependencies are much very flexible. Once jobs are set up they run consistently with minimal intervention. AutoSys Workload Automation is powerful but very complex o understand. Mainly for beginners the interface is not user friendly. AutoSys Workload Automation is very useful in terms of job scheduling and automation. AutoSys Workload Automation is also useful for strong logging and reporting purpose. AutoSys Workload Automation has reduced a lot of human efforts and manual processing.

Incentivized

My colleague contacted them directly, I only know hearsay on this but it was not good.

Incentivized

The workload automation solution is based on the specific needs of an organization, as well as the features, capabilities, and costs of various solutions. A thorough evaluation process and consideration of these factors can help ensure the selection of a solution that aligns with overall business objectives and meets the specific needs of the organization.

Incentivized

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.

Incentivized

• ActiveBatch can automate intricate procedures and minimise manual involvement, which can boost an organization's production and efficiency.
• Organisations can save money by using ActiveBatch to automate operations, which lowers the expenses of manual labour and potential mistakes.
• Implementing ActiveBatch could come with hefty up-front expenses including licencing, instruction, and consultancy fees, which could have a short-term negative impact on ROI.

• 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.

Incentivized