NERC GADS 101 Data Reporting Workshop

1. NERC GADS 101Data Reporting Workshop G. Michael CurleyManager of GADS ServicesOctober 27-29, 2010

2. Welcome • GADS Services Staff • Mike Curley – Manager of GADS Services • Joanne Rura – GADS Services Coordinator • Ronald Niebo – Reliability Assessment and Performance Analysis Coordinator • Please stand and introduce yourselves • Your name, company, and experience with GADS

3. Overview of Attendees at this Conference • Representatives of: • Generating companies (IOU, IPPs, Government, etc) • Consultants • Insurance • ISOs

4. What’s in the folder? • Agenda • List of attendees (as of October 20, 2010) • Changes to the 2011 DRI • Slides for GADS 101 Data Reporting Workshop • Slides for GADS Wind Data Reporting Workshop • Slides for Benchmarking Seminar • Slides for pc-GAR and pc-GAR MT Workshop • Slides for Unit Design Data Entry Program • Flash drive

5. What’s on the flash drive? Same as the folder plus … • GADS Data Reporting Instructions (effective January 1, 2011) • GADS Data Editing Program • GADS Services Pricing Schedule • pc-GAR and pc-GAR MT Demo Software • pc-GAR Order Forms • GADS Wind Turbine Generation Data Reporting Instructions • GADS Wind Generation Data Entry Software • WEC Studies

6. Agenda • Introduction and welcoming remarks • What is NERC? • What is GADS? • Fundamentals on the three GADS Databases • Event • What are the elements of the event database? • Performance • What are the elements of the performance database? • Design • What makes up the design database?

7. Agenda (cont.) • IEEE 762 Equations and their meanings • What are the equations calculated by GADS? • What are they trying to tell you? • Review of standard terms and equations used by the electric industry. • Data release policies • What’s new with GADS? • Closing Comments

8. NERC is the ERO

9. NERC Background • NERC started in 1968. • NERC chosen as the ERO for the US in 2006. Started developing the “Rules of Procedure” to manage the bulk power supply. • BPS consists of the transmission and generation facilities. • NERC changed from “council” to “corporation” in January 2007. • From 2007 to now, NERC became the ERO of 6 of the 10 Canadian Provinces.

10. Energy Policy Act of 2005 • Signed by President Bush in August 2005 • The reliability legislation amends Part II of the Federal Power Act to add a section 215 making reliability standards for the bulk- power system mandatory and enforceable. • Electric Reliability Organization (ERO) • Not a governmental agency or department • Same purpose: “To keep the lights on” but with more power to do so.

11. Energy Policy Act of 2005 • “Bulk-power System” means the facilities and control systems necessary for operating an interconnected electric energy transmission network (or any portion thereof) and electric energy from generation facilities needed to maintain transmission system reliability. The term does not include facilities used in the local distribution of electric energy.

12. About NERC Develop & enforce reliability standards Analyze system outages and near-misses & recommend improved practices Assess current and future reliability International regulatory authority for electric reliability in North America

13. Meeting Demand in Real Time Typical Daily Demand Curve Operating Reserves Peak Load Capacity: Instantaneous measure of electricity available at peak Intermediate Load Base Load Energy: Electricity Produced over Time

14. About NERC: Regional Entities (RE)

15. What does NERC do? • Sets reliability standards (96 in place; 24 being reviewed) • Monitors compliance with reliability standards • Provides education and training resources • Conducts reliability assessments • Facilitates reliability information exchange • Supports reliable system operation and planning • Certifies reliability organizations and personnel • Coordinates security of bulk electric system • Cyber attacks • Pandemics • Geomagnetic disturbances

16. One of the first orders of business… • Create a transmission database • Transmission Availability Data System (TADS) • 200 kV and above. • Currently 2 years of data in TADS

17. Work now… • Marry the transmission to the generation databases, using Section 1600 of the Rules of Procedure.

18. GADS Task Force • Talked about mandatory GADS reporting for many years. • In June 2010, the NERC Planning Committee (PC) approved a task force to determine if GADS should be mandatory and to what level. • About 77% of the installed capacity already report to GADS. • Voluntary database now. • To date, the GADSTF is recommending mandatory reporting of GADS data.

19. Rules of Procedure: Section 1600Overview • NERC’s authority to issue a mandatory data request in the U.S. is contained in FERC’s rules. Volume 18 C.F.R. Section 39.2(d) states: “Each user, owner or operator of the Bulk-Power System within the United States (other than Alaska and Hawaii) shall provide the Commission, the Electric Reliability Organization and the applicable Regional Entity such information as is necessary to implement section 215 of the Federal Power Act as determined by the Commission and set out in the Rules of Procedure of the Electric Reliability Organization and each applicable Regional Entity.”

20. Rules of Procedure: Section 1600Request Details • A complete data request includes: • a description of the data or information to be requested, how the data or information will be used, and how the availability of the data or information is necessary for NERC to meet its obligations under applicable laws and agreements • a description of how the data or information will be collected and validated • a description of the entities (by functional class and jurisdiction) that will be required to provide the data or information (“reporting entities”) • the schedule or due date for the data or information • a description of any restrictions on disseminating the data or information (e.g., “confidential,” “critical energy infrastructure information,” “aggregating” or “identity masking”) • an estimate of the relative burden imposed on the reporting entities to accommodate the data or information request

21. Rules of Procedure: Section 1600Procedure NERC Approval Committees Acting Subgroup Not Approved Submit Data Request to PC Submit Data Request to DCS Draft Data Request Data Rule In Effect Not Approved Public Comment Period FERC Comment Period Submit Data Request Post Data Request (45 Days) File Data Request (21 Days) No Appeal Collect, Respond, & Post Comments NERC Board of Trustees Affected Parties Submit Final Data Request Appeal (30 Days) Finalize Data Request Approved Not Approved

22. Rules of Procedure: Section 1600Limitations • NERC Registered Entities • Subject to FERC Rules • Data Request does not carry the same penalties to non-U.S. entities. • However, all NERC Registered Entities, regardless of their country of origin, must comply with the NERC Rules of Procedure, and as such, are required to comply with Section 1600

23. What if a GO doesn’t comply? • Possible NERC actions: • From Rule 1603:  “Owners, operators, and users of the bulk power system registered on the NERC Compliance Registry shall comply with authorized requests for data and information.”  The data request must identify which functional categories are required to comply with the request. In this case, it presumably would be Generation Owners.

24. What if a GO doesn’t comply? • Possible NERC actions: • NERC will audit the GADS data submittals through logical evaluations of the data reported and that previously reported by the entity.  Reconciliation findings will be reviewed with the reporting entity.

25. What if a GO doesn’t comply? • Possible NERC actions: • NERC may resort to a referral to FERC for only United States entities, not Canadian entities. NERC will make use of the mechanisms it has available for both U.S. and Canadian entities (notices, letters to CEO, requests to trade associations for assistance, peer pressure) to gain compliance with the NERC Rules. A failure to comply with NERC Rules could also be grounds for suspension or disqualification from membership in NERC. Whether or not NERC chooses to use that mechanism will likely depend on the facts and circumstances of the case. • NERC cannot impose penalties for a failure to comply with a data request.

26. What if a GO doesn’t comply? • Possible FERC actions: • All members of NERC (US and Canadian) are bound by their membership agreement with NERC to follow NERC’s Reliability Standards and Rules of Procedure, including section 1600.   • Under section 215 of the Federal Power Act, FERC has jurisdiction over all users, owners, and operators of the bulk power system within the United States. • FERC could treat a failure by a U.S. entity to comply with an approved data request as a violation of a rule adopted under the Federal Power Act using its enforcement mechanisms in Part III of the FPA.

27. What if a GO doesn’t comply? • What about Canada? • Canadian provinces who have signed agreements stating they recognize NERC’s ERO status, will be compliant with the NERC approved standards and Rules of Procedure issued by the NERC Board. • The obligation arises for the Canadian utilities if they are members of NERC. For example, if Canadian Utility “A” is a member of NERC, then it must go by the Rules of Procedure, standards, etc. If Canadian Utility “X” is not a NERC member but its providence recognizes NERC as their ERO, then Utility “X” is not under obligation to follow the rules.

