Mainframe charges are not flat. They are a measured peak you control.
Monthly License Charges, MSU based pricing, IPLA, Tailored Fit Pricing, and sub capacity reporting. We read the actual peak, the contractual position, and the moves available to keep the bill under control.
Pay for the MSU peak you actually drove, not the box you bought.
IBM mainframe software is priced on Millions of Service Units (MSU), the IBM proprietary measure of LPAR processor capacity. For Monthly License Charge (MLC) products, the bill each month is computed from the four hour rolling average MSU peak in the prior month under the sub capacity reporting scheme. For IBM Program License Agreement (IPLA) products, the entitlement is acquired up front but the deployment is still measured in MSU and capped accordingly. Tailored Fit Pricing, where adopted, replaces the rolling peak with an annual MSU baseline at a fixed price.
The single largest lever on the mainframe bill is the four hour rolling average. Workload that drives the peak high once a month costs the same as workload that drives it high every day. Defensive capping, workload scheduling, and judicious use of zIIP and zAAP specialty engines all change the bill. The arithmetic is well understood. The execution depends on coordination between the systems programming team, the capacity team, and the finance team.
Our mainframe expertise is operational. We have run MSU peak reduction programmes, validated the SCRT submissions IBM uses to bill, sequenced Tailored Fit Pricing migrations, and rebuilt the contract position into the next IBM Z renewal. Read related work on the license consulting and negotiation pages.
What we read.
- Monthly License Charge (MLC) products and rates.
- IPLA entitlement and deployment.
- SCRT submissions and their accuracy.
- Defined Capacity, Group Capacity, and capping.
- zIIP and zAAP specialty engine offload.
- Tailored Fit Pricing baselines where adopted.
- Container Pricing and Application Development Solution.
How we approach mainframe cost reduction.
SCRT and four hour rolling peak read
Pull the last twelve months of Sub Capacity Reporting Tool submissions. Read the four hour rolling average peak per LPAR and per product. Identify the workloads driving the peak. Validate the SCRT accuracy.
Capping and workload placement
Model Defined Capacity and Group Capacity changes that reduce the peak without breaking the SLA on critical workloads. Identify workloads that can move to specialty engines. Quantify the MSU reduction and the dollar impact.
Tailored Fit Pricing analysis
Where TFP is on the table, build the case both ways. TFP removes the rolling peak pricing in exchange for a fixed annual baseline. The break even depends on workload growth and on the negotiated baseline. The decision is largely irreversible.
Contract and renewal position
Translate the operational position into the contract position for the next IBM Z renewal. Sequence the moves so the reduced peak carries into the negotiation. Hand over to the negotiation practice.
Common mainframe cost issues.
- Defined Capacity set too high relative to the actual workload peak.
- Batch windows scheduled within the same four hour window as online peak.
- Workloads eligible for zIIP not being routed to zIIP.
- SCRT submissions including LPARs that should be excluded.
- Tailored Fit Pricing baseline set without a credible growth model.
- IPLA products that have moved to MLC equivalents but the IPLA is still maintained.
What changes with TFP.
TFP replaces the rolling peak with a fixed annual baseline. Growth above the baseline is billed at a marginal MSU rate. The advantage is predictability and the removal of the peak management burden. The disadvantage is that the baseline once set is hard to renegotiate downwards. The break even depends on growth, on workload volatility, and on the discount achieved on the baseline. Most enterprises benefit from a careful baseline negotiation rather than a default acceptance.
- Workload Tailored Fit for product specific baselines.
- Software Consumption Solution for variable consumption.
- Development and Test Solution for non production use.
- New Application Solution for net new workloads.
How clients approach mainframe licensing.
Should we move to Tailored Fit Pricing?
The case is workload specific. Stable workloads with low growth often benefit. Highly variable workloads sometimes do not. The diagnostic models both positions over a five year horizon before recommending.
How much can we reduce MSU peak in practice?
Typical engagements identify five to fifteen percent peak reduction through capping and workload placement, without operational risk. Aggressive programmes that change scheduling can find more.
Are SCRT submissions audited?
IBM accepts SCRT as the basis for billing under the sub capacity scheme. IBM can and does review the submissions and the underlying LPAR data. The audit posture on mainframe is different from distributed but the same principles apply. See audit defense.
Do specialty engines really matter?
Yes. Workload routed to zIIP or zAAP is excluded from the MLC peak calculation. For DB2, Java, and certain other workloads the offload is material. The runtime and middleware configuration determines whether it happens.
What about Container Pricing?
Container Pricing applies to specific qualified workloads run inside a defined logical container on the LPAR. The MSU for that workload is priced separately from the general MSU peak. Eligibility and configuration are specific.
Resources
Expertise
Services
Need an independent read on this area?
A senior advisor responds within 24 hours and scopes a credible engagement structure within a week.
Get an independent read on this area of your IBM estate.
Tell us where you are in the cycle. A senior advisor will respond within 24 hours with a scoped engagement structure and an availability window. No sales call, no pitch deck. We do not resell IBM software. We have no IBM Business Partner status. Our recommendations are constrained only by what is good for the buyer.
Read more on why independence matters or browse the services overview for engagement structures.
Request a conversation
Corporate email required. Personal email addresses are not accepted.