PJM©2009 1 PJM DOCs # Frequency Response Drafting Team Frequency Response Background Frequency...

PJM©20091PJM DOCs #

Frequency Response Drafting Team

• Frequency Response Background• Frequency Response Standard History• Briefing on Frequency Response Meeting (8/28)• Data Request• Next Steps

1


History

• Resources Subcommittee (RS) has been tracking frequency response with help of ad hoc “spotters” for several years

• Based on concern on trends, RS posted a draft of the FRS in 2001 with a revised Policy 1

• SAR posted in 2002 • Submitted an alternative Common Balancing Data SAR • Whitepaper prepared and SAR posted in 2005, 2006, 2007

2


4

Frequency Response Basics

• Frequency Response, termed beta (β), is– a fundamental reliability service– a combination of governor and load response

• Following a sudden generator (or load loss)– β stabilizes frequency at a new point– Frequency does not return to 60 Hz until the contingent Balancing Authority replaces

the loss • There is confusion on the requirements of BAL-003

– Some believe there is a minimum required β in the standard– The Resources Subcommittee (author of the standard and its predecessor) disagrees

• FERC Order No. 693 directs improved calculation and determination of need for a performance obligation


Classifications - Time Frame - Measures


Excursion Recovery

A = 60.000

C = 59.812

B = 59.874

59.750

59.775

59.800

59.825

59.850

59.875

59.900

59.925

59.950

59.975

60.000

60.025

60.050

-30 0 30 60 90 120 150 180 210 240 270 300 330 360 390 420

Time (Seconds)

Frequency (Hz)

Recovery Completed, TV


Interconnections Depicted on same Axis


Frequency response is always the same through out the year or is it?


How to use differing scan rate supplied values to apply a standard technique


Standardized calculation method of frequency response


ERCOT MethodDate/Time MW Loss MW/0.1 Hz MW/0.1 Hz MW/0.1 Hz

Point B Point B+30 FRSSDT10/23/07 19:24 612.2 580.2 398.2 637.5

10/29/07 9:50 587.5 595.0 614.0 580.911/2/07 9:17 624.2 624.2 1047.0 828.9

11/13/07 16:19 583.0 612.9 633.1 537.611/23/07 17:26 633.0 469.2 381.8 382.1

11/29/07 6:35 343.5 489.6 379.6 316.812/5/07 10:45 343.5 1054.3 835.5 774.6

12/10/07 11:23 521.6 614.0 687.8 684.012/12/07 1:48 1026.5 453.5 420.9 537.012/19/07 8:51 656.9 547.4 581.3 517.7

1/20/08 8:39 326.9 294.1 320.6 276.82/3/08 15:23 781.9 555.0 503.1 548.2

2/8/08 5:03 472.4 1368.8 1861.7 1268.22/19/08 3:05 723.9 580.6 580.6 551.0

2/20/08 22:59 384.1 843.2 1084.0 824.93/3/08 10:08 497.1 474.6 554.6 448.2

3/4/08 4:14 549.5 599.7 519.0 471.73/9/08 20:30 530.9 557.9 504.2 541.73/13/08 9:16 559.3 642.8 625.3 654.6

3/16/08 11:37 570.0 508.9 703.7 578.53/30/08 8:33 501.2 359.2 342.9 348.8

4/3/08 9:24 740.3 650.2 637.6 783.94/10/08 3:47 1078.4 560.6 695.3 632.0

4/17/08 13:26 552.3 582.5 928.1 674.54/23/08 13:08 587.0 745.6 953.3 675.94/24/08 10:13 557.5 775.1 928.6 747.9

5/26/08 2:36 552.3 489.2 629.8 517.36/22/08 18:29 564.3 930.1 1431.0 1392.76/24/08 16:48 530.0 815.4 868.9 679.9

Average 633.6 712.1 634.9

ERCOT experience using the FRSSDT method – similar outcome on response


Comparing March 2009 vs November 2008 profile of frequency in 5 mHz bins

0

0.01

0.02

0.03

0.04

0.05

0.06

0.07

0.08

0.09

Mar-09Nov-08


Comparing April 2009 vs November 2008 profile of frequency in 5 mHz bins

0

0.01

0.02

0.03

0.04

0.05

0.06

0.07

0.08

0.09

Apr-09Nov-08

ERCOT Frequency Profile – Nov 2008 – 4 base load super critical units providing governor support @ +/- 1 rpm – on outage in April


RS/FRSDT (Sept 09)

• Seek OC Concurrence to Pilot Voluntary Data Collection– Utilize annual 2010 Bias calculation as “Phase 1” – Utilize ACE data for centralized verification calculation –(pilot with voluntary data from

BRDSDT already provided) *– Support web-based reporting tool for unit trip data *

• Seek Standards Committee endorsement• Draft Formal Scope for Phase 2 (generator level data for low responders) for OC

consideration in 1st quarter 2010• Frequency Response Reference Document by December 2009• Refine data requirements based on Phase 1 data submissions• Report on need for Section 1600 Request to OC March 2010 • If needed, mandatory collection would begin July 1, 2010

14

* May require some development expenditures


• Background

• Three levels of data needed in this process:• Interconnection• Benchmark Trends• Validate net BA performance• Balancing Authority• Sound Bias calculation• Identify areas and reasons for lower response• Generator • For BAs with lower response•


•Goals of Voluntary Data Collection

•Provide valid data for FRS drafting team

•Minimize impact on entities providing data

•Simple as possible

•Ride on existing processes


BalancingAuthorities

RS Frequency Task Force

Define pointsA, B and selectEvents for analysis

Step 1:Enter events

