IBM
Nordic Financial Institution. Mainframe software cost cut at renewal.
MLC charges tracked batch scheduling, not business growth. Peak management lowered the baseline and the renewal priced the lowered number.
MLC charges tracked batch scheduling, not business growth. Peak management lowered the baseline and the renewal priced the lowered number.
A Nordic financial institution cut its IBM mainframe software cost materially at renewal by attacking peak driven MLC charges, sub capacity reporting hygiene, and the ELA structure in one program.
The institution reviewed the estate because mainframe software had become its largest single IBM cost while feeling unmanageable: charges moved with monthly peaks that batch scheduling set, and the renewal added contractual uplift on top. The IBM Z platform ran core banking, so exit was not the lever; cost engineering was.
Monthly license charges price on the rolling four hour average MSU peak. One badly placed batch job in one month sets the bill for that month, which makes the peak a controllable cost driver.
The analysis found the billable peaks were artifacts of scheduling, not demand. Month end batch collided with online windows, soft capping was unused, and several peaks traced to movable housekeeping jobs.
Mainframe cost findings and actions
| Finding | Cost effect | Action |
|---|---|---|
| Batch and online collision at month end | Set the MSU peak in most months | Reschedule batch outside online windows |
| No defined capacity caps | Peaks ran uncontrolled | Apply soft capping to non critical LPARs |
| Housekeeping jobs in peak windows | Inflated rolling four hour average | Move to low utilization windows |
| ELA growth assumptions | Uplift priced on unsupported growth | Renegotiate against the workload baseline |
Modeling Tailored Fit Pricing against the optimized peak profile showed the consumption model priced higher than well managed MLC for this workload shape. TFP suits growing or spiky estates; an optimized flat estate kept the advantage under MLC.
Engineering moves came first so the renewal negotiated against the lowered baseline. The sequencing matters: a renewal signed before peak management locks the old peaks into the new term.
Because the ELA prices the baseline. Every MSU removed from the peak before signature compounds across the term, while the same MSU removed after signature saves nothing until the next renewal.
The program closed with a material double digit percentage reduction in annual mainframe software cost, a renewal priced on measured workload rather than assumed growth, and a standing peak management discipline owned by a named team.
Yes, wherever peaks are scheduling artifacts. The engagement file shows 10 to 25 percent MLC reductions from peak management alone, before any contract negotiation, in estates that had never run the analysis.
The standard advice is that mainframe software cost only falls when workload leaves the platform, so every business case becomes a migration case. We disagree. In roughly 10 to 15 mainframe reviews Morten Andersen advised in 2024 to 2025, peak management and reporting hygiene cut MLC charges 10 to 25 percent with zero migration risk, while the migration programs pitched against those estates carried multi year costs that dwarfed the savings. Migration can be right strategically, but as a cost lever it is the slowest and riskiest one available. The buyer side move is to manage the rolling four hour average first; it pays this year, not in five.
Three cuts of our advisory engagement file frame the size of the opportunity.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Five moves turn this analysis into a lower invoice on the next renewal.
White Paper · IBM
IBM Z Mainframe Licensing Negotiation
How to cut IBM Z mainframe cost: Tailored Fit Pricing, MLC and IPLA mechanics, MSU optimization, and the sub capacity levers that hold at renewal. Read it free.
MLC products price on the rolling four hour average MSU peak each month, so the highest sustained usage interval sets the bill. Managing that peak directly reduces cost.
Peak management cut MLC charges 10 to 25 percent without hardware or migration changes in the estates we reviewed, by rescheduling workloads and applying capacity caps.
Not always. TFP prices consumption and suits growing or spiky workloads, but a flat, well managed estate can price lower under optimized MLC, which is why modeling both before renewal matters.
Soft capping sets defined capacity limits on LPARs so the rolling four hour average cannot exceed the cap, holding the billable peak down where service levels allow it.
After peak optimization lowers the measured baseline, because the ELA prices that baseline across the whole term. Signing first locks the unoptimized peaks in.
The PVU, MLC, and ELA moves that cut IBM costs across mainframe and distributed estates.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The mainframe bill is set by a four hour window someone scheduled. Own the window and you own the bill.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Pricing moves, audit signals, and the levers that work. No vendor spin.
