P6 Professional vs P6 EPPM vs Primavera Cloud (Version 26)

Before you learn a single P6 command, you need to know which P6 you are looking at. "Primavera" covers several products, and the one a contractor uses may not be the one an owner should buy. This lesson sorts out Oracle Primavera P6 Professional, P6 EPPM and Oracle Primavera Cloud as they stand in Version 26, and shows which one an owner needs to review a contractor's schedule.

Learning outcomes

• Tell apart P6 EPPM, P6 Professional and Oracle Primavera Cloud, and say which are desktop, web or cloud.
• Explain the three common ways P6 Professional is set up: standalone, connected on-premises and connected to Oracle's cloud.
• Explain what XER and P6 XML files carry, and why the difference matters when a contractor submits a baseline.
• Choose a sensible P6 set-up for an owner who receives contractor schedules.

The lesson

One family, two scheduling products

Oracle sells two separate families for project scheduling. The first is Oracle Primavera P6, the critical path method (CPM) tool most Canadian general contractors, schedulers and claims consultants have used for decades. The second is Oracle Primavera Cloud, a newer product built for the cloud from the start. They share a name and a heritage, but they are different products with different data models [1][4].

Inside the P6 family there are two main pieces you will hear about every day:

• P6 EPPM (Enterprise Project Portfolio Management). This is the enterprise system: a web application used in a browser, sitting on an enterprise database. Oracle describes the web application as the main place to administer and manage projects, with an extended schema of reporting views in the database [2].
• P6 Professional. This is the Windows desktop application for planning and scheduling. It is what most schedulers mean when they say "P6". It can run on its own, or it can connect to an EPPM database, and some of its features only work when it is connected [2].

Around them sit companion pieces: P6 Team Member, which lets field staff report status through a browser, a mobile app or email; P6 EPPM Web Services for integrations; and reporting tools such as Primavera Analytics and Primavera Data Warehouse [2][3].

Version 26: what the number means

Oracle numbers P6 releases by year. The current documentation library is Version 26, covering P6 EPPM in both cloud and on-premises deployments; Oracle notes that most of the content is the same for both, and that anything specific to one deployment is labelled [3]. The Version 26 client requirements also cover P6 Professional and P6 Professional Cloud Connect [5].

The cloud and on-premises versions do not move at the same pace. For single-tenant P6 cloud customers, Oracle describes feature releases twice a year, critical patches quarterly and bug fixes monthly, and expects cloud environments to stay within two versions of the general release [6]. An on-premises customer decides when to install a new release. Oracle Primavera Cloud, by contrast, states that it adds new capabilities every month [4].

Three ways to set up P6 Professional

The same P6 Professional program behaves differently depending on what database it is pointed at. Oracle's migration guide makes this point directly: P6 Professional can connect to an EPPM schema, a PPM schema or a SQLite database, and a comparison of features only makes sense once you know which [7]. For an owner, three set-ups cover nearly every case.

A. Standalone. P6 Professional runs on one computer and stores its data in a local SQLite file. Oracle has a separate installation guide for this "standalone" configuration [8]. It is the cheapest and quickest way to open a contractor's file, and it works offline. Its limit is that it is a single-user database on one machine: there is no shared repository, and the enterprise features that depend on EPPM are not there.

B. Connected, on-premises. Your organization (or its IT provider) installs the P6 EPPM database and web server. Schedulers use P6 Professional on the desktop; managers and reviewers use the P6 web application in a browser; both read the same data [2]. You control upgrades, backups and access, and you carry the IT work.

C. Connected, Oracle cloud. Oracle hosts the EPPM database and web application. Browser users simply log in. Desktop users connect P6 Professional through Cloud Connect, which links the desktop client to an EPPM database in the cloud [2]. You trade IT effort for a subscription and Oracle's release cycle.

Desktop or web: who uses which

A common beginner question is whether "P6 is a web app now". The honest answer is: partly. In an EPPM set-up, most administration, portfolio views, dashboards and project review can be done in the browser, and team members can report progress without ever seeing a Gantt chart [2]. Many professional schedulers still build and update detailed CPM schedules in P6 Professional, because the desktop client is fast and familiar for heavy editing. Both clients work on the same database, so the choice is about the user's job, not about where the data is.

