Midwestern robotics manufacturer. 87 percent of IBM audit exposure removed.

A Midwestern robotics manufacturer cut IBM audit exposure by 87 percent by rebuilding PVU and VPC counts from ILMT data and consolidated Passport Advantage entitlements.

What did IBM's audit claim assert?

The claim asserted material license exposure across the manufacturer's PVU and VPC licensed products, anchored on full capacity counting and an incomplete read of the entitlement record. The asserted number was the auditor's maximum, not a measured position.

Manufacturing estates invite this pattern: virtualized plants, mixed IT and operations technology, and ILMT coverage that stops at the data center boundary.

• Claim basis: full capacity PVU on virtualized hosts plus asserted VPC shortfalls.
• Entitlement read: the auditor's view missed trade ups and bundled rights.
• Pressure point: the claim arrived ahead of a renewal, as they usually do.

What did the deployment data actually show?

The rebuilt data showed an estate dramatically smaller than the claim. ILMT remediation and hypervisor log reconstruction established sub capacity positions, and the corrected VPC and PVU counting removed the structural multipliers from the auditor's arithmetic.

Where did the 87 percent reduction actually come from?

Roughly in thirds: sub capacity correction of the PVU base, measured VPC counts replacing peak assumptions, and entitlements the auditor's record had missed. No single argument carried it; the rebuilt dataset did.

How was the defense run from notice to settlement?

The defense controlled the data flow from day one. Scope was agreed in writing, raw data requests were answered with validated reports, and every assertion in the findings draft was tested against the rebuilt baseline before any commercial conversation began.

1. Acknowledge the notice and agree scope, products, and timeline in writing.
2. Stabilize ILMT and close agent coverage gaps immediately.
3. Rebuild deployment history from hypervisor and ILMT data.
4. Consolidate the Passport Advantage entitlement record.
5. Rebut the findings draft line by line, then negotiate the residual.

Why does controlling the data flow matter so much?

Because the auditor's model fills every gap with the most expensive assumption. Validated reports replace those assumptions with facts, and each replaced assumption takes a slice of the claim with it.

What should other IBM customers take from this case?

The settled outcome, 87 percent below the opening claim with the residual closed on renewal terms, is repeatable. It follows from sequence and evidence rather than negotiation heroics.

• Sequence: facts first, money second, renewal third and separate.
• Evidence: ILMT, hypervisor logs, and a consolidated entitlement baseline.
• Posture: treat the opening claim as an anchor to be dismantled, not a bill to be discounted.

Could the residual gap have been avoided too?

Mostly yes. The residual traced to genuine deployment ahead of entitlement in two product areas, the kind of drift a quarterly baseline review catches a year before any auditor does.

Where the common advice on IBM audit claims is wrong

The standard advice treats the IBM audit claim as a negotiation starting point, to be argued down by percentage in commercial talks. We disagree. In roughly 25 to 35 IBM engagements Morten Andersen advised in 2024 to 2025, claims collapsed 60 to 96 percent when the underlying data was rebuilt, against far shallower outcomes when customers negotiated the asserted number directly. The claim is not a price, it is a model output built on default assumptions. The buyer side move is to replace the assumptions with validated data and let the model recompute, because every fact inserted removes money no discount ever returns.

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 across IT and plant environments alike.
2. Reconstruct sub capacity positions from hypervisor data now, not under audit.
3. Consolidate Passport Advantage records into one entitlement baseline.
4. Agree audit scope in writing before sharing any data.
5. Answer data requests with validated reports, never raw exports.
6. Keep settlement and renewal negotiations in separate channels.

White Paper · IBM

IBM Audit Defense Guide

The buyer side framework we use with Fortune 500 clients defending IBM software audits. Read it free.

Read the white paper

Frequently asked questions

How did the robotics manufacturer cut IBM audit exposure by 87 percent?

By rebuilding PVU and VPC counts from ILMT and hypervisor data and netting them against a consolidated entitlement baseline. The corrected dataset removed the full capacity and peak assumptions the claim was priced on.

What is the difference between PVU and VPC licensing?

PVU licenses processor value units tied to core counts and processor types, while VPC licenses virtual processor cores, common in container and cloud pak deployments. Both reward accurate measurement and punish defaults.

Why was the opening IBM claim so much higher than the settlement?

Because audit models fill data gaps with maximum assumptions: full capacity, peak counts, and partial entitlement records. Closing the gaps recomputed the claim 87 percent lower.

Did the manufacturer pay anything at settlement?

A residual tied to genuine deployment ahead of entitlement in two areas, closed on renewal terms rather than as a back bill. The remaining 87 percent of the assertion did not survive the evidence.

How can manufacturers reduce IBM audit risk in advance?

Extend ILMT discipline across plant and IT environments, keep quarterly sub capacity reports, and maintain a consolidated entitlement baseline. Estates with those controls settle audits fast and small.