IBM ELA Review: New England Bank Saves $5.7M Annually and Reduces Agreement by 28%

Client Background and Challenge

The client is a regional financial institution headquartered in New England with approximately 4,200 employees, operating a mix of on-premises data centres, virtualised infrastructure running VMware, and a growing footprint on a major public cloud platform. IBM software underpinned the organisation's core transaction processing, data integration, and customer analytics capabilities, with an ELA that had been in place for five years and was approaching renewal.

The bank's IT leadership had concerns about the upcoming renewal on two fronts. First, the organisation's actual IBM software usage had diverged significantly from the entitlement commitments in the original ELA — the result of infrastructure consolidation, a core banking platform migration, and a strategic decision to move certain workloads off IBM Db2 onto cloud-native alternatives. The bank estimated it was paying annual support fees on between 25 and 35 percent of its entitled IBM software that was no longer actively deployed. Second, the bank's IBM License Metric Tool (ILMT) deployment had not been maintained adequately following a significant virtualisation infrastructure upgrade, raising questions about the accuracy of its sub-capacity licence position.

IBM's account team had opened preliminary renewal discussions 90 days before contract expiry — the typical IBM approach — and had presented a renewal proposal that reproduced the existing ELA scope with a modest three-year price lock. The bank's procurement team recognised that accepting the proposal without independent review would perpetuate the shelfware problem and leave the ILMT compliance risk unaddressed.

Assessment Phase: What the Review Uncovered

Redress Compliance conducted a structured IBM software estate assessment over a six-week period, encompassing entitlement reconciliation, deployment verification, ILMT configuration audit, and compliance gap analysis across all IBM products in the ELA.

Shelfware and Entitlement Overage

The assessment identified seven IBM products within the ELA where deployment had fallen materially below the committed entitlement level. The most significant positions involved IBM WebSphere Application Server, where a consolidation project had reduced active application servers from 48 to 22 while entitlement remained at 48, and IBM DataStage, where a data integration platform migration had left 12 of 20 committed DataStage licences completely undeployed. IBM Cognos Analytics showed similar patterns: the bank's business intelligence platform had partially migrated to a cloud-based alternative, leaving Cognos entitlements substantially over-committed relative to active users. Across all seven products, unused licence obligations totalled $4.5 million per year in S&S fees on software generating no business value.

ILMT Configuration Deficiencies

The ILMT audit revealed a more complex picture than the bank's internal team had anticipated. ILMT had been deployed correctly at the time of the original ELA signing, but the virtualisation infrastructure upgrade 18 months earlier had introduced three specific configuration gaps. First, ILMT agents had not been deployed on 14 newly provisioned virtual machines running IBM software, meaning those deployments were excluded from sub-capacity reporting entirely. Second, ILMT's licence metric configuration had not been updated following IBM's transition of two Cloud Pak products from PVU-based metrics to VPC-based metrics, meaning ILMT was still reporting PVU consumption for products that IBM had moved to VPC licensing. Third, ILMT's reporting schedule had slipped from monthly to quarterly as a result of a resource gap in the ITAM team — creating a reporting frequency gap that IBM's auditors would treat as non-compliant with sub-capacity licensing requirements.

The combined effect of these three ILMT deficiencies was significant. IBM's sub-capacity licensing terms require correct ILMT deployment and configuration as a precondition for claiming sub-capacity pricing. Had IBM initiated an audit in advance of or during the renewal process, it could have challenged the bank's sub-capacity entitlement position for all products on those 14 unmonitored virtual machines, reverting them to full-capacity licensing requirements. The potential financial exposure from this challenge was estimated at $3.2 million in additional licence obligations.

Remediation: Closing the Compliance Gap

Before entering renewal negotiations with IBM, the bank's ITAM team — working with Redress Compliance's technical specialists — undertook a structured ILMT remediation programme. ILMT agents were deployed on all 14 previously unmonitored virtual machines running IBM software, with a 30-day observation period established to generate a compliant usage baseline. ILMT's licence metric configuration was updated to correctly capture VPC metrics for the two Cloud Pak products that had transitioned from PVU, and historical VPC usage was reconstructed from IBM's deployment records to establish a defensible retrospective position. ILMT's reporting schedule was restored to monthly, and a monitoring procedure was put in place to prevent future schedule slippage.

