Guide · For the CIO

The CIO Guide to Mainframe Licensing.

Mainframe software is one of the largest lines in the IT budget and routinely the least governed. It is licensed on capacity, it spans several publishers with different metrics, and it grows quietly between renewals. Here is what decides the bill, and where a CIO should direct leverage and governance.

48H Audit notice or renewal under 18 months out? We mobilize within 48 hours.

Get expert help →

Your largest IT line, governed least. That is the gap.

For most large enterprises the mainframe still runs the systems that cannot fail: core banking, claims, billing, reservations, and records. The hardware is a small part of the cost. The software, licensed on capacity and renewed every few years across IBM, Broadcom (CA), BMC, Rocket Software, Software AG, Compuware (BMC), and Syncsort (Precisely), is the large part, and it is usually managed as an occasional procurement event rather than a continuous discipline.

That gap is where the money leaks. Between renewals, capacity grows and resets baselines, bundles accumulate families no one uses, and sub-capacity scope drifts. Then a renewal lands with an uplift that looks like a price increase but is mostly drift the organization allowed. A CIO does not need to learn SCRT line by line. The CIO needs to know what decides the bill, what to govern continuously, and where to bring in buyer side help. This guide covers all three.

What decides the bill

Licensing concepts →
The levers that move a mainframe software bill, and who owns them
LeverWhat it controlsWhere to act
Licensing metric (MSU, MIPS, capacity)How cost scales with the machineUnderstand the metric per product; manage sub-capacity scope
The baselineThe capacity figure the renewal resets toCap it; stop uncapped growth from staging the next uplift
The bundleWhich product families you still pay forRationalize; retire idle families before renewal
The pricing modelTraditional capacity versus consumption modelsEvaluate Tailored Fit Pricing and Broadcom MCL on their merits, not the pitch
The renewal calendarWho controls the clockStart 18 months out; never negotiate against your own deadline
The credible alternativeYour floor in any negotiationBuild it before the renewal; it works even when you stay
Audit exposureCompliance risk that becomes a billValidate your own sub-capacity and entitlement position continuously

Directional and pattern level. Metrics, pricing model names, and vendor behavior evolve, so confirm the current rules and your own contract terms before acting. The point for the CIO is the shape: seven levers, most of them set between renewals, not at them.

What a CIO should govern

Our approach →
01

Keep a current inventory

Every product, every contract, the metric and licensed capacity per product, and the expiry per agreement. Most organizations cannot produce this on demand. It is the foundation of every decision, and its absence is the first thing a vendor exploits.

02

Measure consumption against entitlement

Track what you actually use against what you are contracted for, continuously, not just before a renewal. The gap between contractual and consumed capacity is where both overpayment and audit exposure live.

03

Own the renewal calendar

Know every expiry 18 months out and run each renewal as a planned program. The single most common cause of a bad mainframe deal is a renewal that arrives as a surprise and is negotiated against a deadline the vendor set.

04

Treat licensing as an operating discipline

Stand up a light, recurring governance rhythm rather than a procurement scramble every few years. The estate that reviews its position quarterly captures more, is surprised less, and walks into renewals with leverage already built.

Where buyer side help fits

Our services →

You sit on one side of the table. So should your advice.

The vendors field specialists whose job is to maximize the renewal. Most enterprises meet them with a generalist sourcing team and a mainframe manager already running the platform full time. Independent buyer side advice closes that asymmetry: estate baselining, bundle rationalization, alternative evaluation, and the negotiation itself, all on the buyer's side only. Across our engagements, buyer side preparation commonly recovers 20 to 35 percent against the opening position, with the bigger wins from retiring idle families and correcting baselines rather than shaving rates.

Start with the publisher hubs for the vendors you run, and the licensing concepts index for the metrics. Match work to a service: renewal advisory, license negotiation, cost optimization, or audit defense. For the renewal mechanics, see the 18 month plan and handling a large uplift.

Questions CIOs ask

Ask yours →
Q1

Why is the software so expensive?

Because it is licensed on capacity, not hardware purchase, so it scales with MSU or MIPS and recurs every year. Over a lifecycle, software and support dwarf the box, across several publishers with different metrics.

Q2

What should I govern?

Continuously: a current inventory, consumption against entitlement, and the renewal calendar. At renewal: the leverage position, meaning a rationalized scope and a credible alternative built before the vendor controls the clock.

Q3

How much can we save?

Commonly 20 to 35 percent against the opening renewal position, with the larger wins from retiring idle families and correcting uncapped baselines rather than negotiating headline rates.

Q4

Do I need outside help?

The vendors bring specialists; most buyers bring generalists. Independent buyer side advice closes that asymmetry on baselining, alternatives, and the negotiation, entirely on your side of the table.

Audit notice or renewal under 18 months out? We mobilize within 48 hours.

Your largest line deserves governance. Let's build it.

Get expert help