UK Mining Group. IBM audit closed at sub capacity.

A UK mining group faced an IBM audit claim anchored at full capacity PVU. ILMT remediation and a sub capacity defense closed it for a fraction of the opening number.

Why did IBM audit the UK mining group?

IBM audited the group because its virtualized Db2 and WebSphere estate had grown for years without consistent ILMT reporting, which is exactly the profile the publisher targets. The estate spanned IBM Db2, WebSphere, and Maximo across UK operations with roughly fifteen thousand employees.

IBM's sub capacity licensing terms make eligibility conditional: deploy and maintain ILMT, retain quarterly reports, or default to full capacity licensing of every physical core under the virtualization layer.

• Audit trigger: stale ILMT reporting across a growing VMware cluster estate.
• Publisher position: full capacity PVU on every host in each cluster running IBM software.
• Customer reality: actual sub capacity use was a small share of the asserted core base.

What did the audit data actually show?

The audit data showed a compliant runtime footprint hidden under a reporting failure, not real overdeployment. Rebuilding the deployment picture from hypervisor data and ILMT scans cut the licensable base dramatically.

Why does the full capacity default matter so much?

Because it licenses hardware you never used. In a dense cluster, full capacity counting can multiply the PVU base by the ratio of physical cores to allocated virtual cores, and that ratio is the entire audit claim.

How was the IBM audit claim defended?

The defense rebuilt the facts before negotiating the money. ILMT was redeployed and configured correctly, historical hypervisor logs reconstructed the true high water marks, and the Passport Advantage entitlement record was consolidated into a single baseline.

1. Stabilize ILMT and verify agent coverage across every host running IBM software.
2. Reconstruct historical allocation from hypervisor data to evidence the sub capacity position.
3. Rebuild entitlements from Passport Advantage records, including unused trade up rights.
4. Contest retroactive full capacity billing as disproportionate to a curable reporting gap.
5. Negotiate closure tied to a forward compliance plan rather than a backdated invoice.

What role did ILMT remediation play in the settlement?

It converted the dispute from a contractual default into a curable process gap. With ILMT live and generating clean quarterly reports, IBM's incentive shifted from maximizing the back claim to securing the renewal relationship.

What was the commercial outcome for the mining group?

The audit closed at a small fraction of the opening claim, with sub capacity eligibility preserved going forward. The group avoided both a forced enterprise agreement and retroactive full capacity fees, and kept its renewal calendar on its own terms.

• Claim reduction: the settled number landed more than 90 percent below the opening position.
• No forced bundle: the group declined the broad agreement IBM positioned as the settlement vehicle.
• Forward posture: quarterly ILMT reporting now runs as a standing control with named ownership.

Could the audit have been avoided entirely?

Probably not the audit letter, but certainly the exposure. A standing ILMT control with quarterly review would have left the auditor nothing to anchor on, and the engagement file shows estates with that discipline settle fast and small.

Where the common advice on IBM audit settlements is wrong

The standard advice is to settle an IBM audit quickly by rolling the claim into a bigger ELA, because the discount optics look good and the dispute disappears. We disagree. In roughly 25 to 35 IBM engagements Morten Andersen advised in 2024 to 2025, customers who rebuilt the deployment and entitlement facts first closed 60 to 96 percent below the opening claim, while customers who went straight to the bundle conversation paid for the claim twice: once in the settlement and again in years of inflated subscription baseline. The buyer side move is to fix ILMT, rebuild the baseline, and only then talk commercial structure.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Verify ILMT agent coverage on every host running IBM software this quarter.
2. Archive quarterly ILMT reports with named ownership and a review step.
3. Rebuild your Passport Advantage entitlement baseline before any audit letter arrives.
4. Map every IBM product to its metric and its cluster placement.
5. Treat any ILMT gap as an urgent fix, not a backlog item.
6. If a notice arrives, control the data flow before discussing money.

White Paper · IBM

Defend an IBM Audit: The Full Buyer Side Playbook

Defend an IBM audit end to end: triage the claim, fix ILMT gaps, sample sub capacity, and turn a bad finding into a renewal you control. Read it free.

Read the white paper

Frequently asked questions

What triggered the IBM audit at the UK mining group?

Stale ILMT reporting across a growing virtualized estate triggered it. Sub capacity eligibility depends on continuous ILMT operation, and the gap let the auditor assert full capacity PVU licensing.

How much of the IBM audit claim was reduced?

More than 90 percent of the opening claim was removed. The settled figure reflected actual sub capacity deployment against a consolidated entitlement baseline rather than full capacity defaults.

What is the difference between full capacity and sub capacity PVU licensing?

Full capacity licenses every activated physical core in the server or cluster, while sub capacity licenses only the cores allocated to the virtual machines running the software. ILMT compliance is the condition for the cheaper sub capacity basis.

Does fixing ILMT after an audit notice still help?

Yes. Remediating ILMT during the audit converts a contractual default into a curable gap, supports a retroactive evidence argument, and shifts the negotiation toward a forward compliance plan.

Did the mining group have to sign a new IBM ELA to settle?

No. The audit closed as a standalone settlement at a fraction of the claim, and the group kept its renewal negotiation separate from the audit resolution.