Operating Procedure Manual Frequency Control Desk

Document Sample
Operating Procedure Manual Frequency Control Desk Powered By Docstoc
					OPERATING PROCEDURE
      MANUAL


 Frequency Control Desk
ERCOT Operating Procedure Manual
Frequency Control Desk

Document Control
 PREPARATION
Prepared by         Role                        Date Completed
Stone               Preparer                    April 8, 2009
Frosch, Hartmann    Procedure Writers/Editors   April 9, 2009
Frosch, Hartmann    Procedure Writers/Editors   May 15, 2009
Frosch, Hartmann    Procedure Writers/Editors   June 15, 2009
Frosch, Hartmann    Procedure Writers/Editors   July 10, 2009
Frosch, Hartmann    Procedure Writers/Editors   July 29, 2009
Frosch, Hartmann    Procedure Writers/Editors   August 27, 2009
Frosch, Hartmann    Procedure Writers/Editors   September 21, 2009
Frosch, Hartmann    Procedure Writers/Editors   October 30, 2009
Frosch, Hartmann    Procedure Writers/Editors   November 25, 2009
Frosch, Hartmann    Procedure Writers/Editors   December 30, 2009
Frosch, Hartmann    Procedure Writers/Editors   January 29, 2010
Frosch, Hartmann,   Procedure Writers/Editors   March 1, 2010
Stone
Frosch, Hartmann    Procedure Writers/Editors   March 29, 2010
Frosch, Hartmann    Procedure Writers/Editors   May 10, 2010
ERCOT Operating Procedure Manual
Frequency Control Desk


MANUAL CHANGE HISTORY
 Procedure   Ver/Rev               Reason for Issue                  Effective Date
Introduction  4.0 / 0    Revised Section 1.4 “General Duties”       May 1, 2009
                        New Format, editorial change to the
2.1.1      4.0 / 0      reference displays in Steps 1, 2, 2a, and   May 1, 2009
                        2b.
                        New format, Revised 1st NOTE to
2.1.2      4.0 / 0                                                  May 1, 2009
                        NERC and made editorial change
2.1.3      4.0 / 0      New format, Revised Step 1                  May 1, 2009
2.1.4      4.0 / 0      New format                                  May 1, 2009
2.1.5      4.0 / 0      New format                                  May 1, 2009
2.1.6      4.0 / 0      New format                                  May 1, 2009
2.1.7      4.0 / 0      New format, Editorial change to Step 4      May 1, 2009
2.2.1      4.0 / 0      New format                                  May 1, 2009
2.2.2      4.0 / 0      New format                                  May 1, 2009
2.2.3      4.0 / 0      New format, Revised 3rd NOTE                May 1, 2009
2.3.1      4.0 / 0      New format                                  May 1, 2009
2.4.1      4.0 / 0      New format, Revised Steps 3 and 4           May 1, 2009
2.4.2      4.0 / 0      New format                                  May 1, 2009
2.4.3      4.0 / 0      New format                                  May 1, 2009
2.4.4      4.0 / 0      New format                                  May 1, 2009
2.5.1      4.0 / 0      New format, Revised Step 1                  May 1, 2009
2.5.2      4.0 / 0      New format                                  May 1, 2009
2.5.3      4.0 / 0      New format                                  May 1, 2009
2.5.4      4.0 / 0      New format                                  May 1, 2009
2.5.5      4.0 / 0      New format                                  May 1 ,2009
2.5.6      4.0 / 0      New format                                  May 1, 2009
2.6.1      4.0 / 0      New format                                  May 1, 2009
2.6.2      4.0 / 0      New format                                  May 1, 2009
                        New format, changed procedure title
2.6.3      4.0 / 0      and references from “Alert” to              May 1, 2009
                        “Watch”.
ERCOT Operating Procedure Manual
Frequency Control Desk


2.6.4      4.0 / 0     New format                                  May 1, 2009
2.6.5      4.0 / 0     New format, Revised NOTE                    May 1, 2009
                       New format, revised 1st and 2nd
2.6.6      4.0 / 0     NOTES, revised Steps 1b, 1d, 1e, 2e,        May 1, 2009
                       2f, 3a, 3c, 3d, 3e, 4d, and 4e.
                       New format, revised 2nd NOTE,
2.6.7      4.0 / 0     revised Steps 4a, 4b, 4c, 4d, 4e, 4f, 4g,   May 1, 2009
                       3e, 3f, 2d, 2e, 1a, and 1e.
                       New format, revised Steps 3, 4. 5, 6, 7,
2.6.8      4.0 / 0                                                 May 1, 2009
                       8, and 9.
                       New format, revised Steps 1, 2, 3, 4, 5,
2.6.9      4.0 / 0                                                 May 1, 2009
                       and 6.
                       New format , Editorial changes to 2nd
2.6.10     4.0 / 0                                                 May 1, 2009
                       NOTE, and Step 5
                       New format, editorial change to 2nd
2.6.11     4.0 / 0                                                 May 1, 2009
                       NOTE, revised 2nd and 3rd NOTEs
                       New format, Revised „Monitor Critical
2.6.12     4.0 / 0                                                 May 1, 2009
                       Facilities‟
2.6.13     4.0 / 0     New format                                  May 1, 2009
                       New format, revised all references to
2.7.1      4.0 / 0                                                 May 1, 2009
                       NERC E-Tags and tags to be “E-Tags”
2.7.2      4.0 / 0     New format, revised Steps 1 and 2           May 1, 2009
                       New format, revised Steps 2, and 3,
2.7.3      4.0 / 0     revised all references to NERC E-Tags       May 1, 2009
                       and tags to be “E-Tags”
                       New format, revised procedure title,
2.7.4      4.0 / 0     revised all references to NERC E-Tags       May 1, 2009
                       and tags to be “E-Tags”
                       New format, revised all references to
2.7.5      4.0 / 0                                                 May 1, 2009
                       NERC E-Tags and tags to be “E-Tags”
                       New format, revised title, added 3rd
2.7.6      4.0 / 0     NOTE, revised 2nd NOTE, revised             May 1, 2009
                       Steps 1, 2, 3, 4, 5, 6, 7, 8, and 9
                       New format, revised all references to
2.7.7      4.0 / 0                                                 May 1, 2009
                       NERC E-Tags and tags to be “E-Tags”
                       New format, revised Step 2, revised all
2.7.8      4.0 / 0     references to NERC E-Tags and tags to       May 1, 2009
                       be “E-Tags”
2.7.9      4.0 / 0     New format, Revised 2nd NOTE                May 1, 2009
                                              st
                       New format, revised 1 NOTE, added
2.7.10     4.0 / 0                                                 May 1, 2009
                       2nd NOTE, revised Steps 1 and 2
ERCOT Operating Procedure Manual
Frequency Control Desk

                       New format, added 1st and 2nd NOTEs,
2.7.11       4.0 / 0   revised Step 2, revised all references to   May 1, 2009
                       NERC E-Tags and tags to be “E-Tags”
                       New format, revised 2nd and 3rd
                       NOTEs, revised Step 1, revised all
2.7.12       4.0 / 0                                               May 1, 2009
                       references to NERC E-Tags and tags to
                       be “E-Tags”
2.7.13       4.0 / 0   New format                                  May 1, 2009
                                              nd
                       New format, Revised 2 NOTE revised
2.7.14       4.0 / 0   all references to NERC E-Tags and tags May 1, 2009
                       to be “E-Tags”,
2.8.1        4.0 / 0   New format, Revised Step 1                  May 1, 2009
                       All procedures that contained to
                       Emergency Electric Curtailment Plan
Multiple     4.0 / 0                                               May 1, 2009
                       (EECP) have been changed to Energy
                       Emergency Alert (EEA).
                       All procedures that contained
Multiple     4.0 / 0   references to “ALERT” have been             May 1, 2009
                       changed to “WATCH”.
                       All procedures that contained
                       references to Appendix or Appendices
Multiple     4.0 / 0   have been changed to refer to the           May 1, 2009
                       appropriate section(s) of the Desktop
                       Reference Guide
Appendix/              Removed from Procedure Manual and
             N/A                                                   May 1, 2009
Appendices             placed in Desktop Reference Guide
2.1.1                  Updated title, updated step 2b & 3
2.1.4                  Updated script in step 1 & 2
2.2.2                  Updated step 1
2.5.1                  Updated script in step 2 & 6
2.5.3                  Updated note and added steps 4 & 5
2.5.4                  Updated steps 6 & 10
2.6.1                  Deleted notes, updated step 1 & 2
2.6.2                  Deleted notes, updated step 1, 2, & 3
2.6.3                  Deleted notes, updated step 1, 2, & 3
             4.0 / 1                                               May 20, 2009
2.6.4                  Deleted notes, updated step 1, 2, & 3
2.6.5                  Updated script in step 2
2.6.6                  Added 5th note, updated scripts
2.6.7                  Updated scripts
2.6.8                  Updated scripts and updated scripts
2.6.10                 Updated step 2
2.6.11                 Updated 1st and 4th notes, deleted steps
                       6&7
2.6.12                 Updated 2nd step
ERCOT Operating Procedure Manual
Frequency Control Desk

2.6.13                 Updated 2nd step
2.7.12                 Updated title
2.7.14                 Updated title

2.2.3      4.0 / 1     Updated step 1 & 3, added step 6 and
                       changed 3rd note to step 7
2.4.1      4.0 / 1     Updated step 3
2.5.5      4.0 / 1     Changed title
2.5.6      4.0 / 2     Updated section number
2.5.7      4.0 / 2     Updated section number and 2nd Step
2.5.8      4.0 / 1     Updated section number
2.6.6      4.0 / 2     Updated section number                  June 18, 2009
2.6.7      4.0 / 1     Updated section number
2.6.8      4.0 / 2     Updated section number
2.6.9      4.0 / 2     Updated section number
2.6.10     4.0 / 2     Updated section number and 1st note
2.6.11     4.0 / 2     Updated section number
2.7.3      4.0 / 1     Updated 3rd note
2.7.10     4.0 / 1     Updated 1 note, step 1 & 2
2.5.4      4.0 / 2     Updated title
2.6.3      4.0 / 2     Updated step 1
2.6.4      4.0 / 2     Updated step 1
2.6.6      4.0 / 3     Updated step 6 & 7
2.6.10     4.0 / 3     Updated step 2 & 5
2.7.10     4.0 / 0     New procedure                           July 15, 2009
2.7.11     4.0 / 2     Updated section number
2.7.12     4.0 / 1     Updated section number
2.7.13     4.0 / 2     Updated section number
2.7.14     4.0 / 1     Updated section number
2.7.15     4.0 / 2     Updated section number
2.1.3      4.0 / 1     Updated 2nd note
2.4.1      4.0 / 2     Updated steps 2 & 4
2.4.2      4.0 / 1     Updated step 1
2.5.3      4.0 / 2     Updated step 1
2.5.6      4.0 / 3     Updated step 1
2.6.6      4.0 / 4     Updated step 7
2.6.8      4.0 / 3     Updated step 1b                         August 3, 2009
2.6.10     4.0 / 4     Updated step 2
2.6.11     4.0 / 3     Updated step 2
2.7.6      4.0 / 1     Updated steps 1, 2, 3, 4, 5, 6, 7 & 9
2.7.7      4.0 / 1     Updated title name
2.7.8      4.0 / 1     Updated title name
2.7.9      4.0 / 1     Updated title name
2.1.7      4.0 / 1     Updated step 4                          September
2.3.1      4.0 / 1     Updated steps 1 & 2                     1,2009
ERCOT Operating Procedure Manual
Frequency Control Desk

2.5.1      4.0 / 2     Updated step 1
2.5.8      4.0 / 0     New procedure
2.5.9      4.0 / 2     Updated section number
2.6.7      4.0 / 2     Updated step 4
2.6.10     4.0 / 5     Updated 2rd note
2.7.1      4.0 / 1     Updated step 1
2.7.3      4.0 / 2     Updated step 1
2.7.4      4.0 / 1     Updated 1st note
2.1.4      4.0 / 2     Deleted 1st note
2.3.1      4.0 /       Updated step 2
2.7.1      4.0 / 2     Updated step 1                            October 1, 2009
2.7.3      4.0 / 3     Updated step 1
2.7.12     4.0 / 2     Updated step 2
1.3        4.0 / 1     Updated bullet points
1.4        N/A         Deleted section
2.2.3      4.0 / 2     Updated step 6
2.4.4      4.0 / 1     Updated step 1
2.5.1      4.0 / 3     Updated step 1
2.5.7      4.0 / 3     Updated title and 2nd note
2.6.2      4.0 / 2     Updated step 1                            November 2,
2.6.3      4.0 / 3     Updated step 1                            2009
2.6.8      4.0 / 4     Updated 5th note
2.6.10     4.0 / 6     Updated step Contact Security, Notify
                       Market Participant and Monitor Critical
                       Facilities
2.6.11     4.0 / 4     Updated step Market Notification
2.7.12     4.0 / 3     Updated note
2.2.1                  Updated title name and step 1
           4.0 / 1
2.2.3                  Updated title name, step 5, changed
           4.0 / 3
                       step 7 to 6, Added “Alternate Control
                                                                 December 1,
                       Center”, and added step 1 & 2
           4.0 / 7                                               2009
2.6.10                 Updated step Additional Notifications
           4.0 / 5
2.6.11                 Updated step Notification of Additional
                       and step Contact Security
2.1.7      4.0 / 2     Updated 1st Note
2.7.1      4.0 / 3     Added 2nd Note and updated 3rd Note
                                                                 January 6, 2010
2.7.3      4.0 / 4     Added 2nd Note, updated 3rd Note and
                       added 4th Note
ERCOT Operating Procedure Manual
Frequency Control Desk


                              Added Note
             4.0 / 2
                              Updated step 1, 2 & 6
2.1.1        4.0 / 3
                              Updated 1st & 2nd Note, step 3 & 5
2.1.4        4.0 / 2
                              Updated step 1 & 2
2.2.1        4.0 / 2
                              Updated Objective, step 1, , 4, 6 & 8
2.2.2        4.0 / 4
                              Updated Note
2.5.1        4.0 / 34.0 / 3
                              Updated step 6 & 10
2.5.32.5.4   4.0 / 4
                              Updated 4th Note
2.5.6        4.0 / 4
                              Updated 1st Note & step 5
2.5.7        4.0 / 1
                              Updated step 2
2.5.8        4.0 / 2
                              Updated step 3 & 4
2.6.1        4.0 / 3
                              Updated step 3 & 4
2.6.2        4.0 / 4
                              Updated step 3 & 4
2.6.3        4.0 / 3
                              Updated step 1, 3 & 4
2.6.4        4.0 / 2                                                     February 2, 2010
                              Updated step 2 & 3
2.6.5        4.0 / 5
                              Updated step 1, 2 & 5
2.6.6        4.0 / 3
                              Updated step 5
2.6.7        4.0 / 5
                              Updated step 1b, 1c, 2b, 2d, 3b, 3d, 4b
2.6.8
                              & 4c
             4.0 / 3
                              Updated step 4b, 4d, 4e, 3b, 3c, 2b, 2c,
2.6.9
                              1b & 1c
             4.0 / 8
                              Added step Constant Frequency and
2.6.10
                              updated step Notify Market
                              Participants, step Stability Limits
                              Reached 90% and step Respond to
                              TSP‟s
2.6.11       4.0 / 6
                              Updated procedure purpose and
                              Restoring Constant Frequency
1.3          4.0 / 2          Changed IA to IC
2.1.1        4.0 / 3          Added step 2b, changed step 2b to 2c
2.1.5        4.0 / 1          Updated step 1
2.4.1        4.0 / 3          Updated step 1, 3, 4, deleted step 5 &6
2.4.4        4.0 / 2          Updated Goal
2.5.1        4.0 / 5          Incorporated sections 2.52, 2.5.5, 2.5.6
                              & CN#630
2.5.2                         Deleted section
                                                                         March 9, 2010
2.5.3        4.0 / 4          Section # changed to 2.5.2, added step
                              3, deleted Note & step 4
2.5.4                         Deleted section
2.5.5                         Deleted section
2.5.6        4.0 / 5          Section # changed to 2.5.3
2.5.7        4.0 / 2          Section # changed to 2.5.4, updated
                              step 2
2.5.8        4.0 / 3          Section # changed to 2.5.5
ERCOT Operating Procedure Manual
Frequency Control Desk

2.5.9      4.0 / 3     Section # changed to 2.5.6
2.6.10     4.0 / 9     Updated Notify Market, Respond to
                       TSP‟s, Thermal Limits
2.7.1      4.0 / 4     Updated 3rd Note & step 1
2.7.3      4.0 / 5     Updated 5th Note & step 1
2.7.5      4.0 / 1     Updated step 1
2.7.7      4.0 / 2     Updated 1st Note, Caution & step 3
2.7.8      4.0 / 2     Updated 1st Note, Caution & step 3
2.1.1      4.0 / 4     Updated step 2b
                       Added 1st note, updated step 3 & 4,
                                                             March 31, 2010
2.2.3      4.0 / 4     deleted step 5 & 6 for PCC, updated
                       step 1 & 2 and added step 3 for ACC
2.2.2      4.0 / 3     Updated step 1                        May 12, 2010
     ERCOT Operating Procedure Manual
     Frequency Control Desk



     Contents

1.   Introduction

     1.1   Purpose

     1.2   Scope

     1.3   Roles/responsibilities

2.   Procedures

     2.1 Monitor Generation

           2.1.1    Capacity and Reserve Monitoring
           2.1.2    Three Part Communication
           2.1.3    Verbal Dispatch Instructions (VDI)
           2.1.4    VDI for Hold Last Interval
           2.1.5    VDI Guidelines to Relieve QSEs from Ancillary Service Obligations
           2.1.6    QSEs changing zones for NSRS schedules during the adjustment period
           2.1.7    Replacing Responsive Reserve through a Bilateral Trade

     2.2 Hotline, Satellite Phone and NXT Communicator Testing Procedure

           2.2.1    QSE Hotline Test
           2.2.2    Site Failover Hotline Message
           2.2.3    Testing of Satellite Phone and NXT Communicator

     2.3 Weather & Load Forecasts

           2.3.1    Monitor Weather and Load Forecasts

     2.4 Monitor SCE

           2.4.1    Monitor SCE for each QSE
           2.4.2    Loss of Unit/Resource Plan Update
           2.4.3    Regulation Participation Factors Monitor and Override
           2.4.4    Review AGC Performance



     2.5 Frequency Control

           2.5.1    Frequency Control Operating Procedure
ERCOT Operating Procedure Manual
Frequency Control Desk

      2.5.2    Actions When Frequency Telemetry is Incorrect
      2.5.3    Monitor and Control Time Error Correction
      2.5.4    Potential DCS Event
      2.5.5    LaaR Deployment for North-Houston Voltage Stability Limit
      2.5.6    Alarm Processing and Acknowledgement

2.6 Emergency and Short Supply Operations

      2.6.1    Issue an Operating Condition Notice (OCN)
      2.6.2    Issue an Advisory
      2.6.3    Issue a Watch
      2.6.4    Issue an Emergency Notice
      2.6.5    Termination of Notification
      2.6.6    Provide Advance Notice of Diminishing Responsive Reserve
      2.6.7    Diminishing Reserve Notice Cancellation Guidelines
      2.6.8    Implement EEA
      2.6.9    Restore EEA
      2.6.10   Loss of Primary Control Center Functionality
      2.6.11   Restoration of Primary Control Center Functionality

