General comments
Bottom line
The DCS scope is not missing from the schedule — it is invisible in it. W-15095986 (1,790 h, 132 activities) is in the P6 network with logic and float, but none of its activities carry baseline dates, so every date-filtered view drops it. The fix: date it, re-baseline, date the three DCS milestones, republish on the confirmed 16 Oct calendar.
A-17 cannot be closed as written: the big job is undated, six Workbook WOs have 0 h in P6, no MOC is approved, and the delivery → narrative freeze → configuration → FAT chain has no activities.
Findings — 💬 to raise a clarification against any finding
The gap, as one statement
In the P6 network: 3,090 h (DCS 1,790 + instrumentation 1,300). Not in the schedule: 6 WOs at 0 h — hours to be quantified by K. Kennedy. And 58% of the DCS hours that are "in" have no dates, so no defensible float.
How this gets worked — two passes, one register
DCS scope — work breakdown structure — six elements, gate-mapped; 💬 on each
DCS / I&E work order register — 💬 on any row to raise a clarification
P6 export 16 Jul (hours, floats, windows) · Workbook 17 Jul (flags, MOC) · floats on the 16-Oct calendar.
| 💬 | WO | Group | Description | P6 h | Phase | Window | Min float | P6 | MOC | Flags | Quick note | ✓ |
|---|
W-15095986 — Install new upgraded DCS for ASU 1 (1,790 h)
21 sub-jobs, 132 activities, PRE + TAR · FCO approved 9 Jun, moved to Workscope · cabinets CP0101, CP0108, FCP270/280, A501, A531, A541/543, A544, F533 · dashed red = no activities in P6.
Sub-jobs (hours / activities / min float)
| Sub-job | Phase | h | Acts | Min float |
|---|
Does the DCS chain compute onto the critical path?
Not on the current numbers — but the numbers are not defensible. Stated path W-14551438 (MAC compressor 36M KPM) carries 0d 2h; the MAC feeder cable 0d 4h; the DCS job's tightest activity 4d 8h.
1. W-15095986's float rides on undated, unbaselined activities — one re-baseline could move it.
2. The 2 Nov date in the Workscope header is superseded — TAR start confirmed 16 Oct (12 Aug). Correct the Workbook.
3. The delivery → narrative → config → FAT chain has no activities: zero float visibility.
Float ladder — biggest jobs, min total float (16-Oct calendar)
Bars ranked at 8 h/day; values are P6 strings. 1,075 activities carry 1.0-unit placeholder labour.
The seven questions — where they stand after this pass — 💬 to add a clarification
Proposed actions — for the meeting — 💬 to amend before tabling
| 💬 | Owner | Action | Due |
|---|
Clarification register (TQ log)
Every 💬 lands here as a numbered TQ. Saved in this browser only — export before sharing. The .csv merges into the tracker sheet; the .txt goes to the meeting thread.
| TQ # | Ref | Item | Raised by | Date | Clarification / question | Suggested owner | Status |
|---|
No clarifications yet — use 💬 anywhere on the dashboard.