How to open a Primavera P6 XER file without P6

What exactly is a Primavera P6 XER file?

An .xer file is a text-based export used by Oracle Primavera P6 to exchange project data. It is not a PDF or a set of Gantt screenshots. Instead it contains tabular sections, with records for activities, WBS nodes, calendars and relationships. That is why opening an XER in a plain text editor is possible but rarely useful for a schedule review.

For example, the TASK table stores activity records, TASKPRED stores dependencies and PROJWBS stores WBS hierarchy. To make sense of a programme you must interpret these records together—especially when an activity date is influenced by several relationships or calendars.

How to open an XER without Primavera P6

1. Export or obtain an XER from the scheduler responsible for the current Primavera P6 programme. Note the revision and data date so you can identify what was actually issued.
2. Open the SEQNCS free XER Viewer. Choose a supported .xer file from your computer. A P6 licence or installation is not needed simply to inspect it in SEQNCS.
3. Start with the fitted overview. Check the project hierarchy and visible date range rather than drawing conclusions from a single activity.
4. Use WBS and Activity Codes included in your export to group the programme. Search by ID and name, then inspect relationships where available.
5. Export a PDF when you need a shareable read-only view. Make actual logic or date changes in the planning system, not in the viewer.

A real example from the included demonstration XER

The SEQNCS Metro L4 demonstration file is synthetic; it is supplied with SEQNCS for product testing and does not contain a customer's schedule. Counting the export's records gives a useful illustration of why a structured viewer helps.

One activity record is PM001, “Monthly Project Controls Cycle 01”. Its activity ID, description, WBS reference, dates and logic data live in different columns or sections of the file. The viewer brings this information into the same review context.

Download the synthetic demonstration XER to see the same source data, or use the demo flow on the SEQNCS homepage.

What should you inspect first?

WBS and structure

Are stations, buildings, packages or disciplines grouped the way the project team expects? WBS codes and Activity Codes are useful navigation aids, but their quality depends on the export. An unlabeled or inconsistent code should not silently become a factual discipline assignment.

Dates and milestones

Confirm the source data date, then look for key milestones and time windows. Zooming can help with a meeting, but visual bar positions alone do not tell you whether a forecast is realistic.

Relationships and logical sequence

Review predecessor/successor relationships where the file contains them. Missing logic, unusual lags and constraints can make apparently tidy dates misleading. To assess schedule-quality rules, use the free DCMA Schedule Check.

PDF sharing and limitations

When exporting, check the date range, visible columns and grouped activities. A PDF is a snapshot for discussion, not a replacement for the underlying XER or a signed scheduling submission.

When should you compare two XER files?

A single viewer answers “what is in this schedule?” Revision comparison answers “what changed?” If you have a baseline and an update, open Schedule Explorer COMPARE to inspect added and removed activities, milestones and changed relationships.

Comparing revisions is not, by itself, a delay analysis or a contractual entitlement assessment. Always distinguish record-level changes from their actual effect on the project completion date.