Menu

Advanced Work Packaging Specs after the Takt & CPM Specifications?

PART 1 — GENERAL

1.01 RELATED DOCUMENTS

A. Construction Agreement and amendments.

B. Exhibit C-1 — Project Milestones.

C. Exhibit C-2 — Project Production Plan Specification (Takt-Based Production Planning with Advanced Work Packaging). This Specification is read together with Exhibit C-2; Exhibit C-2 establishes the Production Plan (the engine), and this Section establishes the work-package structure (the deliverable). The two documents shall be applied as one coherent system.

D. Exhibit D-1 — Project Cost Specifications.

E. Section 01 31 00 — Project Management and Coordination.

F. Section 01 91 00 — Global General Commissioning Requirements.

1.02 SUMMARY

A. What this Specification does. This Specification establishes the Contractor’s obligation to deliver the Work to the field as a chain of prepared, sequenced, fully kitted work packages, sized to the Takt beat established in the Production Plan, and released only when roadblock-free. The package the crew actually picks up — the Installation Work Package (IWP) — is the unit at which the Work is built; every other deliverable in this Specification exists to make that package ready.

B. What this Specification does not do. This Specification does not introduce a parallel CPM schedule, an over-the-wall workface-planner role, or a fixed week-long IWP sizing rule. Where this Specification conflicts with the legacy work-packaging guidance previously embedded in Section 01 31 00, this Specification governs.

C. Purpose. The purpose of Advanced Work Packaging on this Project is to deliver work to crews the way a flat-pack box delivers furniture: complete, prepared, ready-to-build, sequenced in the order the work actually goes together, with everything the crew needs on hand and nothing in their way. AWP on this Project is run on a Takt base, with the field doing the planning, and never on a CPM schedule with a specialist throwing packages over a wall.

D. Mental model. Every component of the Work passes through four verbs in order: Design → Make → Transport → Build. The Engineering Work Package (EWP) designs it. The Procurement Work Package (PWP) buys and fabricates it. Logistics and kitting transport it to the work face. The Installation Work Package (IWP) builds it. The Commissioning Work Package (CxWP) proves the finished system works. The Contractor’s job is to keep these four verbs lined up to the Takt beat so the field always has a complete box on the day it builds.

1.03 DEFINITIONS

A. Construction Work Area (CWA) — The geographic territory within which construction packages are organized; equivalent to a Phase in the Takt Production Plan.

B. Construction Work Package (CWP) — A management container: one discipline within one CWA, sized as a budget a single accountable manager can own. Not the package the crew takes to the field. Each CWP must divide cleanly into many crew-week IWPs.

C. Engineering Work Package (EWP) — The design deliverable for one discipline in one work area: IFC drawings, model deliverables, specifications, bills of material, calculations, approved vendor data, and clear scope boundaries. Built to match a planned CWP, released in the order the field needs it.

D. Procurement Work Package (PWP) — The plan to buy, expedite, deliver, and stage every piece of material and equipment a construction scope requires, organized by lead time, back-scheduled from the required-on-site date.

E. Installation Work Package (IWP) — The crew-sized, fully roadblock-free, fully kitted package a single foreman runs at the work face for one trade, in one Takt zone, within one Takt time. The only package that reaches the tools.

F. Commissioning Work Package (CxWP / System Turnover Package) — The system-based turnover package that proves a finished system works. Built to the same roadblock-free, fully-kitted standard as an IWP.

G. Full Kit / Pre-Kit Checklist (17 items). The condition in which every element a crew needs to start and finish an IWP is present, ready, and confirmed by the Workface Planning Team. The 17 pre-kit items include, at minimum: (1) approved IFC drawings; (2) field-engineered lift drawings and layout; (3) coordinated BIM model package; (4) RFIs closed; (5) submittals approved; (6) materials delivered and inspected on the face; (7) prefabricated assemblies on the face; (8) consumables and fasteners staged; (9) tools and equipment staged or assured; (10) crew identified, sized, and committed; (11) safety plan and hazard controls in place; (12) permits pulled; (13) predecessor work accepted; (14) quality holds released and quality visuals in hand; (15) access cleared and verified at the work face; (16) inspection and hold points scheduled; (17) visual work instructions present at the package.

