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
JAMS
Score 8.2 out of 10
N/A
JAMS is a centralized workload automation and job scheduling solution that runs, monitors, and manages jobs and workflows. Reliably orchestrate the critical IT processes that run your business from a single pane of glass.
$9,996
per year
Pricing
AutoSys Workload Automation
JAMS
Editions & Modules
No answers on this topic
Core
9,996.00
per year
Advanced
Customized Pricing
per year
Offerings
Pricing Offerings
AutoSys Workload Automation
JAMS
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
- Core: For small teams getting started with automation. Core Integrations: PowerShell, SQL, Azure Data Factory, Python, 20+ others.
- Advanced: Comprehensive solution for large-scale operations. Core Integrations: SAP, JDE, Ellucian Banner, Informatica, Mainframe and Power Systems.
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 currently one of the best of the lower entry cost options out there, as it currently is a set license cost, not based on the number of jobs executed. In the hands of a good script writer and users with workflow experience, it's a powerful tool to accomplish just about any process that you have a need to complete.
The Activity Monitor clearly shows the Running Jobs, and Jobs that are to run soon. Successful Jobs can be viewed as well. The Refresh of this monitor is completely customizable to your liking.
Job Definitions are very well organized by use of Folders. This simplifies the structure of how to best Implement JAMS Jobs, including the ability to provide specific properties on each folder - whereby Jobs will inherit these properties.
Connectivity to servers is well thought out by having Shortcuts to include Credentials and Connection Store for server information.
JAMS Jobs can be controlled via System Resources. This is very powerful and is a very useful configuration found in JAMS.
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
JAMS is a critical resource free up people to do other things and ensuring that processes and tasks are run consistently. We are also confident that procedures are run consistently and on time or as soon as the necessary data is available. With automated job failure notification, we are not required to check that jobs are running correctly.
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.
JAMS is very user friendly; you hardly need to do coding. The only thing that I would say a challenge is setting it up, but that's because you barely know the product yet and, in every processing, setting up is the difficult part. But once you've set it up and you are going to use it, you will really feel that it is worth to invest in this kind of software solution, it really does it job very well.
We didnt really encounter any downtime, no issues encountered during 2 years of use of JAMs also our client barely raise an issue with JAMS, mostly the issues is on the batch jobs that jams executes. So I would gave it a perfect 10, very reliable hardly encounters any error and bug
JAMS performance is very great, there are no issues raised with the performance, it just like nothing happens on the job after integration it gives you this monitoring capability, no reports and bugs raised on the performance, we didnt do integration with other software only database and with use of JAMS agent to different servers
I've never had to wait more than a day for a response to any email queries submitted. We had a very positive experience using support hours during out migration process from v6 to v7. We've also recently had a weeklong group training course where all attendees were positive about the learning outcomes, a shoutout to Jose who did both the migration and the weeklong course!
People that were involved in the POC found the training a lot easier to follow. I think most people would have preferred to just get the training material and run through themselves.
I Was not part of the original Implementation, and the persons did that are no longer with the Organization. But I was part of the recent Upgrade process a year ago and I am the JAMS admin and was very pleased
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.
JAMS is WAY more advanced, it isn't a fair comparison. The history is easy to get through. It is easy to get alerts of complete to failed and with a log. Adding jobs is extremely easy that even my teammates who do not manange the software are able to set them up. With the new web component we are very excited for the future of JAMS advancements.
The product is quite flexible. There are a number of features and functions that we use on a daily basis, and there are many features that are available that we have not yet needed or explored (like setting up jobs with the ability to do FTP or Sftp file transfers).
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.
Using JAMS when working from home (initially COVID, and now permanent) gives me tremendous visibility into the running operations of our business without any loss in productivity for not being in the office.
With JAMS I can more tightly schedule evening batch jobs by running one job after the successful completion of predecessor, as opposed to the CRON like guessing at safe start times.
Central control on a monitored server in a datacenter for all job scheduling tasks has given us 99.9% uptime reliability, instead of herding cats on multiple machines.
