8.1 Emergency Response Planning & Incident Command System (ICS/NIMS)

Emergency Response Planning & Incident Command System (ICS/NIMS)

Industrial facilities storing, handling, or manufacturing hazardous substances operate under constant risk of unexpected releases, fires, explosions, and toxic vapor emissions. A Certified Hazardous Materials Manager (CHMM) must master the regulatory frameworks governing emergency planning, establish compliant incident command structures, and execute command protocols under the National Incident Management System (NIMS) and the Incident Command System (ICS).

---

1. Regulatory Architecture: EAP vs. ERP

The Occupational Safety and Health Administration (OSHA) establishes two distinct tiers of facility emergency planning based on whether on-site personnel actively mitigate chemical emergencies or immediately evacuate the premises.

+-----------------------------------------------------------------------------------------+
|                   OSHA EMERGENCY PLANNING REGULATORY CLASSIFICATION                     |
|                                                                                         |
|   REGULATORY STANDARD          SCOPE & INTENT                   MANDATORY ACTIONS       |
|   +--------------------------+--------------------------------+-----------------------+ |
|   | 29 CFR 1910.38           | Facilities where ALL employees | - Total evacuation    | |
|   | Emergency Action Plan    | evacuate upon alarm; NO        | - Primary/alt routes  | |
|   | (EAP)                    | in-house emergency response    | - Headcount accounting| |
|   +--------------------------+--------------------------------+-----------------------+ |
|   | 29 CFR 1910.120(q)       | Facilities utilizing in-house  | - Written ERP document| |
|   | HAZWOPER Emergency       | emergency response teams       | - ICS implementation  | |
|   | Response Plan (ERP)      | (ERT/HAZMAT) to control spills | - HAZWOPER training   | |
|   +--------------------------+--------------------------------+-----------------------+ |
+-----------------------------------------------------------------------------------------+

Emergency Action Plan (EAP - 29 CFR 1910.38)

An EAP is required whenever an OSHA standard mandates it (e.g., Flammable Liquids 1910.106, Process Safety Management 1910.119). Key provisions include:

• Evacuation Only: Explicit policy that all facility employees must evacuate the danger area immediately upon alarm. No employee is permitted to assist in active containment.
• Core Elements: Designates escape routes and emergency exits; establishes employee headcount and accounting procedures; outlines alarm systems and reporting protocols; designates personnel responsible for critical plant shut-down before evacuating.

HAZWOPER Emergency Response Plan (ERP - 29 CFR 1910.120(q))

If an employer chooses to have its own employees respond to chemical releases to stop, contain, or neutralize the hazard, the employer must develop and implement a written ERP meeting 29 CFR 1910.120(q).

Incidental Release vs. Emergency Response:

Under OSHA Compliance Directive CPL 02-02-059, the distinction between an "incidental release" and an "emergency release" determines whether HAZWOPER applies:

• Incidental Release: A release of a hazardous substance that does not pose a significant safety or health hazard to employees in the immediate vicinity or to the cleanup team, and does not have the potential to become an uncontrolled emergency. Maintenance or operating personnel in the immediate work area can absorb, neutralize, or clean up the spill using standard operating procedures without activating the ERP or donning specialized chemical protective equipment.
• Emergency Release: An uncontrolled release that poses a substantial threat to human life, health, or the environment (e.g., toxic gas generation, explosive vapor buildup, fire, oxygen deficiency, or life safety threats). Such releases strictly require the activation of the written ERP and the Incident Command System.

Interfacing Emergency Plans:

Facility emergency planning must integrate overlapping federal programs:

• EPA Risk Management Plan (RMP - 40 CFR Part 68): Requires facilities with threshold quantities of regulated toxic and flammable substances to establish either a non-responding or responding facility program coordinated with local emergency response authorities.
• EPA Spill Prevention, Control, and Countermeasure (SPCC - 40 CFR Part 112): Requires oil storage facilities to maintain discharge response procedures, designated spill coordinators, and mutual aid contacts.
• EPCRA Sections 302/303 (40 CFR Part 355): Requires facilities with Extremely Hazardous Substances (EHSs) at or above Threshold Planning Quantities (TPQs) to appoint a Facility Emergency Coordinator (FEC) to participate with the Local Emergency Planning Committee (LEPC).