2.7 DC Ties

      2.7.1    Approve E-Tags for SPP DC Ties
      2.7.2    Import and Export Limits for the CFE DC Ties
      2.7.3    Approve E-Tags for the CFE DC Ties
      2.7.4    Adjustment of SPP DC Ties
      2.7.5    Curtailment of SPP DC Ties
      2.7.6    Adjustments/Curtailment for the CFE DC Ties
      2.7.7    Managing Daily Inadvertent Energy for the SPP DC Ties
      2.7.8    Managing Daily Inadvertent Energy for the CFE DC Ties
      2.7.9    Managing Inadvertent Energy Payback
      2.7.10   Loss of E-Tagging
      2.7.11   Emergency Energy across the CFE DC Ties
      2.7.12   EEA 1 Schedule across the SPP DC Ties
      2.7.13   Emergency Energy across the SPP DC Ties for EEA 2 or 3
      2.7.14   Backing out of EEAs and Termination
      2.7.15   Fast Start Emergency Energy to SPP

2.8 Outages

      2.8.1    Maintenance Level 2 & 3 Outages
ERCOT Operating Procedure Manual
Frequency Control Desk


1.    Introduction


1.1   Purpose

      This Procedure provides the System Operator assigned to the Frequency Control
      Desk with detailed procedures required for performing duties assigned to that
      position. The ERCOT Frequency Control Desk is responsible for ensuring that
      sufficient generation is available and on-line to cover load and meet reserve
      requirements, such that the frequency within the ERCOT System remains within
      the tolerances specified by the Protocols and NERC, for the current Operating
      Day.

      The ERCOT Frequency Control Desk monitors load and generation for the
      current operating hour.

1.2   Scope

      The instructions contained in this procedure are limited to those required for the
      ERCOT Frequency Control Desk. Instructions for other ERCOT control room
      positions are contained in separate procedures, one for each position. This
      procedure does not imply that the duties contained herein are the only duties to be
      performed by this position. The individual assigned to this position will be
      required to follow any other instructions and to perform any other duties as
      required or requested by appropriate ERCOT supervision.

1.3   Roles/Responsibilities

      ERCOT Shift Supervisor
      The ERCOT Shift Supervisor is responsible for supervision of the ERCOT
      Frequency Control Desk position and may at times be responsible for performing
      the procedures contained in this manual.

      ERCOT System Operator, Frequency Control Desk
      The ERCOT System Operator – Frequency Control Desk position represents the
      following NERC functional entities collectively for the ERCOT ISO at any time:

                 Reliability Coordinator.
                 Balancing Authority
                 Transmission Operator
                 Interchange Coordinator

      This representation includes the responsibility and clear decision making
      authority during normal and emergency conditions to direct and implement real-
      time actions to ensure the stable and reliable operation of the ERCOT electric
ERCOT Operating Procedure Manual
Frequency Control Desk

     system. These actions shall include shedding of firm load without obtaining
     approval from higher-level personnel.
         2.      Procedures
         2.1     Monitor Generation

         2.1.1   Capacity and Reserve Monitoring

         Procedure Purpose: To ensure the required amount of operating reserves are
         available to meet the load forecast.

Protocol Ref.

Guide Ref.
                             BAL-002-0       IRO-005-2
                             R2.4            R1.4, R1.5,
NERC Std.
                                             R4


Approved by:                                 Effective Date: March 31, 2010
Version: 4                          Revision 4


   Step          Action
                 Monitor the current ERCOT System Load and Short Term Load Forecast.

                 Reference Displays:
    1
                        Generation Area Status
                        Short-Term Load Forecast
                        Excel MAI (Market Analysis Interface)
                 Determine that the current ERCOT System generation capacity is sufficient
                 to meet the Short-Term Load Forecast requirements.
    2
                 Reference Displays:
                        Generation Area Status
                        Excel MAI (Market Analysis Interface)
                 Compare the current generation and load with the planned capacity values
                 from resource plan at least every other hour.

    2a           Reference Displays:
                        Generation Area Status
                        Daily Operation Plan – Resource Plan
                        Excel MAI (Market Analysis Interface)
                 When QSE‟s representing WGR‟s notify ERCOT of possible icing, instruct
    2b
                 them to reflect that in their resource plans.
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           If real-time generation is approaching planned capacity a possible reserve
           capacity shortage is developing. Discuss situation with Operating Period
           Desk and Shift Supervisor, and increase monitoring of reserves.

   2c      Reference Displays:
                   Generation Reserve Status – Available Details
                   Real Time Balancing Market – Balance Bid Tab
                   Real Time Balancing Market – QSE Tab
                   Excel MAI (Market Analysis Interface)
           If a projected reserve capacity shortage is developing in the next hour,
    3      consider OOMC or deploying of Non-Spinning Reserve Service. Consult
           with the Operating Period Desk regarding hour-ahead study results.
           If OOMC is decided upon, request the Transmission & Security Desk
           perform the actual instruction.
    4
           If NSRS is decided upon, request the Operating Period Desk perform the
           actual instruction.
           MONITOR additional available generation capacity and available DC tie
           capacity. Evaluate amount of additional capacity available in a short time
           frame using telephone communications to QSEs as appropriate.
    5
           Reference Displays:
               Generation Area Status
               Generation Reserve Status
               Generation Tie-Line Status
           Monitor Responsive Reserves on the QSE Reserve Status Display.

           If Adjusted Responsive Reserve plus LaaRs is correctly calculated, and is
    6      below 2300 MW,
                notify the Shift Supervisor
                implement EEA
                log in the Operator‟s Log any decision to declare an EEA
           Monitor Ancillary Service Obligations.

           If a QSE is not meeting its Ancillary Services obligations as shown on the
    7      QSE Reserve Status Display,
                contact the QSE to correct the deficiency
                notify the Shift Supervisor of the QSE‟s response
                log the activities performed in connection with this step
           Due to generation minimum down time, if NSRS is deployed and has
 NOTE:     ended, it would be acceptable for a QSE to keep their unit(s) providing
           non-spin on-line at its LSL. If NSRS is deployed again, it would need to
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           move to its HSL.
ERCOT Operating Procedure Manual
Frequency Control Desk



        2.1.2   Three Part Communication

        Procedure Purpose: To ensure that three part communication is used for all
        directives.

Protocol Ref.

Guide Ref.
                              COM-002-2
NERC Std.                     R2


Approved by:                                   Effective Date: May 1, 2009
Version: 4                           Revision: 0


   Step         Action
                Each Reliability Coordinator, Transmission Operator, and Balancing
                Authority shall issue directives in a clear, concise, and definitive manner,
 NERC:          shall ensure the recipient of the directive repeats the information back
                correctly; and shall acknowledge the response as correct or repeat the
                original statement to resolve any misunderstandings.
 NOTE:          A directive is an authoritative instruction or direction; specific order.
                ERCOT ISO is the Reliability Coordinator, Transmission Operator, and
                Balancing Authority.

                When issuing a directive you shall follow the three-part communication:

    1                   Issue the directive
                        Receive a correct repeat back
                        Give an acknowledgement

                Failing to do any one of the three parts is a NERC Reliability Standard
                violation.
                Many scripts have been placed throughout the procedures as a reminder for
    2           the three-part communication. However, a script can not be provided for
                every scenario. Effective three-part communication skills are mandatory.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.1.3   Verbal Dispatch Instructions (VDI)

        Procedure Purpose: Issue A VDI to QSE(s) to give a directive.

Protocol Ref.

Guide Ref.
                             COM-002-2
NERC Std.                    R2


Approved by:                                 Effective Date: August 3, 2009
Version: 4                          Revision 1


   Step         Action

 NOTE:          VDIs should not re-iterate an instruction given via XML.
                Whenever a VDI is issued, instruct the QSE to repeat back the instructions.
                IF the QSE Hotline is used to issue a VDI, direct all hotline participants to
                remain on the line until a hotline participant of your choice correctly
 NOTE:
                repeats back to you the directive. If the repeat back is not acceptable,
                restate the instructions and direct a repeat back again. Continue until an
                acceptable repeat back is received.
                As time permits, complete the VDI form (See Desk Top Guide Section
                7.4).

                The following are required fields on all VDIs:
                    VDI #
                          o EXAMPLE: For the 4th VDI issued by the Frequency
                              Control Desk on May 01, 2009 the number would appear as
                              “F-050109-04”
                    Operating Day
    1               ERCOT System Operator
                    Receiving Entity
                    Receiving Entity‟s Operator
                    Time & Date
                    Instruction
                    Reason for Instructions
                    Intervals
                    Repeated Instruction back
                    ERCOT Operator‟s signature
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action


           Blank fields are to have N/A entered.
           LOG in the Operator‟s Log the VDI information and information relevant
    2
           to the decision for issuing the VDI.
    3      Forward the VDI form to the Shift Supervisor, as time permits.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.1.4   VDI for Hold Last Interval

        Procedure Purpose: To issue a Verbal Dispatch Instruction to hold the last good
        interval.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                 Effective Date: February 2, 2010
