① Guide · Modernization
Modernization lowers your MIPS and MSU footprint. It does not lower your bill, because the contract decides whether a falling footprint reaches the invoice. This guide is the five step sequence that turns engineering work into licensing savings rather than capacity you still pay for.
Cutting MIPS is the engineering win. Cutting the bill is the contract win. They are not the same project.
Modernization programs, whether offloading workload to zIIP, moving batch and analytics to distributed or cloud platforms, refactoring inefficient code, or retiring applications, reliably reduce the capacity a mainframe estate consumes. Teams commonly report meaningful MIPS reduction and lower operational cost. The problem buyers hit is that the licensing contract does not automatically follow the workload. If committed capacity is locked at a peak baseline, or the multi year term has no flex down right, the footprint falls while the invoice holds. The saving was real on the floor and invisible on the bill.
The license position is the bridge between the two. Before, during, and after a modernization program you have to manage what you are committed to pay, not just what you consume, so that every MIPS removed has a contractual path to the bottom line. That means timing your renewal against the program, writing reduction rights into the contract, and being deliberate about specialty engine offload. For the mechanics see mainframe cost optimization and MSU optimization, and for the offload detail, zIIP engines and software cost offload.
Translate the modernization roadmap into its effect on the billing metric, MSU or MIPS per product, not just on infrastructure. Offloading a batch suite to zIIP, retiring an application, or moving analytics off platform each changes the capacity that specific products are charged on. Knowing which products lose chargeable capacity, and when, is the foundation for every contract move that follows.
The worst sequence is to renew at peak capacity just before the program takes the footprint down, locking the vendor's best year as your baseline. Where you can, align the renewal to land after the reduction shows in your SCRT and R4HA data, so you negotiate against the lower real number rather than the historical peak. Timing alone often moves the renewal more than any rate argument.
A flex down or capacity reduction right is what lets a falling footprint reach the invoice. Without it, modernization lowers usage while the committed baseline keeps charging. Negotiate the right to reduce committed capacity as the estate shrinks, and the right to drop products you retire, so the contract tracks the program instead of freezing it.
Specialty engine offload to zIIP and sub-capacity reporting genuinely lower software charges, but the saving depends on how each product is licensed and measured. Some charges follow general purpose MSU and fall with offload; others do not. Model the offload product by product before you assume a saving, and confirm the sub-capacity reporting is capturing the reduction.
A lower footprint is only a durable saving if the next renewal does not quietly re-baseline it upward. Keep the license position current as the program runs, validate consumption independently, and carry the reduced number into each cycle. When a renewal lands under 18 months out mid program, we compress the work and mobilize within 48 hours.
| Modernization move | Why the saving can stall | What captures it |
|---|---|---|
| zIIP offload | Charge may not follow general purpose MSU | Model per product; confirm sub-capacity reporting |
| Application retirement | No right to drop the product from the deal | Drop right written into the contract |
| Workload moved off platform | Committed capacity locked at peak | Flex down or capacity reduction right |
| Code refactoring | Renewal timed before the reduction shows | Align renewal to post reduction SCRT data |
| Consolidation | Next renewal re-baselines upward | Carry the lower number through each cycle |
Reduction and offload outcomes vary by product, metric, and contract. Figures and behavior here are pattern level; model your own estate and validate against your SCRT and R4HA data.
Audit notice or renewal under 18 months out? We mobilize within 48 hours. Modernizing into a renewal window? Get the license position right before the program lands.
Make every MIPS you remove a line the vendor has to credit.