H. Roadblock vs. Constraint. A constraint is a planning-level limit (Takt time, zoning, sequence, buffer, bottleneck) adjusted around in the planning room. A roadblock is a temporary, removable obstacle in front of work coming up to a crew, cleared at the work face. The Contractor shall adjust constraints in planning and remove roadblocks in the field.

I. Workface Planning Team. The field-based team that makes the work ready: the Superintendent (enabler-in-chief; secures the access, sequence, conditions, and support); the Field Engineer (layout and control, frontline quality and safety, lift drawings); the Project Engineer (information and materials, RFIs closed, submittals approved, kits ordered); and the Foreman (last planner; builds the plan for the next stretch, walks the crew through it, and removes roadblocks shoulder to shoulder with the crew). The Foreman is the decisive planner whose commitment actually builds the Work.

J. Just-in-Time Delivery. Delivery to the work face by one of three lean routes — vendor → zone, vendor → laydown → zone, or supermarket → zone — exactly when the crew reaches for the material. Material delivered to the zone before the crew reaches for it is prohibited.

L. Five Work-Package Types — chain of cuts.

  1. EWP — owned by Design, organized by discipline within area. What are we building, exactly?
  2. PWP — owned by Supply Chain, organized by commodity and lead time. What must be bought, and when?
  3. CWP — owned by Construction Management, organized by discipline within area. How is the field scope divided into manageable budgets?
  4. IWP — owned by the Field, organized as one crew × one zone × one Takt. What does one crew do this beat?
  5. CxWP — owned by Startup/Commissioning, organized by system and subsystem. Does the finished system actually work?

The first four packages are cut by location. The fifth — and only the fifth — is cut by function (system). The Contractor shall maintain a live cross-reference between the area-map and the system-map throughout the Work.

1.04 GUIDING PRINCIPLES

A. Begin with the end in mind. The Commissioning Sequence pulls the Path of Construction; the Path of Construction pulls the EWP release order; and the IWP release rhythm pulls the supply chain. The Contractor shall plan the package chain backward from the order in which systems must come alive.

B. One discipline, one area, one beat. The CWP is one discipline within one CWA. The IWP is one trade within one zone within one Takt time. The Contractor shall not deliver IWPs that span multiple trades, multiple zones, or multiple beats.

C. Cut to the beat, not to the calendar. The IWP shall be sized to the Takt beat for its train and zone, as determined by the Takt Calculator under Exhibit C-2 §3.03, not to a rule-of-thumb of “approximately one week.” An IWP sized to a week instead of the beat is by definition mis-sized for the rhythm of the train and will bottleneck the zone.

D. Plan with the field. The Workface Planning Team builds the packages. The Contractor shall not staff a disconnected workface-planner specialist to package work at a desk and hand it to the field over a wall.

E. Roadblock-free or held. A released IWP is a promise: everything you need is here, go build. The Contractor shall not release an IWP with any open roadblock against it. An IWP with one open roadblock stays in backlog.

F. Do not start until you are ready to finish. This is the operative readiness test for every IWP, and it covers more than materials: the place (clean, safe, access-cleared), the people (crew sized and aligned), the path (sequence and handoffs set), and the parts (full kit). If the team cannot see a clear path all the way to done, the package is not ready to start.

H. Respect for people. Workface Planning is respect for people made operational. The Workface Planning Team carries the discomfort of preparation so that the men and women doing the building walk up to work that is ready.

PART 2 — PRODUCTS

2.01 ENGINEERING WORK PACKAGE (EWP)

A. Definition and scope. Each EWP is the complete design deliverable for one discipline within one CWA, sufficient that the field can build from it whole. Partial designs released to “let the field start while we finish the rest” are prohibited.

B. Required contents. Each EWP shall contain:

  1. The list of IFC drawings that govern the package, with revision identifiers;
  2. A coordinated, clash-detected BIM model deliverable for the package’s scope and adjacent scopes;
  3. The relevant specifications;
  4. The bill of material (BOM) feeding the corresponding PWP;
  5. Supporting calculations and engineering analyses;
  6. Approved vendor data for equipment within the package’s scope;
  7. A clear statement of the package’s spatial and scope boundaries (where it begins, where it ends, what it includes, what it explicitly does not); and
  8. A back-scheduled release date driven from the IWP install dates the EWP supports.

C. Release order. EWPs shall be released in the order the field needs them — i.e., the order set by the Path of Construction and the Norm Production Plan — and not in the order convenient to the design office. The Contractor shall sequence design deliverables to match the Path of Construction approved under Exhibit C-2 §3.01.

2.02 PROCUREMENT WORK PACKAGE (PWP)

A. Definition and scope. Each PWP is the plan to buy, expedite, deliver, and stage the material and equipment a construction scope requires.

B. Required contents. Each PWP shall contain:

  1. The BOM consumed from the corresponding EWP;
  2. Vendor identification and award status;
  3. Lead-time identification, with long-lead items isolated and back-scheduled;
  4. PO release date, fabrication-by date, ship-by date, required-on-site date, and required-on-face date — all back-scheduled from the IWP install date with explicit supply-chain buffer;
  5. The proposed Just-in-Time delivery route (vendor → zone, vendor → laydown → zone, or supermarket → zone);
  6. The kitting plan (material kitting, room kitting, or prefabrication; see §3.05);
  7. The on-site staging and storage plan;
  8. Tag-and-label scheme tying every delivered item to its IWP, zone, and step; and
  9. A material-readiness status indicator, reported package-by-package, that feeds the Live Roadblock Log under Exhibit C-2 §2.01.C.

C. Long-lead items. All long-lead equipment and major fabricated assemblies shall be identified within 30 days of GMP award, isolated from the rest of the PWP, and back-scheduled from their IWP install dates with explicit buffer. Long-lead status shall be reported weekly.

2.03 CONSTRUCTION WORK PACKAGE (CWP)

A. Definition and scope. Each CWP is a management container: one discipline within one CWA. It is the unit at which the construction budget, the construction schedule, and the discipline scope are organized. A CWP is not the package a crew takes to the field.

B. Sizing test. Each CWP shall pass the test of dividing cleanly into many crew-week IWPs (cut to the Takt beat per §3.02). If a proposed CWP cannot be divided into IWPs, it is mis-scoped or it spans too much; the CWP shall be re-cut.

C. Required contents. Each CWP shall contain:

  1. The single discipline and single CWA it covers;
  2. Its scope boundaries;
  3. The budgeted cost and craft hours (CWE direct hours) for the scope, broken down to the SPA / TWP level per the OneWBS;
  4. The CWP’s place on the Norm Production Plan;
  5. The cross-reference to its parent EWP and PWP;
  6. The cross-reference to the commissioning systems it feeds; and 
  7.  A single accountable manager.

2.04 INSTALLATION WORK PACKAGE (IWP)

A. Definition and scope. Each IWP is the crew-sized, fully roadblock-free, fully kitted package a single foreman runs at the work face. Each IWP is:

  1. One trade;
  2. One Takt zone;
  3. One Takt time (one beat) of duration;
  4. One accountable foreman; and
  5.  The convergence of its upstream EWP, CWP, and PWP into the work the crew finally holds.

B. Sizing rule (mandatory). Each IWP shall be sized to the Takt beat for its train and its zone, as set by the Takt Calculator under Exhibit C-2 §3.03. The Contractor shall not size IWPs to a rule-of-thumb calendar week, to a fixed craft-hour count, or to a default 4–6-person crew. Where the Takt beat is shorter than a week, the IWP is shorter than a week. Where the Takt beat is longer than a week, the IWP is longer than a week. Mis-sized IWPs are the single most common failure mode of orthodox AWP; this Specification expressly forbids them.

