P6 Professional vs EPPM
Last reviewed 16 September 20267 min read
Desktop vs web — same database, different doors, and which one a planner actually needs
🟩 In one line: P6 Professional is the Windows desktop application planners build and update schedules in; P6 EPPM is the web application a PMO or client uses to govern many projects, dashboards, portfolios and team-member progress on top of the same database; a contractor's planner lives in Professional, submits XER to whichever the client runs, and needs to know EPPM only well enough to understand why the client's global data is locked and their layouts look different.
👤 Who this is for: J/M. Prerequisites: p6-eps-obs-and-enterprise-data, importing-and-exporting-xer.
First, let's be honest about why this page exists
Job adverts say "P6" and mean either. A planner who has only used Professional standalone logs into a client's EPPM and cannot find Reflections, cannot create a global code, and is told the project is "checked out." A PMO analyst who has only used EPPM asks the contractor to "just publish to the portfolio." Neither side is wrong; they are using two products on one database.
This page is a map, not a manual. The mechanics of scheduling are identical in both.
🟨 The standard — what "good" looks like
| Source | What it asks for (paraphrased) | Relevance |
|---|---|---|
| AACE RP 38R-06 | Basis states the software and version | "P6 Professional 20.12" or "P6 EPPM 21.x web" — say which |
| Client schedule specifications (typical Gulf) | Native file format and version; sometimes direct access to the Employer's EPPM | Determines whether the planner works in Professional and exports, or works inside the client's database |
| PMI Practice Standard for Scheduling, 2nd ed. | Schedule model maintained in a controlled environment | Both qualify; EPPM adds governance |
| Convention (p6-global-vs-project-data) | Global data owned by the admin; project data by the planner | EPPM enforces this by role; Professional relies on discipline |
🟢 Rule: build and update in Professional; know which product the client runs and what it does to global data, check-in/check-out and access; submit XER (or XML where specified) regardless; record product and version in the SBM and every transmittal.
How it actually works
1. Side by side
| P6 Professional | P6 EPPM | |
|---|---|---|
| Interface | Windows desktop application | Browser (web client), plus optional Professional as a connected client |
| Database | Standalone (local) or shared enterprise DB | Shared enterprise DB only |
| Typical user | Planner, delay analyst, scheduler | PMO, portfolio manager, client controls team, team members entering progress |
| Building and editing activities, logic, calendars | Full | Full in the web client, slower for bulk work; most EPPM sites give planners Professional as the editing tool |
| Scheduling (F9), options, multiple float paths | Yes | Yes (web "Schedule" service; same options) |
| Reflections | Yes | Not in the web client (check against your copy); planners with Professional connected to the EPPM DB can use them |
| Schedule Comparison (Claim Digger) | Yes (Professional) | Not in the web client; via Professional or Visualizer-type reporting (check against your copy) |
| Global Change | Yes | Yes (web) |
| Baselines | Maintain / Assign | Same, plus portfolio-level baseline views |
| Layouts | User / project / .plf export | Web views; separate from Professional layouts |
| Portfolios, dashboards, scorecards | No | Yes — the main reason EPPM exists |
| Team Member / timesheets / progress entry by non-planners | No | Yes |
| Risk register (project risks) | Basic risks tab | Fuller risk module (web) |
| Document management, workflows | No | Yes |
| Security and access | OBS + user profiles | Same model, more granular, usually locked down |
| Check-in / check-out | Yes (rarely used standalone) | Common — a checked-out project is read-only to others |
| Import / export XER, XML | Yes | Yes |
| Where global data is created | Enterprise menus, by anyone with rights | Administration pages, usually admin-only |
| Reporting | Built-in reports; export to Excel | BI Publisher / web reports (check against your copy) |
A note on names: "Primavera P6" without qualification usually means Professional; "P6 Web" and "P6 EPPM" mean the web product; Oracle Primavera Cloud is a separate, newer product with its own file format and is not P6 EPPM — referenced here only so the names are not confused.
2. Three working arrangements
| Arrangement | Who has what | What the planner does |
|---|---|---|
| Contractor standalone | Professional on a laptop or company DB; client has Professional or nothing | Build, update, export XER; client imports |
| Client runs EPPM, contractor submits files | Professional on the contractor side; EPPM at the client | Same as above; client's PMO imports into their EPPM under a Received node; client's global data rules apply on their side |
| Contractor works inside the client's EPPM | Client grants OBS access; planner uses the web client or Professional connected to the client DB | Everything the planner creates is in the client's database: project calendars and project codes only; no global objects; check-out discipline; baseline register still kept, but baselines created by whoever the client's procedure says |
The third arrangement is where most friction happens. The planner cannot create a Notebook topic, a UDF or a global code without a request, cannot see the Reflections menu in the browser, and finds the project checked out by the client's reviewer on update day.
3. What changes in practice
| Topic | Professional habit | In EPPM |
|---|---|---|
| Layouts | Six .plf files (p6-layouts-and-filters) | Rebuild as web views, or connect Professional and import the .plf |
| Reflections / what-if | Right-click → Create Reflection | Copy the project to a What-If node via the web, or use Professional connected |
| Global Change proof | Reflection + comparison | Copy project + Professional comparison, or export both and compare in Professional |
| Global data | Project-level by discipline | Enforced by role; ask the admin |
| Check-out | Rare | Check out before editing, check in after; agree a window with the client's reviewer |
| Version | Record Professional build | Record web version and, if used, the connected Professional build |
| Submission | XER | XER unless the client wants XML with baselines; some EPPM clients ask for the project to be "published" rather than exported — confirm which |
4. Which to learn
Professional first — every mechanic in this hub is written from it. EPPM second, for the roles that need portfolio reporting: client-side controls, PMO, consultant review teams. A planner who can do the monthly update, a TIA and a recovery plan in Professional can learn the EPPM navigation in a week.
🟥 Where people go wrong
- Assuming the client's EPPM will accept whatever the XER carries. Their import is governed; global calendars in your file are refused or overwritten by policy. Project calendars only, transmittal note listing globals (p6-global-vs-project-data).
- Looking for Reflections in the browser. They are not there. Copy to a What-If node, or use Professional connected to the same database.
- Editing a checked-out project. Read-only, silently. Check the status line; agree an update window.
- Creating a UDF in the client's database. You cannot, or you can and shouldn't. Request it; the admin creates once.
- Writing "P6" in the SBM. Product and version, so a reviewer opening the file knows which behaviours to expect.
- Using the web client for bulk editing. Slower than Professional for 400 remaining durations. Professional connected, or spreadsheet import.
⚖️ When you're challenged
"Just publish your project to our portfolio." Our schedule is built in Professional on our database; the deliverable under the contract is the XER with the narrative. If the Employer wants it inside their EPPM, your PMO imports it under a Received node — I'll send the layout files and the transmittal listing the calendars and codes it carries so the import goes cleanly.
"You can't create that code here. Ask the administrator." Understood — that's the right governance. I'll use the project-level Area and Level codes I've already got access to, and request the Change Ref code through the admin today so it exists before the first variation.
📄 Related pages
- P6 EPS, OBS and Enterprise Data — the structures EPPM governs tightly
- P6 Global vs Project Data — why project-level matters more under EPPM
- Importing and Exporting XER — the submission route in both worlds
- P6 Reflections and What-If — Professional-only, and the workaround
- P6 Layouts and Filters — .plf files and web views
- P6 vs msp vs asta — choosing the tool at company level
✏️ Worked example
Consultant's review team in Abu Dhabi runs EPPM; contractor runs Professional 20.12 on a company database. Agreed arrangement, recorded in the SBM and the schedule specification response:
| Item | Agreement |
|---|---|
| Authoring tool | Contractor: P6 Professional 20.12 |
| Submission | XER + PDF Gantt + narrative + six .plf layout files + scheduling-options screenshot, monthly |
| Baseline | Accepted baseline XER issued separately per register; consultant imports both into EPPM under "Received – Contractor" |
| Global data in submitted files | Project calendars and project codes only; zero resources unless resource-loaded phase begins (then under a named node) |
| Consultant's comparison | Run in Professional connected to their EPPM database; comments issued as a comment sheet |
| Contractor access to EPPM | Read-only view of the imported project for reconciliation; no editing |
| Version conflicts | ERMHDR route (what-is-an-xer-file) if the consultant's DB lags; declared in the transmittal |
Result: twelve monthly submissions imported without a global-data incident. The only friction — the consultant's reviewer checking out the received copy during the contractor's read-only window — was solved with a calendar invite.
📖 References
- AACE International RP 38R-06, Documenting the Schedule Basis
- PMI Practice Standard for Scheduling, 2nd ed.
- Oracle Primavera P6 Professional User Guide; Oracle Primavera P6 EPPM User Guide and Administrator's Guide (feature availability per version and deployment — verify against the versions in use)
From the field
Notes, corrections and additions from people who've done this on a real job. Everything is checked before it appears here.
Loading notes…
Checked before it appears. No client, project or employer names. Your name is shown; your email never is. Terms.