1.2 Organization & Resource Breakdown Structures (OBS, RBS, RAM)

1.2 Organization & Resource Breakdown Structures (OBS, RBS, RAM)

AACE Professional Context: Defining project scope via the Work Breakdown Structure represents only one dimension of project controls. In total cost management, planners must establish who executes the work, what resources are mobilized, and how financial accounts capture expenditures. Integrating the Work Breakdown Structure (WBS) with the Organizational Breakdown Structure (OBS), the Resource Breakdown Structure (RBS), and the Cost Breakdown Structure (CBS) establishes the governance architecture required for Earned Value Management (EVM). For PSP preparation, understand how these structures support responsibility, resource analysis, cost collection, and integrated control, while applying the governance conventions stated in the scenario.

---

The Multi-Dimensional Architecture of Project Breakdown Structures

Comprehensive project controls requires four foundational breakdown structures operating in concert:

1. Work Breakdown Structure (WBS): Organizes WHAT authorized scope is controlled.
2. Organizational Breakdown Structure (OBS): Identifies WHO is performing and managing the work (Organization & Authority).
3. Resource Breakdown Structure (RBS): Classifies WHAT RESOURCES (labor, equipment, materials) are utilized.
4. Cost Breakdown Structure (CBS): Tracks HOW MONEY is categorized and expensed (General Ledger alignment).

                    ┌──────────────────────────────────────────────┐
                    │          THE PROJECT CONTROLS CUBE           │
                    ├──────────────────────────────────────────────┤
                    │  Scope (WBS)       --> What is produced?     │
                    │  Organization (OBS)--> Who executes the work?│
                    │  Resources (RBS)   --> What assets are used? │
                    │  Accounts (CBS)    --> How are costs charged?│
                    └──────────────────────────────────────────────┘

---

Organizational Breakdown Structure (OBS) Architecture

The Organizational Breakdown Structure (OBS) is a hierarchical model depicting the project management organization, functional operating departments, field teams, joint-venture partners, and prime subcontractors.

Characteristics of the OBS

• Reporting Lines and Authority: Unlike the WBS, which decomposes physical things, the OBS decomposes human and organizational entities. It clearly outlines chains of command, supervisory spans of control, and organizational resource pools.
• Independence from Scope: An OBS exists independently of any single project's physical deliverables. For instance, the "Mechanical Engineering Department" or "Electrical Subcontractor Inc." exists within the OBS regardless of whether the project is constructing a chemical plant or a commercial terminal.
• Resource Custodianship: Functional managers within the OBS are responsible for maintaining craft pools, professional development, technical standards, and wage classifications.

                                  1.0 Executive Leadership
                                            │
                        ┌───────────────────┴───────────────────┐
                        │                                       │
            2.0 Engineering Division                3.0 Construction Execution
            ├── 2.1 Civil / Structural              ├── 3.1 Civil Earthworks Sub
            ├── 2.2 Mechanical & Piping             ├── 3.2 Mechanical Erection Sub
            └── 2.3 Electrical & I&C                └── 3.3 Electrical & Telecom Sub

---

Resource Breakdown Structure (RBS) Categorization

The Resource Breakdown Structure (RBS) is a hierarchical classification of resources organized by resource category and resource type. It provides a standardized framework for resource allocation, schedule leveling, and direct cost estimating.

Core Categories of the RBS

1. Labor (Personnel):
   • Direct Craft Labor: Welders, pipefitters, electricians, carpenters, ironworkers, equipment operators.
   • Indirect Project Labor: Superintendents, field engineers, safety inspectors, quality control managers, schedulers.
   • Engineering / Design Labor: Process engineers, structural modelers, CAD drafters, procurement expediters.
2. Equipment (Machinery & Fleets):
   • Heavy Lifting & Rigging: 500-ton crawler cranes, mobile hydraulic cranes, tower cranes.
   • Earthmoving Equipment: Excavators, bulldozers, dump trucks, trenchers.
   • Specialized Construction Tools: Orbital welding machines, hydrostatic test skids, heat-treatment rigs.
3. Materials (Bulk & Engineered):
   • Engineered Equipment: Compressors, pumps, turbines, heat exchangers, transformers, control valves.
   • Bulk Materials: Structural steel beams, piping spools, conduit, concrete, rebar, gravel.
   • Consumables: Welding gas, grinding discs, formwork timber, fuel.
4. Subcontractors & Specialist Services:
   • NDT (Non-Destructive Testing) radiographic inspection, specialized refractory lining, post-weld heat treatment.

Role of RBS in CPM Scheduling

