① Journal · BMC · AMI Data for IMS · Renewal
BMC AMI Data for IMS is priced on MSU under consumption licensing, billed against prior period actuals. The renewal turns on the consumption baseline, the MIPS to MSU conversion ratio, and the peak the bill is measured against. The number moves when you check all three. Five levers move it.
AMI Data for IMS is consumption priced on MSU. Check the ratio and the peak, and you move the price.
BMC AMI Data for IMS, the database and system management portfolio for IMS, is licensed on mainframe capacity measured in MSU (Million Service Units), commonly under BMC consumption licensing where the bill follows prior period actual z/OS MSU consumption with a year end true up. Where a contract converts older MIPS entitlement to MSU, BMC bases the conversion on a stated MIPS to MSU ratio derived from the mainframe models in use at order time. That gives an AMI Data for IMS renewal three moving parts: the consumption baseline the bill is measured against, the conversion ratio that translates older entitlement into MSU, and the sub-capacity peak that drives measured consumption. The buyers who move the number examine all three rather than accepting the consumption, the ratio, and the peak the vendor presents.
The pattern we commonly observe is a consumption baseline that has crept up with the year end true up, a MIPS to MSU ratio frozen at an order made several hardware generations ago, and a rolling four hour average that has never been shaped for the AMI products specifically. The largest levers are the consumption baseline and the conversion ratio, because a stale ratio can translate the same workload into more MSU than the current machine warrants. Around them sit R4HA shaping, AMI portfolio unbundling, and a credible alternative. Read this with our explainer on soft capping and defined capacity and the BMC publisher hub.
What moves the number on a BMC AMI Data for IMS renewal · the lever and its effect
| Lever | How it works | Effect on the number |
|---|---|---|
| Consumption baseline | Reset the consumption the bill is measured against to genuine steady state | Lowers the prior period actual the true up builds on |
| MIPS to MSU ratio | Re-examine the conversion ratio against current hardware, not the order date | Removes MSU overstated by a stale ratio, a large hidden lever |
| R4HA shaping | Defined capacity and soft capping hold the rolling four hour average | Lowers the measured consumption the bill follows |
| Portfolio unbundling | Pay only for the AMI Data for IMS components you actually run | Removes line items from the renewal |
| Alternative tooling path | A credible IBM IMS tools or competitive path sits behind the renewal | Caps the renewal against a real switch |
These are levers and patterns we commonly observe on BMC AMI Data for IMS renewals, not guaranteed outcomes. The effect of each depends on your contract, baseline, conversion ratio, and consumption profile; validate your own SCRT data before relying on any figure.
Where MIPS entitlement was converted to MSU, the ratio was set from the model ratings in use at order time, and a ratio frozen several hardware generations ago can translate the same workload into more MSU than the current machine warrants. Pull the original ratio, recompute it against current hardware, and challenge any conversion that overstates MSU on newer, more efficient processors. This is a large hidden lever that buyers rarely examine. See our explainer on MSU explained.
A stale ratio overstates the MSU you pay for.
BMC consumption licensing bills against prior period actual MSU with a year end true up, so the consumption baseline and the rolling four hour average that feeds it are the recurring number. Pull twelve months of measured consumption, true the baseline back to steady state, and shape the R4HA with defined capacity and soft capping on the LPARs AMI Data for IMS runs on. The bill follows the consumption, so the consumption is where the renewal is won. See our explainer on the MSU baseline and how to reset it.
The bill follows consumption, so shape it.
AMI Data for IMS ships as a family of database and system management components, and a renewal often carries pieces no longer used. Inventory what is deployed, pay only for that, and resist consolidation pressure that re-bundles dropped components. Behind it, keep a credible IBM IMS tools or competitive path on the table, because a real alternative caps the renewal whether or not you execute it. See our piece on BMC audit activity.
Pay for what you run, with an exit in hand.
④ Where the AMI Data for IMS renewal is won
An AMI renewal turns on consumption, the ratio, and the peak. All three are yours to examine. Check the ratio, reset the baseline, shape the R4HA.
Typical renewal reduction
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
It is licensed on mainframe capacity measured in MSU, commonly under BMC consumption licensing where the bill follows prior period actual z/OS MSU consumption with year end true up. Where a contract converts older MIPS entitlement to MSU, BMC bases the conversion on a stated MIPS to MSU ratio derived from the models in use at order time. A renewal turns on the consumption baseline, that conversion ratio, and the sub-capacity profile consumption is measured against.
The consumption baseline and the conversion ratio. Consumption licensing bills against prior period actual MSU, so the measured consumption and year end true up drive the number. Where MIPS is converted to MSU, a ratio derived from older models can overstate MSU on newer hardware. Beyond those, shaping the rolling four hour average lowers measured consumption, unbundling the AMI portfolio removes line items, and a credible IBM IMS tools alternative caps the renewal.
Because the ratio set at order time can become stale. BMC has based MSU conversions on a ratio such as 8.2 MIPS to 1 MSU derived by dividing the model MIPS rating by the IBM MSU rating for the machines in use at the order. As hardware refreshes to newer processors, the same workload carries a different relationship, so a conversion frozen at an older ratio can translate into more MSU than the current machine warrants. The discipline is to re-examine the ratio against current hardware. See Datacom renewal negotiation.
We recompute the MIPS to MSU conversion ratio against current hardware, validate the consumption data independently, reset the baseline to genuine steady state, shape the rolling four hour average, and build the credible alternative before the vendor controls the clock. Our BMC license negotiation service runs the renewal from the buyer side and our renewal advisory service sets the strategy.
Related: BMC publisher hub · BMC audit activity · CICS renewal negotiation · soft capping and defined capacity · BMC license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →