Practice · V.

IBM. ILMT, sub-capacity, audit defence.

The sub-capacity reporting regime, ILMT deployment correctness, PVU computation under virtualisation, mainframe MLPS audits, the Passport Advantage anchor, the Red Hat subscription estate. Long-cycle audits where evidence and tooling matter more than commercial posturing. Independent buyer-side advisory across the full IBM portfolio. The ILMT position is reconstructed inside the firm before any data flows to the publisher.

Speak with a Senior Advisor Engagement models

Where the practice intervenes

Six points on the IBM contract cycle.

Sub-capacity

ILMT health review

The IBM License Metric Tool deployment is reviewed against the sub-capacity reporting regime. ILMT version currency, scan coverage, virtualisation host inventory, agent deployment completeness and the bundling reports are validated. ILMT health gaps are remediated before the next quarterly report is published. The senior advisor signs the ILMT health letter.

PVU computation

ii.

Virtualisation reconstruction

IBM Processor Value Unit computation under VMware, KVM, AIX LPAR and zSeries virtualisation is reconstructed against the deployment. Full-capacity versus sub-capacity scope, eligibility, and the documentation requirements for each virtualisation technology are reviewed. The PVU position paper governs the audit defence.

Passport Advantage

iii.

Renewal anchor strategy

The IBM Passport Advantage anchor is the renewal pivot for software subscription and support. Renewal preparation is filed twelve months in advance. Discount tier strategy, multi-year commitment design, product mix reconciliation and the Software Value Plus channel route are negotiated against the documented position.

Mainframe MLPS

iv.

MLPS audit defence

IBM mainframe Monthly License Pricing Software audits are evidence-heavy and timeline-long. The SCRT and SMF data flows are validated. The closing position is negotiated against documented workload utilisation rather than publisher exposure estimates. The Audit Defence Programme governs the cycle.

Red Hat

Subscription reconciliation

Red Hat Enterprise Linux, OpenShift, Ansible and the JBoss estate are reconciled against documented deployment. The Red Hat subscription model and the integration with the IBM Passport Advantage anchor are negotiated. The Red Hat scope is filed before the renewal commercial letter is returned.

Audit notice

vi.

Audit defence interception

An IBM audit notification triggers the Audit Defence Programme protocol within forty-eight hours. The first written response acknowledges receipt, asks for a documented scope letter, and declines to send data. The senior advisor leads the response from notification through to closing settlement memorandum.

Named senior advisor

The senior advisor named on the engagement letter leads every IBM conversation. No leverage model, no rotation of junior consultants onto an ILMT health review, no anonymous correspondence with the publisher. The advisor signs every position document.

II.

Counter-signed positions

Every written counter-position to IBM is signed by the senior advisor and counter-signed by a second partner before transmission. Two named signatures on every PVU position, every ILMT health letter, and every settlement position.

III.

Independent on every clause

Admodum holds no commercial relationship with IBM. No reseller margin, no Software Value Plus channel relationship, no subcontract from IBM's licence compliance team. We do not work both sides.

IV.

Evidence-first, not rhetoric-first

IBM audits are evidence-heavy and timeline-long. The defence is built on documented ILMT deployment, documented sub-capacity eligibility, documented PVU computation, and documented workload utilisation. The commercial argument follows the evidence, never precedes it.

Five-year retention

Every position paper, counter-position, ILMT health letter and closing memorandum is retained inside the firm for five years from engagement close. The buyer can request source workings at any point.

VI.

Counsel coordination, never displacement

Where an IBM audit escalates to a legal threshold, the senior advisor coordinates with the buyer's counsel through to legal close. Admodum remains advisory. Counsel remains the legal lead.

Operating principles

How the practice is run.

Evidence before argument.

IBM audits are won on the documentation, not on the rhetoric. ILMT deployment correctness, sub-capacity eligibility documentation, PVU computation evidence and SCRT data validation precede every commercial argument. The defence is the documentation. The argument follows.

ILMT as the contract instrument.

The IBM License Metric Tool is the contract instrument under the sub-capacity reporting regime. ILMT version currency, scan coverage and bundling report completeness are health-reviewed quarterly. ILMT health gaps are remediated before the next quarterly report is published.

Passport Advantage by anchor.

The Passport Advantage anchor is the renewal pivot. Renewal preparation is filed twelve months in advance. Discount tier strategy, multi-year commitment design, and the Software Value Plus channel route are documented against the position paper.

Audit response by protocol.

IBM audit notifications are responded to by documented protocol, not by reaction. First response inside forty-eight hours. Scope letter counter-position before any data flows. Findings counter-position against the documented position paper. The Audit Defence Programme governs the full cycle.

Questions

Asked before engagement.

Why does ILMT matter so much for IBM licensing?

Because without a correctly deployed ILMT, IBM's rules default virtualised workloads to full-capacity licensing — the entire physical host rather than the sub-capacity actually used. ILMT deployment and report hygiene are the single largest cost-avoidance controls in an IBM estate.

How do IBM audits usually begin?

Through the Passport Advantage audit clause, typically executed by a third-party firm. The defence is the buyer's own measurement, entitlement mapping across bundles and part numbers, and holding findings to the contract rather than the auditor's methodology.

Can Cloud Pak entitlements be optimised?

Yes. Cloud Paks carry conversion ratios from legacy entitlements and container-based metrics that reward accurate deployment mapping. Most estates carry convertible entitlement value that is never surfaced by the vendor.

How are engagements priced?

Three frameworks: fixed fee for scoped deliverables, contingency tied to verified savings, and an annual retainer for continuous coverage across every vendor. The model is agreed on the first call, which is always complimentary, and independence is warranted in writing on every engagement letter.