1

NERC/GADS Reporting Requirements

John YaleHydro Plant Engineering ManagerChelan County PUD

GADS REPORTING

WHAT IS IT?

WHY ARE WE REPORTING?

WHAT IS THE FUTURE?

Material for these slides is from the NERC GADS workshop, October 2011

3

What is GADS?

A - Availability

S - System

G - Generating

D - Data

4

North American UtilityDatabase

Std 762Standard

Terminology

IEEE

Beginnings 1960’s - 1970’s

EEI

EPRI

1979 moved from EEI to NERC - Voluntary

5

Purpose

Generating unit availability database • Critique the past• Monitor the present• Assess the future

6

Critique the Past

• Conduct special studies High impact/low probability studies

• Produce annual GADS publications Generating Availability Report publication GADS Brochure

• Perform benchmarking services… and more

7

Monitor the Present

199619971998199920002001200220032004200520062007200820092010

3000

3500

4000

4500

5000

5500

6000

• 5,963 units reported in 2010!

8

Why Mandatory ReportingBefore 2012…

• Nearly 300 GW are not reported to GADS.• Nearly 50% of new units 2000-2008 did not

report • Large amounts of hydro-pumped storage,

combined cycle and gas turbines are missing. • These units are needed to analyze the

reliability of the bulk power system.

From GADS Task Force Report

9

Mandatory GADS in 2012

• Conventional Units– Units 50MW and larger - 2012– Units 20MW and larger – 2013

• Variable sources – wind, solarlater

10

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, NERC wants to know why!

11

The GADS Data Monster

12

webE Data System

TADS and DADS were already mandatory. GADS is the final step.

13

GADS Databases

• Design – equipment descriptions such as manufacturers, MW rating, etc.

• Performance – summaries of generation produced, fuels, start ups, etc.

• Event – description of equipment failures such as when the event started/ended, type of outage (forced, maintenance, planned), etc.

14

Design Data• GADS utility code (assigned by GADS Services)• GADS unit code (assigned by the reporting company following the

guidelines in Appendix C of the GADS Data Reporting Instructions.)

• NERC Regional entity where the unit is located• Name of the unit• Commercial operating date• Type of generating unit (fossil, combined cycle, etc.)• MW size (nameplate)• State or province location of the unit.• Energy Information Administration (EIA) Plant number (US units

only).

15

Performance Records

• Provides summary of unit operation during a particular month of the year. Actual Generation Hours of operation, outage, etc.

• Allows validation of event data• Submitted quarterly for each month of the year.

16

Event Records

• Track problems at your plant for your use.• Track problems at your plant for others use.• Provide proof of unit outages (ISO, PUC,

consumers groups, etc).• Provide histories of equipment for “lessons

learned.”• Provide planning with data for determining

length and depth of next/future outages.

17

GADS is a DYNAMIC System

Make as many changes as you want,

as many times as you want,

whenever you want.

18

Uniformity of Data

• Uniformity of data collection format is essential. All GADS data shall be collected using the GADS Data Reporting Instructions. The Reporting Instructions will be updated annually and each reporting company will be required to follow the latest Reporting Instructions for the current year.

• All questions or needs for interpretation of the reporting instruction interpretations will be coordinated with NERC staff and the GADSTF.

19

The “Ouch” Factor

• Non-IEEE or any other term• A description of what is the maximum

information you can gather from a power generator before they yell “ouch!”

• GADS is at the maximum Ouch Factor at this time. (NERC’s words not mine)

20

Use of IEEE Definitions

• IEEE definitions are designed to be guidelines and are interpreted by GADS.

• NERC asks all reporters to follow the guidelines so that uniformity is reporting and resulting statistics.

• Do not fit all hydro conditions and events.

21

What Does the Data Produce?

• Time Based Indices• Rates – Time Based Equations

22

Time Based Indices (factors)• Equivalent Availability Factor (EAF)• Equivalent Unavailability Factor (EUF)• Scheduled Outage Factor (SOF)• Forced Outage Factor (FOF)• Maintenance Outage Factor (MOF)• Planned Outage Factor (POF)• Net Capacity Factor (NCF)• Net Output Factor (NOF)

23

Time Based Equations – (rates)

• Forced Outage Rate (FOR)• Equivalent Forced Outage Rate (EFOR)• Equivalent Forced Outage Rate – Demand

(EFORd)

24

Accessing the Data• PC-GAR - NERC provided tool

– By subscription (annual, monthly)– Different versions for user type

• Produces reports for benchmarkingAF EAF FOR EFOR GCF SOF FOF

98.89 98.89 0.08 0.08 38.54 1.03 0.08

96.36 96.36 1.03 1.03 51.2 2.64 1

94.24 94.24 0.21 0.21 39.57 5.56 0.2

96.47 96.47 0.49 0.49 39.69 3.05 0.48

16.13 16.13 0 0 7.66 83.87 0

95.12 95.12 0.03 0.03 39.97 4.85 0.03

93.05 93.05 0.03 0.03 57.65 6.92 0.03

25

Data Release Guidelines• Operating companies have access to own data

only.• Manufacturers have access to equipment they

manufactured only.• Other organizations do not have access to

unit-specific data unless they receive written permission from the generating company.

• In grouped reports, no report is provided if less than 7 units from 3 operating companies.

26

What is Happening?• Leadership of GADS at NERC is in flux

– Mike left in 2012, Jay left in 2013– Currently recruiting for GADS leadership

• PC-GAR Not Currently Available– Needs commitment from NERC, – Rumor is late 2013/early 2014

• Current effort is to get data from OATI to NERC• GADS Task Force

27

Questions?

Call NERC!