Version: 4                         Revision: 3


   Step         Action



                If market control mechanisms have failed, or ERCOT has issued erroneous
                instructions THEN, using the hotline, issue an instruction:
                     When QSEs have answered the Hotline, review Hotline participants
                        and log any issues. If necessary call participants individually.

                Typical 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
    1
                [first and last name]. ERCOT is issuing VDI [#]. Hold the [interval ending
                time] Balancing Energy deployments until further notice. [QSE] please
                repeat this directive back to me. That is correct, thank you.”

                All directives shall be in a clear, concise, and definitive manner.
                Ensure the recipient of the directive repeats the information back
                correctly. Acknowledge the response as correct or repeat the original
                statement to resolve any misunderstandings.
                To resume with Real-Time Balancing deployments, using the hotline, issue
                an instruction:
                     When QSEs have answered the Hotline, review Hotline participants
                        and log any issues. If necessary call participants individually.
    2
                Typical 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
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           [first and last name]. ERCOT is ending VDI [#] at [time]. Resume with the
           [interval ending time] Balancing Energy deployments. [QSE] please repeat
           this directive back to me. That is correct, thank you.”

               All directives shall be in a clear, concise, and definitive manner.
               Ensure the recipient of the directive repeats the information back
               correctly. Acknowledge the response as correct or repeat the
               original statement to resolve any misunderstandings.
           As time permits complete the VDI form (See Desk Top Guide Section 7.4),
           using these instructions:
            Issued a Verbal Dispatch Instruction to – write in “All QSEs”
            Receiving entity‟s operator – write in “All QSEs”
    3       The instruction was as follows – write in “Hold interval ending <time>,
               resume with interval <time>
            Instruction repeated back

           ALL fields are to have either pertinent data or N/A entered. Leave NO
           field(s) blank.
           A held interval message must be posted on the MIS and ENS:

    4      Typical posting:
           Real-time balancing deployments were held for IE XX:XX.

           LOG in the Operator‟s Log the VDI information and reason(s) why interval
    5
           was held.
    6      Forward VDI to the Shift Supervisor, as time permits.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.1.5   VDI Guideline to Relieve QSEs from Ancillary Service Obligations

        Procedure Purpose: To relieve a QSE of their Ancillary Service obligations
        when they receive a prior dispatch instruction.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                   Effective Date: March 9, 2010
Version: 4                           Revision: 1


   Step         Action
                When a QSE receives a dispatch instruction that will prevent them from
                meeting their Ancillary Service obligation, choose one of the following
                options:

                        Upon a QSE‟s request (coordinate with the Transmission desk),
    1                    issue a VDI to relieve the QSE from their Ancillary obligation, OR
                        Coordinate with the Transmission desk to release the QSE from the
                         dispatch instruction so they can come back into compliance.

                Note: If relieving a QSE from Non-Spin obligation, issue a VDI whether
                the service has been deployed or not.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.1.6   QSEs Changing Zones for NSRS Schedules during the Adjustment
                Period

        Procedure Purpose: Process to identify the changes that a QSE will make when
        they change their NSRS schedules during the Adjustment Period.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                   Effective Date: May 1, 2009
Version: 4                           Revision: 0


   Step         Action
                When a QSE notifies or requests changing zones on NSRS schedules
                during the adjustment period request them to follow the steps below:
    1
                        QSE will change the NSRS resource to a different zone.
                        QSE will also update the bi-lateral agreement obligation to the
                         ERCOT ISO.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.1.7   Replacing Responsive Reserve through a Bilateral Trade

        Procedure Purpose: Process to monitor a QSEs obligation to maintain their
        Responsive Reserve commitments through a bilateral trade with another QSE.

                            4.10.8
Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                   Effective Date: January 6, 2010
Version: 4                           Revision: 2


   Step         Action
                A QSE has the option to reduce their base power schedule and replace the
                difference from the balancing market. This will allow the QSE to back
                down their generation so they can provide their Ancillary Service
 NOTE:
                obligation.
                There is a two (2) hours immediately following a forced outage
                compliance grace period.
                When a resource (either LaaR or generation) that is supplying RRS
                becomes unavailable to a QSE (QSE A) and needs to be replaced through a
 NOTE:
                Bilateral Trade with another QSE (QSE B), then QSE A is expected to
                inform ERCOT.
                Obtain the following information from QSE A:
    1                Intervals affected
                     Name of QSE with whom the bilateral trade was made
                IF the resource that became unavailable was a LaaR, then ENSURE QSE B
                maintains an amount of Responsive Reserve Service equal to their own
    2
                obligations PLUS the amount of the bilateral agreement with QSE A for
                the affected intervals.
                If the QSEs response is not satisfactory, notify the Shift Supervisor so a
                determination of protocol violation can be made.
    3
                LOG in the Operator‟s Log the conversation, including the information
                provided.
    4           Email the information to: RRSList@ercot.com
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.2     Hotline, Satellite Phone and NXT Communicator Testing Procedure

        2.2.1   QSE Hotline Test

        Procedure Purpose: To test the communication systems for the QSE Hotline.

Protocol Ref.

Guide Ref.
                             COM-001-1.1
NERC Std.                    R2


Approved by:                                 Effective Date: February 2, 2010
Version: 4                         Revision: 2


   Step         Action

    1           Each Monday between 0630 and 1100 test the QSE Hotline.
                Check with the Shift Supervisor and determine the ERCOT current
    2
                threatcon level.
                In the event of a failure of the Forum Conference Client software, the most
 NOTE:          recent printout of the hotline log may be used as a checklist to perform a
                manual roll call of QSEs.
                Ensure all Invalid Hotlines “Lost Souls” are cleared prior to the hotline
 NOTE:
                call.
                Using the hotline, notify all QSEs of the purpose of the call.
                     When QSEs have answered the Hotline, print Hotline participants
                        and log any issues. If necessary call participants individually.

                Typical script:
                “This is ERCOT operator [first and last name]. ERCOT is conducting the
    3
                weekly QSE hotline test. We are currently at threatcon level [threatcon
                level]. The following notices are currently in effect:
                     List OCNs, Advisories, Watches and/or Emergency Notices in
                        effect.
                     State “None” if none in effect.
                This ends this test of the ERCOT Hotline. That is all.”
                Notify the Shift Supervisor of any QSE that did not respond to the Hotline
    4           test. The Shift Supervisor and/or Help Desk may notify the
                telecommunications department for repairs.
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action

    5      Ensure printed Hotline log is forward to Shift Supervisor, as time permits.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.2.2   Site Failover Hotline Message

        Procedure Purpose: To inform the QSEs when a planed site failover is about to
        occur.

Protocol Ref.

Guide Ref.
                             COM-001-1.1
NERC Std.                    R2


Approved by:                                  Effective Date: May 12, 2010
Version: 4                          Revision: 3


   Step         Action
                Using the hotline if available notify all QSEs before the scheduled time for
                a planned site failover (preferably five (5) to 30 minutes). The following
                message should be communicated. The variable information is in brackets.
                     When QSEs have answered the Hotline, review Hotline participants
                       and log any issues. If necessary call participants individually.

                Typical script:
    1           “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 [time], ERCOT will perform a [planned,
                unplanned, emergency] site failover of its Energy & Market Management
                Systems from [Taylor, Austin] to [Austin, Taylor]. During this time,
                market communications will be unavailable for about 15 minutes, and real-
                time communications will be unavailable for about five minutes. All
                systems should reestablish communications automatically.”
    2           As time permits, notify the Shift Supervisor of any issues during the call.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.2.3   Testing of Satellite Phone and NXT Communicator

        Procedure Purpose: To ensure ERCOT maintains communication capability via
        the Satellite Phone System and NXT Communicator.

Protocol Ref.

Guide Ref.
                             COM-001-1.1      EOP-005-1
NERC Std.                    R2               R5


Approved by:                                 Effective Date: March 31, 2010
Version: 4                         Revision: 4


   Step         Action

                Primary Control Center
                When a participant dials into the conference bridge before the moderator
 NOTE:
                dials in, they will hear music and be placed on hold.
                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 Transmission Service Providers. As the Shift Supervisor makes
 NOTE:          the calls to the individual Transmission Service Provider, they will set a
                time that the ERCOT Operator will call the Satellite Phone System
                Conference Bridge and establish communication with the appropriate
                Transmission Service Providers.
                Use the ERCOT Satellite Phone User Guide located in Section 7 of the
                Desktop Guide for a list of the Transmission Service Providers that will be
 NOTE:
                contacted by the ERCOT Operator and instructions on how to place a
                Satellite Phone System Conference Bridge Call.
                     On page 11 of the MX Turret phone select the appropriate line that
                        applies to the ERCOT Operations Desk that is making the call.
                        These numbers are located in the bottom right of the page 11
                        screen.
                        BKST Day- Day Ahead Desk
    1
                        BKST Freq.- Frequency Desk
                        BKST OPD – Operating Period Desk
                        BKST TS #1 – Transmission Desk #1
                        BKST TS#2 – Transmission Desk #2
                     If the preprogrammed number does not function correctly, refer to
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
                    Section 7 of the Desktop Guide for the appropriate conference
                    number.
                   When prompted enter the Moderator Pass Code.
                   If necessary wait on the line for approx. five minutes for the
                    Participants to dial into the Conference Bridge.
                   As each participant connects to the Conference Bridge record the
                    name of the individual from the Transmission Service Provider
                    making the call and any problems identified with the connection
                    process.

                  If one or more of the Transmission Service Providers fails to
                   connect to the Satellite Phone System Conference Bridge Call
                   investigate the cause and log the following:
    2                  o Reason for inability to connect
                       o Actions taken by ERCOT
                Establish a time for a retest of the Transmission Service Providers
                   not able to connect in the initial test.
           Inform the Shift Supervisor when test is complete indicating any issues
    3
           identified.
    4      Log the test results in the Operations Log.

           Alternate Control Center
           When working out of the alternate control center during the monthly
           scheduled dates:
               Test the Satellite phone
    1          Test NXT Communicator by activating the “Test Message
                  Monthly”. Refer to Desktop Guide 7.10 (Test early evening).

           If problems are encountered with NXT Communicator, open help ticket.
           Inform the Shift Supervisor when test is complete indicating any issues
    2
           identified.
    3      Log the test results in the Operations Log.
ERCOT Operating Procedure Manual
Frequency Control Desk



        2.3     Weather & Load Forecasts

        2.3.1   Monitor Weather and Load Forecasts

        Procedure Purpose: To monitor and update the weather and load forecasts due to
        bad or missing data.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                   Effective Date: October 1, 2009
Version: 4                           Revision: 1


   Step         Action
                Validate the weather forecast data in EMS as needed to contribute to
                reliable system performance.

                Meteorlogix support is available 24 hours a day, seven days a week at
                (952) 882-4312.

                If the operator determines the EMS weather forecast is valid, no action is
                required.
    1
                If the operator determines the EMS weather forecast is invalid:

                      Call Meteorlogix.
                      Call the Operations Planning Engineer supporting the LF
                       application for support
                     E-mail the information to OPSPlanning@ercot.com as time permits
                       .
                EVALUATE Load Forecast as needed to contribute to reliable system
                performance.

                If the operator determines the load forecast is valid, no action required.
    2
                If the operator determines an adjustment needs to be made to the load
                forecast:
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           Before modifying data in the “Override” column to replace unsatisfactory
           or missing data; notify an Operations Planning Engineer supporting the
           MTLF application to adjust the load forecast accuracy.

           E-mail the information to OPSPlanning@ercot.com as time permits

           Reference Display:
                  Load Forecast Study Results and History
           Changes entered less than 45 minutes before the beginning of the
 NOTE:
           Operating Hour might not be used by the Hour Ahead Study.
ERCOT Operating Procedure Manual
Frequency Control Desk

        2.4     Monitor SCE

        2.4.1   Monitor SCE for each QSE

        Procedure Purpose: To ensure that QSE‟s Schedule Control Error is maintained
        within acceptable limits and the telemetry is working correctly.

Protocol Ref.

Guide Ref.
                             BAL-005-0.1b      IRO-005-2
NERC Std.                    R14               R1.6


Approved by:                                  Effective Date: March 9, 2010
Version: 4                          Revision: 3


   Step         Action
                Compare QSE‟s SCE with the ERCOT calculated SCE. If these two
                values differ significantly, and the cause is not known, review SCE
                components with the QSE to determine the source of the disagreement.
    1
                Reference Displays:
                     Responsive, Regulation, and SCE – SCE Calculation
                    Responsive, Regulation, and SCE – SCE Calculation – Details
                When the source of disagreement is established, decide which end (QSE or
                ERCOT) is most likely in error. If the error is on the ERCOT end, call
                technical support if appropriate. If the error is on the QSE end, instruct
                that the QSE take corrective action and/or develop a plan to mitigate the
    2           problem.

                Reference Displays:
                    Responsive, Regulation, and SCE – SCE Calculation
                Responsive, Regulation, and SCE – SCE Calculation – Details
                Monitor QSE generation and SCE:
                 Remove a QSE‟s SCE feedback if they have a large SCE and their
                    generation is not moving in the proper direction or rate to correct their
                    SCE.
    3
                 If SCE for a QSE departs significantly from 0 for an unknown reason,
                    or if a SCE violation is causing a reliability problem, call the QSE
                    involved and determine the reason for the deviation.
                 If a wind only QSE SCE deviates significantly from 0, call the QSE
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
               and instruct them to update their resource plan and base power
               schedules. The resource plans and base power schedules should be
               updated together and stay matched. Since base power changes are not
               allowed during the operating hour the SCE cannot be corrected
               immediately.

           Reference Display
                 Responsive, Regulation, and SCE Regulation
           NEVER (unless directed by the Control Engineer or designee):
               Modify “Total (SCE-responsive) Feedback Gain” (should be altered
                 by the Control Engineer)
    4          Change other tuning parameters (including QSE ramp rates, dead
                 bands, thresholds, gains, time constants)

           Reference Displays:
                 Responsive, Regulation, and SCE – Details
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.4.2   Loss of Unit/Resource Plan Update

        Procedure Purpose: To ensure a QSE‟s Resource Plan is updated after the loss
        of a generating unit.

Protocol Ref.

Guide Ref.
                             IRO-005-2       TOP-002-2
NERC Std.                    R1.1            R3


Approved by:                                  Effective Date: August 3, 2009
Version: 4                          Revision: 1


   Step         Action
                After the loss of a resource, a QSE has the ability to update their resource
                plan. If the resource plan is updated after the Operating Period Desk
 NOTE:
                Operator has run the Hour Ahead study, real time balancing results could
                be incorrect.
                When a QSE has the loss of any resource greater than 200 MW, contact
                that QSE and request what interval ending is the first interval they were
    1           able to update their resource plan.

                (Resource Plans can be updated for interval ending, every 15 minutes)
                Supply the Operating Period Desk Operator with:
                 Name of the QSE
    2            Resource name
                 MW amount of change
                 First interval ending that was updated
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.4.3   Regulation Participation Factors Monitor and Override

        Procedure Purpose: To update a QSE‟s regulation participation factors due to a
        system failure.

Protocol Ref.

Guide Ref.
                             EOP-002-2.1     IRO-005-2
NERC Std.                    R6.1            R1.6


Approved by:                                  Effective Date: May 1, 2009
Version: 4                          Revision: 0


   Step         Action
                Regulation (up and down) participation factors are transferred from the
                Market Operations System every 15 minutes. If this transfer fails for any
 NOTE:
                reason, the regulation participation factor field on the “ERCOT
                RESPONSIVE, REGULATION AND SCE” screen will become enterable.
    1           MONITOR the regulation participation factor and regulation deployed.
                In the event of a transfer failure (fail over), the regulation participation
                factors could all default to zero, or some other unacceptable number.

                In this event, enter your best estimate of each QSE‟s participation factor
    2
                (share of regulation up/down) to allow regulation deployment to continue.

                Reference Display:
                Responsive, Regulation, and SCE – Regulation
                Forward a “print screen” copy of the NEW participation factors, with date
    3
                and time, to the Shift Supervisor.
                Using the Emergency Notification System (ENS), notify the QSEs of the
    4           failure of the regulation participation factor.
                 ENS: short version – 32 characters
                LOG in the Operator‟s Log the time of the failure, time the participation
    5           factors were changed, time the QSEs were notified, and any other relevant
                information.
ERCOT Operating Procedure Manual
Frequency Control Desk

        2.4.4   Review AGC Performance

        Procedure Purpose: To maintain NERC Control Performance Standard 1
        compliance.

Protocol Ref.

Guide Ref.
                            BAL-005-0.1b      EOP-002-      NUC-001
                            R2                2.1           R4.2
NERC Std.
                                              R6


Approved by:                                 Effective Date: March 9, 2010
Version: 4                         Revision: 2


   Step         Action
                Maintain CPS1 over 100.

                Reference Displays:
                      Generation Area Status
 GOAL:
                      Responsive, Regulation, and SCE – Regulation
                      Ancillary Service Performance Monitor – Regulation Services

                Note: Nuclear Power Plants do not run in AGC Mode.
                If performance drops below 100 for over three consecutive hours, attempt
                to identify the reason.

                Actions that may be taken are:
                 Check Regulation Service available during the time frame.
                 If Regulation Service was depleted check with Operating Period Desk
    1
                    and inquire if enough Balancing Energy had been deployed to restore
                    Regulation Service.
                 If Regulation Service was depleted check for QSEs with large SCE in
                    the direction of the depleted Regulation Service. If the cause for the
                    large SCE is unknown contact the QSE and inquire about the status of
                    their SCE.
                LOG in the Operator‟s Log the event and the probable cause of the poor
    2           performance.
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.5       Frequency Control

      2.5.1     Frequency Control Operating Procedure

      Procedure Purpose: To maintain system frequency within acceptable levels.

Protocol Ref.

Guide Ref.
                           BAL-002-0      BAL-005-0.1b BAL-007           NUC-001
NERC Std.                  R6, R7, R8     R6


Approved by:                               Effective Date: March 9, 2010
Version: 4                       Revision: 5


      Step           Action
                        Frequency should be maintained within +/- 0.03 Hz of schedule
                        Attempt to maintain CPS1 scores over 100

                     Reference Displays:
   Objective:              Generation Area Status
                           Responsive, Regulation, and SCE – Regulation
                           Responsive, Regulation, and SCE – Regulation – Details


                     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. Performance under BAAL will be captured under
                     the following:
     BAAL
                     BAALHigh – effective when Actual Frequency id greater than 60 Hz.

                     ERCOT ISO BAALHigh = 60.09 HZ = 600 MW

                     BAALLow – effective when Actual Frequency is less than 60 Hz.

                     ERCOT ISO BAALLow = 59.91 HZ = -600 MW
ERCOT Operating Procedure Manual
Frequency Control Desk


     Step       Action

Response to High Frequency
                Open realtime on „erpfileb‟/_Operations Official Spreadsheets/BAL
    BAAL
                007 ERCOT Interconnection and select Control T simultaneously to
    SHEET
                start spreadsheet.
                Frequency above 60.05 and continuing to climb or over 60.05 > five
                minutes:
                     Remove SCE feedback from QSEs with positive SCE and
  MONITOR               monitor frequency response.
                     Consult with the Transmission and Security desk to confirm
                        that no OOMs from that desk could be affecting frequency.
                     Check to ensure available Down Regulation.
                If 10 consecutive minutes of ACE above BAALHigh (60.09 Hz):
                     Monitor regulation services and ensure that deployments are
                        sent out.
                     Remove SCE feedback from QSEs with positive SCE and
                        monitor frequency response.
                     Call QSEs with positive SCE and instruct them to reduce
                        generation to return their SCE to zero as soon as possible.
                     If out of Down Regulation, issue fleet down instruction to a
                        QSE with sufficient Down Regulation (see script below).

                Issue Verbal Dispatch instructions to one or more QSE‟s (other than
                those failing to maintain 0 SCE) to reduce generation.

                Typical script:
      10        This is ERCOT operator [first and last name]. ERCOT is issuing
   MINUTES      VDI [#] to [QSE]. Reduce your fleet generation by [MW amount]
                due to high frequency. Please repeat this directive back to me. That
                is correct, thank you.”

                It is not mandatory that a VDI # is given with the directive, if
                filling out paperwork later, use script below:


                Typical script:
                This is ERCOT operator [first and last name]. Reduce your fleet
                generation by [MW amount] due to high frequency. Please repeat
                this back to me. That is correct. I will call back with a VDI #.”


                All directives shall be in a clear, concise, and definitive manner.
ERCOT Operating Procedure Manual
Frequency Control Desk


     Step       Action
                Ensure the recipient of the directive repeats the information
                back correctly. Acknowledge the response as correct or repeat
                the original statement to resolve any misunderstandings.
                If 15 consecutive minutes of ACE above BAALHigh (60.09 Hz):
                     Remove SCE feedback from QSEs with positive SCE and
                        monitor frequency response.
                     Call the QSE with the positive SCE and explain to them that
                        their dispatch is causing the high Frequency resulting
                        frequency to be higher than NERC BAALHigh trigger limit.
      15
                        Instruct the QSE with the positive SCE to bring their SCE
   MINUTES
                        back to zero within 10 minutes.
                     Issue fleet down instructions to additional QSEs with Down
                        Regulation room (see script above).
                     Log the event and notify Shift Engineer.
                     Shift Engineer will send the event notification via email to
                        BAALfieldtrials@ercot.com
                If 20 consecutive minutes of ACE above BAALHigh (60.09 Hz):
                     Remove SCE feedback from QSEs with positive SCE and
                        monitor frequency response.
                     Call the QSE with the positive SCE and explain to them that
      20                their dispatch is causing the high Frequency resulting
   MINUTES              frequency to be higher than NERC BAALHigh trigger limit.
                        Instruct the QSE with the positive SCE to bring their SCE
                        back to zero within 5 minutes.
                     Log the event and actions undertaken to bring the frequency
                        below BAAL trigger limit.
                If 25 consecutive minutes of ACE above BAALHigh (60.09 Hz):
                     If the non-compliant QSE‟s inform you that they cannot
                        restore zero (0) SCE or no QSE appears to be hanging out or
      25                no physical regulation down service is available.
   MINUTES           Issue fleet down instructions to additional QSEs with Down
                        Regulation room (see script above).
                     Log the event and actions undertaken to bring the frequency
                        below BAAL trigger limit.
                Once regulation is restored and frequency is stable, end fleet down
                generation instruction:

   STABLE       Typical script:
                This is ERCOT operator [first and last name]. ERCOT is ending
                VDI [#] at [time]. This ends the fleet down instruction. Please
                repeat this back to me. That is correct, thank you.”
ERCOT Operating Procedure Manual
Frequency Control Desk


     Step       Action

Response to Low Frequency
                Open realtime on „erpfileb‟/_Operations Official Spreadsheets/BAL
    BAAL
                007 ERCOT Interconnection and select Control T simultaneously to
    SHEET
                start spreadsheet.
                Frequency below 59.95 and continuing to drop or below 59.95 > 5
                minutes:
                     Remove SCE feedback from QSEs with negative SCE and
  MONITOR               monitor frequency response.
                     Consult with the Transmission and Security desk to confirm
                        that no OOMs from that desk could be affecting frequency.
                     Check to ensure available Up Regulation.
                If 10 consecutive minutes of ACE is less than BAALLow (59.91
                Hz):
                     Monitor regulation services and ensure that deployments are
                        sent out.
      10             Remove SCE feedback from QSEs with negative SCE and
   MINUTES              monitor frequency response.
                     Call QSEs with negative SCE and instruct them to increase
                        generation to return their SCE to zero as soon as possible.
                     Responsive Reserve (Contingency Reserve) will deploy to
                        bring back the frequency within normal range.
                If 15 consecutive minutes of ACE is less than BAALLow (59.91
                Hz):
                     Monitor regulation services and ensure that deployments are
                        being sent out.
                     Remove SCE feedback from QSEs with negative SCE.
                     Explain to the QSE with the negative SCE that their dispatch
                        is causing the low Frequency resulting frequency to be lower
                        than NERC BAALLow trigger limit. Instruct the QSE with
                        the negative SCE to bring their SCE back to zero within 10
      15                minutes.
   MINUTES           Issue fleet up instruct to QSE with Up Regulation room (see
                        script below).
                     Log the event and notify Shift Engineer.
                     Shift Engineer will send the event notification via email to
                        BAALfieldtrials@ercot.com.

                Issue Verbal Dispatch instructions to one or more QSE‟s (other than
                those failing to maintain SCE) to increase generation.

                Typical script:
ERCOT Operating Procedure Manual
Frequency Control Desk


     Step       Action
                “This is ERCOT operator [first and last name]. ERCOT is issuing
                VDI [#] to [QSE]. Increase your fleet generation by [MW amount]
                due to low frequency. Please repeat this directive back to me. That
                is correct, thank you.”

                It is not mandatory that a VDI # is given with the directive, if
                filling out paperwork later, use script below:


                Typical script:
                This is ERCOT operator [first and last name]. Increase your fleet
                generation by [MW amount] due to low frequency. Please repeat
                this back to me. That is correct; I will call back with a VDI #.”


                All directives shall be in a clear, concise, and definitive manner.
                Ensure the recipient of the directive repeats the information
                back correctly. Acknowledge the response as correct or repeat
                the original statement to resolve any misunderstandings.
                If 20 consecutive minutes of ACE is less than BAALLow (59.91
                Hz):
                     Monitor regulation services and ensure that deployments are
                       sent out.
                     Remove SCE feedback from QSEs with negative SCE.
                     Explain to the QSE with the negative SCE that their dispatch
                       is causing the low Frequency resulting frequency to be lower
      20
                       than NERC BAALLow trigger limit. Instruct the QSE with
   MINUTES
                       the negative SCE to bring their SCE back to zero within 5
                       minutes. Get an update on dispatcher actions and corrective
                       actions being taken.
                     Issue fleet up instruct to additional QSE(s) with Up
                       Regulation room (see script above).
                     Log the event and actions undertaken to bring the frequency
                       above BAAL trigger limit.
                If 25 consecutive minutes of ACE is less than BAALLow (59.91
                Hz):
                     If the non-compliant QSE‟s inform you that they cannot
                       restore zero (0) SCE or no QSE appears to be hanging out or
      25
                       no physical regulation down service is available.
   MINUTES
                     Issue fleet up instruct to additional QSE(s) with Up
                       Regulation room (see script above).
                     Log the event and actions undertaken to bring the frequency
                       above BAAL trigger limit.
ERCOT Operating Procedure Manual
Frequency Control Desk


     Step       Action
                Once regulation is restored and frequency is stable, end fleet up
                generation instruction:

                Typical script:
   STABLE
                This is ERCOT operator [first and last name]. ERCOT is ending
                VDI [#] at [time] This ends the fleet up instruction. Please repeat
                this back to me. That is correct, thank you.”

                Performance under the BAAL criteria for the yearly incentive plan
                will have the following levels of performance:

                        Level 1: Average of the 12 Monthly Maximum Durations
                         not to exceed 25 minutes.
                        Level 2: Average of the 12 Monthly Maximum Durations
  CRITERIA               not to exceed 17 minutes.
                        Level 3: Average of the 12 Monthly Maximum Durations
                         not to exceed 14 minutes.

                Individual performance will be assessed Level 0 if ACE exceeds the
                BAAL for more than 30 consecutive clock-minutes.

                If it is recognized that frequency is or expected to be outside +/- 0.1
   NOTIFY       Hz for a non-transient event and will not recover within 15 minutes,
                notify the Nuclear Power Plants QSEs.
Loss of Frequency Control
                IF the Energy Management System (EMS) frequency control is not
                functioning as indicated by:
                     AGC is SUSPENDED or PAUSED or
                     “Last AGC Cycle” time on Generation Area Status display is
      EMS              not updating, or
    ISSUES               AGC operation adversely impacts the reliability of the
                         Interconnection

                Place a large QSE (that has regulation reserve) on constant
                frequency, by issuing a VDI.
                 In the scenario where AGC operation adversely impacts the
  MONITOR           reliability of the interconnection, (ERCOT is handing over the
   MODE             frequency control to a large QSE), ERCOT AGC should be
                    placed into the MONITOR mode.
     QSE        Using the Hotline, notify all QSEs that ERCOT is having computer
   HOTLINE      issues and is putting a QSE on constant frequency.
ERCOT Operating Procedure Manual
Frequency Control Desk


     Step       Action
                        When QSEs have answered the Hotline, review Hotline
                         participants and log any issues. If necessary call participants
                         individually.

                Typical 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]. ERCOT is currently having
                computer issues and has put a QSE on constant frequency until
                further notice. [QSE] please repeat this back to me. That is correct,
                thank you.”

                All directives shall be in a clear, concise, and definitive manner.
                Ensure the recipient of the directive repeats the information
                back correctly. Acknowledge the response as correct or repeat
                the original statement to resolve any misunderstandings.”
     TO         Notify the Transmission & Security Desk to make the same hotline
   HOTLINE      call to the TO‟s.
                If the QSE that is put on constant frequency is having trouble
                keeping up, issue fleet VDI‟s to other QSE‟s to help out or put a
    FLEET       different QSE on constant frequency. Remember to take the first
                QSE off constant frequency.

                When frequency control is functional, remove QSE from constant
                frequency.

                Notify all QSE‟s by Hotline that ERCOT is back on control.
                    When QSEs have answered the Hotline, review Hotline
                       participants and log any issues. If necessary call participants
                       individually.

                Typical Script:
     QSE
   HOTLINE      “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]. ERCOT is back to normal
                operations. [QSE] please repeat this back to me. That is correct,
                thank you.”

                All directives shall be in a clear, concise, and definitive manner.
                Ensure the recipient of the directive repeats the information
                back correctly. Acknowledge the response as correct or repeat
ERCOT Operating Procedure Manual
Frequency Control Desk


     Step       Action
                the original statement to resolve any misunderstandings.”

     TO         Notify the Transmission & Security Desk to make the same hotline
   HOTLINE      call to the TO‟s.
                The ability to view an adequate Frequency source during a site-
                failover, Database load or if AGC is temporarily unavailable may be
                limited. To view the system Frequency during these conditions you
                may monitor the following sources.
   LOSS OF
                   ERCOT Control Room digital wall frequency displays
   EMS OR
                   PI ProcessBook → ERCOT → TrueTime Frequency
    SITE
                    (Taylor) and/or
  FAILOVER
                   PI ProcessBook → ERCOT → TrueTime Frequency
                    (Austin)

                Refer to procedure 2.5.2 for Actions When Frequency Telemetry is
                Incorrect.
ERCOT Operating Procedure Manual
Frequency Control Desk


2.5.2   Actions When Frequency Telemetry is Incorrect

        Procedure Purpose: To prevent the unnecessary deployment of Responsive
        Reserve due to incorrect telemetry frequency data.

Protocol Ref.

Guide Ref.
                            BAL-005-0.1b
NERC Std.                   R8


Approved by:                                 Effective Date: March 9, 2010
Version: 4                         Revision: 4


 Step     Action
          IF frequency is BELIEVED to be incorrect VERIFY that the frequency is
          correct by comparing the data from multiple sources.
   1               Go to the “Generation Area Status” display, and click on the “i” to
                      the left of “Current Frequency” to view “OPA Measurement”
                      window.
          In “OPA Measurement” window, under “Status” column, check “Prime” on a
   2
          valid frequency source.
   3      Refer to section 2.5.1 for action to be taken to correct frequency.

   4      LOG in the Operator‟s Log any relevant information on this event.
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.5.3     Monitor and Control Time Error Correction

      Procedure Purpose: This procedure will establish the standard for implementing
      time error correction.

Protocol Ref.
                          2.2.7
Guide Ref.
                          BAL-004-0
NERC Std.

Approved by:                                Effective Date: March 9, 2010
Version: 4                        Revision: 4


       Step            Action
                       ERCOT ISO is the Reliability Coordinator and Balancing
                       Authority that implements and terminates ERCOT Time
                       Corrections in accordance with ERCOT Protocols and Operating
                       Guides.
      NOTE:
                       ERCOT Reliability Coordinator is the Interconnection Time
                       Monitor within the ERCOT Interconnection.

                       When time error is equal to or greater than ±3 seconds, ERCOT may
                       initiate a time correction.

                       Time error corrections normally start and end on the hour or half-
                       hour.

                       The correction will be ended when the error is less than ±0.5
                       seconds.

REQUIREMENTS: The time correction may be postponed if it is determined that load
              patterns in the immediate future will result in the desired time
              correction.

                       However, at no time should the accumulated time error be allowed
                       to exceed five (5) seconds.

                       Time error correction notifications shall be labeled alphabetically
                       on a monthly basis (A-Z). In the succeeding month, the first time
                       error correction will revert back to “A”.
ERCOT Operating Procedure Manual
Frequency Control Desk


      Step        Action
                  DISPLAY the Generation Area Status display.

       1          Reference Display:
                        Generation Area Status – Time Error – “Correction
                  Schedule”
       2          Select Time Error – Correction Schedule.

       3          ENTER the appropriate Time error ID letter.
                  ENTER the frequency offset using – 0.02 for fast time correction
       4
                  (59.98 Hz) or +0.02 for slow time correction (60.02 Hz).
                  ENTER a Start Time later than the current time AND ENTER a
       5
                  Stop Time later than the scheduled start time.
                  The following notice is to allow QSEs time to incorporate the
     NOTE:        changed frequency in their Ancillary Service Performance
                  Monitor.
                  Notify all QSEs using a hotline call, if available, before starting
                  time correction, of the start time and frequency offset.

                  Typical script:
                  “This is ERCOT operator [first and last name]. ERCOT is
       6          initiating a time error correction, we will ENTER the frequency
                  offset using [– 0.02] or [+0.02] at [time]. The current time error
                  is [time]. Thank you.”

                  Review Hotline participants and log any issues. If necessary call
                  participants individually.
                  VERIFY the Manual radio button to be selected. Time correction
                  will start at selected date and time.
       7          Reference Display:
                           Generation Area Status – “Time Error” – Correction
                  Schedule
                  Monitor the time error on the Generation Area Status Display
                  until it reaches an acceptable value (+/- 0.5 seconds).
       8
                  Time error correction may be terminated after five hours, or after
                  any hour it has reached an acceptable value of +/- 0.5 seconds.
                  If a time error correction is prematurely terminated, wait at least
       9          one hour between sending the termination and re-initiation
                  notices.
                  The following notice is to allow QSEs time to incorporate the
     NOTE:
                  changed frequency in their Ancillary Service Performance
ERCOT Operating Procedure Manual
Frequency Control Desk


      Step        Action
                  Monitor.

                          Notify all QSEs using a hotline call, if available, before
                           ending time correction.

                  Typical script:
                  “This is ERCOT operator [first and last name]. ERCOT is ending
       10
                  the time error correction at [time]. The current time error is
                  [time]. Thank you.”

                         Review Hotline participants and log any issues. If
                          necessary call participants individually.
                  LOG in the Operator‟s Log start time, stop time, Time error ID
       11         letter, time error, and frequency offset for each start and
                  termination.
ERCOT Operating Procedure Manual
Frequency Control Desk


2.5.4 Potential DCS Event

      Procedure Purpose: To meet NERC Recovery Criteria after a potential NERC
      Reportable DCS Event.

Protocol Ref.

Guide Ref.
                             BAL-002-0        EOP-001-0       EOP-002-2.1
NERC Std.                    R2.4, R6.2       R5              R5, 6.1


Approved by:                                  Effective Date: March 9, 2010
Version: 4                          Revision: 5


   Step         Action
                There are times when the MW amount lost will be more than the NERC
 NOTE:          reportable amount. In these cases LaaRs can be used to recover frequency.

                NERC Recovery Criteria

                 Within 15 minutes ERCOT shall:
                 Return system frequency to scheduled frequency if it was greater than
                    or equal to scheduled frequency prior to the disturbance, OR
                 Return system frequency to its pre-disturbance value if it is was less
                    than scheduled frequency prior the disturbance.

                ERCOT ISO shall fully restore the minimum Contingency Reserve
                requirement of the ERCOT Region‟s largest single contingency (1354
                MW) as soon as practical. Within 90 minutes, ERCOT ISO will restore
 NOTE:          Responsive Reserves to 2300 MW or greater. This 90 minute restoration
                period begins at the end of the disturbance recovery period.

                 A potential NERC Reportable DCS Event
                 Single contingencies – one event characterized by the sudden,
                    unanticipated loss of generation greater than or equal to 1083 MW
                    OR
                 Multiple contingencies – the loss of multiple units within one minute
                    or less if the combined magnitude exceeds 1083 MW.

                It is anticipated that the deployment of LaaRs will occur in stages.
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           LaaRs UFRs are set at 59.7 Hz.

           If ERCOT declares an “Emergency Notice”, a text message may be sent as
           time permits so as not to impede system operations.

           In order to control frequency, be prepared to issue a “Fleet Down” VDI
           once the system has recovered to its scheduled/pre-disturbance frequency
           value.
           When a low frequency disturbance occurs due to a loss of generation,
    1      DETERMINE immediately, by calculating the loss of generation, if the
           event is potentially a NERC Reportable DCS Event.
           If a low frequency disturbance occurs, AND there is NO indication of a
           generation loss, determine the magnitude of the event by using the
           “Interconnection Control Error ” tag, Analyze the change in this tag after
           a minimum of 20 seconds to avoid the initial overshoot. Assume that a
           potential DCS event has occurred and SCADA communications has been
           lost if the total generation loss is greater than 1000 MW, implement Step 4
           of this procedure.

                   Determine the magnitude of the event by using the “Interconnection
    2
                    Control Error” tag on the “ERCOT & QSE Summary Page” in PI.
                   Take care to calculate the entire generation loss from the PI tag, not
                    just the difference between zero and the lowest number.

              Example:

           If the “Interconnection Control Error” pre-disturbance value is +150 MW,
           and post disturbance value is -950 MW, then the total generation loss is
           1100 MW. This constitutes a NERC Reportable DCS Event.
           IF the event is not a NERC Reportable DCS Event, proceed with normal
    3
           operation.
           IF the event is a potentially NERC Reportable DCS Event and the
           Frequency is above 59.7 Hz,
            When system conditions warrant, issue a VDI using the hotline
                instructing QSEs to deploy ALL un-deployed LaaRs and hydro
                generation that are bid to supply Responsive Reserve.
    4
           Typical 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]. ERCOT is issuing Verbal Dispatch Instruction F-
           (mmddyy-#) to all QSEs and instructing all QSEs to deploy LaaRs and
           hydro supplying Responsive Reserve. [QSE] please repeat this directive
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           back to me. That is correct, thank you.”

           It is not mandatory that a VDI # is given with the directive, if filling
           out paperwork later, use script below:

           Typical 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]. ERCOT is issuing a Verbal Dispatch Instruction
           instructing all QSEs to deploy LaaRs and hydro supplying Responsive
           Reserve. [QSE] please repeat this directive back to me. That is correct; I
           will call back with a VDI #.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
           Review Hotline participants and log any issues. If necessary call
    5
           participants individually.
           Complete the VDI form (See Desk Top Guide Section 7.4) and process.
            Issued a Verbal Dispatch Instruction to – write in “All QSEs”
            Receiving entity‟s operator – write in “All QSEs”
    6
            The instruction was as follows: “All QSEs are required to deploy any
                un-deployed LaaRs and hydro supplying Responsive Reserve due to a
                potential DCS event.”
           REQUEST that the Transmission & Security Desk notify the Transmission
    7
           Operators that LaaRs are being deployed.
           Verify all RRS from resources is recalled prior to restoring LaaRs
 NOTE:
           providing RRS.
            REQUEST that the Transmission & Security Desk notify the
    8
            Transmission Operators that LaaRs are being restored.
ERCOT Operating Procedure Manual
Frequency Control Desk



2.5.5       LaaR Deployment for North-Houston Voltage Stability Limit

            Procedure Purpose: To maintain North-Houston voltage stability.

Protocol Ref.

Guide Ref.
                                EOP-001-0     IRO-003-2      IRO-005-2         IRO-006-4
                                R2, R4.2      R1             R1.2, R1.7,       R1
NERC Std.                                                    R3
                                TOP-002-2
                                R10

Approved by:                                    Effective Date: March 9, 2010
Version: 4                            Revision: 2


   Step           Action
                  The North – Houston VSAT voltage stability limit is an IROL; the actual
  IROL            flow MUST NOT exceed the limit for more than 30 minutes. This is a
                  violation of the NERC Reliability Standards.
                  Deploy LaaRs in the Houston zone that are bid into the Responsive
                  Reserve market when requested by the Transmission and Security Desk for
                  the North – Houston IROL.

                          Make Hotline call to deploy LaaRs in the Houston zone that are
                           bid into the Responsive Reserve market.
                          Post a message on the MIS:
        1
                  Typical 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]. ERCOT is instructing QSE‟s to deploy LaaRs located
                  in the Houston Zone that are bid into the market within ten (10) minutes.
                  [QSE] please repeat this back to me. That is correct, thank you.”

                  Review Hotline participants and log any issues.          If necessary call
        2
                  participants individually.
ERCOT Operating Procedure Manual
Frequency Control Desk



2.5.6       Alarm Processing and Acknowledgment

            Procedure Purpose: To monitor and acknowledge system alarms.

Protocol Ref.

Guide Ref.
                               IRO-003-2       IRO-005-1
NERC Std.                      R2              R1.1


Approved by:                                    Effective Date: March 9, 2009
Version: 4                            Revision: 3


   Step           Action
                  The Alarm Displays for ERCOT are primarily used to show changes in
                  equipment status.

                  The alarms are categorized based on alarm criticality and prioritization on
                  the Alarm Summary Display:

                  Page 1: 345 KV Transmission Equipment Status
                  Page 2: 138 KV Transmission Equipment Status
  NOTE:
                  Page 3: Generator Breaker Status
                  Page 4: Transmission Line Overloads and Voltage Violations- critical
                  alarms
                  Page 5: Generator Unit, QSE SCE, and ERCOT ACE Status
                  Page 6: RTNET Status
                  Page 7: ICCP Status
                  Page 8: EMS Task Application Alarms

                  Monitor the Alarm Summary Display pages 3, 5, 6, and 7 as necessary to
        1
                  confirm system reliability status.
        2         Take appropriate action as system conditions warrant.
                  Coordinate with the Transmission & Security Desk to clear the alarms
        3
                  approximately every 2 to 3 hours or as needed.
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.6       Emergency and Short Supply Operations


Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                               Effective Date: May 1, 2009
Version: 4                       Revision: 0


      The ERCOT System Operators have the authority to make and carry through
      decisions that are required to operate the ERCOT System during emergency or
      adverse conditions. The following operating procedures detail the actions by the
      Frequency Control Desk for emergency or short supply situations and for
      restoration of service in the event of a partial or complete grid system shutdown.
      TDSP and QSE procedures shall describe implementation of ERCOT requests in
      emergency and short supply situations, including interrupting load, notifying
      others and restoration of service.

      Each TDSP will endeavor to maintain transmission intact if at all possible. This
      will: (1) permit rendering the maximum assistance to an area experiencing a
      deficiency in generation, (2) minimize the possibility of cascading loss to other
      parts of the system, and (3) assist in restoring operation to normal.

      These operating procedures shall meet the following goals while continuing to
      respect the confidentiality of market sensitive data:

      a. Utilization of the market to the fullest extent practicable without jeopardizing
         the reliability of the ERCOT System;
      b. Utilization of Responsive Reserve Services and other Ancillary Services to the
         extent permitted by ERCOT System conditions.
      c. Maximum utilization of ERCOT System Capability.
      d. Maintain station service for nuclear generating facilities.
      e. Securing startup power for power generating plants.
      f. Operating generating plants isolated from ERCOT without communication.
      g. Restoration of service to critical loads such as:
              Facilities necessary to restore the electric utility system
              Nuclear Units
              Military facilities
              Law enforcement organizations
              Facilities affecting public health.
ERCOT Operating Procedure Manual
Frequency Control Desk

             Communication facilities
     h. Restoration of service to all customers following major system disturbances,
        giving priority to the larger group of customers.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.6.1       Issue an Operating Condition Notice (OCN)

        Procedure Purpose: To inform the QSEs of a system Operating Condition
        Notice.

                              5.6.3
Protocol Ref.
                              4.2.1
Guide Ref.
                              IRO-005-2
NERC Std.                     R1.10


Approved by:                                    Effective Date: February 2, 2010
Version: 4                            Revision: 2


   Step         Action
                As directed by the Shift Supervisor, OR when appropriate, ISSUE an
                Operating Condition Notice
                (OCN) IF:

                    There is a hurricane in the Gulf with >20% chance of landfall in Texas
                     according to the National Hurricane Center (http://www.nhc.noaa.gov)
    1
                 A cold front is approaching with temperatures anticipated to be in mid
                     to low 20o F range and maximum temperature expected to remain near
                     or below freezing impacting 50% or more of major metropolitan areas.
                 Wet weather, such as a tropical storm making land fall.
                 There is a projected reserve capacity shortage and/or projected
                     balancing energy bid shortage.
                Issuance of an OCN requires:
                 Posting on the ENS
    2
                 Posting on the MIS
                 Notifying QSEs via the Hotline
                Using the Hotline, notify all QSEs of OCN.
                     When QSEs have answered the Hotline, review Hotline participants
                        and log any issues. If necessary call participants individually.

    3           Typical 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]. ERCOT is issuing an OCN for [state OCN]. [QSE]
                please repeat this back to me. That is correct, thank you.”
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           As time permits, notify the Shift Supervisor of any issues during the call.
    4
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.6.2       Issue an Advisory

        Procedure Purpose: To inform the QSEs of a system Advisory.

                              5.6.4
Protocol Ref.
                              4.2.2
Guide Ref.
                              IRO-005-2
NERC Std.                     R1.10


Approved by:                                    Effective Date: February 2, 2010
Version: 4                            Revision: 3


   Step         Action
                As directed by the Shift Supervisor, OR when appropriate, ISSUE an
                Advisory IF:

                     There is a hurricane in the Gulf with >20% chance of landfall in Texas
                      according        to     the      “National      Hurricane      Center”
                      http://www.nhc.noaa.gov
                     When ERCOT recognizes that conditions are developing or have
                      changed and more Ancillary Services will be needed to maintain
                      current or near-term operating reliability
                     When weather or ERCOT System conditions require more lead-time
                      than the normal Day Ahead market allows
                     Transmission system conditions indicate ERCOT is likely to exceed
                      established limits and no practicable resource solution exists
    1
                     Loss of communications or control condition is anticipated or
                      significantly limited
                     If ERCOT is unable to comply with any of the market timing
                      deadlines in the Day Ahead or Adjustment Period, or omits one or
                      more procedures in the scheduling process
                     Adjusted Responsive Reserve drops below 3000 MW (see procedure
                      2.6.6)
                     When long-range notice (approximately 48 hours) is needed to ensure
                      the secure operation of the ERCOT system, alert the Market
                      Participants to a potential threat to reliable operations with the
                      following:
                      o Lead time for dual fuel generating units to prepare for fuel supply
                          problems in the event of anticipated severe cold weather
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
               o Any other operational concerns

           Issuance of an Advisory requires:
            Posting on the ENS
    2
            Posting on the MIS
            Notifying QSEs via the Hotline
           Using the Hotline, notify all QSEs of Advisory.
                When QSEs have answered the Hotline, review Hotline participants
                  and log any issues. If necessary call participants individually.

           Typical 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
    3
           [first and last name]. ERCOT is issuing an Advisory for [state Advisory].
           [QSE] please repeat this back to me. That is correct, thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
           As time permits, notify the Shift Supervisor of any issues during the call.
    4
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.6.3    Issue a Watch

        Procedure Purpose: To inform the Market Participants of a system Watch

                            5.6.5
Protocol Ref.
                            4.2.3
Guide Ref.
                            COM-002-2       EOP-001-0      IRO-005-2
NERC Std.                   R2              R4.1           R1.10


Approved by:                                  Effective Date: February 2, 2010
Version: 4                          Revision: 4


   Step         Action
                ERCOT must issue a Watch before acquiring Emergency Short Supply
 NOTE:          Regulation Services, Emergency Short Supply Responsive Reserve
                Services, or Emergency Short Supply Spinning Reserve Services.
                As directed by the Shift Supervisor, OR when appropriate, ISSUE a Watch
                IF:
                 Transmission system conditions are such that ERCOT is expected to
                    exceed limits with no practicable resource solution
                 A transmission condition has been identified that requires emergency
                    energy from any of the CFE DC-Ties.
                 A short supply, or congestion condition has been identified and no
                    alternatives exist to relieve the condition
                 Conditions have developed such that additional Ancillary Services are
    1               needed in the Operating Period
                 There is a hurricane in the Gulf with expected landfall in Texas
                 A cold front has arrived with temperatures anticipated to be in mid to
                    low 20°F range and maximum temperature expected to remain near or
                    below freezing impacting 50% or more of major metropolitan areas
                 A situation is emerging that will have an adverse effect on grid
                    reliability
                 Loss of communications or control condition is pending or in progress.
                 Adjusted Responsive Reserve drops below 2500 MW (see procedure
                    2.6.6)
                Issuance of a Watch requires:
                 Posting on the ENS
    2
                 Posting on the MIS
                 Notifying QSEs via the Hotline
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           Using the Hotline, notify all QSEs of the Watch.
               When QSEs have answered the Hotline, review Hotline participants
                  and log any issues. If necessary call participants individually.

           Typical 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
    3
           [first and last name]. ERCOT is issuing a Watch for [state Watch]. [QSE]
           please repeat this back to me. That is correct, thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
           As time permits, notify the Shift Supervisor of any issues during the call.
    4
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.6.4       Issue an Emergency Notice

        Procedure Purpose: To inform the Market Participants of an Emergency Notice.

                              5.6.6           4.8
Protocol Ref.
                              4.2.4
Guide Ref.
                              COM-002-2       EOP-001-0      IRO-005-2
NERC Std.                     R2              R4.1           R1.10


Approved by:                                    Effective Date: February 2, 2010
Version: 4                            Revision: 3


   Step         Action
                Knowledge of an emerging/existing situation that could/does require
 NOTE:          intervention to ensure system reliability requires ERCOT to notify Market
                Participants through the use of Emergency Notifications.
                As directed by the Shift Supervisor, OR when appropriate, ISSUE an
                Emergency Notice IF:

                   A transmission condition has been identified causing unreliable
                    operation or overloaded elements.
                 A short supply, congestion condition is affecting voltage and/or
                    frequency with risk of grid area failure(s) and no practicable resource
                    solution exists.
                 A severe single contingency event presents the threat of uncontrolled
    1
                    separation or cascading outages, large-scale service disruption to load,
                    and/or overload of critical transmission elements and no practicable
                    resource solution exists.
                 ERCOT has determined a fuel shortage exists that would affect
                    reliability.
                 ERCOT varies from requirements or omits one or more scheduling
                    procedures, as described in Section 4.8, Temporary Deviations from
                    Scheduling Procedures.
                 Loss of Primary Control Center Functionality
                Issuance of an Emergency Notice requires:
                 Posting on the ENS
    2
                 Posting on the MIS
                 Notifying QSEs via the Hotline
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           Using the Hotline, notify all QSEs of the Emergency Notice.
               When QSEs have answered the Hotline, review Hotline participants
                  and log any issues. If necessary call participants individually.

           Typical 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
    3      [first and last name]. ERCOT is issuing an Emergency Notice for [state
           Emergency Notice]. [QSE] please repeat this back to me. That is correct,
           thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
           As time permits, notify the Shift Supervisor of any issues during the call.
    4
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.6.5    Termination of notification

        Procedure Purpose: To inform the QSEs of a cancellation of a previous
        notification.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                 Effective Date: February 2, 2010
Version: 4                         Revision: 2


   Step         Action
                If a condition increases in severity, then the posting of the corresponding
                Advisory, Watch, or Emergency Notice will constitute cancellation of the
 NOTE:
                previous notification. The termination of OCNs does not require a hotline
                call; however updating the ENS and MIS is necessary.
                Update cancellation notice:
                 On the ENS
    1
                 On the MIS
                 Notify QSEs via the Hotline
                Using the Hotline, notify all QSEs when notice has been canceled.
                      When QSEs have answered the Hotline, review Hotline participants
                        and log any issues. If necessary call participants individually.

                Typical 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
    2
                [first and last name]. ERCOT is canceling the [state Emergency Notice].
                [QSE] please repeat this back to me. That is correct, thank you.”

                All directives shall be in a clear, concise, and definitive manner.
                Ensure the recipient of the directive repeats the information back
                correctly. Acknowledge the response as correct or repeat the original
                statement to resolve any misunderstandings.
                As time permits, notify the Shift Supervisor of any issues during the call.
    3
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.6.6    Provide Advance Notice of Diminishing Responsive Reserve

        Procedure Purpose: Guidelines for issuing advance notice of diminishing
        Responsive Reserves

Protocol Ref.

Guide Ref.
                             BAL-002-0       EOP-001-0       EOP-002-2.1     IRO-005-2
                             R2.4            R3.1            R1, R2, R4,     R1.4, R1.5,
NERC Std.                                                    R6.1, R6.2,     R4
                                                             R6.4, R8


Approved by:                                 Effective Date: February 2, 2010
Version: 4                         Revision: 5


   Step         Action
                Adjusted Responsive Reserve (ARR)
 NOTE:
                Reference Display:
                EMS, Generation Area Status, ADJ_RESPONS
                Using the Hotline to issue the Advisory, notify QSEs when Adjusted
                Responsive Reserve is equal to or less than 3000 MW.
                    When QSEs have answered the Hotline, review Hotline participants
                       and log any issues. If necessary call participants individually.

                Typical 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]. ERCOT is issuing an Advisory to provide notice that
    1
                Adjusted Responsive Reserve has fallen below 3000 MW. Please keep
                your Resource Plan updated and notify ERCOT of any changes that will
                prevent you from meeting your Responsive Reserve obligation. [QSE]
                please repeat this back to me. That is correct, thank you.”

                All directives shall be in a clear, concise, and definitive manner.
                Ensure the recipient of the directive repeats the information back
                correctly. Acknowledge the response as correct or repeat the original
                statement to resolve any misunderstandings.
                As time permits, notify the Shift Supervisor of any issues during the call.
    2
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           Instruct the Transmission & Security Desk Operator to notify the TOs that
    3
           an Advisory has been issued.
           Ensure the following is posted on the ENS and MIS:
    4
                Advisory issued for ARR below 3000 MW.
           When adjusted Responsive Reserve falls below 2500 MW:

           Using the Hotline, notify QSEs:
               When QSEs have answered the Hotline, review Hotline participants
                  and log any issues. If necessary call participants individually.

           Typical 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]. ERCOT is issuing a Watch to provide notice that
           Adjusted Responsive Reserve has fallen below 2500 MW.
    5
                   Please keep your Resource Plan updated and notify ERCOT of any
                    changes that will prevent you from meeting your Responsive
                    Reserve obligation.
                   ERCOT ISO is reminding you, that you can schedule available
                    interchange into ERCOT across the DC-Ties.
                    Suspend all ERCOT required generation unit testing. [QSE] please
                    repeat this back to me. That is correct, thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
           Ensure the Operating Period Operator has deployed Non-Spin for ARR
    6
           below 2500 MW.
           If additional generation is needed, OOME to full output as many “Quick
           Start” GTs as necessary that are bid into the Balancing Market and show
           “On” and “Plan MW” = 0.
    7
           If issuing an OOME instruction on quick-start CTs that are showing “On”
           and “Plan MW” = 0. Follow up with a Settlements only VDI stating
           OOME for Quick-start” on the VDI form.
           Instruct the Transmission & Security Desk Operator to notify the TOs that
    8
           a Watch has been issued.
           Ensure the following is posted on the ENS and MIS:
    9
                 Watch issued for ARR below 2500 MW.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.6.7    Diminishing Reserve Notice Cancellation Guidelines

        Procedure Purpose: To provide notifications and back out of the actions taken
        during diminishing system reserves.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                 Effective Date: February 2, 2010