C. Required contents. Each IWP shall contain:

  1. A plain-language scope statement — exactly what is built and to what line;
  2. The relevant IFC drawings and model views, including the field engineer’s lift drawings;
  3. The kitted material list, with bag-and-tag identifiers, tied to the PWP;
  4. The tool and equipment list, with availability confirmed;
  5. The named crew and its size, with hours budgeted to the OneWBS Trade Package level;
  6. The safety plan for the specific hazards of the task;
  7. The quality requirements: standard, inspection and hold points, “what right looks like”;
  8. The predecessor that must be accepted before the IWP starts, and the successor waiting downstream;
  9. The visual work instructions — pictures and steps that let the crew see the finished work before they build it;
  10. The expected start beat and finish beat on the Norm Production Plan;
  11. The Pre-Kit Checklist (17 items), all confirmed and signed off; and
  12. The cross-reference to the CxWP / system(s) the IWP feeds.

D. Integration with the Production Plan. Each IWP shall be tied to a wagon, an activity, or a Takt position on the Norm Production Plan under Exhibit C-2 §3.02. The IWP set, the Production Plan, the Procurement Log, and the Live Roadblock Log shall be one connected document set, not four independent files.

E. Resource loading. Each IWP shall be resource-loaded with planned and actual direct labor hours at Level-5 detail, in work-hours per day per person, aligned to the Current Working Estimate (CWE) and baseline GMP. Resource loading shall not be based on crew-days. Where the L3 CPM Summary export is required under Exhibit C-2 §3.11, the IWP resource loading shall flow up into that export at L3 only.

F. Project TWP localization. Where the Owner has provided a Program Trade Work Package template for a scope, the Contractor shall localize the template into a site-specific Project TWP and ensure consistency with the OneWBS coding for cost and schedule rollup.

2.05 COMMISSIONING WORK PACKAGE (CxWP)

A. Definition and scope. Each CxWP is the system-based turnover package that proves a finished system works. CxWPs are organized by system and subsystem, not by area, and break the location-pattern of the first four packages on purpose.

B. Required contents. Each CxWP shall contain:

  1. The system and subsystem boundaries, marked on the drawings;
  2. The scope and objective — what “working” means here, and the evidence that will prove it;
  3. The prerequisites and constraints, including which enabling systems must already be live;
  4. The pre-commissioning records for de-energized preparation (flushing, cleaning, drying, calibration, loop checks);
  5. The commissioning procedures and test records for energized, dynamic tests, with acceptance criteria and signature blocks;
  6. Vendor requirements, naming which equipment needs a manufacturer’s representative present and when;
  7. The safety package — energization procedures, lockout/tagout, first-fill lubricants and chemicals;
  8. The punch list, sorted by what blocks commissioning, what blocks startup, and what can wait;
  9. The custody-transfer certificates moving the system from construction to commissioning to operations;
  10. The resources — technicians, competencies, consumables, spares — the work will consume; and
  11. The cross-reference to the CWPs / IWPs that physically delivered the system.

C. The completion ladder. Each CxWP shall define its place on the completion ladder: Mechanical Completion → Pre-Commissioning → Commissioning → Startup → Performance and Handover. Each rung shall have explicit acceptance criteria and a signed certificate. The ladder shall be defined before the first walkdown, not negotiated rung by rung.

D. Tag-loading. CxWP activities shall be loaded with the appropriate tag quantities by equipment and/or system as outlined in the Global General Commissioning Requirements.

PART 3 — EXECUTION

3.01 CUT THE PACKAGE CHAIN BACKWARD FROM COMMISSIONING

