An effective SLAC National Accelerator Laboratory Work Breakdown Structure (WBS) is a deliverable-oriented, hierarchical decomposition designed to track massive technical, scientific, and civil infrastructure scopes within a Department of Energy (DOE) Earned Value Management System (EVMS) framework. Building a WBS for complex facilities like the Linac Coherent Light Source (LCLS) requires aligning physical machine geography, technical systems, and clear organizational accountability. The Standard SLAC WBS Hierarchy
SLAC projects break down work across structured levels to balance macro-level reporting with granular task engineering:
Level 1: The Total Project – The overarching facility or upgrade initiative (e.g., LCLS-II Project Baseline).
Level 2: Major Technical Systems & Lifecycles – Broad programmatic buckets dividing the accelerator systems, conventional facilities, and project management.
Level 3: Functional Subsystems / Sub-projects – Specific pieces of the machine where a dedicated Task Manager translates high-level system requirements into hard design criteria.
Level 4+: Control Accounts and Work Packages – The foundational layer where scope integrates directly with specific institutional teams, budgets, and schedules for physical tracking. Core Rules for Building a SLAC WBS Effectively
Enforce the 100% Rule: Ensure each parent level contains exactly 100% of the work from its children, incorporating internal tasks, outsourced fabrications, and indirect efforts like safety compliance and project management.
Incorporate Physical and Geographic Scope: Unlike corporate software projects, SLAC projects must segment work packages by specific geographic sectors of the accelerator complex or machine line where possible.
Integrate the OBS to Map Accountability: Explicitly marry your WBS with the Organizational Breakdown Structure (OBS). This cross-section forms a Responsibility Assignment Matrix (RAM), guaranteeing that every single technical control account maps to one single institutional entity or manager.
Map the ⁄80 Guideline to Reporting Cycles: Keep individual, lowest-level work packages constrained roughly between 8 and 80 hours of effort, or design them to sit cleanly within a single monthly project reporting period to streamline EVMS updates.
Standardize Naming Conventions: Keep level elements deliverable-focused by utilizing clear nouns and adjectives (e.g., S20 Injector, Cryoplant Warm Compressor) rather than open-ended verbs. Example Matrix: Level 2 & 3 Technical Layout
Large-scale accelerator and light-source projects at SLAC structurally classify their WBS scopes using a format similar to this:
Creating effective work breakdown structures– or how to … – PMI
Leave a Reply