The Challenge
A San Francisco-based enterprise technology company with approximately 3,200 employees operates a SaaS-based platform built on cloud-native infrastructure spanning AWS and Google Cloud Platform. Over the previous three years, the company had aggressively migrated from a traditional on-premises data center architecture to hybrid cloud deployment, reducing on-premises infrastructure by over 60 percent.
Legacy IBM middleware components—IBM MQ (message queue), IBM App Connect Enterprise (integration middleware), and IBM DataPower (API gateway and XML processing)—remained critical to the integration layer connecting inherited systems to newer cloud-native services. However, IBM licensing reflected historical on-premises capacity rather than the dramatically reduced footprint in use.
The company maintained full Processor Value Unit (PVU) licensing for all three IBM middleware products at their original scale, even as the actual production deployment shrank. Additionally, IBM ILMT (License Management Tools) had been deployed as a sub-capacity reporting agent but was misconfigured post-migration, reporting inflated utilisation metrics that masked opportunities for licence consolidation and reduction.
A Passport Advantage renewal was approaching, presenting a strategic window to recalibrate licensing and negotiate modernised terms aligned to cloud deployment architecture.
The Approach
Redress conducted a three-phase engagement structured around licence correction, middleware rationalisation, and strategic renegotiation.
Phase 1: ILMT Configuration and Sub-Capacity Reporting (Weeks 1-5)
The company's ILMT implementation was capturing all potential deployment capacity but not accurately reporting actual deployed resources under a sub-capacity licensing model. Redress reviewed ILMT configuration, identified measurement periods where only 22-28 percent of licensed PVUs were in active use, and corrected the deployment topology to reflect true hybrid architecture.
By reconfiguring ILMT to accurately report distributed cloud and on-premises middleware across multiple data centres and AWS/GCP regions, Redress established a factual baseline for licence entitlement. Within five weeks, ILMT compliance was fully restored with auditable sub-capacity reporting. This revealed immediate opportunities for licence reduction across all three middleware components without affecting production workloads.
Phase 2: Middleware Rationalisation (Ongoing)
While IBM MQ remained essential to the legacy integration layer, analysis revealed that IBM App Connect Enterprise was being used for only 12 percent of integration workflows; 88 percent had been migrated to cloud-native alternatives (AWS Lambda, Google Cloud Functions, event-driven architectures). Similarly, IBM DataPower was operating at only 18 percent of provisioned capacity, with API gateway functionality largely displaced by AWS API Gateway and Google Cloud Apigee.
Redress advised a phased decommissioning strategy: maintain IBM MQ and reduce its PVU licensing to production utilisation, eliminate IBM App Connect Enterprise licensing entirely over six months as remaining on-premises integrations migrate to cloud, and negotiate a reduced capacity model for IBM DataPower aligned to declining usage trajectory.
Phase 3: Passport Advantage Renegotiation (Renewal)
Armed with accurate ILMT data and a documented cloud migration roadmap, Redress negotiated a new 2-year Passport Advantage agreement with IBM that reflected:
- Sub-capacity licensing for IBM MQ: Reduced from full 160 PVUs to 45 PVUs based on audited production utilisation, with sub-capacity measurement terms embedded in the agreement.
- Elimination of App Connect Enterprise: Removed entirely from the new agreement with decommissioning milestones embedded as contractual flexibility clauses.
- DataPower right-sizing: Reduced from 80 PVUs to 28 PVUs with a declining capacity path and renegotiation trigger at 12 months if usage continues to decline.
- Cloud migration flexibility clause: Embedded language allowing licence reduction or suspension without penalty as cloud migration milestones are achieved, aligning payment to actual deployment.
Is your IBM licensing aligned to actual deployment?
Let us audit your middleware footprint and right-size your licence estate.The Outcome
Financial Impact
$2.4M in Annual Savings (28% IBM spend reduction) distributed across three components:
- ILMT Correction and Sub-Capacity Licensing (IBM MQ): $1.3M annual savings. Accurate measurement of production utilisation allowed the company to right-size IBM MQ from 160 PVUs to 45 PVUs, reflecting actual middleware message throughput. Sub-capacity measurement is fully auditable and defensible in any IBM compliance audit.
- Middleware Rationalisation (App Connect and DataPower): $0.7M annual savings. Elimination of IBM App Connect Enterprise licensing and reduction of IBM DataPower PVUs from 80 to 28 realise immediate savings with a documented decommissioning roadmap.
- Passport Advantage Renegotiation: $0.4M annual savings. Structured as a 2-year agreement with volume discounts reflecting lower total PVU commitments and embedded flexibility for further reductions as migration progresses.
Operational and Compliance Impact
ILMT is now properly configured and generating auditable sub-capacity reports monthly. The company has established a baseline for IBM middleware licensing that is defencible in any IBM licensing compliance audit, eliminating the risk of unexpected true-up demands. The integration team has visibility into actual middleware utilisation and can model future licensing needs based on documented migration milestones.
Strategic Positioning
The Passport Advantage agreement includes a 12-month renegotiation trigger for DataPower and a cloud migration flexibility clause that allows licence suspension or reduction without penalty as integration workflows move to cloud-native architecture. The company has locked in a two-year pricing plan aligned to its cloud transformation roadmap, eliminating unpredictable licensing surprises during the critical migration window.
Key Takeaways
1. ILMT Misconfiguration Masks Licence Reduction Opportunities
Sub-capacity ILMT deployments are widely misconfigured across enterprise environments. If ILMT is reporting inflated utilisation or is not correctly isolating production from non-production deployments, it will distort licensing decisions. A thorough ILMT audit should be the first step in any IBM middleware licensing review.
2. Middleware Rationalisation Unlocks Significant Savings
Legacy IBM middleware often persists in hybrid and cloud environments long after business logic has migrated to cloud-native services. A functional audit of actual utilisation (not just installed capacity) typically reveals that 60-80 percent of licensed middleware can be eliminated or substantially reduced without affecting core business operations.
3. Cloud Migration Timelines Create Negotiation Leverage
IBM sales teams understand that cloud migration is existential for middleware revenue. Documenting a clear migration roadmap and embedding it in the Passport Advantage agreement as a flexibility clause creates enforceability around licence reductions tied to migration milestones. This converts abstract "future savings" into locked-in contractual terms.
4. Sub-Capacity Measurement Must Be Auditable
ILMT data is only valuable if it is accurately configured and properly documented. The corrected ILMT implementation should produce monthly reports that are suitable for submission to IBM audit teams. Undocumented reductions create compliance risk.
5. Passport Advantage Renewal Windows Are Strategic
Passport Advantage agreements are renewal events where licensing terms can be fundamentally restructured. Attempting to renegotiate IBM middleware terms outside of a renewal window is typically unsuccessful. Identifying the renewal timeline and preparing comprehensive utilisation data months in advance is essential to capturing maximum savings.