1. Purpose
Provide a structured response framework for water leak or water detection incidents affecting critical infrastructure operations, with focus on personnel safety, leak containment, infrastructure protection, operational overview, escalation and incident control.
2. Scope
Applies to abnormal conditions involving water leaks, condensate leaks, pipe failures, cooling-water incidents, roof ingress, drainage overflow or water detection alarms affecting technical rooms, data halls or supporting infrastructure spaces.
This example does not replace plumbing repair procedures, electrical safety procedures, fire procedures, manufacturer instructions, local regulations or site-specific emergency plans.
3. Activation Criteria
This EOP may be activated when one or more of the following conditions are observed:
- Visible water leak in a technical or operational area
- Water detection alarm activation
- Condensation or moisture affecting critical infrastructure
- Pipe, valve or hose failure
- Cooling-water leak affecting operational rooms
- Roof ingress or external water intrusion
- Drain blockage or overflow condition
- Water located near energized equipment or critical systems
Emergency principle: Protect personnel first, then stop spread, then stabilize infrastructure impact.
4. Immediate Response Priorities
| Priority | Focus Area | Objective |
|---|---|---|
| 1 | Life Safety | Identify electrical, slip or structural hazards. |
| 2 | Leak Identification | Determine source, location and active spread. |
| 3 | Containment | Limit water spread and protect critical infrastructure. |
| 4 | Operational Overview | Determine affected systems and current operational risk. |
| 5 | Communication | Notify responsible stakeholders and escalation paths. |
| 6 | Incident Logging | Maintain timeline and operational record. |
5. Initial Response Procedure
| Step | Area/Tag | Action | Verification | Owner |
|---|---|---|---|---|
| 1 | OPS-BRIDGE | Declare operational incident and assign response lead. | Single responsible coordinator established. | Operations Lead |
| 2 | AFFECTED AREA | Confirm personnel safety and identify immediate hazards. | No uncontrolled electrical or personnel hazard remains. | Operations / Security |
| 3 | WATER-DETECTION / ROOM | Identify visible leak source, leak path and affected area. | Leak location and spread direction understood. | Facility Operations |
| 4 | CRITICAL INFRASTRUCTURE | Determine whether water threatens energized equipment or critical systems. | Current infrastructure risk level identified. | Electrical Responsible Person |
| 5 | CONTAINMENT | Deploy approved containment measures if safe and available. | Water spread reduced or controlled where possible. | Facility Operations |
| 6 | BMS / DCIM | Review alarms and affected environmental or cooling systems. | Secondary infrastructure impact identified. | Operations |
| 7 | COMMUNICATION | Notify required stakeholders according to incident communication plan. | Stakeholder notification completed and logged. | Incident Lead |
| 8 | INCIDENT LOG | Start or maintain incident timeline and operational log. | Observations, actions and escalation decisions continuously recorded. | Assigned Recorder |
| 9 | OPS-BRIDGE | Establish monitoring interval and escalation threshold. | Response cadence agreed and communicated. | Incident Lead |
6. Containment and Stabilization
Containment actions should focus on limiting infrastructure exposure while maintaining personnel safety and operational control.
- Protect energized equipment from direct water exposure
- Prevent water migration into additional technical areas
- Protect floor openings, cable penetrations and airflow paths
- Use only approved containment materials and methods
- Maintain safe access and evacuation routes
- Escalate immediately if leak source cannot be identified
Any isolation of water systems, cooling systems or electrical systems should follow approved site procedures and authorized decision-making.
Control rule: Avoid uncontrolled intervention near energized equipment. Escalate uncertainty early.
7. Escalation Triggers
Immediate escalation is required if one or more of the following conditions occur:
- Water reaches energized equipment or power infrastructure
- Leak source cannot be identified or controlled
- Cooling infrastructure becomes affected
- Water spreads into critical technical areas
- Structural damage or ceiling instability is suspected
- Environmental monitoring becomes unavailable
- Additional leaks or alarm points appear
- Personnel safety becomes uncertain
8. Communication Structure
Water incidents should be communicated using clear factual updates focused on:
- Current leak status
- Affected areas
- Infrastructure risk level
- Containment progress
- Escalation actions
- Expected next update
Example update structure:
9. Recovery and Return to Normal
Recovery should focus on restoring a known safe and stable operating condition before closing the incident.
- Verify leak source isolated or repaired
- Verify no remaining active water spread
- Inspect affected infrastructure for residual risk
- Confirm cooling, power and monitoring systems stable
- Review environmental alarms and moisture conditions
- Remove temporary containment only after approval
- Complete incident documentation and operational review
10. Related Procedures
- Cooling Failure Response (EOP)
- Cooling System Visual Inspection Procedure (SOP)
- CRAC/CRAH Planned Maintenance (MOP)
- Utility Power Loss Response (EOP)
- Site Water Isolation Procedure (Site-Specific)
11. Operational Notes
Water incidents in technical facilities are often deceptive. Small leaks can migrate through cable routes, floor penetrations, ceilings, containment systems and hidden infrastructure paths before becoming fully visible.
Strong response depends on maintaining overview, escalating early and preventing secondary infrastructure impact while avoiding unsafe improvisation.
Real emergency response procedures must align with facility design, electrical safety requirements, environmental controls, local regulations and approved operational governance.
Key principles: protect personnel, identify the leak source, contain spread, protect infrastructure, escalate early and maintain a structured incident timeline.
Template provided by © Tom Jensen | tomjensen.no