Meeting Minutes GADS Working Group (GADSWG) Availability Data...• June 2015 : GASDWG approves responses to comments & a revised wind DRI • September 2015: NERC PC asked to approve

Meeting Minutes GADS Working Group (GADSWG) September 30, 2015 | 1:00 PM -5:00 PM ET Meeting and October 1, 2015 | 8:30 AM -3:30 PM ET In Person and Ready Talk Conference Introduction and Chair’s Remarks – Chair Gary Brinkworth welcomed attendees and provided an overview of the meeting. NERC Antitrust Compliance Guidelines and Public Announcement – NERC GADSWG Coordinator Margaret Pate reviewed the Antitrust and Public Announcement Policies of NERC. Agenda Items Day 1: • GADSWG roster: GADSWG reviewed the membership roster. Salvatore Spagnolo volunteered to be

the Northeast Power Coordinating Council (NPCC) Generation Owner (GO) representative. o Presentation: GADSWG members

(attached) • Wind Data Reporting Instructions (DRI):

o Slide 7 contains the schedule presented to the Planning Committee (PC). The PC is supportive of this implementation plan. Pending Board approval in November 2015, both the platform implementation and training timelines will be developed.

o Presentation: Wind GADS NERC PC 0915m2 (attached)

• Personal computer version of NERC's Generating Availability Report (pc-GAR) reporting errors: o In order to prevent reporting errors in pc-GAR, NERC decided to set Gross Actual Generation

(GAG) to 0.01 until GADSWG confirms DRI data validation can be systematically implemented. o Presentation: How to prevent Errors when GAG Lee

(attached) • Input for the 2016 work plan:

o Sinnott Murphy of Carnegie Mellon University reviewed his findings to date. Additionally, guidance was provided by the GADSWG on the challenges Sinnott presented.

o Presentation: Murphy GADSWG 093015 final.pdf (attached)

o Jack Norris of Georgia Southern gave a year over year comparison of Quarter 1 (Q1) Equivalent Forced Outage Rates (EFOR) for 2014 and 2015

o Presentation: GADSWG Presentation 92915 Norris (002) (attached)

• Regional coordinator workshop o An overview of the upcoming regional coordinator workshop was provided. Contact Trinh Lee

for agenda modifications.

o Presentation: Regional Meeting Agenda Nov2015 DRAFT 9 23 201 (attached)

• Notice of Proposed Rule Making (NOPR) September 17, 2015: The Federal Energy Regulatory

Commission (FERC) today proposed to require the North American Electric Reliability Corporation (NERC) to provide the Commission with access to NERC’s transmission availability data system, generating availability data system and protection system misoperations databases.

o Several industry representatives indicated that their companies planned to respond to the request. NERC is formulating the appropriate course of action to take.

Day 2: • Review 2016 work plan priorities:

o Training opportunities Impact of poor data quality: Leeth De Priest presented several examples of poor data

quality in GADS. GADSWG agreed that data quality should be an area of focus in 2016. Spreadsheets: Boiler Misc, Electrostatic Precipitator Fouling, Emergency Generator Trip

Devices, Major Turbine Overhaul and Other LP Turbine Problems (attached)

GADSWG to review the GADS FAQ page and provide updates to DL-GADS. GADS training can be found at

http://www.nerc.com/pa/RAPA/gads/Pages/Training.aspx. Leeth De Priest will be the training sub team lead. Training for wind reporting will be

coordinated by Fred Beasom. Lewis De La Rosa volunteered to be the lead to develop a basic data entry guide. Other GADSWG members will be tapped as needed.

o Chapter for the State of Reliability Report (SoRR) – Input for the GADS chapter and the timeline will be agenda item on the next GADSWG call.

• Technical sub team report out: o 2016 Data Reporting Instructions (DRI) will be submitted by Lee Thaubald for approval by the

GADSWG in the November meeting. o Cause codes – Lee Thaubald will update the cause codes for fires, GTs/CTs and hydro and then

post the current version on the GADS web page. GADSWG will be requested to approve the cause codes in the November meeting.

o Pending change orders: Lee Thaubald will provide status of these change orders in the November GADSWG meeting.

o webE-GADS Bug Discussion – Ed Tindell provided an overview of several bugs encountered when trying to submit data. WebE-GADS is on the agenda at the regional coordinator meeting in November. NERC staff coordinators have requested OATI to respond to questions contained in the presentation. Additionally, several best practices were recommended by Ed.

o Presentation: webE-GADS Bug Discussion (attached)

• 2016 Meetings: GADSWG decided to keep the 2016 in person meetings in Atlanta. Training sessions to be offered in Atlanta as well as regional locations.

Minutes – GADS Working Group – September 30th and October 1st, 2015 2

http://www.ferc.gov/media/news-releases/2015/2015-3/09-17-15-E-3.asp%23.VhP9TvlVhBc

http://www.nerc.com/pa/RAPA/gads/Documents/GADS%20FAQ%20080414.pdf

http://www.nerc.com/pa/RAPA/PA/Performance%20Analysis%20DL/2015%20State%20of%20Reliability.pdf

http://www.nerc.com/pa/RAPA/gads/Pages/default.aspx

• Chair and Vice-chair appointments: Leith De Priest and Steve Wenke will be recommended respectively as Chair and Vice-Chair of the GADSWG to the Performance Analysis Subcommittee (PA).

o Future scope of GADSWG: Original scope of the organization can be found here. GADSWG reviewed the scope and recommended that the Chair, Vice Chair, Vice Chair elect and NERC staff coordinators consider adding advising and training activities to the scope.

o Membership structure: GADSWG will consider added additional ISO, wind and solar representation.

Minutes – GADS Working Group – September 30th and October 1st, 2015 3

http://www.nerc.com/comm/PC/Generating%20Availability%20Data%20System%20Working%20Group/GADSWG_Scope_12-02-2011.pdf

GADSWG Membership Structure

October 1, 2015

RELIABILITY | ACCOUNTABILITY2

• Chair• Vice Chair• NERC staff coordinator(s)• Eight (8) Generation Owner members from each NERC region• One Canadian member• One North American Generation Forum (NAGF) member• One Electric Power Supply Association (EPSA) member• One additional “at large” member• Other members, as requested by the NERC staff coordinator

GADSWG Membership


• Chair: Gary Brinkworth

• Vice Chair: Leeth De Priest

• The subcommittee chair and vice chair are appointed by the chairs of the NERC Operating Committee and Planning Committee for one, two-year term. The vice chair should be available to succeed to the chair. The Operating Committee members shall be appointed by the chair of the

Operating Committee for a two-year term.

GADSWG Officers


• NERC staff coordinators: Lee Thaubald, Margaret Pate, and Matthew Varghese

• One Canadian member Daniel Gent, Canadian Electricity Association David Mah, Saskatchewan Power

• One North American Generation Forum (NAGF) member Brian Buckley, Douglas Jerzycke, Mike Grimes, and Steve Wenke

• One Electric Power Supply Association (EPSA) member Becky Davis, PPL EnergyPlus, LLC

• One additional “at large” member Many working group members available

GADSWG Membership


Eight (8) Regional Coordinators – one from NERC region

GADSWG Membership


• Eight (8) Generation Owner members from each NERC region Need NPCC member

GADSWG Membership



GADSWG Scope

PurposeThe Generating Availability Data System Working Group (GADSWG) is to

implement a uniform approach to reporting and measuring North American generating plant availability, performance and other related reliability data.

ActivitiesTo accomplish its purpose, the GADSWG will perform the following activities:

1. Review and recommend new generation availability data that should be subject to mandatory collection by NERC.2. Review additions and changes to the GADS Data Reporting Instructions (DRI).3. Analyze, assess and report on trends and risks to reliability from generator availability and performance.

Annual DeliverablesThe GADSWG will contribute to the PAS’s annual Performance Analysis Report.


GADSWG Scope

MembershipThe GADSWG will consist of:

• Chair

• Vice Chair

• NERC staff coordinator(s)

• Eight (8) Generation Owner members from each NERC region

• One Canadian member

• One North American Generation Forum (NAGF) member

• One Electric Power Supply Association (EPSA) member

• One additional “at large” member

• Other members, as requested by the NERC staff coordinator

• Additional Members can be added: At the request of the Planning Committee sector representatives, or

As needed by the NERC coordinator.


GADSWG Scope

The subcommittee chair and vice chair are appointed by the chairs of the NERC Operating Committee and Planning Committee for one, two-year term. The vice chair should be available to succeed to the chair. The Operating Committee members shall be appointed by the chair of the Operating Committee for a two-year term.


GADSWG Scope

Order of BusinessIn general, the desired, normal tone of GADSWG business is to strive for

constructive technically sound solutions which also achieve consensus. On the relatively few occasions where that desired outcome cannot be achieved, the GADSWG will defer to a vote by the Planning Committee to settle the issue. If any strong minority opinions develop, those opinions may be documented as desired by the minority and forwarded to the PAS Chair and PC Chair for future meeting consideration.

NERC staff advice should be about what the ERO needs to be successful. The above normal tone of PAS to seek a technically sound consensus is very important. NERC staff and Observers are also expected to strive for constructive technically sound solutions and seek consensus.


GADSWG Scope

ReportingThe GADSWG reports to the Performance Analysis Subcommittee

(PAS). Reports and recommendations developed by the GADSWG require approval by PAS and the Planning Committee.

MeetingsFour to six open meetings per year, or as needed.

Approved by the NERC Planning Committee: ____________, 2011


GADSWG Roster


GADSWG Roster


GADSWG Roster

Wind GADS Data Reporting Instructions (DRI)

Gary S. Brinkworth, P.E.Chair, GADS Working GroupPlanning CommitteeSeptember 15, 2015

2 RELIABILITY | ACCOUNTABILITY

Purpose

• Requesting Planning Committee approval of the revised wind Data Reporting Instructions (DRI) Generating Availability Data System Working Group

(GADSWG) revised the wind DRI document based on industry comments

DRI provides guidance for mandatory GADS reporting of wind generatorso Modifies the existing Section 1600 mandatory data collection for

GADS

• If the PC approves the revision, approval by the NERC Board will then be requested at their November 2015 meeting


Why Is This Important?

GADS-W (wind) data is required for the following NERC and Regional Entity activities: • reliability assessment reports and modeling; • loss-of-load expectation studies and modeling; • NERC and its stakeholders need to understand how

resource availability and performance impacts Planning Reserve Margin calculations;

• actual wind generator performance data is needed to continue to refine the severity risk index to establish the effect that wind generation is having on Event Driven and Condition Driven risk, detailed event information and generation performance characteristics

• monitoring the impact of transmission outages on generators and generator outages on transmission.


Wind DRI Schedule

• 12/9/14: NERC PC approved Section 1600 process

• 1/21-2/11/15: FERC notice period• 2/17-4/3/15: Industry comment period• June 2015 : GASDWG approves responses to

comments & a revised wind DRI• September 2015: NERC PC asked to approve

revised wind DRI• November 2015: NERC Board agenda item for

mandatory wind GADS data collection• January 2017: voluntary (trial) reporting of

wind GADS data


Revised GADS-W DRI

• Formal comments received from 10 organizations (including AWEA & EEI)

• Comments generally fall into two categories Concerns about reporting timeline, obligations Clarifications about some aspects of data collection specs

• GADSWG reviewed the comments and revised the original DRI to address these concerns

• No substantial changes in the original DRI were deemed necessary Revised DRI was not circulated for additional comments But responses and the revised document were posted


Summary of Revised DRI

Who will report:• Plants with a Commissioning date of January 1,

2005 or later.

• Plants greater than or equal to 75MW.

• Any plant of any size can voluntarily report.

What will be reported:• Plant Data – Initial and whenever there is a

change with the quarterly reports.

• Group Data – Initial and whenever there is a change with the quarterly reports.

• Sub-Group Data – Initial and whenever there is a change with the quarterly reports.

• Performance at the Sub-Group level – Quarterly by month. All data except derates are optional.

• Component level and derate data can be reported on a voluntary basis.


Summary of Revised DRI

Frequency:• Quarterly

• 45 days after the end of the quarter

When will it start:• Date will be determined by the Planning

Committee and the NERC budget cycle

• Targeting January 1, 2017

Phases:• 1st year voluntary reporting

• 2nd year 200 MW plants and above

• 3rd year 100 to 199 MW plants

• 4th year 75 to 99 MW plants


Conclusion

• Requesting Planning Committee approval of the revised wind Data Reporting Instructions (DRI) Generating Availability Data System Working Group

(GADSWG) revised the wind DRI document based on industry comments

DRI provides guidance for mandatory GADS reporting of wind generatorso Modifies the existing Section 1600 mandatory data collection for

GADS

• If the PC approves the revision, approval by the NERC Board will then be requested at the November 2015 meeting


Questions?


Appendix


Plant, Group and Sub-Group data

Presenter

Presentation Notes

The figure represents a typical plant with the plant boundary at the revenue meter. Groups usually represent different phases of development. For example in Group 1 there are two Sub-Groups, where each Sub-Group contains different turbine types installed the same year. If a Sub-Group is repowered, the Sub-Group is retired and a new Sub-Group created under the same Group. GADS-W recognizes that there are many potential layouts of wind plants so there are no hard and fast rules for Plant, Group and Sub-group layout other than a Sub-Group can only contain turbines of a specific make, model, version and commissioning date. Submitted once and if any characteristics change Installed equipment design and operating characteristics


Initial Draft: Wind DRI

• Mandatory Reporting Wind farm/facilities with a

capacity 75 MW+ and a commercial date of 1/1/2005 or later

MW threshold would be lowered at a future date

• Data collection to include Generator data: plant, group

and subgroup levels Performance data Component outage data

Presenter

Presentation Notes

Before submitting the component outage and performance data for your wind plants, the plant, group, and sub-group data for each plant must be reported to the GADS-W database. The plant, group, and sub-group data only needs to be provided once when you begin reporting data for each plant and when the characteristics of the plant change. Although, we strongly recommend that all five of the files above be reported with each quarterly submittal. This data provides information regarding installed equipment design and operating characteristics of the plant that are used in special analysis as sorting criteria. In addition, component outage and performance data cannot be verified without this data so it must be submitted before you report any component outage and performance data. Once the plant, group, and sub-group data have been reported to the GADS-W database you can begin to report the component outage and performance data. The component outage and performance data should be submitted to GADS-W within 45 days after the end of every calendar quarter to [email protected]. These data should be reported throughout the life of each plant.