A. Order of operations. The Contractor shall develop the package chain in the following order, and not in any other:

  1. Systemize the facility during engineering. Divide the asset into systems and subsystems on the drawings, tag every component to a system, and deliver the Commissioning Systems and Subsystems List before drawings are issued for construction.
  2. Write the commissioning sequence first. Determine the order in which systems must come alive, starting with enabling and utility systems that everything else depends on. This sequence is the head of the Path of Construction.
  3. Set the Path of Construction under Exhibit C-2 §3.01, pulled backward from the commissioning sequence.
  4. Phase and zone the Project with the Takt Calculator under Exhibit C-2 §3.03. The phases that fall out of this step are the CWAs; the zones are the increment of space each package occupies.
  5. Cut the Construction Work Packages. A wagon’s full run through a phase — one discipline, one CWA — is one CWP. Confirm each CWP divides cleanly into many IWPs.
  6. Cut the Engineering Work Packages and Procurement Work Packages backward from the CWPs they serve, sequenced and back-scheduled to the IWP install dates within the CWPs.
  7. Cut the Installation Work Packages. A single wagon working a single zone for a single beat is one IWP. Size each IWP to the Takt beat, not to a week.
  8. Cut the Commissioning Work Packages by system. Maintain the cross-reference between the area map (CWPs/IWPs) and the system map (CxWPs) at all times.

B. Two maps, kept live. The Contractor shall maintain, throughout the Project, a live cross-reference between (i) the area map (CWA → CWP → IWP) and (ii) the system map (System → Subsystem → CxWP). For any subsystem the Contractor shall be able to name the construction packages that gate it; for any area the Contractor shall be able to name the systems the area’s work feeds.

3.02 PACKAGE SIZING — TAKT CALCULATOR, NOT CALENDAR

A. Mandatory use of the Takt Calculator. Before any package sizing decision is made, the Contractor shall run the Takt Calculator per Exhibit C-2 §3.03 for each phase, to determine the number of zones and the Takt time that produce flow along the Path of Construction.

B. CWA sizing. Each CWA shall be sized to match the phase boundary set by the Takt Calculator.

C. CWP sizing. Each CWP shall be one discipline within one CWA, and shall cleanly divide into many IWPs of one Takt beat each.

D. IWP sizing (mandatory). Each IWP shall be sized to one Takt beat for its train and zone, as set by the Takt Calculator. The legacy AWP convention of “typical maximum one-week duration, single crew of 4–6 people” is expressly superseded by this Specification.

  1. Where the Takt beat is shorter than a week (e.g., one day), the IWP is shorter than a week. The crew composition is whatever the work requires within that beat, not a default 4–6 persons.
  2. Where the Takt beat is longer than a week (e.g., on heavy industrial / prefab work where larger zones are appropriate), the IWP is longer than a week and runs at the beat the work demands.
  3. In all cases, the crew shall be able to start and finish the IWP within its single Takt time, in its single zone, without waiting on anyone.

E. Single-trade, single-zone test. All IWPs shall pass the single-trade, single-zone, single-Takt test. Packages that span multiple trades, multiple zones, or multiple Takt times shall be re-cut.

F. Re-cutting allowed. As the Project progresses and work-density data is gathered, the Contractor shall re-cut IWPs to keep them sized to the actual Takt beat in each phase. The Owner shall not lock the Contractor into fixed IWP sizes for the duration of the Project.

3.03 WORKFACE PLANNING — WITH THE FIELD, NOT OVER A WALL

A. The Workface Planning Team. Workface Planning shall be performed by the Workface Planning Team defined in §1.03.I — the Superintendent, Field Engineer, Project Engineer, and Foreman — as part of their existing roles, not as the responsibility of a separate specialist.

B. Role allocation.

  1. Superintendent (enabler-in-chief). Ensures the crews have the entire list of what they need: access, sequence, conditions, support. Owns the live wall and walks the zones daily. Acts as Guardian of the Production System.
  2. Field Engineer. Owns layout and control; frontline safety and quality; and the lift drawings that turn design into something the crew can build.
  3. Project Engineer. Owns information and materials: RFIs closed, submittals approved, materials ordered, deliveries tracked, kits assembled.
  4. Foreman (last planner). Builds and owns the plan for the next stretch of work; walks the crew through it in the prep huddle; removes roadblocks shoulder to shoulder with the crew. The Foreman’s commitment is the one that actually builds the Project.

