The AMI bundle is a discount on what you don't use.

BMC AMI, Automated Mainframe Intelligence, groups BMC's mainframe products into suites: operations and observability (BMC AMI Ops, built from the former MainView estate), data and database management, security, and the DevX developer tooling that arrived with Compuware (BMC). These are sold as bundles, with a headline discount calculated against the sum of component list prices.

The pattern we commonly observe: the bundle includes products the buyer barely uses, the discount is framed against an inflated component list, and the structure makes dropping any one product look like forfeiting the deal. The result is steady payment for shelfware, renewed automatically because unpicking it seems to cost the discount. It does not have to.

A bundle exists to prevent exactly the analysis that would weaken it. Once you have a defensible price per component and a usage map beside it, three things become visible: what you pay for products you do not run, how much of the discount is real versus framed off inflated list, and where a credible alternative would actually save money. Vendors resist component pricing precisely because it converts a single take it or leave it number into a set of negotiable lines. Insisting on it, early, is the move that makes the rest possible.

We know how BMC AMI bundles are constructed and where the room sits: which components are routinely overweighted, how comparable suites have been repriced, and how drop rights and zCL caps have been won. We build the usage map, force the component view, and develop the credible exit on the products you use least. Directionally, across 500+ engagements and $180M+ in negotiated mainframe spend, unbundling work of this kind typically lands renewals 20 to 35 percent below the opening position. With a renewal under 18 months out, we mobilize within 48 hours.