Oracle Primavera P6 Licensing: Metrics, Costs, and Compliance Rules Explained

Oracle Primavera P6: The Two Editions

Oracle Primavera P6 is available in two distinct product variants, each with a different delivery model, user base, and licensing structure. Understanding which edition applies to your deployment is the starting point for any compliance or cost analysis.

Primavera P6 EPPM (Enterprise Project Portfolio Management)

P6 EPPM is the web-based, enterprise deployment of Primavera that supports large, multi-project environments with centralised administration, role-based access, and integrations to ERP systems. It runs on Oracle WebLogic Server, uses an Oracle Database backend, and is accessed via web browser. P6 EPPM is typically deployed in capital projects, infrastructure, utilities, government, and large engineering organisations where hundreds or thousands of project managers, schedulers, resource managers, and executives require access to a common project data environment.

The EPPM licence includes rights to Oracle Database and Oracle WebLogic Server for the specific purpose of running P6 EPPM — these are restricted-use licences, not full entitlements to those Oracle technology products. This distinction matters significantly in audit situations and in cost analysis, as it means the Primavera licence does not permit broader use of Oracle Database or WebLogic beyond the P6 application boundary.

Primavera P6 Professional

P6 Professional is the legacy desktop client application that connects directly to a shared Oracle Database or an EPPM database. It is the preferred tool for schedulers who require the full feature depth of P6 for schedule creation, analysis, and reporting without the web interface. P6 Professional is typically deployed alongside EPPM, with dedicated schedulers using the desktop client and broader project audiences using the EPPM web interface.

P6 Professional is licensed separately from P6 EPPM. Users who access P6 through both the EPPM web interface and the P6 Professional desktop client require licences for both products. Organisations should audit whether P6 Professional licences are being used by individuals who also hold EPPM licences, as overlap is common and represents avoidable cost.

The Licensing Metric: Named User Plus

Oracle Primavera P6 is licensed exclusively on the Named User Plus (NUP) metric. This is the most important fact about P6 licensing and the one most frequently misunderstood by organisations deploying the software at scale.

What Named User Plus Means in Practice

A Named User Plus licence authorises one specific, identified individual to use the software. The licence belongs to that individual and cannot be shared, transferred between users, or used on a concurrent or floating basis. Every person who is authorised to access P6 — regardless of how frequently they do so — must hold a named user licence in their own name.

The "Plus" element of the NUP metric extends the authorisation to the necessary technology infrastructure. A P6 EPPM NUP licence authorises the named individual to use the P6 application, the underlying Oracle Database (in restricted-use mode), and the Oracle WebLogic Server (in restricted-use mode) that the application runs on. It does not authorise any other use of those technology products.

There is No Concurrent User Licensing for P6

This point requires emphasis because many organisations arrive at their P6 deployment with experience of project management tools that do licence on a concurrent user basis — where a pool of licences can be shared across a larger population with only the peak simultaneous user count determining the licence requirement. Oracle Primavera P6 does not work this way. Oracle has never offered concurrent user licensing for P6. Every user in the system, whether they logged in yesterday or have not logged in for six months, requires a named user licence.

The practical implication is that licence accumulation happens naturally as deployments grow and user populations turn over. Former employees, contractors who have left, or users whose roles no longer require P6 access continue to consume named user entitlements until their accounts are actively deactivated and removed from the system. Organisations that do not manage this process rigorously will find their actual licence demand consistently higher than the population of active, current users.

For a structured framework, download our Oracle Primavera Compliance Playbook — a step-by-step resource built from 500+ Oracle advisory engagements.

User Roles and Licence Types

Oracle Primavera P6 EPPM includes several defined user profile types that correspond to different access levels within the application. Matching the correct licence type to each user role is both a compliance requirement and a cost management opportunity.

Application User (Full Access)

The Application User profile provides full access to P6 EPPM functionality — project creation and management, schedule development, resource assignment, progress reporting, and administrative functions. This is the highest-cost licence tier and should be assigned only to users who genuinely require the full breadth of P6 capability: senior project managers, schedulers, programme managers, and P6 system administrators.

Resource and Role Access

Resource users can view and update their own task assignments within P6 without access to the broader project management and scheduling functionality. This licence tier is appropriate for engineers, tradespeople, and other operational staff who receive task assignments through P6 but do not build or manage project schedules. In deployments where large populations of operational staff are assigned tasks through P6, the cost difference between licensing them as Application Users versus the lower-tier resource access is material.

Read-Only Users and Executives

Executive or read-only users require access to project status, portfolio dashboards, and management reporting within P6 but have no need for the scheduling and project management functions available to full Application Users. Oracle's licensing rules require that even read-only users hold named user licences. The cost of licensing large executive or stakeholder audiences in P6 often leads organisations to consider alternative approaches to delivering project reporting — such as exporting summary data to enterprise BI tools — rather than provisioning P6 licences for audiences that do not require the full application.

Indirect Access: The Most Dangerous Compliance Risk

