① Product · BMC
MaxView is a BMC mainframe tool, and like the rest of the BMC z/OS portfolio it is priced on MSU, often under consumption terms. The product name may have shifted with the AMI rebrand, but the licensing mechanics are the constant worth knowing.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →MaxView sits within BMC's mainframe systems management portfolio, the same lineage that produced MainView and the current AMI Ops suite. BMC has rebranded much of that portfolio under the Automated Mainframe Intelligence, or AMI, banner, so a current order may carry a related AMI name rather than the MaxView label. We describe it at the level the evidence supports and flag where it is worth confirming the exact product on your own contract. What does not change is the part that determines cost: BMC licenses its z/OS tools on a single, consistent commercial model, and that model is what this page is about.
As a BMC mainframe product, MaxView is licensed on MSU based capacity, the metric BMC applies across its z/OS portfolio. Many estates contract under BMC's zConsumption Licensing, paying on the prior year's actual MSU consumption with an annual true up on overage, while older agreements remain on fixed MSU capacity. The charge follows machine capacity, not a per user or per object count. Consumption conversions have commonly rested on a stated MIPS to MSU ratio tied to the machine models in place when the order was signed.
| Element | How MaxView is treated |
|---|---|
| Metric | MSU based capacity |
| Model | zConsumption Licensing (zCL) or fixed MSU |
| Reconciliation | Annual true up on consumption overage |
| Conversion basis | Stated MIPS to MSU ratio, e.g. 8.2 to 1 |
| Cost driver | Licensed or consumed MSU |
Directional summary. Confirm the exact product entitlement and terms on your own BMC order.
Three drivers set the number on any BMC mainframe line, MaxView included. Consumed or licensed MSU, because the metric follows capacity, so estate growth and peak shifts lift the charge regardless of how the tool itself is used. The MIPS to MSU conversion ratio, because a ratio fixed to older machines can drift and inflate the consumption baseline as hardware changes. And bundling, because BMC products are frequently sold inside a larger AMI agreement where the individual line cannot be benchmarked. Consumption pricing rewards a flat profile and punishes an uncapped true up.
The recurring traps live in the consumption mechanics that govern the whole BMC estate. An uncapped annual true up turns a single high consumption year into a higher recurring baseline. A MIPS to MSU ratio carried forward without review, the classic being a figure such as 8.2 to 1 tied to retired machines, can overstate consumption against current hardware. And scope creep, where components spread onto systems the entitlement never covered, widens the basis quietly. Independent validation of the consumption report and the conversion ratio against actual capacity is the defense, the same discipline we bring to BMC contract review.
The consumption levers come first. A true up cap so a single peak year cannot become a permanent floor, and a renegotiation of the MIPS to MSU ratio in good faith as hardware changes, language BMC contracts commonly anticipate. The contract levers are uplift caps and unbundling the line from the wider BMC AMI agreement so it can be benchmarked on its own. Where a credible alternative exists for the function MaxView performs, a costed displacement study adds leverage even when the intent is to reprice. We confirm the entitlement, model the consumption baseline, and test the ratio before the renewal sets the next term, the core of our BMC work.
As a BMC mainframe product, MaxView is licensed on MSU based capacity, the metric BMC applies across its z/OS portfolio. Many estates contract under BMC's zConsumption Licensing, paying on the prior year's actual z/OS consumption with an annual true up on overage, while older agreements sit on fixed MSU capacity. The charge follows machine capacity rather than a per user or per object count. Confirm the exact entitlement on your own order, as BMC product names and bundles have shifted with the AMI rebrand.
MaxView sits within BMC's mainframe systems management portfolio, the same lineage that produced MainView and the current AMI Ops suite. BMC has rebranded much of that portfolio under the Automated Mainframe Intelligence, or AMI, banner, so the product may appear under a related AMI name on a current contract. The buyer side point holds either way: the licensing mechanics are BMC's standard MSU model.
Under zConsumption Licensing you pay on prior year actual MSU and true up overage at year end. An uncapped true up lets a single high consumption year reset the recurring baseline upward, and a MIPS to MSU conversion ratio tied to retired machines can overstate consumption against current hardware. Both are negotiable, and both are commonly left unexamined.
The levers are a true up cap, a renegotiated MIPS to MSU ratio as hardware changes, uplift caps, unbundling the line from the wider BMC agreement so it can be benchmarked, and a costed alternative where one exists. Modeling the consumption baseline independently before renewal is what turns these from theory into price movement.
Publisher hub: BMC mainframe licensing. Related product: BMC AMI Ops. Related concept: MSU explained. Put it to work: BMC mainframe contract review.