Oracle Primavera Cloud is browser-based throughout. Its scheduling screens look different, and so does its structure: Oracle's own guide for schedulers moving from P6 notes, for example, that P6 allows several EPS root nodes, while Primavera Cloud uses a single root workspace with workspaces beneath it [9]. We use the EPS heavily in Lesson 3, so this difference matters if you ever migrate.

XER and P6 XML: the files that move between parties

On a construction project, the schedule usually travels as a file. P6 Professional reads and writes several formats, but two carry native P6 data [10]:

• XER is Oracle's proprietary P6 exchange format. It carries project, resource and role data and can hold several projects in one file. It does not carry baselines. It also imports with fewer safeguards: a failed import can leave a partial result.
• P6 XML shares project and baseline data between P6 databases, enforces user security on import, opens the project exclusively and rolls back a failed import rather than leaving half of it.

P6 Professional also exchanges spreadsheets (XLSX) and Microsoft Project formats (MPX and Microsoft Project XML, with version limits) [10]. Oracle Primavera Cloud can import P6 XML or XER data too, but it converts the data into its own structure [11].

The baseline point catches owners out. If a contractor sends only an XER of the current update, the owner cannot see the accepted baseline inside it. Either ask for the baseline as its own project in the file, or ask for P6 XML where you need baselines to travel with the project.

Northgate worked example

Northgate Distribution Centre (fictional) is a 12,000 m² tilt-up warehouse in Vaughan, Ontario, built by Halvorsen Builders Ltd. (fictional) for Northgate Logistics Inc. (fictional) under a CCDC 2-2020 stipulated price contract. Halvorsen schedules in P6 and submits native XER files. The owner keeps its master schedule in Microsoft Project desktop. See the Northgate fact sheet.

The owner's PM asks a simple question before the contract is signed on January 11, 2027: "Which Primavera do we need?" Here is how the owner's representative works through it.

1. What must the owner do with the files? Open each XER, check logic and float, compare each update with the accepted baseline, and keep every submission as received. That is review work, not schedule building.
2. How many people need access? At least three: the owner's scheduler (edits review copies), the owner's PM and the owner's representative (view and comment). One person on one laptop is not enough.
3. Is security needed? Yes. In Lesson 3 we set up an EPS that separates the accepted baseline, the GC's untouched submissions and the owner's review copies, with OBS-based access. That needs a multi-user database with users and security profiles, which standalone SQLite does not provide.
4. Does Northgate have P6 servers? No. It is a logistics company, not a contractor.

Decision. Northgate keeps its own P6 database: P6 Professional for the owner's scheduler, connected through Cloud Connect to an Oracle-hosted EPPM database (set-up C), with browser access for the PM and owner's representative. A standalone copy of P6 Professional is kept on the scheduler's laptop only as a scratch tool. Primavera Cloud is not chosen, because Halvorsen submits P6 files and the owner wants to review them in the same data model they were built in.

The file rule written into the Supplementary Conditions. Each schedule submission includes the native XER of the update, the accepted baseline as a separate project (or P6 XML), and the P6 version used.

Owner's move

Owners do not need to schedule like a contractor, but they do need to read the contractor's schedule in its native form. A PDF of a Gantt chart hides logic, constraints and float. Demand, check and reject as follows:

• Demand native files. Require the native XER with every schedule submission, the baseline in a form that carries it, and a statement of the P6 version. Put it in the specification, not just in a meeting.
• Check that you can open them before award. Ask bidders for a sample XER and import it into your own database. You find version or format problems before they become a dispute.
• Own your database. Keep the owner's copy of every submission in a database the owner controls, not on the contractor's server or in a consultant's personal file.
• Reject "PDF only" submissions and reject a schedule tool switch mid-project unless the contract allows it and the data transfers cleanly.

View the data

Criterion	Standalone P6 Pro	P6 Pro + EPPM	Primavera Cloud
Open and review a GC's XER	Good	Good	Partial
Several reviewers, one database	No	Good	Good
User security and EPS/OBS access	No	Good	Partial
Browser access for the owner's PM	No	Good	Good
Same data model as the GC's P6 file	Good	Good	Partial
IT effort to stand up	Good	Partial	Good
Cost and set-up for a single project	Good	Partial	Partial