How to prevent Errors when GAG = 0 Pc-GAR processing has Errors when Gross Actual Generation (GAG) = 0 and both Gross Maximum Capacity (GMC) and Service Hours (SH) are reported. This causes an error in pc-GAR due to calculations in statistics. “GAG must be reported if Serv Hr & GMC are” From the GADS Data Reporting Instructions (DRI) highlighting, bold, and italics on the relevant text. From Page IV-4: Gross Actual Generation (GAG) (Record 01, columns 28-36) - Voluntary Enter the actual number of gross electrical megawatthours (MWh) generated by the unit during the month. If you report both service hours and gross actual generation (one to 9999999), you must also report GMC or GDC. Similarly, if you report both service hours and a gross capacity value, you must also report gross actual generation. This provides consistency when calculating performance statistics. Gross Maximum Capacity (GMC) - Voluntary

From Appendix F: Unweighted (time-based) methods for calculating single unit statistics.

Unweighted (time-based) methods for calculating pooled (grouping) unit statistics

Weighted (capacity-based) methods for calculating pooling (grouping) unit statistics

Currently, there is no webE-GADS data validation for this error. NERC staff manually updates these errors when processing data into pc-GAR. This task is very time consuming and delays reporting times.

Possible Solutions:

• Have an error in webE-GADS to prevent data submittal when GAG = 0, but GMC and SH are reported. (recommended based on DRI)

• Have webE-GADS automatically calculate GAG = GMC * SH (not recommended)

• Have webE-GADS automatically set GAG = .01 (current manual solution – not recommended)

The Distribution of Unavailable Capacity in North America

Sinnott Murphy, NERC and Carnegie Mellon University GADS Working Group September 30, 2015

RELIABILITY | ACCOUNTABILITY 2

Presentation outline

§  Introduc)on and mo)va)on §  Overview of methods §  Select early results §  Discussion and ques)ons


Introduction to GADS

§  NERC has amassed a treasure trove of data in the Genera)ng Availability Data System (GADS) §  Voluntary repor)ng since 1982; mandatory repor)ng since 2012 §  Approximately 500,000 events logged every year in GADS

§  Each event record entered into GADS reports an amount of unavailable capacity for a par)cular unit at a point in )me

§  These data have historically been used for benchmarking a unit’s performance against its peers to understand: §  How many events per year does a unit experience? §  What is the breakdown of events by type or cause code? §  What is the average dura)on of an event?


Introduction: Why system analysis?

§  The reliability of the bulk power system depends on how much capacity is out at one point in )me, rather than what is out on average

§  What could we study if we knew how much capacity was actually unavailable at any point in )me over the past 30 years? §  Risk and impacts of extreme weather events §  Common-‐mode failures and correlated outages §  On-‐peak versus off-‐peak availability §  Reliability implica)ons of a changing resource mix

§  …With GADS we can


Introduction: Scope of analysis

§  To calculate total unavailable capacity at any point in )me for a given power system I need to do two things: §  Determine how much capacity is unavailable for each unit at each point

in )me §  Add up unavailable capacity across units

§  Note I only consider unscheduled unavailable capacity, which includes seven event types: §  SF: startup failures §  U1, U2, U3: forced outages §  D1, D2, D3: forced dera)ngs §  (Why? Because other events are “scheduled”, meaning we can plan

around con)ngencies and )ght spots)


Methods (1): From events to units

§  To calculate a )me series of unavailable capacity for a single unit I need to: §  Compute magnitude of each event §  Add up unavailable capacity across events for each unit §  Check resul)ng )me series of unavailable capacity against reported “net

available capacity” values included in each event record

§  Challenges: §  Simultaneous events §  More than 100% of nameplate capacity unavailable §  Dominant dera)ngs


Graphical validation of calculations


Methods (2): From units to system

§  To get from a unit-‐level )me series of unavailable capacity to a system-‐level )me series I simply add up the previous result across all units contained in a given power system §  Currently available aggrega)ons: NERC regions and interconnec)ons §  Future: NERC assessment areas, control areas, etc.

§  Examples of early results follow; please treat all numbers as preliminary and subject to change


Time series of unavailable capacity


Disaggregating results by NERC region


Next steps

§  Data wrangling and valida)on: §  Con)nue valida)ng ini)al results §  Extend )me period of analysis §  Increase temporal resolu)on from hour to minute §  Geocode all units to aggregate results to addi)onal geographies

§  Data analysis: §  Predic)ve modeling of correlated outages §  Assessing reliability impacts of changes in genera)on fleet §  Analyze on-‐peak and off-‐peak unavailability §  Generate input data for NERC’s probabilis)c assessments


Challenges

§  Fully shadowed dera)ngs: §  Treat reported NAC as true always, or ignore event when reported NAC is

higher than unit’s NAC in prior instant?


Challenges (2)

§  Duplicate records: §  Iden)cal start date, end date, and NAC? §  Iden)cal start date and NAC?


Challenges (3)

§  Simultaneous dera)ngs (same start date): §  How to compute the dera)ng magnitude? If NAC of the two events is

iden)cal? If NAC is different? §  Treat one as overlapping the other?


Challenges (4)

§  Dera)ng to 0.01 MW

§  Available capacity changes when event is broken across calendar years


Thank you!


Supporting material


Distribution of unavailable capacity

§  Once the )me series of unavailable capacity is built, how do we make it useful to planners and system operators?

§  One example: plot the frequency of each unique level of unavailable capacity in a system over a chosen )me interval §  Shows risk of having more than X MW unavailable in this interval for this

system §  Think of it as loosely analogous to a load dura)on curve §  Example on next slide


Distribution of unavailable capacity

EFOR & 2014/2015 Q1 Comparison

Jack NorrisAugust 2015


• EFOR – Equivalent Forced Outage RateUsed for calculating generator outage ratesReserve shutdown skewing

• WeightingUnweighted – Single or few similar unitsWeighted – Large number of various units

EFOR Introduction


𝑊𝑊𝑊𝑊𝑊𝑊𝑊𝑊𝑊𝑊 =∑[(𝑊𝑊𝑊𝑊𝐹𝐹 + 𝑊𝑊𝑊𝑊𝐸𝐸𝐹𝐹) ∗ 𝑁𝑁𝑁𝑁𝑁𝑁]

∑[ 𝑊𝑊𝑊𝑊𝐹𝐹 + 𝑆𝑆𝐹𝐹 + 𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝑆𝐹𝐹 + 𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝑃𝐹𝐹 + 𝑊𝑊𝑊𝑊𝐸𝐸𝐹𝐹𝑊𝑊𝑆𝑆 ∗ 𝑁𝑁𝑁𝑁𝑁𝑁]∗ 100%

WEFOR – Weighted Equivalent Forced Outage RateFOH – Forced Outage HoursSH – Service HoursSynchH – Synchronous HoursPumpH – Pumping HoursEFDH – Equivalent Forced Derated HoursEFDHRS – Equivalent Forced Derated Hours During Reserve ShutdownNMC – Net Max Capacity

Current EFOR Equation


2014 vs 2015 EFOR

Region Fuel 2014 Low 2015 Low 2014 High 2015 High

MROCoal 4.76% 5.37% 5.15% 8.06%

Natural Gas 45.04% 52.00% 68.24% 67.64%Hydro 1.92% 1.24% 2.71% 1.44%

Nuclear 3.05% 0.00% 10.10% 9.87%NPCC

Coal 6.18% 19.46% 12.12% 19.95%Natural Gas 43.04% 35.19% 59.76% 51.82%

Hydro 4.89% 11.75% 9.63% 16.97%Nuclear 0.73% 1.42% 4.51% 7.56%

RFCoal 11.58% 11.55% 13.72% 14.10%


Nuclear 0.83% 0.74% 3.33% 2.55%SERC

Coal 6.11% 8.65% 7.30% 11.49%Natural Gas 24.70% 11.84% 31.72% 12.95%

