A leading robotics manufacturing company based in the Midwest, specialising in industrial automation, collaborative robotics, and autonomous systems, received an IBM software audit claiming USD 18 million in non-compliance across sub-capacity overcounting, entitlement mismatches, and virtualisation overages. Our systematic defence deconstructed every component of IBM’s claim, demonstrating that simulation workload peaks had been misrecorded as sustained production capacity, technology partnership and reseller entitlements were absent from IBM’s records, and test lab virtualisation configurations had been incorrectly assessed at full-capacity rates. Final settlement: USD 720,000 — a 96% reduction — covering genuinely required licences for the company’s expanding autonomous systems platform, with zero penalties.
The company was one of the Midwest’s leading robotics manufacturers, designing and producing industrial automation systems, collaborative robots (cobots), autonomous mobile robots (AMRs), and advanced vision-guided systems for automotive, aerospace, electronics, and logistics customers. Its engineering teams operated at the intersection of mechanical design, embedded systems, machine learning, and real-time control software — requiring substantial computational infrastructure for simulation, testing, and production support.
Db2 powered the company’s manufacturing execution system (MES), product lifecycle management (PLM) database, supply chain planning, and quality management records. WebSphere Application Server supported the customer configuration portal, supplier collaboration platform, and internal engineering workflow applications. MQ messaging connected the MES to robotic cell controllers, vision system interfaces, warehouse automation, and ERP integration points across multiple manufacturing facilities. IBM Engineering Lifecycle Management (formerly Rational) tools supported requirements management, test planning, and traceability for safety-critical robotics systems subject to ISO 10218 and ISO/TS 15066 standards.
The company had maintained an IBM relationship for 15+ years, with annual support spend of approximately USD 2.4 million. IBM initiated its audit through the standard ILMT data request process, and the resulting claim of USD 18 million threatened to consume an entire year’s engineering R&D budget. With tight margins in the competitive robotics sector and an aggressive product development roadmap, the company engaged Redress Compliance to mount a comprehensive defence.
One of the Midwest’s largest robotics companies producing industrial automation, cobots, AMRs, and vision-guided systems. Customers across automotive, aerospace, electronics, and logistics. Engineering teams combining mechanical design, embedded systems, ML, and real-time control.
Db2 (MES, PLM, supply chain, quality), WebSphere (customer portal, supplier platform, engineering workflows), MQ (robotic cell controllers, vision systems, warehouse automation, ERP), and Engineering Lifecycle Management tools — spanning design labs, simulation clusters, test environments, and production facilities.
IBM’s audit alleged non-compliance across three categories: sub-capacity overcounting (USD 10.2M), entitlement mismatches (USD 4.8M), and virtualisation overages in test lab environments (USD 3M). The claim represented approximately 7.5x the company’s annual IBM support expenditure. Learn more about independent IBM advisory services.
The USD 18 million claim equalled the company’s annual engineering R&D budget. Payment at IBM’s claimed level would have forced postponement of the next-generation autonomous systems platform — potentially ceding market position to competitors in a rapidly evolving sector.
IBM’s audit methodology in manufacturing environments exploits specific characteristics of how robotics and advanced manufacturing companies deploy and consume IBM software. Understanding these patterns is essential to mounting an effective defence.
Robotics companies run computationally intensive simulation workloads — physics-based robot motion simulation, digital twin validation, machine learning model training, and hardware-in-the-loop (HIL) testing. These workloads create massive but temporary compute spikes that VMware DRS and auto-scaling policies accommodate by expanding vCPU allocations. ILMT captures these peak allocations as the sustained licensing baseline, inflating PVU requirements by 50–80% compared to the baseline engineering and production workloads that represent the company’s actual sustained capacity.
Manufacturing companies maintain extensive test and validation environments that replicate production configurations for quality assurance, safety certification, and customer acceptance testing. These environments run IBM software but are not production systems — they are active only during specific test cycles and idle between campaigns. IBM’s audit methodology treats any environment with IBM software installed as requiring full licensing, regardless of whether it is a continuously active production system or a periodic test environment.
Robotics manufacturers frequently acquire IBM software through technology partnerships, OEM agreements, and specialised manufacturing resellers. These procurement channels operate outside Passport Advantage and are commonly absent from IBM’s audit entitlement records. The result is that IBM’s audit counts deployments from partnership-sourced licences as unlicensed — converting legitimate, paid-for entitlements into inflated compliance claims.
We structured our defence across four phases: independent data collection and verification, claim-by-claim analysis against independently established baselines, evidence compilation into a corrected compliance report, and structured negotiation with IBM’s audit team.
We deployed independent ILMT verification across all environments, configured sub-capacity reporting where it was missing or misconfigured, collected 12 months of VMware performance data from every cluster, and mapped every IBM product installation to its configuration, usage pattern, and business purpose. Simultaneously, we reconstructed the company’s complete entitlement history from Passport Advantage records, technology partnership agreements, OEM contracts, and reseller purchase orders spanning 15 years. Learn more about IBM license audit survival guide.
We analysed IBM’s audit findings line by line, comparing their claimed PVU counts against our independently measured sub-capacity data, their entitlement assumptions against our reconstructed entitlement register, and their virtualisation assessments against the actual configuration and usage patterns of the company’s test lab and simulation environments. Every discrepancy was documented with supporting evidence.
We compiled a 94-page corrected compliance report presenting the company’s actual licensing position with independently verified data for every product, environment, and deployment. The report included ILMT sub-capacity measurements with simulation peak corrections, a complete entitlement register with partnership and reseller documentation, and test lab configuration evidence demonstrating non-production usage patterns.
We led structured negotiations with IBM’s audit team, presenting the corrected report and negotiating the settlement from a position of independently verified data rather than IBM’s inflated claims.
IBM’s sub-capacity claim of USD 10.2 million was the largest component of the audit. Our analysis demonstrated that the vast majority of this claim was attributable to simulation workload peaks being recorded as sustained capacity, decommissioned environments being counted as active, and a genuine but modest shortfall from the company’s expanding autonomous systems platform.
The company ran physics-based robot simulation, digital twin validation, and ML model training workloads on the same VMware clusters that hosted Db2 and WebSphere production instances. These simulation campaigns — typically lasting 2–5 days during design sprints — triggered VMware DRS to expand vCPU allocations by 60–80% across the cluster. ILMT captured these peaks as the sustained PVU baseline, inflating Db2 and WebSphere counts by approximately 4,800 phantom PVUs. We presented 12 months of VMware DRS logs correlated with the company’s engineering sprint calendar, demonstrating that peak allocations occurred during discrete simulation campaigns averaging 8–12 days per month, with baseline capacity representing the company’s actual sustained requirement.
The company had migrated its primary manufacturing execution system from an older Db2-based platform to a modern architecture 14 months before the audit. The legacy MES servers remained powered on in a read-only archive state for regulatory traceability purposes (FDA 21 CFR Part 11 requirements for medical device customer records) but were not running active IBM software workloads. ILMT continued reporting these servers, adding approximately 2,200 phantom PVUs. We provided decommissioning records, the MES migration project closure documentation, and server configuration data showing the Db2 instances in read-only archive mode with no active connections.
The company’s hardware-in-the-loop testing infrastructure connected physical robot controllers to virtual MES and MQ environments for integration validation. HIL test campaigns ran 3–5 times per month, each lasting 6–18 hours. During these campaigns, the test cluster’s Db2 and MQ instances scaled to production-equivalent capacity. ILMT captured the peak HIL allocations as sustained production, adding approximately 1,600 phantom PVUs. We presented HIL test schedules, automation logs showing start/stop timestamps, and VMware data confirming zero IBM workload between test campaigns. Learn more about IBM PVU sub-capacity licensing explained.
IBM’s claim: USD 10.2 million based on ILMT peak captures inflated by simulation workloads (USD 5.6M), decommissioned legacy MES (USD 2.4M), and HIL test cluster peaks (USD 1.8M).
Our correction: VMware DRS correlation with engineering sprint calendars separated simulation peaks from sustained production. Decommissioning records and server configurations proved legacy MES was archived, not active. HIL test automation logs demonstrated periodic, not sustained, usage patterns.
IBM’s entitlement analysis claimed USD 4.8 million in licensing gaps. Our reconstruction of the company’s complete procurement history revealed that the majority of these “gaps” were entitlements that IBM’s audit had failed to account for — procured through channels outside Passport Advantage that IBM’s records did not capture.
IBM’s virtualisation claim targeted the company’s test and validation environments, where a 19-day ILMT reporting gap during an infrastructure upgrade had triggered IBM’s full-capacity fallback argument, combined with assertions that test lab environments required production-level licensing.
Redress Compliance provides independent IBM licensing advisory — fixed-fee, no vendor affiliations. Our specialists have defended enterprises against IBM audits across every industry, consistently reducing claims by 90–100%.
Explore IBM Advisory Services →During a planned VMware infrastructure upgrade at the company’s primary data centre, ILMT reporting was interrupted for 19 days. IBM applied its standard full-capacity fallback argument, claiming the company must be licensed for every physical core in the affected cluster for the entire reporting period — a 6x multiplier over the actual sub-capacity consumption. We presented the change management records, VMware vCenter migration logs showing orderly VM migration during the upgrade, ILMT data from immediately before and after the gap showing consistent sub-capacity counts, and the project plan demonstrating the planned nature of the maintenance window.
The company maintained three test and validation environments: a customer acceptance testing (CAT) lab, a safety certification lab (for ISO 10218 compliance testing), and a continuous integration/continuous deployment (CI/CD) environment. IBM’s audit treated all three as production environments requiring full licensing. We documented the actual usage: CAT lab active only during customer sign-off cycles (approximately 40 days per year), safety certification lab active during certification campaigns (approximately 30 days per year), and CI/CD running automated test suites with minimal Db2/MQ footprint. Combined, these environments required a fraction of the licensing IBM claimed.
The company had expanded its WebSphere deployment to support a new cloud-connected robot monitoring and diagnostics portal without completing a sub-capacity true-up. This single expansion represented the genuine virtualisation overage: approximately 280 PVUs of WebSphere capacity added for the IoT gateway and monitoring dashboard. Settlement: USD 200,000 at negotiated pricing. Learn more about IBM ILMT compliance and deployment guide.
We entered structured negotiations with IBM armed with the 94-page corrected compliance report. The negotiation combined the detailed technical evidence with commercial and strategic framing designed to achieve a resolution that reflected the company’s actual position rather than IBM’s inflated claims.
Our negotiation strategy leveraged three dimensions: the corrected technical evidence demonstrating that 96% of IBM’s claim was attributable to measurement errors, missing entitlements, and mischaracterised test environments; the company’s ongoing IBM commercial relationship (USD 2.4 million annual support plus planned investment in IBM Engineering tools for the autonomous systems programme); and the competitive context of the advanced manufacturing sector, where the company’s continued investment in IBM technology depended on a constructive resolution.
The 94-page corrected report established our position with independently verified data for every product and environment. IBM could not credibly dispute VMware DRS logs, engineering sprint calendars, HIL test automation data, decommissioning records, or partnership agreement documentation. This evidence made IBM’s original USD 18 million claim indefensible in any escalation scenario.
The company was planning significant IBM investment for its next-generation autonomous systems platform: Engineering Lifecycle Management expansion for safety-critical development workflows, Db2 scaling for the AMR fleet management database, and MQ Advanced for real-time robot-to-cloud messaging. We framed the settlement as the foundation for this expanded relationship, securing the genuinely required licences at preferential pricing rather than punitive audit rates.
The robotics and advanced manufacturing sector operates on tight margins with R&D investment cycles measured in years. An aggressive audit settlement would have directly impacted the company’s ability to invest in product development — exactly the kind of engineering innovation that drives IBM technology adoption. We ensured IBM’s audit team understood this context and the reputational risk of being seen to impede American manufacturing innovation.
| Claim Category | IBM’s Claim | Our Assessment | Reduction |
|---|---|---|---|
| Sub-capacity overcounting | USD 10.2M | USD 380K | 96% |
| Entitlement mismatches | USD 4.8M | USD 140K | 97% |
| Virtualisation overages | USD 3.0M | USD 200K | 93% |
| Total | USD 18.0M | USD 720K | 96% |
“Redress Compliance turned an insurmountable challenge into a manageable situation. Their expertise saved us millions and provided a clear roadmap for maintaining compliance as we grow. They were invaluable to our business.” — CTO, Midwestern Robotics Manufacturer
The audit revealed how the company’s engineering-focused culture — moving fast on product development, simulation, and testing — had created licensing blind spots. We implemented a governance framework that accommodated the dynamic nature of a robotics engineering environment while maintaining continuous compliance visibility.
We reconfigured ILMT with engineering-specific monitoring profiles that distinguished between sustained production workloads and transient simulation/test peaks. Automated tagging correlated ILMT data with the company’s engineering sprint management system (Jira), enabling real-time separation of simulation campaign peaks from baseline capacity. ILMT was deployed with redundant reporting paths to prevent future reporting gaps during infrastructure maintenance. Learn more about IBM IULA unlimited license agreement guide.
We created a single authoritative register consolidating all IBM entitlements from Passport Advantage, the technology partnership agreement, reseller purchases, and the acquired company’s original agreements. The register was integrated with the company’s procurement system so future purchases from any channel were automatically captured. Partnership and OEM entitlements were given equal visibility alongside direct IBM purchases.
We established clear licensing boundaries for the company’s three test environments (CAT, safety certification, CI/CD), with documented usage schedules, automated power-on/power-off logs, and configuration records that would withstand future audit scrutiny. Each test environment was classified with its IBM licensing status, usage frequency, and supporting evidence maintained on a rolling 24-month basis.
We delivered training for the engineering, IT, and procurement teams covering IBM sub-capacity licensing implications of VMware DRS and auto-scaling, the licensing impact of expanding IBM deployments during product development sprints, test environment licensing requirements and documentation practices, and the procurement registration process for all purchasing channels. Quarterly reviews were established to assess the licensing position alongside engineering sprint planning.
This engagement reinforced patterns we observe consistently in IBM audits of advanced manufacturing and engineering companies. The specific products and amounts vary, but the underlying dynamics — simulation peak inflation, test environment mischaracterisation, and partnership entitlement omissions — appear across the manufacturing sector.
Engineering simulation workloads create temporary compute spikes that ILMT records as sustained licensing requirements. Every manufacturer running simulation, digital twin, ML training, or HIL testing on shared infrastructure must maintain VMware performance data correlated with engineering schedules. This data is the primary evidence for separating genuine licensing requirements from transient peak inflation.
IBM treats every environment with IBM software installed as requiring production licensing unless the company can demonstrate otherwise. CAT labs, certification environments, and CI/CD pipelines must maintain documented usage schedules, power-on/off logs, and configuration records that prove their periodic, non-production nature. Without this documentation, IBM will claim full licensing for environments used 30–40 days per year.
Manufacturing companies frequently acquire IBM software through technology partnerships, OEM agreements, and specialist resellers. These channels operate outside Passport Advantage, creating entitlements that IBM’s audit process does not recognise. Every partnership-sourced IBM licence must be documented and included in the company’s entitlement register with the same rigour as direct Passport Advantage purchases. Learn more about IBM Passport Advantage guide.
Legacy systems maintained in read-only archive mode for regulatory traceability still appear in ILMT reports. Manufacturers with FDA, ISO, or other regulatory requirements for archived data must either fully decommission IBM software on archive servers or document the archive-only configuration with evidence that no active IBM workloads are running.
The 2020 acquisition brought USD 980,000 in unrecognised entitlements. Every manufacturer with M&A activity must include IBM licensing reconciliation in its integration protocol — recovering the acquired company’s entitlements and consolidating them before IBM identifies the deployment gap.
The advisory investment represented approximately 4% of the settlement savings achieved. Without independent IBM licensing expertise, the company would have been negotiating against a USD 18 million claim with no basis to challenge simulation peak inflation, recover partnership entitlements, or defend test lab configurations. The information asymmetry between IBM’s audit team and an unassisted manufacturer is substantial.
Advanced manufacturing and robotics companies operate IBM estates with unique complexity: simulation and testing workloads that create transient compute peaks, multiple procurement channels including technology partnerships and OEM agreements, test and validation environments with periodic rather than sustained usage, and rapid product development cycles that drive IBM deployment changes. IBM’s audit methodology does not account for these manufacturing-specific dynamics — it applies generic counting rules that systematically overstate the licensing requirement.
In this engagement, the company’s internal IT team was focused on supporting engineering operations and maintaining production uptime. They lacked the specialised expertise to interpret ILMT data in the context of simulation workload patterns, reconstruct entitlements from technology partnership and OEM agreements, defend test lab configurations against IBM’s production-licensing assumptions, and negotiate with IBM’s audit team from independently verified data. The difference was USD 17.28 million.
Redress Compliance’s team includes former IBM licensing professionals who understand the specific challenges of manufacturing IBM estates: simulation workload dynamics, test environment licensing, OEM and partnership entitlement structures, and the regulatory traceability requirements that create archived-but-reported systems. This expertise is essential to mounting effective defences against audit claims in the manufacturing sector.
Our 94-page corrected compliance report combined ILMT data, VMware performance logs, engineering sprint calendars, HIL test automation data, decommissioning records, partnership agreements, and test lab configuration documentation into a single authoritative evidence package. This level of technical rigour is what transforms audit negotiations from IBM’s framing to the company’s verified position. Learn more about IBM contract negotiation strategies.
Redress Compliance has no commercial relationship with IBM — no partner status, no resale revenue, no referral commissions. Our audit defence recommendations are exclusively aligned with the manufacturer’s interests. This independence is particularly important in audit defence, where advisory firms with IBM partnerships may prioritise preserving their vendor relationship over achieving the best possible outcome for the client.
“Manufacturing companies are among the most vulnerable to inflated IBM audit claims. The combination of simulation workload peaks, test environment complexity, technology partnership entitlements that IBM’s records don’t capture, and the rapid pace of engineering-driven deployment changes means that IBM’s standard audit methodology systematically overstates the licensing requirement by 80–95% in advanced manufacturing environments.”
Redress Compliance delivers independent IBM audit defence for manufacturers and engineering companies — deconstructing inflated claims, recovering missing entitlements, defending test and simulation environments, and negotiating settlements that reflect actual licensing requirements. USD 18 million reduced to USD 720,000 for this robotics manufacturer. Complete vendor independence.
Book a free consultation with our licensing specialists. No obligations, no vendor ties — just independent advice tailored to your situation.
Book Your Free Consultation →