Home / Publishers / BMC / MSU Optimization
① Commercial desk · BMC
BMC software commonly bills against MSU capacity, which means your peaks, your tier definitions, and your contracted baseline decide the spend before any discount does. We attack all three: the consumption, the contract, and the renewal where they meet.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →BMC's mainframe portfolio, the AMI families, MainView heritage monitoring, and Control-M for z/OS, is commonly licensed against MSU capacity. That creates a quiet coupling: as the IBM estate grows, through real workload or simple MIPS creep, the BMC bill typically grows with it, even though nothing about your BMC usage changed. Suite bundling adds a second layer, where individual products inside an AMI agreement stop being separately visible, and a third layer arrives at renewal, when growth assumptions get priced into the new baseline.
The buyer's counterweight is that the same MSU discipline that controls the IBM bill controls the BMC bill. The peaks are one estate. The work is making the contracts recognize that. Background: the BMC publisher guide and MSUs explained.
Five steps, in order
The MSU figure stops being the vendor's number. BMC's tier placement and growth assumptions get tested against an independently reconstructed consumption history, and the negotiation anchors on what you measurably run, not on what the agreement drifted into covering. Where BMC positions itself as the cheaper displacement for IBM or Broadcom (CA) tooling, we make that competitive posture do real work in your pricing. And the renewal lands with the contract terms, tier definitions, measurement windows, and caps, that make next cycle's optimization possible instead of contractually irrelevant.
Across 500+ engagements and $180M+ of negotiated mainframe spend, combining consumption discipline with a contractual reset typically produces renewal reductions of 20 to 35% against the initial quote.
Mainframe spend negotiated
Engagements delivered
Typical renewal reduction
Mobilization on audit notice or renewal
BMC products are commonly licensed against capacity, typically MSU based, whether on the full capacity of the machines where products run or on negotiated sub-capacity terms. That makes the contracted MSU figure and its measurement definition the primary cost driver, before any rate discussion.
Not automatically. Technical reductions lower cost only when the contract lets them: many BMC agreements bill against contracted capacity tiers rather than measured consumption until the renewal resets the baseline. The technical work and the contractual reset have to land together, which is why we run them as one engagement.
Control-M for z/OS commonly carries capacity linked terms while distributed Control-M is priced per job or per endpoint, and the mix is negotiated. Renewals are where the metric, the tier definitions, and growth assumptions get reset. See Control-M renewal levers.
12 to 18 months out is the runway that consistently produces the best outcomes, because consumption evidence takes months to build. Closer in, we compress the sequence; we mobilize within 48 hours.
Related desks: BMC license negotiation, BMC cost optimization, and the firm wide MSU optimization service.