EOP Example — Utility Power Loss Response

Document ID: EOP-PWR-001

Revision: 1.0

Status: Example

Activation: Utility Power Loss

1. Purpose

Provide a structured response framework for utility power loss events affecting critical infrastructure operations, with focus on personnel safety, operational overview, emergency power verification, communication, escalation and incident control.

2. Scope

Applies to abnormal conditions involving total or partial loss of normal utility power to critical facilities, including data centers, technical infrastructure spaces and supporting operational systems.

This example does not replace electrical switching procedures, emergency evacuation procedures, manufacturer instructions, utility coordination requirements, 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:

Loss of utility power to critical systems or infrastructure
Unexpected transfer to generator or battery-supported operation
UPS systems operating on battery due to upstream utility loss
Generator startup following utility failure
Partial facility blackout or abnormal electrical condition
Loss of redundancy affecting critical power infrastructure
Unclear or unstable power system operating state

Emergency principle: Stabilize first. Diagnose second. Maintain operational overview throughout the event.

4. Immediate Response Priorities

Priority	Focus Area	Objective
1	Life Safety	Protect personnel and confirm no immediate safety hazard exists.
2	Operational Overview	Determine current infrastructure state and affected systems.
3	Emergency Power	Confirm generator, UPS and transfer system behavior.
4	Impact Control	Limit escalation, instability or secondary failures.
5	Communication	Inform responsible stakeholders and maintain updates.
6	Incident Logging	Maintain timeline and record key observations/actions.

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	FACILITY	Confirm personnel safety and identify any immediate hazard.	No active life-safety emergency identified.	Operations / Security
3	BMS / EPMS / DCIM	Review active alarms, event logs and current infrastructure state.	Affected systems and current operating mode identified.	Operations
4	UPS-A / UPS-B	Verify UPS operating condition and battery status.	UPS systems supporting load as expected.	Power Specialist
5	GEN-001 / GEN-002	Verify generator startup, stabilization and load acceptance.	Generators operating normally or issue escalated immediately.	Generator Specialist
6	ATS / SWITCHGEAR	Confirm transfer equipment state and power-path condition.	Power path status understood and recorded.	Electrical Responsible Person
7	DATAHALL / TECH AREAS	Verify cooling systems, monitoring systems and critical operational areas remain stable.	No secondary infrastructure failure observed.	Facility Operations
8	COMMUNICATION	Notify required stakeholders according to incident communication plan.	Stakeholder notification completed and logged.	Incident Lead
9	INCIDENT LOG	Start or maintain incident timeline and event log.	Actions, alarms and decisions continuously recorded.	Assigned Recorder
10	OPS-BRIDGE	Establish next update interval and escalation threshold.	Response cadence agreed and communicated.	Incident Lead

6. Stop Conditions / Escalation Triggers

Immediate escalation is required if one or more of the following conditions occur:

Generator fails to start or remain stable
UPS runtime becomes uncertain or battery autonomy degrades unexpectedly
Critical load shutdown occurs or appears likely
Loss of cooling or secondary infrastructure begins
Smoke, electrical smell, fire alarm or arc-related concern observed
Power-path state cannot be confirmed
Personnel safety becomes uncertain
Facility redundancy falls below approved operational limits

Control rule: If the operating state is unclear, assume increased risk until verified otherwise.

7. Communication Structure

During utility loss events, communication should remain structured, factual and time-based.

Use one operational lead for coordination
Separate technical investigation from stakeholder communication
Avoid unverified assumptions during updates
Record times for all major changes and decisions
Maintain regular update intervals during unstable conditions

Example update structure:

Time → Current State → Impact → Actions → Risk Level → Next Update

8. Recovery and Return to Normal

Return to normal operation should be controlled and verified. Utility restoration alone does not automatically mean the incident is resolved.

Confirm utility stability before normalization
Verify UPS systems returned to approved operating state
Verify generators returned to standby condition
Review alarms, events and abnormal conditions
Confirm cooling and monitoring systems stable
Confirm no hidden degraded condition remains
Complete incident documentation and closeout review

9. Related Procedures

Planned Utility Transfer Test (MOP)
UPS Maintenance Bypass Procedure (SOP)
Generator Weekly Inspection Procedure (SOP)
Cooling Failure Response (EOP)
Site Electrical Switching Procedure (Site-Specific)

10. Operational Notes

Utility power loss events often create secondary operational risks beyond the initial outage itself. Cooling stability, battery runtime, transfer behavior, monitoring visibility and human communication quality all influence the final outcome.

Strong incident response depends on maintaining operational overview, avoiding uncontrolled parallel action and escalating uncertainty early.

Real emergency response procedures must align with facility design, utility agreements, local regulations, electrical safety requirements, emergency management structure and approved operational governance.

Type: EOP Example

Category: Emergency Power / Incident Response

Criticality: Critical

Status: Public example — not for direct production use

Key principles: establish control, verify the power path, protect critical load, communicate clearly, escalate uncertainty early and maintain a structured incident timeline.