Hydro 1.43% 6.57% 1.76% 7.99%Nuclear 0.02% 0.50% 2.73% 2.43%

SPPCoal 6.31% 3.37% 7.46% 7.90%


TRECoal 8.96% 12.20% 12.86% 20.58%


Nuclear 0.00% 0.00% 3.94% 0.03%

Table A3: 2014 vs 2015 EFOR Comparison


• Use in conjunction with capacity outage data

Further Comparison


Agenda DADS, GADS, and TADS Regions Meeting November 9, 2015 | 8:00 a.m. – 5:00 p.m. ET November 10, 2015 | 8:00 a.m. – 3:00 p.m. ET NERC Atlanta Headquarters, Room #611 3353 Peachtree Road NE Suite 600 North Tower Atlanta, GA 30326 NERC On-Site Contact: Trinh Ly (609) 610-6044 Webinar (both days): Readytalk Teleconference: (866)740-1260 | Access Code: 3650195 | Security Code: 110915 Introduction and Chair’s Remarks NERC Antitrust Compliance Guidelines and Public Announcement Agenda Items

1. Administrative Items

a. Introductions

b. Roll Call (round table and conference callers)

c. Facilities & Safety Briefing

d. Review and approval of agenda of this meeting –All

2. Roles and Responsibilities – Brad Gordon

a. NERC and Regional Staff Liaisons

b. NERC

c. Regional

d. Utilities/Entities

3. Review of the NERC GADS,TADS,DADS Website – Margaret Pate

a. How to navigate the website

b. Useful documents

c. Program management

d. NERC shared drive

http://www.readytalk.com/?ac=3650195

4. Review of the OATI Website – Nong Lor

a. Reporting Periods

i. Documented Process for missing due dates

b. Help documents and how to use the help feature

i. Web Help

c. OATI Training for Regional Entity Coordinators - Erika Eells – OATI

d. Company Hierarchy and User Management

i. Company Contact List

e. Reports Process of adding/removing FE

i. New companies/FE

ii. Active/inactive

iii. Regional Functions and capabilities

f. Completing the Checklist

5. Data Validation

a. Data – Matthew Varghese

i. Validation

ii. Checklists

iii. Which datasets is incomplete

iv. Reviewing the data content

v. Recommendations from the sub-team

b. Quality– Matthew Varghese and Leeth De Priest

i. How to measure unknown

ii. 2014 Completion Planning

iii. 2015 Completion Planning

iv. Implementing Data Quality Review Process

c. Reporting – Lee Thaubald

i. State of Reliability Report

ii. Dashboards

iii. Special Reports

iv. Data Report Instructions

Agenda – DADS, GADS, and TADS Regions Meeting - November 9-10, 2015 2

6. New Members Process

a. Review Scope documents

b. NERC’s process

c. Members’ process

7. ERO Future Vision: Strategic Plans – David Till

8. November Board Meeting Update – David Till

a. GADS 1600 Data Request

b. TADS 1600 Data Request

9. Using Data Within and Outside of the ERO – Round table discussion

a. NERC Reports

b. Regional Reports

c. Benchmark/ Metrics

d. Confidentiality Barriers

10. Regional Entity Issues/Question and Answer Session – Round table discussion

11. Training - Trinh Ly

a. Upcoming Training

b. Past Training Results

12. Misoperations Data Collection - Trinh Ly

13. Future Meetings

Agenda – DADS, GADS, and TADS Regions Meeting - November 9-10, 2015 3

Antitrust Compliance Guidelines I. General It is NERC’s policy and practice to obey the antitrust laws and to avoid all conduct that unreasonably restrains competition. This policy requires the avoidance of any conduct that violates, or that might appear to violate, the antitrust laws. Among other things, the antitrust laws forbid any agreement between or among competitors regarding prices, availability of service, product design, terms of sale, division of markets, allocation of customers or any other activity that unreasonably restrains competition. It is the responsibility of every NERC participant and employee who may in any way affect NERC’s compliance with the antitrust laws to carry out this commitment. Antitrust laws are complex and subject to court interpretation that can vary over time and from one court to another. The purpose of these guidelines is to alert NERC participants and employees to potential antitrust problems and to set forth policies to be followed with respect to activities that may involve antitrust considerations. In some instances, the NERC policy contained in these guidelines is stricter than the applicable antitrust laws. Any NERC participant or employee who is uncertain about the legal ramifications of a particular course of conduct or who has doubts or concerns about whether NERC’s antitrust compliance policy is implicated in any situation should consult NERC’s General Counsel immediately. II. Prohibited Activities Participants in NERC activities (including those of its committees and subgroups) should refrain from the following when acting in their capacity as participants in NERC activities (e.g., at NERC meetings, conference calls and in informal discussions):

• Discussions involving pricing information, especially margin (profit) and internal cost information and participants’ expectations as to their future prices or internal costs.

• Discussions of a participant’s marketing strategies.

• Discussions regarding how customers and geographical areas are to be divided among competitors.

• Discussions concerning the exclusion of competitors from markets.

• Discussions concerning boycotting or group refusals to deal with competitors, vendors or suppliers.

NERC Antitrust Compliance Guidelines 2

• Any other matters that do not clearly fall within these guidelines should be reviewed with NERC’s General Counsel before being discussed.

III. Activities That Are Permitted From time to time decisions or actions of NERC (including those of its committees and subgroups) may have a negative impact on particular entities and thus in that sense adversely impact competition. Decisions and actions by NERC (including its committees and subgroups) should only be undertaken for the purpose of promoting and maintaining the reliability and adequacy of the bulk power system. If you do not have a legitimate purpose consistent with this objective for discussing a matter, please refrain from discussing the matter during NERC meetings and in other NERC-related communications. You should also ensure that NERC procedures, including those set forth in NERC’s Certificate of Incorporation, Bylaws, and Rules of Procedure are followed in conducting NERC business. In addition, all discussions in NERC meetings and other NERC-related communications should be within the scope of the mandate for or assignment to the particular NERC committee or subgroup, as well as within the scope of the published agenda for the meeting. No decisions should be made nor any actions taken in NERC activities for the purpose of giving an industry participant or group of participants a competitive advantage over other participants. In particular, decisions with respect to setting, revising, or assessing compliance with NERC reliability standards should not be influenced by anti-competitive motivations. Subject to the foregoing restrictions, participants in NERC activities may discuss:

• Reliability matters relating to the bulk power system, including operation and planning matters such as establishing or revising reliability standards, special operating procedures, operating transfer capabilities, and plans for new facilities.

• Matters relating to the impact of reliability standards for the bulk power system on electricity markets, and the impact of electricity market operations on the reliability of the bulk power system.

• Proposed filings or other communications with state or federal regulatory authorities or other governmental entities.

Matters relating to the internal governance, management and operation of NERC, such as nominations for vacant committee positions, budgeting and assessments, and employment matters; and procedural matters such as planning and scheduling meetings.

BoilerMisc 1