When assigning resources to CPM schedule activities in software, linking each resource code to the global RBS allows the planner to execute resource leveling across specific craft pools (e.g., leveling all "Class A Pipefitters" across multiple concurrent work packages without distorting non-pipefitter activities).

---

Responsibility Assignment Matrix (RAM) & RACI Governance

The Responsibility Assignment Matrix (RAM) cross-references the WBS with the OBS to ensure that every single scope deliverable is assigned to a responsible organizational unit or role.

The RACI Framework

One common notation for a RAM is the RACI matrix:

• R — Responsible (The Doer): The role or individual who performs the work to achieve the deliverable. Multiple individuals can share "R" duties on a team.
• A — Accountable (The Owner / Approver): The single individual with ultimate decision-making authority, veto power, and ownership of the deliverable outcome. The "A" must answer for deliverable completion, quality, budget, and schedule compliance.
• C — Consulted (The Subject Matter Expert): Individuals or teams whose technical expertise or statutory approval is required prior to completing the deliverable or making a major change. This involves two-way communication.
• I — Informed (The Stakeholder): Individuals or departments kept updated on progress, milestones, or completion. This involves one-way communication.

A common single-accountability RACI convention

Common convention: assign one clearly Accountable role to each row. The project should document its adopted notation and decision authority.

Multiple approval roles can create ambiguity unless their distinct authorities are defined. Under a single-accountability RACI convention, one A clarifies final decision ownership while several roles may remain Responsible or Consulted.

Example High-Level Responsibility Assignment Matrix (RAM)

Note: An individual can be both Accountable and Responsible (A/R) when they personally oversee and execute the task.

---

The Control Account (CA): Where Scope and Organization Converge

A Control Account (CA) is a management control point where scope, organization, schedule, and budget are integrated; it is commonly described at an intersection of the WBS and OBS.

                                   WBS (Scope Axis)
                       1.1 Substructure   1.2 Core & Shell   1.3 MEP Infrastructure
                     ┌──────────────────┬──────────────────┬──────────────────────┐
Civil Dept (OBS)     │ CONTROL ACCOUNT  │                  │                      │
                     │    CA-CIV-01     │                  │                      │
                     ├──────────────────┼──────────────────┼──────────────────────┤
Structural Dept (OBS)│                  │ CONTROL ACCOUNT  │                      │
                     │                  │    CA-STR-02     │                      │
                     ├──────────────────┼──────────────────┼──────────────────────┤
Mechanical Dept (OBS)│                  │                  │   CONTROL ACCOUNT    │
                     │                  │                  │      CA-MEP-03       │
                     └──────────────────┴──────────────────┴──────────────────────┘

Significance of the Control Account in Project Controls

1. Management Control Point: A Control Account is the formal level where scope, budget, and schedule are integrated. It is the primary node for measuring project performance via Earned Value Management (EVM).
2. Performance Measurement Baseline (PMB) Allocation: The Performance Measurement Baseline is distributed down to Control Accounts. Budget at Completion (BAC), Planned Value (PV), Earned Value (EV), and Actual Cost (AC) are calculated and analyzed at the CA level.
3. Decomposition into Packages: Within a Control Account, work is subdivided into:
   • Work Packages (WPs): Near-term, detailed work scopes with assigned budgets and CPM schedule activities.
   • Planning Packages (PPs): Far-term work held at budget and high-level duration, rolled into work packages as execution approaches.

---

The Control Account Manager (CAM): Role and Mandate

An EVMS governance design identifies a Control Account Manager (CAM) or equivalent responsible manager for each Control Account, with authority and duties defined by the organization.

Core Responsibilities of the CAM

• Baseline Planning: Collaborating with the project planner to build the original scope, schedule, and cost baseline for the control account.
• Work Authorization: Formally opening internal charge numbers to allow field labor and procurement orders to charge against the account.
• Progress Assessment: Objectively evaluating physical percent complete on underlying work packages each reporting period using defined Earned Value Measurement Techniques (EVMTs).
• Variance Analysis: Reviewing monthly cost variances ($CV = EV - AC$) and schedule variances ($SV = EV - PV$). If performance exceeds contractual variance thresholds, the CAM authors the formal Variance Analysis Report (VAR) detailing root causes, impact projections, and corrective action plans.
• Change Management: Authoring or approving baseline change requests affecting the Control Account and maintaining the CAM Notebook (audit trail of assumptions, contracts, and revisions).

Governance check: when the project uses a single-CAM convention, each Control Account names one accountable CAM, while one CAM may manage multiple accounts. Apply the governance model stated by the organization or exam scenario rather than claiming that an AACE Recommended Practice creates a universal organization chart.

