① Journal · Renewal negotiation
Under consumption licensing, the AMI Ops renewal is decided before the meeting starts, in the baseline drawn from last year's SCRT data. Five factors move the number, and the one that matters most is set the moment that baseline is committed.
AMI Ops is priced on a baseline set from your own history.
BMC AMI Ops, the z/OS monitoring family BMC formerly sold as MainView, watches the performance and availability of the estate, alongside the alternatives IBM OMEGAMON and Broadcom (CA) SYSVIEW. It is commonly licensed under BMC zConsumption Licensing, where the annual baseline is built from the previous twelve months of Sub-Capacity Reporting Tool data, the fee is projected to cover that baseline, and a year end true up reconciles consumption above it. The renewal that focuses only on a discount misses where the money is: the baseline is the number, and it is drawn from your own consumption history before the negotiation even opens.
That reframes the exercise. The buyers who win an AMI Ops renewal arrive having validated the consumption history the baseline is built on, modeled the true up exposure, audited the monitoring modules actually in use, and built a costed view of the alternative on a stack that, unlike a security manager, can be displaced. The five factors below run roughly in order of how much they move, the baseline and the true up first, the alternative and timing last. Read this with our BMC publisher hub and our explainer on the Sub-Capacity Reporting Tool.
Each factor and which direction it moves the AMI Ops bill
| Factor | What it moves | When it pays most |
|---|---|---|
| The zCL baseline | The committed consumption the fee is projected against | Before the baseline is set, from clean SCRT history |
| True up exposure | The year end charge for consumption above baseline | Where workload climbs through the term |
| Module scope | How many monitoring modules the deal actually needs | Where modules accumulated beyond what is used |
| A credible alternative | Whether the vendor prices a permanent stack or a movable one | When a costed OMEGAMON or SYSVIEW view is built early |
| Timing and the term | The leverage window and the consumption protections | At the term boundary, before the baseline commits |
Consumption model names, module names, and baseline mechanics change; verify the current ones on your own agreement at the time of negotiation. The order is the durable part: the baseline and the true up set the floor, and the scope, the alternative, and timing price what is left.
Under zConsumption Licensing the baseline is set from the prior twelve months of MSU consumption and becomes the figure the fee is projected against. A baseline drawn from a peak period locks a high floor into the term. Validate the consumption history independently and stress test the baseline before it commits, because it is far easier to set high than to bring back down.
The baseline is the renewal, set before the meeting.
Consumption above the baseline is reconciled through a year end true up, so a baseline set tight against a growing workload trades a lower fee now for a larger reconciliation later. Model the true up across the realistic workload path before you agree the baseline, so the projected fee and the expected true up are weighed together rather than discovered at year end.
Price the baseline and the true up as one number.
AMI Ops is modular, covering z/OS and subsystems such as Db2, IMS, and CICS. Modules accumulate over years, and a deal often carries monitoring the estate no longer relies on. Audit which modules are genuinely in use before the renewal, because retiring unused scope reduces what the consumption deal has to cover.
Pay for the monitoring you watch, not the modules you own.
Unlike a security manager, a monitoring stack can be displaced with planning. IBM OMEGAMON and Broadcom (CA) SYSVIEW are established alternatives, and the migration is real but bounded work. A costed view built early, including the effort to rebuild dashboards and automation, removes the assumption that the monitoring stack is permanent and changes how BMC prices the renewal.
A stack you can move is a stack you can price.
Leverage exists in a window before the term ends and before the consumption baseline is committed. Start early enough to validate the history, model the true up, and audit the modules, then write consumption protections and review points into the close so a flat estate does not carry a compounding fee for standing still.
Start before the baseline becomes the floor.
④ The order that wins
Consumption licensing decides the renewal in the baseline. Set it from a peak and you pay the peak all term. Stress the baseline, model the true up, and price what is left.
Typical reduction negotiated on renewal spend
Mainframe spend negotiated on the buyer side
Engagements delivered since 2019
The consumption baseline. AMI Ops is commonly licensed under BMC zConsumption Licensing, with the annual baseline built from the prior twelve months of SCRT data and a year end true up above it. Validating that baseline and the true up exposure, not chasing a headline discount, is where the recoverable cost sits.
Because it is the figure the fee is projected against for the whole term. A baseline drawn from a peak period locks a high floor in, and it is far easier to set high than to bring back down. Stress testing it before it commits is the single most valuable move.
Yes, with planning. IBM OMEGAMON and Broadcom (CA) SYSVIEW are established alternatives, and the migration is real but bounded work. A costed view built early removes the assumption that the monitoring stack is permanent and changes how the renewal is priced.
Early enough to validate the history, model the true up, and audit the modules before the baseline commits. See our BMC publisher hub and license negotiation service.
Related: BMC publisher hub · Control-M renewals · MAXM renewal · Log Master for Db2 renewal
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →