IBM Audit Defence: Midwestern Robotics Manufacturer Reduces $22.3M Claim by 93%

Client Profile and IBM Deployment Context

The client is an industrial robotics and automation systems manufacturer headquartered in Ohio, supplying robotic assembly lines, automated quality inspection systems, and factory control software to automotive, aerospace, and consumer goods manufacturers across North America. With approximately 3,800 employees and annual revenues exceeding $1.2 billion, the company runs a capital-intensive IT infrastructure that supports both its internal operations and the software-defined elements of the industrial systems it sells to customers.

The IBM product estate included IBM Maximo Asset Management (used for internal maintenance and asset lifecycle management across nine manufacturing facilities), IBM MQ and IBM Db2 supporting the factory control integration layer, and a more recently deployed IBM Cloud Pak for Integration, which the company had adopted in 2021 to modernise its EDI and supplier communication infrastructure using containerised IBM integration components on a Red Hat OpenShift cluster.

The company had also separately purchased Red Hat OpenShift Container Platform licences in 2020 to underpin a broader factory automation software modernisation project predating the Cloud Pak adoption. This pre-existing OpenShift licence was the seed of the most complex and most valuable audit defence challenge in this engagement.

IBM's Three-Part Claim Architecture

IBM's audit notice arrived in August 2022 and covered the period from January 2019 through December 2022. IBM's preliminary findings, delivered after a 90-day data collection period that we managed carefully, were structured around three distinct claim categories totalling $22.3 million.

Claim 1: Cloud Pak OpenShift Double-Licensing ($9.8 Million)

IBM's largest claim element asserted that the company required full, unrestricted Red Hat OpenShift Container Platform licences for all cluster nodes used in any capacity by the Cloud Pak for Integration deployment. IBM's auditors had observed that the OpenShift cluster hosting the Cloud Pak for Integration also carried non-Cloud Pak workloads — specifically, a set of factory automation microservices developed internally by the company's software engineering team.

IBM's assertion was that because the cluster hosted workloads beyond the Cloud Pak's restricted-use boundary, the restricted-use OpenShift entitlement bundled within the Cloud Pak for Integration was voided across the entire cluster. IBM then counted the cluster's full node capacity as requiring separately purchased full OpenShift entitlements, at a cost of $9.8 million for the audit period.

This is the single most common Cloud Pak licensing trap that IBM exploits in audits. IBM Cloud Paks include a restricted-use OpenShift licence that covers nodes exclusively running Cloud Pak workloads. The moment a non-Cloud Pak workload is placed on those nodes — even a small, low-resource internal application — IBM claims that the restricted-use entitlement is invalidated for the entire cluster.

Claim 2: IBM Maximo ILMT Coverage Gaps ($7.4 Million)

IBM identified ILMT coverage gaps across 22 servers in three manufacturing facilities that had undergone infrastructure upgrades between 2020 and 2021. The facilities in question had migrated from legacy bare-metal servers to a VMware virtualised environment as part of a factory modernisation programme. During the VMware deployment, ILMT agents had not been installed on the new virtual machines for a period ranging from four to nine months per facility.

IBM used these ILMT gaps to assert full-capacity PVU pricing for IBM Maximo across the affected facilities for the entire gap period. The full-capacity PVU calculation, applied to the largest available physical server in each facility, produced a claimed shortfall of $7.4 million for the sub-capacity rights IBM argued had been forfeited.

Claim 3: IBM Maximo Deployment Scope Interpretation ($5.1 Million)

The third claim element was more contentious. IBM's auditors asserted that certain IBM Maximo modules deployed at the company's customer-facing service depot — where the company provides maintenance and repair services for robotic systems it had sold to customers — required additional Authorised User licences beyond the company's existing Maximo entitlement.

IBM's argument was that the service depot technicians accessing Maximo to manage customer equipment maintenance records were "external users" not covered by the company's internal Authorised User entitlement. IBM's interpretation of the Maximo licence terms, if accepted, would have required a separate external Authorised User class of licence for the 340 depot technicians.

Defence Phase 1: Dismantling the Cloud Pak Double-Licensing Claim

The Cloud Pak OpenShift double-licensing claim was the highest-value and most technically complex element to challenge. The defence strategy had two components: a factual challenge to IBM's characterisation of the cluster workload separation, and a contractual challenge to IBM's interpretation of the restricted-use boundary.

The factual challenge involved a detailed analysis of the OpenShift cluster architecture. Our review found that while the factory automation microservices did run on the same OpenShift cluster, they ran on a physically separate set of worker nodes that had been deliberately allocated to non-Cloud Pak workloads at the time the cluster was designed. The Cloud Pak for Integration workloads ran on a separate node pool within the same cluster.

IBM's restricted-use licence documentation references workload separation at the node level. Workloads running on physically separate worker nodes — even within the same cluster — can be treated as separate licensing domains for the purposes of the Cloud Pak restricted-use boundary. We presented IBM with the OpenShift cluster configuration documentation, node pool allocation records, and IBM License Service reports demonstrating that the Cloud Pak workloads had never consumed capacity from the non-Cloud Pak node pool.

IBM initially resisted this interpretation but accepted it after we submitted a formal written position with supporting OpenShift architecture documentation. The $9.8 million Cloud Pak double-licensing claim was withdrawn entirely. IBM retained a smaller claim related to a brief period early in the cluster deployment when node pool separation had not yet been fully implemented, which we negotiated to $180,000 — a 98% reduction on that specific claim element.

Defence Phase 2: ILMT Gap Challenge for IBM Maximo

The ILMT gap defence followed the same pattern as the Florida logistics engagement. The 22 servers affected were all newly provisioned VMware virtual machines that had entered production without ILMT agents as a result of an oversight in the virtualisation migration checklist. For each server and each gap period, we gathered vCenter performance data, VMware vSphere allocation records, and Maximo application logs demonstrating actual resource consumption.

The evidence demonstrated that none of the affected servers were running Maximo at full-capacity utilisation during the gap period. The Maximo application was running on VMs allocated between four and eight virtual CPUs each, on physical hosts with 32 to 40 cores. The actual sub-capacity PVU requirement for the gap period, calculated using the vCenter telemetry and IBM's PVU table, was approximately $1.1 million — compared to IBM's full-capacity assertion of $7.4 million.

IBM accepted the vCenter evidence for 18 of the 22 servers as adequate to support sub-capacity treatment. For the remaining four servers where vCenter performance data was incomplete due to a storage system migration during the gap period, IBM agreed to apply a negotiated blended rate rather than full-capacity pricing. The final agreed amount for the ILMT gap was $890,000, compared to IBM's claim of $7.4 million.

Defence Phase 3: Maximo Authorised User Scope Challenge

The Maximo external Authorised User claim required a contractual analysis of the company's Passport Advantage agreement and the specific IBM Maximo licence terms. The key question was whether service depot technicians managing customer equipment records within Maximo were "external users" as defined in IBM's licence terms, or whether they were covered under the company's existing Authorised User entitlement.

Review of the IBM Maximo licence terms and the company's Passport Advantage agreement revealed that IBM's Authorised User metric covered "named users" accessing the software for the purpose of the licensee's business operations. The service depot's primary function — maintaining and repairing equipment manufactured and sold by the licensee — was clearly within the scope of the licensee's business operations, even where that activity was performed on behalf of customers.

IBM's auditors had applied a consumer software interpretation of "external user" that is not supported by the Maximo Passport Advantage terms. The external user concept in IBM licensing typically applies to software products accessed by the licensee's customers for their own independent business purposes — not to employees or contractors performing services on behalf of the licensee. We submitted a formal legal position with supporting Passport Advantage term citations, and IBM withdrew this claim element entirely.

Final Settlement and Post-Engagement Compliance Programme

The settlement negotiation concluded in December 2022 — a deliberate timing choice that aligned with IBM's fiscal year-end pressure. IBM's Q4 commercial teams were motivated to close the engagement and book any resulting revenue before December 31. The final settlement of $1.56 million comprised: the negotiated sub-capacity shortfall for the ILMT gap period ($890,000), the minor Cloud Pak boundary period shortfall ($180,000), and a new two-year Passport Advantage agreement contribution ($490,000) covering the company's IBM estate through 2024.

Following settlement, the company implemented automated ILMT agent deployment through its VMware provisioning pipeline, established monthly IBM License Service reporting for the OpenShift Cloud Pak cluster, and formally documented the node pool separation boundary between Cloud Pak and non-Cloud Pak workloads — creating a permanent audit defence record for any future engagement.

For IBM Cloud Pak licensing advisory, ILMT implementation support, or audit defence services, see the IBM Knowledge Hub or our IBM Advisory Services page.