Shelfware refers to purchased software licences that sit unused "on the shelf," often still incurring support fees. Organisations accumulate shelfware by buying more licences than needed — anticipating future deployments, settling audit claims, or simply renewing the same IBM software quantities year after year without evaluating current needs. IBM enterprise agreements often bundle "nice-to-have" products with must-haves, creating a risk that half the bundle becomes shelfware — yet you still pay maintenance on it.
By treating IBM software licences as a lifecycle — from acquisition to retirement — CIOs can convert shelfware from a budget drain into an opportunity for optimisation. Stop paying for what you don't use and redeploy those resources to what matters.
Identifying IBM Shelfware Across Software Portfolios
📋 Assess the Full IBM Estate
Gain a comprehensive view of all IBM software across your organisation. IBM's portfolio spans analytics (Cognos, SPSS), middleware (WebSphere, MQ, integration brokers), databases (DB2, Informix), security tools (QRadar, Guardium), and more. Ensure an inventory that cuts across silos, capturing every IBM application deployed across business units and geographies. List each product, version, and the number of licences owned versus deployed. Common shelfware candidates include products purchased for projects that never went live, "throw-in" licences from past bundle deals, or components of suites never activated.
🔍 Use Tools and Data to Pinpoint Under-Usage
Deploy IBM's Licence Metric Tool (ILMT) to inventory and measure usage of IBM software in your environment — especially useful for products licensed by PVU or virtual cores. ILMT reports highlight which installations are consuming licences and their respective capacities. Complement with broader SAM platforms (Flexera, ServiceNow SAM) that integrate IBM licence data and automatically detect installed software. Leverage available usage logs: Cognos active user counts vs licences purchased, WebSphere server uptime and load. Compare metrics to entitlements — if a tool is barely used compared to what's licensed, flag it as potential shelfware.
🔄 Spotlight on Overlapping and Legacy Products
IBM's portfolio has evolved through acquisitions — check for functional overlap. You might find both Lotus Domino and newer IBM collaboration tools, or multiple monitoring tools (Tivoli vs newer Cloud Pak-based monitors). These overlaps signal opportunity to eliminate one. Also identify IBM products effectively replaced by non-IBM solutions — if you moved from DB2 to open-source databases but still own DB2 licences, those are pure shelfware. Involve application owners and architects: conduct surveys to identify which tools are mission-critical vs candidates for decommissioning.
Recommendations for CIOs
Conduct an Enterprise-Wide IBM Licence Inventory
Create a centralised inventory of all IBM software owned and deployed across the organisation. Include product names, versions, licence counts, and deployment locations. Update this inventory regularly to reflect new purchases or decommissions.
Leverage SAM Tools and ILMT for Discovery
Deploy IBM's Licence Metric Tool (ILMT) and/or SAM tools to automatically discover IBM software and measure its usage. Schedule regular scans to ensure no installations or VMs are missed, and promptly resolve any ILMT scanning errors for accurate data.
Identify Underutilised Installations
Use the collected data to flag licences that are underutilised or not used at all. Look for IBM products installed but not launched in months, or user-based licences (e.g. Cognos users) that far outnumber active users. These are prime shelfware candidates.
Engage Application Stakeholders
Meet with business and IT owners of each IBM application to validate usage. Confirm if certain tools are still needed or can be retired. User feedback often reveals "We no longer use that system" — confirming shelfware status and enabling action.
Maintain Visibility Across All IBM Categories
Examine analytics, middleware, databases, and security for potential shelfware. High-cost areas — databases and integration middleware — are particularly important to scrutinise, as even a few unused licences can result in significant savings.
Entitlement Reviews and Aligning Licences with Usage
Knowing what is deployed is only half the story — CIOs must also understand what they are contractually entitled to use. An entitlement review involves reviewing IBM contracts, purchase records, and Proofs of Entitlement (PoE) to accurately itemise the exact number of licences your organisation owns for each IBM product.
📑 Perform a Licence Entitlement Audit
Use IBM's Passport Advantage online portal as a starting point for entitlement reports. Be cautious: historical entitlements may be spread across multiple sites or agreements (ELA, division-specific purchases). Gather all relevant IBM licence agreements including any special terms (e.g. some enterprise agreements allow swapping products or have unique bundle rights). Reconcile with deployed software to reveal two critical insights: compliance gaps (where usage exceeds entitlements — a risk) and shelfware surpluses (where entitlements exceed usage — an optimisation opportunity).
📊 Compare Usage Data to Entitlements
List each IBM product with two numbers: licences owned and licences actively in use. Any product with a significant surplus is producing shelfware. For example, 100 WebSphere licences with only 40 servers running WebSphere means 60 extra licences — likely paying support on them — that might never be deployed. Dig deeper: projects may have been cancelled, usage downsized due to cloud migration, or an ELA was over-provisioned. Verify licence metrics — IBM licences by PVUs, RVUs, users, install counts — ensure the metric in use aligns with entitlements.
⚖️ Align Licensing to Actual Needs
Formulate a plan to realign entitlements with usage. For true shelfware, you have options: terminate the excess licences, reallocate them to areas of need, or trade them via IBM conversion programmes. In one real-world case, a 9-month review of IBM licences across 30+ sites enabled a firm to confidently cancel an IBM support contract resulting in $8 million in savings over three years. Perform this internal audit proactively — before IBM initiates one — to both avoid compliance issues and identify shelfware.
📚 Related Reading
Recommendations for CIOs
Establish a Baseline of Entitlements vs Deployments
Conduct a thorough entitlement review by collecting all IBM licensing agreements, Purchase Orders, and Proofs of Entitlement. Match this against the inventory of installed software to create a clear licence baseline (Effective Licence Position).
Identify Shelfware in the Baseline
For each IBM product, compare licences owned to licences in use. Mark any surplus as shelfware. Prioritise the largest gaps — these represent immediate cost-saving opportunities (e.g. dozens of unused licences of costly middleware).
Address Compliance and Surplus Separately
Rectify compliance shortfalls (where usage exceeds entitlements) to mitigate audit risk. For surplus licences, develop a plan to eliminate or repurpose them so you're not paying for idle capacity.
Use Measurable Data in Decision-Making
Leverage concrete data from ILMT and usage logs to support findings. If ILMT shows 50 PVUs used out of 200 purchased for WebSphere, use that data to justify reducing licences. Data-driven insights strengthen your case in IBM negotiations and with internal stakeholders.
Engage Independent Licence Experts If Needed
If your team lacks bandwidth or expertise, consider hiring an independent IBM licensing assessment firm such as Redress Compliance. External experts can validate entitlements, perform gap analyses, and uncover hidden shelfware you may have missed.
Need help mapping your IBM Effective Licence Position?
IBM Licensing Assessment →Optimising or Terminating Support Renewals for Unused Software
IBM's annual support (S&S) fees typically cost around 20% of the licence price each year. If you're paying S&S for licences that are not being used, that's pure waste. Vendors like IBM rely on customer inertia — many organisations blindly renew maintenance on all licences, even shelfware, due to fear of losing support or facing reinstatement penalties. CIOs must break this cycle.
🔎 Scrutinise IBM Support & Subscription Renewals
Before the renewal quote is due, perform an internal usage audit to identify which products are truly needed going forward. It is far easier to remove or reduce licences before you pay the renewal than after. IBM's renewal quotes may bundle multiple products together; insist on a breakdown and focus on shelfware items. Do not be deterred by scare tactics — IBM may warn that reinstating later could be very expensive (often 50%+ of back support costs). For shelfware that is truly no longer needed, paying for support "just in case" is usually more costly than any future reinstatement.
📊 Use Hard Data to Decide What to Cut or Keep
Categorise IBM products into tiers: Must-Haves (critical software you use heavily — renew, potentially securing multi-year discounts), Optional (used sparingly or could be replaced — scrutinise closely), and Retire (not used at all — strong candidates for dropping). Quantify underutilised licences in each tier. Build a business case: dropping maintenance on a $500,000 unused licence saves ~$100,000 per year. If a software's future is uncertain, options include suspending or "parking" licences, or partial renewal covering current usage only.
🔄 Consider Third-Party Support Alternatives
Companies like Origina claim to support many IBM products at roughly 50% of IBM's cost. Third-party support covers bug fixes and helpdesk for current versions but cannot provide new IBM versions. If you have shelfware you use sparingly but can't justify full IBM support, third-party maintenance can save money while keeping software running. Even without switching, obtaining a third-party quote provides leverage — if IBM proposes a 7% increase, showing that a third-party would do it for half price is a powerful negotiation chip. Best suited for stable, mature software you don't plan to upgrade.
🤝 Negotiate Renewal Terms in Your Favour
Engage IBM with a strategic mindset. If making a large renewal payment, request concessions: price protections (cap annual S&S increases to 3% or CPI), flexibility to terminate unused licences at renewal or transfer fees to other IBM products. In enterprise agreements, try to include the right to drop or swap entitlements at defined intervals. Leverage upcoming new purchases: "We'll renew these three products if you agree to cancel support on these two shelfware products without penalty." IBM sales teams may accommodate if it secures new revenue.
Recommendations for CIOs
Audit Usage Before Renewal Time
Proactively review IBM licence usage 3–6 months ahead of support renewal dates. Identify which products and how many licences can be reduced or eliminated from the renewal. This preparation enables informed negotiations rather than rushed last-minute decisions.
Cancel Support for True Shelfware
Do not renew maintenance on licences that analysis shows are not in use. Communicate to IBM which licences you are dropping. Accept the trade-off that reinstatement may cost more later — but cumulative savings will likely outweigh that risk.
Negotiate Flexible Renewal Terms
Seek terms allowing adjustment: the right to reduce licence counts at next renewal if usage drops, or to apply unused support value towards other IBM products ("substitution" rights). Ensure multi-year deals have caps on support fee increases to prevent creeping costs.
Leverage Third-Party Support Options
If IBM's renewal quote is exorbitant for legacy products, obtain quotes from third-party providers. Use this as leverage — "match this price or we'll switch." For non-critical, stable software, consider moving to third-party support at lower cost.
Document Everything
Keep thorough records of licences you choose not to renew, with formal confirmation from IBM. Track savings achieved by trimming shelfware — demonstrating six-figure annual cost reductions reinforces the value of active licence management internally.
Leveraging IBM Licence Conversion and Trade-In Programmes
IBM offers programmes to help customers modernise licences, often turning older unused licences into newer solutions. Rather than letting shelfware languish, CIOs can explore converting legacy entitlements into productive software — effectively "recycling" shelfware into tools the business actually needs.
☁️ Modernise to Eliminate Shelfware via Cloud Paks
IBM Cloud Paks are containerised software bundles encompassing multiple IBM products under a unified licensing model. They enable clients to transition from legacy metrics (PVUs, component-based licences) to a flexible Virtual Processor Core (VPC) metric with mix-and-match capabilities. From a shelfware perspective, Cloud Paks let you consolidate multiple older product entitlements into a single pool used for whichever tools you need. For example, trade up barely-used legacy middleware licences into a Cloud Pak covering both old and new functionality — avoiding new purchases while preventing old licences from becoming idle.
🔄 Explore Trade-In and Upgrade Programmes
IBM's licensing has formal provisions for migrations — entitlement conversion or licence trade-up. You might exchange entitlements for one product for credits towards a newer product. IBM has offered trade-ups from older Cognos or TM1 licences to modern Planning Analytics subscriptions, and from WebSphere to Cloud Pak for Integration. IBM typically provides conversion ratio tables (e.g. one old licence = X new licence credits). Those 50 unused licences of Product A could convert into 10 licences of Product B you plan to use — significantly reducing waste.
🗺️ Align Conversions with Your Technology Roadmap
Licence conversion is most valuable when it aligns with your technology roadmap. If you plan to modernise applications or migrate to cloud/containers, converting old licences to Cloud Paks accomplishes two goals simultaneously: reduce shelfware and advance strategic initiatives. Converting to a Cloud Pak gives you the option to deploy on Red Hat OpenShift in the future — ensuring licences won't become obsolete because you can redeploy them in modern environments when ready.
💰 Negotiate Credit for Unused Software
For significant shelfware you want to dispose of, negotiate a credit or buyback as part of new deals. Three common approaches: Return (vendor cancels licences, reduces support costs — you lose rights), Park (vendor allows holding licences without paying support until needed — rare but achievable), Apply Credit (vendor gives credit value for shelfware applied towards new software — a trade-in). With IBM, raise shelfware in every negotiation: "We have $X of unused licences — we'd like to terminate those and use that spend towards this new solution."
Recommendations for CIOs
Evaluate Cloud Pak Conversions
Review IBM Cloud Pak offerings to determine if they can effectively integrate with your legacy products. Analyse IBM's conversion ratios and ensure the maths make sense — converting to a Cloud Pak can enable you to utilise existing entitlements for functionality your business actually requires.
Map Shelfware to Current Needs
For each chunk of shelfware identified, ask if there's an IBM alternative or newer product that fulfils a current need. If so, approach IBM about trade-in programmes. For example, unused BPM licences could potentially convert into a Cloud Pak that developers use for new projects.
Incorporate Shelfware Trade-In in Deal Negotiations
When making a significant IBM purchase or renewal, bundle the discussion of shelfware. Frame it as win-win: "We will commit to this new multi-year deal if we can terminate these legacy licences without penalty or with a credit applied." IBM secures new revenue; you eliminate unused licences.
Validate Cost-Benefit Before Converting
Compare the cost of conversion (if any) versus the status quo. Ensure the move reduces total cost of ownership or at least increases the utility of the spend (more value for the same cost). Don't convert shelfware into different shelfware.
Reducing IBM Licence Sprawl and Contract Consolidation
Large organisations often suffer from licence sprawl — IBM software deployed in an uncoordinated fashion, spread across multiple contracts and purchasing units. This leads to duplicate software fulfilling the same function and a maze of support agreements renewing at different times. CIOs should spearhead a portfolio rationalisation.
🏗️ Rationalise and Consolidate the IBM Footprint
Assess which IBM products are truly needed and eliminate redundant or outdated ones. If two departments use different IBM tools for similar purposes (two monitoring tools, two analytics platforms), evaluate whether one can be phased out. Check for products IBM has divested or deprecated — IBM sold Notes/Domino to HCL and introduced replacements for others. If you're still hanging on to a soon-to-be-obsolete IBM product, it's better to move off it on your own terms.
📄 Consolidate Contracts — But on Your Terms
Bringing all IBM licensing under one master or a few coordinated agreements can yield cost benefits and administrative simplicity. IBM's Enterprise Licence Agreement (ELA) can simplify procurement with one negotiation and renewal date plus volume discounts. However, an ELA is a double-edged sword — vendors bundle shelfware into ELAs under the guise of a "good deal." Insist that consolidation excludes products you don't plan to use. Negotiate clauses to remove or swap unused components at checkpoints. Also ensure co-termination of support — all key licences renewing on the same date — so you can review everything holistically.
🏛️ Centralised Licence Management Governance
Manage IBM licences centrally rather than department-by-department. Establish an internal IBM licence governance committee or SAM function that oversees all IBM software requests. If someone wants a new IBM analytics tool, the team checks if an existing entitlement can be repurposed instead. Treat IBM licences as a shared asset pool rather than isolated per-project purchases — this reduces shelfware accumulating unnoticed. Institutionalise regular internal audits (at least annually) with SAM tool dashboards spotlighting low-utilisation deployments.
📈 Leverage Volume Discounts — But Avoid Overbuying
Consolidation unlocks higher discount tiers in IBM's Passport Advantage programme or enterprise pricing. IBM's standard volume discounts can reach 20% at the highest tier, with deeper discounts (50%+) in large deals. But remain cautious: don't let the allure of a bulk discount prompt you to buy more than needed. It's better to pay for 100 licences at 50% off that you'll use than 200 at 70% off when half sit unused — shelfware at 70% off is still waste. In negotiations, insist on itemising and justifying each component. Set the tone that shelfware will not be tolerated.
Recommendations for CIOs
Rationalise the IBM Portfolio
Perform a functional overlap analysis of IBM tools. If multiple products address the same need, choose one as the standard and phase out the others. Identify legacy software no longer aligned with IT strategy and formulate a retirement plan.
Consolidate Contracts Deliberately
Consolidate disparate IBM contracts into a unified agreement to increase bargaining power and simplify renewals. Be selective — don't bundle software you have no intention of using. The consolidated contract should reflect your actual needs, not the vendor's full catalogue.
Ensure Flexibility in Enterprise Agreements
When entering an ELA, include terms that protect you: ability to remove or swap unused licences at renewal, caps on support escalations, and clarity on how divestitures or mergers affect licence counts. This prevents being locked into paying for shelfware long-term.
Establish Centralised IBM Licence Oversight
Create a centralised SAM function or steering committee for managing IBM licensing. This team should approve new acquisitions (preventing unnecessary buys), track usage enterprise-wide, and lead annual internal licence audits. A single source of truth catches sprawl and shelfware much faster.
Coordinate Renewal Timing
Align major IBM licence renewals to occur around the same time. Co-termination allows you to evaluate total IBM spend in one cycle and redistribute or cut licences holistically. It also provides a larger negotiation opportunity. Staggered, isolated renewals lead to auto-renewing shelfware because they often go unnoticed.
By treating IBM software licences as a lifecycle — from acquisition to retirement — CIOs can convert shelfware from a budget drain into an opportunity for optimisation. The key is proactive management: discover what you have, compare it to what you need, eliminate the gap, and continuously monitor. Stop paying for what you don't use and redeploy those resources to what matters.
Tackling IBM Shelfware and Cost Optimisation?
Whether you need a comprehensive IBM licence inventory, entitlement review, support renewal rationalisation, guidance on Cloud Pak conversions, or help negotiating enterprise agreements that don't lock you into paying for unused software — our IBM licensing specialists deliver vendor-neutral expertise to reduce waste, mitigate audit risk, and redirect savings to strategic priorities.