Engineer reviewing infrastructure monitoring dashboards on dual screens
IBM Practice

IBM ILMT deployment. The 2026 sub capacity guide.

ILMT is the gate to sub capacity pricing. Deployed wrong, it silently converts your estate to full capacity billing. Six steps done right.

Contact Us IBM Practice
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent
Article · IBM Practice

ILMT deployment. Six steps to sub capacity.

ILMT decides whether IBM bills 16 cores or 200. Across roughly 25 ILMT deployment and remediation projects we led in 2024 and 2025, almost every estate believed it was covered until the report said otherwise. Work the six steps in sequence, then run the cadence like the financial control it is: IBM audits the report history, not the install date.

0 of 37 complete
01Before day one

Clear the prerequisites

The slowest item is never the software. The tool is free and the infrastructure is modest, but the eligibility it protects is routinely worth seven figures.

  • Pick a supported server platform, sized against your endpoint count
  • Decide the database: bundled DB2 at no charge, or SQL Server, each with backup and retention policies — this database is your audit evidence
  • File the read only hypervisor credential requests first; vCenter accounts are the longest lead time item
  • Open agent to server network paths across every zone, explicitly including acquisitions and DMZ segments
  • Name an owner; without one the stack decays within two quarters
02Step 1 · Month 1

Build the ILMT server

The 90 day window starts at the first eligible product deployment, not at the SAM team’s convenience. A late install leaves a permanently uncovered period.

  • Confirm when the 90 day clock actually started — the first sub capacity eligible product, anywhere in the estate
  • Small and mid size estates: take the all in one installer with bundled DB2
  • Larger or segmented estates: run ILMT on the BigFix platform with agents carrying the scan schedules
03Step 2 · Month 1

Roll out agents to every eligible host

Agent gaps at the edges are the number one failure we see. Every uncovered eligible host defaults to full physical capacity.

  • Deploy through your standard software distribution, with acquisitions, DMZ hosts, and validated systems explicitly in scope
  • Use the disconnected scanner for isolated zones, with results moved by file transfer
  • Hold coverage at 98 percent or better and treat every gap as an incident, not a backlog item
04Step 3 · Month 1

Connect the VM managers

The step most deployments miss. Sub capacity math compares virtual cores to physical capacity; without hypervisor visibility the calculation, and your eligibility, fails.

  • Connect vCenter and every other hypervisor platform in scope
  • Verify ILMT can see the physical capacity under every virtualized IBM workload
  • Re verify the connection after any vCenter migration or credential rotation — it severs silently
05Step 4 · Months 2–3

Classify the software catalog

Stale catalogs inflated PVU counts 10 to 25 percent in our remediation engagements. This is where the hidden money sits.

  • Update the catalog and confirm bundled components map to their parent entitlements instead of billing standalone
  • Review every newly discovered component and classify it deliberately
  • Put the catalog refresh on a quarterly schedule from day one
06Step 5 · Months 2–3

Validate the first report

Reports that generate but are never reviewed compound errors silently across the two year audit window.

  • Reconcile the ILMT computer list against CMDB and hypervisor inventories
  • Manually verify cores, product mapping, and bundling on a sample of high PVU hosts
  • Fix classification errors before sign off, not after the audit letter
07Step 6 · Go live

Hand over to operations

In 18 of the 25 remediation projects behind this guide, the tool was installed and technically working; what failed was operations after go live.

  • Hand over to a named owner with sign off authority
  • Put the quarterly review meeting on the calendar before the project closes
  • Stand up the agent coverage KPI with the 98 percent floor
08Always on

Hold the scan cadence

Sub capacity bills on peak virtual capacity within the period. A host with no valid scan cannot prove what it consumed, and IBM prices unproven periods at full capacity.

  • Capacity scans every 30 minutes, unbroken
  • Software scans weekly by default, never past the 30 day contractual minimum
  • Keep VM manager collection live — every 12 hours in central mode
  • Alert when any eligible host’s software scan age passes 21 days, leaving a week of margin
  • Keep the ILMT version current; aged versions hand IBM an argument the tooling was invalid
09Every quarter

Run the validation and evidence runbook

Audits test two years of quarterly report history, not the install date. The report history is the exhibit; the install is assumed.

  • Check scan health: zero hosts past 30 days, capacity feed unbroken, VM connections green
  • Reconcile coverage against CMDB and hypervisor inventories; open incidents below 98 percent
  • Sample audit the numbers on high PVU hosts
  • Have the named owner sign, export the report snapshot, and archive it the same day
  • Keep a rolling two years of signed reports where an audit response team can produce them within days
10If not ILMT

Check the approved alternatives

Changing tools never changes obligations. The 90 day window, the scan cadence, and the quarterly signed report apply identically to every approved path.

  • Only HCL BigFix Inventory and Flexera One with IBM Observability ITAM are accepted substitutes
  • ILMT Lite with the disconnected scanner is pre approved under 5,000 VMs or LPARs
  • Containerized IBM software uses the IBM License Service instead, with its own snapshot retention duties
  • Manual sub capacity counting ended May 1, 2023 — without an approved tool, full capacity applies
Vera AI · 30 day free trial
Entitled, deployed, active: Vera reconciles all three.
  • Entitled vs deployed vs active seats compared, priced at your actual contract terms
  • Duplicate tools and unused capacity surfaced across the portfolio
  • A ranked savings queue with dollar values, not license counts
Start the free Vera AI trial →30 days free · no credit card · cancel anytime
Run it with us

Twenty five ILMT deployments and remediations, 2024 to 2025.

An estate review with the IBM advisory practice verifies coverage, catalog quality, and report history before IBM does. If the audit letter has already landed, start with the IBM audit defense playbook and the audit defense service. Pair this plan with the ILMT sub capacity guide and the wider IBM knowledge hub.

Contact Us Read the IBM audit defense playbook →
IBM Audit Defense Checklist

The full ibm audit defense checklist from the IBM Practice.

The ILMT coverage checklist, report validation method, and the audit response sequence for estates that need sub capacity to hold.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.

Get the white paper →
Opens the white paper landing page. We only email you about this download.
Run the software spend health check against your IBM estate in under five minutes.
Open the Tool →