① Guide · insurance estates
Insurance mainframe estates share a profile: deep IBM Db2 and IMS under policy and claims, Adabas and Natural legacy beneath older administration systems, and a cost curve driven by overnight and quarter end batch peaks. Those peaks, not the average, set the MLC. Here is the licensing pattern, where it bites, and the levers that move it.
The peak is monthly. The charge is for the month.
Insurance is among the most batch intensive industries on the mainframe. Premium calculation, policy renewal cycles, claims settlement, regulatory reporting, and actuarial modeling concentrate large amounts of work into narrow overnight and quarter end windows. Because IBM sub-capacity monthly license charges bill on the rolling 4 hour average, the highest sustained four hour MSU window in the month, a single overnight batch run that overlaps the online day can set the charge for thirty days. The cost is driven by when the work runs as much as by how much there is.
On top of that consumption profile sits a multi vendor contract estate. Core processing leans on the IBM stack, but many insurers also carry Adabas and Natural from Software AG under long lived policy administration systems, plus security, scheduling, output, and sort tooling from Broadcom (CA) and BMC. An insurer is therefore usually negotiating several agreements on several metrics at once, which is both a complication and, handled well, a source of leverage.
| Function | Common products | Licensing pressure |
|---|---|---|
| Core policy and claims | IBM z/OS, CICS, Db2 for z/OS, IMS | Sub-capacity MLC on the R4HA peak; the largest line. |
| Legacy administration | Software AG Adabas and Natural | Audit exposure on older contracts; entitlement drift. |
| Security | Broadcom (CA) ACF2 or Top Secret, or IBM RACF | Capacity priced; switching cost very high. |
| Scheduling and output | CA 7, Control-M, CA View, output management | Bundled into portfolio deals; co-term repricing risk. |
| Batch and data utilities | DFSORT or Syncsort (Precisely) MFX, Db2 tools | Capacity priced; zIIP offload can reduce MLC. |
A composite pattern, not any one insurer. Estates vary widely, but the batch driven MLC peak and the multi vendor mix are near universal. Confirm your own product owners and metrics before modeling.
Shape the consumption first. Then negotiate the contract.
For most insurance estates the largest single lever is the batch peak. Rescheduling heavy overnight and quarter end runs out of the online prime window, soft capping to hold the billable peak, and moving eligible Db2 and Java work to zIIP engines all reduce the rolling 4 hour average that sets the MLC, with no application changed. Because insurance peaks are predictable, monthly cycles and quarter end concentrations, they are unusually amenable to this discipline. That is the work in our MSU optimization and cost optimization practice.
On the contract side, the recurring theme is Adabas and Natural. Long lived insurance policy systems often carry legacy Software AG agreements where deployed use has drifted from entitlement, which is exactly the gap an audit looks for. Validating that position before a notice arrives, rather than after, is the difference between a managed renewal and a defended audit. Across the rest of the estate, the multi vendor mix becomes leverage when renewals are timed and a credible alternative is prepared, which is the core of our license negotiation work.
④ What changes with us in the room
The overnight run sets the bill. We reshape the run.
Typical renewal reduction we negotiate
Engagements delivered since 2019
Mainframe spend negotiated on the buyer side
Because insurance is batch heavy and MLC bills on the rolling 4 hour average peak, not total work. Overnight renewals, premium runs, claims settlement, and actuarial jobs concentrate MSU into narrow windows, and when batch overlaps the online day the four hour peak that sets the month's charge is inflated by work that runs only briefly.
The IBM stack of z/OS, CICS, Db2 for z/OS, and often IMS carries core processing, concentrating spend in sub-capacity MLC. Many insurers also run Adabas and Natural from Software AG under legacy administration systems. Around that sit security, output, scheduling, and sort tooling from Broadcom (CA) and BMC, so several metrics are in play at once.
Shape the batch peak first: reschedule heavy runs, soft cap to hold the billable peak, and move eligible work to zIIP. Then validate Adabas and Natural entitlement before any audit, consolidate the multi vendor footprint where it adds volume without removing alternatives, and time renewals so the walk away is built first. Consumption first, contract second.
Long lived insurance policy systems often carry legacy Software AG agreements where deployed use has drifted from entitlement, the exact gap an audit targets. Validate that position before a notice arrives, not after. See what auditors test and the Software AG hub.
Related: IBM licensing hub · MSU optimization service · IBM MLC cost reduction · mainframe licensing in logistics
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →