within the Tv. IROL’s (Part 1.2). IRO-009-2 R2. Each Reliability Coordinator shall initiate No Operating one or more Operating Processes, Processes, Procedures, Procedures, or Plans (not limited to the or Plans were initiated Operating Processes, Procedures, or Plans that were intended to developed for Requirement R1) that are prevent a predicted intended to prevent an IROL exceedance, as IROL exceedance as identified in the Reliability Coordinator’s identified in the Real-time monitoring or Real-time Reliability Assessment. Coordinator’s monitoring or Real-time Assessment. IRO-009-2 R3. Each Reliability Coordinator shall act or Actual system direct others to act so that the magnitude and conditions showed that duration of an IROL exceedance is mitigated there was an IROL within the Tv, as identified in the IROL’s exceedance in its Reliability Real-time Coordinator’s Reliability monitoring or Real-time Assessment. Coordinator Area, and that the IROL exceedance was not mitigated within the Tv. IROL’s IRO-009-2 R4. Each Reliability Coordinator shall operate to The most limiting the most limiting IROL and Tv in instances IROL or its Tv was where there is a difference in an IROL or its not operated to Tv between Reliability Coordinators that are between Reliability responsible for that Facility (or group of Coordinators that are Facilities). responsible for the Facility (or group of Facilities) associated with the IROL. R1. The Reliability Coordinator shall have a Data specification is Data specification is Data specification No data specification documented specification for data and complete with the complete with the incomplete (missing (R1) information to build and maintain models to following exception: following exception either the list of support Real-time monitoring, Operational no process for data required data (R1.1), or – Planning Analyses, and Real-time provision when Assessments of its Reliability Coordinator automated
within the IROL’s Tv. (Part 1.2). IRO-009-2 R2. Each Reliability Coordinator shall initiate one or more Operating Processes, Procedures, or Plans (not limited to the Operating Processes, Procedures, or Plans developed for Requirement R1) that are intended to prevent an IROL exceedance, as identified in the Reliability Coordinator’s Real-time monitoring or Real-time Assessment. No Operating Processes, Procedures, or Plans were initiated that were intended to prevent a predicted IROL exceedance as identified in the Reliability Coordinator’s monitoring or Real-time Assessment. IRO-009-2 R3. Each Reliability Coordinator shall act or direct others to act so that the magnitude and duration of an IROL exceedance is mitigated within the IROL’s Tv, as identified in the Reliability Coordinator’s Real-time monitoring or Real-time Assessment. Actual system conditions showed that there was an IROL exceedance in its Reliability Coordinator Area, and that the IROL exceedance was not mitigated within the IROL’s Tv. IRO-009-2 R4. Each Reliability Coordinator shall operate to the most limiting IROL and Tv in instances where there is a difference in an IROL or its Tv between Reliability Coordinators that are responsible for that Facility (or group of Facilities). The most limiting IROL or its Tv was not operated to between Reliability Coordinators that are responsible for the Facility (or group of Facilities) associated with the IROL. R1. The Reliability Coordinator shall have a documented specification for data and information to build and maintain models to support Real-time monitoring, Operational Planning Analyses, and Real-time Assessments of its Reliability Coordinator Data specification is complete with the following exception: Data specification is complete with the following exception – no process for data provision when automated Data specification incomplete (missing either the list of required data (R1.1), or No data specification (R1)
VSL_Matrix_Complete_2016_01_27.docx