750 MW – EI & WI500 MW ERCOT

(monthly)

NERC-FMA1-Second

FrequencyPhasor Data

CERTS

Step 2:Call

Survey

NERC Central site

Monthly EventCollection

VOLUNTARY FRRSDT EVENT DATA REQUEST – INTERIM AND TARGET PROCESSES

Rev:11.23.09

InterimProcess

TargetProcess


Phase 1 Data Collection (2010)Interconnection Benchmarking

U0 code created in GADS to capture unit trip dataUse Quarterly DCS report to gather unit trips > 750 MW (current reporting

threshold is 1000MWMinor change to CERTS Frequency Monitoring application to

automatically create an event database Balancing Authority Data

Use annual bias calculation spreadsheet (calculation already required, BAs have been provided a tool to do this for 2010 bias calculation)

Implement a tool that calculates frequency response from monthly data that is already collected for the Reliability-Based Control standard

Implement a minor change to the CERTS Frequency Monitoring Application that calculates BA frequency response from ICCP ACE data already streamed to NERC Supporting ToolsFRSDT and RS develop and post tools that BAs can use to analyze their performance and that of their generators.

This is a field trial for tools that may be implemented in 2011Modified based on comments in the FRS drafting team effort


BalancingAuthorities

RS Frequency Task Force

Define pointsA, B, and C

Step 2 Call SurveySelect Events within a quarter NERC-FMA

1-Second Frequency

Phasor Data

CERTS

Call Survey

Central site

SurveyCollection &Calculations

FRSDT

EventAnalysis

Reports

VOLUNTARY FRRSDT DATA REQUEST – INTERIM AND TARGET PROCESSESRev:11.23.09

InterimProcess

Respond Survey – scan rate data

Survey count should be selecting approximately 3 per month

NERC Central site

Monthly EventCollection


1) Governor droop setting. (5%, 4% or other)2) Governor deadband setting. (Expressed in Hz, 0.035 Hz, 0.017 Hz etc.)3) Pmax MW of the Resource, both nameplate and during the event.4) Type of resource, combustion turbine, steam turbine or other.5) AGC scan rate data of grid frequency, MW output of the Resource and for steam turbines, supply steam pressure at rated output and at the time of the event. This can be scan rate data or a curve within the spreadsheet .

Draft Formal Scope for Phase 2 (generator level data for low responders) for OC consideration by first quarter of 2010

Consideration of detail on low performing BAs – detail level -

PJM©2009PJM DOCs #

Performance is based on the calculator that is part of FRS Form 1. The example in Table 1 below shows the calculation for a Balancing Authority with a -1000MW/0.1Hz Frequency Response, that has identified a 1200MW unit as its MSSC, and operates in an area where the first step of firm UFLS is at 59.95 Hz. The calculator assumes a Time Error Correction is in effect.

The calculator is based on the concept that the Balancing Authority is forced to operate as an independent island (such as during restoration) and is still able to withstand credible contingencies.

Starting Frequency 59.98 HzHighest UFLS 59.50 HzFrequency Safety Margin 0.48 HzFrequency Response (Beta) -1000 MW/0.1HzTriggering Event (Causes UFLS) 4800 MWMSSC 1200 MWSafety Margin 3600 MW# of MSSC required to trigger UFLS 4.0

T a b l e 1 E x a m p l e C a l c u l a t o r

T h e t w o c o l u m n s i n t h e F r e q u e n c y R e s p o n s e R i s k L e v e l ( F R R L ) t a b l e a c c o u n t s f o r t h e f a c t r i s k i s l o w e r f o r m u l t i - B a l a n c i n g A u t h o r i t y i n t e r c o n n e c t i o n s f o r t h e s a m e c o n t i n g e n c y . T h i s i s b e c a u s e a l l B a l a n c i n g A u t h o r i t i e s i n a n i n t e r c o n n e c t i o n w i l l c o n t r i b u t e t o c o n t i n g e n c i e s a n y w h e r e i n t h e i n t e r c o n n e c t i o n .

T h e F r e q u e n c y R e s p o n s e R i s k L e v e l i s r e p o r t e d a n n u a l l y a s p a r t o f F R S F o r m 1 . B a l a n c i n g A u t h o r i t i e s w i t h a F R R L > 0 w i l l c a l c u l a t e a n d r e p o r t t h e i r 1 2 m o n t h r o l l i n g a v e r a g e F r e q u e n c y R e s p o n s e e a c h q u a r t e r . C o m p l i a n c e w i l l b e a s s e s s e d e a c h q u a r t e r t h e r e a f t e r u n t i l F R R L = 0 .

Case Frequency Response Risk Level

Cases below are calculated based on BA or RSG operating as an island. See calculator in Appendix 1

Single BA or RSG Interconnection

Multi BA or RSG Interconnection

Performance Based proposal


Cases below are calculated based on BA or RSG operating as an island. See calculator in Appendix 1

Single BA or RSG Interconnection

Multi BA or RSG Interconnection

Event 2x MSSC will initiate firm UFLS

0 0

Event 1.5x MSSC will initiate firm UFLS

1 0

Event = MSSC will initiate firm UFLS

2 1

Event = MSSC will initiate UFLS > 10 % of firm demand

3 2

Mitigation Successfully Applied

Decrement Risk Level by 1 Decrement Risk Level by 1

Table 1 Frequency Response Risk Level Table

PJM©2009 1 PJM DOCs # Frequency Response Drafting Team Frequency Response Background Frequency...

Documents

Transcript of PJM©2009 1 PJM DOCs # Frequency Response Drafting Team Frequency Response Background Frequency...