Primavera integration

Your customer plans in Primavera P6. You plan in Linetrack.

In plant engineering and EPC projects the contract often states that the schedule has to be delivered in Oracle Primavera P6. Linetrack reads P6 schedules as .xer or Primavera XML and returns your plan as Primavera XML, with readable activity IDs, the project calendar and all four relationship types. Your team keeps planning design, manufacturing and installation in Linetrack, and the customer's scheduler gets a P6 file.

Ready-made connectionImport .xer and Primavera XMLExport as Primavera XMLUnscheduled tasks survive the roundtrip

Primavera P6 website ↗

In short

Primavera P6 is connected to Linetrack through file import and file export. Linetrack reads P6 schedules in .xer or Primavera XML format up to 200 MB, with project structure, milestones, dates and relationships, and returns any project plan via "Export as" as Primavera XML (PMXML). Unscheduled tasks are preserved: the export marks them [UNGEPLANT] and Linetrack recognises them again on re-import. The exchange works file by file; there is no live connection to the P6 database.

Import and export

What travels between P6 and Linetrack

The exchange runs on files that your project manager or the customer's scheduler produces anyway. We built both directions so that the same plan can move between the tools several times over the life of a project.

Import

Reading P6 schedules

Linetrack reads Primavera's XER export as well as Primavera XML, each up to 200 MB. You start the import with the button showing the Primavera logo, from "Import from" → Primavera P6, or by dragging the file onto the Gantt. Before anything is saved, the preview shows the project title, the number of tasks and the number of relationships.

  • .xer
  • Primavera XML
  • up to 200 MB
  • Project title
  • Tasks
  • Relationships

Where in Linetrack: Gantt in the project wizard for a new project and "Edit project", in templates and the detailed-planning template

ImportWBS

The WBS becomes the project structure

The WBS levels from P6 arrive as summary tasks, with the activities and their names beneath them. Linetrack recognises milestones by their flag or a duration of 0. Start and finish are taken over to the day, and activities without dates become unscheduled tasks.

  • WBS
  • Summary tasks
  • Activities
  • Milestones
  • Start
  • Finish
  • Unscheduled tasks
ImportCalendar

Recalculated on your calendar

Linetrack recalculates durations on the project calendar, with the working days and holidays of your plant. Relationships of all four types arrive with their lag in days, and auto-scheduling aligns the dates with them. Where the customer's calendar has different working days from your plant, you see it in the dates.

  • Finish-to-start
  • Start-to-start
  • Finish-to-finish
  • Start-to-finish
  • Lag in days
ExportPMXML

Handing it back as Primavera XML

From the Gantt of any project, archived ones included, the plan goes out via "Export as" → Primavera P6 as a PMXML file. It contains structure and order, summary tasks, milestones, dates, durations in working days and relationships with positive and negative lags. Task descriptions appear in P6 as notes.

  • Structure
  • Summary tasks
  • Milestones
  • Dates
  • Durations in working days
  • Lags +/−
  • Notes

Where in Linetrack: project Gantt → "Export as" → Primavera P6

ExportIDs

Activity IDs people can read

Every activity gets a readable activity ID in the export, plus a "Linetrack ID" field. The customer's scheduler finds the same tasks again in the next delivery, and when questions come up both sides talk about the same number. The project calendar travels with the file, holidays and exceptions included.

  • Activity ID
  • Linetrack ID
  • Project calendar
  • Holidays
  • Exceptions
Roundtrip

Unscheduled stays unscheduled

Tasks that do not have a date yet are marked [UNGEPLANT] in the export. The scheduler can see they are still open, and on re-import Linetrack reads them back as unscheduled tasks. We run the conversion in both directions on our own infrastructure; your plan is not sent to a third-party conversion service.

  • [UNGEPLANT]
  • Recognised on re-import
  • Own infrastructure

What this makes possible

Scenes from projects where P6 is mandatory

Delivery schedule for the EPC contractor

You are supplying the filling and packaging line for a new plant, and the EPC contractor keeps the overall schedule in Primavera P6. Once a month your project management sends the current status as a Primavera XML file. The contractor's scheduler loads it into the master schedule, and nobody on your side maintains a second plan in P6.

The framework schedule arrives as .xer

At kick-off the main contractor sends its framework schedule as an .xer file, with site release, installation window and mechanical completion. Project management reads it into a new project and has the customer's key dates in its own Gantt. Design, manufacturing and shipping are then aligned with those dates.

Capacity that P6 does not show

The customer's plan says when electrical design has to be finished, but not who does it. After the import, project management assigns the tasks in Linetrack to its own electrical designers and resource groups. The resource view shows that the date clashes with a parallel project before it is promised to the customer.

Commissioning without a date

When unit 2 is commissioned depends on the customer's utilities. There is no date yet, so commissioning sits in the Linetrack plan as an unscheduled task. In the P6 export it carries the [UNGEPLANT] marker, and when the plan comes back from the customer it is unscheduled again in Linetrack instead of holding a placeholder date.

Plant shutdown in the customer's calendar

