7.2 Organizational Breakdown Structure (OBS) & Control Accounts

7.2 Organizational Breakdown Structure (OBS) & Control Accounts

While the Work Breakdown Structure (WBS) defines what deliverables must be produced to fulfill project scope, successful project execution requires clear definition of who will perform, manage, and take accountability for the work. In Total Cost Management (TCM) and Earned Value Management Systems (EVMS), this organizational integration is achieved through the Organizational Breakdown Structure (OBS), the Responsibility Assignment Matrix (RAM), and the establishment of Control Accounts (CAs).

For Certified Cost Professional (CCP) candidates, understanding how organizational units intersect with deliverable hierarchies to form control accounts—and how Work Packages and Planning Packages are managed within them—is fundamental to cost control, earned value reporting, and contract governance.

---

1. Structural Breakdown Architecture: WBS vs. OBS vs. CBS

Project cost engineering operates at the nexus of three distinct hierarchical structures:

+-----------------------------------------------------------------------------+
|                   THE TRI-AXIAL COST ENGINEERING STRUCTURE                  |
|                                                                             |
|   1. WORK BREAKDOWN STRUCTURE (WBS) --------------> [ WHAT is delivered ]  |
|      - Deliverable-oriented physical/functional scope decomposition         |
|      - Examples: Compressor Skid, Foundation, High-Voltage Substation       |
|                                                                             |
|   2. ORGANIZATIONAL BREAKDOWN STRUCTURE (OBS) ----> [ WHO performs work ]  |
|      - Hierarchical chart of performing organizational units & contractors  |
|      - Examples: Civil Engineering Dept, Piping Lead, Electrical Subcontractor|
|                                                                             |
|   3. COST BREAKDOWN STRUCTURE (CBS) --------------> [ HOW MUCH / WHAT TYPE ]|
|      - Financial chart of accounts classifying resource expenditure types   |
|      - Examples: Direct Labor, Material, Construction Equipment, Subcontracts|
+-----------------------------------------------------------------------------+

The Role of the OBS:

The Organizational Breakdown Structure (OBS) is a functional hierarchy depicting the organization's management structure. It starts with the Project Manager / Executive Sponsor at Level 1 and cascades down through functional department heads, discipline leads, field supervision teams, and specialized external subcontractors. It provides a formal reporting chain for project execution.

---

2. Control Account (CA) Mechanics & Architecture

Under National Standard EIA-748 (Standard for Earned Value Management Systems), the Control Account (CA) is defined as the primary management control point where scope, budget, schedule, and actual cost are integrated and managed.

+-----------------------------------------------------------------------------+
|                     CONTROL ACCOUNT INTERSECTION MATRIX                     |
|                                                                             |
|                       ORGANIZATIONAL BREAKDOWN STRUCTURE (OBS)              |
|                       Civil Dept     Mechanical Dept    Electrical Dept     |
|   WBS DELIVERABLES    (OBS 100)      (OBS 200)          (OBS 300)           |
|   -----------------   ----------     ---------------    ---------------     |
|   1.1 Site Earthwork  [ CA-101 ]           --                 --            |
|                                                                             |
|   1.2 Reactor Module      --           [ CA-201 ]*            --            |
|                                                                             |
|   1.3 Power Substation    --               --             [ CA-301 ]        |
|                                                                             |
|   *CA-201 = Single Control Account at intersection of WBS 1.2 and OBS 200   |
|             Managed by ONE Control Account Manager (CAM)                    |
+-----------------------------------------------------------------------------+

Critical Control Account Integrity Rules for Cost Professionals:

1. The Single Intersection Rule: A Control Account exists at the intersection of exactly ONE WBS element (a deliverable) and exactly ONE OBS element (an organizational unit).
2. Single Point of Management Accountability: Every CA has exactly one named Control Account Manager (CAM). Multiple managers cannot share responsibility for a single CA.
3. No Cross-Organizational Accounts: A Control Account cannot span across multiple OBS departments. If work on a single WBS deliverable requires civil, piping, and electrical departments, three separate Control Accounts must be created under that WBS node.
4. Roll-up Integrity: All project performance metrics—Budget at Completion ($BAC$), Planned Value ($PV$), Earned Value ($EV$), and Actual Cost ($AC$)—roll up cleanly through both the WBS hierarchy (for deliverable reporting) and the OBS hierarchy (for organizational performance reporting).

---

3. Control Account Manager (CAM) Authority & Governance

The Control Account Manager (CAM) is the central operational figure in project performance management. The CAM is typically a discipline lead, engineering manager, or construction superintendent entrusted with full technical and financial ownership of the Control Account.

