Balancing Authority ACE Limit Proof-of-Concept Field Trial Project

Transcription

1 Balancing Authority ACE Limit Proof-of-Concept Field Trial Project WECC Update Discussion April 10, 2012 DISCUSSION STARTING AT 3:30 PM EDT Brian Van Gheem - MISO Balancing Authority Reliability-based Control Standard Drafting Team (BARCSDT)

2 Balancing Authority ACE Limit Proof-of-Concept Field Trial Western Interconnection Field Trial Participation Participation reflects approximately xx% of the projected 2010 peak load for the Western Interconnection

3 Clock-Minute Frequency Below Hz FTL Low Prevailing Time PTimeZone FreqError ActualFreq SchedFreq 02/06/ :04 MST

4 Clock-Minute Frequency Above Hz FTL High Prevailing Time PTimeZone FreqError ActualFreq SchedFreq NONE

5 Balancing Authority ACE Limit Proof-of-Concept Field Trial The Balancing Authority ACE Limit (BAAL) shall not be exceeded for more than 30 consecutive clock-minutes* MinCtLow BAAL Low BAAL High BAAL Low BAAL High BAAL Low BAAL High BAAL Low BAAL High BA Number MinCtLow MinCtHigh MinCtLow2 MinCtHigh2 MinCtLow MinCtHigh LowLimitCt HighLimitCt BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA BA = Count of consecutive clock-minutes BAAL Low was exceeded MinCtHigh = Count of consecutive clock-minutes BAAL High was exceeded MinCtLow2 = Count of consecutive clock-minutes BAAL Low was exceeded MinCtHigh2 = Count of consecutive clock-minutes BAAL High was exceeded *BAAL being exceeded for more than 30 consecutive clock-minutes would be a violation under the draft BAAL standard.

6 Statistics of BAAL being exceeded > 25 consecutive clock-minutes : Date Time Time Zone Actual Freq Sched Freq MinCtLow MinCtHigh CPS1 ACPS1 MinCtLow2 MinCtHigh2 LowLimitCt HighLimitCt 2/27/ :41 MST /27/ :42 MST /27/ :43 MST /27/ :44 MST /27/ :45 MST /27/ :46 MST /27/ :47 MST /27/ :48 MST /27/ :49 MST /27/ :50 MST /27/ :51 MST /27/ :52 MST /27/ :53 MST

7 Examples in this Presentation Example# Type #mins Sched Freq Start Time Time Zone Stop Time Time Zone 1 BAAL High /27/12 22:26 MST 2/27/12 22:53 MST

8 EXAMPLE 1

9 02/27/2012 ending 22:53 MST 28-minute duration above BAAL High EI Clock-Minute Average Frequency FTL Frequency (Hz) FTL Clock-minute Actual Frequency of Participants

10 02/27/2012 ending 22:53 MST 28-minute duration above BAAL High 3000 ACPS1 Clock-Minute Averages ACPS1 CF (%) BAAL Adjusted CPS1 of individual BAs under the Field Trial

11 02/27/2012 ending 22:53 MST 28-minute duration above BAAL High 30 Consecutive Minutes Exceeding BAAL BAAL shall not be exceeded for more than BAAL Violation* 30 consecutive clock-minutes * 25 Consecutive Minutes Exceeding BAAL *BAAL being exceeded for more than 30 consecutive clock-minutes would be a violation under the proposed standard.

12 Balancing Authority ACE Limit Proof-of-Concept Field Trial Examples of circumstances when BAAL was exceeded and actions taken if appropriate On a monthly basis, each Balancing Authority will review its performance for the prior month and identify any periods where the ACE exceeded the low BAAL ( BAAL Low ), the high BAAL ( BAAL High ), the low ATL or high ATL for more than 30 consecutive clock-minutes. To help the RBCSDT gain a better understanding of the circumstances that all Balancing Authorities may be faced while operating under BAL-007, each Balancing Authority will provide a brief explanation of the circumstances related to any periods where the duration of consecutive clock-minutes exceeded 30 minutes. In the event that no period exceeded 30 minutes in the prior month, but the longest duration exceeded 25 minutes, the Balancing Authority will provide a brief explanation of the circumstances related to that longest-duration event. Limit Exceeded (Enter one of the following: BAAL high, BAAL low, ATL high, ATL low) Clock-minute of ACE exceeding the BAAL or ATL (mm/dd/yy hh:mm) Clock-minute of ACE returning within the BAAL or ATL (mm/dd/yy hh:mm) TimeZo ne Total duration of ACE exceeding the BAAL or ATL (minutes) Event associated with a DCS- Reportable Event? (0=No, 1=Yes) Event associated with a resource loss other than a DCS- Reportable Event? (0=No, 1=Yes) Brief explanation of circumstances and notable actions taken if applicable BAAL HIGH 2/27/12 22:26 2/27/12 22:54 MST Wind speed increased intra-hour causing generation to increase with frequency trending above 60 Hz. Forecast did not indicate an increase in wind speed. Operator deployed dec resources, but wind speed continued to increase, so operator initiated measures to cap turbine output to return ACE to zero.

13 Balancing Authority ACE Limit Proof-of-Concept Field Trial Project Discussion Brian Van Gheem - MISO Balancing Authority Reliability-based Control Standard Drafting Team (BARCSDT) bvangheem@misoenergy.org