---

2. Fundamentals of the Incident Command System (ICS/NIMS)

The Incident Command System is a standardized, on-scene, all-hazard incident management concept originated under FIRESCOPE and formalized federally under Homeland Security Presidential Directive 5 (HSPD-5) and NIMS.

+-----------------------------------------------------------------------------------------+
|                              CORE ICS OPERATIONAL PRINCIPLES                            |
|                                                                                         |
|   1. COMMON TERMINOLOGY:       Standard plain-language terms; no ten-codes or slang     |
|   2. MODULAR ORGANIZATION:     Expands and contracts based on incident size/complexity  |
|   3. MANAGEABLE SPAN OF CONTROL: Optimal ratio 1:5 (operational limits 1:3 to 1:7)     |
|   4. UNIFIED COMMAND:          Joint decision-making for multi-agency / multi-jurisdiction|
|   5. INCIDENT ACTION PLAN:     Consolidated IAP directing all tactical operational periods|
|   6. COMPREHENSIVE RESOURCE MGMT: Categorization, tracking, and status monitoring       |
|   7. INTEGRATED COMMUNICATIONS: Common communications plan, frequencies, and call signs |
+-----------------------------------------------------------------------------------------+

Manageable Span of Control

Span of control refers to the number of individuals or organizational elements that one supervisor can manage effectively during emergency operations: $\text{Optimal Span of Control} = 1:5$ $\text{Acceptable Operational Range} = 1:3 \text{ to } 1:7$

• When a supervisor oversees more than 7 subordinates (ratio $> 1:7$), the organization must expand by adding another layer of supervision (e.g., creating Branches, Divisions, or Groups).
• When a supervisor oversees fewer than 3 subordinates (ratio $< 1:3$), organizational units should be consolidated.

Unified Command

In incidents involving multiple political jurisdictions, multiple agencies (e.g., Local Fire Department, State Environmental Agency, US Coast Guard, EPA Region), or shared private-public responsibility, a Unified Command (UC) structure is established. Under Unified Command:

• Agencies work together through their designated Incident Commanders to formulate common incident objectives, approve a single consolidated Incident Action Plan (IAP), and maximize resource utilization.
• No individual agency surrenders its legal statutory authority, yet the incident is managed as a single integrated operation.

---

3. Command Staff: Functions & Authority

The Incident Command structure is headed by the Incident Commander (IC), supported by specialized Command Staff officers who handle non-operational advisory functions.

+-----------------------------------------------------------------------------------------+
|                                 ICS COMMAND STAFF ROLES                                 |
|                                                                                         |
|   ROLE                        PRIMARY MANDATE & STATUTORY AUTHORITY                     |
|   +-------------------------+---------------------------------------------------------+ |
|   | Incident Commander (IC) | Sets incident objectives, establishes priorities,       | |
|   |                         | authorizes resource requests, and approves the IAP.     | |
|   +-------------------------+---------------------------------------------------------+ |
|   | Safety Officer (SO)     | Assesses scene hazards, monitors tactical safety, and   | |
|   |                         | holds UNILATERAL STOP-WORK AUTHORITY for unsafe ops.    | |
|   +-------------------------+---------------------------------------------------------+ |
|   | Public Information      | Point of contact for media; manages public warnings and | |
|   | Officer (PIO)           | establishes the Joint Information Center (JIC).         | |
|   +-------------------------+---------------------------------------------------------+ |
|   | Liaison Officer (LNO)   | Primary contact for assisting and cooperating agency    | |
|   |                         | representatives (EPA, Coast Guard, LEPC, state DEP).    | |
|   +-------------------------+---------------------------------------------------------+ |
+-----------------------------------------------------------------------------------------+

The Safety Officer's Unilateral Authority

