EOP-010-1 – Geomagnetic Disturbance Operations
Purpose
To mitigate the effects of geomagnetic disturbance (GMD) events by implementing Operating Plans, Processes, and Procedures.
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. Transmission Operator with a Transmission Operator Area that includes a power transformer with a high side wye-grounded winding with terminal voltage greater than 200 kV
5. Background:
Geomagnetic disturbance (GMD) events have the potential to adversely impact the reliable operation of interconnected transmission systems. During a GMD event, geomagnetically-induced currents (GIC) may cause transformer hot-spot heating or damage, loss of Reactive Power sources, increased Reactive Power demand, and Protection System Misoperation, the combination of which may result in voltage collapse and blackout.
6. Effective Date:
The first day of the first calendar quarter that is six months after the date that this standard is approved by an applicable governmental authority or as otherwise provided for in a jurisdiction where approval by an applicable governmental authority is required for a standard to go into effect. Where approval by an applicable governmental authority is not required, the standard shall become effective on the first day of the first calendar quarter that is six months after the date this standard is adopted by the NERC Board of Trustees or as otherwise provided for in that jurisdiction.
Requirements and Measures
R1. Each Reliability Coordinator shall develop, maintain, and implement a GMD Operating Plan that coordinates GMD Operating Procedures or Operating Processes within its Reliability Coordinator Area. At a minimum, the GMD Operating Plan shall include: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning, Operations Planning, Same-day Operations, Real-time Operations]
1.1 A description of activities designed to mitigate the effects of GMD events on the reliable operation of the interconnected transmission system within the Reliability Coordinator Area.
1.2 A process for the Reliability Coordinator to review the GMD Operating Procedures or Operating Processes of Transmission Operators within its Reliability Coordinator Area.
M1. Each Reliability Coordinator shall have a current GMD Operating Plan meeting all the provisions of Requirement R1; evidence such as a review or revision history to indicate that the GMD Operating Plan has been maintained; and evidence to show that the plan was implemented as called for in its GMD Operating Plan, such as dated operator logs, voice recordings, or voice transcripts.
R2. Each Reliability Coordinator shall disseminate forecasted and current space weather information to functional entities identified as recipients in the Reliability Coordinator’s GMD Operating Plan. [Violation Risk Factor: Medium] [Time Horizon: Same-day Operations, Real-time Operations]
M2. Each Reliability Coordinator shall have evidence such as dated operator logs, voice recordings, transcripts, or electronic communications to indicate that forecasted and current space weather information was disseminated as stated in its GMD Operating Plan.
R3. Each Transmission Operator shall develop, maintain, and implement a GMD Operating Procedure or Operating Process to mitigate the effects of GMD events on the reliable operation of its respective system. At a minimum, the Operating Procedure or Operating Process shall include: [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning, Operations Planning, Same-day Operations, Real-Time Operations]
3.1. Steps or tasks to receive space weather information.
3.2. System Operator actions to be initiated based on predetermined conditions.
3.3. The conditions for terminating the Operating Procedure or Operating Process.
M3. Each Transmission Operator shall have a GMD Operating Procedure or Operating Process meeting all the provisions of Requirement R3; evidence such as a review or revision history to indicate that the GMD Operating Procedure or Operating Process has been maintained; and evidence to show that the Operating Procedure or Operating Process was implemented as called for in its GMD Operating Procedure or Operating Process, such as dated operator logs, voice recordings, or voice transcripts.
Compliance
1. Compliance Monitoring Process
1.1 Compliance Enforcement Authority
As defined in the NERC Rules of Procedure, “Compliance Enforcement Authority” (CEA) means NERC or the Regional Entity in their respective roles of monitoring and enforcing compliance with the NERC Reliability Standards.
1.2 Evidence Retention
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 CEA may ask an entity to provide other evidence to show that it was compliant for the full time period since the last audit.
The Reliability Coordinator and Transmission Operator shall keep data or evidence to show compliance as identified below unless directed by its CEA to retain specific evidence for a longer period of time as part of an investigation:
The responsible entities shall retain documentation as evidence for three years.
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 time specified above, whichever is longer.
The CEA shall keep the last audit records and all requested and submitted subsequent audit records.
1.3 Compliance Monitoring and Assessment Processes
- Compliance Audit
- Self-Certification
- Spot Checking
- Compliance Investigation
- Self-Reporting
- Complaint
1.4. Additional Compliance Information
None
Guidelines and Technical Basis
During development of this standard, text boxes were embedded within the standard to explain the rationale for various parts of the standard. Upon BOT approval, the text from the rationale text boxes was moved to this section.
Rationale for R1:
An Operating Plan is implemented by carrying out its stated actions.
Coordination is intended to ensure that Operating Procedures are not in conflict with one another. An Operating Plan is maintained when it is kept relevant by taking into consideration system configuration, conditions, or operating experience, as needed to accomplish its purpose.
Elements of Requirement R1 take place in various time horizons. Development of the GMD Operating Plan occurs in the Long-Term Planning Time Horizon. Maintenance of the GMD Operating Plan occurs in the Operations Planning Time Horizon. Implementation of the GMD Operating Plan occurs in the Operations Planning, Same-Day and Real-Time Time Horizons.
Rationale for R2:
Requirement R2 replaces IRO-005-3.1a, Requirement R3. IRO-005-4 has been adopted by the NERC Board and filed with FERC, and will retire IRO-005-3.1a Requirement R3. If EOP-010-1 becomes effective prior to the retirement of IRO-005-3.1a, Requirement R2 shall become effective on the first day following retirement of IRO-005-3.1a.
Space weather forecast information can be used for situational awareness and safe posturing of the system. Current space weather information can be used for monitoring progress of a GMD event.
The Reliability Coordinator is responsible for disseminating space weather information to ensure coordination and consistent awareness in its Reliability Coordinator Area.
Rationale for R3:
In developing an Operating Procedure or Operating Process, an entity may consider entity- specific factors such as geography, geology, and system topology.
An Operating Procedure or Operating Process is maintained when it is kept relevant by taking into consideration system configuration, conditions, or operating experience, as needed to accomplish its purpose.