Screenshot to come

Screenshot to come

Screenshot to come

Common mistakes

1. Thinking Primavera Cloud is just P6 in a browser. It is a separate product with its own structure. P6 EPPM in Oracle's cloud is still P6.
2. Buying a single standalone licence and expecting a team tool. Standalone P6 Professional uses a local SQLite file on one computer. Fine for one reviewer; not a shared, secured owner database.
3. Accepting XER files without the baseline. XER does not carry baselines. Without the accepted baseline you cannot measure slippage properly.
4. Not recording the P6 version. A version mismatch is found at the worst moment, often when a claim is being prepared.
5. Importing contractor files over the live project. Always import into a separate submissions area and work on copies.

Quick quiz

1. Which statement best describes P6 Professional?

   1. A browser-only scheduling tool
   2. A Windows desktop client that can run standalone or connect to an EPPM database
   3. Another name for Oracle Primavera Cloud
   4. A reporting add-on for Microsoft Project

2. Standalone P6 Professional stores its data in:

   1. A local SQLite database
   2. Oracle's cloud
   3. An XER file only
   4. The contractor's server

3. What does Cloud Connect do?

   1. Converts XER to XML
   2. Connects P6 Professional to an EPPM database hosted in the cloud
   3. Migrates P6 projects to Primavera Cloud
   4. Publishes schedules as PDFs

4. A contractor sends an XER of Update 3. What will the owner not find inside it?

   1. Activities
   2. Relationships
   3. Resources
   4. Baselines

5. Northgate needs three people to review GC files with EPS-based security, and has no servers. Which set-up fits best?

   1. Standalone P6 Professional on one laptop
   2. PDF review only
   3. P6 Professional connected through Cloud Connect to Oracle-hosted EPPM
   4. Oracle Primavera Cloud, because it is newest

Show answers and explanations

1. B. P6 Professional is the Windows desktop client; it can work alone or connected to an EPPM database.
2. A. Oracle's standalone installation guide describes SQLite as the storage for standalone P6 Professional.
3. B. Cloud Connect links the desktop client to an EPPM database in Oracle's cloud.
4. D. XER carries project, resource and role data but not baselines. Ask for the baseline as a separate project or use P6 XML.
5. C. It gives a shared, secured database without owner-run servers, in the same data model the GC uses. Primavera Cloud could work but converts P6 data into a different structure.

Key terms

P6 EPPM

Oracle's enterprise version of P6: a web application and enterprise database, deployed on-premises or in Oracle's cloud.

P6 Professional

The Windows desktop P6 client for planning and scheduling.

Standalone

P6 Professional working with a local SQLite database on one computer.

Cloud Connect

The connection method that links P6 Professional to a cloud-hosted EPPM database.

Oracle Primavera Cloud

A separate, cloud-native Oracle product for scheduling, resources and risk, with its own data model.

XER

Oracle's proprietary P6 exchange file; carries projects, resources and roles but not baselines.

P6 XML

An XML exchange format for P6 that carries baselines and enforces security on import.

References

1. Oracle, Primavera P6 Enterprise Project Portfolio Management (product page, with migration path to Primavera Cloud).
2. Oracle, Working with the Oracle Primavera P6 EPPM Suite, P6 EPPM System Architecture Data Sheet (Version 24).
3. Oracle, P6 EPPM User and Integration Library, Version 26.
4. Oracle, Oracle Primavera Cloud (product page and FAQ).
5. Oracle, P6 EPPM Client System Requirements, Version 26, and Other Primavera Applications.
6. Oracle, P6 and Unifier Cloud release cycle.
7. Oracle, P6 vs. Primavera Cloud: A Quick Reference (P6 EPPM migration guide).
8. Oracle, P6 Professional Installation and Configuration Guide (Standalone), Version 25.
9. Oracle, Key differences between Oracle P6 and Oracle Primavera Cloud.
10. Oracle, P6 Professional Importing and Exporting Guide: Import/Export file formats (Version 23).
11. Oracle, Import P6 XML or XER Data into Oracle Primavera Cloud.

Verified on November 4, 2026.

Next lesson in this trackInterface tour and navigation