Year Error Comment1999 Forced Unacceptable reporting - no info for understanding event1999 Forced Unacceptable reporting - no info for understanding event1999 Unit 2 Tripped Offli Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 FP00 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 U1-Immediate Ou Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 BTB-3 PACKING L 0640 Startup system bypass valves1999 MFT high drum level Operator error, instrumentation, controls ? It's always one of these1999 LIGHTING STRIKE TRIP POWER 9020 Lightning1999 LIGHTING STRIKE TRIP POWER 9020 Lightning1999 LIGHTING STRIKE TRIP POWER 9020 Lightning1999 LIGHTING STRIKE TRIP POWER 9020 Lightning1999 Boiler Trip Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 F430 Boiler trip on loos of fuel from drag chain. F430 is an error, there are codes for error1999 F870 Unit Trip due t Unacceptable reporting - no info for understanding event1999 F870 Unit Trip due t Unacceptable reporting - no info for understanding event1999 F870 Unit Trip due t Unacceptable reporting - no info for understanding event1999 Tripped on Drum Level - Steam Valve Issues Code to the particular valve1999 Unacceptable reporting - no info for understanding event1999 Boiler 2 tripped on high furnace temperatures from low fluidizing air flow. I think we added new code for fluidizing air after this event1999 MFT on high drum level Operator error, instrumentation, controls ? It's always one of these1999 MFT on low drum level Operator error, instrumentation, controls ? It's always one of these1999 Boiler 1 trip on high cylcone outlet temp Something caused this high temp and that should influence the code1999 Unacceptable reporting - no info for understanding event1999 BOILER MISCELLANEOUS Unacceptable reporting - no info for understanding event1999 BOILER MISCELLANEOUS Unacceptable reporting - no info for understanding event1999 Boiler tripped on high water level after coming on line. Looks like drum level. Operator error, instrumentation, controls ? It's always one of these1999 Out of Coal Lack of fuel or bunker flow or fuel handling issue - there are codes for these1999 F320 Washdown OK if exterior washdown, interior washdown would probably be slagging1999 F320 Unacceptable reporting - no info for understanding event1999 unit tripped during startup on low drum level Operator error, instrumentation, controls ? It's always one of these1999 Unit tripped on high drum level during startup Operator error, instrumentation, controls ? It's always one of these1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info

BoilerMisc 2

Year Error Comment1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Considerations - Boiler Floor. Reason for outage is equipment problem until repaired - need more info1999 Budgetary Consideration - boiler conditions. Worn cyclone re-entry an Reason for outage is equipment problem until repaired - need more info1999 UNIT MFT TRIP; DUE TO OLD ID FAN HARD-WIRE TRIP STILL ACTIVE. Error or controls issue1999 MFT / Boiler Drum Level Operator error, instrumentation, controls ? It's always one of these1999 Master Fuel Trip - Boiler Pressure Swing/Bad Card for Turbine 4311 steam turbine turbine control - hardware problems (including card failure)1999 #10 Boiler Outage What is cause? Unacceptable reporting - no info for understanding event1999 Boiler throttle valve opened causing water wall pressure to go below the trip 0640 Startup system bypass valves1999 While ramping boiler pressure #3 boiler throttle valve flew open causing the Water Wal 0640 Startup system bypass valves1999 Leak on the steam drum south drum vent root valve has a packing leak. 0800 Drums and drum internals1999 F780 High temperatur Unacceptable reporting - no info for understanding event1999 F060 Low Steam temps Unacceptable reporting - no info for understanding event1999 secondary superheater high temps Something caused this high temp and that should influence the code1999 F480 frozen lines What was frozen? Perhaps drum level transmitter lines?1999 Unit Online; Tripped on High Drum Level Operator error, instrumentation, controls ? It's always one of these1999 F830 High Pressure Drum west door gasket failed 0800 Drums and drum internals1999 F830 High Pressure Drum west door gasket failed during startup 0800 Drums and drum internals1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 A Boiler Infeed Conveyor ripped and taken off line for repairs 0030 coal conveyers and feeders, 0250 pulverizer feeders, also 0111, 0131,0150 ,01621999 RECOVERY BOILER TRIP DUE TO LOSS OF ID FAN. SUBSEQUENT PB TRIP DUE TO STM TRANSIENT. Code to ID fan, ID fan motor or controls 1455-14761999 tripped on drum level during start up Operator error, instrumentation, controls ? It's always one of these1999 Unacceptable reporting - no info for understanding event1999 42 HIGH HP DRUM LEVEL TRIP Operator error, instrumentation, controls ? It's always one of these1999 Start Delay sl Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 Unacceptable reporting - no info for understanding event1999 REPAIR TUBE LEAK IN NE CORNER OF FIREBOX 1000 Waterwall leaks1999 Fluid Bed Grate Damage Possibly correct - investigate fliud bed boiler codes. Is plant listed as fluid bed in GADS?1999 Fluid Bed Grate Damage Possibly correct - investigate fliud bed boiler codes. Is plant listed as fluid bed in GADS?1999 Blown observation port on boiler 0830 Doors might work, 1999 may be OK1999 REPAIR BOILER T Unacceptable reporting - no info for understanding event1999 REPAIR TUBE LEAK IN FRONT WATERWALL 1000 Waterwall leaks1999 REPAIR EXTERNAL TUBE LEAK NW CORNER OF U2 1000-1090 Tube leaks1999 Boiler Casing Leak-"" hot spot""3rd elevation east side 0820 Casing

Electrostatic Precipitators 1

CAUSE CODE DESCRIPTION Comment

8550 Vacuum precipitator hoppers OK8550 E2 Precip ashes and clinkers in hopper rodding ashes OK8550 Opacity Issues We think these may be duplicate events that last all year. Need NERC to investigate. Description may be OK but more insight would be good.8550 Opacity Issues We think these may be duplicate events that last all year. Need NERC to investigate. Description may be OK but more insight would be good.8550 Opacity Issues We think these may be duplicate events that last all year. Need NERC to investigate. Description may be OK but more insight would be good.8550 Opacity Issues We think these may be duplicate events that last all year. Need NERC to investigate. Description may be OK but more insight would be good.8550 Opacity Issues We think these may be duplicate events that last all year. Need NERC to investigate. Description may be OK but more insight would be good.8550 Opacity Issues We think these may be duplicate events that last all year. Need NERC to investigate. Description may be OK but more insight would be good.8550 Opacity Issues We think these may be duplicate events that last all year. Need NERC to investigate. Description may be OK but more insight would be good.8550 Opacity Issues We think these may be duplicate events that last all year. Need NERC to investigate. Description may be OK but more insight would be good.8550 Unit 5 Precipit Unacceptable reporting - no info for understanding event8550 ESP Fouling OK, not much more to say with this cause code unless there is a special reason for fouling like test burning a new coal.

Would never expect precipitator fouling to be long term event or high sustained loss event. These appear to be at one plant.

Emergency Generator Trip 1