Version: 4                         Revision: 3


   Step         Action
                System conditions may dictate operating beyond the scope of this
                procedure. The System Operator has the authority to issue and/or keep a
                notification in effect as he/she deems necessary.
 NOTE:
                Adjusted Responsive Reserve (ARR)

                Reference Display: EMS, Generation Area Status, ADJ_RESPONS.
                IF Non-Spin has been deployed, work in conjunction with the Operating
    1           Period Desk Operator to recall Non-spin Reserve Services as system
                conditions permit.
                As system conditions permit, recall/release incrementally, any additional
    2
                generation that was brought online to recover ARR.
                Cancel a Watch or Advisory when:
                 All related OOM and Non-spin deployments have ended, AND
                 ARR is >= 3200 MW, AND
    3
                    o Load is trending down, OR
                    o The Excel MAI shows the “Max Cap Room” increasing over the
                        next two hours
                . IF a watch has been canceled,
                 NOTIFY QSEs that testing may be resumed.

                Typical scripts:
    4
                Cancel Advisory - “This is ERCOT operator [first and last name].
                ERCOT is canceling the Advisory for Adjusted Responsive Reserves
                below 3000 MW. [QSE] please repeat this back to me. That is correct,
                thank you.”
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action



           Cancel Watch - “This is ERCOT operator [first and last name]. ERCOT
           is canceling the Watch for Adjusted Responsive Reserves below 2500
           MW. At this time, performance testing may resume. [QSE] please repeat
           this back to me. That is correct, thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
           As time permits, notify the Shift Supervisor of any issues during the call.
    5
           Instruct the Transmission & Security Desk Operator to notify the TOs that
    6
           an Advisory or Watch has been cancelled.
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.6.8     Implement EEA

      Procedure Purpose: To implement an Energy Emergency Alert(s) for the
      appropriate system conditions.

                             5.6.7