Your plant is closed for the first three weeks of August, while the customer plans on a continuous calendar. The export takes your project calendar to P6, holidays and exceptions included. The scheduler can see for himself why final assembly only starts in September.

A question about one activity

The customer's scheduler calls because something has slipped in engineering. He reads out the activity ID from his list, and the readable ID together with the "Linetrack ID" field makes it clear at once which task he means. Both sides are looking at the same line, even though they plan in different tools.

How it works

From the .xer export back to P6

  1. 1

    File from the customer

    The scheduler at the customer or main contractor exports the plan from P6 as .xer or Primavera XML and sends you the file.

  2. 2

    Read in and check

    You drag the file onto the Gantt in the project wizard. The preview shows the project title, tasks and relationships, then you take the plan over.

  3. 3

    Plan in Linetrack

    Your team assigns hours and resources, adds its own detailed planning and carries on in the Gantt on your project calendar.

  4. 4

    Back as Primavera XML

    Before the status meeting you export the current plan via "Export as" → Primavera P6. The PMXML file goes to the scheduler, who imports it into P6.

In practice

How do suppliers in EPC, outage and wind projects work with Primavera P6 and Linetrack?

Linetrack reads the customer's P6 plan as .xer or Primavera XML, your team keeps planning manufacturing, installation and resources in Linetrack, and the current status goes back as Primavera XML. Three typical setups show how this looks in EPC plant engineering, power plant outages and offshore and wind energy supply.

EPC suppliers in refinery and chemical plant construction

Heat exchangers and piping modules for a chemical plant

Starting point
A manufacturer supplies heat exchangers and prefabricated piping modules to an EPC contractor. The contract requires a monthly schedule in Primavera P6. Until now the project manager built that file by hand from an Excel list, and it rarely matched the internal status.
How Linetrack is used
The project manager reads the contractor's master schedule into a new project as .xer and checks tasks and relationships in the preview. Below the customer's tasks, the team adds its own detailed planning: design, material procurement, welding, pressure testing, documentation, factory acceptance and shipping. The departments enter their dates directly in the Gantt. Before the progress meeting the plan goes out via “Export as” as Primavera XML to the contractor's scheduler.
Result
If the factory acceptance slips, it shows in the plan where design and manufacturing already work. The file for the contractor comes out of it by export, and the Excel list alongside is no longer needed.
Linetrack in machine and plant engineering →
Power plant outages

Service technicians for two outage windows

Starting point
A service company for turbines and generators is booked by power plant operators for outages. The operator keeps the outage plan in P6 and sets the shutdown window. The company's fitters and specialists, however, are scheduled for several outages, and the operator sees none of that. Its IT also does not open access for external partners.
How Linetrack is used
The operator sends the outage framework plan as a file, and the service company reads it into Linetrack. Project management assigns the work packages to fitters and resource groups and plans the overhaul of components in the workshop ahead of the shutdown. Work that depends on findings after opening sits in the plan as unscheduled tasks. In the export they carry the [UNGEPLANT] marker, so the operator can see they are still open.
Result
Before the service company commits to a crew, the resource view shows both windows side by side. The exchange stays file-based, and neither side has to open system access.
Resources and capacity in Linetrack →
Offshore and wind energy components

Tower sections and steel parts against the loading window

Starting point
A steel fabricator builds tower sections and foundation structures for a wind farm. The project developer plans in P6 and has fixed the port loading window and the use of the installation vessel. What matters to the supplier is whether welding, coating and inspection are finished in time for that window.
How Linetrack is used
Project management imports the customer's dates as .xer and keeps the loading date as a milestone in the Gantt. For each component it sets up cutting, welding, blasting and coating, inspection and loading, links them, and assigns them to the resource groups of the shop. If a component slips, auto-scheduling realigns the following tasks. Project management sends the status to the customer as Primavera XML.
Result
Project management sees a slip in coating before it endangers the loading window, and passes the updated status on to the customer as a file.
Project planning in Linetrack →

Examples without a reference label describe typical workflows in the respective industry and therefore name no company.

FAQ

Frequently asked questions

Any questions?

Book a call with our team.

Does Linetrack also export .xer files?

No, the export produces Primavera XML (PMXML). P6 reads this format through its import, in P6 Professional as well as P6 EPPM. For importing into Linetrack both formats work, .xer and Primavera XML.

Is there a live connection to the customer's P6 database?

No. The exchange runs on files: the customer sends an export, you send an export back. Neither your IT nor the customer's has to open access to the other side's system.

What does Linetrack take over from a P6 plan?

The schedule: the WBS as a structure with summary tasks, activities with their names, milestones, start and finish dates, and relationships of all four types with lag. Linetrack recalculates durations on your project calendar. You then assign hours and resources in Linetrack to your employees and resource groups.

What if the customer uses MS Project instead of Primavera?

Then it works the same way. Linetrack reads .mpp and MS Project XML and exports MS Project XML. The details are on the MS Project integration page.

The platforms and brands mentioned belong to their respective owners. Mentioning them describes the technical connection and does not imply a partnership or certification.