Work Breakdown Structure

A $95M biologics manufacturing suite expansion is in the planning phase. The project spans facility design, construction, utility installation, equipment procurement, cleanroom build-out, equipment installation, IQ/OQ/PQ qualification, process validation, and regulatory submission. Without a structured decomposition, the project manager is managing a cloud of activities. With a properly built WBS, every dollar of budget, every hour of effort, and every dependency traces to a specific work package that someone owns.

ProBeya's WBS module provides a hierarchical breakdown of project work into manageable elements with auto-generated codes, drag-and-drop reordering, dependency management with cycle detection, critical path calculation, and WBS dictionary documentation. It is the structural foundation on which schedule, budget, and EVM are built.

WBS for Pharma Capital Projects

Pharmaceutical capital projects follow recognizable decomposition patterns. A typical WBS for a facility build follows a phase-based structure:

1.0  Project Management
  1.1  Project Planning & Controls
  1.2  Stakeholder Management
  1.3  Regulatory Coordination
2.0  Engineering & Design
  2.1  Conceptual Design
  2.2  Basic Engineering (FEED)
  2.3  Detailed Engineering
  2.4  Design Qualification (DQ)
3.0  Procurement
  3.1  Long-Lead Equipment
  3.2  Process Equipment
  3.3  Utility Equipment
  3.4  Instrumentation & Controls
4.0  Construction & Installation
  4.1  Civil & Structural
  4.2  Mechanical Installation
  4.3  Electrical Installation
  4.4  Cleanroom Build-Out
  4.5  HVAC & Clean Utilities
5.0  Commissioning
  5.1  Utility Commissioning
  5.2  Equipment FAT/SAT
  5.3  System Integration Testing
6.0  Qualification & Validation
  6.1  Installation Qualification (IQ)
  6.2  Operational Qualification (OQ)
  6.3  Performance Qualification (PQ)
  6.4  Process Validation
  6.5  Cleaning Validation
7.0  Regulatory & Handover
  7.1  Regulatory Filing Preparation
  7.2  Pre-Approval Inspection Readiness
  7.3  Operations Training
  7.4  Handover to Manufacturing

This WBS template serves as a starting point. Each project adapts it based on scope: a packaging line upgrade might skip civil/structural work, while a greenfield facility adds site preparation and external infrastructure.

WBS Code Generation

WBS codes are auto-generated based on the element's position in the hierarchy. When a new element is created, the system counts existing siblings under the same parent and assigns the next sequential code. Codes follow a dot-separated format (e.g., 1, 1.1, 1.1.2).

تلميح

Use a consistent WBS numbering philosophy across the portfolio. When every project uses the same top-level structure (1.0 PM, 2.0 Engineering, 3.0 Procurement, etc.), portfolio-level cost analysis by WBS category becomes possible. The PMO can compare engineering costs across all projects or benchmark qualification effort as a percentage of total project cost.

Tree Structure and Element Properties

Elements are stored with parentId references and ordered by sortOrder. Each element includes:

• Title and description
• Planned effort hours and duration days
• Completion percentage: leaf nodes set manually, parents computed via weighted roll-up
• Responsible person with name and email
• Linked board reference for bridging WBS planning with Kanban execution boards
• Milestone flag with type classification: internal, external, regulatory, or contractual

The milestone type classification is particularly important for pharma projects. A regulatory milestone (e.g., "submit variation to EMA") has different governance implications than an internal milestone (e.g., "complete detailed design review"). ProBeya tracks the distinction.

Dependencies and Scheduling

Dependency Types

Four dependency types are supported, matching industry-standard scheduling tools:

• FS (Finish-to-Start) -- Successor starts after predecessor finishes. The most common type: "Installation starts after equipment delivery."
• FF (Finish-to-Finish) -- Successor finishes when predecessor finishes. Example: "Documentation completion finishes when IQ execution finishes."
• SS (Start-to-Start) -- Successor starts when predecessor starts. Example: "HVAC installation starts when cleanroom framing starts."
• SF (Start-to-Finish) -- Successor finishes when predecessor starts. Rare in practice but supported for completeness.