4740 Action of the protective relay 59N If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Action of the protective relay 59N If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Action of the protective relay 59N If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Action of the protective relay 59N If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 GENERATOR DIFF 40 RELAY FLAG 86G If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 TRIPPED - OVER EXCITATION - VARS Need more info to verify code is correct4740 GENERATOR DIFFERENTIAL LOCK OUT If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 TRIP - GENERATOR BREAKER 87G3 OVERCURRENT WITH VOLT RESTRAINT Need more info to verify code is correct4740 Unit tripped off line with closing of yard breakers 1002 &1014 If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 OOS - Replace RTD If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 WATER LEAKED INTO CONTROL CABINET CAUSING CONTROL NET A & B TO FAIL Makes sense4740 Test trip of the low forebay elevation primary trip scheme Makes sense4740 Protective shutdown first indication generator earth ground Code to where the ground is located4740 GENERATOR LOCKOUT RELAY 2386B WOULD NOT RESET Makes sense, but is there another cause4740 Generator Breaker Malfunction / Generator Bearing Failure 4551 generator bearings, 4810 generator output breaker4740 PM on Generator Breaker; 4810 generator output breaker4740 PM on Generator Breaker 4810 generator output breaker4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Generator breaker tripped while lowering the AVR's set point for our l 4700 generator voltage control4740 UNIT TRIPPED DUE TO COLD GAS TEMP HI CAUSED BY LOSS OF THE CCW PUMP DUE LOSS OF MULTIL 3210 cirulating water pump or whatever caused it to trip4740 Bearing Flow De 4550 generator bearings and lube oil system4740 Ground Detected Code to where the ground is located4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Generator locko Unacceptable reporting - no info for understanding event4740 F840 Negitive Phase Unacceptable reporting - no info for understanding event4740 F840 Neg phase seque Unacceptable reporting - no info for understanding event4740 During trip check of Unit 04 EFS`s recieved a trip on Unit 01. Cause uncertain. Makes sense (5 MWH)4740 During unit operations of Unit 04 Unit 01 tripped. EFS is looking into the issue. Makes sense (2 MWH)4740 286BF relay operated opening the high side breaker and generator breaker. (belongs to reviewer 8 MWH) If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip. (belongs to reviewer 8 MWH)4740 Unit tripped on reverse powere when unit did not depress 7181 tailwater depressing equipment (belongs to reviewer 24 MWH)4740 286BF relay operated opening the high side breakers and generator breaker. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip. (635 MWH)4740 Gen 32G Reverse Power Relay Activated/ Fuel Flow Issues Causing Low Drum Pressure. Code to fuel flow issue code. Fuel flow is the problem that needs to be fixed.4740 Generator Tripped off line 59GN Relay Indication. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Generator Tripped off line 59GN Relay Indication. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Generator Tripped off line 59GN Relay Indication. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Generator Tripped off line 59GN Relay Indication. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 GT8 Tripped on 86G generator lockout relay. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Reason-H-Forced Outage T1 86 Trip Explanation-Pump/Relay scheme was incorrect Correct as is or should be an error4740 Reason-H-Forced outage Explanation-25 Sync check relay. Makes sense4740 Reason-H-Forced Outage Explanation-Pump/Relay scheme incorrect Correct as is or should be an error4740 Reason-H-Forced Outage Explanation-Pump/Relay scheme incorrect Correct as is or should be an error4740 Reason-H-Forced Outage Explanation-Pump/Relay scheme incorrect Correct as is or should be an error4740 Reason-H-ELECTRICAL Explanation-TIR (Trip Indication Relay ) failure Makes sense4740 Reason-H-ELECTRICAL Explanation-TIR (Trip Indicaton Relay) Failure Makes sense4740 CT 32 Trip - Gen Breaker PT Failure 4810 generator breaker4740 Generator relay trip If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 87G (GEN DIFF) TRIP & 86G LOCKOUT @ 3MW ON S/D If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 87G (GEN DIFF) TRIP & 86G LOCKOUT @ 3MW ON S/D If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 CT1A tripped offline due to activation of generator relay 86 lockout from lightning 9020 Lightning4740 Relay 5DETX tripped emergency lockout. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip. (76 MWH)4740 Relay 5DETX tripped emergency lockout. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip. (81 MWH)4740 Generator tripped on high voltage. Possibly 4700 generator voltage control. Appears trip device worked properly. (3 MWH)4740 The ""generator out of step relay"" tripped the unit offline. (1207 MWH)4740 Unacceptable reporting - no info for understanding event4740 86RE Relay Picked Up If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 86RE Relay Picked Up If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 86RE Relay Picked Up If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Generator lockout relay If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Generator lockout relay testing Makes sense4740 Generator lockout relay If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Generator lockout relay If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Generator lockout relay If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Stator ground caused Generator trip 4520, 4530, 4535 stator codes4740 F490 in Forced Derate due to Generator Protective Relay Trip. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Investigation revealed a tripped 86-2 and a target #9 on the 7UM512 relay If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Generator Breaker Opened in SwitchYard (test) took unit offline Need more info to pick cause code4740 LOCK OUT DIFF. POSSIBLE WIRING RELATED PROBLEMS Makes sense4740 Trip - relaying issues -AST alarm Need more info to pick cause code4740 Units off line due to unit trip devices due to controls project issues Sounds like controls issue4740 Units off line due to unit trip devices due to controls project issues Sounds like controls issue4740 System (grid) upset - resulted in generator max. excitation limit trip 9300 Transmission problems



