Emergency Response Planning Template for Public Drinking Water Systems

Standard Operating Procedure: Emergency Response Planning (ERP) for Public Drinking Water Systems

1. Document Control Block

---

2. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional requirements, structural phases, and operational execution metrics for developing, maintaining, and executing the Emergency Response Plan (ERP) for public drinking water systems.

The purpose of this procedure is to ensure continuous potable water delivery, rapid threat mitigation, regulatory compliance under the EPA/AWIA framework, and safeguarding of public health during natural disasters, infrastructure failures, cyber-attacks, or intentional contamination events.

---

3. Scope & Prerequisites

Scope

This procedure applies to all Class A, B, and C public drinking water systems managed, operated, or monitored under Template Registry infrastructure, including source water abstraction, treatment facilities, storage reservoirs, and distribution network nodes.

Prerequisites & Required Tools

• Software: Enterprise GIS (ArcGIS/QGIS), SCADA (Supervisory Control and Data Acquisition) with remote isolation capability, WaterCAD/EPANET hydraulic modeling tools, and mass notification software (Alertus/Everbridge).
• Hardware: Redundant emergency power (Tier 4 generators), portable satellite communications (BGAN/Iridium), field testing kits (Colilert, Hach DR900), and SCADA backup HMI terminals.
• Personal Protective Equipment (PPE): Level C/D ensemble (as dictated by hazard assessment), chemical-resistant gloves, steel-toed footwear, and NIOSH-approved particulate/vapor respirators.

---

4. Roles & Responsibilities (RACI Matrix)

• R = Responsible (The role that performs the activity)
• A = Accountable (The role with final approval and fiduciary ownership)
• C = Consulted (The role providing advisory input)
• I = Informed (The role kept updated on progress/status)

---

5. Step-by-Step Procedure

Phase 1: Risk Assessment & Hazard Identification

• 1.1 Review and update asset characterization data, mapping all critical nodes (intakes, treatment trains, booster stations, finished water storage).
• 1.2 Perform threat analyses covering malevolent acts (cyber-attacks, physical sabotage, chemical injection) and natural hazards (seismic activity, extreme weather, flooding).
• 1.3 Validate vulnerability scores using the EPA Risk Assessment Methodology (RAM) or equivalent institutional standards.
• 1.4 Ensure all physical security perimeters (SCADA enclosures, chemical containment zones, wellheads) meet AWWA Standard M28 criteria.

Phase 2: ERP Plan Architecture & Drafting

• 2.1 Assemble the baseline ERP utilizing the Template Registry standardized modular structure.
• 2.2 Define clear emergency action triggers based on SCADA alarms, water quality exceedances (e.g., turbidity > 1.0 NTU, chlorine residual < 0.2 mg/L), or physical security breaches.
• 2.3 Establish explicit lines of succession and delegation of authority for the Incident Command System (ICS) structure.
• 2.4 Compile an up-to-date, verified internal and external emergency contact matrix (Local Hazmat, State Primacy Agency, EPA Region, Local Law Enforcement).

Phase 3: Notification Protocols & Communications Plan

• 3.1 Configure automated public notification templates for Tier 1 public water system (PWS) violations (e.g., E. coli contamination, acute chemical toxicity).
• 3.2 Test mass notification systems quarterly to ensure 95%+ delivery success to affected service populations within 60 minutes of authorization.
• 3.3 Establish secure, encrypted communication channels between the Incident Command Post (ICP), field operators, and municipal/state emergency operations centers (EOCs).
• 3.4 Prepare standardized media holding statements for public information officers (PIOs) to prevent misinformation spread.

Phase 4: Operational Mitigation & Response Execution

• 4.1 Immediate Isolation: Upon threat confirmation, isolate affected treatment trains or distribution zones via remote SCADA actuation or manual valve closures.
• 4.2 Alternative Water Supplies: Activate mutual aid agreements (WARN networks) and deploy emergency interconnections or bottled/tanker water distribution points within 4 hours of primary supply loss.
• 4.3 Sampling & Monitoring: Increase grab sampling frequency to hourly at critical control points; analyze parameters for biological, chemical, or radiological contaminants based on threat signature.
• 4.4 Remediation & Flushing: Execute unidirectional flushing (UDF) protocols and breakpoint chlorination or targeted chemical neutralization as directed by the Incident Commander and state primacy agency.

Phase 5: Incident Closure & Post-Incident Review

• 5.1 Obtain written clearance from the State Primacy Agency and public health officials prior to lifting boil-water advisories or returning systems to service.
• 5.2 Conduct a mandatory After-Action Report (AAR) workshop within 14 calendar days of incident resolution with all key stakeholders.
• 5.3 Update the ERP document repository with lessons learned, root-cause analyses, and necessary capital improvement modifications.
• 5.4 Submit required regulatory post-incident reports to the EPA within the mandated statutory window (typically 30 days).

---

6. Quality Assurance & Pro-Tips

Best Practices (Pro-Tips)

• SCADA Air-Gapping: Maintain strict network segmentation between operational technology (OT) and enterprise IT networks to prevent lateral movement during cyber intrusions.
• Redundant Power Testing: Execute monthly load-bank tests on emergency diesel generators and maintain a minimum 72-hour fuel supply on-site under standard operating capacity.
• Pre-Scripted Notices: Keep pre-approved, multi-lingual public safety notification templates formatted and ready for immediate deployment to eliminate drafting delays during high-stress crises.

Common Pitfalls to Avoid

• Outdated Contact Lists: Relying on unverified phone numbers or email addresses in the contact matrix; verify all external agency rosters bi-annually.
• Single Points of Failure: Failing to designate secondary and tertiary operational leads in the ICS chain of command, leading to command paralysis if the primary lead is incapacitated.

Metric Thresholds

• Time-to-Isolation (TTI): Critical distribution contamination isolation must be achieved within $\le 30\text{ minutes}$ of verified alarm.
• Public Notification Execution: Tier 1 public alerts must be disseminated within $\le 24\text{ hours}$ of violation confirmation (target threshold: $\le 60\text{ minutes}$ for acute biological threats).

---

7. Frequently Asked Questions (FAQ)

Q1: What triggers an automatic mandatory update to the ERP outside of the annual review cadence?
A: Any significant structural modification to the water system (e.g., addition of a new treatment train, change in primary disinfection chemistry), a declared local or federal state of emergency affecting utility operations, or a cyber/physical security breach necessitates an immediate ERP review and update within 30 days.

Q2: How do we coordinate emergency response actions when local law enforcement establishes a crime scene at a water facility?
A: Under the Incident Command System (ICS), Unified Command must be established immediately between utility operations and law enforcement. Plant operators retain technical control over water safety adjustments (e.g., shutting down pumps, adjusting chemical feeds), while law enforcement controls site access, forensics, and perimeter security. Never compromise structural integrity or public health without coordinating access clearances through the law enforcement Incident Commander.