$198.8M IBM claim, compressed to $12.4M.

The audit notice arrived in the second week of January. The IBM Software License Compliance team flagged a sub capacity continuity gap across the financial institution's WebSphere and MQ deployments. The customer commercial team initially treated the notice as a compliance exercise. Within ninety days, the audit firm had constructed an opening claim of one hundred and ninety eight point eight million dollars across Passport Advantage, sub capacity, and the middleware portfolio. The customer commercial team brought Redress in at week twelve.

The first observation was structural. The opening claim assumed full capacity entitlement across the entire WebSphere and MQ deployment because of intermittent ILMT continuity gaps over the prior twenty four months. The full capacity assumption inflated the entitlement requirement by an order of magnitude against the actual virtualised footprint. Read the 47 step checklist for the operating sequence we ran inside the engagement.

The position before Redress

The customer commercial team had been responding to the audit firm in good faith for ten weeks. Every data submission had reinforced the audit firm's framing. The customer team had not formally reserved rights in writing on any submission. The customer team had treated the ILMT continuity gap as a contractual default. The customer team had not reconstructed the deployment evidence independently. The customer team had been preparing to negotiate a payment plan against the opening claim.

The position carried three structural problems.

1. The ILMT continuity gap window did not span the full audit window. The defensible position was sub capacity for the periods of ILMT continuity, with a defensible position on the gap windows that did not require full capacity treatment.
2. The deployment evidence had been pulled from a single configuration management database extract. The extract did not reconcile against discovery tooling or the finance asset register. The cross check produced a meaningfully smaller deployment footprint than the audit firm had used.
3. No commercial track had been opened in parallel. The audit was running as a compliance exercise.

The audit firm opened on a 198 million dollar claim. Redress reconstructed the position. We closed at 12 million inside the renewal envelope. The audit was a renewal conversation in disguise.

The reconstruction

Redress opened the engagement with a written rights reservation against every prior data submission. The first ten days went into the position reconstruction. Read also the complete IBM audit playbook for the framework.

• ILMT history reconstruction. The continuity gap window was reconstructed against the server roster, the data collection logs, and the agent deployment timeline. The gap window narrowed to two discrete five week periods rather than the rolling exposure the audit firm had assumed.
• Deployment evidence reconciliation. The CMDB extract was reconciled against Flexera discovery, the IBM specific discovery agents, and the finance asset register. The reconciliation excluded decommissioned servers, development and test environments with separate entitlement, and disaster recovery servers carrying separate contractual language.
• Sub capacity calculation rebuild. The cluster level capping configuration was validated against the audit firm's calculation. The audit firm had assumed two hypervisor cluster boundaries that did not match the actual cluster configuration.
• Bundle hierarchy validation. The audit firm had misclassified four bundle relationships across WebSphere Application Server and the WebSphere Message Broker family. The misclassification inflated the PVU calculation by approximately thirty four percent.
• Cloud Pak entitlement layer. The customer had a current Cloud Pak for Integration entitlement that covered a portion of the disputed deployment. The audit firm had not credited the Cloud Pak entitlement against the WebSphere and MQ requirement.

The commercial conversation

Redress opened the commercial conversation in week ten of the engagement. The renewal envelope conversation moved to the front of the commercial track. The audit settlement was anchored on the renewal envelope rather than on the price book. Read the IBM ELA renewal service for the framework. The IBM account team had a deliverable economic incentive to compress the audit claim against renewal commitment, particularly with the Cloud Pak portfolio sitting inside the renewal envelope conversation.

The settlement closed at twelve point four million dollars across an extended renewal commitment. The audit closure language was negotiated into the renewal contract. The post audit baseline became the contractual baseline for the forward governance pattern. The customer commercial team moved into a quarterly governance cadence with the always on cover available through Vendor Shield.

The lessons

The financial institution's experience carries five lessons for any customer commercial team facing an IBM audit notice.

• Reserve rights from day one. Every data submission carries a written rights reservation. Without the reservation, the data submission becomes the contractual position.
• Reconstruct the position before any data conversation. The audit firm will reconstruct the position from your data. The customer commercial team has to reconstruct the position first.
• Open a commercial track in parallel. Every IBM audit ends in a settlement conversation. The settlement is a renewal conversation in disguise. Open the renewal envelope in parallel with the audit defense.
• Cross check the deployment evidence. A single CMDB extract is rarely the buyer side position. The cross check against discovery tooling, the finance asset register, and the entitlement library produces a defensible position.
• Forward governance prevents the cluster pattern. Audit cycles cluster. The post audit governance cadence prevents the next audit cycle from arriving with the same exposure. Read the Vendor Shield always on cover for the forward pattern.

If you have an IBM audit notice in flight, the audit defense engagement is the single highest yield investment you can make in the response. Read the 47 step checklist, the IBM audit defense guide, the IBM Knowledge Hub, the IBM Services, the IBM Advisory, and the US airline IBM audit case study for the cross sector benchmark. The blog and newsletter carry monthly IBM movement.