4740 UNIT 2 GENERATOR DIFFERENTIAL TRIP Need more info to pick cause code4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 UNIT 2 PUMP START FAILURE DUE TO FALSE OVERSPEED TRIP Correct as is4740 Faulty Beckwith Correct as is4740 WHEN UNIT WAS COMING DOWN U5 TRIP ON REV POWER-GENERATOR RELAYS ROLLED If unit was coming off, use code for the reason you were bringing unit off4740 Transformer Protection relay 86T-CD Trip. 86T-CD trips bus one Units A If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Transformer Protection relay 86T-CD Trip. 86T-CD trips bus one Units A If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Transformer Protection relay 86T-CD Trip. 86T-CD trips bus one Units A If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Transformer Protection relay 86T-CD Trip. 86T-CD trips bus one Units A If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Unacceptable reporting - no info for understanding event4740 OVERSPEED TESTING 4460 Turbine overspeed trip test4740 TSM RELAY TESTING IN SWITCHYARD. Makes sense but may be error4740 system protecti Unacceptable reporting - no info for understanding event4740 Generator breaker 9970 tripped due to relay activation. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Generator breaker 9970 tripped due to relay activation. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Reverse Power Trip If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Reverse Power Trip If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Unit tripped off line on mechanical trip issue being worked on at this time. 4302 turbine trip devices because of the mechanical issue4740 Unit tripped off line on mechanical trip issue being worked on at this time. 4302 turbine trip devices because of the mechanical issue4740 86 lockout due to an 87 alarm on phase differential If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 86 lockout due to a 20X IPS logic trip. Code IPS (whatever that is)4740 Speed sensor ring broke Possibly 4302 turbine trip device4740 emergency stop issued by operator. Fire on the MPT bearing. Oil leak Code to bearings and lube oil system and describe oil leak and fire4740 Tripped on GSU Probably 3620 main transformer4740 Tripped on Generator Protection Controls - Isophase BUS Moisture Intru 4800 generator main leads with moisture description4740 Tripped on Generator Protection Controls - Isophase BUS Moisture Intru 4800 generator main leads with moisture description4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 unit tripped after start and was restarted soon afterward Unacceptable reporting - no info for understanding event4740 unit automatically tripped after startup due to a bad thermocouple (TT7 Top- Bottom Sp Correct if TC on generator4740 2nd time-unit automatically tripped after startup due to a bad thermocouple (TT7 Top- Correct if TC on generator4740 XXX Line 1 230KV switches opened at YYY substation tripping GT1 and the Steam T 3720 Transmission at 1st substation or 9300 transmission system problems4740 relay trip 24 volt hertz Unacceptable reporting - no info for understanding event4740 Genertor trip Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Stator RTD #1 alarmed at 150 degrees and shut down Unit If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 OLoss of Power/AVR...Car # YU241457 Need more info to pick cause code4740 AVR/Vars(MVAR'S)...Car # YU241462 Need more info to pick cause code4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Testing Tripping Relays Make sense but could be error4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Generator breaker trouble 4810 generator output breaker4740 Generator breaker trouble 4810 generator output breaker4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Overvoltage Relay 59BN flagged along with 59GN Stator Ground Alarm. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Overvoltage Relay 59BN flagged along with 59GN Stator Ground Alarm. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 59GN Stator Ground Alarm. If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 UNIT RELAY DUE TO LIGHTNING 9020 lightning4740 UNIT RELAY DUE TO LIGHTNING 9020 lightning4740 UNIT RELAY DUE TO LIGHTNING 9020 lightning4740 A00000000000Unit tripped for unknown reason. No pretrip alarms just master trip a Makes sense4740 F840A00000000000Generator protection relay trip during start-up - investigating Need to go back and code based on findings4740 F840A00000000000Generator protection relay trip during start-up - investigating Need to go back and code based on findings4740 Unit relayed on generator undervoltage 4700 generator voltage control



4740 Unit relayed on generator undervoltage 4700 generator voltage control4740 UNIT TRIPPED. RECEIVED NORMAL SHUTDOWN LOCKOUT AND STATIC EXCITER TROUBLE. UNIT PAR Possibly 4603 solid state static exciter4740 UNIT TRIPPED BY ELEVATED NEUTRAL DEVICE. FOUND WATER ACCUMULATED IN GENERATOR PIT FRO Code should be associated with the water that was present4740 UNIT TRIPPED BY ELEVATED NEUTRAL DEVICE. FOUND WATER ACCUMULATED IN GENERATOR #1 PIT Code should be associated with the water that was present4740 [Generator][Controls] 4740:EMERGENCY GENERATO Unacceptable reporting - no info for understanding event4740 64S Generator Protection Relaytrip during connection for relay setting Correct or an error4740 Unacceptable reporting - no info for understanding event4740 Generator 86-1 Lockout relay - due to gas fuel valve logic 5041 Fuel piping and valves4740 Bad RTD Makes sense but no usable information4740 86M trip Due to a bad RTD Causing thrust Brg temp to spike up to the trip setting Sounds like 4302 turbine trip devices including instruments4740 Generator air housing temp high during an attemped air cooler changeout 4620 Air cooling system4740 Mechanical lockout at startup-no apparent reason Makes sense4740 Mechanical lockout on start. Relay 41RX appears to have failed. Makes sense4740 1 minute U1 event before SF event Unacceptable reporting - no info for understanding event4740 Unit relayed when Reverse Peak 12kV line locked out. No loss in generation. Unacceptable reporting - no info for understanding event. If this is outage or derate, why is there no loss of generation4740 Handle on 86 Relay coil broke Correct4740 Handle on 86 Relay handle broke. Correct4740 UNIT TRIP. Unacceptable reporting - no info for understanding event4740 UNIT TRIPPED. Unacceptable reporting - no info for understanding event4740 86 GT relay issues Makes sense4740 GENERATOR 15KV BUS GROUND 4800 generator main leads4740 GENERATOR 15KV BUS GROUND 4800 generator main leads4740 GENERATOR 15KV BUS GROUND 4800 generator main leads4740 UNIT 3 GENERATOR GROUND TRIP Need to know what component in generator4740 UNIT 3 GENERATOR GROUND TRIP Need to know what component in generator4740 CONTINUING STATOR GROUND REPAIR 4520, 4530, 4535 stator codes4740 CONTINUING STATOR GROUND REPAIR 4520, 4530, 4535 stator codes4740 CONTINUING STATOR GROUND REPAIR 4520, 4530, 4535 stator codes4740 CONTINUING STATOR GROUND REPAIR 4520, 4530, 4535 stator codes4740 UNIT 3 UPPER GUIDE BEARING 38 OVERHEAT/86GT WITH NO OTHER ALARMS Either a bearing lube oil issue or bad instrument4740 D2 tripped on an incomplete shu D2 tripped on an incomplete shu Unacceptable reporting - no info for understanding event4740 FIELD GROUND FIELD GROUND 4500 rotor windings4740 O/S Gen. Diff. Relay O/S Gen. Diff. Relay Unacceptable reporting - no info for understanding event4740 LC #1 Diff Lockout LC #1 Diff Lockout If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 LC #1 Diff Lockout LC #1 Diff Lockout If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 LC #1 Diff Lockout LC #1 Diff Lockout If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 LC #1 Diff Lockout LC #1 Diff Lockout If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 LC #1 Diff Lockout Tripped LC #1 Diff Lockout Tripped If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 LC #1 Tripped LC #1 Tripped If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Gen Drop Gen Drop Unacceptable reporting - no info for understanding event4740 Gen Drop Gen Drop Unacceptable reporting - no info for understanding event4740 Gen Drop Gen Drop Unacceptable reporting - no info for understanding event4740 Resetting Transfer Trips Resetting Transfer Trips Need more info to pick cause code4740 Gen Drop Gen Drop Unacceptable reporting - no info for understanding event4740 Field Ground Relay 64F Activate Field Ground Relay 64F Activate If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 Upper Guide Bearing Over Temper Upper Guide Bearing Over Temper Either a bearing lube oil issue or bad instrument4740 Gen Diff Lockout Gen Diff Lockout Unacceptable reporting - no info for understanding event4740 Unit Lock out Unit Lock out Either a bearing lube oil issue or bad instrument4740 Unit Creep Detected (By New Pro Unit Creep Detected (By New Pro Need more info to pick cause code4740 Unit Creep Detected (By New Pro Unit Creep Detected (By New Pro Need more info to pick cause code4740 86'd on shutdown. 86'd on shutdown. Code to reason the unit was coming off. If coming to RS, this is correct but need better description.4740 UNIT LOCKOUT ON 64G UNIT LOCKOUT ON 64G If the device was supposed to trip the unit for the condition detected, the device is not the cause of the trip. If it malfunctioned, it is the cause of the trip.4740 MEGGER UNIT/64G L/O MEGGER UNIT/64G L/O Need more info to pick cause code4740 Unit Trpped Unit Trpped Unacceptable reporting - no info for understanding event4740 Trip-Generator Unacceptable reporting - no info for understanding event4740 Remote Shutdown Failed slic 2389102 Need more info to pick cause code4740 F170 Faulty sudden pressure device caused unit trip. Moisture from recent Correct4740 Testing of low penstock pressure trip Makes sense or error4740 86E Trip Unacceptable reporting - no info for understanding event4740 86E trip device Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 Unacceptable reporting - no info for understanding event4740 replace coils on relays Correct

Major Turbine Overhaul 1


4400 Unacceptable reporting - no info for understanding event4400 Unacceptable reporting - no info for understanding event4400 Unacceptable reporting - no info for understanding event4400 Unacceptable reporting - no info for understanding event4400 Unacceptable reporting - no info for understanding event4400 Unacceptable reporting - no info for understanding event

4400 Steam Turbine Had A Fire In The Steam Turbine Enclosure. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 Steam Turbine Had A Fire In The Steam Turbine Enclosure. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 Steam Turbine Had A Fire In The Steam Turbine Enclosure. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 Steam Turbine Had A Fire In The Steam Turbine Enclosure. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 CT 2A Is Unavailable Due To Steam Turbine Fire. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 CT 2A Is Unavailable Due To Steam Turbine Fire. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 CT 2A Is Unavailable Due To Steam Turbine Fire. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 CT 2A Is Unavailable Due To Steam Turbine Fire. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 CT 2B Is Unavailable Due To Steam Turbine Fire. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 CT 2B Is Unavailable Due To Steam Turbine Fire. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 CT 2B Is Unavailable Due To Steam Turbine Fire. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard4400 CT 2B Is Unavailable Due To Steam Turbine Fire. The cause of the fire should be determined and the correct cause code picked. For example, if a lube oil line ruptured, 4283 lube oil piping and valves could be used with the description: lube oil line ruptured which resulted in fire at front standard

These events are for the same combined cycle plant

4400 Turbine Control Valve Problems 4261 Control valves. The description should define the failure4400 Turbine Control Valve Problems 4261 Control valves. The description should define the failure4400 Cracked turbine There are codes for inner and outer casing and shafts which is likely what is cracked. The description does not indicate any understanding of the plant.4400 Cracked turbine There are codes for inner and outer casing and shafts which is likely what is cracked. The description does not indicate any understanding of the plant.4400 STG3 PLANNED MI OUTAGE EXTENSION Unacceptable reporting - no info for understanding event4400 STG3 PLANNED MI OUTAGE EXTENSION Unacceptable reporting - no info for understanding event4400 Planned Outage work continuation. If it is planned outage work continuation, why is it reported as forced. No description to support event type.

4400 Major turbine overhaul should never be used for a forced event. The work may look like a major overhaul but should be coded to the part of the turbine that caused thr forced event.

Other LP Turbine Problems 1


4250 FV00 2 STG tripped due to high vibration on 5X and 6Y 4420 vibration of turbine generator4250 FV00 2 STG tripped due to high vibration on 5X and 6Y 4420 vibration of turbine generator4250 FV00 2 STG forced outage for LP turbine disassembly Pick a code based on the problem found from the disassembly4250 blown rupture disk There is not a good code for rupture disk4250 Turbine tripped on High Hood Exhaust Temp 4303 Exhaust hood and spray controls, but may be an operational issue4250 TG1 - Low vacuum - rupture disc leaking There is not a good code for rupture disk4250 TG1 - Low Vacuum 3149 unless you know why4250 Trip on High Backpressure/Low Vacuum 3149 unless you know why4250 High Vibrations 4420 vibration of turbine generator4250 F850 Turbine Vibrati 4420 vibration of turbine generator4250 F850 Tripped on turb 4420 vibration of turbine generator4250 Turbine LP lead seal leaking vacuum badly There is not a good code for rupture disk4250 F830 Condenser Tube Leak Caused the Steam Turbine to be Shut Down 3110 condenser tube leaks - not a turbine issue4250 TRIPPED UNIT ON LOW VACUUM 3149 unless you know why4250 Unit was not on line when problem occurred with LP'sl; unit was in start up getting re Unacceptable reporting - no info for understanding event4250 Unit was not on line when problem occurred with LP'sl; unit was in start up getting re Unacceptable reporting - no info for understanding event4250 Unit was not on line when problem occurred with LP'sl; unit was in start up getting re Unacceptable reporting - no info for understanding event4250 Unit was not on line when problem occurred with LP'sl; unit was in start up getting re Unacceptable reporting - no info for understanding event4250 Unit was not on line when problem occurred with LP'sl; unit was in start up getting re Unacceptable reporting - no info for understanding event4250 Unit was not on line when problem occurred with LP'sl; unit was in start up getting re Unacceptable reporting - no info for understanding event4250 Unit was not on line when problem occurred with LP'sl; unit was in start up getting re Unacceptable reporting - no info for understanding event4250 Unit was not on line when problem occurred with LP'sl; unit was in start up getting re Unacceptable reporting - no info for understanding event4250 Unit was not on line when problem occurred with LP'sl; unit was in start up getting re Unacceptable reporting - no info for understanding event4250 Testing following work done during extended catastrophic forced outage. Would recommend using same code as original ouatage to tie them together. But this code may be OK.4250 Unacceptable reporting - no info for understanding event4250 Unacceptable reporting - no info for understanding event4250 High LP Exhaust Temperature Trip 4303 Exhaust hood and spray controls, but may be an operational issue4250 TG1 - Replaced rupture disc There is not a good code for rupture disk4250 Sealing steam p 4430 Gland seal system

A blown rupture disk is usually the result of an operational issue and is not really the cause of the outage. The rupture disk blows to protect the turbine. If it leaks or fails when it should not, then it is the cause of the outage.

webE-GADSBug Discussion

GADSWG Fall Face To Face Meeting9/29/15

Example Bug - Background

• While submitting my Q2 data I discovered that cause code 4536 did not apply to all of the necessary unit types in webE-GADS.

• In fairness to OATI cause code 4536 was only listed in the NERC DRI for GT and the unit I was trying to submit with it was a CC GT. It was an error in the cause code list NERC gave to OATI to implement.




• So the GADSWG worked with NERC to get 4536 added to all unit types.

• However, I missed the 45 day deadline on submitting my Q2 data and was frozen out.

• So I sent my Q2 data to my regional representative to enter for me.

• They emailed me about some problems with submitting the data.

Example Bug - Discovery

• So I logged onto webE-GADS to see what I could do.

• The checklist showed my data entered for both Q1 and Q2 but only completed for Q1.


• That is when I found a new problem.• I tried the “Modify” button to complete Q2 and

got the errors shown below. But Q1 was showing as completed!


• Q1 had submitted without error when I originally submitted it. It was Q2 that had the cause code error. Something was not right.

• I emailed my results to my regional representative who told me he had encountered the same problem with other entities which means the error is wide spread and does not occur for just one person.

Example Bug - Analysis

• I am not sure what happened to cause the bug.

• I sent the same data files to NERC and they submitted both Q1 & Q2 successfully for me. Regional entity take note.

• (So now I’m all caught up. Yeah!)• But that still leaves the question of the display

discrepancies encountered while trying to submit my data.


• webE-GADS let me try to “Modify” the submitted quarters without checking the validate boxes (greyed out so I couldn’t) and showed me the March errors, yet March showed Completed.

• That is two (2) errors: – If I am locked out I shouldn’t be able to modify

anything. – My data shouldn’t show completed when it has errors

in it.


• When you think about it OATI can really only control the quality of their own software.

• Here are some examples of contributing factors in these errors:– NERC gave OATI bad cause code data which is

what led me to find the error to begin with, by trying to do something with the data.

– OATI cannot control the environment on the entities PC at the time they submit their data.


• Could the PC environment be responsible for this error? Software interference is a possibility.

• Could my regional representative have been trying to work with the data at the same time I was? – Can multiple people work in the same place at the

same time in webE-GADS? – Had we been the victims of a moving target?


• What version of Java, et cetera, if any, is needed for webE-GADS?

• What was the environment on the PC like when OATI acceptance tested webE-GADS?

• How many other applications were running?• How much clutter (old temporary files,

program fragments left in memory by memory leaks, et cetera) was on the PC?


• What was the quality of the submitting entities Internet connection?

• I have found that when webE-GADS doesn’t do something the first time, trying it again will quite often work, even if it gave you an error the first time.

• That type of inconsistent behavior could be due to a noisy or slow Internet connection.

Example Bug - Conclusions

• What can we do?• We could ask OATI to verify the quality of their

software. It’s behavior should be consistent.• We could survey the data submitters and ask

them about the environment on their PC when they run webE-GADS.

• We could compare the survey results to the OATI acceptance test PC environment.


• Based on the comparison results, we could propose some PC etiquette to users to help them create a standard environment on their PCs before using webE-GADS, such as:– Close all other programs– Delete all temporary browser files– Delete all Windows temporary files– Cold boot the PC to clear RAM memory– Et cetera


• The Regional Entities are going to meet in November and discussing webE-GADS errors is on their agenda.

• If you have experienced any kind of problem with webE-GADS I encourage you to write it up and send it in to NERC for compilation and presentation at the Regional Entity meeting.

• Question and Answers