① Guide · IBM contract consolidation
IBM Monthly License Charge bills usage every month. International Program License Agreement is bought once and supported annually. Consolidating them can save real money, or quietly lock you in for years. Here is the line between the two.
Aligning dates is easy. Aligning them in your favor is the work.
A large IBM estate is rarely one contract. It is Monthly License Charge (MLC) on the core stack, z/OS, CICS Transaction Server, Db2 for z/OS, IMS, and MQ, billed monthly on the rolling 4 hour average MSU peak, plus a layer of International Program License Agreement (IPLA) tools bought for a one time charge with recurring Subscription and Support. Years of separate purchases leave staggered co termination dates, mismatched discounts, and overlapping entitlements that nobody has reconciled.
Consolidation is attractive because it turns a stream of small renewals the vendor handles one at a time into a single negotiation event with volume leverage. Done right, it aligns dates, surfaces duplicate and shelfware entitlements, and lets you negotiate once, well, instead of many times, blind. Done wrong, the same alignment becomes the vendor's tool: everything co terminated onto a longer agreement that bakes in MLC growth assumptions and trades away IPLA flexibility.
| Dimension | MLC (Monthly License Charge) | IPLA (one time charge) |
|---|---|---|
| Charge logic | Recurring, monthly, usage based. | Perpetual, bought once, plus annual S&S. |
| Metric | Rolling 4 hour average MSU peak, via SCRT. | Capacity tier at purchase (often MSU based). |
| Typical products | z/OS, CICS, Db2, IMS, MQ. | Tools and utilities, many sub-capacity IPLA. |
| Budget shape | Variable, tracks the monthly peak. | Capital up front, predictable annual S&S. |
| Main lever | Shape the R4HA peak; pick the pricing model. | Right size capacity; review S&S on static tools. |
| Consolidation risk | Longer term locks in growth assumptions. | Lapsed S&S can be costly to reinstate. |
Structures and metrics described as commonly observed under current IBM terms. Specific entitlements vary by agreement, which is why consolidation starts from your own contract inventory.
Every MLC product, every IPLA license, every S&S stream, every co termination date, in one map. Duplicate entitlements, shelfware, and lapsed coverage all surface here, before any consolidation is proposed.
You cannot align what you cannot see.
Alignment that shortens exposure and preserves your best inherited terms is pursued. Alignment that extends term length or folds good entitlements into a worse template is refused. The two look identical on a vendor proposal until you read the term.
Same word, opposite outcome.
A single consolidated event carries volume leverage a stream of small renewals never does. The MLC run rate, the IPLA capacity, and the S&S streams are negotiated together, with the credible alternative built in parallel.
One informed negotiation beats ten blind ones.
Caps on MLC growth, capacity right sizing on IPLA, S&S decisions on static products, and exit rights all go into the consolidated agreement, so the structure protects you for its full term rather than just at signature.
Price fades; the clauses stay.
④ What changes with us in the room
The vendor prefers your contracts scattered. We bring them into one view.
Typical renewal reduction
Engagements delivered since 2019
Mainframe spend negotiated on the buyer side
They bill on opposite logic. MLC is a recurring usage charge on core software, driven by the monthly rolling 4 hour average MSU peak. IPLA is a perpetual license bought for a one time charge, with optional recurring Subscription and Support, common for tools and utilities. MLC tracks usage monthly; IPLA is owned once and supported annually.
Large estates accumulate dozens of agreements with staggered dates, mismatched discounts, and overlapping entitlements. Consolidation aligns dates, surfaces duplicates and shelfware, and creates one negotiation with volume leverage instead of a stream of small renewals the vendor handles separately. One informed negotiation, not many blind ones.
When alignment extends term length or folds favorable legacy terms into a worse template. A vendor will co terminate everything onto a longer agreement that locks in MLC growth or trades away IPLA flexibility. Consolidation should shorten exposure and preserve your best inherited terms, not bundle good and bad into one long commitment.
Sometimes, on stable products you do not need updates for, but with consequences. Dropping S&S stops maintenance and can make later reinstatement costly, and on some products lapsed support cannot be repurchased at the old rate. A legitimate lever for genuinely static tools, after mapping which products are frozen and which still need current fixes.
Related: IBM licensing hub · IBM contract review · MLC cost reduction · cost optimization service
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →