1. PJM©2009 1 PJM DOCs # Frequency Response Drafting Team Frequency Response Background Frequency Response Standard History Briefing on Frequency Response Meeting (8/28) Data Request Next Steps 1

2. PJM©2009 2 PJM DOCs # 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

3. PJM©2009 3 PJM DOCs #

4. PJM©2009 4 PJM DOCs # 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

5. PJM©2009 5 PJM DOCs # Classifications - Time Frame - Measures

6. PJM©2009 6 PJM DOCs #

7. PJM©2009 7 PJM DOCs # Interconnections Depicted on same Axis

8. PJM©2009 8 PJM DOCs # Frequency response is always the same through out the year or is it?

9. PJM©2009 9 PJM DOCs # How to use differing scan rate supplied values to apply a standard technique

10. PJM©2009 10 PJM DOCs # Standardized calculation method of frequency response

11. PJM©2009 11 PJM DOCs # ERCOT experience using the FRSSDT method – similar outcome on response

12. PJM©2009 12 PJM DOCs #

13. PJM©2009 13 PJM DOCs # ERCOT Frequency Profile – Nov 2008 – 4 base load super critical units providing governor support @ +/- 1 rpm – on outage in April

14. PJM©2009 14 PJM DOCs # 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 1 st 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

15. PJM©2009 15 PJM DOCs # 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

16. PJM©2009 16 PJM DOCs # 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

17. PJM©2009 17 PJM DOCs # Balancing Authorities RS Frequency Task Force Define points A, B and select Events for analysis Step 1: Enter events 750 MW – EI & WI 500 MW ERCOT (monthly) NERC-FMA 1-Second Frequency Phasor Data CERTS Step 2: Call Survey NERC Central site Monthly Event Collection VOLUNTARY FRRSDT EVENT DATA REQUEST – INTERIM AND TARGET PROCESSES Rev:11.23.09 Interim Process Target Process

18. PJM©2009 18 PJM DOCs # Phase 1 Data Collection (2010) Interconnection Benchmarking U0 code created in GADS to capture unit trip data Use Quarterly DCS report to gather unit trips > 750 MW (current reporting threshold is 1000MW Minor 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 Tools FRSDT 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 2011 Modified based on comments in the FRS drafting team effort

19. PJM©2009 19 PJM DOCs # Balancing Authorities RS Frequency Task Force Define points A, B, and C Step 2 Call Survey Select Events within a quarter NERC-FMA 1-Second Frequency Phasor Data CERTS Call Survey Central site Survey Collection & Calculations FRSDT Event Analysis Reports VOLUNTARY FRRSDT DATA REQUEST – INTERIM AND TARGET PROCESSES Rev:11.23.09 Interim Process Respond Survey – scan rate data Survey count should be selecting approximately 3 per month NERC Central site Monthly Event Collection

20. PJM©2009 20 PJM DOCs # 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 -

21. PJM©2009 PJM DOCs # CaseFrequency 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

22. PJM©2009 22 PJM DOCs #