Why ILMT matters.
The IBM Licence Metric Tool (ILMT) is the IBM provided agent and reporting platform that measures the actual sub capacity consumption of IBM products. ILMT is a contractual prerequisite for sub capacity entitlement under the Passport Advantage Sub Capacity Attachment. A buyer without functioning ILMT loses sub capacity rights and is required to licence at full server capacity.
The operational reality is that most enterprise ILMT deployments are partly broken in ways the buyer only discovers in the audit cycle. The remediation is to run ILMT as a managed platform with defined health signals, a documented bundle file lifecycle, and an Audit Snapshot archival discipline. The dedicated white paper is the ILMT deployment playbook. The expertise page is ILMT expertise.
1. Deployment architecture.
ILMT deploys as a centralised server plus per server agents. The centralised server runs the measurement aggregation, the reporting, and the Audit Snapshot generation. The per server agent is the data collection point that runs on each licensed server. The agent integrates through BigFix as the deployment substrate.
The BigFix integration is the operational backbone. BigFix carries the agent deployment, the agent health monitoring, and the agent configuration push. The most common ILMT architectural failure is the BigFix coverage gap: BigFix not deployed on every server, BigFix not reporting cleanly to the ILMT server, or BigFix not updated through OS patch cycles. The BigFix coverage gap is the upstream cause of the ILMT measurement gap.
The centralised ILMT server itself needs to be sized correctly for the estate. Under sized servers produce incomplete aggregation cycles and missed daily scan windows. The sizing reference is in the IBM published ILMT installation guide and is documented in the operational playbook for the engagement.
2. Scan coverage.
The ILMT scan coverage is the percentage of licensed servers running a healthy ILMT agent and reporting to the central server. The target coverage is 100 percent. The audit threshold for sub capacity entitlement is also 100 percent: ILMT coverage gaps revert the affected servers to full capacity licensing.
The coverage measurement runs on the BigFix agent inventory cross referenced to the licensed server inventory. The gap is the set of licensed servers not running a healthy BigFix agent. The gap is the operational priority for the ILMT team and is the highest leverage remediation lever.
The most common coverage failure modes are: new servers commissioned without BigFix, BigFix agents stopped after OS patch cycles, BigFix agents on container hosts not configured for the container scan, and BigFix agents on isolated network segments without connectivity to the central server. Each failure mode has a defined remediation path.
3. Bundle file lifecycle.
The bundle files are the IBM published product definition files that tell ILMT which installed components belong to which licensed product. The bundle files are updated by IBM on a quarterly cadence. The buyer side must apply the bundle file updates promptly or the ILMT measurements diverge from the licensed product set.
The bundle file lifecycle has three phases: download the new bundle file from IBM, validate the bundle file against the deployed environment, and apply the bundle file to the ILMT server. The validation phase catches bundle file definition changes that affect the deployed environment (for example a bundle file change that splits a previous single product into two licensed products).
The disciplined bundle file lifecycle runs on a 30 day cycle after each IBM publication. The cadence keeps the measurement aligned with the licensed product definition without back logging multiple quarters of bundle file changes at once.
4. The Audit Snapshot.
The Audit Snapshot is the ILMT report that documents the sub capacity peak consumption per product for a defined period. The Snapshot is the contractual record of the sub capacity consumption and is the central exhibit in any IBM audit on the sub capacity entitlement.
The Snapshot must be generated, archived, and retained on the buyer side independently of the live ILMT server. The retention period under the standard Passport Advantage Sub Capacity Attachment is two years. A buyer with a clean two year Snapshot archive defends the historical sub capacity position; a buyer with no archive concedes the historical position to the IBM measurement at the audit.
The Snapshot generation cadence is quarterly. The quarterly cadence aligns with the sub capacity peak reconciliation that drives the licensed PVU count. The cadence also creates the documentary record that the audit team uses to test the sub capacity consumption period by period.
5. Containers and Cloud Pak measurement.
The containerised IBM workloads measure through the IBM Licence Service rather than ILMT. The Licence Service is the container native measurement endpoint that runs on the OpenShift cluster or the Kubernetes cluster carrying the IBM containers. The Licence Service measures the Cloud Pak entitlement on the Virtual Processor Core (VPC) basis.
The Licence Service has its own coverage, scan, and reporting requirements distinct from ILMT. The most common Cloud Pak failure mode is the Licence Service not deployed on every cluster, or the Licence Service deployed but not reporting cleanly. The remediation is the parallel discipline for the container environment: the Licence Service plays the ILMT role.
The mixed environment (containers plus bare metal plus virtualised servers) requires both ILMT (for the non container portfolio) and the Licence Service (for the Cloud Pak container portfolio). The two systems are operationally independent but both must be healthy for the sub capacity entitlement to apply across the full estate. The Cloud Pak expertise page documents the Licence Service.
6. The seven ILMT health signals.
The disciplined ILMT operations team watches seven health signals on the platform.
- BigFix coverage on the licensed server inventory (target 100 percent).
- ILMT agent reporting cadence (target daily scan cycle completing).
- Bundle file currency (target current within 30 days of publication).
- Discovered product cross check (target zero unknown discovered products).
- Audit Snapshot generation cadence (target quarterly Snapshot complete).
- Audit Snapshot archive retention (target two year rolling archive).
- Cloud Pak Licence Service cluster coverage (target 100 percent of OpenShift clusters reporting).
The seven signals form the operating dashboard for the ILMT team. The disciplined practice runs the dashboard weekly and remediates any signal below the target within the cycle.
7. Governance cadence.
The ILMT governance cadence aligns the platform team, the procurement team, and the executive sponsor. The platform team runs the daily and weekly health cycles. The procurement team runs the quarterly Audit Snapshot review tied to the sub capacity entitlement reconciliation. The executive sponsor reviews the annual position at the renewal preparation gate.
The governance also includes the cross over to the self assessment cycle. The clean ILMT position is the foundation of the annual self assessment. A buyer with a broken ILMT cannot run a clean self assessment regardless of the procurement discipline. The dedicated reference is IBM self assessment.
Frequently asked questions.
What happens if ILMT was not deployed on day one of the sub capacity entitlement?
The Passport Advantage Sub Capacity Attachment requires ILMT from the start of the sub capacity period. A deployment that started before ILMT was in place is technically a full capacity exposure for the pre ILMT period. The remediation path is to deploy ILMT, generate the forward Snapshot record, and use the forward record as the baseline for the audit conversation. The pre ILMT period is the negotiation surface, not the strict contractual frame.
Can ILMT be replaced by a third party tool?
No. The Sub Capacity Attachment specifies ILMT as the measurement tool. A third party tool can supplement ILMT but cannot replace it for sub capacity entitlement purposes.
Does ILMT cover Cloud Paks?
No. Cloud Paks measure through the IBM Licence Service running on the OpenShift cluster, not through ILMT. The two systems are independent. Both must be healthy for the full sub capacity entitlement to apply.
How often should the bundle files be updated?
The IBM publication cadence is quarterly. The buyer side application target is within 30 days of each IBM publication. The disciplined practice avoids back logging multiple quarters of bundle file changes at once.
Related pillars across the blog.
IBM Sub Capacity Licensing Explained.
The sub capacity programme, eligibility, ILMT prerequisite, peak reconciliation, and failure modes. The pillar that frames the ILMT discipline.
Read the pillarThe IBM Audit Complete Guide.
The full audit reference covering triggers, opening response, contractual rights, settlement, and the post audit posture.
Read the audit pillarWhere to go next.
For the sub capacity programme reference, continue to IBM sub capacity explained. For the operational deployment playbook, continue to the ILMT deployment playbook white paper. For the audit defense frame, continue to the audit complete guide. For the Cloud Pak measurement path, continue to Cloud Pak expertise. For a scoped ILMT engagement, the license consulting service page is the entry point.
Restore ILMT discipline before the audit?
An independent senior advisor scopes the ILMT health and remediation engagement within a week. The seven health signals are the operating dashboard for the disciplined platform.