① Guide · logistics estates
Logistics and transportation mainframe estates are transaction heavy and seasonal: real time tracking and order processing on IBM CICS and IMS, EDI around the edges, and a cost curve anchored to a few weeks of peak shipping. The surge sets the MLC. Here is the licensing pattern, where it bites, and the levers that move it.
A few weeks of surge set the whole year's run rate.
Logistics is a transaction driven industry. Shipment tracking, order capture, rating, and routing run as high volume online workloads, and the volume rises and falls with the calendar: holiday peaks, promotional events, and seasonal shipping surges. Because IBM sub-capacity monthly license charges bill on the rolling 4 hour average, the highest sustained four hour MSU window in the month, the surge weeks can set the MLC even though the rest of the year runs well below that level. The cost curve is anchored to the peak, not the average.
That makes logistics estates different from batch heavy industries. The pressure is online and seasonal rather than overnight and monthly, which changes which levers matter. Capacity has to be there for the surge, so the question is not whether to run the peak but how to keep the peak from pricing the whole year, and how to structure the contract so a predictable seasonal spike is not treated as permanent growth.
| Function | Common products | Licensing pressure |
|---|---|---|
| Tracking and order processing | IBM z/OS, CICS, IMS, Db2 for z/OS | Sub-capacity MLC on the seasonal R4HA peak. |
| EDI and integration | Connectivity and messaging, IBM MQ | Volume scales with partners and shipment counts. |
| Scheduling | CA 7, Control-M | Bundled into portfolio deals; co-term repricing risk. |
| High volume data movement | DFSORT or Syncsort (Precisely) MFX | Capacity priced; zIIP offload can reduce MLC. |
| Security | Broadcom (CA) ACF2 or Top Secret, or IBM RACF | Capacity priced; switching cost very high. |
A composite pattern, not any one carrier or 3PL. The transaction driven, seasonal MLC peak is the defining trait. Confirm your own product owners and metrics before modeling a renewal.
Manage the surge, not the average.
For most logistics estates the leading lever is the seasonal peak. Capacity planning that anticipates the surge, soft capping that holds the billable peak where service levels allow, moving eligible work to zIIP engines outside MLC, and shaping any batch that overlaps the online peak all reduce the rolling 4 hour average that sets the charge. The aim is not to throttle the business during its most important weeks but to keep a few weeks of necessary surge from pricing the entire year. That is the focus of our MSU optimization and cost optimization work.
On the contract side, the structure has to fit a spiky profile. A pricing model built for flat, predictable consumption can penalize a seasonal estate, so the levers are choosing the model deliberately, securing terms that do not treat a predictable surge as permanent growth, and timing renewals away from peak season, when the business cannot risk disruption and the vendor knows it holds the clock. Building the credible alternative and the renewal calendar ahead of the surge is the core of our license negotiation work.
④ What changes with us in the room
Peak season sets the year's bill. We keep the surge from staying.
Typical renewal reduction we negotiate
Engagements delivered since 2019
Mainframe spend negotiated on the buyer side
Because volume is seasonal and MLC bills on the rolling 4 hour average peak. Holiday surges and peak shipping push transaction processing above baseline, and the highest four hour MSU window during the surge can set the MLC for the month even though the rest of the year runs lower. The cost curve is anchored to a few weeks.
It is transaction heavy rather than batch heavy. The IBM stack of z/OS, CICS, and often IMS and Db2 for z/OS carries tracking, order processing, and rating. Around the core sit EDI and integration, scheduling, sort utilities, and security. Uptime during peak makes core switching costs high, so leverage comes from capacity discipline and renewal timing.
Manage the seasonal peak, not the average. Capacity planning for the surge, soft capping where service levels allow, zIIP offload, and shaping overlapping batch all hold the rolling 4 hour average down. On the contract side, choose a pricing model that suits a spiky profile and time renewals away from peak season. See IBM MLC cost reduction.
Away from peak season. During the surge the business cannot risk disruption and the vendor knows it controls the clock, which weakens the buyer position. Build the alternative and the renewal calendar ahead of the surge so the negotiation happens when you hold leverage. See the 18 month renewal runway.
Related: IBM licensing hub · cost optimization service · mainframe licensing in insurance · the 18 month renewal runway
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →