Work Breakdown Structure

Scope decomposed into leaves that drive modules and BOQ groupings.

The WBS is the spine. Every leaf becomes a module instance; every root becomes a BOQ section. I kept it shallow where the customer's structure is well-defined, deeper only where ambiguity needed splitting.

04-wbs.md

Download

The WBS spine is built around three orthogonal organizing axes:

Lifecycle phase (Project Management → Material Supply → Installation → Programming → T&C → Training → Optional/OOS) — drives proposal narrative + BOQ groupings
Customer two-phase delivery (Phase 1: Stations→OCC; Phase 2: Buildings→FCCR per TOR §5)
INTEG BOQ alignment — the 12 lump-sum lines in the customer's BOQ map to specific WBS leaves so the DUPA back-calculation is clean

This combined structure keeps the proposal customer-readable (matches their two-phase scope description) while preserving the lifecycle organization needed for engineering scoping + cost estimation.

Work breakdown

10 roots · 93 leaves · 103 nodes

04-wbs.md · supporting sections

3 sections·

Why I made these choices

3 decisions

Sources for this step

Primary sources

Customer-provided documents.

Secondary sources

System-generated artifacts ProposalGen built upon.