Each dependency supports a lag in days (positive for delay, negative for lead time). Before creating a dependency, the system runs cycle detection to prevent circular references.

Scheduling Constraints

Eight constraint types control how the CPM engine positions tasks:

Constraint	Behavior	Pharma Use Case
ASAP	As soon as possible (default)	Most tasks
ALAP	As late as possible	Defer equipment delivery to minimize storage costs
SNET	Start no earlier than	Regulatory submission cannot begin before clinical data is available
SNLT	Start no later than	Construction must start by April to avoid winter weather
FNET	Finish no earlier than	Equipment FAT cannot finish before vendor completes manufacturing
FNLT	Finish no later than	Qualification must finish before regulatory filing deadline
MSO	Must start on	Pre-approval inspection is scheduled for a specific date
MFO	Must finish on	Product launch date is fixed by commercial commitments

Task Types

Three task types determine how effort, duration, and resources interact:

• Fixed Duration: Duration stays constant; effort adjusts with resource changes. Used for: equipment delivery lead times, curing periods, regulatory review periods.
• Fixed Work: Total effort stays constant; duration adjusts with resources. Used for: engineering design, qualification execution, document preparation.
• Fixed Units: Resource allocation stays constant; effort and duration adjust. Used for: ongoing project management, quality oversight.

Critical Path Calculation

The calculateSchedule procedure runs a full CPM engine:

1. Fetches all elements and dependencies for the project
2. Resolves project calendars (weekdays Mon-Fri by default)
3. Runs the CPM algorithm to compute early start, early finish, late start, late finish, total float, and free float for each element
4. Marks elements with zero total float as critical
5. Persists computed dates back to the database

The getCriticalPath procedure returns only critical-path elements with their dependencies. For pharma capital projects, the critical path typically runs through long-lead equipment procurement, installation, and qualification, which is why procurement decisions made in month 2 determine whether the project finishes on time in month 30.

تلميح

Always run Calculate Schedule after adding or changing dependencies. The critical path is only updated when you explicitly trigger recalculation. After a major re-planning session, recalculate and review the new critical path before communicating updated dates to stakeholders.

Completion Roll-Up

The rollUpCompletion procedure computes parent completion as a weighted average of children, where the weight is plannedEffortHours (elements with zero effort get a weight of 1 to avoid being ignored). The roll-up propagates recursively from leaves to root, and the final project-level completion percentage is written back to the project record.

This roll-up feeds directly into EVM calculations. When a WBS element is marked 60% complete with $100K of planned effort, that represents $60K of earned value. The accuracy of the entire EVM system depends on honest, timely completion updates at the work package level.

WBS Dictionary

Each element can carry extended dictionary attributes for formal documentation:

• Dictionary description and responsible organizational unit
• Acceptance criteria and technical references
• Quality requirements and contract information
• Code of accounts for financial system integration

The exportDictionary procedure returns all elements ordered by WBS code for report generation. In pharma environments, the WBS dictionary often serves as the foundation for the project's Validation Master Plan, mapping each qualification activity to its acceptance criteria and responsible department.

حذر

Moving elements via drag-and-drop recalculates all WBS codes in the project. For large projects with 200+ elements, this operation may take a moment. More importantly, if WBS codes have been referenced in external documents (contracts, regulatory submissions), coordinate the renumbering with affected stakeholders.

Permissions

Action	Required Role
Create/edit WBS elements	Project Manager or Admin
Reorder elements	Project Manager or Admin
Manage dependencies	Project Manager or Admin
Calculate schedule	Project Manager, PMO, or Admin
Update dictionary	Project Manager or Admin

Related Features

• Projects -- The project that owns this WBS
• Budgets & Costs -- Cost entries reference specific WBS elements for granular cost tracking
• EVM -- Earned value computed from WBS completion percentages and planned effort
• Stage-Gate Reviews -- WBS milestones often align with gate review triggers