IBM Dev Test Licensing. The optimization read.

IBM licenses non production and dev test environments by default at the same metric as production. A WebSphere PVU on dev is the same as a WebSphere PVU on production. The list price is identical.

The buyer side response is to use the three specific discount paths IBM does accept: the Authorized User Single Install metric, the Cloud Pak entitlement carryover, and the Passport Advantage Dev Test bundle. Each cuts non production spend by thirty to fifty percent on the right workload.

Read this alongside the sub capacity and ILMT reference, the IBM license models reference, the IBM knowledge hub, the IBM advisory practice, and the Vendor Shield subscription.

Default IBM treatment

The IBM Passport Advantage agreement treats every install as license requiring unless an explicit non production carve out exists. The carve outs are narrow. The default position is full PVU or full VPC on every dev, test, staging, and disaster recovery environment.

Four default rules to know

• Every install requires entitlement. Dev, test, staging, and DR each consume entitlement.
• The metric matches production. A PVU on dev equals a PVU on production at list.
• Sub capacity applies when ILMT is running. Without ILMT, the full capacity of the host applies.
• DR carries a specific cold standby exception. Cold standby is unlicensed. Warm and hot standby are licensed.

Default cost on a 100 PVU dev test estate

Environment	Default treatment	List PVU cost	Buyer side response
Production	Full PVU	$100K	Discount tier
Test	Full PVU	$100K	Apply dev test path
Dev	Full PVU	$100K	Apply Authorized User Single Install
Staging	Full PVU	$100K	Apply Cloud Pak carryover
DR cold standby	Unlicensed	$0	Maintain cold standby posture
DR warm standby	Full PVU	$100K	Apply Cloud Pak carryover

Dev test specific paths

IBM offers three specific discount paths for non production. Each fits a different workload pattern. The buyer side response is to map every workload to one of the three.

Authorized User Single Install

The Authorized User Single Install metric ties the license to a named developer on a single non production install. The metric replaces PVU on the dev workload. The list price is forty to sixty percent below the equivalent PVU.

Cloud Pak entitlement carryover

IBM Cloud Pak entitlements include a non production usage right. One VPC of Cloud Pak for Integration covers the production environment plus one matching dev or test environment at no extra entitlement. The carryover applies across the Cloud Pak family.

Passport Advantage Dev Test bundle

Selected Passport Advantage SKUs ship as a Dev Test only metric. The list price runs thirty to fifty percent below the equivalent production SKU. The metric carries a strict non production use only restriction.

Path fit by workload

Path	Best fit workload	Typical saving	Constraint
Authorized User Single Install	Named developer workstations	40 to 60 percent	Workstation only, no shared dev clusters
Cloud Pak carryover	Matching dev and prod pairs	50 to 60 percent on dev	Requires Cloud Pak production entitlement
Passport Advantage Dev Test	Shared dev and test clusters	30 to 50 percent	Strict non production use only
Default PVU	Production parity environments	0	Buyer side last resort

Sub capacity discipline

The sub capacity rules apply to non production environments at the same intensity as production. ILMT must run. Quarterly reports must be archived. The buyer side response is to treat dev and test ILMT as a board level compliance topic.

Four sub capacity rules in non production

1. ILMT must be running on every host. Including dev and test hosts.
2. Quarterly reports must be archived. The audit window asks for two years of history.
3. Within thirty days of any host change. The ILMT scan must be re executed.
4. VMware and KVM are approved. Hyper V and OpenShift are approved with ILMT 9.2.39 or later.

What happens when sub capacity fails

• Conversion to full capacity. The non production estate moves to full host PVU.
• Settlement multiplier. Audit settlements typically apply a one point five multiplier for the discovery period.
• Back support on the gap. IBM charges the support fees that would have applied during the gap years.
• Settlement size on a 1,000 PVU dev test estate. Around $1.5M list on the WebSphere ND metric.

ILMT scope in non production

The ILMT tool runs in dev and test environments under the same rules as production. The buyer side response is to confirm the scope before any IBM audit.

ILMT scope checklist

Environment	ILMT required	Quarterly report required	Audit risk
Production	Yes	Yes	High
Test	Yes	Yes	High
Dev clusters	Yes	Yes	High
Developer workstation	No if AUSI	No	Low under AUSI
DR cold standby	No	No	Low
DR warm standby	Yes	Yes	High

Five common cost patterns

Most IBM non production estates carry five common cost patterns. Each hides between five and twenty percent of the bill.

Five patterns to find and fix

• Dev clusters on production PVU. Apply the Passport Advantage Dev Test bundle.
• Developer workstations on shared PVU pool. Move to Authorized User Single Install.
• Cloud Pak with no carryover. Claim the non production usage right.
• Warm DR licensed at production rate. Apply Cloud Pak carryover where eligible.
• Sandbox environments left on full PVU. Most qualify for Authorized User Single Install.

Saving by pattern on a $5M IBM software bill

Pattern	Spend slice	Saving range	Effort
Dev clusters on production PVU	$800K	$240K to $400K	Medium
Workstations on shared PVU	$300K	$120K to $180K	Low
Cloud Pak with no carryover	$600K	$300K to $360K	Low
Warm DR at production rate	$400K	$120K to $200K	Medium
Sandbox on full PVU	$200K	$80K to $120K	Low

Eight buyer side moves

The buyer side has eight specific moves on IBM non production licensing. Each maps to one cost line or one risk line.

Eight moves worth pursuing

1. Map every non production environment. Build a register of dev, test, staging, sandbox, and DR.
2. Apply Cloud Pak carryover. Claim the non production usage right on every Cloud Pak VPC.
3. Move workstations to AUSI. Convert named developer installs to Authorized User Single Install.
4. Move dev clusters to PA Dev Test. Negotiate the Passport Advantage Dev Test SKU.
5. Confirm ILMT scope. Verify dev and test hosts run ILMT and archive quarterly.
6. Maintain DR cold standby posture. Avoid warm DR unless explicitly entitled.
7. Insert a dev test ratio clause. Cap dev test entitlement at twenty percent of production.
8. Run an annual dev test review. The estate drifts. Reset every twelve months.

Typical savings ranges

Move	Cost line	Typical saving	Effort
Cloud Pak carryover	Non production VPC	50 to 60 percent on dev VPC	Low
AUSI on workstations	Workstation PVU	40 to 60 percent	Medium
PA Dev Test bundle	Dev cluster PVU	30 to 50 percent	Medium
ILMT discipline	Audit settlement risk	Avoid 50 to 100 percent uplift	Medium
Cold DR posture	Warm DR PVU	100 percent on the warm DR line	High

What to do next

The eight step checklist is the buyer side starting position on every IBM non production review.

1. Inventory every non production environment. Dev, test, staging, sandbox, DR.
2. Confirm ILMT is running on every host. Production and non production.
3. Audit the Cloud Pak entitlements. Claim the non production carryover on every VPC.
4. Move workstations to AUSI. Convert named developer installs.
5. Move dev clusters to PA Dev Test. Negotiate the bundle SKU.
6. Confirm DR posture. Maintain cold standby where possible.
7. Insert a dev test ratio clause. Cap entitlement at twenty percent of production.
8. Schedule the annual review. Reset the estate every twelve months.

Frequently asked questions

How Redress engages on IBM non production

Redress runs IBM dev test reviews inside the Vendor Shield subscription, the Renewal Program, the Benchmark Program, and the Software Spend Assessment. Every engagement is led by a former IBM commercial executive on the buyer side.

Read the related benchmarking, about us, locations, and contact pages.