Sub-capacity licensing is one of the most valuable cost controls available to IBM customers. For large virtualised environments, the savings from sub-capacity licensing compared to full-capacity charges can be substantial — often 5 to 10 times lower. However, IBM's strict compliance requirements mean that a single misstep in ILMT deployment, reporting, or configuration can eliminate these savings entirely and expose your organisation to full-capacity charges.

This guide covers the key risk factors in IBM sub-capacity licensing and provides an assessment framework for evaluating your compliance posture.

Critical Compliance Risk Areas

ILMT Deployment and Coverage

The single most common compliance gap in IBM sub-capacity environments is incomplete ILMT deployment. IBM requires ILMT agents on every server or VM running IBM software under sub-capacity licensing. A missing agent on even one cluster or environment can invalidate your sub-capacity rights for that entire infrastructure.

Common scenarios include:

  • Disaster recovery or failover clusters without ILMT agents
  • Development or test environments thought to be outside the scope
  • Cloud instances deployed without ILMT agents (AWS, Azure, GCP)
  • New satellite offices or regional deployments added without SAM team involvement
  • Containerised environments without IBM Licence Service (ILS) deployed

During an audit, IBM will ask for proof of ILMT coverage across your entire IBM software footprint. Missing or incomplete coverage is a red flag that triggers deeper scrutiny and often results in full-capacity re-calculations for the uncovered portion.

The 90-Day Deployment Rule

IBM's Passport Advantage agreement requires ILMT to be installed within 90 days of first deploying IBM software in a virtualised environment. If you deployed new IBM software months or years ago without ILMT, and only recently installed it, you may have already forfeited sub-capacity rights for that period.

Although late ILMT deployment is common in larger organisations, IBM will not typically grant retroactive sub-capacity rights. Your exposure covers the entire period from initial deployment until ILMT was first active.

Quarterly Reporting Compliance

Beyond deployment, IBM requires quarterly ILMT audit snapshots to be generated and retained for at least two years. Many organisations run ILMT but fail to establish a reporting process. Without documented quarterly reports, IBM can claim you were non-compliant during any quarter for which reports are missing.

The financial impact is severe: IBM will back-charge at full-capacity rates for any quarter without an ILMT report, even if the tool was running.

Virtualisation Platform Eligibility

Not all virtualisation platforms are eligible for sub-capacity licensing. IBM's list of eligible technologies includes VMware, Hyper-V, IBM PowerVM, and certified public cloud platforms (AWS, Azure, GCP). Running IBM software on unsupported platforms means ILMT data is not relevant; IBM can disallow sub-capacity entirely and charge full capacity.

Unsupported scenarios include end-of-life operating systems and older hypervisor versions.

Hybrid and Cloud Environments

Organisations with hybrid deployments — some workloads on-premises, others on cloud, and some in containers — face compounded compliance complexity. Each environment type requires its own monitoring tool:

  • Traditional VMs: ILMT
  • Cloud VMs (AWS, Azure, GCP): ILMT
  • Containers (Kubernetes, OpenShift): IBM Licence Service (ILS)

Many organisations extend IBM software to cloud or containers without extending the compliance programme. This creates blind spots where usage is untracked and sub-capacity rights are forfeited.

ILMT Configuration and Maintenance

ILMT must be kept up to date and properly configured. An outdated ILMT version may fail to recognise new processor types or product versions, causing it to miss or miscount usage. Misconfigured hypervisor credentials, failed scans, or disabled agents all contribute to compliance gaps.

Regular monitoring of ILMT health — checking for agent failures, successful scans, and updated software catalogues — is essential. Many organisations install ILMT and then neglect it, only to discover during an audit that it has been non-functional for months.

Risk Assessment Framework

Organisations should evaluate their sub-capacity compliance across these dimensions:

ILMT Deployment Completeness: Do you have ILMT agents on every server, VM, and cloud instance running IBM software under sub-capacity licensing? Are development, test, and disaster recovery environments covered?

Timely Installation: Was ILMT deployed within 90 days of your first IBM software deployment in a virtualised environment? If not, what is your exposure window?

Quarterly Reporting: Do you generate and retain ILMT audit snapshots every quarter? Do you have at least two years of reports archived?

Platform Eligibility: Are all virtualisation platforms running IBM software on IBM's approved list? Are operating systems and hypervisor versions supported?

Cloud and Container Coverage: For any IBM software deployed on public cloud or in containers, is the appropriate monitoring tool deployed (ILMT for cloud VMs, ILS for containers)?

ILMT Health: Is ILMT regularly updated? Are agents reporting successfully? Is the software catalogue current?

Estimating Compliance Risk

Your financial risk exposure is the difference between sub-capacity and full-capacity licensing multiplied by the percentage of your environment at risk. For a large virtualised environment, this can reach millions of pounds.

For example, an environment with 5,000 PVUs of IBM software under sub-capacity might have an annual maintenance cost of 1 to 1.5 million pounds. If full capacity were applied, that could jump to 7 to 10 million pounds. A compliance gap affecting 30 percent of that environment creates a potential exposure of 1.8 to 2.7 million pounds annually, multiplied by years of non-compliance.

Even organisations that believe they are compliant often have gaps that are discovered only during an IBM audit. The earlier you conduct an independent compliance review, the more time you have to remediate.

Next Steps

If your organisation has IBM software in virtualised environments, consider these immediate actions:

  • Conduct an inventory of all environments running IBM software and verify ILMT coverage
  • Confirm ILMT deployment dates against the date of initial IBM software deployment
  • Check that quarterly ILMT reports have been generated and archived for at least two years
  • Verify that all virtualisation platforms are on IBM's approved list
  • Ensure ILMT is up to date with the latest version and software catalogue
  • For any cloud or container deployments, confirm the appropriate monitoring tool (ILMT or ILS) is deployed
  • Engage an independent IBM licensing advisor to conduct a compliance health check

Proactive compliance management is far less expensive and stressful than remediating issues during an IBM audit.