Indirect access to Oracle Primavera P6 data is the compliance area that most frequently produces large, unexpected audit claims. It is also the area where Oracle's licence enforcement has become most rigorous and where the financial exposure is most difficult to quantify without a systematic review.

The Indirect Access Definition

Indirect access occurs when a person accesses Oracle Primavera P6 data or functionality through any interface other than the P6 application itself. Oracle's licence terms do not require that a person log in to P6 directly for the licence obligation to apply — if they benefit from P6 data, they are considered a user in Oracle's view. Common indirect access scenarios include viewing P6 schedule or milestone data in a Power BI, Tableau, or MicroStrategy report, accessing P6 project data through an ERP system interface, receiving P6 data through a custom reporting portal, or triggering P6 workflows through an integration with a document management or asset management system.

The practical challenge is that indirect access populations are often many times larger than the direct P6 user population. A P6 deployment with 500 licensed users may generate reporting that reaches 2,000 stakeholders via an integrated BI system. Oracle's audit position is that all 2,000 stakeholders require named user licences unless the reporting mechanism is structured so that P6 data is aggregated before reaching individual users — a technical threshold that is rarely satisfied in practice.

Remediation Options for Indirect Access

When indirect access exposure is identified, organisations have three remediation paths. The first is to purchase named user licences for the indirect user population — appropriate when those users genuinely require ongoing access to P6 data and the business case supports the investment. The second is to restructure the integration so that P6 data is aggregated into anonymous, non-user-specific formats before it reaches the consuming population, which eliminates the named user licence obligation for that population. The third is to eliminate the integration entirely and migrate the reporting or workflow need to a system that does not draw from P6 data.

The optimal remediation strategy depends on the size of the indirect user population, the business value of the access, and the cost of restructuring versus licensing. Independent analysis of each integration is required to identify the most cost-effective approach.

Restricted-Use Licence Boundaries

The Oracle Database and Oracle WebLogic Server licences bundled with P6 EPPM carry significant restrictions that are easy to violate and difficult to remediate retroactively. Understanding these boundaries is essential for any organisation hosting P6 on premises.

Oracle Database Restricted-Use Rules

The Oracle Database licence included with P6 EPPM may only be used to store and process P6 application data. The database instance must be dedicated exclusively to P6 — no other application schemas, no other application data, and no general-purpose database usage is permitted under the restricted licence. If the P6 database instance is shared with any other application, or if any non-P6 schemas exist in the database, the restricted-use boundary has been breached and the full cost of an unrestricted Oracle Database licence applies to the server.

In practice, database sharing occurs frequently in organisations where infrastructure teams consolidate workloads onto shared database servers. A DBA who adds a non-P6 schema to the Primavera database for convenience — perhaps to support a custom reporting application or a small administrative tool — creates a licence violation that can be worth several hundred thousand dollars in a subsequent Oracle audit.

Oracle WebLogic Restricted-Use Rules

The Oracle WebLogic Server licence bundled with P6 EPPM is restricted to the purpose of running the P6 EPPM application. Deploying any additional Java EE application on the same WebLogic instance, using WebLogic as a general-purpose application server, or connecting non-P6 applications to the WebLogic deployment violates the restricted-use boundary. As with the database restriction, violations require a full, unrestricted WebLogic licence for the server.

Support Costs and Annual Uplift

Oracle charges annual support fees at approximately 22 percent of the net licence value. These fees cover software updates, patches, and access to Oracle support services. Oracle increases support fees by 8 percent per year, compounding the base support cost year on year without any corresponding obligation to increase software usage or deployments.

The 8 percent annual support uplift has a significant long-term cost impact. An organisation paying £200,000 per year in P6 support today will pay approximately £370,000 per year in ten years, assuming the same licence base and no commercial intervention. Proactive management of the licence footprint — eliminating unused licences, managing user population growth, and challenging support increases at renewal — is the only mechanism to contain this structural cost escalation.

Oracle does not reduce support fees voluntarily. Reductions require commercial negotiation, typically in the context of a broader Oracle contract renewal or in response to a competitive evaluation of alternative project management platforms. Organisations that present Oracle with data demonstrating reduced usage or credible migration plans consistently obtain better renewal terms than those that renew passively.

Key Takeaways

Oracle Primavera P6 licensing is governed by a single metric — Named User Plus — applied to every individual who accesses P6 data or functionality, whether directly through the application or indirectly through an integrated system. There is no concurrent user licensing, no processor-based option, and no tolerance for account sharing.

The two editions — EPPM and Professional — are licensed separately and the restricted-use licences for Oracle Database and WebLogic bundled with EPPM carry strict usage boundaries that must be actively managed. Violations of those boundaries are among the most common sources of large-value audit findings in Primavera deployments.

Cost management for P6 requires active governance: monthly user account reconciliation to prevent licence accumulation, integration mapping to identify and quantify indirect access exposure, and proactive renewal negotiation to resist Oracle's 8 percent annual support uplift. Organisations that treat P6 licensing as a set-and-forget function consistently face larger compliance liabilities and higher total cost of ownership than those that manage it continuously.