SCED is not solving with a valid solution and EBPs are needed; THEN: Enter the EBP increment/decrement as needed to control frequency, Notify Resource Operator to post a message on MIS Public , Notify Transmission Operator to make Hotline call to TOs, Make the following hotline call to QSEs: Q#22 - Typical Hotline Script for Watch and Emergency Basepoints until Site Failover complete Site Failover Complete If EBPs were needed WHEN: SCED is solving with a valid solution; THEN: Remove the Emergency Base Point flag, Initiate Hotline call to cancel the Watch, Notify Resource Operator to cancel MIS posting, Notify Transmission Operator to cancel the Watch with TOs. Q#23 - Typical Hotline Script Cancel and Emergency Basepoints, Site Failover complete 2.7 Switching Control Center Procedure Purpose: To provide notice to the QSEs when ERCOT is working from the Alternate Control Center. Protocol Reference Guide Reference NERC Standard Version: 1 Revision: 5 Effective Date: May 1, 2018 Step Action Hotline Call When transferring operations from primary site to alternate site (and vice versa). Make the following hotline call to QSEs: Q#24 - Typical Hotline Script for working from Alternate site Q#25 - Typical Hotline Script for working from Primary site MIS Posting Typical MIS Posting for working from Alternate site: ERCOT is working from alternate control center. Typical MIS Posting for working from Primary site:
ERCOT is working from primary control center. Log Log all actions. 3.0 Monitor and Manage System Security 3.1 Frequency Control Operating Procedure Procedure Purpose: To control frequency within defined limits. Protocol Reference 6.5.7.6.1 6.5.7.6.2.2(7) 6.5.9.1(1)(b) Guide Reference 2.2.4 2.2.8 NERC Standard BAL-001-2 R2 IRO-001-4 R1 NUC-001-3 R4, R4.1, R4.2, R9, R9.2, R9.2.1, R9.4, R9.4.2 TOP-001-4 R2 Version: 1 Revision: 29 Effective Date: October 1, 2018 Step Action Maintain System Frequency Objective Frequency should be maintained within +/- 0.03 Hz of schedule Attempt to maintain CPS1 scores over 100 Operate within the BAAL Frequency Bias set to 759MW/0.1Hz CPS1 less than 100 IF: Performance drops below 100 for over three consecutive hours; THEN: LOG the event and the possible cause of the poor performance. BAAL Corrective action shall be taken whenever the clock-minute average ACE is outside its clock-minute average Balancing Authority ACE Limit (BAAL). This is to ensure that the Balancing Authority ACE does not remain outside the BAAL for more than 30 consecutive clock-minutes. Caution NEVER (unless directed by EMMS Production or Support Engineer): Change other tuning parameters (including QSE ramp rates, dead bands, thresholds, gains, time constraints) Base Point Deviation REVIEW REFERENCE DISPLAY:
SCED Failure NOTE When RLC sees that the SCED solution has not updated within the last 425 seconds, emergency base points (EBP) will automatically activate. Any time EBPs are activated, SCED solutions are being blocked from being communicated to MPs. The RLC Control Parameters (SCED Failure Threshold) should be set to 125 seconds. This is due to a code that adds 300 seconds to the 125 seconds from SCED Failure Threshold Parameter in the display, so total number of seconds RLC waits for SCED solution is 425 before enabling the emergency base points. During System Failures, Emergency Base Point (EBP) or instructing a QSE to go on Constant Frequency Control (CFC) Frequency within +/- 0.03 Hz of schedule – Normal with available regulation Frequency within +/- 0.05 Hz of schedule – When returning to Normal Operations with available regulation Frequency maintained within +/- 0.09 Hz of schedule – Balancing Authority ACE Limit (BAAL) NOTE If for some reason a manual EBP is required for a Resource, communicate the Resource name, MW output requested, start time and duration of the dispatch instruction to the QSE representing the Resource. 1 IF: Any module of the SCED Workflow Controller fails; THEN: Manually run the SCED process. 2 IF: SCED still fails after manually running, AND EBPs have automatically activated; THEN: Contact the Help Desk, Initiate the Watch Hotline call to QSEs, Notify Resource Operator to post a message on MIS Public, Notify Transmission Operator to make Hotline call to TOs. Q#27 - Typical Hotline Script for Watch for SCED Failure 3 EMP Applications>Generation Area Status>Related Displays>ERCOT Nodal Summary MONITOR: Regulation Service (Up/Dn) margins to ensure frequency can be adequately maintained. IF:
THEN: Send an e-mail with the details to “1 Shift Supervisors” for the Managers to handle. LOG Log all actions. Real-Time Non-Spin Shortage Non-Spin Shortage REVIEW REFERENCE DISPLAY: EMP Applications>Generation Area Status>Related Displays>Ancillary Service Monitoring Summary>Non-Spin Reserve QSE Detail Continually monitor for Non-Spin shortages: Review display for shortages between the Day-Ahead Award and Responsibility WHEN: A shortage is identified; THEN: Coordinate with the Resource Operator, this shortage may have presented itself in their checks and QSE may have already been contacted. IF: QSE has not already been contacted by Resource Operator; THEN: Notify the QSE to correct the shortage. IF: QSE does not provide appropriate justification for not satisfying their A/S obligation; THEN: Send an e-mail with the details to “1 ERCOT Shift Supervisors” for the Managers to handle. LOG Log all actions. Resources not dispatchable to SCED Not Dispatchable to SCED REVIEW REFERENCE DISPLAY: EMP Applications>Resource Limit Calculator WHEN: A QSE has telemetered more A/S on a specific Resource that is greater than their HSL; THEN: SCED will set the HDL=LDL=MW making the Resource undispatchable,
Shutdown/ Startup Shut-down: A QSE representing a Generation Resource that is not actively providing A/S (with the exception of Off-line Non-Spin) may only use a Resource Status of SHUTDOWN through telemetry that the Resource is operating in a shutdown sequence requiring manual control and is not available for Dispatch. Start-up: A QSE representing a Generation Resource that is not actively providing A/S may only use a Resource Status of STARTUP through telemetry that the Resource is operating in a start-up sequence requiring manual control and is not available for Dispatch. NOTE QSEs can manage basepoint deviations by adjusting their telemetered ramp rate. NOTE When a Resource is carrying “Off-Line” Non-spin and that Non-Spin is being recalled, the QSE would continue to show the Non-Spin responsibility on the Resource that is shutting down. Combine Generation Resources NOTE WHEN: Combine Cycle Generation Resources are changing configuration creating basepoint deviations THEN: QSEs will need to manage their telemetered HSL for proper basepoints. Telemetry Issues that could affect SCED and/or LMPs Not Dispatchable to SCED REVIEW REFERENCE DISPLAY: EMS Applications>Generation Control>Resource Calculation>RLC Unit Input Data and RLC Unit Output Data WHEN: A QSE has telemetered more A/S on a specific Resource that is greater than their HSL, OR A Resource is generating more than their telemetered HSL; THEN: SCED will set the HDL=LDL=MW making the Resource undispatchable, Request the QSE to make corrections to their telemetry (Resource status, Resource limits, A/S responsibilities, etc.) Real-Time Data Issues by the QSE
Version: 1 Revision: 5 Effective Date: December 28, 2017 Step Action Primary Control Center NOTE When a participant dials into the conference bridge before the moderator dials in, they will hear music and be placed on hold. NOTE On the first weekend of each month, between the hours of 0000 Saturday and 0500 Monday, the Satellite Phone System Conference Bridge will be tested with the TOs. As the Shift Supervisor makes the call to the individual TO, they will set a time that the ERCOT Operator will call the Satellite Phone System Conference Bridge and establish communication with the appropriate TO. NOTE Use the ERCOT Satellite Phone User Guide (See Desktop Guide Common to Multiple Desks Section 2.7) for a list of the TOs that will be contacted by the ERCOT Operator and instructions on how to place a Satellite Phone System Conference Bridge call. NOTE The numbers for the ERCOT Operator to call into the Conference Bridge are Desk specific. Select: SATELLITE directory or go to page 41 to view the programmed numbers on the Turret Phone for each Bridge: BLACKSTRT RUC – RUC Desk BLACKSTRT RRD – Reliability Risk Desk BLACKSTRT RES – Resource Desk BLACKSTRT REAL – Real-Time Desk BLACKSTRT TS#1 – Transmission Desk (Island Coordination) BLACKSTRT TS#2 – Transmission Desk 1 IF: The pre-programmed number does not function correctly, THEN: to the ERCOT Satellite Phone User Guide (See Desktop Guide Common to Multiple Desks Section 2.7.2) for the appropriate conference number and continue with this procedure. 2 When prompted: the Moderator Pass Code If necessary, allow five minutes for Participants to dial in As each Participant connects, record the following: Name of Participant Company Name Any problems identified with the connection process 3 IF: One or more of the QSEs fail to connect to the Bridge call, THEN: Investigate the cause and log the following:
Hartmann, Gaddy and Ballew Procedure writers and editors June 23, 2017 Hartmann, Gaddy and Ballew Procedure writers and editors July 24, 2017 Hartmann, Gaddy and Ballew Procedure writers and editors September 27, 2017 Hartmann, Gaddy and Ballew Procedure writers and editors October 27, 2017 Hartmann, Gaddy, Ballew and Frosch Procedure writers and editors December 22, 2017 Hartmann, Gaddy, Ballew and Frosch Procedure writers and editors February 22, 2018 Hartmann, Gaddy and Ballew Procedure writers and editors April 2, 2018 Hartmann, Gaddy, Ballew and Frosch Procedure writers and editors April 27, 2018 Hartmann, Gaddy and Ballew Procedure writers and editors August 24, 2018 Hartmann, Gaddy and Ballew Procedure writers and editors September 27, 2018 Hartmann, Gaddy and Ballew Procedure writers and editors December 21, 2018 Hartmann, Gaddy and Ballew Procedure writers and editors January 25, 2019 Manual Change History Procedure Ver/Rev Reason for Issue Effective Date All Sections 1.0 / 0 New procedures for all sections for Nodal implementation November 28, 2010 2.4 3.1 3.2 3.4 3.5 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 Updated Categories and Priorities Updated Response to High Frequency 15, 20 and 25 minutes and Response to Low Frequency step 15 Updated steps Failure Indication/Issues and QSE Capacity Issues Updated steps AGC/RLC Issues, System Wide Capacity Issue and AGC/RLC Issues Resolved Updated step 1 December 1, 2010