IRO-002-2: Reliability Coordination — Facilities
Purpose
Reliability Coordinators need information, tools and other capabilities to perform their responsibilities.
Applicability
Reliability Coordinators
Proposed Effective Date
In those jurisdictions where no regulatory approval is required, the standard shall become effective on the latter of either April 1, 2009 or the first day of the first calendar quarter, three months after Board of Trustee adoption.
In those jurisdictions where regulatory approval is required, the standard shall become effective on the latter of either April 1, 2009 or the first day of the first calendar quarter, three months after applicable regulatory approval.
Requirements
R1. Each Reliability Coordinator shall have adequate communications facilities (voice and data links) to appropriate entities within its Reliability Coordinator Area. These communications facilities shall be staffed and available to act in addressing a real-time emergency condition.
R2. Each Reliability Coordinator — or its Transmission Operators and Balancing Authorities — shall provide, or arrange provisions for, data exchange to other Reliability Coordinators or Transmission Operators and Balancing Authorities via a secure network.
R3. Each Reliability Coordinator shall have multi-directional communications capabilities with its Transmission Operators and Balancing Authorities, and with neighboring Reliability Coordinators, for both voice and data exchange as required to meet reliability needs of the Interconnection.
R4. Each Reliability Coordinator shall have detailed real-time monitoring capability of its Reliability Coordinator Area and sufficient monitoring capability of its surrounding Reliability Coordinator Areas to ensure that potential or actual System Operating Limit or Interconnection Reliability Operating Limit violations are identified. Each Reliability Coordinator shall have monitoring systems that provide information that can be easily understood and interpreted by the Reliability Coordinator’s operating personnel, giving particular emphasis to alarm management and awareness systems, automated data transfers, and synchronized information systems, over a redundant and highly reliable infrastructure.
R5. Each Reliability Coordinator shall monitor Bulk Electric System elements (generators, transmission lines, buses, transformers, breakers, etc.) that could result in SOL or IROL violations within its Reliability Coordinator Area. Each Reliability Coordinator shall monitor both real and reactive power system flows, and operating reserves, and the status of Bulk Electric System elements that are or could be critical to SOLs and IROLs and system restoration requirements within its Reliability Coordinator Area.
R6. Each Reliability Coordinator shall have adequate analysis tools such as state estimation, pre and post-contingency analysis capabilities (thermal, stability, and voltage), and wide-area overview displays.
R7. Each Reliability Coordinator shall continuously monitor its Reliability Coordinator Area. Each Reliability Coordinator shall have provisions for backup facilities that shall be exercised if the main monitoring system is unavailable. Each Reliability Coordinator shall ensure SOL and IROL monitoring and derivations continue if the main monitoring system is unavailable.
R8. Each Reliability Coordinator shall control its Reliability Coordinator analysis tools, including approvals for planned maintenance. Each Reliability Coordinator shall have procedures in place to mitigate the effects of analysis tool outages.
Measures
M1. Each Reliability Coordinator shall have and provide upon request evidence that could include, but is not limited to, a document that lists its voice communications facilities with Transmission Operators Balancing Authorities and Generator Operators within its Reliability Coordinator Area and with neighboring Reliability Coordinators, that will be used to confirm that it has communication facilities in accordance with Requirements 1 and 3.
M2. Each Reliability Coordinator shall have and provide upon request evidence that could include, but is not limited to, a data-link facility description document, computer print-out, trainingdocument, or other equivalent evidence that will be used to confirm that it has data links with entities within its Reliability Coordinator Area and with neighboring Reliability Coordinators, as specified in Requirements 1 and 3.
M3. Each Reliability Coordinator shall have and provide upon request evidence that could include, but is not limited to, Energy Management System description documents, computer printouts, SCADA data collection system communications performance or equivalent evidence to demonstrate that it has real-time monitoring capability of its Reliability Coordinator Area and monitoring capability of its surrounding Reliability Coordinator Areas to identify potential or actual System Operating Limit or Interconnection Reliability Operating Limit violations.
M4. Each Reliability Coordinator shall have and provide upon request evidence that could include, but is not limited to, documentation from suppliers, operating and planning staff training documents, examples of studies, or other equivalent evidence to show that it has analysis tools in accordance with Requirement 6.
M5. Each Reliability Coordinator shall provide evidence such as equipment specifications, operating procedures, staff records of their involvement in training, or other equivalent evidence to show that it has a backup monitoring facility that can be used to identify and monitor SOLs and IROLs. (Requirement 7)
M6. Each Reliability Coordinator shall have and provide upon request evidence that could include, but is not limited to, a documented procedure or equivalent evidence that will be used to confirm that the Reliability Coordinator has the authority to veto planned outages to analysis tools, including final approvals for planned maintenance as specified in Requirement 8 Part 1.
M7. Each Reliability Coordinator shall have and provide upon request its current procedures used to mitigate the effects of analysis tool outages as specified in Requirement 8 Part 2