Broadcom offers AutoSys Workload Automation, a solution to enhance visibility and control of complex workloads across platforms, ERP systems, and the cloud. It helps to reduce the cost and complexity of managing mission critical business processes, ensuring consistent and reliable service delivery. It is based on the former CA AutoSys, acquired by Broadcom with CA Technologies.
N/A
ignio AIOps
Score 8.1 out of 10
N/A
ignio AIOps, from Digitate in Santa Clara, is a solution designed to improve business agility by creating a unified view of the IT estate, connecting business functions to applications and infrastructure. This is combined with behavior profile of systems and applications that is continuously learnt using this blueprint. ignio aims to improve the transparency of complex Enterprise IT landscapes.
N/A
Pricing
AutoSys Workload Automation
ignio AIOps
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
AutoSys Workload Automation
ignio AIOps
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
AutoSys Workload Automation
ignio AIOps
Features
AutoSys Workload Automation
ignio AIOps
Workload Automation
Comparison of Workload Automation features of Product A and Product B
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
It's good for issue resolution, user access request automation, standard report generation, health checks, executing self-healing as configured in the attributes. Currently not good at real-time monitoring to trigger an action. Health checks have to be on a scheduled basis.
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
There is a lot more the desktop tool can do. For example, we need to apply an upgrade to get the tool to talk to our infrastructure while employees are working from home. The tool was initially installed with the assumption that the desktops would be in UserLand. Instead after COVID-19 the desktop/laptops have been used for over a year on people's home networks. As of right now, we have to sync when the devices are connected to VPN. Moving forward with the upgrade, we will be getting this data over TLS when they are connected to the untrusted networks.
The concept of ignio AlOps requires OCM efforts within most operational teams. This isn't necessarily the fault of the tool itself, but when implementing ignio, or any AIOps tool, the team will get a lot of pushback as an outside team is centralizing the operational improvements. The tool should have a centralized intake process that will allow the collection, ranking, and management of automation opportunities. ignio AlOps should then simulate the proposed efficiencies from implementing something within the backlog. Right now a lot of local teams are having a hard time getting on the same page as the enterprise teams, and a common methodology for prioritizing (even if overly simplistic) would go a long way to enterprise planning.
These tools are very new and things get added to them all the time. There should be a way for the product's stakeholders and process owners to understand the additional value ignio AlOps is gaining over time.
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.
ignio AIOps version upgrades were a heavy lift. Having to learn a new language versus an industry standard language took time. More consideration on overall internal long-term support needs to be determined.
We have built a healthy relationship with the vendor support team throughout the implementation phase, all incidents raised were resolved within the SLA without a fail
I am happy with the way team has implemented and shared the product for our organization. However, would like to see it get extended to the other line of business too.
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.
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.