C. No specialist workface planner. The Contractor shall not assign a disconnected workface-planner specialist to develop IWPs at a desk and hand them across a wall to the field. This Specification expressly supersedes any legacy AWP guidance to that effect.

D. Standard work for the Workface Planning Team. The Contractor shall publish leader standard work for the Superintendent and the Workface Planning Team that defines:

  1. The daily walks and what is observed;
  2. The weekly look-ahead cycle and its inputs and outputs;
  3. The handoff verification routine at each zone boundary;
  4. The roadblock log review cadence; and
  5. The improvement loop (per §3.10).

3.04 ROADBLOCK-FREE RELEASE — DO NOT START UNTIL READY TO FINISH

A. The full kit and the readiness test. No IWP shall be released to the field unless and until:

  1. Every one of the 17 Pre-Kit items is confirmed and signed off;
  2. Every open roadblock against the IWP has been removed;
  3. The Workface Planning Team has affirmatively answered “yes” to the question, “Can this crew see a clear path all the way to done?”

B. Adjust constraints in planning; remove roadblocks in the field. During preconstruction and during open pull-plan cycles, constraints (Takt time, zoning, sequence, buffers) are adjusted in the planning room. Once the Norm Plan for a phase is set, anything raised after is treated as a Roadblock to be removed at the work face — not as a constraint to renegotiate.

C. Roadblock removal — for and with the crews. Roadblocks shall be removed for and with the crews, at the work face — not stamped clear from a desk. The Foreman and Workface Planning Team shall walk the work, find the roadblocks the trailer cannot see, and clear them in person.

D. Live Roadblock Log. The Contractor shall maintain a Live Roadblock Log per Exhibit C-2 §2.01.C, with each roadblock identified by:

  1. The roadblock (what it is);
  2. The IWP it threatens;
  3. The owner (who is clearing it, by name);
  4. The required-by date (the IWP’s start date minus a safety margin);
  5. The status today.

The Log shall be visible to all trade partners and the Owner, reviewed in the make-ready meeting, and burned down weekly. Roadblock-Removal Average (the average lead time roadblocks are cleared ahead of need) is reported as a Vital Sign under Exhibit C-2 §3.09.

E. Held IWPs. An IWP with any open roadblock at its scheduled start beat shall be held in backlog, not released to the field. The Production Plan shall be adjusted under §3.07 / Exhibit C-2 §3.08 to absorb the hold.

3.05 MATERIAL FLOW AND KITTING — JUST-IN-TIME, KITTED LIKE IKEA

A. Kit to the IWP. Each IWP shall arrive at the work face with the materials it requires gathered, sorted, labeled, and tied to the IWP, the zone, and the step. Loose bulk delivered to the zone is prohibited.

B. Kitting depth. The Contractor shall determine, task by task, the appropriate kitting depth:A. Kit to the IWP. Each IWP shall arrive at the work face with the materials it requires gathered, sorted, labeled, and tied to the IWP, the zone, and the step. Loose bulk delivered to the zone is prohibited.

  1. Material kitting — bag-and-tag of loose materials for one task;
  2. Room kitting — entire space kitted at once, with the trade partners agreeing on what lands where; or
  3. Prefabrication — whole assemblies (modules, racks, skids, spools) built off-site and delivered as finished pieces. The Contractor shall lean toward prefabrication wherever the BIM model and the work allow.

C. Stage to the face, just in time. Each kit shall reach the exact work face — not the gate, not a distant yard — exactly when the crew reaches for it, by one of the three lean routes:

  1. Vendor → zone;
  2. Vendor → laydown → zone; or
  3. Supermarket → zone.

Material delivered to the zone before the crew reaches for it is prohibited. Laydown yards and supermarkets are deliberate lean buffers and shall be planned, located, and managed as such.