---

Cost Breakdown Structure (CBS) & the Code of Accounts (COA)

A frequent breakdown in project execution occurs when project controls schedules cannot communicate with corporate accounting software. The bridge that connects scope, schedule, organization, and finances is the Code of Accounts (COA).

Cost Breakdown Structure (CBS) vs. WBS

• The WBS organizes costs by deliverable (e.g., Foundation Slab, Compressor Skid).
• The CBS organizes costs by accounting expense type (e.g., Direct Labor Wages, Equipment Rental, Bulk Materials, Subcontract Billings, Overhead/Indirects).
• The General Ledger (GL) operates under the corporate Chart of Accounts, tracking invoices, debits, credits, and taxes.

The Standardized Code of Accounts (COA)

The Code of Accounts is a standardized alphanumeric coding system that uniquely indexes every WBS element, OBS organizational node, and CBS expenditure line item.

                      STRUCTURE OF AN INTEGRATED CHARGE CODE
                                 102-12-04-5110
                                  │   │  │   │
  Project Number (Project 102) ───┘   │  │   └── CBS Expense Element (5110 = Direct Craft Labor)
  WBS Deliverable (1.2 Compressor) ───┘  └────── OBS Discipline (04 = Mechanical Execution)

When a pipefitter enters hours on a timesheet or a vendor submits an invoice for pipe valves, the transaction is tagged with the exact Code of Accounts number. This allows the ERP system (e.g., SAP, Oracle) to automatically pass actual costs ($ACWP$) directly into the corresponding WBS Work Package in the scheduling and earned value software.

Without a synchronized Code of Accounts, project controllers must manually re-code thousands of accounting transactions each month, resulting in late data, misallocated costs, and distorted Cost Performance Index ($CPI$) figures.

---

Common Pitfalls & Exam Traps

1. Ambiguous accountability in RACI tables: Under a stated one-A convention, two undifferentiated Accountable roles require correction or explicit separation of decision authority.
2. Unclear Control Account authority: The adopted EVMS governance should identify who approves changes, owns forecasts, and explains variance for the account.
3. Conflating the OBS with the WBS: Keep performing organizations in the OBS or RAM and map them to the authorized scope structure, whether that WBS is product or process oriented.
4. Failure to Convert Planning Packages: Allowing field labor to charge hours directly to a Planning Package. Planning packages should be detail-planned and converted according to the EVMS work-authorization rules before the associated work begins.
5. Misaligned Accounting Charge Codes: Allowing corporate accounting to collect all labor under a single general plant charge code, making it impossible to determine which specific WBS control account incurred cost overruns.

---

Worked Example: Petrochemical Gas Compression Unit

An engineering and construction firm is executing a $120 million petrochemical expansion. WBS Element 1.3.2 "Feed Gas Compression Skid" has been established.

Step 1: Mapping the Intersection to Establish the Control Account

• WBS Element: 1.3.2 Feed Gas Compression Skid (Deliverable Scope)
• OBS Unit: 3.2 Mechanical Execution Department (Performing Organization)
• Control Account Established: CA-COMP-01
• Designated CAM: Marcus Vance, P.E. (Lead Mechanical Project Engineer)
• Budget at Completion (BAC): $4,200,000

Step 2: Internal Control Account Decomposition

Marcus Vance and the planning team decompose CA-COMP-01 into near-term Work Packages and a far-term Planning Package:

• WP-101: Structural Base & Anchor Skid Installation (BAC: $650,000 — Duration: 4 Weeks — EVMT: Milestone Weighting)
• WP-102: Reciprocating Compressor Core Rigging & Setting (BAC: $1,400,000 — Duration: 3 Weeks — EVMT: Physical % Complete)
• WP-103: Suction/Discharge Lube Oil Piping Interconnects (BAC: $1,150,000 — Duration: 6 Weeks — EVMT: Quantity Tracking [Linear Feet])
• PP-201: Skid Pre-Commissioning & Lube Oil Flushing (BAC: $1,000,000 — Planning Package: To be converted to WP-104 60 days prior to turnover)

Step 3: Code of Accounts (COA) Integration

Every purchase order and timesheet is indexed to ensure pristine accounting roll-up:

• Labor charging to structural rigging on WP-101: PRJ120-WBS132-WP101-OBS32-CBS5100 (Direct Craft Labor)
• Specialized 300-ton crane rental for WP-102: PRJ120-WBS132-WP102-OBS32-CBS5300 (Equipment Rental)
• Seamless data flow enables the project controls system to calculate monthly earned value without manual reconciliation errors.