① Journal · BMC
MainView, the BMC performance monitoring family now branded BMC AMI Ops Monitoring, is MSU priced like the rest of the estate, but it carries a second dimension: it is modular. Each subsystem monitor is separately entitled, and estates routinely pay to watch things they no longer run. The monitor footprint is the negotiation.
MSU priced and modular. The monitor footprint is the negotiation.
MainView is the BMC mainframe performance monitoring family, now offered under the BMC AMI Ops Monitoring brand. It is commonly licensed on mainframe capacity in MSUs, frequently tracking the rolling four hour average, and BMC offers zConsumption Licensing as an alternative that bills on actual MSU utilization, charging on the prior year's consumption with a true up on any overage. So far this is the standard capacity story. What makes MainView different is that it is modular: it covers many subsystems, among them z/OS, CICS, Db2, IMS, MQ, and middleware, and each is a separately entitled monitor.
That modularity is where the money hides. Monitor entitlements accrete over years as subsystems are added, but they rarely come off when a subsystem is retired or a team stops watching it. The result is an estate paying to monitor capacity it no longer runs, or duplicating coverage another tool now provides. The buyer who reconciles the entitled monitors against the ones genuinely used, on top of managing the capacity baseline, controls the number. Read this alongside our BMC support cost escalation piece and the BMC publisher hub.
MainView cost drivers · what each one is and the buyer side lever on it · illustrative, not a quote
| Driver | What it is | Buyer side lever |
|---|---|---|
| Capacity baseline | The MSU capacity and rolling four hour average the charge follows | Reconcile the baseline and smooth the peak |
| Monitor modules entitled | Separate monitors for z/OS, CICS, Db2, IMS, MQ, and more | Reconcile entitled monitors against those actually used |
| Retired subsystems | Monitors still entitled for workloads no longer run | Drop monitors for subsystems you have decommissioned |
| zConsumption Licensing | Usage based billing on actual MSU utilization | Model fixed capacity against zConsumption and choose on cost |
| Annual escalator | The yearly increase on the recurring charge | Cap the escalator in writing for the full term |
| Tool overlap | Coverage duplicated by another monitoring product | Consolidate so you are not paying twice to watch one thing |
Branding, modules, and the exact metric follow your specific BMC entitlement and the current MainView and BMC AMI Ops terms; treat the basis as something to read from the contract, not assume. The pattern, that the capacity baseline and the monitor footprint drive the number, is consistent across the estates we see.
The lever unique to MainView is the monitor footprint. Entitlements for individual subsystem monitors accrete over years and rarely come off when a subsystem retires. Inventory which monitors are genuinely watched against which are merely entitled, and drop the coverage that is buying nothing. This is usually the largest single lever on a MainView renewal.
Pay to watch what you run, not what you used to.
MainView is MSU priced, so the contracted capacity and your rolling four hour average drive the recurring charge. Reconcile the baseline against real monitored capacity and smooth the peak where it makes sense. The monitoring function does not change; the capacity it is billed at does, and that is real money recovered without losing visibility.
Same coverage, lower peak, smaller bill.
zConsumption Licensing bills on actual MSU utilization rather than fixed contracted capacity, which can favor an estate running below baseline or one whose monitored capacity has fallen. Do not take the model on the pitch. Build the renewal under both fixed capacity and zConsumption on your real numbers, then choose on cost with the trend working for you.
Decide the model on math, not on the slide.
Large estates often run more than one monitoring tool, with coverage that overlaps where products grew into each other's territory. At renewal, map the overlap and decide what each tool is genuinely for. Consolidating duplicated coverage stops you paying twice to watch one subsystem and tightens the baseline the next term builds on.
Do not pay two tools to watch one thing.
④ Where the MainView number is won
Monitors accrete. They rarely come off. The renewal is when they do. True the footprint, then sign the term.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
On mainframe capacity in MSUs, frequently tracking the rolling four hour average, under the MainView and BMC AMI Ops Monitoring branding. BMC also offers zConsumption Licensing, which bills on actual MSU utilization with a true up on overage. Because MainView is modular, the number also reflects which subsystem monitors you are entitled to. Read the exact basis from your entitlement.
The capacity baseline and the monitor modules. MainView is MSU priced, so contracted capacity and the rolling four hour average drive the charge, while each subsystem monitor is separately entitled. Estates frequently carry monitors for subsystems they no longer run. Reconciling entitled monitors against those actually used is usually the largest lever.
Decide on the numbers. zConsumption Licensing bills on actual MSU utilization rather than fixed capacity, which can favor an estate running below baseline or one whose monitored capacity has fallen. Model the renewal under both fixed capacity and zConsumption on your real utilization and monitor footprint, then choose on cost.
Inventory which monitors are entitled versus used, measure real MSU utilization against the baseline, and model zConsumption both ways. Reconcile monitors for retired subsystems out of the entitlement and press for a written escalator cap. Start twelve to eighteen months out. Our BMC MSU optimization service runs the full play.
Related: AMI Data for Db2 licensing · Log Master for Db2 renewals · Control-M renewals · BMC support escalation · BMC publisher hub · BMC MSU optimization
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →