① IBM · cost optimization
The IBM bill is the largest line on most mainframe budgets, and the most mechanical. It is calculated from metrics you can measure, manage and dispute: R4HA peaks, sub capacity reports, TFP baselines, IPLA entitlements. We optimize all four, then lock the gains into the agreement.
48 hour mobilization Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →IBM mainframe software spend typically grows without anyone deciding to grow it. MLC products such as z/OS, CICS, Db2 for z/OS, IMS and MQ bill on the monthly peak of the rolling four hour average (R4HA), reported through SCRT under sub capacity rules. A single badly scheduled batch window sets the month's bill. A hardware refresh changes the capacity rating underneath the price. MIPS creep does the rest.
On top of the metered stack sits the commercial layer: IPLA one time charge products with subscription and support renewing every year whether used or not, and increasingly a Tailored Fit Pricing commitment whose baseline was set from a historical high. Each layer is optimizable. Together they are where 20 to 35 percent typically hides.
Four levers, worked in order
IBM's pricing teams work from your reported consumption and their own benchmarks. We bring the counterweight: independently validated consumption data, market benchmarks from comparable estates, and the technical plan that makes a lower baseline credible rather than aspirational. The conversation shifts from "what discount can we get" to "what number is this estate actually obligated to pay", which is a different negotiation.
Across 500+ engagements and $180M+ in negotiated mainframe spend, the typical outcome on addressable renewal spend is a 20 to 35 percent reduction, with the technical gains compounding every month after signature.
20 to 35 percent on addressable renewal spend is the typical outcome across our engagements, from a mix of commercial work and technical work that lowers the metered base itself.
The monthly R4HA peak per LPAR, reported through SCRT under sub capacity licensing. The bill follows the peak, not the average. See the R4HA explained and SCRT explained.
Sometimes. TFP trades R4HA mechanics for a committed baseline with discounted growth. Steady growth estates can do well; declining or spiky estates can overcommit. The baseline and the entry and exit terms decide it, and both are negotiable. See TFP explained.
Usually not. Scheduling, capping, WLM policy and zIIP offload deliver most of the technical gains. Application rewrites are a last resort, not a first step.
Twelve months of SCRT reports, the current agreements and entitlements, and SMF data for the peak windows. A defensible savings case typically takes weeks, not months.
The technical sibling of this page: the consumption levers in depth.
Optimization sets the number; the renewal locks it in. Timing both is the strategy.
The step by step guide to cutting the metered bill while running the same work.
How specialty engines take eligible work off the MLC meter.