The telemetry, Outage Scheduler and COP have not been correctly updated by the QSE. E-mail the information to: Operations Analysis 1 ERCOT Shift Supervisors The Operations Analysis Engineer will do further analysis and potentially override the forecast the description above after checking the following: Number of turbines online Number of turbines offline Outage scheduler Telemetered wind speed (MPH) LOG Log all actions. 4.3 Operations in the Rio Grande Valley Region Procedure Purpose: To monitor AWS Truepower wind forecast in the instance of a capacity shortage potential in the Lower Rio Grande Valley (RGV). Protocol Reference Guide Reference NERC Standard Version: 1 Revision: 0 Effective Date: January 30, 2017 Step Action Load in capacity short area is high and wind is also forecasted to be above 75% of regional capacity. REVIEW IF: The AWS RGV wind forecast seems invalid, OR IRR generation is not meeting the AWS RGV wind forecast that could cause a reliability concern, THEN: Notify an Operations Analysis Engineer for adjustments, E-mail the information to: Operations Analysis 1 ERCOT Shift Supervisors
5.0 General Voltage Support 5.1 STNET Study Procedure Purpose: To review and analyze future voltage violations. Protocol Reference Reference NERC Standand IRO-001-4 R1 TOP-001-4 R2 VAR-001-5 R2 Version: 1 Revision: 3 Effective Date: August 31, 2018 Step Action Reliability Risk Desk performs Study NOTE Each hour run a STNET study for four hours out (example it is 0100, run study for 0500) to review voltage violations. Voltage Contingencies IF: Voltage contingencies exist; THEN: “Voltage Tracking Issues spreadsheet” on Sharepoint to ensure the contingency is not listed. If not listed, convey the voltage violations to the Transmission and Security Operator Create a savecase, use naming convention “SC_RRD(HE)_(DATE) Make at least one detailed log entry per shift that the studies are being executed. If any new voltage violations are identified that do not have a solution, log the information and notify the Transmission and Security Operator of the new violation(s). IF: Unsolved contingencies exists; THEN: Communicate any unsolved contingency to the Shift Engineer and Transmission Security Desk Operator for potential solutions. Some potential solutions could be transmission switching, creation of a manual constraint, bringing on an additional Resource, returning a planned outage, or development of a CMP. Violated Constraints REVIEW REFERENCE DISPLAYS: Market Operation>Reliability Unit Commitment>HRUC Displays>DSP Displays> DSP Binding Constraint Summary Market Operation>Reliability Unit Commitment>HRUC Displays>DSP Displays> DSP Constraint Summary
THEN: Call the QSE representing Resource to determine the correct resource status and have them make the necessary correction. NOTE: It is not necessary to make calls for inconsistent telemetry/COP for quick start units. LOG Log all actions. ON TEST Review the list of “Approved Unit Tests” and “New Units Currently in Commissioning Process” on the System Operations SharePoint; compare this list to the units showing a unit status of ONTEST. WHEN: A unit with a status of ONTEST without an approved unit test exists or the unit is not in the commissioning process; THEN: Notify the QSE that they do not have an approved unit test and cannot use the ONTEST status. LOG Log all actions. Monitor Resource Telemetry for Values Telemetered Status REVIEW REFERENCE DISPLAY: EMS Applications>Generation Control>Resource Limit Calculation>RLC Unit Input Data and RLC Unit Output Data and IF: Stale telemetry is identified; THEN: Call the QSE representing the Resource to determine the cause and request them to make the necessary correction. LOG Log all actions.
Manual Change History Procedure Ver/Rev Reason for Effective Date All 1.0 / 0 New procedures January 30, 2017 2.1 3.1 4.4 5.1 7.1 7.2 9.1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 Updated System Operator Responsibility and Authority Updated Up Ramp Event step 2 Updated Panhandle Region Updated Reliability Risk Desk performs STNET Study Updated title and all 1st steps Updated Implement EEA Level 3 steps Updated Title March 31, 2017 3.1 1.0 / 2 Updated Down Ramp Event step 1, 2 & 3 Updated Up Ramp Event step 1 & 2 June 1, 2017 3.1 7.2 1.0 / 3 1.0 / 2 Updated Down Ramp Event step 2 Updated 1st note, step 1 changed to EEA Level 3 June 30, 2017 7.2 1.0 / 3 Added note Implement EEA Level 2 and Level 3 July 28, 2017 7.2 1.0 / 4 Updated Implement EEA Level 3 September 29, 2017 8.1 1.0 / 1 All procedures in this manual have been reviewed Updated Primary Control Center 4th note December 28, 2017 3.3 1.0 / 1 Updated Day Ahead RRS Sufficiency Monitoring, moved Real-time RRS Sufficiency Monitoring down, added Look Ahead Critical Inertia Level Sufficiency Monitoring and Real-time Critical Inertia Level Sufficiency Monitoring February 28, 2018 9.1 1.0 / 2 Updated Note March 30, 2018 2.2 1.0 / 1 Updated procedure purpose May 1, 2018 5.1 1.0 / 2 Added Phase Angles steps May 31, 2018 5.1 1.0 / 3 Updated and named step to Voltage contingencies August 31, 2018 4.1 4.2 1.0 / 1 1.0 / 1 Updated procedure purpose, note and updated step Updated procedure purpose, added note and updated step All procedures in this manual have been reviewed December 28, 2018 4.2 1.0 / 2 Updated January 31, 2019