The schedule nobody looks at
A three-month programme doesn't tell a foreman what to finish this week.
Keep Primavera P6 as the schedule of record. BuildCore reads it for portfolio dashboards, imports it for look-aheads and weekly plans, and measures what actually gets done — PPC, the reasons tasks slip, and the constraints that stop a workfront.
A three-month programme doesn't tell a foreman what to finish this week.
Without PPC and reasons, the same constraint stops work week after week.
Hours go into rebuilding S-curves and milestone lists by hand.
The latest P6 schedule comes in as XER.
Pull the next three weeks' activities.
Weekly work plans agreed with the crews.
Constraints closed before the crew arrives.
Daily plans and progress reports from site.
PPC and its reasons, trended.
No. The live dashboards are read-only, and XER import brings a copy of the schedule into BuildCore's own module. P6 stays the schedule of record.
The live dashboards need a SQL Server-hosted P6 database. On Oracle, export XER files and import them into BuildCore's schedule module.
Yes. Each task closed as not completed carries its reason, and the reasons are trended alongside PPC.
Modules on this page: APM — Primavera P6 · Construction PM
Tell us about your projects and we'll show you the parts of BuildCore that matter to you.