Docstoc

ercot_2012_seminar___nodal_outage_scheduling

Document Sample
ercot_2012_seminar___nodal_outage_scheduling Powered By Docstoc
					Importance of accurate and
 timely outages information


   Robert Matlock/Darrell Jenkins
  Supervisor’s Outage Coordination
       Long Term/Short Term

                                     1
               Objectives
• Identify the timelines for submitting
    outages
•   Identify the importance of entering
    accurate outage information in a timely
    manner
•   Describe how the Forced Outage Detector
    works and how it is used in real-time


                                          2
                   Acronyms
• CRR – Congestion Revenue Rights
• FOD – Forced Outage Detector
• OS – Outage Scheduler
• PTP – Point to Point
• RUC – Reliability Unit Commitment
   • DRUC – Daily Reliability Unit Commitment
   • HRUC – Hourly Reliability Unit Commitment
• SARA – Seasonal Assessment of Resource Adequacy
• SCED – Security Constrained Economic
              Dispatch
•   TO – Transmission Operator
•   TOAP – Temporary Outage Action Plan
                                                    3
                      Definitions
•   Planned Outage - An Outage that is planned and
    scheduled in advance with ERCOT, other than a Maintenance
    Outage or Opportunity Outage.
• Forced Outage - An Outage initiated by protective relay, or
    manually in response to an observation by personnel that the
    condition of equipment could lead to an event, or potential
    event, that poses a threat to people, equipment, or public safety.

    For a Generation Resource, an Outage that requires immediate
    removal, either through controlled or uncontrolled actions, of all
    or a portion of the capacity of the Resource from service through
    automated or manual means. This type of Outage usually
    results from immediate mechanical/electrical/hydraulic control
    system trips and operator-initiated actions in response to a
    Resource’s condition.

                                                                         4
               Definitions (continued)
•   Maintenance Outage - An Outage initiated manually to
    remove equipment from service to perform work on components
    that could be postponed briefly but that is required to prevent a
    potential Forced Outage and that cannot be postponed until the
    next Planned Outage. Maintenance Outages are classified as
    follows:
     • Level 1 Maintenance Outage – Equipment that must be removed from
         service within 24 hours to prevent a potential Forced Outage;
     •   Level II Maintenance Outage – Equipment that must be removed from
         service within seven days to prevent a potential Forced Outage; and
     •   Level III Maintenance Outage – Equipment that must be removed from
         service within 30 days to prevent a potential Forced Outage.




                                                                               5
   Outages – Zonal to Nodal

• The average number of outage requests per year in
  the Zonal Market was in the 30,000 range
• For Nodal we had over 100,000 outage requests in
  2011.
   • Processing between 500 and 600 new outage
     request a day during the peak months.
      • Spring - Feb, Mar, Apr
      • Fall – Sep, Oct, Nov




                                                      6
                            Number of Outages




                               0
                             100
                             200
                             300
                             400
                             500
                             600
                             700
                             800
                             900
                           1,000
                           1,100
                           1,200
                           1,300
                           1,400
                           1,500
                           1,600
                           1,700
                           1,800
                           1,900
                           2,000
                           2,100
                           2,200
                           2,300
                           2,400
                           2,500
                           2,600
                           2,700
                           2,800
                           2,900
                   01/01
                   01/08
                   01/15
                   01/22
                   01/29
                   02/05
                   02/12
                   02/19
                   02/26
                   03/05
                   03/12
                   03/19
                   03/26
                   04/02
                   04/09
                   04/16
                   04/23
                   04/30
                   05/07
                   05/14
                   05/21
                   05/28
                   06/04
                   06/11




Year 2011
                   06/18
                   06/25
                   07/02




            DATE
                   07/09




Year 2010
                   07/16
                   07/23
                   07/30
                   08/06
                   08/13
                   08/20
                   08/27
                   09/03
                   09/10
                   09/17
                   09/24
                   10/01
                   10/08
                   10/15
                   10/22
                   10/29
                                                    per day for 2010 and 2011




                   11/05
                   11/12
                   11/19
                   11/26
                   12/03
                   12/10
                   12/17
                   12/24
                   12/31
7
                                                Comparison of the number of outages
Outage Timelines




                   8
Timeline for Resource Planned
           Outages
 If QSE submits
 outage                    ERCOT will approve or reject…
 request…
                     Within 8 business hours of receipt by
