Broadcom Automic Workload Automation sits at the heart of enterprise batch and scheduling estates. The buyer side reference. The agent metric. The job execution math. The renewal levers under Broadcom.
Broadcom Automic Workload Automation is the rebranded CA Automic platform, now under Broadcom subscription terms. The licensing reference is the agent metric. The commercial risk sits in the subscription tier consolidation, the renewal uplift, and the unilateral end of life patterns Broadcom has applied across its software portfolio since the VMware acquisition.
This article reads as a buyer side reference. Pair it with the Broadcom VMware negotiation playbook, the Broadcom ELA article, the Broadcom advisory practice, and the Broadcom hub.
Automic runs the enterprise batch and scheduling stack for many global organizations. The platform sits between core ERP, banking, manufacturing, and payment systems. The replacement cost is high. The migration window is long. The renewal leverage is asymmetric to Broadcom.
Automic uses the agent metric as the primary license unit. Each server, mainframe, application, or endpoint with an Automic agent installed counts as one unit. The metric is simple. The traps sit in the tier definition and the renewal cycle.
The agent is the Automic software installed on the managed system that executes the scheduled job. Agents run on Linux, Windows, mainframe, AS400, SAP, Oracle E Business Suite, and other endpoints. Each instance of the agent counts as one license unit. The unit price varies by agent type with mainframe and SAP agents priced at a premium.
Automic does not license by job count or by execution volume. A buyer with 1,000 agents can run 10 million jobs per month at the same license cost as a buyer running 100,000 jobs. The agent count is the only license variable.
The Automation Engine and the underlying database carry their own license footprint on Oracle, SQL Server, or PostgreSQL. The database license is separate from the Automic agent count and is counted under the database vendor rules.
Broadcom collapsed the legacy CA catalog into three or four subscription tiers across most products. The tiers bundle functionality that was previously sold as discrete add ons. The renewal moves functionality between tiers each cycle.
| Tier | Typical content | Notes |
|---|---|---|
| Core or Standard | Base scheduling, agent platform, monitoring | Floor tier |
| Advanced or Enterprise | SLA management, calendar engine, predictive analytics | Most enterprise estates land here |
| Premium or Service Orchestration | Service orchestration, automation studio, hybrid cloud connectors | Top tier |
| Add on packs | SAP integration, mainframe integration, cloud connectors | Often pulled into tiers at renewal |
Broadcom moves features between tiers at the renewal anniversary. A capability bundled into the Advanced tier in 2024 may be repackaged into the Premium tier in 2026. The buyer either pays for the higher tier or loses the capability. Read the latest catalog before negotiating.
The agent count is the renewal math. The buyer side audit pulls the agent inventory, reconciles to the deployed estate, and rightsizes before the renewal. Most Automic estates carry 8 to 18 percent excess agent count from decommissioned systems and orphaned endpoints.
Broadcom runs a consistent renewal playbook across the CA portfolio. The buyer should expect three traps at the next renewal and plan around each one before the quote arrives.
The contract levers sit in the renewal terms, the audit clause, the migration window, and the price cap. Each lever is negotiable in the right order of operations.
The eight step checklist below moves the Broadcom Automic renewal from a passive uplift to an active negotiation. Open it 36 months before the next renewal on enterprise scale estates.
Yes. Broadcom inherited the CA audit clauses and applies them to the Automic product family. The audit pulls the agent inventory from the Automation Engine and reconciles it to the licensed agent count. Buyers should run an internal reconciliation every six months and remove decommissioned agents from the inventory to avoid an audit finding at renewal.
Yes. The renewal is the moment when the agent count is reset. Inside the term, true down is typically limited to specific clauses in the order form. At renewal the buyer can drop agents that are no longer deployed, decommission test and dev pools, and right size the tier mix. Always reconcile the inventory before signing the next subscription period.
Broadcom is converting perpetual CA entitlement to subscription on most products. The conversion runs at the renewal or earlier when the support contract lapses. Buyers carrying perpetual Automic licenses should expect a subscription conversion proposal and should model the cost difference before signing the next renewal.
The credible enterprise alternatives include Stonebranch Universal Automation Center, BMC Control M, Redwood RunMyJobs, and selected open source schedulers for non production workloads. Each alternative carries different commercial mechanics and different migration costs. Run a competitive RFP at every renewal even if the migration is not executed, to inform the negotiation envelope.
Yes. The Automic SAP agent and the mainframe agent are priced at a premium against the standard Linux and Windows agent. The premium reflects the integration depth, the certified compatibility, and the support level. Buyers running SAP or mainframe workloads should price the agent mix separately when modeling the renewal.
An enterprise scale Automic migration runs 18 to 36 months. The work covers inventorying every scheduled job, mapping the dependencies, rebuilding the calendar and SLA configuration, and re testing the production schedule. The cost typically runs into single digit millions plus internal resource. The credible migration plan is the negotiation lever, even when execution is not the preferred outcome.
Redress runs the Automic renewal work as a 16 to 24 week assessment plus negotiation engagement. The work pulls the agent inventory, reconciles to the deployed estate, scores the tier mix, and builds the migration plan. The deliverable is a defended subscription envelope, the five contract levers, and the 36 month renewal calendar.
Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.
A buyer side framework for the next Broadcom renewal cycle. Tier benchmarks, agent metric math, price cap language, and the residual clause checklist for the wider Broadcom portfolio.
Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for Broadcom customers running VMware, Automic, Symantec, Mainframe, and the wider CA estate.
Open the white paper in your browser. Corporate email only.
Open the Paper →We pulled the agent inventory at month 30, decommissioned 11 percent of orphaned endpoints, rightsized the tier mix from Premium to Advanced on the non orchestration estate, and negotiated a three year price cap at 3 percent. The next renewal landed 22 percent below the Broadcom opening quote.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
VMware bundle movement, Automic tier composition, Symantec packaging, mainframe price patterns, and the wider Broadcom commercial leverage signals across every renewal cycle.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