The ILMT remediation established something critically important before the renewal negotiation: the bank entered discussions with IBM holding a clean, documented compliance position — not one that IBM could challenge. This removed IBM's most powerful leverage tool in ELA renewal negotiations, the implied threat that the renewal is the customer's opportunity to resolve compliance exposure. With that lever removed, the negotiation could focus on commercial terms rather than compliance remediation framing.

Renewal Negotiation: Achieving True-Down and Cost Reduction

Armed with a complete entitlement reconciliation, verified deployment data, and a clean ILMT position, the renewal negotiation proceeded on the bank's terms rather than IBM's. The negotiation strategy focused on three primary objectives: eliminating shelfware obligations through true-down rights, securing S&S price protection for the renewed term, and aligning the ELA scope to the bank's genuine three-year technology roadmap rather than IBM's aspirational upsell.

True-Down Rights

IBM's initial position was that true-down on existing ELA products was not commercially available — a standard IBM negotiating stance that has no basis in IBM's actual commercial flexibility at the enterprise level. Presenting IBM with the full deployment data, which demonstrated that the bank was paying annual support on $4.5 million of unused entitlement, shifted the conversation from IBM's position to the bank's documented reality. IBM's alternative was to accept that the bank would not renew at existing scope, potentially converting to Passport Advantage for the products it continued to use. Faced with a credible non-renewal alternative, IBM agreed to true-down rights across five of the seven identified shelfware products, with conversion of the remaining two into credits toward IBM products included in the renewal scope.

S&S Price Protection

The renewed ELA included contractual S&S price protection tying annual support renewal costs to the discounted licence price paid rather than IBM's current list price. An annual increase cap of three percent was agreed for the three-year renewed term. Over the three-year term, this price protection clause alone represented approximately $1.2 million in avoided cost growth versus IBM's standard approach of reverting S&S to list-price-based calculation at renewal.

Scope Rationalisation

The renewed ELA was scoped to reflect the bank's genuine IBM software roadmap: products with clear deployment plans and business justification included at appropriate commitment levels, products with declining or uncertain deployment trajectories moved out of ELA scope and managed through Passport Advantage as needed. The overall ELA commitment was reduced by 28 percent versus the expiring agreement, while maintaining full coverage for the IBM products core to the bank's technology stack.

Outcome Summary

The combined impact of the shelfware elimination, S&S price protection, and ELA scope rationalisation produced the following documented financial outcomes:

• Annual savings from unused licence elimination: $4.5 million — S&S fees on IBM products removed from the ELA through true-down and credit conversion.
• Additional savings from S&S price protection and scope reduction: $1.2 million annually — avoided cost growth from S&S list-price reversion and scope rationalisation.
• Total annual savings: $5.7 million, representing a 28 percent reduction in IBM software costs versus the original ELA renewal proposal.
• Compliance exposure closed: $3.2 million in potential sub-capacity licence exposure from ILMT deficiencies was eliminated through the pre-negotiation remediation programme.
• Post-renewal audit findings: Zero. The bank completed its first post-renewal ILMT reporting cycle with a fully compliant position and no IBM audit activity.

Lessons for IBM ELA Customers in Financial Services

Financial services organisations face specific IBM licensing complexity that amplifies both the risk and the opportunity in ELA renewals. Banking infrastructure is typically heavily virtualised, often across multiple hypervisor layers, creating sub-capacity licensing complexity that requires precise ILMT configuration to manage correctly. Regulatory compliance requirements add a further layer of complexity: banks frequently maintain IBM software deployments in separate compliance environments for audit trail, data retention, and disaster recovery purposes — deployments that carry their own licence requirements and that are easy to overlook in an entitlement reconciliation.

The bank's case illustrates the general pattern we observe across IBM ELA renewals in financial services. Organisations that have held ELAs for multiple years almost invariably have three things in common: significant shelfware resulting from infrastructure rationalisation and platform migrations, ILMT configuration gaps resulting from infrastructure changes that outpaced ITAM maintenance, and an IBM account team that will not voluntarily surface either issue before or during renewal negotiations. Independent assessment, timed to allow remediation before negotiations begin, consistently delivers better renewal outcomes than any negotiation tactic applied after IBM has already set its commercial position.