Oracle Primavera P6 licenses by Named User. Project portfolios pull access from internal planners, external contractors, joint venture partners, and audit reviewers. The named user count rarely matches the entitlement. Five inputs decide the audit position.
Oracle Primavera P6 licenses by Named User Plus. Every authorized user counts. The metric covers internal planners, contractor planners, joint venture partners, project sponsors, finance reviewers, audit reviewers, and any service account that drives the Primavera Integration API.
The contractor footprint in construction, energy, defense, and engineering project portfolios typically expands the authorized user count by 3 to 5 times the directly employed planner population. The audit defense rests on the documented user census, not the active user census.
Oracle Primavera P6 ships in two editions. Each edition carries a separate license metric. The customer that mixes editions has to test each license rule against the deployment topology and the authorized user population.
The enterprise edition runs on a web tier and licenses by Named User Plus. Every authorized user counts toward the entitlement. The license does not separate active users from inactive users. Inactive accounts that retain authorization count in full.
The desktop edition licenses by Named User without the Plus suffix. The metric counts each authorized user. Concurrent use is not the metric. The license rule is identity based.
The cloud edition licenses by subscription user. The metric is similar to Named User Plus but applies under the cloud service description. The license rule counts authorized users on the cloud tenant.
Adjacent Primavera products license under their own metrics. Each carries a separate Named User Plus count. The customer that uses multiple Primavera products has to test each metric independently.
The named user count is identity based. Every authorized user counts, regardless of activity. Authorization is the trigger, not consumption. The customer that counts active users underestimates the bill by 2 to 4 times the actual entitlement need.
Every user with a valid login credential on the Primavera environment counts. The license rule does not care whether the user logs in monthly, annually, or never. The credential is the trigger.
Service accounts that drive the Primavera Integration API, the SDK, or any direct database access count in full. The customer that uses a single service account for a downstream BI tool consumes one Named User Plus license per environment.
Primavera does not separate read only access from edit access in the license metric. A read only user counts the same as a project manager with edit rights. Reporting users count the same as scheduling users.
Every contractor, joint venture partner, external auditor, or external regulator with authorized credentials counts. The user record sits in the Primavera authentication store, and Oracle reads the store at audit.
| User population | Counted as named user | Typical share of total |
|---|---|---|
| Internal planners | Yes, every authorized user | 20 to 30 percent |
| Internal reviewers and sponsors | Yes, even at read only | 10 to 20 percent |
| External contractors | Yes, every authorized credential | 30 to 50 percent |
| Joint venture partners | Yes, every authorized credential | 5 to 15 percent |
| Service accounts and API users | Yes, one license per account | 5 to 10 percent |
Construction, energy, defense, and engineering project portfolios run on extended contractor networks. Every contractor scheduler, every cost engineer, and every project control analyst with Primavera access carries the license obligation. The contractor footprint typically expands the named user count by 3 to 5 times.
Owner operator portfolios that retain scheduling in house carry a smaller named user count. EPC and EPCM contractors that deliver projects under their own scheduling carry a larger count under the customer entitlement.
Joint venture projects with shared scheduling responsibility frequently load both sides of the JV onto a single Primavera environment. The host carries the license obligation for every authorized user, regardless of payroll.
Subcontractor schedules that load into the primary Primavera environment expand the authorized user count. The customer that allows subcontractors to maintain their own schedule fragments inside the primary environment carries the license.
Remote site planners frequently hold credentials they rarely use. The credential is the trigger. Inactive remote credentials still count toward the entitlement.
Oracle License Management Services runs predictable audit motion against Primavera customers. The audit pattern reads the user export, the EPS access map, the integration log, and the authentication store. The audit defense has to match the same evidence chain.
LMS asks for an export of every authorized user covering the last 12 months. The export comes from the Primavera authentication store. The export shows contractor accounts, expired accounts, service accounts, and any account that ever held authorized access.
LMS reviews the Enterprise Project Structure access map to identify which users had access to which projects. The EPS access map frequently grants broader access than the customer realizes. The audit reads the access map as evidence of authorization.
Primavera Integration API logs, web service logs, and direct database access logs show service account usage. LMS reads the logs as evidence of named user consumption against the service account license.
LMS asks for the contractor offboarding process. The customer that cannot demonstrate consistent offboarding carries audit exposure across every contractor that ever held credentials.
The defense pattern is documentary. Every named user has to be justified. Every credential has to be tied to an authorization record. Every service account has to be tied to an integration. The customer that holds the documentation cleanly closes the audit position.
Export the Primavera authentication store. Reconcile against the active employee register, the active contractor register, and the active joint venture register. Document every credential that does not reconcile and trigger offboarding.
Document the EPS access map for every authorized user. Tighten the access map so each user holds access only to the projects the user actually needs. Tight EPS access narrows the audit conversation.
List every service account and tie each account to a specific integration. The service account license cost is contained when the integration list is documented. Undocumented service accounts inflate the cost.
Implement a contractor offboarding process that revokes Primavera credentials within 24 hours of contract end. Document the process. The audit defense rests on the documented process plus the execution record.
The checklist takes the buyer from the renewal letter to the executed strategy. The window is the renewal anniversary. The earlier the work starts, the wider the option set.
Primavera P6 EPPM licenses by Named User Plus. The metric counts every authorized user, regardless of activity. Inactive accounts that retain authorization count in full. Service accounts that drive integration APIs consume named user licenses. Read only users count the same as edit users.
Yes. Every contractor with authorized credentials on the Primavera environment counts toward the entitlement. The credential is the trigger. The audit defense rests on the documented contractor offboarding process. Contractors whose credentials remain active after project end carry the license obligation.
Oracle License Management Services requests an export of the authentication store covering 12 months. LMS reviews the EPS access map, the integration log, and the contractor offboarding process. The audit reads every credential as a license consumption signal.
No. Each Primavera environment requires a separate license count. Development, training, and production environments each carry their own named user counts. The customer that runs four environments licensed once carries exposure across the other three.
The typical exposure gap runs 3 to 5 times the directly employed planner population. The gap opens at contractor accounts, joint venture partner accounts, expired service accounts, and EPS access expansion across closed projects. Documented offboarding closes the gap.
Primavera Cloud Service uses a subscription user metric that broadly mirrors Named User Plus. The cloud model simplifies the database licensing question because Oracle hosts the database. The named user count rules remain similar. Authorization is still the trigger.
Redress runs the user census, the EPS access map review, the service account documentation, and the contractor offboarding loop inside the Vendor Shield subscription and the Renewal Program. The work covers EPPM, Professional, Cloud Service, and the Integration API.
A complete buyer side Primavera review for a mid sized project portfolio runs 4 to 6 weeks. The output is the validated license position, the documented offboarding loop, and the audit defense package. The cost is recovered against the audit exposure in every engagement.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the Oracle service line, and the Software Spend Assessment.
Read the related Oracle Database licensing guide, the Oracle Knowledge Hub, the LMS audit script analysis, the benchmarking service, and the Benchmark Program.
The companion playbook covers the Oracle Unlimited License Agreement decision tree, certification mechanics, and the negotiation moves that protect the customer at exit.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Open the playbook in your browser. Corporate email only.
Open the Paper →Primavera audits read the authentication store. The credentials that linger from a closed project five years ago carry the same license weight as a credential issued yesterday.
We have run Primavera P6 reviews across construction, energy, and defense project portfolios. Every engagement starts with one conversation.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
