Home / Guides / BMC Audit Notice
① Buyer guide · BMC audit
A BMC audit notice tests two things: your MSU sub-capacity record on MainView and the AMI estate, and your zConsumption Licensing true up. Respond well and the claim holds to actual consumption. Here is the seven step protocol we run.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →BMC's mainframe estate spans MSU based products, MainView and the AMI portfolio prominent among them, and the consumption based AMI programs. For the MSU based products, a BMC audit commonly examines sub-capacity SCRT data and the capacity the software is deployed against. Where BMC zConsumption Licensing applies, you pay against the previous year actual z/OS consumption and true up any overage at year end, so the audit becomes largely a consumption reconciliation. The two methods carry different risks, and the first job is knowing which contract vehicle each product sits in before any data moves. Background: the BMC publisher guide.
Run these in order
The audit stops being two separate scrambles, one over MSU data and one over consumption, run against the vendor's clock. Scope gets held to the contract per vehicle, the SCRT peak gets validated before it becomes a number, the zCL consumption figure gets independently confirmed, and the sub-capacity record gets reconstructed before full capacity can be asserted. Most important, the finding gets handled as part of the commercial relationship: a settlement framed into the renewal is leverage, while a settlement paid alone is just loss. We mobilize within 48 hours of a notice.
Across 500+ engagements and $180M+ of negotiated mainframe spend, disciplined audit response paired with renewal sequencing typically holds claims to actual consumption and produces renewal reductions of 20 to 35% against the initial quote, with 48 hour mobilization the moment a notice lands.
For MSU based products such as MainView and the AMI portfolio, BMC commonly examines sub-capacity SCRT data and the capacity the software is deployed against. Where BMC zConsumption Licensing applies, the focus shifts to the annual true up of actual z/OS consumption against the prior year baseline. The method examined depends on which contract vehicle each product sits in.
Under zCL, you pay against the previous year actual z/OS consumption and true up any overage at year end. An audit in that context is largely a consumption reconciliation. The lever is validating the consumption figure independently and confirming the products in scope are actually the ones the zCL agreement covers, before the overage is calculated.
As with any MSU based vendor, incomplete or unreliable sub-capacity data risks exposure defaulting toward full capacity, the most expensive basis. Reconstructing a defensible sub-capacity and SCRT record before responding caps the claim at actual peak rather than installed capacity.
Usually yes. A standalone settlement is pure cost; folded into a renewal or enterprise agreement it becomes leverage, traded against caps, term, and the products you keep. We mobilize within 48 hours of a notice.
Related: BMC audit defense, BMC MSU optimization, and the firm wide audit defense service.