Protocol Ref.
                             4.5.3.2
Guide Ref.
                             COM-002-2         EOP-001-0      EOP-002-2.1     IRO-005-2
                             R2                R3.1, R3.3,    R1, R2, R4,     R1.5, R1.10
                                               R5             R6.1, R6.2,
NERC Std.                                                     R6.4, R6.6,
                                                              R8


Approved by:                                     Effective Date: February 2, 2010
Version: 4                             Revision: 5


   Step         Action
                Frequency Control Desk will implement applicable levels of the EEA.

                EEA in this procedure is to be implemented in concert with the
                Transmission & Security Desk EEA procedures.

                Public media appeals may be enacted prior to EEA as deemed necessary by
 NOTE:          the Shift Supervisor. When a media appeal for voluntary energy
                conservation is enacted QSE‟s should be notified via Hotline call.

                For the purpose of this procedure, Physical Responsive Capability PRC
                plus Responsive Reserve Service (RRS) provided from LaaR as defined
                and used in the ERCOT Operating Guides Section 1.6 and 4.5.3.3 shall be
                referred to as Adjusted Responsive Reserves.
                Whenever the QSE or TO hotline is used to issue an Emergency Notice
                that any level of EEA is being implemented, direct all hotline participants
                to remain on the line until a hotline participant of your choice correctly
 NOTE:
                repeats back to you the directive. If the repeat back is not acceptable,
                restate the directive and direct them to repeat back again. Continue until an
                acceptable repeat back is received.
                IF frequency falls below 59.8 Hz, ERCOT CAN immediately implement
 NOTE:          EEA 3.
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           IF frequency falls below 59.5 Hz, ERCOT SHALL immediately
           implement EEA 3
           Implement EEA 1 IF:
               Adjusted Responsive Reserves fall below 2300 MW, OR
               ERCOT has deployed over 760 MW of Responsive Reserve Service
                 (RRS) supplied from generation resources in response to low
   1a            frequency due to a capacity insufficiency.

           Reference Display:
           Generation Area Status, Generation Reserve Status, Available Details,
           ERCOT ON UNIT ERCOT Load Acting As Resource (LaaR)
           Using the hotline, notify QSEs to implement EEA 1.
               When QSEs have answered the Hotline, review Hotline participants
                  and log any issues. If necessary call participants individually.


           Typical 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]. ERCOT is implementing EEA 1, QSEs are to do the
           following:
                 Report when online available capacity is at risk due to adverse
                    circumstance.
                 Immediately and continually update Resource Plans to reflect all
                    resource delays and limitations should they occur.
                 Notify ERCOT of all available uncommitted units within the
   1b
                    expected time frame of the emergency.
                 QSE‟s are not to take units off-line while ERCOT is in emergency
                    operations unless it is due to a forced outage.
                 Suspend testing on all resources.
                 QSEs are to report back to the ERCOT System Operator on the
                    progress and/or completion of the aforementioned items.
                 ERCOT ISO is reminding you, that you can schedule available
                    interchange into ERCOT across the DC-Ties.
                [QSE] please repeat this directive back to me. That is correct, thank
                you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           As time permits, notify the Shift Supervisor of any issues during the call.
   1c
           Ensure the following is posted on the ENS and MIS:
   1d
               Implemented EEA 1
           VERIFY and log the following as appropriate:
               Available Non-Spin has been deployed
   1e          Available uncommitted units have been dispatched and loaded as
                  necessary
               Testing has been suspended on all resources
           IN ADDITION TO MEASURES ASSOCIATED WITH EEA 1

           IMPLEMENT EEA 2A IF:
              EEA 1 fails to maintain Adjusted Responsive Reserves equal to or
   2a           greater than 1750 MW.

           Reference Display:
           Generation Area Status, Generation Reserve Status, Available Details,
           ERCOT ON UNIT ERCOT Load Acting As Resource (LaaR)
           Using the hotline, notify QSEs to implement EEA 2A.
               When QSEs have answered the Hotline, review Hotline participants
                  and log any issues. If necessary call participants individually.

           Typical 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]. ERCOT is implementing EEA 2A; ERCOT is issuing
           Verbal Dispatch Instruction F-(mmddyy-#) to QSEs to deploy all LaaRs
           bid to supply Responsive Reserves Service within ten (10) minutes. Also:
   2b            QSEs are not to take units off-line while ERCOT is in emergency
                    operations unless it is due to a forced outage.
                 QSEs are required to report back to the ERCOT System Operator
                    when this task has been completed.
                [QSE] please repeat this directive back to me. That is correct, thank
                you.”

               All directives shall be in a clear, concise, and definitive manner.
               Ensure the recipient of the directive repeats the information back
               correctly. Acknowledge the response as correct or repeat the
               original statement to resolve any misunderstandings.
           Instruct the Transmission & Security Desk Operator to inform the TOs via
   2c
           the Hotline that LaaR have been deployed.
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           As time permits, notify the Shift Supervisor of any issues during the call.
   2d
           Ensure the following is posted on the ENS and MIS:
   2e
               Implemented EEA 2A
           VERIFY and log the following as appropriate:
               Available Non-Spin has been deployed
               Available uncommitted units have been dispatched and loaded as
   2f             necessary
               Testing has been suspended on all resources.
               LaaRs have been deployed.

           Unless a media appeal is already in effect, one is required in this level.
 NOTE:     Ask the Shift Supervisor about the issuance of the media appeal for
           voluntary energy conservation
           IN ADDITION TO MEASURES ASSOCIATED WITH EEA 1 & 2A;

           IMPLEMENT EEA 2B IF:
           EILS has been procured AND any of the following occur:
               Frequency drops below 60.00 Hz, OR
               Frequency begins to trend down with no indication for recovery,
                 OR
   3a
               Adjusted Responsive Reserves continue to trend down, OR
               Adjusted Responsive Reserves are no longer available
               Based on a combination of system conditions, the operator believes
                 that an EILS deployment is necessary to maintain frequency at
                 60.00 Hz.

           If no EILS exist, skip EEA 2B and proceed to EEA 3 if needed.
           Using the hotline, notify QSEs to implement EEA 2B.
                When QSEs have answered the Hotline, review Hotline participants
                   and log any issues. If necessary call participants individually.

           Typical 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
   3b
           [first and last name]. ERCOT is implementing EEA 2B. ERCOT is issuing
           Verbal Dispatch Instruction F-(mmddyy-#) to all QSE‟s to deploy
           contracted EILS Resources in the current time period until further notice.
           [QSE] please repeat this directive back to me. That is correct, thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
           Instruct the Transmission & Security Desk Operator to inform the TOs via
   3c
           the Hotline that EILS Resources have been deployed.
           EILS Resources have 10 minutes to comply with this instruction.
           If conditions develop that require implementing EEA 3, ERCOT may
           at its discretion shed firm load prior to the expiration of the 10 min.
           period.

           When a deployment of EILS is implemented and the event is still in effect
           when one Time Period ends and the other begins, deployed EILS
           Resources will remain deployed until, at ERCOT‟s discretion, they are
 NOTE:     recalled via a Hotline call to QSEs.

           In the event of a new EILS Time Period, a new VDI may need to be issued
           to deploy obligated EILS Resources that have become available due to the
           Time Period transition.

           ERCOT System Operators will make reasonable efforts to recall EILS
           Resources that are no longer obligated due to the expiration of a Time
           Period.
           As time permits, notify the Shift Supervisor of any issues during the call.
   3d
           Ensure the following is posted on the ENS and MIS:
   3e
                Implemented EEA 2B
           IN ADDITION TO MEASURES ASSOCIATED WITH EEA 1, 2A, &
           2B;

           IMPLEMENT EEA 3 IF:
   4a
            Frequency drops below 59.80 Hz, OR
            Frequency begins to trend down with no indication for recovery, OR
            Adjusted Responsive Reserves continue to trend down, OR
            Adjusted Responsive Reserves are no longer available.
           Using the hotline, notify QSEs to implement EEA 3.
               When QSEs have answered the Hotline, review Hotline participants
                  and log any issues. If necessary call participants individually.

   4b      Typical 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]. ERCOT is implementing EEA 3. Transmission
           Operators have been instructed to shed <MW Amount> of firm load.
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           QSEs confirm that their generation resources are at maximum output.
           [QSE] please repeat this directive back to me. That is correct, thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
           As time permits, notify the Shift Supervisor of any issues during the call.
   4c
           Ensure the following is posted on the ENS and MIS:
   4d
             Implemented EEA 3
           VERIFY the following:
            All Generation Resources are at full capacity
            Available Non-Spin has been deployed
   4e       Uncommitted QSE‟s available units have been dispatched to full load
            All resource testing has been suspended
            All LaaRs have been deployed by QSEs with RRS Obligations
            All EILS Loads have been deployed by QSEs with EILS Obligations
ERCOT Operating Procedure Manual
Frequency Control Desk


         2.6.9   Restore EEA

         Procedure Purpose: Backing out and terminating Energy Emergency Alert(s).

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                   Effective Date: February 2, 2010
Version: 4                           Revision: 3


   Step          Action
                 The Frequency Control Desk will implement applicable levels of the EEA
                 Restoration.

                 Numbering of procedure steps is reversed to coincide with EEA.
 NOTE:
                 EEA in this procedure is to be implemented in concert with the
                 Transmission & Security Desk EEA procedures.

                 Restore firm load when:
                      Sufficient Regulation Service exist to control to 60 Hz, AND
    4a
                      Adjusted Responsive Reserve supplied from generation is greater
                         than 1150 MW
                 Notify the QSEs when the Transmission & Security Desk Operator begins
                 to restore firm load.

                 Using the hotline, notify QSEs of the restoration of firm load:
                     When QSEs have answered the Hotline, review Hotline participants
                        and log any issues. If necessary call participants individually.

    4b           Typical 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]. ERCOT is currently restoring firm load. [QSE]
                 please repeat this back to me. That is correct, thank you.”

                 All directives shall be in a clear, concise, and definitive manner.
                 Ensure the recipient of the directive repeats the information back
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.

           Move from EEA 3 to EEA 2B when:
              Sufficient Regulation Service exist to control to 60 Hz, AND
              Adjusted Responsive Reserve supplied from generation is equal to
   4c
                 1150 MWs, AND
              All firm load has been restored.

           Using the hotline, notify QSEs of the reduction from EEA
           3 to 2B, if 2B was skipped move from EEA 3 to 2A :
               When QSEs have answered the Hotline, review Hotline participants
                  and log any issues. If necessary call participants individually.

           Typical 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
   4d      [first and last name]. ERCOT is moving from EEA 3 to EEA 2B.” QSEs
           that deployed LaaR in EEA 2A may begin to restore them at this time.
           [QSE] please repeat this directive back to me. That is correct, thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.

           As time permits, notify the Shift Supervisor of any issues during the call.
   4e
           Ensure the following is posted on the ENS and MIS:
   4f
                EEA 3 to EEA 2B
           Instruct the Transmission & Security Desk Operator to notify the TOs that
   4g
           LaaRs are being restored.
           Maintain a minimum of 1150 MWs of Adjusted Responsive Reserve
 NOTE:
           supplied from generation resources while LaaRs are being restored
           Move from EEA 2B to EEA 2A when:
                The system can maintain Adjusted Responsive Reserve equal to or
   3a              greater than 1750 MWs, AND
                All LaaRs have been recalled. AND
                Sufficient Regulation Service exist to control to 60 Hz.
           Using the hotline, notify all QSEs of the reduction from EEA 2B to EEA
   3b      2A:
                When QSEs have answered the Hotline, review Hotline participants
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
                    and log any issues. If necessary call participants individually.

           Typical 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]. ERCOT is moving from EEA 2B to EEA 2A. [QSE]
           please repeat this back to me. That is correct, thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.

           As time permits, notify the Shift Supervisor of any issues during the call.
   3c
           Ensure the following is posted on the ENS and MIS:
   3d
                EEA 2B to EEA 2A
           Instruct the Transmission & Security Desk Operator to notify the TOs that
   3e
           ERCOT moved from EEA 2B to EEA 2A.
           Appeals through the public news media for voluntary energy conservation
   3f
           may be terminated, notify Shift Supervisor
           Move from EEA 2A to EEA 1 when:
                The system can maintain Adjusted Responsive Reserve equal to or
   2a              greater than 2300 MW AND
                All LaaR have been requested to be restored or replaced with
                   generation
           Using the hotline, notify QSEs of the reduction from EEA 2A to EEA 1:
                When QSEs have answered the Hotline, review Hotline participants
                   and log any issues. If necessary call participants individually.

           Typical 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]. ERCOT is moving from EEA 2A to EEA 1. QSE‟s
   2b
           that deployed EILS Resources in EEA 2B may begin to restore them at this
           time. [QSE] please repeat this directive back to me. That is correct, thank
           you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
