Midwestern robotics group. IBM audit exposure cut 91 percent.

How a Midwestern robotics group cut an acquisition triggered IBM audit claim by 91 percent: cluster separation, timeline reconstruction, and a forward structured settlement.

What was the situation at this robotics group?

The client is a Midwestern industrial robotics group running IBM middleware and integration software across a virtualized estate spanning two manufacturing campuses and an acquired controls business. The IBM audit letter arrived eighteen months after that acquisition closed.

The audit found what the integration never inventoried: IBM products from the acquired entity running on shared VMware clusters, with ILMT coverage gaps across exactly those hosts. The opening claim priced the shared clusters at full capacity.

Why the exposure looked severe

• Cluster contamination: acquired workloads landed on the group's largest clusters, dragging every host into the claim.
• Evidence gap: the acquired entity had never run ILMT; the group's own coverage stopped at the legacy estate boundary.
• Back maintenance: the claim stacked support charges back to the acquisition date.

How was the defense run?

The defense followed the standard sequence: scope control, evidence rebuild, written contest, commercial close, compressed into seven months. The acquisition timeline became the backbone of the time base argument.

The evidence rebuild

1. Host mapping: every IBM instance mapped to its actual VMs and hosts from vSphere vCenter records, separating acquired workloads from legacy ones.
2. Timeline reconstruction: deployment dates anchored to the acquisition close, cutting the back maintenance window the claim assumed.
3. Sub capacity restoration: partial ILMT data plus hypervisor records rebuilt the eligible count under the IBM sub capacity rules and the License Metric Tool documentation.

The written contest

The counter position contested the metric base and the time base in writing, with the Passport Advantage terms as the reference frame. A genuine shortfall in the acquired estate was acknowledged early and priced at commercial rates rather than list.

Where the common advice on acquisition audits is wrong

The standard advice after an acquisition triggered audit is to settle quickly and absorb the cost as a deal expense. We disagree. In roughly 18 of the 15 to 25 IBM matters we worked in 2024 to 2025, the acquired estate's claim collapsed the same way every IBM claim collapses: on the metric and time layers. The buyer side move is to treat the acquisition date as evidence, not liability; it caps the back maintenance window and isolates the contaminated clusters. Speed matters less than the rebuilt deployment record.

The audit followed the acquisition because that is when audits come. The defense won because the deployment record, once rebuilt, was better than the auditor's model.

What were the results and the lessons?

The matter settled at a 91 percent reduction against the opening claim, structured as a forward license purchase covering the genuine acquired estate gap, with back maintenance waived and full release on the audited period.

• Cluster hygiene: IBM workloads were consolidated onto dedicated hosts, shrinking future countable capacity.
• ILMT extended: coverage now spans the full group including acquisitions, with quarterly report archiving.
• M&A checklist: license inventory is now a diligence item before close, not an audit finding after.

What transfers to other manufacturers

Three controls: a named license owner for the IBM estate, ILMT validated quarterly, and a license inventory in every acquisition diligence pack. Estates with those three rarely see claims of this shape.

What to do next

1. Name an owner for IBM entitlements and deployment records.
2. Validate ILMT coverage across the whole estate, including acquired entities.
3. Consolidate IBM workloads onto dedicated hosts where practical.
4. Add license inventory to the M&A diligence checklist.
5. If a letter lands, confirm scope in writing and start the evidence rebuild immediately.
6. Acknowledge genuine gaps early and structure settlement as forward spend.

The full defense sequence is in the IBM audit settlement playbook, and the IBM practice runs the engagement end to end. More matters like this one are in the case study library.

Frequently asked questions

How did the robotics group cut the IBM claim by 91 percent?

By rebuilding the deployment record from vCenter and partial ILMT data, separating acquired workloads from legacy clusters, anchoring the timeline to the acquisition close, and settling the genuine gap as a forward purchase at commercial rates.

Why did the audit arrive after the acquisition?

Acquisitions are a standard audit trigger. They import unlicensed deployments, disturb entitlement records, and signal budget for settlement. The letter landing within two years of close is the pattern, not the exception.

What made the shared clusters so expensive in the claim?

Full capacity counting. With ILMT contested on those hosts, every core in each shared cluster counted, even where the IBM products ran on a few VMs. Cluster separation and rebuilt evidence collapsed that base.

Did the group pay anything?

Yes. A genuine shortfall in the acquired estate was acknowledged early and settled as a forward license purchase at negotiated rates with back maintenance waived, a fraction of the opening claim.

How do you prevent acquisition triggered audits?

Put license inventory in the diligence pack, extend ILMT to acquired entities before workloads move, and keep acquired IBM products off shared clusters until entitlements are confirmed.