Most ULA attention goes to processor counting, but Named User Plus decides part of many certifications. The metric carries per processor minimums that can lift or limit the count. This explains how Named User Plus works at exit and how to count it defensibly.
Named User Plus licenses by the number of individuals and devices authorized to use a program, subject to a minimum number of users per processor. At certification you count the named users and devices for each product licensed this way, then compare the result against the minimum implied by the deployed processors. The certified quantity is the higher of the two. The exact minimum depends on the product and the contract.
Named User Plus rewards organisations that count their users as carefully as their processors. The metric is only an advantage when the user population is genuinely measured and documented, not estimated.
Named User Plus counts people and devices, not cores. A named user is an individual authorized to use the program, and the metric also captures non human operated devices where they access the software. This makes it a fit for environments with a defined, countable user population rather than broad or public access, where processor licensing is usually the cleaner metric.
The defining feature of Named User Plus is the minimum. Each licensed product carries a minimum number of named users per processor, so even a lightly used program cannot be certified below that floor. If the deployed processors imply more users than you actually have, the minimum sets the count. If your real user population exceeds the minimum, the actual count governs. Reading the minimum for each product is the first step, because it is set by the contract and varies.
A single ULA can mix metrics. Some products are certified by processor, some by Named User Plus, and the choice carries through into permanent licenses. The two are not interchangeable after the fact, so the metric you certify under is the metric you keep. This is why the decision deserves modelling rather than habit.
Suppose a product is licensed as Named User Plus with a minimum of 25 users per processor, and it runs on hosts totalling 8 processors after core factor adjustment. The processor based minimum is 200 named users. If the organisation can document 260 genuine named users, it certifies 260. If it can only document 150, the minimum applies and it certifies 200. The lesson is that an accurate, documented user count is what unlocks the higher number. Figures are indicative and depend on the specific contract language.
As with processor counting, the evidence file decides whether the number holds. For Named User Plus the file should document how users and devices were identified and counted, drawn from directory records, application access lists, and account inventories rather than estimates. Where devices are counted, the basis for including them should be recorded. A user count without a documented source is fragile, and fragility is what surfaces in the first two years after certification when audit risk is highest.
Two errors recur. The first is undercounting users, which leaves entitlement on the table because the certified number lands at the minimum when the real population was higher. The second is counting users that cannot be evidenced, which inflates the declaration and weakens it under review. The discipline is the same in both directions: count the genuine population and prove it.
The per processor minimum, the products eligible for Named User Plus, and the definition of a named user all come from the specific agreement. Two ULAs can treat the same product differently. In ULA work the answer almost always depends on the specific wording, so the metric choice and the minimums should be read from your own contract before any count is finalised.
If your ULA includes products licensed by Named User Plus, count the user population as deliberately as the processors. Start with the Oracle ULA certification guide, then read building the deployment inventory and counting across data centers and regions.
Named User Plus is an Oracle metric that licenses by the number of individuals and devices authorized to use a program, subject to a per processor minimum. At certification you count the named users and devices for products licensed this way, then check the result against the minimum the contract sets for each processor.
Yes. Named User Plus carries a minimum number of users per processor, so the certified quantity is the higher of the actual user count and the minimum implied by the deployed processors. The exact minimum depends on the product and the contract, so it has to be read, not assumed.
It depends on how the product is licensed in your ULA and on which metric yields the stronger defensible entitlement. Some products are processor only, some allow Named User Plus, and the choice carries through to perpetual licenses. The decision should be modelled against the contract.
Book a confidential assessment and we will measure your Named User Plus and processor positions together, so the metric works for your certified count.