Introduction to NERC GADS

Transcription

1 Introduction to NERC GADS General Overview to GADS Reporting for Beginners Mike Curley, GADSWG Observer, Navigant Consulting, Inc. GADS Data Reporting Training

2 Introduction - Mike Curley Former Manager of GADS Services for the North American Electric Reliability Corporation (NERC) Part of the GADS team for 29 years Principal trainer of GADS fundamentals for over 18 years Provided GADS consulting services to companies for over 33 years Past member of the World Energy Council Active member of ASME and IEEE societies Current MicroGADS Product Manager for Navigant Consulting, Inc. 2

3 Reminders No such thing as a dumb question Others may have the same question but are too shy to ask Help everyone get the most out of this workshop We will have breaks during the workshop However, feel free to leave if you need to make a call, stretch, use the restrooms, etc. 3

4 Why Are We Here? We are here at the GADS Workshops this week to: Discuss and learn correct principles for reporting GADS data in a uniform, complete, accurate and efficient way. Provide information to help with reporting work. Provide instructions to help reporters understand how to calculate performance hours as well as the GADS factors and rates. To provide knowledge for submitting GADS data to webe-gads and have it pass the edits the first time! 4

5 Agenda Why and what is GADS? Mandatory GADS What is webe-gads? GADS Data Reporting Instructions Resources High-level introduction to GADS details including Design data Event types and examples What is collected in the Event data What is collected in the Performance data Break out session on forced outage types 5

6 What is and Why GADS? 6

7 What is GADS? Generating Availability Data System (GADS) Introduction: Off shoot of the Edison Electric Institute (EEI) database introduced in 1960 s by the EEI Prime Movers Committee GADS introduced to the industry in 1982 Database to collect and analyze power plant equipment failures Assess and improve unit output and reliability Set realistic generating unit goals Foundation to determine the reliability of the bulk power system as related to generating units 7

8 Mandatory GADS As of January 1, 2013, all conventional units 20 MW+ are required to report to NERC. MW size (nameplate = generator MVA times power factor) To qualify: Company must be listed on the NERC Compliance Registry (NCR) Must be a generation owner (GO) Wind reporting became mandatory on January 1, 2018 for plants with a Total Installed Capacity of 200 MW or larger Training on wind reporting on Thursday! Solar reporting in development 8

9 What is webe-gads? GADS data collection software is operated by Open Access Technology International, Inc. Data is Uploaded monthly or quarterly data to the webe-gads portal Requires a digital certificate you received from either NERC or your OATI Security Administrator Upload the data yourself, or Designated Reporting Entity (DRE) can be approved to report for your company 9

10 GADS Data Reporting Instructions Data Reporting Instructions (DRI) Consists of 5 sections and 13 Appendices Sections: Introduction, Data Scope and Transmittal, Event Reporting, Performance Reporting and Design Data Reporting Appendices: Change of unit status, cause codes for 9 unit types, utility and identification codes, list of major components, unit design data forms, 8 unit types, equations (covered on Wednesday), examples and recommendations, failure and mechanism codes, data release guidelines, cause code amplification codes, outside plant management control, calculating combined cycle and co-generation block data, differences between NERC GADS and ISO GADS, year over year changes Cause codes and amplification codes in Excel 10

11 GADS Resources Websites GADS Program: o o General news like submission deadlines o Data reporting instructions (DRI) o Regional contacts o Training GADS working group (GADSWG) o Working-Group-(GADSWG)-2013.aspx o Members o Meeting agendas and notes 11

12 GADS Resources Technical support Regional contact s on GADS program website For webe-gads application support, contact OATI Support o Support@oati.net o Phone: Complex questions on how to report o GADS@nerc.net o Technical team of experts from the working group 12

13 13

14 Overview of GADS Reporting Collection of Unit Physical and Operating Information 14

15 What is Required? 15

