Licensing glossary

What is an Effective License Position (ELP)?

An Effective License Position (ELP) is a reconciliation of what you are entitled to run against what you actually run, product by product and metric by metric, stating the difference.

How it works

On one side sit your entitlements: every ordering document, with its product, metric, quantity and the definitions that govern it. On the other sits your deployment: every installation, the edition and options in use, and the hardware it runs on, counted under the vendor's rules. The position is the delta, in the license metric, with the money attached.

It is not a license inventory, which lists what you bought, nor a discovery report, which lists what you installed. Surplus and shortfall are both findings: surplus is money on the table at renewal, shortfall is the exposure.

Worked example

Illustrative numbers. Oracle Database Enterprise Edition, 16 Processor licenses owned, running on one two-socket server with 32 Intel Xeon cores:

Database
32 × 0.5 = 16 Processors, covered
Diagnostics Pack, enabled, no entitlement
16 Processors short
Position
Shortfall of 16 Diagnostics Pack licenses, priced at list with support

Options are licensed to the same metric and quantity as the database they run in.

What to watch

  • Counting the VM instead of the host. Under Oracle's policy a four-vCPU VM on a 64-core cluster is a 64-core installation unless the partitioning is hard.
  • Options used once. The data dictionary records use, not intent.
  • Percentages. A position that says 92% compliant tells nobody which 8% to fix.
  • Age. Estates move, and a six-month-old ELP is a history document.

Related terms