10 Must-Know Facts About Oracle Primavera Licensing
Oracle Primavera P6 licensing can be complex, and misunderstandings can lead to compliance issues, unnecessary expenses, or audits.
Here are 10 essential facts IT and licensing professionals should know about Primavera licensing.
1. Primavera P6 is Licensed per User (Application User)
Oracle licenses Primavera P6 primarily using the Application User metric, similar to the Named User Plus (NUP) model. Each authorized user must have an individual license.
- No concurrent licenses: Licenses cannot be shared among multiple users.
- No floating licenses: Each license is strictly tied to a specific named individual.
2. Named User Plus (NUP) and Application User Licenses Explained
Primavera licenses are closely related to Oracle’s Named User Plus licenses:
- Named User Plus (NUP) means each license corresponds to exactly one named individual.
- Historically, Primavera P6 licenses follow the NUP concept closely.
- Oracle requires every individual accessing Primavera, directly or indirectly, to be licensed individually.
3. Application Read-Only Users Must Be Licensed
Oracle requires licensing even for users with minimal or read-only access.
- Read-only users can run queries or reports without editing data.
- Although potentially less expensive, read-only users still must hold valid licenses.
- Organizations must own full-use licenses before adding any read-only user licenses.
4. Indirect Access Requires Licensing
Indirect usage is one of the biggest compliance risks in Primavera licensing:
- Indirect access occurs when users access Primavera data via third-party systems (e.g., ERP, BI dashboards, custom apps).
- Oracle explicitly requires licensing for indirect users accessing Primavera data through any external interface.
- Example: Users viewing Primavera data in Power BI dashboards must have Primavera licenses.
Read Indirect Access in Oracle Primavera P6 Licensing.
5. Restricted-Use Licenses Include Specific Limitations
Oracle bundles certain restricted-use licenses with Primavera software:
Oracle WebLogic Server (Standard Edition)
- Allowed only for hosting Primavera’s web application.
- Prohibited: deploying non-Primavera apps, clustering, or using advanced Java features.
- Violations trigger the need for full WebLogic licenses.
Oracle Analytics Publisher (Oracle BI Publisher)
- Allowed solely for Primavera reports using built-in templates.
- Prohibited: creating custom BI reports outside Primavera’s defined scope.
Oracle Web Services (Primavera Web Services API)
- Allowed for Primavera integrations only.
- Prohibited: third-party use without licensing end-users.
Oracle Java SE
- Allowed only to run Primavera.
- Prohibited: using bundled Java SE licenses for other applications.
6. Full-Use Licenses May Be Required for Expanded Use
Organizations exceeding restricted-use license limitations must purchase full-use licenses:
- For example, deploying additional custom applications on bundled WebLogic servers triggers full-use licensing.
- Oracle strictly enforces this rule during licensing audits, imposing additional license costs for misuse.
7. Primavera Does Not Technically Enforce Licenses
Primavera software itself lacks technical enforcement mechanisms:
- No built-in license keys or user-limit enforcement exists within Primavera.
- Organizations must manually monitor and manage licensing compliance, user counts, and module usage.
- Compliance responsibility rests fully with the organization.
8. Administrators and Support Staff May Require Licensing
Administrators and support roles interacting with Primavera directly must also hold valid licenses:
- Primavera application admins, report developers, or support staff logging into Primavera interfaces require individual licenses.
- Database administrators using direct database queries (without Primavera interfaces) typically do not require licenses.
9. Team Members and Field Users Need Licenses
Team members performing limited tasks (e.g., submitting progress or timesheets) also require licensing:
- Primavera Cloud offers lower-cost Primavera Progress or Team Member licenses for limited tasks.
- On-premises Primavera offers similar options (e.g., P6 Progress Reporter).
- Each team member updating Primavera data directly or indirectly must be individually licensed.
10. Oracle Audits Indirect Usage and Integration Carefully
Oracle’s License Management Services (LMS) carefully scrutinizes indirect usage during audits:
- Auditors use scripts, questionnaires, and direct interviews to identify indirect usage scenarios.
- Common audit triggers include integrations with ERP systems, custom dashboards, or BI reporting tools.
- Organizations not properly licensing indirect users face additional fees, penalties, and audit findings.
Conclusion
Oracle Primavera licensing requires organizations to clearly understand and actively manage user licenses, indirect access, and bundled restricted-use components.
By understanding these 10 critical Primavera licensing facts, organizations can avoid common pitfalls, ensure compliance, and effectively manage their Primavera license investments.
