EOP-004-4 – Event Reporting
Purpose
To improve the reliability of the Bulk Electric System by requiring the reporting of events by Responsible Entities.
Applicability
4.1. Functional Entities: For the purpose of the Requirements and the EOP-004 Attachment 1 contained herein, the following functional entities will be collectively referred to as “Responsible Entity.”
4.1.1. Reliability Coordinator
4.1.2. Balancing Authority
4.1.3. Transmission Owner
4.1.4. Transmission Operator
4.1.5. Generator Owner
4.1.6. Generator Operator
4.1.7. Distribution Provider
5. Effective Dates:
4/1/2019
Requirements and Measures
R1. Each Responsible Entity shall have an event reporting Operating Plan in accordance with EOP-004-4 Attachment 1 that includes the protocol(s) for reporting to the Electric Reliability Organization and other organizations (e.g., the Regional Entity, company personnel, the Responsible Entity’s Reliability Coordinator, law enforcement, or governmental authority). [Violation Risk Factor: Lower] [Time Horizon: Operations Planning]
M1. Each Responsible Entity will have a dated event reporting Operating Plan that includes protocol(s) and each organization identified to receive an event report for event types specified in EOP-004-4 Attachment 1 and in accordance with the entity responsible for reporting.
R2. Each Responsible Entity shall report events specified in EOP-004-4 Attachment 1 to the entities specified per their event reporting Operating Plan by the later of 24 hours of recognition of meeting an event type threshold for reporting or by the end of the Responsible Entity’s next business day (4 p.m. local time will be considered the end of the business day). [Violation Risk Factor: Medium] [Time Horizon: Operations Assessment]
M2. Each Responsible Entity will have as evidence of reporting an event to the entities specified per their event reporting Operating Plan either a copy of the completed EOP-004-4 Attachment 2 form or a DOE-OE-417 form; and some evidence of submittal (e.g., operator log or other operating documentation, voice recording, electronic mail message, or confirmation of facsimile) demonstrating that the event report was submitted by the later of 24 hours of recognition of meeting an event type threshold for reporting or by the end of the Responsible Entity’s next business day (4 p.m. local time will be considered the end of the business day).
Compliance
1. Compliance Monitoring Process
1.1. Compliance Enforcement Authority:
“Compliance Enforcement Authority” means NERC or the Regional Entity, or any entity as otherwise designated by an Applicable Governmental Authority, in their respective roles of monitoring and/or enforcing compliance with mandatory and enforceable Reliability Standards in their respective jurisdictions.
1.2. Evidence Retention:
The Responsible Entity shall keep data or evidence to show compliance as identified below unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of time as part of an investigation:
The following evidence retention periods identify the period of time an entity is required to retain specific evidence to demonstrate compliance. For instances where the evidence retention period specified below is shorter than the time since the last audit, the Compliance Enforcement Authority may ask an entity to provide other evidence to show that it was compliant for the full time period since the last audit.
-
- Each Responsible Entity shall retain the current Operating Plan plus each version issued since the last audit for Requirement R1, and Measure M1.
- Each Responsible Entity shall retain evidence of compliance since the last audit for Requirement R2 and Measure M2.
If a Responsible Entity is found non-compliant, it shall keep information related to the non-compliance until mitigation is complete and approved or for the duration specified above, whichever is longer.
The Compliance Enforcement Authority shall keep the last audit records and all requested and submitted subsequent audit records.
1.3. Compliance Monitoring and Enforcement Program
As defined in the NERC Rules of Procedure, “Compliance Monitoring and Enforcement Program” refers to the identification of the processes that will be used to evaluate data or information for the purpose of assessing performance or outcomes with the associated Reliability Standard.
EOP-004 – Attachment 1: Reportable Events
NOTE: Under certain adverse conditions (e.g. severe weather, multiple events) it may not be possible to report the damage caused by an event and issue a written Event Report within the timing in the standard. In such cases, the affected Responsible Entity shall notify parties per Requirement R2 and provide as much information as is available at the time of the notification. Submit reports to the ERO via one of the following: e-mail: systemawareness@nerc.net, Facsimile 404-446-9770 or Voice: 404-446-9780.
Submit EOP-004 Attachment 2 (or DOE-OE-417) pursuant to Requirements R1 and R2.
Rationale for Attachment 1:
System-wide voltage reduction to maintain the continuity of the BES: The TOP is operating the system and is the only entity that would implement system-wide voltage reduction.
Complete loss of Interpersonal Communication and Alternative Interpersonal Communication capability at a BES control center: To align EOP-004-4 with COM-001-2.1. COM-001-2.1 defined Interpersonal Communication for the NERC Glossary of Terms as: “Any medium that allows two or more individuals to interact, consult, or exchange information.” The NERC Glossary of Terms defines Alternative Interpersonal Communication as: “Any Interpersonal Communication that is able to serve as a substitute for, and does not utilize the same infrastructure (medium) as, Interpersonal Communication used for day-to-day operation.”
Complete loss of monitoring or control capability at a BES control center: Language revisions to: “Complete loss of monitoring or control capability at a BES control center for 30 continuous minutes or more” provides clarity to the “Threshold for Reporting” and better aligns with the ERO Event Analysis Process.
|
Event Type |
Entity with Reporting Responsibility |
Threshold for Reporting |
|
Damage or destruction of a Facility |
Damage or destruction of a Facility within its Reliability Coordinator Area, Balancing Authority Area or Transmission Operator Area that results in action(s) to avoid a BES Emergency. |
|
Event Type |
Entity with Reporting Responsibility |
Threshold for Reporting |
|
Damage or destruction of its Facility |
Damage or destruction of its Facility that results from actual or suspected intentional human action.
It is not necessary to report theft unless it degrades normal operation of its Facility. |
|
|
Physical threats to its |
Physical threat to its Facility excluding weather or natural disaster
related threats, which has the potential to degrade the normal operation of the Facility. OR Suspicious device or activity at its Facility. |
|
|
Physical threats to its BES control center |
Physical threat to its BES control center, excluding weather or
natural disaster related threats, which has the potential to degrade the normal operation of the control center. OR Suspicious device or activity at its BES control center. |
|
|
Public appeal for load reduction resulting from a BES Emergency |
Public appeal for load reduction to maintain continuity of the BES. |
|
|
System-wide voltage reduction resulting from a BES Emergency |
TOP |
System-wide voltage reduction of 3% or more. |
|
Firm load shedding resulting from a BES Emergency |
Firm load shedding ≥ 100 MW (manual or automatic). |
|
Event Type |
Entity with Reporting Responsibility |
Threshold for Reporting |
|
TOP |
A voltage deviation of =/> 10% of nominal voltage sustained for ≥ 15 continuous minutes. |
|
|
Uncontrolled loss of firm load resulting from a BES Emergency |
Uncontrolled loss of firm load for ≥ 15 minutes from a single incident: ≥ 300 MW for entities with previous year’s peak
demand ≥ 3,000 MW
OR
≥ 200 MW for all other entities |
|
|
System separation (islanding) |
Each separation resulting in an island ≥ 100 MW |
|
|
Generation loss |
Total generation loss, within one minute, of:
≥ 2,000 MW in the Eastern, Western, or Quebec Interconnection
OR
≥ 1,400 MW in the ERCOT Interconnection
Generation loss will be used to report Forced Outages not weather patterns or fuel supply unavailability for dispersed power producing resources. |
|
Event Type |
Entity with Reporting Responsibility |
Threshold for Reporting |
|
Complete loss of off-site power to a nuclear generating plant (grid supply) |
TO, TOP |
Complete loss of off-site power (LOOP) affecting a nuclear generating station per the Nuclear Plant Interface Requirements |
|
Transmission loss |
TOP |
Unexpected loss within its area, contrary to design, of three or
more BES Facilities caused by a common disturbance (excluding successful automatic reclosing). |
|
Unplanned evacuation of its BES control center |
Unplanned evacuation from its BES control center facility for 30
continuous minutes or more. |
|
|
Complete loss of Interpersonal Communication and Alternative Interpersonal Communication capability at its staffed BES control center |
Complete loss of Interpersonal Communication and Alternative Interpersonal Communication capability affecting its staffed BES control center for 30 continuous minutes or more. | |
|
Complete loss of monitoring or control capability at its staffed BES control center |
Complete loss of monitoring or control capability at its staffed
BES control center for 30 continuous minutes or more. |
EOP-004 – Attachment 2: Event Reporting Form
