WebSphere Application Server editions and PVU.

One name, several entitlements.

The WebSphere family spans editions that look interchangeable on a server but are licensed very differently. Network Deployment, the clustering and high-availability edition, is the most expensive and the most heavily counted. Base, sometimes called Application Server, is a lighter entitlement. Liberty Core and Express target smaller footprints with their own constraints. Because the binaries can be installed from overlapping media, an environment frequently ends up running a higher edition than it is entitled to without anyone deciding to.

How edition mix drives the PVU.

All the processor-based editions are counted in Processor Value Units, where the PVU rating per core, roughly 70 PVU on a typical Intel core, is multiplied by the cores the software can use. The edition matters because Network Deployment instances draw a richer entitlement than Base for the same cores, and because clustering spreads the deployment across more hosts. An audit that finds Network Deployment running where only Base is entitled will price the gap at the higher edition across every core in scope.

• Network Deployment carries the heaviest PVU entitlement and clusters across hosts
• Base and Express are lighter, but easy to over-install from shared media
• Liberty Core has its own footprint rules that an auditor will test separately
• Sub-capacity still applies, so the cores the edition can reach set the count

Where the audit finding comes from.

WebSphere findings usually combine two errors: the wrong edition attributed to an install, and full-capacity counting where sub-capacity was actually in force. IBM's data collection tooling reports what binaries are present, not what you are entitled to run, so it tends to read the richest edition it can detect. The buyer side defense maps each running instance to its true edition and entitlement, then applies the correct sub-capacity scope per host, frequently moving the number sharply.

What this means under audit.

WebSphere sits at the center of IBM audit activity because the edition ambiguity and the sub-capacity exposure compound. Under Contain, Reconcile, Challenge, Settle, the Reconcile step is where this is won: rebuild the deployment edition by edition, match it to entitlements and Passport Advantage records, and apply sub-capacity correctly before IBM's edition assumptions harden into a bill. A finding corrected on the true edition mix stays corrected.