D. A delivery board (Kanban). The Contractor shall maintain a material-delivery board that pulls each kit to the face exactly when its IWP comes ready in the six-week look-ahead. The delivery board, the Live Roadblock Log, and the Production Plan shall be connected.

E. A water spider (or equivalent). The Contractor shall name a person whose role is to keep the work face fed — owning deliveries, staging, hoisting, pre-kitting, and prefab coordination, and protecting tool-time at the face. On large jobs this person is a dedicated role; on small jobs this responsibility may be combined with another field role but shall be explicitly named.

F. De-trashing and logistics zero tolerance. Material delivered to site shall be on a scheduled delivery, inspected on arrival, unpacked, and de-trashed (in de-trashing tents on the larger jobs), with the trash removed and the recycling handled in place. Destinations shall be coordinated. Kits shall be brought to the zones on wheels (rolling carts) as complete kits, not in bulk drops. Logistics is a zero-tolerance line under §3.08.

3.06 THE DAILY CHAIN — THREE HUDDLES AT THE WORK FRONT

A. Daily huddle — day before. The Foreman daily huddle shall be held the afternoon before the work, with the foremen and the Superintendent. The huddle aligns tomorrow’s zones, handoffs, and outstanding roadblocks while there is still time to fix them.

B. Worker huddle — start of the day. At the start of the day, the entire workforce in a functional area — every crew and every trade partner working that part of the job — shall huddle together. The day’s goals, zones, safety, and handoffs shall be communicated out loud. Single-crew briefings that omit adjacent trades are prohibited as the sole morning huddle.

C. Crew preparation huddle — at the work face. Immediately before the work, the crew shall gather around the IWP and its visual work instructions and walk the task through together — steps, sequence, kit, quality standard. The crew prep huddle is the last hundred feet of all upstream planning. The Contractor shall not skip it.

D. Coordination Meetings and Progress Meetings (per Section 01 31 00 §1.10). The weekly Coordination Meetings and Progress Meetings required by Section 01 31 00 shall be conducted as set forth in that Section, but shall be driven by the Norm Production Plan and the Live Roadblock Log, not by a CPM schedule. Schedule discussion shall focus on Trade Flow, handoffs, buffer position, and the six Vital Signs.

3.07 ZONE CONTROL AND HANDOFFS

A. The zone is the unit of control. For every active zone, the Contractor shall be able to answer at all times: (i) what wagon, activity, or IWP is currently in this zone; (ii) is it on beat; and (iii) if not, what is in the way.

B. Plan ahead, finish as we go. The Contractor shall hold both directions at once — making the upcoming zones ready before the work reaches them, and finishing each zone fully before the work moves on. A trail of unfinished business behind the train (deferred work to end-of-phase punch) is prohibited.

C. Handoff measurement. Each trade-to-trade handoff shall be measured at the zone boundary against two tests: (i) was the zone complete at the boundary; (ii) was it on time to the Takt time. Both passing equals one “perfect handoff.” Perfect Handoff % is reported as a Vital Sign per Exhibit C-2 §3.09.

D. Live wall. The Norm Plan, the IWP status, and the zone status shall be rendered on a live wall — physical or digital — visible to all trade partners and to the Owner. Each zone shall be marked on beat, behind, or blocked.

E. Walk the zones. The Superintendent shall walk the zones daily, comparing the wall to the ground, and shall reconcile the two with the field team. Zone status shall not be falsified to keep the wall green.

F. Honest red is a gift. A zone honestly marked behind shall be treated as a gift — a problem that can still be fixed. Zone status shall not be the basis on which crews or trade partners are penalized.

3.08 QUALITY AT THE SOURCE — AND THE FIVE DISCIPLINE SYSTEMS

A. Quality at the source. Defects shall be corrected in the zone, in the moment, before the handoff. The Contractor shall not pass defective work down the line. Quality at the source is the field measurement of the readiness rule: an IWP that reaches its successor with defects has not actually finished.

