THEN: The E-Tag will be automatically denied. IF: You feel an E-Tag failed validation erroneously; THEN: Go to the list of approved ERCOT Registered QSE’s at the following website: Select the “List of Market Participants in ERCOT Region”, Select the DC Tie Scheduling List tab to view the ERCOT Registered QSEs. IF: The QSE name is on the list but was denied by WebTrans; THEN: Approve the E-Tag and inform the help desk and OATI help desk if needed. WebTrans Reference Display: Validation > Tag Validation Monitor 2 When a New or Updated E-Tag is received in WebTrans system: Manually validate the following: Contact Information must be the QSE information and not “ERCO” must not be listed as a PSE in Tag Information “ERCO” must not be listed as a PSE in the Physical Path Time Zone should be CS (central standard), CD (central daylight) or CP (central prevailing) during time change “Transaction type” must be “Energy or Normal” “ERCOT-E” or “ERCOT-N” must be selected for the correct POR (Point-of-Receipt) or POD (Point of Delivery) in the Physical Path or “ERCOT-N” must be selected for the correct POR (Point-of-Receipt) or POD (Point of Delivery) on the ERCO TP Row Do not same tie on the same row for the POR and POD, example: “ERCOTN to “ERCOTN” are no losses (MW) in the ERCOT Control Area. This would be either to or from SPP as shown on the “Energy and Transmission Profiles” section, loss accounting may be blank, financial or in-kind for ERCOT Tags are permitted to be submitted within the COP time (up to seven days in advance), but a separate tag for each day must be submitted and the Start Time and Stop Time MUST NOT cross the midnight hour
Curtail the E-Tag to 0 (zero). NOTE E-Tag curtailments must be in an “Approved” or “Implemented” status to be calculated into the net scheduled interchange. 3 IF: The net schedule interchange value changes intra-hour, and Requested by the SPP Operator, THEN: Checkout the net scheduled interchange value for each SPP DC Tie affected by E-Tag curtailments. WebTrans Reference Display: Realtime Summary
Check the Control Room video camera to determine the status of the PCC and personnel, Contact Security at the ACC Notify them of the situation AND Have them attempt to make contact with Security at PCC. Have them contact you with information acquired OR IF: Notified by the PCC that they are evacuating and/or transferring sites; THEN: Continue with procedure. IROL The North – Houston VSAT voltage stability limit is an IROL; the actual flow should not be allowed to exceed the limit, and MUST NOT exceed the limit for more than 30 minutes. If necessary, the System Operator has the authority to direct load shedding before this IROL has been exceeded. 3-Part When issuing an Operating Instruction, follow three-part communication: Issue the Operating Instruction Receive a correct repeat back Give an acknowledgement Systems are Functional Call in Additional Operators Activate the NXT scenario to call in additional shift personnel, which includes a Shift Supervisor. SELECT: SO Loss of Control Room at Taylor, OR; SO Loss of Control Room at Bastrop. Operator will receive an email after 10 minutes with a report of who has responded along with their estimated time of arrival. QSE Hotline Call Typical Hotline Script: “This call requires everyone to remain on the line until it is complete. [QSE] I will be asking you for the repeat back. This is ERCOT Operator [first and last name]; at [xx:xx], ERCOT is issuing an Emergency Notice due to the loss of primary control center and is transferring operations to the alternate control center. Direct all urgent phone calls thru the [Bastrop][Taylor] OPX. All ERCOT systems are functioning at this time. HRUC will be delayed until additional staffing arrives. If you represent a Nuclear Plant, please inform them that RTCA results will not be viewed in a timely manner and is expected to last for approximately 1 hour.” [Select QSE], “Please repeat this back for me.”
Hartmann, Gaddy and Ballew Procedure writers and editors August 24, 2018 Hartmann, and Ballew Procedure writers and editors September 26, 2018 Hartmann, Gaddy and Ballew Procedure writers and editors October 29, 2018 Hartmann, 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 30, 2010 3.1 3.3 3.12 3.13 3.14 3.16 3.17 4.1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 1.0 / 1 Updated step 1 Updated step 1 Updated step 1 and added Log Updated step 4 Updated step 3 Updated step 1 and added Log Updated step 3 Updated Constant Frequency, Respond to QSE’s, Stability Limits Reached and Thermal Limits Reached December 1, 2010 2.3 3.4 4.1 4.2 4.3 1.0 / 0 1.0 / 1 1.0 / 2 1.0 / 1 1.0 / 1 Added new procedure Updated step 1 Updated steps “Constant Frequency”, “QSE Hotline Call”, “TO Hotline Call”, “Respond to QSEs” “Respond to TOs”, “Stability Limits” and added “Nuclear Plants” Updated Note and “Additional Operators” Updated Hotline in “Notifications” January 31, 2011 2.3 3.1 3.2 3.3 3.7 4.1 1.0 / 1 1.0 / 2 1.0 / 1 1.0 / 2 1.0 / 1 / 2 Updated NXT Test Updated 4th Note and step 1 Updated step 2 Updated 5th note, step 1, deleted step 4 and 6th Note Updated all sections Section number changed from 3.12 and updated all steps March 25, 2011
3.2 3.3 3.5 3.6 3.7 3.10 4.1 4.2 4.3 1.0 / 15 1.0 / 27 1.0 / 7 1.0 / 10 1.0 / 15 1.0 / 7 1.0 / 25 1.0 / 22 1.0 / 27 Updated for NPRR825 Updated for NPRR825 Updated for NPRR825 Updated for NPRR825 Updated for NPRR825 Updated for NPRR825 Updated for NPRR825 Updated for NPRR825 Updated for NPRR825 October 1, 2018 3.6 3.7 4.1 4.2 4.3 1.0 / 11 1.0 / 16 1.0 / 26 1.0 / 23 1.0 / 28 Added step to cancel message steps to cancel message steps to post and cancel messages Added step to cancel message Added steps to post and cancel messages November 1, 2018 All procedures in this manual have been reviewed December 28, 2018 3.3 1.0 / 28 Updated step 2 January 31, 2019