Oracle Primavera P6 Licensing
Oracle Primavera P6 is generally licensed per user. For this reason, Oracle uses the term Application User for Primavera P6’s licensing metric, similar to Oracle’s Named User Plus (NUP) licensing model. Understanding how Primavera licensing works ensures that organizations avoid compliance issues and unexpected licensing costs.
Primavera P6 Licensing Types and Concepts
Below are the main license types and key licensing concepts specifically for Oracle Primavera P6:
Application User License (Named User)
The Application User License is a per-user license assigned explicitly to each individual. This licensing model follows clear and strict rules:
- Everyone authorized to use Primavera P6, whether actively or not, must have their license.
- Licenses are not transferable between users and cannot be shared across multiple accounts.
- This means no “floating” or concurrent licensing: one license equals one named user.
- Even users with read-only access typically require a license unless a specialized read-only license is purchased.
Named User Plus (NUP)
The Named User Plus (NUP) is an Oracle licensing term similar to Application User licensing:
- Each license is explicitly tied to one uniquely named individual.
- NUP licenses, historically, also apply to Primavera P6.
- Licenses cannot be shared between individuals or transferred.
- Oracle’s rules mandate licensing for all individuals who access the software, including those who access it indirectly via other systems or integrations.
- Oracle’s general agreements might mandate a minimum number of NUP licenses per server, but specifically for Primavera P6, Oracle typically focuses only on counting actual individual users.
Application Read-Only User
Oracle defines an Application Read-Only User as a limited type of user who can only run queries or view reports within the Primavera application:
- Users granted read-only access may have different licensing conditions than standard users (potentially lower cost).
- Despite potential lower costs, Oracle still explicitly requires licensing for these read-only users.
- Typically, an organization must hold full-use licenses before adding any read-only user licenses.
- A common example is executives or senior management who need to access Primavera reports or data, even if only to view them. They must still have an appropriate license if directly interacting with Primavera P6.
Oracle’s Restricted-Use Licensing
Oracle often includes restricted-use licenses with Primavera P6 licenses. These are bundled licenses permitting supporting Oracle components, but only within strictly defined limitations related to Primavera P6.
Here are examples of typical Oracle restricted-use licenses bundled with Primavera P6 and their limitations:
Oracle WebLogic Server (Standard Edition)
- Allowed Usage: Hosting Primavera P6’s basic web interface.
- Prohibited Usage: Deploying non-Primavera applications, enabling clustering, or utilizing advanced features like Enterprise JavaBeans (EJB).
- A full-use license for WebLogic Server becomes necessary if prohibited uses are identified.
Oracle Analytics Publisher (Oracle BI Publisher)
- Allowed Usage: Running built-in Primavera reports or standard Primavera-related reporting templates inside the application.
- Prohibited Usage: Creating custom or new BI reports outside Primavera’s predefined reporting context or using BI Publisher for non-Primavera purposes.
- Oracle requires the organization to purchase a full-use BI Publisher license if used improperly.
Oracle Web Services (Primavera Web Services API)
- Allowed Usage: Primavera data integrations and web-service calls directly related to Primavera functionalities.
- Prohibited Usage: Any third-party applications utilizing P6 web services unless users of those third-party systems also hold proper Primavera licenses.
Oracle Java SE
- Allowed Usage: Using Java SE solely to run Primavera P6.
- Prohibited Usage: Utilizing the included Java SE software to run non-Primavera applications or systems.
- Misusing this bundled Java license triggers the necessity for additional Java SE licenses.
Additional Components (Oracle HTTP Server, Primavera Gateway, etc.)
- These components come bundled with similar restrictions, strictly limited to Primavera-only purposes.
- Using these components beyond their predefined Primavera scope triggers Oracle’s requirement for additional full-use licenses.
Full-Use Licenses and Their Importance
The Full-Use License is a standard Oracle license that lifts the restrictions imposed by restricted-use licensing. The necessity for obtaining a full-use license arises if bundled components are used beyond Primavera P6’s allowed scope:
- For example, deploying custom web applications on the WebLogic server bundled with Primavera P6 immediately requires acquiring a full WebLogic Server license.
- Similarly, enabling clustering or other advanced features beyond Primavera’s base functionality triggers full-use licensing.
Key Licensing Principles for Primavera P6
It’s important to clearly understand Oracle Primavera’s licensing principles to maintain compliance effectively:
- Primavera P6 licensing is always per user (Application User).
- Oracle does not offer concurrent or floating user licenses for Primavera P6.
- Every individual (employees, contractors, external consultants, etc.) who uses or accesses Primavera P6 in any way requires a license.
- This requirement extends explicitly to both:
- Direct users (logging directly into Primavera P6).
- Indirect users (individuals who access Primavera P6 data indirectly via other integrated systems or reporting solutions).
No Technical Enforcement in Primavera P6
Another key aspect of Primavera P6 licensing:
- Primavera P6 software itself does not technically enforce license counts or prevent user creation based on available licenses.
- There are no built-in license keys or restrictions that limit the creation of user accounts or access to specific modules.
- This absence of built-in license enforcement means the responsibility for compliance lies solely with the organization using Primavera.
- Organizations must actively ensure compliance by monitoring user numbers and types of access granted and continually verifying license coverage.
Ensuring Compliance with Primavera P6 Licensing
To maintain compliance with Oracle Primavera P6 licensing, organizations should follow clear guidelines:
Track Authorized Users Closely
- Ensure each user has a corresponding, explicitly-assigned license.
- Remove or deactivate accounts of users who no longer require access.
Manage Read-Only Users Carefully
- Identify users requiring only read-only access.
- Ensure you hold necessary full-use licenses before adding read-only licenses.
Control Restricted-Use License Usage
- Implement controls preventing restricted-use components from being used outside Primavera’s context.
- Conduct regular checks to ensure no unauthorized usage, such as extra applications deployed on bundled WebLogic servers or unauthorized custom reports using Oracle BI Publisher.
Monitor Indirect Access
- Review integrations regularly and confirm that all indirect Primavera data users are licensed accordingly.
Examples Illustrating Proper Primavera P6 Licensing
To clarify licensing concepts, consider the following scenarios:
Scenario: Shared Accounts (Prohibited)
- Three individuals share one Primavera P6 account.
- Oracle explicitly prohibits this, as each individual must have a separate license.
- The organization must purchase additional licenses immediately to comply.
Scenario: Indirect Access via Integrations (Licensing Required)
- Fifteen project stakeholders indirectly access Primavera data through ERP or BI dashboards but do not log into Primavera P6 directly.
- Oracle mandates that these indirect users be licensed, as indirect access still requires individual licensing.
Scenario: Misuse of Restricted-Use Licenses (Triggers Full-Use License)
- IT staff deploys a non-Primavera custom Java application on the WebLogic instance bundled with Primavera P6.
- This immediately requires the purchase of a full-use WebLogic Server license from Oracle due to breaching restricted-use limitations.
Conclusion
Oracle Primavera P6 licensing is structured but requires diligent management due to its strict per-user, no-concurrency, and restricted-use conditions. Organizations must remain vigilant, as Primavera software itself does not technically enforce licensing compliance.
Continuous monitoring, careful management of restricted-use components, and a clear understanding of direct and indirect licensing requirements are essential to avoiding compliance issues and costly license audits.
