Configuration decided the licensable cost more than list price did, and full capacity licensing where sub capacity was available overcharged buyers by 20 to 40 percent
The chassis is not the unit of sale. The logical partition map is, and it is the one part of the estate the buyer controls after the hardware is bought.
Prepared by Redress Compliance · August 18, 2026 · IBM Power and AIX estate reviews. 20 to 30 estates reviewed, 2024 to 2025.
Executive summary
Full capacity licensing where sub capacity was available overcharged buyers by 20 to 40 percent. Full capacity is not a decision anybody makes. It is the default you adopt by omitting the tooling.
Capacity on demand activations left licensable cores higher than the workload needed on one in three estates. Temporary activation is only temporary if somebody deactivates it.
Shared processor pool caps, where they were used, cut exposure by 15 to 30 percent. A capped pool means you license the cap rather than the whole server.
The licensable unit is the activated core, not the installed core. That single distinction is where most of the recoverable cost on a Power estate sits.
What is actually being licensed on a Power estate?
Activated processor cores, translated into Processor Value Units for many IBM programs. The activated footprint drives the bill, and the installed core count does not.
Each core maps to a PVU value by processor type. The entitlement basis is set out on the IBM Power page and the AIX page.
Two postures, and only one of them is a decision
Sub capacity licenses the partition rather than the whole box, and requires the IBM License Metric Tool deployed and reporting. Full capacity licenses every core in the server, and it is what you get by omission.
| Posture | Requirement | Cost impact |
|---|---|---|
| Full capacity | No tooling needed | Highest cost |
| Sub capacity | ILMT deployed and reporting | 20 to 40 percent lower |
| Shared pool cap | Pool configured with a cap | 15 to 30 percent lower |
| Capacity on demand, untracked | Activation logging | Avoidable overage |
What does capacity on demand do to the licensable footprint?
It raises it, quietly, and it keeps it raised until somebody deactivates the cores. Temporary activation was left in place on one in three of the estates reviewed.
Deactivate cores you no longer need, and confirm how temporary activation interacts with your entitlements before you rely on it. IBM sets out the terms on its sub capacity licensing page.
Reconcile activated cores against entitlements quarterly rather than at refresh. The gap only ever widens between reconciliations, and it is invisible on the invoice.
The IBM audit defense guide
IBM audit posture, ILMT compliance, PVU reconciliation, sub capacity rules and the clauses that hold through the term.
Get the brief →What 20 to 30 IBM Power estates showed
Across roughly 20 to 30 IBM Power and AIX estates reviewed between 2024 and 2025, configuration decided the licensable cost more than list price did. Three patterns recur.
- Full capacity licensing where sub capacity was available overcharged buyers by 20 to 40 percent.
- Capacity on demand activations left licensable cores higher than the workload needed on one in three estates.
- Shared processor pool caps, when used, cut PVU exposure by 15 to 30 percent.
The common advice is that Power licensing is fixed by the hardware you bought. In roughly 13 of the 25 estates reviewed, configuration set the cost rather than the box.
- Every risky clause flagged with the verbatim quote and page anchor
- Entitlements, caps and protections verified across your whole contract portfolio
- Paste ready replacement language and an evidence trail for the response
How do shared processor pools cut the bill?
A capped shared pool limits the maximum cores a set of partitions may consume, so you license the cap rather than the whole server. Configured well, it is one of the largest single savings on the estate.
The saving is structural, not negotiated
It does not depend on a discount, a renewal date or a sales cycle. Buyers who treated the partition map as a cost lever cut exposure by 15 to 40 percent, which is wider than most discount ranges on the same paper.
The same core counting logic drives the container side of the estate, priced in virtual processor cores rather than PVU. That math sits in the Cloud Pak licensing guide.
Watch the briefing · 5:44The IBM Audit Is the Sales CallWhy timing and ILMT hygiene decide how an IBM review lands.
What is the right PVU posture for most estates?
Sub capacity, which requires the IBM License Metric Tool. Full capacity is the expensive default and almost nobody chooses it deliberately.
Three controls hold the treatment in force
- Deploy ILMT, which is the gateway to sub capacity pricing.
- Report quarterly, which is what keeps the treatment in force.
- Cap the pools, which limits licensable cores by design rather than by discipline.
The tooling and reporting requirements are the same ones an audit tests, which is why the ILMT guide and the audit defense guide describe the same controls from two directions.
What the reviews measured, 2024 to 2025
Two cuts of the engagement file frame where the configuration money sat.
Where sub capacity was available and the tooling to qualify for it had simply never been deployed.
Where shared processor pools were configured with a cap, so the licensable figure was the cap rather than the chassis.
Neither figure came from a negotiation. Both came from reading the partition map and changing what it says.
Your first five moves
- Map every logical partition and its processor pool assignment, which is the document the whole cost position is derived from and the one most estates do not hold.
- Deploy ILMT to qualify for sub capacity pricing, worth 20 to 40 percent against the full capacity default, then report quarterly to keep it in force.
- Cap the shared processor pools to limit licensable cores by design, which cut exposure a further 15 to 30 percent where it was done.
- Deactivate capacity on demand cores you no longer use, since idle activations were sitting on one in three estates reviewed.
- Reconcile activated cores against entitlements quarterly and align the next hardware refresh with a license review. The IBM practice rebaselines the entitlement before the refresh, and the ELA guide covers the vehicle it lands in.
Frequently asked questions
How is IBM AIX licensed?
AIX and Power software license to activated processor cores, which translate into Processor Value Units for many IBM programs. The activated footprint, not the installed core count, determines the licensable cost.
What is sub capacity licensing on Power?
It lets you license a partition rather than the whole server, and it requires the IBM License Metric Tool deployed and reporting. It ran 20 to 40 percent cheaper than full capacity in the estates reviewed.
What is full capacity licensing?
Licensing every core in the server regardless of what runs on it. It needs no tooling, which is exactly why estates end up on it by omission rather than by choice.
Does capacity on demand raise the licence bill?
It can, and it did on one in three estates reviewed. Activations that are never deactivated leave licensable cores above what the workload needs, and nothing on the invoice says so.
How much do capped shared pools save?
Between 15 and 30 percent of exposure where they were configured. A capped pool means the licensable figure is the cap rather than every core in the chassis.
Is ILMT mandatory?
It is mandatory for sub capacity treatment. Without it deployed and reporting, the entitlement position defaults to full capacity, which is the most expensive reading of the same hardware.
How often should activated cores be reconciled?
Quarterly. The gap between activated cores and entitlements only widens between reconciliations, and a refresh cycle is far too slow a cadence to catch it.
Is Power licensing really negotiable?
The configuration is more movable than the price. Buyers who treated the partition map as a cost lever cut exposure 15 to 40 percent, which is wider than the discount range on the same paper.
When should the license review happen?
Aligned to the hardware refresh, because the refresh is when the activated footprint is reset and the entitlement can be rebaselined against measured workload.
What is the single biggest recoverable item?
The full capacity default. It is invisible, it needs no decision to happen, and it was worth 20 to 40 percent on the estates where sub capacity had always been available.