Under both OSHA 29 CFR 1910.120(q)(3)(vii) and ICS guidelines, the Safety Officer is uniquely empowered:

Statutory Mandate: The Safety Officer has the absolute authority to immediately alter, suspend, or terminate any operation or activity judged to be an imminent danger or unsafe condition. The SO does not need prior permission from the Incident Commander to stop an unsafe action, though the SO must inform the IC immediately after taking action.

---

4. General Staff Functional Sections (FLOP)

When incident complexity exceeds the IC's direct span of control, the IC activates the four General Staff functional sections, represented by the acronym FLOP:

+-----------------------------------------------------------------------------------------+
|                                ICS GENERAL STAFF (FLOP)                                 |
|                                                                                         |
|   [ FINANCE / ADMIN ]     [ LOGISTICS ]           [ OPERATIONS ]        [ PLANNING ]    |
|   - Time Unit             - Service Branch:       - Staging Area        - Situation Unit|
|   - Procurement Unit        * Communications      - Branches            - Resource Unit |
|   - Comp / Claims Unit      * Medical Unit        - Divisions (Geo)     - Doc Unit      |
|   - Cost Unit               * Food Unit           - Groups (Func)       - Demob Unit    |
|                           - Support Branch:       - Strike Teams        - Technical     |
|                             * Supply Unit         - Task Forces           Specialists   |
|                             * Facilities Unit     - Single Resources                    |
|                             * Ground Support                                            |
+-----------------------------------------------------------------------------------------+

1. Operations Section

Led by the Operations Section Chief (OSC), this section develops and directly implements tactical operations to accomplish the strategic goals defined by the IC in the Incident Action Plan (IAP).

• Staging Area: Designated location where tactical resources (personnel, foam pumpers, vacuum trucks) assemble while awaiting tactical assignment. Resources in Staging must be available for immediate deployment within 3 minutes.
• Divisions: Organizational levels used to divide an incident into geographical areas of operation (e.g., Division A = North Tank Farm, Division B = Rail Loading Rack).
• Groups: Organizational levels used to divide an incident into functional areas of operation (e.g., Decon Group, HazMat Entry Group, Vapor Suppression Group).
• Strike Team: A set number of resources of the same kind and type, with common communications and an assigned leader (e.g., five Type 1 HazMat Entry Teams).
• Task Force: A combination of mixed resources assembled for a specific tactical mission, with common communications and an assigned leader (e.g., one vacuum truck, one foam tender, and two entry personnel).
• Single Resource: An individual personnel unit and its associated equipment (e.g., one HAZMAT response trailer).

2. Planning Section

Led by the Planning Section Chief (PSC), this section collects, evaluates, and disseminates incident intelligence and situation status.

• Prepares and documents the written Incident Action Plan (IAP) for each operational period.
• Tracks resource status (Assigned, Available, Out-of-Service) via the Resource Unit.
• Houses Technical Specialists (e.g., toxicologists, industrial hygienists, chemical dispersion modelers, structural engineers).
• Manages the Demobilization Unit to ensure orderly, safe site demobilization.

3. Logistics Section

Led by the Logistics Section Chief (LSC), this section provides all facilities, services, and physical support required by incident personnel.

• Service Branch: Communications Unit, Medical Unit (first aid and responder medical monitoring), Food Unit.
• Support Branch: Supply Unit (ordering equipment, PPE, sorbents), Facilities Unit (sleeping, sanitation), Ground Support Unit (fueling, maintaining apparatus).

4. Finance/Administration Section

Led by the Finance/Admin Section Chief (FSC), this section tracks financial and administrative aspects of the incident.

• Time Unit: Tracks personnel operating hours for payroll and contractor billing.
• Procurement Unit: Executes commercial equipment leases, contractor contracts, and vendor purchases.
• Compensation & Claims Unit: Manages worker injury claims, liability documentation, and property damage claims.
• Cost Unit: Tracks total cumulative financial burn rate and projects final incident costs.

---

5. Summary Reference: ICS Organizational Hierarchy