Broadcom Software (CA) Mainframe. A buyer side CIO playbook for the CA mainframe framework.

Broadcom acquired CA Technologies in 2018 and inherited the largest non IBM mainframe software portfolio: 50 plus products spanning security (CA Top Secret, CA ACF2), storage (CA Disk, CA View, CA Deliver), systems management (CA OPS/MVS, CA Workload Automation, CA Sysview), and development (CA Endevor, CA Datacom, CA IDMS). Mainframe customers are structurally captive because product replacement requires multi year application refactoring or full mainframe migration. Broadcom has applied 30 to 80 percent price increases at CA renewal across documented enterprise cases since the acquisition. This playbook covers the CA mainframe portfolio under Broadcom, the MIPS and MSU metric mechanics, the workload economics, the renewal exposure patterns, and the 11 move buyer side playbook that delivers 20 to 35 percent against Broadcom CA opening proposals at renewal. Read the related IBM and mainframe practice, the CIO playbook for IBM security and storage software licensing, and the IBM knowledge hub.

The Broadcom CA mainframe portfolio

The Broadcom CA mainframe portfolio covers 4 product families.

• Security: CA Top Secret and CA ACF2 (mainframe RACF alternatives), CA Auditor, CA Cleanup.
• Storage and output: CA Disk, CA View, CA Deliver, CA Output Management.
• Systems management: CA OPS/MVS (mainframe operations automation), CA Workload Automation (mainframe job scheduling), CA Sysview (mainframe performance monitoring).
• Development and databases: CA Endevor (mainframe source control), CA Datacom (database), CA IDMS (database), CA Easytrieve (reporting).

Most enterprise mainframe customers run 5 to 15 CA products at scale, with each product priced separately on MIPS or MSU consumption metrics. Read the related CIO playbook for IBM PVU to VPC licensing transition.

MIPS metric mechanics

MIPS (Million Instructions Per Second) is the legacy mainframe capacity metric used across most CA products. Broadcom meters CA subscriptions against contracted MIPS at signature, with True Forward escalation if consumption exceeds the contracted MIPS during the term.

The 4 MIPS populations are:

• Under MIPS (paying for capacity not used, common in customers whose mainframe utilization dropped after distributed migrations).
• At MIPS (paying for the contracted capacity).
• Over MIPS (paying contracted plus True Forward escalation).
• Bespoke MIPS (negotiated structures at upper customer scale).

The buyer side discipline on MIPS is to reconcile actual deployed MIPS against contracted MIPS at every renewal. Customers who reduced mainframe footprint over the prior term but kept the historical MIPS commitment routinely overpay 15 to 30 percent. The next renewal is the only opportunity to true down; mid term true down is not supported. Read the related IBM licensing assessment service.

MSU metric mechanics

MSU (Million Service Units) is the modern mainframe capacity metric aligned with IBM's standard MSU framework. The MSU metric applies to CA products that Broadcom has migrated from MIPS to MSU pricing, with the migration ongoing across the portfolio.

MSU subscriptions have 4 dimensions.

• Rolling 4 hour average (R4HA) MSU measures peak utilization smoothed across 4 hour windows, which aligns with how customers actually run mainframe workloads.
• Sub capacity MSU licenses individual LPARs or workload groups rather than the full machine capacity, materially reducing license cost on mainframes running multiple workload classes.
• Workload License Charge (WLC) categories assign MSU consumption to specific workload classes for pricing purposes.
• Bespoke MSU covers negotiated structures at upper customer scale.

The buyer side leverage on MSU is the sub capacity transition. Most customers running full capacity MSU pricing on mainframes with multiple LPARs and varying workload patterns are paying for capacity they do not use. Sub capacity transition captures 25 to 50 percent reduction on most CA products that support it.

Workload framework

CA mainframe products integrate with IBM mainframe workloads across CICS, IMS, DB2, and MQ. The workload context matters for commercial leverage. Customers running heavy CICS workloads have higher CA Workload Automation and CA Sysview dependency. Customers running heavy DB2 workloads have higher CA Datacom and CA IDMS dependency. The workload analysis identifies which CA products are commercially critical (genuinely no alternative without years of refactoring) versus which are commercially negotiable (alternative exists with manageable migration cost). Read the related CIO playbook for IBM Maximo and industry solution licensing.

CA mainframe renewal mechanics

CA mainframe contracts run 3 to 5 year terms with annual billing. Broadcom has applied substantial price increases at renewal across documented enterprise cases.

The 4 renewal dimensions are:

• Scope (which products renew).
• Quantity (committed MIPS or MSU).
• Term (3 or 5 year).
• Bespoke (custom structures).

The renewal preparation sequence runs 12 to 18 months before expiry: deployment audit, MIPS or MSU reconciliation, workload analysis, alternative evaluation against IBM mainframe products and BMC competing products, and target outcome modeling. The disciplined preparation captures the 20 to 35 percent reduction that compounds across the 3 to 5 year term.

Renewal exposure patterns

11 move buyer side playbook

1. Inventory the full CA mainframe portfolio. All 5 to 15 deployed products, MIPS or MSU per product, term expiry per contract.
2. Reconcile actual MIPS or MSU consumption against contracted capacity. Under MIPS customers reclaim at renewal; over MIPS customers face True Forward.
3. Transition eligible products from MIPS to MSU. Sub capacity MSU captures 25 to 50 percent reduction where supported.
4. Map workload dependency per product. Critical workload (no realistic alternative) versus negotiable workload (alternative exists).
5. Evaluate IBM and BMC alternatives for negotiable products. CA Workload Automation has competition from IBM Workload Scheduler and BMC Control M. CA security products have competition from IBM RACF.
6. Start renewal preparation 12 to 18 months before expiry. Mainframe renewals require materially longer preparation than distributed software.
7. Cap annual escalator at 0 to 3 percent. Broadcom has applied 30 to 80 percent renewal escalations; explicit cap protects.
8. Negotiate True Forward methodology. Day of measurement, not peak, for MIPS reconciliation.
9. Lock multi year price hold against announced increases. Broadcom may apply further pricing actions during the term.
10. Coordinate CA renewal with broader Broadcom commitments (VMware, Symantec). Single Broadcom commercial conversation.
11. Build the audit defense framework. Mainframe audits require deep workload accounting; preparation matters more than reaction.

The framework is set out in the IBM and mainframe services practice, the CIO playbook for IBM security and storage software licensing, the IBM audit defense playbook, and the IBM vendor management playbook.

How we engage

• CA mainframe scoping. 6 week engagement covering full CA portfolio inventory, MIPS or MSU reconciliation, workload analysis, alternative evaluation. IBM and mainframe practice.
• CA mainframe renewal negotiation. 12 to 18 month managed renewal sequence with full preparation and alternative BATNA. IBM ELA renewal service.
• Mainframe audit defense. Full CA mainframe audit response. IBM license audit defense service.
• Vendor Shield. Continuous Broadcom advisory across CA mainframe and broader portfolio. Vendor Shield.
• Software spend assessment. Full estate baselining including CA mainframe. Software Spend Assessment.