Oracle Primavera P6 License Compliance
Primavera P6 licenses by Named User Plus, so every authorized contractor, reviewer, and service account counts. The audit gap typically runs three to five times the employed planner headcount.
Prepared by Redress Compliance · June 2026 · Representative Oracle Primavera estate scenario (benchmark scenario, not a quote)
Executive Summary
Oracle Primavera P6 Enterprise Project Portfolio Management licenses by Named User Plus. The metric counts identity, not concurrency. Every individual you authorize to access the environment consumes a license, whether they log in daily or never.
That rule is harsh on project estates. Portfolios pull access from internal planners, external contractor planners, joint venture partner staff, and read only reviewers in the PMO, executive, and audit functions. All of them count the same. Read only access carries the same license weight as full edit access.
Two mechanics widen the gap further. Service accounts that drive the Primavera Integration API consume licenses through the Peripheral Access program, and contractor credentials left active after a project closes keep counting. The result is an authorized population that runs three to five times the directly employed planner headcount.
This paper covers the counting rule, the contractor and joint venture trap, read only consumption, the API exposure, and the documentary audit defense. Every number in the worked scenario is a benchmark, not a quote.
What we see across Oracle Primavera reviews, 2023 to 2025
Across roughly 25 to 35 Oracle Primavera reviews Fredrik Filipsson and the Redress team ran between 2023 and 2025, three patterns recur:
- Contractor and joint venture accounts run 2 to 4 times the employed planner count and stay active 6 to 18 months past project close.
- Integration and API service accounts are almost never licensed, and a single unlicensed web service can pull dozens of indirect users into scope.
- Read only reviewer accounts make up 20 to 40 percent of the authorized population and carry the same license weight as planners.
How Does Oracle Primavera P6 License Users
Primavera P6 EPPM licenses by Named User Plus, a metric that counts every authorized individual regardless of activity. The trigger is the authorization, not the login. An account that holds credentials but never opens the application still consumes a license.
Oracle defines a Named User Plus as a person authorized to use the program, and the P6 EPPM licensing information sets a minimum count per contract. Concurrency does not reduce the number. Ten planners who share five seats by schedule still need ten licenses.
| Counting question | How Primavera P6 answers it |
|---|---|
| Is it concurrency based | No. The metric is identity. Every authorized person counts, active or not. |
| Do inactive accounts count | Yes. An authorized account that never logs in still consumes a Named User Plus license. |
| Can a license be shared | No. A Named User Plus license is tied to one named individual and cannot be pooled. |
| Is there a minimum | Yes. Oracle sets a per contract minimum, so small estates still carry a floor. |
Do Contractors Count As Named Users
Yes. Every contractor with authorized credentials on the Primavera environment counts toward the entitlement in full. External planners and joint venture partner staff are not exempt. The credential is the trigger, and a contractor badge does not change the license metric.
This is where most estates break. A capital project pulls in dozens of external schedulers and partner staff who each receive a P6 login. The license count was sized to the internal planner team. The contractor population was never added.
- External planners. Contract schedulers with edit access count exactly like employees.
- Joint venture partners. Partner staff who access shared project data hold authorized accounts and count.
- Stale credentials. Contractor accounts left active after project close keep counting until they are disabled.
Do Read Only Users Still Count
Yes. Read only users count the same as edit users. Primavera P6 does not separate read only from edit access in the license metric. A PMO analyst who only views schedules consumes a Named User Plus license identical to the planner who builds them.
Read only access expands quietly. Executives, finance reviewers, and external auditors all ask for a view into the portfolio, and each viewer becomes an authorized account. On the estates we review, read only reviewers are 20 to 40 percent of the total authorized population.
| Access type | Typical population | License weight |
|---|---|---|
| Planner, full edit | Internal and contract schedulers | One Named User Plus each |
| Read only reviewer | PMO, executive, finance, audit | One Named User Plus each |
| Team member statusing | Field and task update users | Covered by the included Team Member component |
Authorized population by access type
Read only reviewers are 70 of the 275 authorized users, one quarter of the count.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025. Benchmark scenario, not a quote.
Does API And Integration Access Count
Yes. API access counts. Service accounts that drive the Primavera Integration API consume licenses through Oracle's Peripheral Access program. Any user or process that reads or writes P6 data through an automated interface must be licensed, even when no human logs in.
The Primavera P6 Peripheral Access rule names the Access Points: interfaces, APIs, web services, EDI, EFT, ETL processes, and database links. A single integration to an ERP or BI tool can therefore carry a population of indirect users who must each be licensed.
Two embedded restricted use licenses add a second trap. The bundled WebLogic Server and database are restricted to Primavera use only. Clustering the Primavera WebLogic instance, or running other applications on the embedded database, triggers a full use license that sits outside the P6 entitlement.
What Is The Real Audit Exposure
The exposure is the gap between authorized accounts and licenses held. Consider Meridian Infrastructure, a representative engineering and construction estate that bought 80 Named User Plus licenses against its internal planner team and then ran three years of capital projects.
| User population | Authorized accounts | Counts as | Licenses required |
|---|---|---|---|
| Employed planners | 60 | Named User Plus | 60 |
| External contractor planners | 110 | Named User Plus | 110 |
| Joint venture partner staff | 35 | Named User Plus | 35 |
| Read only reviewers | 70 | Named User Plus | 70 |
| Total Named User Plus required | 275 | 275 |
The integration layer adds 8 service accounts under Peripheral Access, licensed as a separate program. The core Named User Plus shortfall is 275 required against 80 held, a gap of 195 licenses.
Authorized accounts versus licenses held
Meridian Infrastructure benchmark estate. 275 authorized users against 80 licenses held.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025. Benchmark scenario, not a quote.
At Oracle's published list of $2,750 per Named User Plus, the 195 license shortfall converts to a clear number. Oracle support runs at 22 percent of the net license fee every year on top.
| Exposure line | Amount |
|---|---|
| Named User Plus shortfall (275 required less 80 held) | 195 licenses |
| Shortfall license at list ($2,750 each) | $536,250 |
| First year support at 22 percent | $117,975 |
| First year list exposure | $654,225 |
First year list exposure on the shortfall
195 unlicensed Named User Plus at $2,750, plus first year support at 22 percent.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025. Benchmark scenario, not a quote.
How Does Oracle Audit Primavera
Audit defense is documentary. The user export, the EPS access map, and the authorization register decide the position, not the verbal account of who uses the system. Oracle License Management Services requests an export of the authentication store and reads every credential as a consumption signal.
LMS reviews the integration log and the contractor offboarding process alongside the user list. Auditors enforce indirect access rules and will demand licenses for unlicensed users found behind a web service, often retroactively. Each Primavera environment also carries its own count, so development, training, and production are reviewed separately.
- User census. A current export of every authorized account, mapped to a named person or a documented service.
- EPS access map. Evidence of which accounts reach which projects, so closed project access can be retired.
- Offboarding register. A dated log showing contractor and partner credentials disabled at project close.
The same discipline carries into Primavera Cloud Service. The cloud subscription metric broadly mirrors Named User Plus, so authorization remains the trigger even when Oracle hosts the database.
Where The Common Advice On Primavera Licensing Is Wrong
The standard partner pitch is that Primavera compliance is a headcount exercise: count your planners, buy that many seats, and you are covered. We disagree, and the engagement file is the reason.
License to the planner headcount
- Size the seat count to the internal scheduling team.
- Treat contractors as temporary and outside the count.
- Assume read only and API access are free.
License to the authorized population
- Count every credential, including contractors, partners, and reviewers.
- License the integration layer under Peripheral Access.
- Run offboarding so closed project access stops counting.
Planner headcount is the smallest number in the room. The authorized population, set by every credential ever issued and never retired, is the number Oracle audits against. The buyer side move is to manage the credential lifecycle, not just the seat purchase, so the authorized count tracks real use.
Our Recommendations
Run a full user census now
Export every authorized account across all environments and map each to a named person or a documented service. The export is the audit position.
Disable stale contractor and partner credentials
Tie a dated offboarding step to every project close. A credential disabled on the last day is a credential that stops counting.
License the integration layer
Identify every Access Point, API, web service, and database link, and license the indirect users under Peripheral Access before LMS finds them.
Count read only and inactive accounts honestly
Read only reviewers and dormant accounts consume Named User Plus licenses. Include them in the position rather than discovering them in an audit.
Model exposure before you respond to Oracle
Build the validated position, the EPS access map, and the offboarding register before any audit letter sets the script.
Talk to Us Before Oracle Counts For You
Redress Compliance is a 100 percent buyer side advisory firm with no vendor affiliations. We serve 500+ enterprise clients with more than $2B under advisory across 11 vendor practices, including deep Oracle Primavera compliance expertise.
If your Primavera estate spans contractors, partners, and integrations, we will run the user census, map EPS access, document the offboarding loop, and build the audit defense. Contact us at fredrik@redresscompliance.com or visit redresscompliance.com to book a review this quarter. We are glad to tie a meaningful part of the fee to delivered value.