ERCOT Operating Procedure Manual
Frequency Control Desk


  Step     Action
           As time permits, notify the Shift Supervisor of any issues during the call.
   2c
           Ensure the following is posted on the ENS and MIS:
   2d
                EEA 2A to EEA 1
           Instruct the Transmission & Security Desk Operator to notify the TOs that
   2e
           EILS Resources are being recalled.
           Move from EEA 1 to EEA 0 when:
                EILS Resources have been requested to be recalled AND
                All uncommitted units secured in EEA 1 can be released to reduce
   1a
                   generation, AND
                Emergency power from the DC Ties is no longer needed, AND
                Sufficient Regulation Service exist to control to 60 Hz.
           Using the hotline, notify QSEs of the reduction from EEA 1 to EEA 0:
                When QSEs have answered the Hotline, review Hotline participants
                   and log any issues. If necessary call participants individually.

           Typical 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
   1b
           [first and last name]. ERCOT is terminating EEA. A Watch still remains in
           effect. [QSE] please repeat this back to me. That is correct, thank you.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
           As time permits, notify the Shift Supervisor of any issues during the call.
   1c
           Ensure the following is posted on the ENS and MIS:
   1d
                EEA termination
           Instruct the Transmission & Security Desk Operator to notify the TOs of
   1e
           the termination of EEA.
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.6.10 Loss of Primary Control Center Functionality

      Procedure Purpose: This procedure is to be performed by the Operator at the
      alternate Control Center (ACC) in the event that:
           Functionality of the Primary Control Center (PCC) is lost OR
           Communication with the PCC is lost OR
           As directed by the Shift Supervisor.

Protocol Ref.

Guide Ref.
                           COM-001-1.1       EOP-001-0     EOP-008-0       IRO-005-2
NERC Std.                  R5                R4.4                          R1.10


Approved by:                                Effective Date: March 9, 2010
Version: 4                        Revision: 9


    Step        Action
                IF:
                       You are unable to reach any Operators at the PCC (cell phone or
                        PBX Bypass phones),
                THEN:
  Contact            Check the Control Room video camera to determine the status of
  Security              the PCC and personnel.
                     Contact Security at the ACC
                            o Notify them of the situation AND
                            o Have them attempt to make contact with Security at PCC.
                            o Have them contact you with information acquired.
                Place a large QSE (that has regulation reserve) on constant frequency, by
                issuing a VDI.
  Constant
 Frequency                               * * * WARNING * * *
                When placing a QSE on constant frequency control, place ERCOT AGC
                in Monitor mode.
                Place the following Hotline calls to the QSE‟s and TO‟s:
  Notify
                Hotline call to QSEs:
  Market
Participants
                Typical 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 Operating Procedure Manual