28. GADS vs. ISO Data Collection Rules • Currently, GADS sets data collection rules for use on a national basis; each ISO can set the rule for data collection within their jurisdiction. • Here are special rules that GADS suggests for hydro units. • As of August 5, 2008 we considered a draft of the rules. • A more “final set of rules” is now Appendix M of the GADS Data Reporting Instructions issued January 2010. • One recommendation of GADSTF is one set of rules for all (coordination between GADS and ISOs).

29. More information? • Please visit our website: www.nerc.com • Most information is open to the public.

30. Question & Answer

31. What is GADS? G - Generating A - Availability D - Data S - System

32. What is GADS? • Analyze the past (1982-2009) • Conduct special studies like high impact/low probability (HILP) studies • Perform benchmarking services • Monitor the present (2010 data) • Track current unit performance • Assess the future • Predict the future performance of units

33. Example – Benchmarking – Distributions [Fossil-steam units 200-400MW; Coal fuel; 6,500+ Service Hours/Yr.; 2005-2009; (79 units from 73 companies)]

34. Example – Benchmarking – Top Problems [Fossil-steam units 200-400MW; Coal fuel; 6,500+ Service Hours/Yr.; 2005-2009; (79 units from 73 companies)]

35. What is meant by “Availability?” • GADS maintains a history of actual generation, potential generation and equipment outages. • Not interested in dispatch requirements or needs by the system! • ** If the unit is not available to produce 100% load, we want to know why!

36. Monitor the Present GADS Generator “C” Generator “D” Generator “B” Generator “A” Generator “E” 5,800+ generating units including 2 international affiliates.

37. Malaysia * Ireland * Brazil * India * Peoples Republic of China Spain New Zealand South Korea Parts of S. America International GADS Users * Are or soon will be reporting outage data to GADS.

38. GADS 2009 Data Reporting 5,874 units reported in 2009, 0.9% increase in the number of units reporting over 2008!

39. Why GADS? • Provide NERC committees with information on availability of power plant for analyzing grid reliability and national security issues. • Provide energy marketers with data on the reliability of power units. • Assist planning of future facilities. • Help in setting goals for production and maintenance.

40. Why GADS? • Evaluating new equipment products and plant designs. • Assisting in prioritizing repairs for overhauls. • Help planners with outage down timing and costs. • Provide insights on equipment problems and preventative outages.

41. Why GADS? • Benchmarking existing units to peers. • Provide a source of backup data for insurance, governmental inquiries and investigations, and lose of hard drives. • Working to find answers to questions not asked. • Economic dispatch records • Generation owners in several regions • Track units bought and sold

42. Question & Answer

43. The GADS Data Monster

44. The GADS Databases • Design – equipment descriptions such as manufacturers, number of BFP, steam turbine MW rating, etc. • Performance – summaries of generation produced, fuels units, start ups, etc. • Event – description of equipment failures such as when the event started/ended, type of outage (forced, maintenance, planned), etc.

45. Design Data Reporting (Section V)

46. Why collect design data? • For use in identifying the type of unit (fossil, nuclear, gas turbine, etc). • Allows selection of design characteristics necessary for analyzing event and performance data. • Provides the opportunity to critique past and present fuels, improvements in design, manufacturers, etc.

47. Unit Types (Appendix C)

48. Minimum Design Data for Editing • Utility (Company) Code • Unit Code • NERC Region • Date of commercial operation • Reaching 50% of its generator nameplate MW capacity • Turned over to dispatch (enters “active state”) • Nameplate rating of unit (permanent) • State location

49. Design Data Forms • Forms are located in Appendix E • Complete forms when: • Utility begins participating in GADS • Unit starts commercial operation • Unit’s design parameters change such as a new FGD system, replace the boiler, etc.

50. Example of Design Data Form