1-2 days prior
                     ERCOT
                     Before 1800 hours, 2 days
3-8 days prior
                     prior to start of proposed Outage
                     Must accept, but may discuss reliability
8+ days prior        and scheduling impacts to minimize
                     hazards/costs
     (note: this will change with the implementation of
                          NPRR365)
                                                                9
    Timeline for Reliability Resource
           Planned Outages
Amount of time between a Request
for approval of a proposed Planned    ERCOT shall approve or
Outage and the scheduled start date   reject no later than:
of the proposed Outage:


                                      15 days before the start of the
       No less than 30 days
                                            proposed Outage

                                      30 days before the start of the
       Greater than 45 days
                                            proposed Outage


                                                                  10
Timeline for Resource Maintenance
              Outages

Forced and Levels I, II, and III Maintenance Outage are
accepted but ERCOT can coordinate the Outages within
the time frames specified in these Protocols.




                                                     11
    Timeline for Reliability Resource
        Maintenance Outages

Amount of time between a Request
for approval of a proposed Outage     ERCOT shall approve or
and the scheduled start date of the   reject no later than:
proposed Outage:

    Maintenance Outage Level I                 Immediate
                                      0000 hours, 2 days before the
       Between 3 and 8 days
                                      start of the proposed Outage
                                      4 days before the start of the
      Between 9 and 30 days
                                           proposed Outage


                                                                  12
Timelines for Transmission Facility
   Planned Outage Requests

  If TSP submits outage      ERCOT will approve or
  request…                   reject…
     90+ days             75 days

    46–90 days            30 days

     9–45 days            4 days

     4–8 days             No later than 1800 hours 3 days

       3 days             No later than 1800 hours 2 days


                                                            13
    Timelines for Transmission Facility
      Maintenance Outage Requests
                   Minimum amount of
                                                      Minimum amount of time
                   time between the
                                                      between any change to an
  Type of          Outage request and
                                                      Outage request and the
  Outage           the scheduled start
                                                      scheduled end date an
                   date of the proposed
                                                      existing Outage:
                   Outage:
Maintenance
Outage Level                Immediate                             Immediate
      I
Maintenance
Outage Level                 2 days [1]                            2 days [1]
     II
Maintenance
Outage Level                  3 days                                 3 days
     III
Note: 1 For reliability purposes, ERCOT may reduce to one day on a case-by-case basis.
                                                                                         14
Why accurate and timely outage
   information is important




                                 15
        ERCOT Responsibilities

• Approve or reject outage requests
• Review and coordinate rolling 12-month plan
• Post proposed and approved Transmission outages
• Monitor outages of immediate nature and
  implement responses
• Establish and implement communication
  procedures
• Produce outage reports




                                                    16
    TSP and QSE Responsibilities


QSEs and TSPs will submit complete information about
outage schedules in the Outage Scheduler and use the
Outage Scheduler tool as needed to keep the information
up to date, according to established submittal and timing
requirements defined in the Nodal Protocols.




                                                            17
               What Outages Impact
                    Outage Coordination


                        Congestion
                      Revenue Rights


                       Gap Studies

Transmission                              Resource
                        Day-Ahead
   Outages                                Outages


                    Adjustment Period


                        Real-Time


                      Post Real Time

                                                     18
         Outage Coordination

• Both Transmission and Resource outages are
  incorporated in the studies
   • Multiple point in time studies
   • Power Flow
   • Contingency Analysis
• Used to Approve/Accept or Reject new outage
  requests or to Withdraw Approved outages if
  system conditions change and reliability show to
  be compromised



                                                     19
Congestion Revenue Rights

        • CRR Awards
        • PTP Awards

         Monthly CRR
       Annual CRR Market




                            20
    Congestion Revenue Rights (cont)
Monthly CRR Market – Approved and Accepted
  Transmission Outages are pulled 45 days prior to the
  monthly auction
   • Greater than 90
      • Approved 75 days before the Planned Start
   • 46 to 90
      • Approved 30 days before the Planned Start


Annual CRR Market – Approved and Accepted
  Transmission outage are pulled 5 months prior to the
  annual auction


                                                         21
              Gap Studies
(the time between when Planned Transmission outages can be
   submitted and real time)

