Primavera P6 holds the programme — the activities, the logic, the dates the contract demands. It does not know that zone B4 passed factory QC on Tuesday, or that 40 of the 60 panels on Level 12 are installed. Muthari OS knows exactly that, at zone level, because the storekeeper, the QC engineer and the site engineer wrote those records as the work happened. For contractors who fabricate what they install, these are two different jobs, and neither system should pretend to do the other’s.
The master programme: activity logic across every trade, the critical path, resource levelling, the contractual baseline the delay story will be argued on. Your planner keeps P6, and the programme stays the programme.
What actually happened, per zone: the drawing revision it was released to, material received and issued, each production stage stamp with actor, role and time, the delivery note it left on, installed quantity recorded daily and capped at the zone quantity, the inspection verdict. None of it is a percentage somebody typed.
When the planner asks where Level 12 is, the answer is not a feeling from the foreman. It is a set of installation entries with names and timestamps, an inspection request with its verdict code, and a stage history that shows how long the zone sat in coating. The number the programme gets updated with has a record behind it.
Your own stages, in your own words — engineering, procurement, production, coating, delivery, installation — with a date and a duration on every BOQ line, and on an individual zone where it differs. The stages are yours to name, because a façade contractor’s run is not a generic template. The project’s own start and finish are worked out from the lines; you never type them twice.
Each stage says which recorded event finishes it — QC passed, dispatched, delivered, installation complete. The actual date is then read off that record rather than typed by anyone, so the delay is the gap between a date your engineer planned and a stamp your team made. A stage nobody planned is never reported as on time. The Command Center lists what is behind programme, worst first.
Chart, calendar, Excel, and MS Project XML — which Primavera P6 imports. P6’s own file type, XER, is a closed format and we do not write it; we will not call an export an integration either. There is no live link between the two systems, and the file your planner opens is the whole bridge.
P6 for time, your ERP for money, Muthari OS for the execution record between them — the system of record for what physically happened to every zone and every batch. Built by contractors in the trade, for companies that run a factory and a site. See also Muthari OS vs a construction ERP.