Editions and Licensing: Which P6 Are You, And Are You Allowed To Use It?

"Tools don't manage projects. People do. But the wrong license turns people into pumpkins at midnight."

Remember in the last section when we met Primavera P6, the heavy-lifting gym bro of project scheduling? Cool. Now let’s talk about the two big questions that decide your day-to-day reality: which edition you actually use, and whether you’re licensed to click the buttons you plan to click.

Yes, this is the part where we summon the Software Licensing Goblin. Stay brave. We’ll make it painless(ish).

---

The Two Big Flavors of P6 (And a Sprinkle)

There are two main editions you’ll see in the wild, plus a standalone sprinkle for tiny teams or lone-wolf schedulers.

1) P6 Professional (aka PPM)

• Best for: Power schedulers who live inside CPM logic, baseline management, resource leveling, and want max speed on the desktop.
• Interface: Windows desktop client. Lightning fast. Keyboard ninjas rejoice.
• Database: Connects to Oracle DB / SQL Server, or a local SQLite DB in "Standalone" mode.
• Collaboration: Works for teams, but collaboration/reporting/governance usually stitched together with shared DBs, integrations, or exports.

2) P6 EPPM (Enterprise Project Portfolio Management)

• Best for: Organizations with portfolios, approvals, web-based workflows, timesheets/progress collection, dashboards, and governance.
• Interface: Web application (for most users) + optional P6 Professional client for planners who still want the desktop speed.
• Database + App: Centralized database with an application server; designed for many users.
• Collaboration: Built-in timesheets (Team Member), web updates, portfolio views, role-based access, audit trails.

"Standalone" Mode (sub-flavor of P6 Professional)

• Use when: You’re solo or piloting. It uses a local SQLite DB—simple, quick, no IT saga.
• Limitation: Not for large teams/enterprise governance.

Shortcut memory: Professional = desktop speed demon. EPPM = enterprise mothership. Standalone = quick solo ride.

---

On-Prem vs Cloud: Same Brain, Different House

• On-Prem EPPM: Your IT hosts the database and app server. You own the plumbing.
• Cloud (Oracle-hosted) EPPM: Oracle hosts it as a subscription (the "Cloud Service"). Same functional DNA, but infrastructure is included and upgrades/patching are managed for you.

Important: Oracle Primavera Cloud (OPC) is a separate, newer product family (planning, risk, tasks) that is not the same as P6, though they can coexist. Today we’re talking P6.

---

Licensing 101 (Without The Tears)

Oracle licensing evolves, but the core ideas you’ll see commonly are:

• P6 Professional (PPM): Typically licensed per person as a Named User Plus (NUP). Translation: one license per individual who uses the software.
• P6 EPPM (On-Prem): Typically licensed per user under an Application User-type metric. Roles matter (planner vs team member), but it’s still per human.
• P6 EPPM Cloud Service: Subscription per user (monthly/annual). Infrastructure baked in.
• Team Member licenses: Lighter, for timesheets and progress updates. Cheaper than full planner licenses, functionally narrower.

What this means in practice:

• No license sharing. One human = one license. Your cousin borrowing your login “just once” is not a personality trait, it’s a compliance risk.
• External contractors need licenses too if they use the tool.
• Training/sandbox users still count if they’re real users. Many orgs provision a few “non-prod” users intentionally.
• Maintenance/support (for perpetual licenses) is separate; it covers updates and support services.

Not legal advice. Always confirm licensing terms with Oracle or a certified partner for your contract, configuration, and geography.

---

Quick Comparison Table

Edition	Interface	Database	Deployment	Best For	Not Great At
P6 Professional (PPM)	Windows desktop	Oracle/SQL Server; SQLite for Standalone	Local or networked DB	Deep scheduling, rapid data entry, power users	Enterprise approvals, broad web access without add-ons
P6 EPPM	Web + optional Pro client	Central DB + app server	On-Prem or Oracle Cloud	Portfolio governance, timesheets, workflows, dashboards	Ultra-fast offline desktop-only workflows without Pro client
P6 Pro Standalone	Desktop	SQLite (local)	Local machine	Pilots, solo schedulers, training	Multi-user collaboration/governance