+-----------------------------------------------------------------------------+
|                        CORE RESPONSIBILITIES OF THE CAM                     |
|                                                                             |
|   1. BASELINE FORMULATION:                                                  |
|      - Develops scope, detailed schedules, and time-phased budgets.         |
|      - Selects Earned Value Measurement Techniques (EVMTs) for WPs.         |
|                                                                             |
|   2. WORK AUTHORIZATION:                                                    |
|      - Receives and executes formal Work Authorization Documents (WADs).    |
|      - Authorizes charging of labor hours, material POs, and subcontracts.  |
|                                                                             |
|   3. PERFORMANCE MEASUREMENT & VARIANCE ANALYSIS:                           |
|      - Evaluates Monthly Cost Variance:  CV = EV - AC                       |
|      - Evaluates Monthly Schedule Variance: SV = EV - PV                    |
|      - Identifies root causes of variances exceeding established thresholds.|
|                                                                             |
|   4. CORRECTIVE ACTION & EAC FORECASTING:                                   |
|      - Develops and executes formal Corrective Action Plans (CAPs).         |
|      - Calculates realistic bottom-up Estimates at Completion (EAC).        |
+-----------------------------------------------------------------------------+

[!IMPORTANT] Work Authorization Document (WAD) Governance: No project work may begin and no costs may be incurred without a signed Work Authorization Document (WAD). The WAD formally transfers contractual budget and schedule authorization from the Project Manager to the CAM. It specifies the approved Statement of Work (SOW), budget values ($BAC$), start/finish dates, and reporting requirements.

---

4. Responsibility Assignment Matrix (RAM) & RACI Charting

The Responsibility Assignment Matrix (RAM) provides the structural bridge linking the WBS to the OBS. In large projects, RAM governance operates at two levels:

• Macro-Level (Project RAM): Maps Level 2/3 WBS elements to OBS departments to identify Control Accounts and assigned CAMs.
• Micro-Level (Operational RAM / RACI): Maps individual Work Packages and schedule activities to team members and functional roles using the RACI model.

+-----------------------------------------------------------------------------+
|                          THE RACI GOVERNANCE FRAMEWORK                      |
|                                                                             |
|   LETTER   ROLE DESIGNATION    DEFINITION & GOVERNANCE RULES                |
|   ------   -----------------   -------------------------------------------  |
|     R      RESPONSIBLE         The "doer" who executes the task or creates  |
|                                the deliverable. (Can be multiple people).   |
|                                                                             |
|     A      ACCOUNTABLE         The individual with ULTIMATE FIDUCIARY       |
|                                OWNERSHIP, approval authority, and veto      |
|                                power. (STRICT RULE: EXACTLY ONE "A").       |
|                                                                             |
|     C      CONSULTED           Subject matter experts whose input is sought |
|                                prior to execution/decision (2-way comms).   |
|                                                                             |
|     I      INFORMED            Stakeholders notified of progress, outcomes, |
|                                or completion (1-way communication).         |
+-----------------------------------------------------------------------------+

Sample RACI Implementation Matrix:

[!CAUTION] The Cardinal RACI Rule: Exactly One "A": A major cause of project failure is assigning multiple Accountables ('A') or zero Accountables to a deliverable. Multiple 'A's create diffusion of responsibility, conflicting direction, and power struggles. Zero 'A's create orphan deliverables with no ownership. There must always be exactly one 'A' per line item.

---

5. Work Packages (WP) vs. Planning Packages (PP) Inside the Control Account

A Control Account is not a monolithic block of budget; it is internally partitioned into Work Packages (WPs) and Planning Packages (PPs).

+-----------------------------------------------------------------------------+
|                 INTERNAL STRUCTURE OF A CONTROL ACCOUNT (CA)                |
|                                                                             |
|   +---------------------------------------------------------------------+   |
|   |                   CONTROL ACCOUNT: CA-MEC-201                       |   |
|   |                   Total Budget at Completion (BAC) = $1,500,000     |   |
|   |                   CAM: J. Rodriguez                                 |   |
|   +---------------------------------------------------------------------+   |
|                                      |                                      |
|               +----------------------+----------------------+               |
|               |                                             |               |
|               v                                             v               |
|   +-----------------------+                     +-----------------------+   |
|   |     WORK PACKAGES     |                     |   PLANNING PACKAGES   |   |
|   |   (Near-Term Scope)   |                     |   (Far-Term Scope)    |   |
|   |   Total: $900,000     |                     |   Total: $600,000     |   |
|   +-----------------------+                     +-----------------------+   |
|   | • WP-101: Shell Fab   |                     | • PP-01: Trim Fitting |   |
|   |   ($400k | Milestone) |                     |   ($250k | Months 10-14)  |
|   | • WP-102: Internals   |                     | • PP-02: Final Testing|   |
|   |   ($300k | Units Comp)|                     |   ($350k | Months 15-18)  |
|   | • WP-103: NDE & X-Ray |                     +-----------------------+   |
|   |   ($200k | 0/100 Rule)|                                                 |
|   +-----------------------+                                                 |
+-----------------------------------------------------------------------------+

Comprehensive Comparison of Work Packages and Planning Packages:

[!IMPORTANT] Budget Preservation Rule During PP to WP Conversion: Under EIA-748 EVMS rules, when a Planning Package is converted into detailed Work Packages, the sum of the budgets of the resulting Work Packages must equal exactly the original budget of the Planning Package. Budget cannot be added, skimmed, or transferred to hide cost variances during rolling wave decomposition without a formal Baseline Change Request (BCR).