Oracle License Processor or NUP metrics. Application User or Professional User. Employee or Contractor. Revenue or Cost of Goods Sold.
The list is endless but Software Asset Managers should be aware of the nuances of Oracle’s licensing metrics.
According to Sheshagiri Anegondi, CEO Rythium Technologies
a licensing metric acts as a proxy for measuring the quantum of use of a software program.
By definition, a license metric is a method to quantify usage and generate revenue for a software publisher. There are four criteria that a license metric should meet:
Many people get confused by the Oracle License Processor or NUP metrics. These two and many others are not difficult to understand if explained well. Oracle, by themselves, are quite clear and transparent about their metrics. They have always provided the information on their websites for all of their customers and Software Asset Managers to understand.
The challenge with the metrics is the innumerable architectural deployments that are possible in an IT infrastructure landscape. This combined with the multitude of integrations with third-party platforms or applications can make interpreting Oracle’s licensing metrics quite difficult.
We have tried to ease the confusion by describing some of the metrics. We are not providing the exact definitions. These are available on the Oracle websites. Instead, we have tried to explain in layman terms the meanings of the metrics & its applicability in different situations. You should always go back to the Oracle websites and their contracts to get the correct & latest definitions of each of these license metrics.
Some of the more commonly used and popular Oracle license metrics are described below.
| Acronym if any | License Metric | Brief Description | Suitability |
|---|---|---|---|
| OMA | Oracle Master Agreement | The first agreement in the contractual hierarchy. Contains general terms governing IP, usage, liability and audit. Has schedules specific to different product sets | Oracle – Customer |
| OMA Schedules | Schedule P Schedule H Schedule C Schedule LVM |
The schedules are described below, they are co-terminus with the OMA | Oracle – Customer |
| Schedule P | Schedule P – Programs (Software) | Schedule pertaining to usage of Software owned or distributed by Oracle. | Oracle – Customer |
| Schedule H | Schedule H – Hardware | Schedule pertaining to usage of Hardware, Operating System Integrated Software | Oracle – Customer |
| Schedule C | Schedule C -Cloud Services | Schedule pertaining to use of Cloud Services (SaaS, Paas, IaaS) | Oracle – Customer |
| Schedule LVM | Schedule LVM – Linux VM Service | Schedule pertaining to use of Linux and Oracle VM Support | Oracle – Customer |
| OLSA | Oracle Licensing & Services Agreement | Legacy agreement for software and support services | Oracle – Customer |
| CSA | Cloud Services Agreement | Agreement specifying hosting and software application service on the cloud | Oracle – Customer |
| LDR | License Definitions & Rules | Document specifying the definitions of different license metrics and their application to different Oracle products | Oracle – Customer |
| OD | Ordering Document | Document showing the bill of material, fees, payment terms, special conditions that might amend other agreements | Oracle – Customer or Oracle – Partner (if the deal is through a reseller) |
| OPN | Oracle Partner Network | Agreement with Oracle PartnerNetwork, ( channel partner program that provides resources and benefits for value-added resellers & independent software vendors.) Has been recently modernized with additional cloud benefits | Oracle – Partner |
| OTN | Oracle Technology Network | OTN is the site for publicly available Oracle technical resources. The OTN agreement is for using Oracle products for development | Oracle – Customer |
| BCL | Binary Code License | Legacy Java License | Oracle – Customer |
| ISV MA | Independent Software Vendor Master Agreement | Contract for software developers who want the right to resell Oracle programs with their software | Oracle – Partner |
| FUDA | Full Use Distribution Agreement | Agreement to allow partner to resell full use Oracle licenses | Oracle – Partner |
| OD Addendum | Addendum to the Ordering Document | Can be any additional changes/entitlements/obligations negotiated with Oracle for use of specific products and services pertaining to a single purchase. All changes to any other documents generally come in these addendums/amendments | Oracle – Customer or Oracle – Partner (if the deal is through a reseller) |
| ASFUDA | Application-Specific Full Use Distribution Agreement | Agreement with ISV to allow resale license that is restricted to a particular application package | Oracle – Partner |
| ESL | Embedded License Agreement | Agreement with ISV to embed Oracle licenses into a specific application package | Oracle – Partner |
| CSDA | Cloud Services Distribution Agreement | Agreement to allow partner to resell Oracle cloud services | Oracle – Partner |
| ULA | Unlimited License Agreement | Specific ordering document pertaining to unlimited license agreements | Oracle – Customer |
| POF | Pool of Funds Agreement | Specific ordering document pertaining to pool of funds agreement | Oracle – Customer |
| Technical Support Policy | Technical Support Policy | Pertaining to the provision of support services including obligations of fees | Not physically signed. Hyperlinked in the OMA |
| OSA | Oracle Services Agreement | Legacy agreement for support services | Oracle – Customer |
| DPA | Data Processing Agreement | Agreement regarding the processing of personal data while providing services | Oracle – Customer |