Frequency Control Desk


    Step        Action
                ERCOT operator [first and last name]; ERCOT is declaring an
                emergency and is transferring operations to the alternate control center.
                Until further notice, direct all urgent phone calls to (512) 225-7100.
                ERCOT has put a QSE on constant frequency. All remaining QSEs
                follow your base power schedules and hold interval ending [last interval].
                VDI # is [#]. Day-Ahead Market functions may be delayed” [Select
                QSE], “Please repeat this directive back for me.”
                If repeat back is CORRECT, “That is correct, thank you.”
                If INCORRECT, repeat the entire process until the repeat back is
                correct.

                Hotline call to TOs:

                Typical Script: “This call requires everyone to remain on the line until
                it is complete. [TO] I will be asking you for the repeat back. This is
                ERCOT operator [first and last name]; ERCOT declaring an emergency
                and is transferring operations to the alternate control center. Until further
                notice, direct all urgent phone calls to (512) 225-7100. Please monitor
                your own service area and notify ERCOT if you exceed the normal rating
                of your transmission elements. Report zonal CSC transfers, West - North
                and North – Houston stability limits if power flows reach 90% of the last
                posted limit. Continue to monitor voltages in your area and notify
                ERCOT of any abnormal line operations.” [Select TO], “Please repeat
                this directive back for me.”
                If repeat back is CORRECT, “That is correct, thank you.”
                If INCORRECT, repeat the entire process until the repeat back is
                correct.

                Notify the appropriate Nuclear Plant‟s QSEs and inform them that
                ERCOT‟s RTCA is not function and is expected to be functional within
                [# minutes].
                IF:
                     The shift personnel at the PCC will NOT be relocating,
                THEN:
  Call in            Call in additional shift personnel, which include a Shift
 Additional            Supervisor, via the Communicator! NXT Notification System
 Operators             (NXT).

                Operator will receive an email after 10 minutes with a report of who has
                responded along with their estimated time of arrival.
                Notify the following:
 Additional
Notifications
                        Manager of System Operations and/or designee
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step       Action


                        o   If unable to reach Manager of System Operations and/or
                            designee, notify the following:

                       Help Desk (to notify EMMS Support and Telecommunications)
                       Engineering Support

              These phone numbers have been programmed into the control room cell
              phone.
              Potential critical facilities will be apparent to the Operator by notification
              from TOs based on the information ERCOT has requested within the
              Hotline Call instructions.

              Critical facilities will be those that show up in RTCA.
              ERCOT considers the list of critical facilities to be the contingencies
 Monitor
              posted on the ERCOT website under „Grid Information‟ in the
  Critical
              Transmission section
 Facilities

              http://www.ercot.com/gridinfo/transmission/index

              Select “Operations Contingency List (ESCA)” in the key document
              section.
              IF:
                   The QSE that is put on constant frequency is having trouble
                      keeping up,
              THEN:
                   Issue fleet VDIs to other QSEs to help out OR
                   Put a different QSE on constant frequency (Remember to take the
                      first QSE off constant frequency).
Respond to
                                                    OR
  QSEs
              IF:
                 QSEs call in with questions about the Day-Ahead Market,
              THEN:
                 Notify the QSE that the Day-Ahead Market functions will resume
                  when additional staff reports to work.
                 Document which QSEs call in and the questions they have to pass
                  along to the Day-Ahead Operator when he/she reports to work.

Respond to    IF:
  TSPs                 TOs call in to report the following:
ERCOT Operating Procedure Manual
Frequency Control Desk


    Step       Action
                        o Thermal limits have reached their continuous rating,
                        o Zonal CSC transfers have reached 90% of the last posted
                          limit,
                        o West-North stability limit has reached 90% of its limit,,
                        o North-Houston stability limit has reached 90% of its limit,
             THEN:
                   If EMS is available, verify their values against ERCOT‟s,
                   Take immediate action, as listed below, for thermal limits and
                     stability limits,
                   Continue to monitor the zonal transfers; Instruct the TO to do the
                     same and notify ERCOT should the limits reach 95%,
                   Prepare to respond, as listed below, should the zonal transfers
                     reach 95% and trending upward.
             IF:
                  The West-North stability limit is approaching 90% and is
                    continuing to trend upward,
                  The North-Houston stability limit is approaching 90% and is
  Stability         continuing to trend upward,
    Limits
                  Notified by TO that a stability limit is approaching 90% and is
Reached 90%
                    continuing to trend upward,
   (IROL)
             THEN:
                  Take immediate action to lower Wind Generation in the west,
                  Issue VDIs as necessary to relieve the congestion,
                  If VDIs are issued, monitor QSE on constant frequency
             IF:
                  Thermal limits have reached their continuous rating and are
  Thermal           continuing to trend upward, OR
    Limits        Zonal transfers have reached 95% of their limit,
Reached and THEN:
    Zonal         Seek a recommendation from the corresponding TO as to what
Transfers at        actions will alleviate the situation,
 95% (SOL)        When you decide the recommended actions are valid, implement
                    the plan and issue VDIs as necessary.
                  Continue to monitor to determine the effect of the plan.
             Make every attempt to handle all DC Tie tags.
DC Tie Tags
               If the workload makes it impossible to keep up with, the tags will be
               passively denied.
               RECORD the following in the shift log:
 Operator
                    Date
 Technical
                    Time of event
   Logs
                    Description of events, failures, or incident
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step     Action
                Actions taken and resolution
            Time of system or function restoration
ERCOT Operating Procedure Manual
Frequency Control Desk



2.6.11 Restoration of Primary Control Center Functionality

      Procedure Purpose: This procedure is to be performed by the Frequency Control
      Desk Operators at the alternate Control Center (ACC) in restoring Real-Time
      operations.
          Essential staff has arrived,
          ACC has become PCC,
          All EMS applications up and functioning properly

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                 Effective Date: February 2, 2010
Version: 4                         Revision: 5


   Step         Action
                As additional Operators arrive, be sure to communicate any pertinent
  NOTE:         information that will assist them in getting their specific functions ready
                for normal operation.
                When an Operating Period Desk Operator has arrived, had time to get the
                offset calculation spreadsheet caught up, and is able to enter offset values
                into the MOI:

                IF:
                   Holding Real-time Balancing Energy Market (RTB) deployments,
                THEN:
 Restoring         Verify the proper operation of the RTB and that deployments are
 Frequency          being sent to the Market Participants (MP) AND
  Control          Remove the QSE that is put on constant frequency and end VDI.


                                      * * * WARNING * * *
                When removing a QSE from constant frequency control, remove ERCOT
                AGC from Monitor mode.


  Market        IF:
ERCOT Operating Procedure Manual
Frequency Control Desk


    Step        Action
Notification       RTBM is running and valid deployments are being sent,
                THEN:
                   Place the following QSE Hotline call:

                Typical 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], ERCOT is resuming normal, Real-
                Time operations from the alternate control center. Please continue to
                direct all phone calls to (512) 225-7100. ERCOT is ending VDI [#] at
                [time]. Resume with the [interval ending time] Balancing Energy
                deployments. [Select QSE], “Please repeat this directive back for me.”
                If repeat back is CORRECT, “That is correct, thank you.”

                If INCORRECT, repeat the entire process until the repeat back is correct.
                Notify the following:

                      Help Desk (to notify EMMS Support, Telecommunications)
 Additional
                      Manager of System Operations and/or designee
Notifications
                      Engineering Support
                          o These phone numbers have been programmed into the
                               control room cell phone.
                WHEN:
Notification
                    All functionality has been resumed at the ACC,
     of
                THEN:
Additional
                    Notify the additional shift personnel, which include a Shift
 Operators
                       Supervisor, via the Communicator! NXT Notification System.
  Contact       Notify Security that the transition of Operations to the ACC has been
  Security      completed
                RECORD the following in the shift log:
                    Date
 Operator
                    Time of event
 Technical
                    Description of events, failures, or incident
   Logs
                    Actions taken and resolution
                    Time of system or function restoration
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7       DC Ties

      2.7.1     Approve E-Tags for SPP DC Ties

      Procedure Purpose: An E-Tag received in the OATI WebTrans regarding DC
      Tie flows into or out of ERCOT will be validated for accuracy, and should be in
      agreement with the Market Operating System (MOS) except for changes made
      during the Operating Period such as curtailments.

Protocol Ref.

Guide Ref.
                             INT-005-2     INT-006-2       INT-007-1       INT-009-1
                             R1            R1, R1.1,       R1.1, R1.2      R1
                                           R1.2, R1.3,
NERC Std.
                                           R1.2
                             TOP-002-2
                             R5, R9

Approved by:                                 Effective Date: March 9, 2010
Version: 4                         Revision: 4


   Step         Action
                AEP TO in Columbus, Ohio is the Tie Operator for the East and North DC
  NOTE:         Ties. The designation in WebTrans for the East tie is DC_E and the North
                tie is DC_N.
                Do not approve an E-Tag that crosses the midnight hour. We need one E-
  NOTE:         Tag per day in order for the schedules to transfer into the Market system
                correctly.
                Each time a new or updated E-Tag is submitted, the WebTrans system will
                automatically validate the E-Tag. WebTrans will display whether the E-
                Tag has passed or failed validation.
                The criteria ERCOT uses to validate E-Tags is:

                        QSE Contract-A QSE ID must be entered into the ERCOT Market
  NOTE:
                         Information field of the E-Tag.
                        QSE MW-A QSE‟s MOI schedule must be greater than or equal to
                         the associated E-Tag.
                        TP Required-ERCOT must be specified as a Transmission
                         Provider in the Physical Path of the E-Tag.
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step    Action
           Currently the validation criterion set to automatically deny an E-Tag is
           “QSE Contract” and “TP Required”. If either or both of these validations
           fail the E-Tag will be automatically denied.

           If you feel an E-Tag failed validation erroneously, the list of approved
           ERCOT Registered QSE‟s can be found at the following website:

           http://www.ercot.com/mktparticipants/docs/QSEs.xls

           Select the DC Tie Scheduling List tab to view the ERCOT Registered
           QSE‟s. If the QSE name is on the list but was denied by WebTrans,
           approve the E-Tag and inform the OATI help desk.

           Another point of reference is to view the “QSE Contracts” in WebTrans.
           Each QSE is associated with each DC-Tie individually.

           WebTrans Reference Display:
           Tag Validation Monitor
           When a new or updated E-Tag is received in the OATI WebTrans system:

           1.1 Determine if the following information is correct on the E-Tag:
                Ensure “ERCO” is not listed as a PSE in the Physical Path
                “ERCOT-E” or “ERCOT-N” is selected for the correct Point-of-
                  Receipt (POR) or Point of Delivery (POD) portion of the physical
                  path.
                “CSWS” is included as a Scheduling Entity on the SWPP TP row
                  in the physical path. EXCEPT if “CSWS” is listed as the
                  Generation Control Area (GCA) or Load Control Area (LCA) in
                  the physical path. (Note: If CSWS is listed in both the Scheduled
                  Entities column and GCA or LCA, this will cause double counting
    1             in the Tie Operators net-scheduled value so the “before the start of
                  the hour” check out will not match. These type tags should be
                  denied).
                There 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.
                Start/Stop times for a new E-Tag must be on a quarter hour (:00,
                  :15, :30, :45).

           If any of this information is incorrect on the E-Tag, deny the E-Tag,
           otherwise go to Step 1.2.

           1.2 If one or more E-Tags are submitted that will cause the DC Tie to be
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step      Action
             overscheduled:

                     Contact SPP to ensure they also see the over-schedule and they
                      will ensure the appropriate actions are taken to correct the over-
                      schedule. Also inform SPP that if the appropriate actions to
                      correct the over-schedule are not in place by 20 minutes before the
                      over-schedule will occur, ERCOT will curtail the E-Tag to zero (0)
                      based on the criteria of “Last in – First out” until the over schedule
                      is alleviated.
                     IF an E-Tag is curtailed to zero (0) due to an over-schedule that
                      was not corrected in time, contact the source/sink control area to
                      ensure the curtailment will be implemented as soon as possible.

             1.3 Determine if the E-Tag passed or failed validation.

                     If the E-Tag passes validation, go to Step 2.
                     If the E-Tag fails validation and the E-Tag is automatically denied
                      (QSE Contract), no further action is required.
                     If the E-Tag fails validation and the E-Tag is not automatically
                      denied (QSE MW), go to Step 2.

         WebTrans Reference Displays:
         Tag Validation Monitor
         Tag Validation Criteria
         Tag Approval Monitor
         QSE Summary
         Do not approve an E-Tag without an associated MOI schedule. If the QSE
CAUTION: does not submit an MOI schedule before the end of the E-Tag approval
         timeline, the E-Tag will automatically be passively denied.
         Periodically refresh the QSE Summary display during the E-Tag approval
         timeline to determine if a QSE has submitted an MOI schedule.

             When an MOI schedule has been received, compare the E-Tag data to the
             schedule:

                     If the E-Tag is greater than the MOI schedule per 15 minute
     2
                      interval, then the MOI schedule does not have enough generation
                      to cover the E-Tag. The “Mismatched” value box will be red and
                      the MW difference will be a negative amount. Deny the E-Tag.
                     If the E-Tag is less than the MOI schedule per 15 minute interval,
                      which means there is enough generation scheduled, the
                      “Mismatched” box will be yellow and the MW amount will be a
                      positive amount. Approve the E-Tag.
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step    Action
                   If the E-Tag equals the MOI schedule per 15 minute interval,
                    which means there is enough generation scheduled; the
                    “Mismatched” box will be green with a value of “0”. Approve the
                    E-Tag.

           WebTrans Reference Display:
           QSE Summary
           Tag Approval Monitor
ERCOT Operating Procedure Manual
Frequency Control Desk

2.7.2 Import and Export Limits for the CFE DC Ties

         Procedure Purpose: To confirm the import and export limits of the CFE DC
         Ties.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                Effective Date: May 1, 2009
Version: 4                        Revision: 0


   Step         Action
                Daily import and export limits for the Railroad and Eagle Pass DC Ties,
  NOTE:         and Laredo VFT will be provided by the Operations Engineering Support
                Group on the “Transmission Limits to Be Monitored Sheet”.
                Once the DC-Tie limits for next day are received, check the sum of the E-
                Tags to ensure the import/export limits are not exceeded on any DC-Tie.
     1
                If so, contact the PSE of the last E-Tag received and request adjustments
                to be made.
                After midnight, verify that the daily import and export limits have been
                updated in RTMONI and are displayed correctly on the ERCOT website
     2          at: http://mospublic.ercot.com/ercot/jsp/frequency_control.jsp      If a
                discrepancy is found, contact the Transmission & Security Desk to
                update.
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7.3     Approve E-Tags for the CFE DC Ties

      Procedure Purpose: An E-Tag received in the OATI WebTrans regarding DC
      Tie flows into or out of ERCOT will be validated for accuracy, and should be in
      agreement with the Market Operating System (MOS) except for changes made
      during the Operating Period such as curtailments.

Protocol Ref.

Guide Ref.
                            INT-005-2      INT-006-3       INT-007-1       INT-009-1
                            R1             R1, R1.1,       R1.1, R1.2      R1
                                           R1.2, R1.3,
NERC Std.
                                           R1.2
                            TOP-002-2
                            R5, R9

Approved by:                                 Effective Date: March 9, 2010
Version: 4                         Revision: 5


   Step         Action
                AEP TO in Corpus Christi is the DC Tie Operator for the Railroad, Eagle
                Pass DC- Ties and the Laredo VFT. The acronym for the Railroad tie is
  NOTE:         DC_R, the Eagle Pass tie is DC_S and the Laredo VFT is DC_L. All
                communications will be with the DC-Tie Operator. The DC-Tie Operator
                will communicate with CFE.
                Do not approve an E-Tag that crosses the midnight hour. We need one E-
  NOTE:         Tag per day in order for the schedules to transfer into the Market system
                correctly.
                ERCOT will not allow an E-Tag to flow from CFE to SPP or from SPP to
                CFE; this will require two separate E-Tags. E-Tags are not calculated in
  NOTE:
                our ACE equation, DC-Tie schedules are seen by our EMMS as a
                generator (import) or load (export)
                The Railroad DC-Tie has a 15 MW minimum flow requirement, if E-tags
  NOTE:
                are scheduled.
                Each time a new or updated E-Tag is submitted, the WebTrans system
                will automatically validate the E-Tag. WebTrans will display whether the
                E-Tag has passed or failed validation.
  NOTE:
                The criteria ERCOT uses to validate E-Tags is:

                        QSE Contract-A QSE ID must be entered into the ERCOT Market
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step    Action
                    Information field of the E-Tag.
                   QSE MW-A QSE‟s MOI schedule must be greater than or equal to
                    the associated E-Tag.
                 TP Required-ERCOT must be specified as a Transmission
                    Provider in the Physical Path of the E-Tag.
           Currently the validation criterion set to automatically deny an E-Tag is
           “QSE Contract” and “TP Required”. If either or both these validations
           fail the E-Tag will be automatically denied.

           If you feel an E-Tag failed validation erroneously, the list of approved
           ERCOT Registered QSE‟s can be found at the following website:

           http://www.ercot.com/mktparticipants/docs/QSEs.xls

           Select the DC Tie Scheduling List tab to view the ERCOT Registered
           QSE‟s. If the QSE name is on the list but was denied by WebTrans,
           approve the E-Tag and inform the OATI help desk.

           Another point of reference is to view the “QSE Contracts” in WebTrans.
           Each QSE is associated with each DC-Tie individually.

           WebTrans Reference Display:
           Tag Validation Monitor Summary
           When a new or updated E-Tag is received in the OATI WebTrans system:

           1.1 Determine if the following information is correct on the E-Tag:

                   Ensure “ERCO” is not listed as a PSE in the Physical Path
                   AEPT is included as a Transmission Provider (TP) in the physical
                    path and ERCO as a Scheduling Entity on the AEPT TP row in the
                    physical path.
                   There are no losses (MW) in the ERCOT Control Area. This
                    should be to or from AEPT as shown on the “Energy and
    1
                    Transmission Profiles” section.
                   Start/Stop times for a new E-Tag must be on the quarter hour (:00,
                    :15, :30, :45).

           If any of this information is incorrect on the E-Tag, deny the E-Tag,
           otherwise go to Step 1.2.

           1.2 Determine if one or more E-Tags being submitted will cause the DC
               Tie to exceed the import/export limit for the tie. If E-Tags are
               received in Day-Ahead then no import/export limits will have been
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step    Action
              posted yet, proceed to step 1.3

                   Call AEP TO in Corpus Christi to ensure they also see that the DC
                    Tie has exceeded the import/export limit for the tie.
                   Call the PSE to have the E-tag modified, if modification is not
                    done 20 minutes before the start of the ramp then;
                   Curtail the E-Tag(s) to the amount needed based on Last-in-first-
                    out (LIFO) until under the import/export limit for the tie.

           1.3 Determine if the E-Tag passed or failed validation.

                   If the E-Tag passes validation, go to Step 2.
                   If the E-Tag fails validation and the E-Tag is automatically denied
                    (QSE Contract), no further action is required.
                   If the E-Tag fails validation and the E-Tag is not automatically
                    denied (QSE MW), go to Step 2.

           WebTrans Reference Displays:
           Tag Validation Monitor
           Tag Validation Criteria
           Tag Approval Monitor
           QSE Summary
            The ramp rate for the Railroad DC-Tie will be 50 MW per minute due to
           reactive issues on the CFE side. Laredo and Eagle Pass DC-Ties will be
           ramped across a 10 minute window.
                Ensure the ramp duration is filled out on Railroad E-Tags only
    2
                Laredo and Eagle Pass ramp duration will remain blank

           Deny any Railroad DC-Tie E-Tag that does not have a ramp duration
           entered.
           The Railroad DC-Tie has a 15 MW minimum flow requirement. Ensure
    3
           the net of the E-Tags are not less than 15 MW.
           ERCOT will allow QSE‟s to submit E-Tags more than one (1) day in
           advance on the CFE DC-Ties. In these cases there will not be an
    4      associated schedule until the day-ahead. If a schedule is not received by
           1400 in the day-ahead, notify the QSE and remind them that a schedule is
           needed. If the schedule is not received by 2000, curtail the E-Tag to zero.
           Periodically refresh the QSE Summary display during the E-Tag approval
           timeline to determine if a QSE has submitted an MOI schedule.
    5
           When an MOI schedule has been received, compare the E-Tag to the
           schedule:
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step    Action


                   If the E-Tag is greater than the MOI schedule per 15 minute
                    interval, then the MOI schedule does not have enough generation
                    to cover the E-Tag. The “Mismatched” value box will be red and
                    the MW difference will be a negative amount. Deny the E-Tag.
                   If the E-Tag is less than the MOI schedule per 15 minute interval,
                    which means there is enough generation scheduled, the
                    “Mismatched” box will be yellow and the MW amount will be a
                    positive amount. Approve the E-Tag.
                   If the E-Tag equals the MOI schedule per 15 minute interval,
                    which means there is enough generation scheduled; the
                    “Mismatched” box will be green with a value of “0”. Approve the
                    E-Tag.

           WebTrans Reference Displays:
           QSE Summary
           Tag approval Monitor
ERCOT Operating Procedure Manual
Frequency Control Desk


         2.7.4   Adjustment of SPP DC Ties

         Procedure Purpose: The process to approve or deny adjustments to E-tags.

Protocol Ref.

Guide Ref.
                              INT-005-2       INT-006-2       INT-007-1       INT-008-2
NERC Std.
                              INT-009-1       INT-010-1

Approved by:                                   Effective Date: September 1, 2009
Version: 4                           Revision: 1


   Step          Action
                 Periodically refresh the QSE Summary display during the E-Tag
                 adjustment approval window to determine if a QSE has changed an MOI
                 schedule that is now making the E-Tag fail validation.

                         If the E-Tag is greater than the MOI schedule per 15 minute
                          interval, then the MOI schedule does not have enough generation
                          to cover the E-Tag. The “Mismatched” value box will be red and
                          the MW difference will be a negative amount. Deny the E-Tag.
                         If the E-Tag is less than the MOI schedule per 15 minute interval,
     1                    which means there is enough generation scheduled, the
                          “Mismatched” box will be yellow and the MW amount will be a
                          positive amount. Approve the E- Tag.
                         If the E-Tag equals the MOI schedule, which means there is
                          enough generation scheduled; the “Mismatched” box will be green
                          with a value of “0”. Approve the E-Tag.

                 WebTrans Reference Display:
                 QSE Summary
                 Tag Approval Monitor
                 E-Tag adjustments must be in an “Approved” or “Implemented” status to
  NOTE:
                 be calculated into the Net Schedule Interchange (NSI).
                 IF requested by the DC Tie Operator, checkout the Net Scheduled
                 Interchange (NSI) value for each DC Tie affected by E-Tag adjustments.
     2
                 WebTrans Reference Display:
                 Realtime Summary
ERCOT Operating Procedure Manual
Frequency Control Desk



         2.7.5   Curtailment of SPP DC Ties

         Procedure Purpose: The process to curtail E-tags for the SPP DC Ties.

Protocol Ref.

Guide Ref.
                            INT-005-2        INT-010-1       IRO-006-4
NERC Std.                   R1.1             R1              R5


Approved by:                                 Effective Date: March 9, 2010
Version: 4                         Revision: 1


   Step          Action
                 Curtailments are customarily scheduled for one hour at a time. Therefore
  NOTE:          a curtailment that occurs several hours in a row may require that this
                 procedure be repeated hourly.
                 When a curtailment alarm is received in WebTrans,
                  Approve the E-Tag curtailment.
     1
                 WebTrans Reference Displays:
                 Tag Validation Monitor
                 Tag Approval Monitor
                 If a QSE or SPP requests an E-Tag be curtailed or adjusted for any reason,
     2
                 curtail the E-Tag to 0 (zero).
                 E-Tag curtailments must be in an “Approved” or “Implemented” status to
  NOTE:
                 be calculated into the Net Scheduled Interchange (NSI)
                 IF requested by the DC Tie Operator, checkout the Net Scheduled
                 Interchange (NSI) value for each DC Tie affected by E-Tag curtailments.
     3
                 WebTrans Reference Display:
                 Realtime Summary
ERCOT Operating Procedure Manual
Frequency Control Desk


         2.7.6   Adjustments/Curtailment for the CFE DC Ties

         Procedure Purpose: The process to curtail E-tags for the CFE Ties.

Protocol Ref.

Guide Ref.
                              INT-005-2      INT-010-1
NERC Std.                     R1.1           R2


Approved by:                                  Effective Date: August 3, 2009
Version: 4                          Revision: 1


   Step          Action
                 Curtailments are customarily scheduled for one hour at a time. Therefore
  NOTE:          a curtailment that occurs several hours in a row may require that this
                 procedure be repeated hourly.
                 Import/export limits for the CFE DC Ties can change due to changes in
                 generation, transmission configuration, and other system conditions.
  NOTE:
                 After receiving the import/export limits for next day, it may be necessary
                 to have the PSE adjust E-tags and schedules.
                 When ERCOT curtails an E-Tag whether to zero (0) or a specific amount,
  NOTE:          only CFE needs to approve the change. Adjustments are done by the PSE
                 which requires all parties to approve.
                 If any of the DC-Ties trip, ERCOT will have the responsibility to curtail
                 the E-tags.
     1
                       Curtail the E-Tags
                       Instruct AEP Corpus to make notification to CFE to approve
                        curtailments
                 Once the DC-Tie that tripped is operational, re-load the curtailed E-Tag(s)

                         Re-load curtailed E-Tag(s)
     2
                         Instruct AEP Corpus to make notification to CFE to approve re-
                          loads

                 Once the import/export limits are posted around 1700, ensure the DC
                 Tie(s) are not overscheduled. If an over schedule is found:
     3
                         Notify the PSE to adjust the E-Tag(s) using the Last-in-
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step    Action
                   First-Out. If just one PSE is involved they may adjust their
                   E-Tags as they wish.
                Notify AEP Corpus with the E-Tag number(s) to approve
                   the adjustment(s)
                Instruct AEP Corpus to make notification to CFE to approve
                   adjustment(s)
           Due to ERCOT transmission issues it may be necessary for
           ERCOT to curtail E-Tags using the Last-in-First-Out (LIFO). If
           notified by the Transmission & Security desk that a curtailment is
           needed:

                   Curtail the appropriate E-tag(s), allowing enough time for
    4
                    CFE to approve; at least 20 – 30 minute notice is needed.
                   Notify AEP Corpus with the E-Tag number(s) that was
                    curtailed
                   Instruct AEP Corpus to make notification to CFE to
                    approve curtailment(s)

           ERCOT must declare an Emergency in order to cut E-Tags without
           notice. If an Emergency has been declared for a transmission issue
           and if notified by the Transmission & Security Desk that a
           curtailment is needed:

                   Contact AEP Corpus that curtailment(s) will be made and
                    to ramp the appropriate DC-Tie to the needed MW level.
                   Curtail the appropriate E-tag(s)
                   Notify AEP Corpus with the E-Tag number that was
                    curtailed
                   Instruct AEP Corpus to make notification to CFE to
    5               approve curtailment

           Typical script to AEP Corpus:
           This is ERCOT operator [first and last name]. ERCOT will be curtailing
           E-Tag(s) on the [DC-Tie name] DC-Tie. Please start ramping the Tie to
           [MW level], the E-Tag will be curtailed shortly. Please repeat this
           directive back to me. That is correct.”

           All directives shall be in a clear, concise, and definitive manner.
           Ensure the recipient of the directive repeats the information back
           correctly. Acknowledge the response as correct or repeat the original
           statement to resolve any misunderstandings.
    6      Due to CFE transmission issues it may be necessary for ERCOT to
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step    Action
           curtail E-Tags using the Last-in-First-Out (LIFO). If notified by
           AEP Corpus or the Transmission & Security Desk of CFE‟s
           situation:
                 Identify if at least 20 – 30 minute notice can be given for
                    curtailment of E-Tag(s), if notice can be given proceeded.
                    If curtailments need to take place immediately, proceeded
                    to Step 7.
                 Curtail the appropriate E-tag(s), allowing enough time for
                    CFE to approve; at least 20 – 30 minute notice is needed.
                 Notify AEP Corpus with the E-Tag number(s) that was
                    curtailed
                 Instruct AEP Corpus to make notification to CFE to
                    approve curtailment

           If notified by AEP Corpus or the Transmission & Security Desk of
           CFE‟s emergency situation:

                   Verify the appropriate DC-Tie is being ramped
                   Curtail the appropriate E-tag(s)
    7
                   Notify AEP Corpus with the E-Tag number(s) that was
                    curtailed
                   Instruct AEP Corpus to make notification to CFE to
                    approve curtailment

           If CFE does curtail schedules for their transmission issues:

                   Once curtailment is received from OATI, approve AND
    8
                   Notify AEP Corpus that they see the curtailment and will
                    ramp the Tie

           Once notified that transmission issues are resolved and E-tags can be re-
           loaded:

                   Re-load curtailed E-Tag(s)
    9
                   Ensure AEP Corpus sees the re-loaded E-Tags, AND
                   Instruct AEP Corpus to make notification to CFE to approve re-
                    loads
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7.7     Managing Daily Inadvertent Energy for the SPP DC Ties

      Procedure Purpose: To do before-the-fact and after-the fact checkouts for the
      SPP DC Ties.

Protocol Ref.

Guide Ref.
                           BAL-005-0.1b      INT-003-2      INT-009-1
NERC Std.                  R12.1             R1.2           R1


Approved by:                                Effective Date: March 9, 2010
Version: 4                        Revision: 2


    Step         Action
         Inadvertent Energy flows across the DC Ties need to be monitored
OVERVIEW frequently enough during the day to ensure that large inadvertent flows
         don‟t accumulate.
         If the proper information is not listed when a E-Tag is created and
         submitted, the E-Tag may not be displayed correctly in all WebTrans
  NOTE:  displays. Examples include, but are not limited to a PSE not using the
         proper POR/POD in the physical path (ERCOT-E, ERCOT-N) or if
         ERCOT is left off the E-Tag as a Scheduling Entity (SE).
                                       CAUTION
         If the E-Tag is created and submitted without any or all information in
CAUTION: the above NOTE OR any other circumstance so that the E-Tag can not
         be seen by either ERCOT or the DC Tie Operator, inadvertent energy
         will be created. The E-Tag should be curtailed to zero (0).
         When communicating with the DC Tie Operator:
  NOTE:
              Contact AEP Ohio TO for the North and East DC Ties
         Due to a deadband issue, if the net schedule on the North DC-Tie is less
         than 25 MW, the DC-Tie Operator has the option of:
  NOTE:
                    Automatically flow 25 MW out of ERCOT and into SPP, OR
                    Add MW flow in the direction of the schedule

                 Before the start of the hour, confirm the net-scheduled value for each DC
                 Tie with the DC Tie Operator. If there is a discrepancy, go over each
     1
                 E-Tag ID and MW amount for the affected DC Tie(s).
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step     Action
                    If an E-Tag cannot be seen in WebTrans OR by the DC Tie
                     Operator, work to resolve the problem OR ensure the E-Tag is
                     curtailed to zero (0).

            WebTrans Reference Displays:
            QSE Summary
            BTF Display
            Check out the Actual SCADA data values for the previous hour with the
            DC Tie Operator for each DC Tie.

                    If ERCOT‟s actual values are different from the DC Tie
                     Operator‟s actual values by less that 10 MWH, overwrite the
                     actual value in the WebTrans system.
                    If ERCOT‟s actual values are different from the DC Tie
                     Operator‟s actual values by 10 MWH or more and the reason is
                     known (database load, loss of ICCP, AEP automatically
                     overriding the schedule on the North DC Tie, etc.), overwrite the
                     actual value in the WebTrans system. Log the appropriate
                     information.
     2
                    If ERCOT‟s actual values are different from the DC Tie
                     Operator‟s actual values by 10 MWH or more and the reason is
                     unknown; ERCOT and the DC Tie Operator will initiate an
                     investigation. Log the appropriate information (time, date, total
                     MW difference, DC Tie, name of the DC Tie Operator and any
                     other relevant information). Also call the ERCOT Help Desk to
                     have a ticket opened for the EMMS Group to investigate
                     problems with the meter information.

            WebTrans Reference Displays:
            Tie Data
            ATF
            After midnight, each day, talk with the DC Tie Operator to check out the
            total scheduled and actual values for each DC Tie. If both parties agree
            on the Scheduled In and Out values and on the Actual In and Out values,
            select “Schedule” on the “Checkout” dropdown on the Filtering Options
     3      button so the “SC” column appears. Check the bottom box in Column
            SC and click the “Apply Checkout” button. Proceed to Step 5.

            WebTrans Reference Display:
            ATF
            If there is a disagreement on the total scheduled and/or actual values with
     4      the DC Tie Operator, verify the values for each hour as necessary to find
            the discrepancy. An effort should be made to workout all discrepancies
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step     Action


            If the discrepancy is with the scheduled values, email an Excel copy of
            the WebTrans Interchange Report display to check their information
            against ERCOT‟s.

                    Check the box for each hour that ERCOT is in agreement with
                     the DC Tie Operator for the scheduled value.
                    Leave the box unchecked for each hour where there is a
                     discrepancy with a scheduled value and it can not be worked out
                     with the DC Tie Operator. Click the “Apply Checkout” button.
                    If asked to change a scheduled value, log the appropriate
                     information and email it to the Manager of System Operations.

            If the discrepancy is with an actual value, change it to the DC Tie
            Operator‟s value.

            WebTrans Reference Displays:
            ATF
            Tie Data
            Create an Excel file for each of the North and East DC Ties and email it
            to the following:
     5           SPP DC-Tie Inadvertent
                 AEPTOWEST@aep.com
                 aepcheckout-west@aep.com
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7.8     Managing Daily Inadvertent Energy for the CFE DC Ties

      Procedure Purpose: To do before-the-fact and after-the-fact checkouts for the
      CFE DC Ties.

Protocol Ref.

Guide Ref.
                            BAL-005-0.1b    INT-003-2     INT-009-1
NERC Std.                   R12.1           R1.2          R1


Approved by:                                Effective Date: March 9, 2010
Version: 4                        Revision: 2


    Step         Action
          Inadvertent Energy flows across the DC Ties need to be monitored
OVERVIEW: frequently enough during the day to ensure that large inadvertent flows
          don‟t accumulate.
          If the proper information is not listed when an E-Tag is created and
          submitted, the E-Tag may not be displayed correctly in all WebTrans
          displays. Examples include, but are not limited to a PSE not using the
  NOTE:   proper POR/POD in the physical path (ROAD_DC, EGPS_DC, or
          LAR_VFT) or if ERCOT is left off the E-Tag as a Scheduling Entity
          (SE).

                                               CAUTION
                 If the E-Tag is created and submitted without any or all information in
 CAUTION:        the above NOTE OR any other circumstance so that the E-Tag can not
                 be seen by either ERCOT or the DC Tie Operator, inadvertent energy
                 will be created. The E-Tag should be curtailed to zero (0).
                 When communicating with the DC Tie Operator:
   NOTE:              Contact AEP Corpus Christi TSP for the Eagle Pass and
                         Railroad DC Ties, and the Laredo VFT.
                 Before the start of the hour, confirm the net-scheduled value for each
                 DC Tie with the DC Tie Operator. If there is a discrepancy, go over
                 each E-Tag ID and MW amount for the affected DC Tie(s).
      1
                         If an E-Tag cannot be seen in WebTrans OR by the DC Tie
                          Operator, work to resolve the problem OR ensure the E-Tag is
                          curtailed to zero (0).
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step      Action


             WebTrans Reference Displays:
             QSE Summary
             BTF Display
             Check out the Actual SCADA data values for the previous hour with the
             DC Tie Operator for each DC Tie.

                     If ERCOT‟s actual values are different from the DC Tie
                      Operator‟s actual values by less than 5 MWH, overwrite the
                      actual value in the WebTrans system.
                     If ERCOT‟s actual values are different from the DC Tie
                      Operator‟s actual values by 5 MWH or more and the reason is
                      known (database load, loss of ICCP, etc.), overwrite the actual
                      value in the WebTrans system. Log the appropriate information.
     2               If ERCOT‟s actual values are different from the DC Tie
                      Operator‟s actual values by 5 MWH or more and the reason is
                      unknown; ERCOT and the DC Tie Operator will initiate an
                      investigation. Log the appropriate information (time, date, total
                      MW difference, DC Tie, name of the DC Tie Operator and any
                      other relevant information). Also call the ERCOT Help Desk to
                      have a ticket opened for the EMMS Production Group to
                      investigate problems with the meter information.

             WebTrans Reference Displays:
             Tie Data
             ATF
             After midnight, each day, talk with the DC Tie Operator to check out
             the total scheduled and actual values for each DC Tie. If both parties
             agree on the Scheduled In and Out values and on the Actual In and Out
             values, select “Schedule” on the “Checkout” dropdown on the Filtering
             Options button so the “SC” column appears. Check the bottom box in
     3
             Column C and click the “Apply Checkout” button. No further action is
             required.

             WebTrans Reference Display:
             ATF
             If there is a disagreement on the total scheduled and/or actual values
             with the DC Tie Operator, verify the values for each hour as necessary
             to find the discrepancy. An effort should be made to work out all
     4       discrepancies

             If the discrepancy is with the scheduled values:
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step      Action
                     Check the box for each hour that ERCOT is in agreement with
                      the DC Tie Operator for the scheduled value.
                     Leave the box unchecked for each hour where there is a
                      discrepancy with a scheduled value and it cannot be worked out
                      with the DC Tie Operator. Click the “Apply Checkout” button.
                     Log the appropriate information and email it to the Manager of
                      System Operations.

             If the discrepancy is with an actual value, change our value to match the
             DC Tie Operator‟s value.

             Reference Displays:
             ATF
             Tie Data
             Create an Excel file for each of the CFE DC-Ties and email to the
             following:
     5
                         CFE DC-Tie Inadvertent
                         cenal.transaccionesinter@cfe.gob.mx
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7.9     Managing Inadvertent Energy Payback

      Procedure Purpose: To provide communication contacts and information prior
      to starting and ending inadvertent energy payback.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                Effective Date: August 3, 2009
Version: 4                        Revision: 1


    Step         Action
                 Payback will only be planned when there is room on the DC Tie(s).
                 Power schedules of market participants will supersede any inadvertent
   NOTE:         payback plan. Payback plans are implemented by the DC Tie Operator.
                 They will bias the DC Tie(s) and create inadvertent in the opposite
                 direction. This will reduce the inadvertent values.
                 When inadvertent needs to be paid back in either direction, the ERCOT
   NOTE:         Operator will receive the payback plan information from the Manager of
                 System Operations or designee
                 When communicating with the DC Tie Operator:
                  Contact AEP Ohio TO for the North and East DC Ties
   NOTE:
                  Contact AEP Corpus Christi TO for the Eagle Pass and Railroad DC
                     Ties, and the Laredo VFT.
                 Prior to the start of the Payback plan, call the appropriate DC Tie
                 Operator and confirm the start time, hourly MW amount, and direction
      1
                 of the payback plan. If payback is planned across the VFT, verify the
                 transmission path (230kV or 138kV).
                 Periodically check the WebTrans system to ensure that the inadvertent
                 values are decreasing. If they are not decreasing or are increasing, call
                 the DC Tie Operator to determine the reason.
      2
                 WebTrans Reference Display:
                 Daily Inadvertent
                 Prior to the Payback plan stopping, call the appropriate DC Tie Operator
      3
                 and confirm the agreed upon stop time.
ERCOT Operating Procedure Manual
Frequency Control Desk

      2.7.10 Loss of E-Tagging

      Procedure Purpose: Contingency plan for loss of E-tagging capability.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                Effective Date: July 15, 2009
Version: 4                        Revision: 0


    Step        Action
                If OATI goes down for an unknown reason (i.e. maintenance), contact
                the operator at the primary to check on their connectivity. If their
      1         system is also down, contact the OATI help desk to see if the issue is on
                their end. If issue is not on the OATI end, contact the ERCOT help
                desk.
                Determine the estimated down time, if longer than 30 minutes, notify
      2         the SPP Reliability Coordinator and the DC-Tie Operators.

                Post message on MIS:

      3         Typical Posting:
                “ERCOT ISO E-tagging is down; we are unable to accept new
                schedules across the DC-Ties at this time”.
                No new E-tags with be accepted, only curtailments required by SPP:

      4                 Coordinate with SPP and the appropriate DC-Tie Operator
                        Notify Operating Period desk to adjust off-set


   NOTE:        Before-the-fact and after-the-fact check outs will not be available

                Once OATI is available, confirm SPP and the DC-Tie Operators
                availability. If available for all parties:
      5
                     Update the MIS posting to “invalid”
                If curtailments were made while OATI was down, ensure E-tags are
                updated
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7.11 Emergency Energy across the CFE DC Ties

      Procedure Purpose: Steps to secure emergency energy across the CFE DC Ties.

Protocol Ref.

Guide Ref.
                           EOP-001-0      EOP-002-2.1     INT-010-1       IRO-005-2
                           R1, R3.1,      R1, R2, R4,     R3              R4
NERC Std.                  R7.2, R7.3     R6.1, R6.2,
                                          R6.4, R8


Approved by:                                Effective Date: July 15, 2009
Version: 4                        Revision: 2


    Step        Action
                ERCOT must declare a Watch or an emergency and make the proper
                posting/hotline call when receiving emergency energy from CFE,
   NOTE:        whether it is for transmission issues or an EEA situation. If CFE
                requests the emergency energy, no emergency notification needs to be
                declared.
                If there are E-tags that can be curtailed to alleviate the emergency
                situation, referred to Procedure 2.7.6, Step 5. When notified by Hotline
   NOTE:
                If in EEA situation, export E-tags should be curtailed first before
                emergency energy is received.
                When notified by Hotline that ERCOT has implemented an EEA level,
                proceed with this procedure
                When ERCOT is in need of the Emergency Energy:

                When notified by the Transmission & Security Desk of the need for
                emergency energy for a transmission issue or if in an EEA situation:

                        If there is import capacity room on the appropriate DC-Tie(s),
      1                  contact AEP Corpus and request that they contact CFE to see if
                         emergency energy is available
                        If emergency energy is available, determine the DC-Tie(s), MW
                         amount, time and duration (if possible),
                        Request AEP Corpus to ramp the appropriate DC-Tie with the
                         emergency energy
                        Issue AEP QSE a VDI for the emergency energy and to AEP
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step      Action
                    Corpus if requested
                 Forward VDI(s) to Shift Supervisor (fax) as time permits
             When CFE is in need of the Emergency Energy:
             The request will come from either the Transmission & Security Desk or
             AEP Corpus:

                     If there is export capacity room on the appropriate DC-Tie(s),
                      coordinated with the Transmission & Security Desk to ensure it
                      will not cause ERCOT transmission issues
     2
                     With no issues, determine the DC-Tie(s), MW amount, time and
                      duration (if possible)
                     Coordinate with Operating Period Desk
                     Issue AEP QSE a VDI for the emergency energy and to AEP
                      Corpus if requested
                     Notify AEP Corpus to ramp DC-Tie(s)
                     Forward VDI(s) to Shift Supervisor (fax) as time permits
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7.12 EEA 1 Schedule across the SPP DC Ties for EEA 1

      Procedure Purpose: Steps to secure a schedule across the SPP DC tie(s) in an
      Energy Emergency Alert 1.

Protocol Ref.

Guide Ref.
                          EOP-001-0        EOP-002-2.1      INT-010-1        IRO-005-2
                          R1, R3.1,        R1, R2, R4,      R3               R4
NERC Std.                 R7.2, 7.3        R6.1, R6.2,
                                           R6.4, R8


Approved by:                               Effective Date: November 2, 2009
Version: 4                       Revision: 3


    Step        Action

                Once notified by Hotline, the DC-Tie Operator at the alternate is
   NOTE:
                responsible for carrying out this procedure.
                Notify the SPP Reliability Coordinator of ERCOT‟s EEA 1 status.

                Typical Script:
      1
                “This is ERCOT operator [first and last name]. At [time], ERCOT
                declared EEA 1. We will contact the Tariff desk to inquire about the
                availability of transmission service, please transfer me.”
                Notify the SPP Tariff desk to determine the availability of transmission
                service across the SPP DC-Ties for an EEA 1 schedule.

                Typical Script:
                “This is ERCOT operator [first and last name]. At [time], ERCOT
                declared EEA 1. Is there transmission service available on either DC-
                Tie to start a schedule into ERCOT?”
      2
                If no current hour transmission service is available, do not proceed and
                make log entry. If status changes from EEA 1 to EEA 2A, 2B, or 3,
                proceed to Section 2.7.13

                If there is transmission service available continue with script:

                “I will be contacting AEP QSE to inquire about the availability of
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step      Action
             capacity not to exceed the transmission service available. Thank you.”

             SPP will contact PSEs with unscheduled reservations and notify them of
  NOTE:      ERCOT‟s EEA 1 status. PSEs may choose to use their reservation to
             schedule into ERCOT.
             Notify AEP QSE (AEP Generation Dispatchers):

             Typical Script:
             “This is ERCOT operator [first and last name]. At [time], ERCOT
             declared EEA 1. SPP Tariff desk reports there is [amount] of available
             transmission service on the East tie and [amount] of available
             transmission service on the North tie. Do you have any available
     3
             capacity up to that amount for an EEA 1 schedule?”

             If no available capacity, do not proceed and make log entry.

             If there is available capacity, ask AEP QSE to submit the transmission
             request and if approved submit the E-Tag(s) and proceed to step 4.
             Issue a VDI to QSE.
             Notify the DC Tie Operator of ERCOT‟s EEA status.

             Typical Script:
     4
             “This is ERCOT operator [first and last name]. At [time], ERCOT
             declared EEA 1. AEP QSE will be submitting the transmission request
             and if approved they will submit the E-Tag (s) for an EEA 1 schedule.
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7.13 Emergency Energy across the SPP DC Ties for EEA 2 or 3

      Procedure Purpose: Steps to secure emergency energy across the SPP DC tie(s)
      in an Energy Emergency Alert 2A, 2B or 3.

Protocol Ref.

Guide Ref.
                          EOP-001-0       EOP-002-2.1     INT-010-1       IRO-005-2
                          R1, R 3.1,      R1, R2, R4,     R3              R4
NERC Std.                 R7.2, R7.3      R6.1, R6.2,
                                          R6.4, R8


Approved by:                               Effective Date: July 15, 2009
Version: 4                       Revision: 2


    Step        Action

                Transmission Service is only good for an hour at a time. Keep AEP
   NOTE:
                informed so they can make the proper submittals hour to hour.
                If ERCOT goes directly to an EEA 2A, 2B or 3 OR if an EEA 1
   NOTE:
                schedule was unsuccessful, proceed with the steps below.
                Notify the SPP Reliability Coordinator or ERCOT‟s EEA status

                Typical Script:
      1
                “This is ERCOT operator [first and last name]. At [time], ERCOT
                declared EEA [2 or 3]. We will contact the Tariff desk to inquire about
                the availability of emergency transmission service, please transfer me.”
                Notify the SPP Tariff desk to determine the availability of emergency
                transmission service across the SPP DC-Ties.

                Typical Script:
                “This is ERCOT operator [first and last name]. At [time], ERCOT
                declared EEA [2 or 3]. Is there emergency transmission service
      2         available across the DC-Tie(s)?”

                If not available, do not proceed and make log entry.

                If there is emergency transmission service available continue with
                script:
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step      Action
             “I will be contacting AEP QSE to inquire about the availability of
             capacity not to exceed the emergency transmission service available.
             Thank you.”
             ERCOT must have the Reliability Coordinator Information System
  NOTE:      (RCIS) updated with the EEA 2 or 3 status before SPP grants
             emergency transmission service.
             SPP will curtail all non-firm transmission service schedules going out of
  NOTE:
             ERCOT.
             Notify AEP QSE (AEP Generation Dispatchers).

             Typical Script:
             “This is ERCOT operator [first and last name]. At [time], ERCOT
             declared EEA [2 or 3]. SPP Tariff desk reports there is [amount] of
             available emergency transmission service on the East tie and [amount]
             of available emergency transmission service on the North tie. Do you
     3
             have any available capacity up to that amount for emergency
             assistance?”
             If no available capacity, do not proceed and make log entry.

             If there is available capacity, ask AEP QSE to submit the transmission
             request and if approved submit the E-Tag(s). Proceed to step 4. Issue a
             VDI to QSE.
             Notify AEP DC-Tie Operator of ERCOT‟s EEA status:

             Typical Script:
     4
             “This is ERCOT operator [first and last name]. At [time], ERCOT
             declared EEA [2 or 3]. AEP QSE will be submitting the transmission
             request and if approved they will submit the E-Tag(s).”
  NOTE:      Keep SPP informed of ERCOT‟s status.
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7.14 Backing out of EEAs and Termination

      Procedure Purpose: Steps to back out off and terminate schedules and/or
      emergency energy across the SPP DC ties.

Protocol Ref.

Guide Ref.
                         EOP-001-0
NERC Std.
                         R1

Approved by:                              Effective Date: July 15, 2009
Version: 4                      Revision: 1


    Step        Action
                When moving EEA status:

                Notify the SPP Reliability Coordinator of ERCOT‟s status.
      1
                Typical script:
                “This is ERCOT operator [first and last name]. At [time], ERCOT
                moved from EEA [3 or 2] to EEA [2 or 1]. We will notify the Tariff
                desk, please transfer me. Thank you.”
                Notify the SPP Tariff desk of ERCOT‟s EEA status.

                Typical Script:
      2
                “This is ERCOT operator [first and last name]. At [time], ERCOT
                moved from EEA [3 or 2] to EEA [2 or 1]. We will notify AEP. Thank
                you.”
                Notify AEP QSE (AEP Generation Dispatchers). Transmission Service
                is only good for an hour at a time. Keep AEP informed so they can
                make the proper submittals hour to hour.
      3
                Typical Script:
                “This is ERCOT operator [first and last name]. At [time], ERCOT
                moved from EEA [3 or 2] to EEA [2 or 1]. We believe this emergency
                [will or will not] continue into the next hour. Thank you.”
                Notify AEP DC-Tie Operator of ERCOT‟s EEA status.

      4         Typical Script:
                “This is ERCOT operator [first and last name]. At [time], ERCOT
                moved from EEA [3 or 2] to EEA [2 or 1]. We believe this emergency
ERCOT Operating Procedure Manual
Frequency Control Desk


   Step      Action
             [will or will not] continue into the next hour. Thank you.”
             Repeat above steps with the notifications until ERCOT‟s status is EEA
  NOTE:
             0 (zero).
ERCOT Operating Procedure Manual
Frequency Control Desk


      2.7.15 Fast Start Emergency Energy to SPP

      Procedure Purpose: Steps to provide emergency assistance to Southwest Power
      Pool across the SPP DC ties.

Protocol Ref.

Guide Ref.
                         EOP-001-0
                         R1, R7.2,
NERC Std.
                         R7.3


Approved by:                              Effective Date: July 15, 2009
Version: 4                      Revision: 2


    Step        Action
                Every effort should be made to render assistance during emergency
                conditions.
   NOTE:

                SPP will notify ERCOT that emergency assistance is needed.
                VERIFY that providing emergency assistance to SPP will not put
      1
                ERCOT in an insecure state, or worsen an existing insecure state.
                SPP will contact the DC Tie Operator and arrange to maximize the DC
                tie output into SPP. It is not necessary to confirm that an emergency
   NOTE:
                condition has been posted in the Reliability Coordinator Information
                System (RCIS). SPP may need to act before the RCIS is updated.
                Notify the Operating Period Desk to adjust the Offset to minimize the
      2
                use of Regulation.
                When possible:
                 Contact AEP QSE and instruct them to create and submit an E-Tag
      3             for the emergency assistance (this can be done after-the-fact but
                    within an hour of the event).
                 Issue a VDI to AEP QSE for the emergency assistance.
ERCOT Operating Procedure Manual
Frequency Control Desk


        2.8     Outages

        2.8.1   Maintenance Level 2 & 3 Outages

        Procedure Purpose: Process level 2 and 3 maintenance outages in the Outage
        Scheduler.

Protocol Ref.

Guide Ref.

NERC Std.

Approved by:                                 Effective Date: May 1, 2009
Version: 4                         Revision: 0


   Step         Action
                Maintenance Level 2 and 3 outages are coordinated with the ERCOT
                Outage Coordination Group. These outages should not be “accepted” by
 NOTE:          anyone other than that group. However, until they are accepted in the
                Outage Scheduler, they will continue to show up every time the Outage
                Scheduler refreshes (that is about every two minutes).
                DO NOT check the “accept” box for Maintenance Level 2 and 3 Outages
                in the Outage Scheduler.
    1
                Instead, place those Maintenance Level 2 and 3 outages in “Study” status
                and notify the Outage Coordination group of the Maintenance Level 2 or 3
                Outage, by email to “OPS Outage Coordination” distribution list.