• Both Transmission and Resource outages are
  incorporated in the studies
   • Take into account any new Forced or Maintenance
     outages
   • Incorporates a better load forecast
• Used to Approve Transmission Maintenance
  outage requests
• Used to Withdraw outages if system conditions
  change and reliability is compromised

                                                             22
          Day Ahead and Adjustment Period
       Outages are used every hour of the day, even in the preceding day
           for many hours
              HRUC runs each hour
0000
 0100
   0200



                              Day 1                                      Day 2


                        1000                                   Day-Ahead Market OpDay
                      DAM runs
                                        1430                  Day-Ahead RUC Study Period
                                      DRUC runs


                 After DRUC completes      1800
                 HRUC runs each hour of      1900
                 current and next day


                                                    0000
                                                     0100
                                                       0200

                                                                                           23
               Real-Time


• Forced Outage Detection
  Looks at both Approved or Accepted Transmission
  and Resource outages as well as COP




                                                    24
             Post Real Time
• Planning
  • SARA - Uses historic Resource outages for future
    statistical seasonal system adequacy
• Outage Reports
  • Resource Monthly Planned Vs Actual
  • Resource Annual Planned Vs Actual




                                                   25
           Post Real Time (cont)
• Audits
  •   FERC
  •   NERC                • Feb 2
  •   TRE
  •   IMM


• Settlements
  • RUC Make-Whole




                                    26
Forced Outage
Detection (FOD)




                  27
         Forced Outage Detector
• A new tool for Nodal
• Runs every 10 seconds
• Detect status changes based on associated breaker and
  switch status changes for the following Transmission
  Facilities
   • Resources
   • Transmission lines
   • Transformers
   • Loads
• Identify forced outages of Transmission Facilities
• Produce alarms for ERCOT Operators in real-time at
  same frequency as SCADA telemetry processing
                                                      28
                      FOD (Continued)
         FOD Inputs                          FOD Outputs
 Breaker & Switch
  Status (SCADA)


     Planned &
Maintenance Outages
        (OS)                                      Forced Outages
                                                      Display
  Existing Forced            Forced Outage
   Outages (OS)                 Detector          Status Change &
                                                   Forced Outage
                                                       Alarm
 Planned Resource
    Status (COP)


Network Operations
      Model
                                                             29
               FOD (Continued)

ERCOT Operator may request that QSE or
TO:
  • Correct the breaker and/or switch
    status indication causing the alarm
  • Enter an Unavoidable Extension, Forced
    Outage or Forced Extension into the Outage
    Scheduler



                                                 30
Future Changes




                 31
Current Timeline for Resource
     Planned Outages
 If QSE submits
 outage                    ERCOT will approve or reject…
 request…

1-2 days prior       Within 8 business hours of receipt*

                     Before 1800 hours, two days
3-8 days prior
                     prior to start of proposed Outage
                     Must accept, but may discuss reliability
8+ days prior        and scheduling impacts to minimize
                     hazards/costs
     (note: this will change with the implementation of
                          NPRR365)
                                                                32
   Future Timeline for Resource Planned
             Outages (NPRR365)
Amount of time between a request
for acceptance of a Planned Outage     ERCOT shall approve, accept or reject no
and the scheduled start of the         later than:
proposed Outage:
                                        ERCOT shall approve or reject within 1800
          Three days                       hours, two days before the start of the
                                                      proposed Outage
                                        ERCOT shall approve or reject within 1800
  Between four and eight days             hours, three days prior to the start of the
                                                      proposed Outage
                                     Five Business Days after submission. Planned
                                         Outages are automatically accepted if not
   Between nine and 45 days
                                       rejected at the end of the fifth Business Day
                                                following receipt of request.
                                      ERCOT must accept, but ERCOT may discuss
                                     reliability and scheduling impacts to minimize
                                        cost to the ERCOT System in an attempt to
     Greater than 45 days             accomplish minimum overall impact. Within
                                         five Business Days, ERCOT will notify the
                                     submitter if there is a conflict with a previously
                                                     scheduled Outage.
                                                                                   33
                 Summary

Identify the Timeline for entering outage
 requests
Recognize the importance of entering accurate
 outage information in a timely manner
Have an understanding of how the Forced
 Outage Detector works and how it is used



                                                 34
Questions


            35

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:8/1/2012
language:English
pages:35