B. Daily correction. Leaders shall be present in their areas, walking, observing, and correcting in person — keeping the environment safe, clean, organized, and ready for flow. Daily correction is small and kind, not saved-up.A. Quality at the source. Defects shall be corrected in the zone, in the moment, before the handoff. The Contractor shall not pass defective work down the line. Quality at the source is the field measurement of the readiness rule: an IWP that reaches its successor with defects has not actually finished.

C. Zero-tolerance lines. The following lines shall not bend, and shall be communicated to every trade partner and crew before mobilization:

  1. A safety violation is non-negotiable. The person shall be kindly removed from the site and required to return through orientation before resuming work.
  2. Areas not clean shall be cleaned in the moment. Cleanup is not a once-a-week event.
  3. Deliveries and logistics. Deliveries arrive on a schedule, are inspected on arrival, are unpacked and de-trashed in place, and reach the zone as complete kits on wheels. Bulk drops to the zone are prohibited.

D. Trade partner grading. Each trade partner shall be graded in the open against shared, fact-based expectations, including Perfect Handoff %, PPC, Roadblock-Removal performance, Quality at the Source, and Safety. Grading shall be transparent.

E. Team health. The Contractor shall measure and report the health of the team itself, including trade partners — load balance, burnout indicators, overtime usage, and trust. Hitting dates by burning out crews is a borrowed gain that comes due later and shall not be the Contractor’s recovery strategy.

3.09 COMMISSIONING TURNOVER TAKT — AND THE LATE-PROJECT FLIP

A. Commissioning gets its own train. Commissioning shall run a Turnover Takt — a steady drumbeat of subsystems advancing one rung up the completion ladder per beat. The Contractor shall plan the Turnover Takt with the Commissioning Authority and integrate it into the Norm Production Plan.

B. Flip from area-led to system-led. Early in the Project, zoning is area-led, because the rhythm of trades flowing through geometric zones drives productivity. As the Project approaches turnover, the zoning of the construction Takt shall flip to system-led — the last zones through the train shall be chosen by what commissioning needs alive next, not by what is geometrically convenient. The transition point shall be defined in the Norm Plan and managed deliberately.

C. One subsystem at a time. Custody transfer (construction → commissioning → operations) shall happen one subsystem at a time, on the Turnover Takt, with formal certificates at each rung. Subsystems shall not sit in limbo without an owner.B. Flip from area-led to system-led. Early in the Project, zoning is area-led, because the rhythm of trades flowing through geometric zones drives productivity. As the Project approaches turnover, the zoning of the construction Takt shall flip to system-led — the last zones through the train shall be chosen by what commissioning needs alive next, not by what is geometrically convenient. The transition point shall be defined in the Norm Plan and managed deliberately.

D. Punch list discipline. The punch list shall be sorted into three categories — what blocks commissioning, what blocks startup, what can wait — and closed weekly. The middle category (the “we’ll get to it” pile) shall not be allowed to accumulate into the final ninety days.

3.10 CONTINUOUS IMPROVEMENT

A. Loop the cycle. Every zone is a rep. The Contractor shall run the improvement loop on every cycle:

  1. Plan the zone;
  2. Build the zone;
  3. Reflect with the crew — identify, discuss, solve;
  4. Improve — change one thing for the next zone.

B. Six steps to lasting improvement.

  1. Stabilize — make flow stable before optimizing;
  2. Visualize — surface problems on the boards;
  3. Empower — put improvement in the hands of the crews;
  4. Experiment small — one change, one zone;
  5. Standardize the wins — build successful experiments into the package and the standard work;
  6. Repeat — every cycle, without end.

C. Problems are gifts. Surfaced problems are the raw material of improvement. The Contractor shall foster a culture in which it is safe to say, out loud, what went wrong, and in which leaders own the system that produced the problem rather than the person who reported it.

D. Improvement, not surveillance. Continuous improvement under this Specification is not used to assign blame, to penalize crews, or to renegotiate scope. It is used to make the next zone better than the last.

Scroll to Top