16 The GADS Data Types Design Equipment descriptions such as manufacturers, number of Boiler Feed Pump (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. 16

17 General Note About GADS Many of the GADS data fields have not changed since 1982 Cause codes are updated annually as needed Items like Cause Code Amplification Codes (amp codes) are added as needed to improve the data quality. Two types of data fields are identified in this and tomorrow s presentation based on Mandatory GADS requirements: Required meaning you must complete this information. Optional or Voluntary meaning you can provide that information if you wish not required data. 17

18 GADS Required Design Data Collection of Unit Physical Plant Information 18

19 Why Collect Design Data? Identify the various unit types Separate units into groups by MW size, fuels, age, etc. 19

20 Nine Required Design Fields 1. GADS utility code (assigned by NERC or webe-gads) 2. GADS unit code (assigned by the reporting company following the guidelines in Appendix C, GADS Data Reporting Instructions) 3. NERC Regional entity where the unit is located (NPCC, WECC) 4. Name of the unit 5. Commercial operating date (date/year turned over to dispatch) 6. Type of generating unit (fossil, combined cycle, etc.) 7. MW size (nameplate = generator MVA times power factor) 8. State or providence location of the unit (CA, UT, NY, etc.) 9. Energy Information Administration (EIA) Plant number (US units only) (from the EIA 860 form) 20

21 Event Reporting General Collection of Unit Outage and Derating Information 21

22 Why Collect Event Data? Evaluate generating unit s performance Insights into equipment problems Required for uniform calculations per IEEE

23 Outages 23 Unit is 100% off line due to equipment, transmission, or other problems preventing unit from generating power. (Unit main breakers are open.) Required! Deratings Unit is not capable of full load due to restrictions from equipment, transmission, regulatory restrictions, insufficient fuels, poor fuels, or other problems. (Unit main breakers can be opened or closed.) Required! Reserve Shutdowns Unit is capable of operation at full load but is not in operation due to economics, management decision, etc. (Unit main breakers are open.) Required except for special cases with hydro units! Non-curtailing Four Event Type Classifications Equipment is out of service but unit is still capable of full load operation. (Redundant equipment spare coal mills, fans, pumps, etc. Not related to main breaker status.) Not Required.

24 Outage Types Timing starts WHEN THE PROBLEM IS DETECTED! Forced Outages (four types) Maintenance Outage (one type plus extension) Planned outage (one type plus extension) Forced Outage Before the end of next weekend (U3) 6 hours (U2) Now or very soon (U1) Can t start (SF) Maintenance Outage After the end of next weekend (MO/ME) Planned Outage Planned Well In Advance (PO/PE) 24

25 25

26 It Takes Team Work to Discovery the Causes of Outages! 26

27 What Are Cause Codes? 27

28 Primary Cause of Event GADS collects details regarding the system, major component, or piece of equipment primarily responsible for causing the outage or derating event. Primary details are required; secondary details are optional. Important details of event outage cause consists of: System/Component cause codes (cause codes) Cause Code Amplification Code (amp codes) Event Contribution Code Verbal Description 28

29 System/Component Cause Codes Four-digit code from Appendix B in the DRI that best identifies the system, major component, or piece of equipment being described More than 1,600 cause codes in GADS Appendix B is divided into several sections for easily locating the appropriate cause codes for each unit type. Fossil-steam Nuclear Combined cycle block Required 29

30 System/Component Cause Codes Several types of units share the same system components Same cause code ranges are used for these system components For example: Unit Types System components Fossil Nuclear Gas Turbines Combined Cycle Steam Turbine x x x Hydro Generator x x x x x Boiler x x Cooling Towers x x x 30

31 System/Component Cause Codes Some cause codes are descriptive of critical components. For example: 31

32 System/Component Cause Codes Check the cause codes for the best one to describe the equipment, failure or condition. For example: 22 cause codes to describe the problems with coal mills, started with CC

33 Verbal Description Provides detailed explanation of the event and the cause(s) identified by system/component cause code(s) Narrative should include a balanced description of the major aspects of the event, focusing on these key areas: Failure description and appearance Cause of immediate failure and contributing factors Corrective actions Limited space is available for your description, so abbreviate as much as possible. Voluntary But Encouraged 33

34 34

35 Performance Reporting Collection of Unit Generation and Fuel Information 35

36 Why Collect Performance Data? Performance data provides information, in a summarized format, pertaining to overall unit operation during a particular month in a given year. This data is needed to calculate unit performance, reliability, and availability statistics. Starting Reliability Equivalent Forced Outage Rate Demand (EFORd) Performance data is required for all unit types and sizes reported to the GADS program. 36

37 Gross vs. Net Capacities 37

38 38