Our Approach · Execution
In-Event Critical Mass Control reads every daily P6 update and answers the questions the turnaround manager has to decide on: is the finish still supported, and when can each craft step down without putting it at risk?
Request a pilot replay Take the free 24-question self-assessmentNot sure this is the right starting point? See all three free assessments.
Once bulk work winds down, every day brings the same decision: hold crews or release them. Hold too long and the event pays for heads with no work in front of them. Release too early and the remaining critical work stalls, and released crafts are not re-hired mid-event.
That decision is usually made on an event-wide S-curve and experience. But holding heads is always a craft question, never an event total. Pipefitters, boilermakers, catalyst crews and electricians each finish on their own date, and the event curve hides all of them.
Every update, the work still needed to reach the target is compared with the rate the crews are actually earning over the last five working days. While the earned rate keeps up, the event is logic-bound: the network sets the finish date. Once the rate falls below what is required and stays there, the event is throughput-bound: crews and productivity set the finish, and the P6 date will slip unless throughput rises. The update where that happens is the tipping point.
Two targets are watched: the finish milestone and a bulk-scope target, the date by which all non-critical work should be done. Bulk scope running past its target is an early warning that critical mass trouble is coming, well before the finish date moves.
For each primary craft, the remaining P6 hours become a headcount forecast to that craft's last work day. When daily craft headcount is reported, the forecast is adjusted to the productivity the field is actually achieving. The result is a calculated step-down for each craft, with a margin, in whole crews, and never released while a later day still needs those heads.
The service runs on the daily P6 update your scheduler already produces, and feeds both tiers of the event's review Rhythm.
| Craft step-down forecast | For each primary craft: heads needed now, peak ahead, last work day and a suggested step-down, updated every reporting period. |
|---|---|
| Forecast finish checks | Whether the finish is supported by the crews on site, whether progress reporting is current, and whether a constraint is holding the finish milestone regardless of the work behind it. |
| Dynamic 3-shift look-ahead | A prioritized work list for each coordinator at shift handover, rebuilt from every progress update. As work finishes early, slips, or is released by its predecessors, the look-ahead re-sequences with it. It is logic-driven and execution-responsive: each shift works from where the event actually is, not from where the baseline said it would be. |
| Event progress report | One printed report for the turnaround manager and senior leadership, with every KPI marked supported, qualified or unreliable. Nothing goes to management until the scheduler has confirmed it. |
| Your data stays with you | Schedule files are read in the browser. They are not uploaded to or stored on a PPI server. |
The forecasts depend on what the schedule carries: a finish milestone, unit completion milestones, a bulk-scope target and labour mapped to crafts. The Schedule Readiness Review checks for these before the event starts.
Send us the baseline and daily updates from a completed turnaround. We will replay it update by update and show where the tipping point arrived, and when each craft could have stepped down, next to what actually happened on site.
Request a pilot replay