Primavera P6

P6 stays with the planner. The owner’s copy stays live.

Most data center programmes already plan in Primavera P6. TerraForge does not ask the planner to abandon it. The owner gets the dates, logic and progress on the same project as the cost sheet, the contract and the RFI.

Request a demo Portfolio, programme, project

TerraForge Schedule Manager with Update from P6, a baseline toggle, and an activity open for edit — P6 · XER and XML · baseline kept

One schedule, two seats

The planner updates P6. The owner reads Schedule Manager, including critical path and baseline.

The file is the exchange

Import an XER or Primavera XML, then update that schedule in place. Activities match on the P6 ID.

Progress is not a Friday paste

Update from P6 sits on the schedule the programme dashboard already reads.

How it connects

XER or XML in. Update in place. Baseline stays here.

Update from P6 is the button on the planner. It re-imports a newer XER or Primavera XML into this schedule. Activities match on the P6 ID: changed dates and progress are applied, new activities are added, and missing ones are flagged. Nothing changes until the import is confirmed. Keep the TerraForge baseline and slippage is computed against it.

The same bar sets the baseline, toggles the grey baseline bars, links activities, adds one, or reschedules. Edit activity holds duration, percent complete, the parent WBS, the constraint, the actual dates, a cost code and the dependencies. Open REST and signed webhooks are the integration surface for other systems. They are not a live two-way link to P6.

The programme team owns it. Same navigation at portfolio, programme and project. Same My Tasks inbox. App Builder publishes the next step on a Tuesday, without a vendor ticket.

TerraForge Schedule Manager showing Update from P6, Set baseline, and the activity editor with dependencies — Update from P6. A newer XER or XML, on the schedule of record. The TerraForge baseline can be kept.

What the owner does with it

Slippage is read on the owner’s schedule.

UPS lead time, utility phasing and energization are visible as activities with float. A programme manager compares projects in the campus on the same Gantt language.

The portfolio cockpit can surface the consequence in a review. The schedule record stays in Schedule Manager.

What ships

Turnkey on arrival. Configurable after go-live.

Primavera P6

XER and XML: Import onto the project or the programme.
Update from P6: A newer export updates the same schedule, matched on P6 activity ID.
Baseline kept: Slippage is computed against the TerraForge baseline.
Schedule Manager: Critical path, baseline, float and variance after the data arrives.
Cost code: An activity can carry the CBS code the cost sheet already rolls.
One project record: Cost, contract, cash flow and field read the schedule’s project.

See the full PMIS against your campus programme.

Your cost codes, your workflow, your campuses. Write sales@terraforge.build.

Request a demo