① Journal · BMC · AMI Security
BMC AMI Security bills on consumption, with a zConsumption Licensing option set against prior year actual MSU, so the consumption baseline and the bundle move the bill more than the list rate. Here are the seven levers that actually shift an AMI Security renewal, and how each one works.
The list rate is the negotiation people expect. The consumption baseline and the bundle are the ones that decide the bill.
BMC AMI Security is a mainframe security detection and response layer that sits on top of the external security manager, whether RACF, ACF2, or Top Secret, rather than replacing it. It is licensed on mainframe capacity measured in MSU, with a zConsumption Licensing option that bills on prior year actual z/OS MSU and settles overage in a year end true up. That means the charge follows the consumption baseline, the true up applied to it, and the way the product is carried within the wider BMC AMI portfolio, not a flat list. Buyers expect to argue the rate card, but the number on an AMI Security renewal moves on the accuracy of the consumption data, the scope of the bundle, and the cap on the true up.
Around the baseline sit the structural levers: the true up under zConsumption Licensing and whether it is capped, the AMI portfolio bundling that can carry modules you do not use, the displaceability of a monitoring layer compared to the security manager beneath it, and a multi year term traded for relief. Each is decided on independently validated consumption data, because an uncapped true up or an unexamined bundle locks in overspend for the life of the deal. Read this with our Top Secret licensing page and the BMC publisher hub.
What we commonly observe · the lever and how it shifts the AMI Security number
| Lever | How it works | What it moves |
|---|---|---|
| Bill on prior year actual | zConsumption Licensing sets the charge on real MSU | The basis the renewal is calculated on |
| Cap the true up | A ceiling on the year end overage settlement | The surprise at the end of each year |
| Scrutinize the AMI bundle | Strip modules carried in the portfolio but not used | What the single number actually covers |
| Scope to monitored LPARs | Confine the product to the systems it actually watches | The consumption baseline the bill rests on |
| Price a credible alternative | A monitoring layer has substitutes, so cost one | The captive assumption behind the renewal |
| Trade term for relief | A multi year commitment in exchange for a concession | The effective rate and any one time credit |
| Validate the consumption data | Independent check of the reported MSU figures | The accuracy of the number everything rests on |
Levers are what we commonly observe working across buyer side engagements, not statements of BMC policy, and the effect of each depends on your estate. Your consumption data, bundle, and contract govern the real number.
Under zConsumption Licensing the charge is set against prior year actual z/OS MSU, with overage settled in a year end true up. That makes the consumption data and the true up the live questions. If the reported MSU overstates what AMI Security actually monitors, or the true up is uncapped, the number drifts upward year on year. Validate the consumption independently and cap the true up before it is applied, so the back half of the term does not run away.
A true up you cannot cap is a renewal you cannot predict.
AMI Security is often carried inside the broader BMC AMI portfolio, where the renewal arrives as a single number and unused modules ride along inside it. Pull the security line out, price it on its own consumption, and the question becomes which capabilities you actually run. Stripping modules you do not use, and scoping the product to the LPARs it genuinely monitors, removes the cover the bundle provides.
The bundle hides the line, so open the bundle.
A security monitoring and response layer is a bounded function with alternatives, including the native auditing of the security manager itself and competing detection products, so it is more displaceable than the RACF, ACF2, or Top Secret estate beneath it. A credible, costed alternative is therefore a usable lever here. It does not have to be executed; pricing it changes the captive assumption the renewal rests on.
The monitoring layer moves more easily than what it monitors.
④ Where the AMI Security number is moved
The list rate is the argument you expect. The consumption, the true up, the bundle are the ones that count. Pin the consumption, cap the true up, open the bundle.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
AMI Security is a detection and response layer on top of the external security manager, licensed on MSU with a zConsumption Licensing option that bills on prior year actual z/OS MSU and trues up at year end. The bill follows the consumption baseline, the true up, and the bundle, not a flat list. See MIPS and MSU explained.
It sets the charge against prior year actual z/OS MSU with overage settled in a year end true up, so the accuracy of the consumption data and the size of the true up are the live questions. Validate the consumption, scope to the monitored LPARs, and cap the true up before it applies. See BMC price increase patterns.
A monitoring and response layer is a bounded function with alternatives, including the native auditing of the security manager and competing detection products, so it is more displaceable than the RACF, ACF2, or Top Secret estate beneath it. A priced alternative is a usable lever. See competitive alternatives as leverage.
Bill on prior year actual, cap the true up, scrutinize the AMI bundle, scope to monitored LPARs, price a credible alternative, and trade term for relief. Our license negotiation service sets the structure and our cost optimization validates the consumption. See also the BMC renewal advisory.
Related: BMC publisher hub · BMC price increase patterns · Top Secret licensing · BMC renewal advisory · license negotiation
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →