IRO-014-1: Procedures, Processes, or Plans to Support Coordination Between Reliability Coordinators
Purpose
To ensure that each Reliability Coordinator’s operations are coordinated such that they will not have an Adverse Reliability Impact on other Reliability Coordinator Areas and to preserve the reliability benefits of interconnected operations.
Applicability
Reliability Coordinator
Effective Date
November 1, 2006
Requirements
R1. The Reliability Coordinator shall have Operating Procedures, Processes, or Plans in place for activities that require notification, exchange of information or coordination of actions with one or more other Reliability Coordinators to support Interconnection reliability. These Operating Procedures, Processes, or Plans shall address Scenarios that affect other Reliability Coordinator Areas as well as those developed in coordination with other Reliability Coordinators.
R1.1. These Operating Procedures, Processes, or Plans shall collectively address, as a minimum, the following:
R1.1.1. Communications and notifications, including the conditions 1 under which one Reliability Coordinator notifies other Reliability Coordinators; the process to follow in making those notifications; and the data and information to be exchanged with other Reliability Coordinators.
R1.1.2. Energy and capacity shortages.
R1.1.3. Planned or unplanned outage information.
R1.1.4. Voltage control, including the coordination of reactive resources for voltage control.
R1.1.5. Coordination of information exchange to support reliability assessments.
R1.1.6. Authority to act to prevent and mitigate instances of causing Adverse Reliability Impacts to other Reliability Coordinator Areas.
R2. Each Reliability Coordinator’s Operating Procedure, Process, or Plan that requires one or more other Reliability Coordinators to take action (e.g., make notifications, exchange information, or coordinate actions) shall be:
R2.1. Agreed to by all the Reliability Coordinatorsrequired to take the indicated action(s).
R2.2. Distributed to all Reliability Coordinators that are required to take the indicated action(s).
R3. A Reliability Coordinator’s Operating Procedures,Processes, or Plans developed to support a Reliability Coordinator-to-Reliability Coordinator Operating Procedure, Process, or Plan shall include:
R3.1. A reference to the associated Reliability Coordinator-to-Reliability Coordinator Operating Procedure, Process, or Plan.
R3.2. The agreed-upon actions from the associated Reliability Coordinator-to-Reliability Coordinator Operating Procedure, Process, or Plan.
R4. Each of the Operating Procedures, Processes, and Plans addressed in Reliability Standard IRO 014 Requirement 1 and Requirement 3 shall:
R4.1. Include version control number or date.
R4.2. Include a distribution list.
R4.3. Be reviewed, at least once every three years, and updated if needed.
Measures
M1. The Reliability Coordinator’s System Operators shall have available for Real-time use, the latest approved version of Operating Procedures, Processes, or Plans that require notifications, information exchange or the coordination of actions betweenReliability Coordinators.
M1.1 These Operating Procedures, Processes, or Plans shall address:
M1.1.1 Communications and notifications, including the conditions under which one Reliability Coordinator notifies other Reliability Coordinators; the process to follow in making those notifications; and the data and information to be exchanged with other Reliability Coordinators.
M1.1.2 Energy and capacity shortages.
M1.1.3 Planned or unplanned outage information.
M1.1.4 Voltage control, including the coordination of reactive resources for voltage control.
M1.1.5 Coordination of information exchange to support reliability assessments.
M1.1.6 Authority to act to prevent and mitigate instances of causing Adverse Reliability Impacts to other Reliability Coordinator Areas.
M2. The Reliability Coordinator shall have evidence that these Operating Procedures, Processes, or Plans were:
M2.1 Agreed to by all the Reliability Coordinators required to take the indicated action(s).
M2.2 Distributed to all Reliability Coordinators that are required to take the indicated action(s).
M3. The Reliability Coordinator’s Operating Procedures, Processes, or Plans developed (for its System Operators’ internal use) to support a Reliability Coordinator-to-Reliability Coordinator Operating Procedure, Process, or Plan received from another Reliability Coordinator shall:
M3.1 Be available to the Reliability Coordinator’s System Operators for Real-time use,
M3.2 Include a reference to the associated source document, and
M3.3 Support the agreed-upon actions from the source document.
M4. The Reliability Coordinator’s Operating Procedures, Processes, or Plans that addresses Reliability Coordinator-to-Reliability Coordinator coordination shall each include a version control number or date and a distribution list. The Reliability Coordinator shall have evidence that these Operating Procedures, Processes, or Plans were reviewed within the last three years.
- Examples of conditions when one Reliability Coordinator may need to notify another Reliability Coordinator may include (but aren’t limited to) sabotage events, Interconnection Reliability Operating Limit violations, voltage reductions, insufficient resources, arming of special protection systems, etc. ↩