>
Product · IBM Sterling

IBM Sterling licensing and audit defense.

IBM Sterling runs the B2B integration and order flows that connect you to partners and customers. Its modules carry different metrics, which is exactly what makes the count slippery under audit. We map the licensing and defend the number. Independent and buyer side, we are not affiliated with IBM.

Mixed metrics · PVU, RVU and VPC by moduleConnections · partners and managed objects counted
How IBM Sterling is licensed.

Sterling is a family, not a single product, and each part is metered differently.

The Sterling portfolio spans B2B integration, file gateway, managed file transfer and order management. Older B2B integration deployments were commonly licensed on the processor value unit, the core based metric where PVU per core is multiplied by the cores allocated to the software. Other modules are metered on resource value units, a usage based metric tied to a resource count such as managed users or devices rather than to CPU.

Newer and containerized Sterling offerings move toward the virtual processor core. Since Passport Advantage version 11, VPC metered products fall under sub capacity reporting and ILMT, and manual counting is no longer accepted. The practical effect is that one Sterling estate can carry three metrics at once, and an audit will test whether your entitlements match the metric each module actually runs on.

The common Sterling audit traps.

Integration platforms grow by connection, and every connection is a counting question.

Trap 01
Metric mismatch across modules
Entitlements bought on one metric while a module runs on another is the fastest way to a finding, and it is easy to miss across a portfolio this broad.
Trap 02
Partner and connection growth
Usage based components scale with trading partners and managed objects, and counts drift well past the original entitlement as the network expands.
Trap 03
Non production and test sprawl
Development, test and disaster recovery copies are often stood up without a clear license basis and are then counted as production capacity.
Trap 04
Sub capacity gaps on core based parts
Where a PVU or VPC module lacks working ILMT coverage, the count defaults to full capacity across the whole host.
How we defend the Sterling count.
01
Contain
Inventory every Sterling module and its metric before any data reaches IBM, so nothing is counted on the wrong basis.
02
Reconcile
Match each module to the correct PVU, RVU or VPC entitlement and apply sub capacity where evidenced.
03
Challenge
Dispute mismatched metrics, inflated partner counts and non production capacity counted as live.
04
Settle
Close on a corrected position with the right metric named for each module in the settlement letter.
Related services.

One estate, three metrics, one defense.

$250M+ in exposure defended. 500+ engagements. We mobilize within 48 hours of your audit notice. Independent and buyer side, every time.

Get audit help now →

The IBM Audit Brief

Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.

IBM Audit

Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.

Services
Audit DefenseAudit NegotiationILMT RemediationSub-Capacity Defense
Products
WebSphereDb2CognosCloud Pak
Company
AboutContactJournalWhite Papers
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019