---

Who Uses What (No Judgment, Just Vibes)

• Small team, 1–5 schedulers, fast turnarounds, minimal governance: P6 Professional (maybe Standalone to start) is your espresso shot.
• Mid-to-large org with PMO, many contributors, executive dashboards, audit needs: P6 EPPM. Add Pro client for advanced planners.
• Field teams just marking progress via phone/portal: EPPM with Team Member licenses.

---

Common Myths (That Need To Retire)

• "EPPM is the new version of Professional." False. They coexist. Think web mothership + optional desktop turbo.
• "We have EPPM, so planners don’t need Professional." Often false. Power schedulers usually need the desktop client’s speed and features, even when the database is EPPM.
• "Concurrent licenses are fine; we’ll just share logins." Not how Oracle typically licenses P6. Named-per-user is the usual world here.
• "Cloud means no licensing headaches." Fewer headaches, yes. Zero? Absolutely not. You still need the right number and type of user subscriptions.

---

Decision Tree (Tiny, but Mighty)

START
  Do you need web-based access, timesheets, workflows, and portfolio dashboards?
    YES -> Choose EPPM
      Do planners need desktop speed and advanced scheduling?
        YES -> EPPM + P6 Professional client for planners + Team Member for contributors
        NO  -> EPPM with web only + Team Member
    NO -> Choose P6 Professional
      Multi-user DB or just you?
        JUST ME -> P6 Pro Standalone (SQLite)
        TEAM   -> P6 Professional with shared Oracle/SQL Server DB
END

---

Real-World Scenarios (Because Reality Is Messy)

1. Two schedulers, ten projects, weekly updates from email

• Edition: P6 Professional (shared DB)
• Licensing: Two Named User licenses
• Tip: Consider a viewer/reporting tool if managers want read-only visibility

2. Global PMO, 200 projects, exec dashboards, team updates from the field

• Edition: EPPM + Pro client for planners + Team Member for field
• Licensing: Mix of Application Users / Cloud subscriptions; Team Member licenses for contributors
• Tip: Governance matters—use portfolios, user roles, and workflows

3. A pilot to convince leadership

• Edition: P6 Pro Standalone for the scheduler
• Licensing: Single Named User; later upgrade to shared DB or EPPM as you scale
• Tip: Document ROI with baselines, resource histograms, and “before/after” slippage

---

Compliance Traps (How To Not Accidentally Summon Auditors)

• Shared logins: Don’t. Audit logs + access control will rat you out.
• Forgotten contractors: Offboard licenses when they leave; onboard when they join.
• Dev/Test/Prod confusion: Track non-production user counts; align with contract terms.
• Middleware/database assumptions: On-Prem EPPM may require separate licensing for the database and app server stack. Cloud bundles this.

Create a simple register:

• Who has which license type?
• Which environment(s) do they access?
• When was it last reviewed?

---

Buying Smart: Questions For Your Team

• How many true schedulers vs casual updaters do we have?
• Do we need timesheets and workflow approvals?
• Do we want Oracle to host it (Cloud) or do we have IT capacity (On-Prem)?
• What integrations are in play (ERP, BI, cost, risk)?
• What’s our governance model—portfolio reviews monthly, quarterly, never? (Please don’t say never.)

---

TL;DR and Takeaways

• P6 Professional = desktop speed + deep CPM for planners. Great for small teams or as the planner front-end even in EPPM.
• P6 EPPM = enterprise web platform with timesheets, workflows, dashboards. Add Pro client for power users.
• Licensing is usually per user. No sharing. Cloud simplifies hosting, not governance.
• Match license types to roles: planners vs contributors. Save money, stay compliant.

The right edition + the right license = fewer roadblocks, cleaner data, happier projects. Your schedule won’t magically behave—but you’ll have the right seatbelt when it doesn’t.