Professional Documents
Culture Documents
System
Data Reporting Instructions
Table of Contents
Section I: Introduction
Industry Development of GADS ........................................................................................ I-2
Event Identification
IR - Inactive Reserve
MB - Mothballed
RU - Retired
Overlapping Deratings
Deratings that Vary in Magnitude with Time
Dominant Derating Reporting
A. Unit Identification
Record Code ........................................................................................................................ IV-2
Utility (Company) Code ....................................................................................................... IV-2
Unit Code ............................................................................................................................. IV-2
Year ...................................................................................................................................... IV-2
Report Period ...................................................................................................................... IV-2
Report Revision Code .......................................................................................................... IV-2
Index of Examples
Appendix M: Differences between NERC-GADS and ISO-GADS Data Collection and Uses .... M-1
SECTION I
I-I Table: Applications of GADS Data................................................................................. I-1
I-2 Table: Regional Entities ................................................................................................ I-3
SECTION III
III-1 Table: Event Reporting Requirements vs. Unit Type/Size .......................................... III-1
III-2 Table: Record Layout of Section A – Event Identification .......................................... III-2
III-1 Figure: Unit States Diagram ........................................................................................ III-5
III-2 Figure: Possible Derating Situations ......................................................................... III-15
III-3 Table: Record Layout of Section B – Event Magnitude ............................................ III-18
III-3 Figure: Allowable Event Type Changes..................................................................... III-20
III-4 Figure: Example of Dominant Derating Code Reporting .......................................... III-22
III-4 Table: Record Layout of Section C – Primary Cause of Event .................................. III-23
III-5 Table: Record Layout of Section D – Additional Work During Event ....................... III-24
III-6 Table: Allowable Cause Codes .................................................................................. III-25
III-7 Table: Record Layout of Event Records Using Failure Codes ................................... III-30
SECTION IV
IV-1 Table: Record Layout of Section A – Unit Identification ............................................ IV-2
IV-2 Table: Monthly Summaries......................................................................................... IV-2
IV-3 . Table: Record Layout of Section B – Unit Generation Performance .......................... IV-4
IV-1 . Figure: Effects of Ambient Temperature on Gas Turbines/Jet Engines ..................... IV-6
IV-4 . Table: Record Layout of Section C – Unit Starting Characteristics ............................. IV-6
IV-5 . Table: Unit Loading Characteristics ............................................................................ IV-7
IV-6 . Table: Record Layout of Section D – Unit Time Information...................................... IV-8
IV-7 . Table: Period Hours .................................................................................................. IV-10
IV-8 . Table: Record Layout of Section E – Primary Fuel; and F – Secondary Fuel ............ IV-11
IV-9 . Table: Fuel Types and Codes .................................................................................... IV-12
SECTION V
V-1 Table: Location of Design Data Forms ......................................................................... V-1
NERC developed the GADS Data Reporting Instructions to assist utility personnel in reporting information to the
Generating Availability Data System (GADS). This reporting system, initiated by the electric utility industry in 1982,
expands and extends the data collection procedures begun by the industry in 1963. NERC-GADS is recognized
today as a valuable source of reliability, availability, and maintainability (RAM) information. This information,
collected for both total-unit and major equipment groups, is used by analysts industry-wide in numerous
applications (See Table I-1). GADS maintains complete operating histories on more than 8,000 generating units,
representing over 90 percent of the installed generating capacity of the United States and Canada. As of January
1, 2013, GADS became a mandatory industry program for conventional generating units 20 MW and larger. GADS
remains open to all non-required participants in the Regional Entities (shown in Table I-2) and any other
organization, domestic or international, 1 that operate electric generating facilities willing to follow the GADS
mandatory requirements as presented in the document Final GADSTF Recommendations Report dated July 20,
2011.
High-impact outages
Utility designers, operating engineers, and system planners developed GADS to meet the information needs of
the electric utility industry. For this purpose, they established specific objectives for the GADS program:
compilation and maintenance of an accurate, dependable, and comprehensive database capable of monitoring
the performance of electric generating units and major pieces of equipment. GADS is not a substitute for the
detailed and often unique data systems typically found at power plants or for maintenance data programs that
record detailed equipment failures and repair techniques. The objectives of the GADS program can be met through
the collective effort of participating GADS members, the cooperation in reporting to GADS, and sharing
information with the industry.
With the GADS mandatory program, participating organizations must be prepared to commit the necessary effort
needed to provide timely, accurate, and complete data. The GADS Data Reporting Instructions detail the data
elements collected by GADS, data identified by the industry as being vital to the understanding and interpretation
1
NERC management reserves final approval authority for GADS data with international organizations on a case-
by-case basis.
Page I-1
Section I – Introduction
of generating unit and major equipment performance. By following the strict guidelines set forth in these
instructions, we have found that the industry analysts can best apply the data in the most beneficial manner.
The industry also realized a need to include standardized terminology in the GADS program if it were to function
on an international scale. As a result, the definitions promulgated by the Institute of Electrical and Electronic
Engineers’ (IEEE) Standard 762, “Definitions for Reporting Electric Generating Unit Reliability, Availability and
Productivity” were incorporated.
Utilities started their reporting using the GADS guidelines on January 1, 1982. GADS superseded the earlier data
collection procedures begun by the Edison Electric Institute (EEI), a program started in the mid-1960s. GADS
contains many of the same elements previously collected by EEI in addition to the many new data items. This
seeming duplication of data was created intentionally: the EEI information can be derived from GADS so analyses
that include data from earlier than 1982 can be completed.
Based on research by the IEEE 762 committee, the boundary between the GO and TO is as follows: “A generating
unit includes all equipment up to (in preferred order) (1) the high-voltage terminals of the generator step-up (GSU)
transformer and the station service transformers; (2) the GSU transformer (load) side of the generator-voltage
circuit breakers; or (3) at such equipment boundary as may be reasonable considering the design and
configuration of the generating unit.”
Not all plants have the high-voltage terminals of the generator step-up (GSU) transformer and the station service
transformers as shown in (1) above. Therefore, the boundaries are shown in preferred order based on unit design.
If (1) is not applicable, then (2); if not (2) then (3).
GADS will continue to collect all problems that prevent the generating facility from providing electrical power to
the customer. However, there are additional guidelines provided by IEEE 762. In Appendix K of this manual
“Outside Plant Management Control” are guidelines to determine what is and is not within the plant management
responsibilities. As a result, new equations are introduced for measuring plant performance. For further details,
refer to Appendix F of this manual.
Page I-2
Section I – Introduction
FRCC SERC
Florida Reliability Coordinating Council SERC Reliability Corporation
MRO SPP
Midwest Reliability Organization Southwest Power Pool
NPCC TRE
Northeast Power Coordinating Council Texas Regional Entity
RF WECC
ReliabilityFirst Western Electricity Coordinating Council
This document has several sections, and each section treats a particular area of data to report to GADS. Section II
describes the three general types of data to be reported to GADS: event, performance, and design. Sections III
and IV provides the details for the event and performance reporting requirements, respectively. Section V
describes the format and procedure to follow when reporting design data to GADS.
Page I-3
Section II – Data Scope and Transmittal
Scope
There are three types of data reported to GADS:
The GADS Data Reporting Instructions document describes the event and performance data in detail in Sections
III and IV. The nine mandatory design data fields described in Section V must be submitted before reporting any
event or performance data to NERC. All other design appendices in appendix E are voluntary but encouraged for
GADS work.
For the purposes of data reporting, the term “unit” is defined as follows:
Nuclear and fossil (steam) units — units consisting of a single reactor or boiler and a single turbine generator. In
cases where multiple boilers and/or multiple turbine-generators are headed together, the entire group is
considered a single unit and reported using the “Miscellaneous Unit” design data forms found in appendix E,
pages E-MS-1 to E-MS-5.
Hydro, pumped storage, gas turbine, jet engine, and diesel units — units consisting of the unique prime mover
and a single generator. In cases where multiple combinations of turbines/engines and generators exist, either
physically or because of operating philosophy, the entire group may be considered as a single unit or reported as
individual units. You should note your specific reporting criteria on the design data forms.
Combined-Cycle units (or blocks) — By definition, a combined-cycle is a process for generating energy (either
electricity or steam) constituted by the marriage of a Rankine Cycle (use heat to boil water to make steam to
turn a steam turbine) and a Brayton Cycle (expand hot gas to turn a gas turbine). The combined-cycle consists of
one or more gas turbines/jet engines and one or more heat recovery boilers. The heat recovery boiler sends
steam to a steam turbine for generating electricity. Each gas turbine/jet engine and each steam turbine is a
“unit”. The entire group is considered a “block”. Units where the gas turbines/jet engines can generate
independent of the heat recovery boilers and steam turbine are also combined-cycle blocks. Report design data
using the “Combined-Cycle Block” design data forms found in appendix E, pages E-CC-1 to E-CC-25.
Co-generation units — units consisting of one or more gas turbines/jet engines and one or more heat recovery
boilers. Co-generation is similar to the combined-cycle block except part of the steam from the heat recovery
boiler is used for other purposes (process steam), not the generating electricity. The entire ensemble is
considered a single block. Report design data using the “Combined-Cycle Block” design data forms found in
appendix E, E-CC-1 to E-CC-25.
Fluidized bed combustion units — units consist of one or more bubbling, circulating, or pressurized bed boilers
or steam turbines. Consider the entire group as a single unit.
Miscellaneous units — Miscellaneous conventional generating units are all other units (including variable fuel –
biomass, landfill gases, etc.) used to generate electric power for the grid. Groups of units using the same electric
meter are also categorized in the miscellaneous units group. For example, if you have five hydro units of 5 MW
Section II – Data Scope and Transmittal
each and they all have the same common revenue meter (measuring the electric output of the five units
combined), then this block of hydro units would be considered a 25 MW miscellaneous unit.
Reporting data to NERC-GADS begins when either one of the two following conditions is met:
1. The unit first enters the active state. This is termed the “service date” and occurs when the unit is first
declared available for the dispatch of power at some level of its capability.
2. The unit first operates at 50% of its generator nameplate megawatt capability. For purposes of
determining reporting requirements, the generator nameplate capability can be calculated by
multiplying the MVA (megavolt amperes) by the rated power factor found on the nameplate affixed to
the generator (nameplates in the case of multiple generator units).
The nine required design fields must be reported to GADS prior to reporting event and performance data. Your
generating company is required to report to GADS if your organization owns generating facilities and is listed on
the NERC Compliance Registry (NCR). This requirement applies to generators within North America that have a
nameplate capacity of 20MW or greater. All other generating units by non-registered generating companies or
units smaller than the required MW size are invited to participate in GADS on a voluntary basis.
We encourage all generating organizations to report all data elements currently collected for their units and any
additional information they can reasonably provide.
An “event” occurs any time a generating unit’s operating status or capability changes. GADS receives reports on
four general classifications of events: outages, derates, reserve shutdowns, and non-curtailing events. Reporting
event data, in addition to performance and design data, provides all the information needed to evaluate
generating unit availability. Event data are especially useful since they are often used to do specialized unit and
equipment operation and design analyses.
As of January 1, 2013, Reporting to the GADS program is mandatory for all conventional units that have a
nameplate capacity of 20 MW and larger. Reporting the level of detail requested in these GADS Data Reporting
Instructions enables you and other industry analysts to perform detailed, useful analyses. Figure III-1 below
presents the classes of events generating companies must report for different types and sizes of conventional,
non-renewable generating units.
Table III-1: Event Reporting Requirements vs Unit Type/Size Starting January 1, 2013
Unit Event Classifications
Size
Type Outage Derates Reserve Shutdown Non-Curtailing
(MW)
Combined Cycle/Co-
generators 20+ Required Required Required Voluntary
Miscellaneous – including
multi-boiler/multi-turbine,
geothermal, other
miscellaneous conventional
generating units (such as
variable fuel – biomass, 20+ Required Required Required Voluntary
landfill gases, etc.) used to
generate electric power for
the grid and similar in design
and operation as the units
shown above
Section III – Event Reporting
Detailed event data reporting for all units is mandatory and is indicated by the term “required.” The term
“voluntary” implies that each operating company must determine if it can reasonably provide detailed data. NERC
encourages all electric generating organizations to report all event data information and any additional
information they can reasonably provide.
You are required to report reserve shutdown events on all units except hydro and pumped storage units without
automatic data recording equipment. All other events (forced, maintenance, and planned) must be reported.
There are four distinct sections of the event report: A) event identification; B) event magnitude; C) primary cause
of event; and, D) additional cause of event or components worked during event. Together, these sections provide
a complete description of each event experienced by a unit.
A description of each section and the data elements within it follows. Included are detailed instructions for
reporting each event data element.
A. Event Identification
There are seven data elements, referred to as “fields,” in this section (see Figure III-2). These elements form a
“key” — an identifier that makes each event card unique from all others in the database. This key is referenced at
the beginning of every event record.
Record Code (columns 1-2) - Required
The “07” code uniquely identifies this data as an event report.
A – Event Identification
Year (required) 4 9
Enter the three-character (alpha-numeric) code NERC assigned to your operating company. Appendix C contains
a complete list of the operating companies participating in GADS and their assigned (operating company) codes.
An event occurred on December 2, 2012 and was reported to GADS on January 31, 2013. Complete columns
9-12 as 2012. (Refer to Page III-21 for instructions on reporting events that begin in one year and continue
into the next.)
You do not have to assign event numbers sequentially, although it is preferred. If you find you have omitted one
after gathering all the events to submit for a quarter, do not renumber all the events for the year; simply assign
the next available event number to the omitted event.
An event that continues through multiple months during the same year keeps the originally assigned event
number. Assign an event that continues from one year into the next with a new event number in the new year.
Refer to Page III-21 for further instructions.
The first time you submit an event to GADS it is called an “original” event. All original events have a revision code
of zero (0).
1, 2…. 9 Use these codes when making corrections or additions to original events. Each time
you make a change, you must increase the revision code by one. Up to nine
corrections and additions to an original event can be made.
When making corrections or additions to an original event, you need to send NERC
all records relating to that event on which the changes are to be made. On the record:
1. Complete columns 1-16, repeating the information from the original event;
and,
3. Make sure the same record number used in the original report is in
columns 81-82. DO NOT LEAVE THE RECORD NUMBER BLANK; and,
To delete data from one or more data fields, GADS RECOMMENDS that you resubmit
the entire data set — year-to-date — for that unit (or all units you report) to GADS.
This procedure will insure that both you and the GADS database have the same
records on file. You have the option to find the record that has the highest revision
code and then increase this number by one or set all revision codes back to zero.
Inactive States
The two most general unit states are shown at the top of figure III-1: active and inactive. Inactive state is called
“Deactivated Shutdown” in IEEE 762 and is defined as “the state in which a unit is unavailable for service for an
extended period of time for reasons not related to the equipment.” GADS interprets this to include:
IR – Inactive Reserve
IR is defined by IEEE 762 and GADS as “the state in which a unit is unavailable for service but can be
brought back into service after some repairs in a relatively short duration of time, typically measured in
days.” GADS added “after some repairs” and defines the phrase “after some repairs” to mean that some
action may be needed to prepare the unit for service because it had been sitting idle for a period of time,
and some equipment parts have deteriorated or need replacing before the unit can be operated. The unit
should be operable at the time the IR begins. This does not include units that may be idle because of a
failure and dispatch did not call for operation. A unit that is not operable or is not capable of operation at
a moment’s notice should be on a forced maintenance or planned outage and remain on that outage until
the proper repairs are completed and the unit can operate. The unit must be on RS a minimum of 60 days
before it can move to IR status. Use Cause Code “0002” (three zeros plus 2) for these events.
MB – Mothballed (MB)
MB is defined by IEEE 762 and GADS as “the state in which a unit is unavailable for service but can be
brought back into service after some repairs with appropriate amount of notification, typically weeks or
months.” GADS added “after some repairs” and defines the phrase “after some repairs” to mean that
some action may be needed because the unit had been idle for a period of time and some equipment,
systems or parts may have deteriorated and should be replaced or repaired prior to the units return to
service. The unit may have also experienced a series of mechanical problems, prior to the MB event, for
which management may wish to wait for a period of time to determine if the unit should be returned to
service or retired. Granted IEEE 762 states that the unit must be capable of operation prior to being placed
in the deactivated state; however, in actual practice management may want to delay a decision to fix the
generator and ‘suspend’ it in a deactivated state until a decision to repair or retire is rendered. If this
option is chosen the unit must enter the MB event no earlier than 60 days after the preceding outage
event (In other words the unit must incur a forced outage of a minimum 60 days prior to the start of an
MB event if the unit is inoperable). If the choice is to retire the generator after a decision is made, then
the generator can be immediately retired coincident with the end of the MB event; If the decision is to
repair, all repairs to make the unit operable must be completed under an outage of same type that
preceded the MB event (in other words, if the generator entered the MB event on the heels of a forced
outage, it must return to a forced outage for repairs to make the generator operable). If repairs are being
made on the unit in order to restore it to operating status once the MB event has started, the MB event
must end prior to the commencement of those repairs and the appropriate outage type started until those
repairs have been completed and the outage ended. Also, if there are long lead-time item(s) that are
ordered (such as a GSU, a generator rotor or the like) the MB event should end when the initial order has
been placed, since a decision at that time has been rendered to repair the generating unit. Again, once a
decision is rendered to repair the unit, whether or not orders are placed and/or work is started, the
mothball event must end and the appropriate outage type started. Repair work cannot be conducted on
a unit in the mothball state.. Use Cause Code “9991” for these events.
RU – Retired
RU is defined by IEEE 762 and GADS as “the State in which a unit is unavailable for service and not expected
to return to service in the future.” RU should be the last event for the remainder of the year (up through
December 31 at 2400). The unit must not be reported to GADS in any future submittals. Use Cause Code
“9990” for these events.
Active States
The lower part of figure 1 more precisely describes the operating state of a unit at any given time. The fourth level
shows the most detailed operating states; this is the level of detail incorporated into the GADS program. The codes
in the blocks are the GADS event types.
Notice on the diagram that D4 (maintenance derating) and MO (maintenance outage) are classified as both
“unplanned” and “scheduled.” Standard 762 classifies these types of events as “unplanned.” GADS recognizes
that, historically, many operating companies referred to these events as “scheduled” and continue to do so. Both
classifications are shown here to illustrate the relationship between unplanned and scheduled events. The
evaluation of unit availability is not affected by the difference in terminology.
1. Outages
An outage exists whenever a unit is not synchronized to the grid system and not in a reserve shutdown state. The
general outage event classification is divided into seven distinct event types. Special instructions for reporting
testing during and following outages can be found on Page III-11.
An outage starts when the unit is either desynchronized from the grid or when it moves from one unit state to
another (for example, goes from a reserve shutdown to a maintenance outage.) The outage ends when the unit
is synchronized to the grid or moves to another unit state.
When a unit moves from one unit state to another, the exact date and time that the first outage ends will be the
same as when the second outage starts. The unit state can only be changed if the first outage ends. For example,
if the unit is forced off-line due to a water wall tube leak (just before it was to come off-line for a planned outage),
then the forced outage leak repair must be completed before the unit state can be changed from a U1 to a PO.
The maintenance crew can start the PO work, but it will not be a PO until the U1 outage work is complete and the
unit could be put back in service.
PO – Planned Outage
An outage that is scheduled well in advance and is of a predetermined duration, can last for several
weeks, and occurs only once or twice a year. Turbine and boiler overhauls or inspections, testing, and
nuclear refueling are typical planned outages. For a planned outage, all of the specific individual
maintenance and operational tasks to be performed are determined in advance and are referred to as
the "original scope of work." The general task of repairing turbines, boilers, pumps, etc. is not
considered a work scope because it does not define the individual tasks to be performed. For example,
if a general task such as repair boiler is considered the work scope, it is impossible to conclude that any
boiler work falls outside of the original scope of work. Discovery work and re-work which render the
unit out of service beyond the estimated PO end date are not considered part of the original scope of
work. A planned extension may be used only in instances where the original scope of work requires
more time to complete than the estimated time. For example, if an inspection that is in the original
scope of work for the planned outage takes longer than scheduled, the extra time should be coded as an
extension (PE). However, if damage found during the inspection results in an extension of the outage,
the extra time required to make repairs should be coded as a forced outage.
MO – Maintenance Outage
An outage that can be deferred beyond the end of the next weekend (defined as Sunday at 2400 hours
or as Sunday turns into Monday), but requires that the unit be removed from service, another outage
state, or Reserve Shutdown state before the next Planned Outage (PO). Characteristically, a MO can
occur any time during the year, has a flexible start date, may or may not have a predetermined duration,
and is usually much shorter than a PO. Discovery work and re-work which render the unit out of service
beyond the estimated MO end date are not considered part of the original scope of work. A
maintenance extension may be used only in instances where the original scope of work requires more
time to complete than the estimated time. For example, if an inspection that is in the original scope of
work for the outage takes longer than scheduled, the extra time should be coded as an extension
(ME). If the damage found during the inspection is of a nature that the unit could be put back on-line
and be operational past the end of the upcoming weekend, the work could be considered MO. If the
inspection reveals damage that prevents the unit from operating past the upcoming weekend, the
extended work time should be Forced Outage (U1).
Note: If an outage occurs before Friday at 2400 hours (or before Friday turns into Saturday), the above
definition applies. But if the outage occurs after Friday at 2400 hours and before Sunday at 2400 hours
(the 48 hours of Saturday and Sunday), the MO will only apply if the outage can be delayed past the next,
not current, weekend. If the outage cannot be deferred, the outage shall be a forced event.
The “predetermined duration” of an outage also determines the “estimated completion date” of the PO or MO.
If the unit is scheduled for four weeks of repairs, then the unit is expected back in service at a certain date four
weeks after the start of the outage. In cases where the outage is moved up or back according to the needs of the
operating company, ISO, or power pool, then the start of the outage plus duration of the outage determines the
new completion date. As long as the outage is no longer than planned, the expected completion date is moved to
coincide with the predetermined duration period.
If the unit is on outage (for example, U1 outage due to a boiler tube leak) at the time the unit is scheduled to start
the PO or MO work, then the work on the cause of the outage (tube repairs) must be completed before changing
from the U1 outage to the PO or MO outage. PO and MO work can start but is not counted as PO or MO work until
the U1 repairs are complete.
All work during PO and MO events is determined in advance and is referred to as the “original scope of work.”
Use ME and PE only in instances where the original scope of work requires more time to complete than originally
scheduled. Where applicable, the extension of the planned or maintenance outage may be required to be
approved in advance by your power pool or ISO. Advance warning of an extension is very important. However,
GADS is not a dispatch-orientated database but rather an equipment-orientated one. The reporting of the PE and
ME is based on IEEE 762-GADS rules, not ISO requirements. Therefore, if the extension meets the GADS rules, then
report it as an ME or PE and not a U1 when reporting to GADS only.
Do not use ME and PE in instances where unexpected problems or conditions are discovered during the outage
which render the unit out of service beyond the estimated end date of the PO or MO. Report these delays as
Unplanned (Forced) Outage-Immediate (U1). Do not use ME and PE if unexpected problems occur during unit
startup. If a unit completes a PO or MO before the original estimated completion date and volunteers to return
to service (i.e., the unit is released to dispatch), then any problems causing outages or deratings after that date
are not considered to be part of the PO or MO.
ME, PE or U1 must start at the same time (month/day/hour/minute) that the PO or MO ended. See Appendix G,
Example 7, Pages G-26 to G-27.
SF – Startup Failure
This is an outage that results when a unit is unable to synchronize within a specified startup time
following an outage or reserve shutdown.
The startup period for each unit is determined by the operating company. It is unique for each unit, and
depends on the condition of the unit at the time of startup (hot, cold, standby, etc.). A startup period
begins with the command to start and ends when the unit is synchronized. SF begins when a problem
preventing the unit from synchronizing occurs. The SF ends when the unit is synchronized, another SF
occurs, or the unit enters another permissible state.
There is a need by a number of the NERC Planning Committee working groups and subcommittees to
collect the various types of trips experienced by generating units. They are most interested in automatic
grid separation trips caused by many things, including transmission. In order to maintain the historical
meanings of the existing component trip codes 82 and 83, GADS created the two amplification codes T1
and T2 to be used for complete, 100% unit trips:
T1 - Tripped/shutdown grid separation --- automatic. A full outage that suddenly trips the unit
from some loading to zero loading without operator initiation. This is an unexpected grid
separation event where the unit is in normal operation when the mechanical, electrical, or
hydraulic control or protective systems automatically trip the generating unit(s). This trip is not
when the unit is manually tripped, or when the unit operator assisted to lower loadings and then
the unit automatically tripped. The unit must be in service (breakers closed) before a grid
separation trip event is accepted by GADS. No other unit outage condition can precede this event.
T2 - Tripped/shutdown grid separation --- manual. The unit is quickly removed from service with
operator assistance. This type of outage includes operator-initiated trips in response to unit alarms.
If the cause of the trip is not known, then you can use amplification code 84 but it must be changed
to the appropriate amplification code (T1 or T2) before the end of the year to be acceptable by
GADS.
84 - Unknown – investigation underway (change this code once failure mechanism is determined)
If the U1 is not a trip but the result of a change of state (from planned outage to U1, for example),
then the amplification code can be any other amplification code if the operating company chooses
to report it. In other words, the amplification code under such conditions is voluntary.
Starting January 1, 2011, the need to report T1, T2 or 84 amplification codes became mandatory to
pass GADS edits. For a complete list of the amplification codes see Appendix J of the GADS Data
Reporting Instructions.
It normally takes 36 hours to repair a tube leak. Therefore, the first 36 hours of the outage would be forced (U2)
outage. After the 36-hour period, the PO outage starts.
Scenario #2: Forced Outage that Can Wait for Repairs Until the End of the Next Weekend.
On a Thursday, Riverglenn #1 experiences a sudden increase in vibration in its ID Fan. The vibration is not severe
enough to trip the unit, but there are signs that the unit must be removed from service soon to check the problem
and make repairs. After some discussion, management decides Riverglenn can be removed from service next week
without further damage to the unit or endangering the safety of the personnel. On Friday, dispatch (or ISO) allows
Riverglenn to come down for repairs because another unit out for maintenance is now available for operation.
Even though Riverglenn came off-line the same week as its problem started, the outage is a maintenance outage
because it could have remained on-line until the end of the next weekend.
Scenario #3: Forced Outage that Cannot Wait for Repairs Until the End of the Next Weekend.
Jumbo #1, a gas turbine, began to vibrate on Friday. At first, the vibrations were not severe, but over the following
4 hours, the mils of vibration increased to where the unit needed to be removed from service. The unit continued
to generate until after the peak period was over. Jumbo was not needed again until the following Monday
afternoon. Shortly after the peak period, the operator tripped the unit.
Even though the unit was not needed until Monday, the unit could not have operated through the weekend
because of the vibration problem. Therefore, the outage is a forced outage and is enforced until the vibration
problem is solved.
Although the unit was not needed, the unit was not available due to management decision for the full 44 hours
and so the forced outage is reported from the time the unit came off-line until the unit was available for operation
(44 hours later). No part of the 44 hours is RS time. The RS time starts after the repairs and unit is available for
operation.
Scenario #5: Extending a Planned/Maintenance Outage When Work Is Part of Original Scope of Work.
During the planned overhaul of Riverglenn #1, the planned repairs to the electrostatic precipitator were more
extensive than expected. More parts were ordered to complete the repairs. However, unexpected longer repairs
to the ESP delayed the return to service for 3 additional days.
Since the ESP repairs were part of the original scope of work and the unit receives the okay for extension from its
ISO, the additional 3-day delay is the justification for the planned outage extension.
Scenario #6: Extending a Planned Outage when work is not part of original scope of work.
Part way through the planned outage of Riverglenn #1, the mechanics checked the packing on the boiler startup
feed pump and decided it best to replace it. It was not part of the original scope of work but was determined
important to prevent a future unit outage. As a result of the repairs and no packing on site, the PO was delayed
from returning to service on time for 12 hours.
All hours of the outage except the last 12 hours are PO. The last 12 hours is a Forced Outage because it 1) delayed
the startup of the unit and 2) was not part of the original work scheduled during the outage.
Scenario #7: Unexpected Repairs During Planned/Maintenance Outage But Completed Within the Scheduled
Outage Time.
Riverglenn #1 was in its annual overhaul when it was discovered that several blades on its ID fan needed
replacement. It was not part of the original scope of work to repair the blades, but parts were available through
the OEM and repairs to the fan were completed during the allotted planned outage time. There were no delays in
unit startup caused by the ID fan repairs.
Since the unit was not delayed from its scheduled startup due to the fan repairs, there was not penalty to the unit
because of the “surprise” repairs. The company reported the ID Fan repair as part of the “work completed during
the outage” section to GADS.
If you wish, you may report this type of testing separate from the outage event. In this case, the testing
period becomes a new event, the outage ending when the testing period begins. You must use the same
event type for the testing event as you did for the original outage (a PE or ME is not considered an original
outage — use the PO or MO event type, as appropriate). The testing event ends when the unit is
synchronized or placed in another unit state.
REPORT ALL OMC events to GADS, and they should not be classified as reserve shutdown or non-curtailing events.
The GADS software in appendix F will allow calculations of events with and without OMC events. The use of
equations without OMC events is left to the decision of plant and corporate management.
When reporting pumped storage units to GADS, know that NERC is more interested in the generating aspect of
pumped storage units than the non-generating mode. Therefore, if the unit is prevented from generating power,
then those events must be reported to GADS using the standard procedures.
In the case where the pumped storage unit cannot operate in the non-generating mode but can operate in the
generating mode, then the operator can report the problem in either one of two ways: 1) report the non-
generating mode equipment failure as a non-curtailing (NC) event, or 2) don’t report the problem to GADS. NERC
prefers option #1, but it is up to the reporter to choose to report the NC events or not.
If the case where the pumped storage unit cannot operate in the generating mode but either can or cannot
operating in the non-generating mode, then the event must be reported using the normal outage procedure. NC
event types are not appropriate in this case. The event should describe the reason why it cannot generate
electricity.
2. Deratings
A derating exists whenever a unit is limited to a power level that is less than the unit’s net maximum capacity.
Similar to outages, the general derating event classification is divided into distinct event types, based on IEEE
Standard 762.
A derating starts when the unit is not capable of reaching 100% capacity. The available capacity is based on the
output of the unit and not on dispatch requirements. The derating ends when the equipment that caused the
derating is returned to service, whether it is used at that time by the operators or not. More than one derate can
occur at one time. The reporter chooses the order of reporting. Events are sorted on the date and time the event
starts.
If a derating is less than 2% of the unit’s Net Maximum Capacity (NMC) and less than 30 minutes in duration, then
report the derating at your discretion (optional). Otherwise, all other deratings shall be reported to GADS. For
example, a derate that is 10% of the NMC but last 10 minutes should be reported to GADS, and a derate that is
1% of the NMC but last 6 hours should be reported to GADS.
Do not report deratings caused by ambient-related conditions or system dispatch requirements (see notes on
reporting deratings, Page III-14).
PD – Planned Derating
This is a derating that is scheduled well in advance and is of a predetermined duration.
Periodic deratings for tests, such as weekly turbine valve tests, should not be reported as PD’s. Report
deratings of these types as Maintenance Deratings (D4).
D4 – Maintenance Derating
This is a derating that can be deferred beyond the end of the next weekend (Sunday at 2400 or before
Sunday turns into Monday) but requires a reduction in capacity before the next Planned Outage (PO). A
D4 can have a flexible start date and may or may not have a predetermined duration.
Note: If a derate occurs before Friday at 2400 hours (or before Friday turns into Saturday), the above
definition applies. But if the derating occurs after Friday at 2400 hours and before Sunday at 2400 hours
(the 48 hours of Saturday and Sunday), the D4 will only apply if the derating can be delayed passed the
next, not current, weekend. If the derating cannot be deferred, the derating shall be a forced derating
event.
Use a DP only in instances where the scope of work requires more time to complete than originally
scheduled. Do not use a DP in instances when unexpected problems or delays outside the scope of work
are encountered that render the unit incapable of full load beyond the estimated end date of the PD. The
DP must start at the same time (month/day/hour/minute) that the PD ended.
Use a DM only in instances where the scope of work requires more time to complete than originally
scheduled. Do not use a DM in those instances where unexpected problems or delays outside the scope
of work are encountered which render the unit incapable of full load beyond the estimated end date of
the D4. The DM must start at the same time (month/day/hour/minute) that the D4 ended.
Although load following is not reported to GADS, any maintenance, testing, etc. done during the load following
period should be reported as an event. Under certain conditions, this work can be reported as a non-curtailing
event (NC). See Page III-18 for details.
Figure III-2 describes the relationships between maximum capacity, dependable capacity, and available capacity
as a result of deratings, and system dispatch requirements.
If a unit ramps up to the full load level OR up to the level of required load within the “normal” time period — set
by the operators of the unit — following a full outage, there is no derating on the unit from the time of
synchronization to the load point.
If the unit takes longer than normal ramp up time to the full load level OR up to the required load, then there is a
derating. The generating capacity of the unit at the end of the normal period will be the level of the derate and
the derate will last until the unit can either reach full load capability or level of required load.
FOR ALL UNITS EXCEPT NUCLEAR: There is no derating for unit shutdown. Each unit must be shut down safely,
without damaging equipment or posing a safety hazard to personnel. Some shutdowns are quick as a unit trip;
others are slower such as coast down to unit planned outages. In either case, the unit is not derated.
FOR NUCLEAR UNITS: Coast down to refueling may take weeks, depending on the operation of the unit. If the unit
can recover from coast down and can still produce 100% capability during coast down, there is no derating. If the
unit is not capable of 100% capacity, the derate is at the level of capability until the unit is taken off-line.
Overlapping Deratings
Deratings often overlap each other in duration. GADS considers all deratings additive except those which are
masked (shadowed) by an outage or a larger derating for their entire duration. This means the derating that
started first is assumed to be the primary cause of the load reduction until it terminates or a full outage begins.
Follow the criteria described below when reporting overlapping deratings:
a) Deratings that are masked (shadowed) for their full duration by outages or larger deratings are
considered non-curtailing in nature; meaning they do not affect the available capacity of the unit.
Report these situations using one of the two options shown below:
Report deratings of this type as derating events. If you choose this option, you must estimate the
available capacity resulting from the derating (see below) since it cannot be readily observed. The
calculation of equivalent derated hours will not be affected if shadowed deratings are reported in
this manner.
Instead of reporting these kinds of deratings as events, you may report them on Section D of the
Event Report that describes the outage or larger derating. See Appendix G, Example 4, Pages G-18
to G-19.
b) Report deratings that are masked (shadowed) due to operation in a load-following mode as
individual events. You must estimate the available capacity (see below and Page III-17) because it
cannot be readily observed.
c) Because of the additive assumption, GADS computer programs automatically increase the available
capacity of a unit when one derating ends while another is still in progress. See Appendix G, Example
3C, Pages G-12 to G-14. If the available capacity of the unit cannot be increased because of the
severity of the derating still in progress, you must indicate this by “artificially” ending the derating
in progress and reporting a “new” derating. For further discussion, see Appendix G, Example 3D,
Pages G-15 to G-17.
Occasionally, two or more individual components will fail at the same time month/day/hour/minute). There are
two ways to report occurrences like these:
1. Report each component failure as a separate derating. Use engineering judgment to determine the
available capacity as a result of each. NERC processes the data first sorting by start date and time
then event number. This means that when start dates are identical, the GADS will process the
derating with the lower event number first.
2. Report one derating, but show one component as the primary cause of event and the other(s) using
Section D of the event report.
1. Report a new derating to GADS each time the available capacity of the unit changes.
2. Determine the unit’s average available capacity during the entire restricted period and report only
one continuous averaged derating event to GADS. The start and end dates of the averaged derating
event would be the start and end of the overall restricted period.
The averaging technique used to determine the unit’s available capacity involves first calculating the megawatt
hours (MWh) lost at each level of the derating, summing them, and then dividing by the number of hours in the
overall derating period. This calculation yields the average megawatts (MW) lost during the period, from which
the average available capacity of the unit during the period is determined. This is the only number you report in
Section B of the event report (see Page III-20).
A 1000 MW unit experienced a derating caused by a stack emission limitation over a ten day period (240
hours). During this period, the magnitude of the derating varied as follows:
During this time, the unit also experienced an Unplanned (Forced) Outage – Immediate (U1) event for 90
hours and a Reserve Shutdown (RS) event for 20 hours.
First, the total megawatt hours (MWh) lost at each derating level are calculated and summed:
(40 hours x 30 MW) + (10 hours x 50 MW) + (110 hours x 20 MW) + (80 hours x 40 MW) = 7100 total
MWh lost.
Next, the average megawatts (MW) lost over the 10-day period is calculated by dividing the total MWh lost
by the number of hours in the entire derating period:
Finally, the available capacity for the unit over the 10-day derating period is calculated by subtracting the
average MW lost from the unit’s dependable capacity.
Again, the start and end dates of this derating would be the start and end dates of the entire period. The
available capacity as a result of the event to be reported on the event report is 970.
Notice in the example that one outage and one reserve shutdown event also occurred during the period of
the stack emission limitation. It is important to note that deratings of the type described above exist even if
the unit is shut down, limited by a more severe derating, or masked by a reserve shutdown. For this reason,
the average megawatts lost over the 10-day period in the example is calculated based on the total number
of hours in the period (240), not just the number of hours the unit was synchronized. NERC computer
programs recognize any full power outages that occur during a continuous derating period and do not double-
count the overlapping periods when calculating performance indexes.
3. Reserve Shutdown - RS
This is an event where a unit is available for load but is not synchronized due to lack of demand. This type of event
is sometimes referred to as an economy outage or economy shutdown. If a unit is shut down due to any
equipment-related problems, whether or not the unit was needed by the system, report an Unplanned (Forced)
Outage, Maintenance Outage, or Planned Outage. Do not report a Reserve Shutdown.
While a unit is on RS, maintenance work is often performed that would have resulted in a unit outage or derating
had the unit been on-line. This work can be reported as part of the RS event if, at any time, the work can be
stopped or completed without preventing the unit from:
This criteria above remain the same whether or not the system needed the unit.
If the above criterion is met, report maintenance work done during the RS on the event report, section D
(beginning with record 04), using an event contribution code 3 – other components worked during event.
If maintenance work cannot be stopped or completed, the reserve shutdown condition of the unit changes and
an outage or derating must be reported. If the unit cannot be synchronized while the work is being performed, an
outage exists and the RS must end. If the unit cannot attain its available capacity while the work is being
performed, a derating exists. The RS event does not end, but report the derating as well. Estimate the available
capacity as a result of the derating.
4. Non-curtailing Event - NC
This is an event that occurs whenever equipment or a major component is removed from service for
maintenance, testing, or other purposes that do not result in a unit outage or derating.
An NC also can exist when a generating unit is operating at less than full capacity due to system dispatch
requirements. During this period, equipment can be removed from service for maintenance, testing, or other
reasons and be reported as an NC if both the following conditions are met:
a) The available capacity of the unit is not reduced below what is required by system dispatch, and
b) Maintenance work can be stopped or completed and the unit can reach its net dependable
capacity (NDC) level within its normal ramp-up time if and when the system needs the unit.
If the conditions cannot be met, report an outage or derating event rather than an NC.
B. Event Magnitude
GADS uses the information in this section to determine the impact of the event identified in Section A on the unit.
This section is located on record 01 of the event report. See Figure III-5.
B – Event Magnitude
(Blank Columns) 20 28
(Blank Columns) 1 68
(Blank Columns) 11 70
Outages — time the unit was desynchronized (either operator or equipment initiated) or entered the
outage state from another state.
Deratings — time the system, major component, or piece of equipment became unavailable for service
affecting an actual or potential loss of unit capacity.
Reserve Shutdowns — time the unit was desynchronized or entered the reserve Shutdown State from
another state.
Non-curtailing Events — time the system, major component, or piece of equipment became unavailable for
service (either operator or equipment initiated).
Use a 24-hour clock to record time. Record midnight as 2400 and the beginning of a new day as 0000. For an
event that began on July 31 at 3:26 p.m., the start of event is recorded as:
07 31 15 26
TO
FROM U1 U2 U3 SF MO PO ME PE RS DM DP
U1 – Immediate Yes No No Yes Yes Yes No No Yes
U2 – Delayed Yes No No Yes Yes Yes No No Yes
U3 – Postponed Yes No No Yes Yes Yes No No Yes
SF - Startup Failure Yes No No Yes Yes Yes No No Yes
MO – Maintenance Yes No No Yes Yes Yes Yes No Yes
PO – Planned Yes No No Yes No Yes No Yes Yes
ME – Maintenance Extension Yes No No Yes No No No No Yes
PE – Planned Extension Yes No No Yes No No No No Yes
RS – Reserve Shutdown Yes No No Yes Yes Yes No No Yes
D1 – Immediate No No
D2 – Delayed No No
D3 – Postponed No No
D4 – Maintenance IEEE Standard 762 does not recognize Yes No
PD – Planned transition to/of deratings from/to No Yes
DM – Maintenance Derating other event types except as shown.
No No
Extension
DP – Planned Derating
No No
Extension
“YES” denotes that a change from one event type to another without intervening synchronization is permissible,
and the end date of the first event can be the same as the start date of the successive event. “NO” indicates that
there is no relationship between the event types and individual events separated by some period of time must be
reported.
When there is no intervening synchronization between events, the start time of one event is the same as the end
time of the immediately preceding event.
Note: Effective January 1, 2005, the section “When to Adjust for Startups” (formally Figure III-7) was removed from
the GADS DRI. The rule for artificially adding start up times to events moving from one event type to another was
untestable and unenforceable. The mass majority of reporters were not following the rules and only a few (as
surveyed at annual workshops) were. Therefore, to allow equal reporting rules, the section was dropped.
Outages — time the unit was synchronized or placed in another appropriate unit state.
Deratings — time the system, major component, or piece of equipment became available for service affecting
an actual or potential increase in unit capacity.
Section III – Event Reporting
Reserve Shutdowns — time the unit was synchronized or placed in another appropriate Unit State.
Non-curtailing Events — time the system, major component, or piece of equipment became available for
service.
For events that extend through multiple quarters within the same year, do not wait until the event is over before
reporting it to GADS. Instead, report the event and leave the end date blank. When the event does end, submit
the end date as a revision, following the instructions on Pages III-3. Every event must have an end date at the end
of every year.
For events that continue into the new year, enter the end date as 12312400. Restart the event in the new year
with a start date of 01010000.
Take care to change the Year (Section A, columns 9-12) to reflect the current year, and assign a new event number
(Section A, columns 13-16).
In addition to the year, event number, and start date, the “new” event being carried into the new year must:
Enter the capacity that is available from the unit given the restriction imposed by the derating event being
reported. This is the capacity after the reduction has been taken into account. Complete these fields only when
the event type is a derating.
The GAC is the greatest capacity at which the unit can operate during the period of restriction caused by the
derating. The NAC is the GAC less any capacity utilized for station service or auxiliary loads.
Either the GAC, the NAC, or both must be completed when the event type is a derating. Net data is required. If
you voluntarily report the gross available capacity (GAC) then you must report, gross maximum capacity (GMC),
gross dependable capacity (GDC), and gross actual generation (GAG) on the performance report (95). Data
consistency is necessary to calculate availability statistics.
See Notes on Reporting Deratings, Pages III-14 to III-17, for more information concerning the reporting of
deratings.
Dominant Derating Code (Record 01, column 69) – Voluntary but strongly recommended.
The purpose of the dominant derating code is to mark the dominate derating if more than two deratings are
occurring at the same time. By marking the dominate derate, the computer program will process the cause code
for that dominate derating for its full impact and not hide part of the impact credited to other derates. Unit
performance statistics will not be affected. Cause code statistics will be more accurate by recording the true
frequency and impact of the dominate derate.
Use the Dominant Derating Code in the unused column 69 of record 01. Identify a dominant derate with a “D”.
One example of how two derates should be reported to GADS – one without the Dominant Derating Code and
one with the Dominant Derating Code – is shown in Figure III-4.
Capacity (MW)
700
Event #1 Event #3 D4-CC 3112
600
Event #2
500
D1-CC 3410
400
“Without” Dominant Derating Code
300
3 events to cover 2 incidents
Capacity (MW)
700
Event #1 Event#2
Event #2 D4–CC 3112
600
500
D1-CC 3410
400
“With” Dominant Derating Code
300
2 events to cover 2 incidents
Figure III-4: Example of Dominant Derating Code Reporting
Use section C to detail the system, major component, or piece of equipment primarily responsible for causing
the event. You can find section C on records 02 and 03 of the event report (refer to Table III-4 on Page III-23).
You must complete one section C for every event submitted to GADS with the exception of reserve shutdown
events. Because the only “cause” of a reserve shutdown is economic, reporting section C is optional. Only one
section C may be reported for each event.
Use section D to report factors contributing to the cause of the event that are not primarily responsible; additional
components worked on while the event was in progress; factors significantly affecting the startup/ramping of the
unit; or, problems that extended the event. Section D begins with records 04 and 05 of the event report (refer to
Table III-5 on Page III-24).
Since you can use section D for several different reasons, multiple section D cards are allowed. Use only one
section D for each system, component, or piece of equipment you are describing. Up to 46 sets of section D records
(numbers 04-99) are allowed, so you can describe up to 46 different items.
Both sections C and D consist of two cards each, one even-numbered and one odd-numbered. Use the even-
numbered record, which contains information like man-hours worked, to begin the description of the causes or
contributing factors of the event. The odd-numbered record is used only to continue the description begun on the
even-numbered card. If additional space is not needed for a description, omit the odd-numbered record rather
than submit a blank one to GADS.
The first 19 characters (A – Event Identification) of each record (02-99) are identical to that of Record 01. These
19 characters link the records together.
Note: Never begin describing a new system, major component, or piece of equipment on an odd-numbered card.
Table III-4: Record Layout of Section C – Primary Cause of Event (Records 02 and 03)
Record 02
Column ID Number of Columns Starting Position
A – Event Identification
Record Code (required) 2 1
Utility (company) Code (required) 3 3
Unit Code (required) 3 6
Year (required) 4 9
Event Number (required) 4 13
Report Revision Code (voluntary) 1 17
Event Type (required) 2 18
C – Primary Cause of Event
System/Component Cause Code
4 20
(required)
Cause Code Amplification Code –
(required for U1 events coming from in
service 2 24
only; strongly recommended for all
other events.)
Time Work Started (voluntary) 8 26
Time Work Ended (voluntary) 8 34
(Blank Columns) 2 42
Event Contribution Code (voluntary) 1 44
Table III-5: Record Layout of Section D – Additional Work During Event (Records 4+
and 5+)
Records 04+ (Even Numbered)
Column ID Number of Columns Starting Position
A – Event Identification
Record Code (required) 2 1
Utility (Company) Code (required) 3 3
Unit Code (required) 3 6
Year (required) 4 9
Event Number (required) 4 13
Report Revision Code (voluntary) 1 17
Event Type (required) 2 18
Column ID Number of Columns Starting Position
D – Additional Work During Event
System/Component Cause Code
4 20
(required)
Cause Code Amplification Code
(Required for U1 events coming from
2 24
in service only; strongly
recommended for all other events.)
Time Work Started (voluntary) 8 26
Time Work Ended (voluntary) 8 34
(Blank Columns) 2 42
Event Contribution Code (voluntary) 1 44
Problem Alert (voluntary) 1 45
Man-hours Worked (voluntary) 4 46
Verbal Description (voluntary but
31 50
strongly recommended.)
Record Number (required) 2 81
Records 05+ (Odd Numbered)
Column ID Number of Columns Starting Position
A – Event Identification
Record Code (required) 2 1
Utility (Company) Code (required) 3 3
Unit Code (required) 3 6
Year (required) 4 9
Event Number (required) 4 13
Report Revision Code (voluntary) 1 17
Cycle/Co-Gen
Geothermal
Gas Turbine
Combine
Fluidized
Pumped
Nuclear
Storage
Hydro/
Diesel
Fossil
Bed
Cause Code Amplification Code (Record 02, columns 24-25) - Required for Unplanned (Forced)
Outages – Immediate (U1) events coming from in service to U1 only. No other amplification codes are
required for U1 or any other event type. It is strongly recommended for all other events but on a
voluntary basis only.
The purpose of the amplification code is to further identify the cause of an outage by describing the
failure mode. The amplification code is two alpha-numeric characters following the cause code. Failure
modes are leaks, corrosion, personnel error, fire, etc. They are almost identical to the GADS failure
mechanism codes (see Appendix H), except the amplification code is just two characters. Some existing
cause codes already contain these amplification codes as part of their description. The amplification
code allows all cause codes to be described with the set of failure modes without increasing the
number of cause codes. It will also allow analysts to further explore the common causes of outages.
You can find a list of the cause code amplification codes in appendix J.
Codes
Note: Event Contribution Codes 2, 3, and 5 can be reported on Section D cards, and may be used more than once.
Verbal Description (Record 02, columns 50-80; Record 03, columns 26-80) - Voluntary but strongly recommended.
GADS provides this space to allow you to give a more detailed explanation of the event and the cause(s) you
identified by system/component cause code(s). You can also use it to report the expanded data format as
described, beginning on Page III-29. Use only two sequential records (02-03, 04-05, etc.) to provide the
description for each cause code you report.
Your narrative should include a balanced description of the major aspects of the event, focusing on these key
areas: 1) failure description and appearance, 2) cause of immediate failure and contributing factors, and 3)
corrective actions. You have limited space available for your description, so NERC suggests using common
abbreviations as much as possible. Following the guidelines below will help you to develop a complete and
concise description encompassing the key areas noted below.
3. Corrective Actions
Record the actions taken to repair and correct the failure problem. If tests or recalibration are made to verify
that repairs are successful, note them as well. You may find the key words listed below useful to describe
corrective actions, but this list is by no means comprehensive. You may use these words as well as any others
you feel are appropriate.
As an example, a relay coil wire burns open because of electrical overload and has to be replaced. The failure
description would be “relay coil wire,” the appearance would be “burned open” and the cause would be
“electrical overload.” Corrective action would be “replaced.” The verbal description would be completed as
follows: “RELAY COIL WIRE BURNED OPEN-ELECTRICAL OVERLOAD REPLACED WIRE”
Reporting of this additional information is optional, although strongly encouraged. We believe the reporting of
this information will enhance the usefulness of our database and benefit the entire electric power industry. If
you choose to report this information to GADS, follow the instructions below (see Figure III-7 on Page III-30). If
you choose not to supply the additional data, report the verbal description as described on Page III-27.
Cumulative Fired Hours at Time of Event* (Record 02, columns 55-60) - Voluntary
Enter the cumulative number of fired hours the unit experienced at the time the event began. This data is taken
directly from the fired-hours meter typically located on the unit’s control panel. This meter clocks cumulative
operating hours since unit start-up. Report the fired hours in columns 55-60 of all even-numbered cards containing
a contribution code of 1 in column 44.
Cumulative Engine Starts at Time of Event* (Record 02, columns 61-65) - Voluntary
Enter the cumulative number of engine starts the unit experienced at the time the event began. This data is taken
directly from the engine starts counter, typically located on the unit’s control panel. This counter clocks cumulative
engine starts since unit start-up. The engine starts must be reported in columns 61-65 of all even-numbered cards
containing a contribution code of 1 in column 44.
Table III-7: Record Layout of Event Records Using Failure Codes
Record 02
Column ID Number of Columns Starting Position
A – Event Identification
Record Code (required) 2 1
Utility (Company)Code (required) 3 3
Unit Code (required) 3 6
Year (required) 4 9
Event Number (required) 4 13
Report Revision Code (voluntary) 1 17
Event Type (required) 2 18
C – Primary Cause of Event
System/Component Cause Code (required) 4 20
Cause Code Amplification Code (Required for U1 2 24
events coming from in service only; strongly
recommended for all other events.
Time Work Started (voluntary) 8 26
Time Work Ended (voluntary) 8 34
(Blank Columns) 2 42
Event Contribution Code (voluntary) 1 44
Problem Alert (voluntary) 1 45
Man-hours Worked (voluntary) 4 46
Failure Mechanism Code* (voluntary) 4 50
Trip Mechanism* (voluntary) 1 54
Cumulative Fired Hours at Time of Event* 6 55
(voluntary)
Cumulative Engine Starts at Time of Event* 5 61
(voluntary)
Verbal Description (Voluntary but strongly 15 66
recommended.)
Record Number (required) 2 81
Record 03
Column ID Number of Columns Starting Position
A – Event Identification
Repeat columns 1-19 from record numbers 01 and 02
C – Primary Cause of Event
System/Component Cause Code (required) 4 20
(Blank Columns) 2 24
Verbal Description (Voluntary but strongly 55 26
recommended.)
Record Number (required) 2 81
*Gas turbine and jet engine units only.
Reporting to the GADS program is now mandatory for all conventional units 20 MW and larger, starting January
1, 2013. Reporting the level of detail GADS Data Reporting Instructions requests enables you and other industry
analysts to perform detailed and useful analyses. Figure III-1 presents the classes of events generating companies
must report for different types and sizes of conventional, non-renewable generating units.
There are six distinct sections of the performance report: a) event identification; b) unit generation performance;
c) unit starting characteristics; d) unit time information; e) primary fuel; and, f) secondary fuel. together, these
sections provide an overall summary of the operating status of a unit.
The performance report (05) is divided into several sections. The different sections of the performance report are
on different records: Sections A, B, and C on Record 01, section d on record 02, and sections E and F on records
03 and 04. unless otherwise stated, do not zero fill or asterisk fill unused data fields in any section of the
performance report.
NERC invites Generator Owners and Operators to report on units that have a nameplate capacity of 20MW or less
on a voluntary basis.
A description of each section and the data elements within it follows. Included are detailed instructions for
reporting each performance data element.
A. Unit Identification
There are six data elements, referred to as “fields,” in this section. See Table IV-1. These elements form a “key”
— an identifier that makes each performance record unique from all others in the database. This key is referenced
at the beginning of every record used to report performance data.
Section IV – Performance Reporting
A – Unit Identification
Year (required) 4 9
The first time you submit a performance report to GADS it is called an “original.” Give all original reports a revision
code of zero (0).
Use the following codes when making changes to an original performance report:
1, 2, . . . 9 Use these codes when making corrections or additions to original performance reports.
Each time you make a change, you must increase the revision code by one. You can make
up to nine corrections and additions to an original report.
When making corrections or additions to an original report, you need to send GADS all
records relating to the performance report you intend to change. On the record:
1. Complete columns 1-14, repeating the information from the original report;
3. Make sure the same record number used in the original report is in columns
124-125. Do not leave the record number blank; and
To delete data from one or more data fields, GADS recommends that you resubmit the
entire data set–year-to-date–for that unit (or all units you report) to GADS. This
procedure will insure that both you and the GADS database have the same records on
file. You also have the option to find the record that has the highest revision code and
then increase this number by one or set all revision codes back to zero.
The GMC of a unit should change only as a result of a new performance tests or permanent unit modifications.
Never change the GMC due to equipment problems even if they persist for a lengthy period of time unless the
unit is permanently modified as a result. If the unit is permanently modified, note changes in the unit’s design on
a new design data form and submit it to NERC-GADS for updating.
The GDC is the same in intent and purpose as the historically reported Maximum Dependable Capacity (MDC).
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.
For consistency in calculating statistics, if you report net actual generation (negative integer or positive integer),
you must also report NMC or NDC. Similarly, if you report net capacity value, you must also report net actual
generation.
Please note: If you only report either the gross or the net capacities, the GADS editing program will calculate any
missing GMC, GDC, NMC, or NDC using the following criteria:
Fossil, Nuclear, and Fluidized Bed: 5.0% difference between gross and net values
Gas Turbine/Jet Engine: 2.0% difference between gross and net values
Diesel: No difference between gross and net values
Hydro/Pumped Storage: 2.0% difference between gross and net values
Miscellaneous: 4.0% difference between gross and net values
For example, if you report a fossil unit’s NMC and NDC, then the program will take your NMC and multiply it by
1.05 to determine the new GMC. The same operation would occur for determining the GDC from the NDC
number.
If you report only one capacity (for example NMC), then the program will assume the NMC and NDC are equal and
will record the unit as such. It will then calculate the GMC and GDC using the calculation stated above.
If you think the differences between gross and net are different than the numbers stated above, then complete
all capacities (maximum and dependable) with the correct numbers. The computer will accept entered numbers
and will only calculate new numbers if the fields are blank, zero-fielded, or have an asterisk (*).
If the unit was off-line during the entire period, describe how the unit typically would have been loaded had it
been on-line.
• Repeated failures for the same cause without attempted corrective actions are considered a single start.
• Repeated initiations of the starting sequence without accomplishing corrective repairs are counted as a
single attempt.
If you abandon startup attempts, the unit is shut down for repairs, and then started at a future time, report two
startup attempts.
The number of actual unit starts must be less than or equal to the number of attempted unit starts.
Unlike the verbal description field on the event report (07), you must abbreviate your description to fit in columns
99-123. You may not use additional records.
The first 15 characters of Record 02 (A – Unit Identification) are identical to that of record 01. These 15 characters
link the records together.
For information regarding work done during Reserve Shutdowns, see Section III, Page III-17.
When calculating statistics involving maintenance outage hours, note that IEEE Standard 762 considers these
hours unplanned. The use of maintenance outage Hours in the GADS statistics is described in detail in Appendix
F.
1. Calculate the duration of each outage (PO, MO, ME, PE, U1, U2, U3, and SF) and reserve shutdown (RS)
reported as an event to the GADS database by subtracting the START OF EVENT from the END OF
EVENT. Convert this to hours.
2. Add the total number of hours during the month spent in each outage category (PO, MO, ME, PE, U1,
U2, U3, and SF) and the reserve shutdown category (RS). Round the resultant values to two decimal
places and enter in the appropriate fields in Section D of the Performance Report.
Month* Hours
January 744
February 672*
March 719 or 744** for 2007 and beyond
April 719 or 720** before 2007
May 744
June 720
July 744
August 744
September 720
October 744 or 745** before 2007
November 719 or 720** for 2007 and beyond
December 744
Year 8760*
Reporting E. Primary Fuel is required for all units except hydro/pumped storage units (optional for these units
only). If a unit was not operated during the reporting period, enter the type of fuel that would have been burned
in the unit had it been on-line.
Secondary, tertiary, and quaternary fuel sections are not used for hydro/pumped storage units, wind- or solar-
powered units, or nuclear units.
The first 15 characters of Records 03 and 04 (A – Unit Identification) are identical to that of Records 01 and 02.
These 15 characters link the records together.
Table IV-8: Record Layout of Section E – Primary Fuel; and F – Secondary Fuel
Records 03 and 04
Column ID Number of Columns Starting Position
A – Unit Identification
Record Code (required) 2 1
Utility Code (required) 3 3
Unit Code (required) 3 6
Year (required) 4 9
Report Period (required) 2 13
Report Revision Code (voluntary) 1 15
E – Primary Fuel
Fuel Code (required) 2 16
Quantity Burned (voluntary) 5 + 2 decimals 18
Average Heat Content (voluntary) 6 25
% Ash (voluntary) 2 + 1 decimal 31
% Moisture (voluntary) 2 + 1 decimal 34
% Sulfur (voluntary) 1 + 1 decimal 37
% Alkalines (voluntary) 2 + 1 decimal 39
Grindability Index / % Vanadium (voluntary) 2 + 1 decimal 42
Ash Softening Temperature (voluntary) 4 45
(Blank columns) 21 49
F – Secondary Fuel
Fuel Code (required) 2 70
Quantity Burned (voluntary) 5 + 2 decimals 72
Average Heat Content (voluntary) 6 79
% Ash (voluntary) 2 + 1 decimal 85
% Moisture (voluntary) 2 + 1 decimal 88
% Sulfur (voluntary) 1 + 1 decimal 91
% Alkalines (voluntary) 2 + 1 decimal 93
Grindability Index / % Vanadium (voluntary) 2 + 1 decimal 96
Ash Softening Temperature (voluntary) 4 99
(Blank columns) 21 103
Record Number (required) 2 124
Please Note: Performance record 04 for the tertiary and quaternary fuels is identical to performance record 03
Fuel Code (Records 03 & 04, columns 16-17 and 70-71) - Required
Enter the two-character code from the list below that identifies the fuels burned in the unit during the reporting
period.
Report in E. Primary Fuel the code for the fuel that made the greatest contribution to thermal generation during
the period. In F. Secondary Fuel, enter the code for the fuel that made the second greatest contribution to
generation. You can only report fuels used for ignition or warm-up in this section if there was no more important
secondary fuel. Tertiary and quaternary fuels, reported in Sections E and F on Record 04 of the Performance
Report, are those which made the third and fourth greatest contribution to generation, respectively.
Quantity Burned (Record 03 & 04, columns 18-24 and 72-78) - Voluntary
Enter the quantity of fuel consumed during the reporting period. Note, NERC-GADS computer programs recognize
a decimal place indicator that appears in the performance report. Therefore, enter a factor of the actual quantity
burned in this field. Use the following factors to determine the correct number to enter: 1,000 short tons (2,000
pounds) for coal; 1,000 barrels (42 gallons/barrel) for oil; and, 1,000,000 cubic feet for gas. Do not attempt to
manually enter a decimal place.
Example:
If coal is your primary fuel and the unit burned 900 tons of coal during the reporting period, enter 0000090
in columns 18-24 of record 03.
If oil is your primary fuel and the unit burned 900,000 barrels of oil, enter 0090000 in columns 18-24 of
Record 03.
When reporting data for geothermal units, enter in this field the quantity of steam brought into the plant from
the geothermal wells. The factor used to determine the number to enter is 1,000,000. Thus, 1,234,500,000 pounds
of steam is entered as 0123450 in columns 18-24 of Record 03.
Leave columns 18-24 blank when reporting data for nuclear units.
Average Heat Content (Records 03 & 04, columns 25-30 and 79-84) - Voluntary
Enter the average heat content for the fuel, to the nearest Btu/lb. of coal, Btu/gal. of oil or Btu/cu. ft. of gas. Enter
a weighted average if the heat content of the fuel varied.
When reporting data for geothermal units, enter the heat content calculated using the following equation:
For nuclear units, enter the Net Plant Heat Rate (Btu/kWh) in this field.
Coal Units Only: Grindability Index (Records 03 & 04, columns 42-44 and 96-98)* - Voluntary
If the fuel type has been identified as coal (CC) or lignite (LI), enter the weighted average grindability index of the
fuel burned during the period. When entering the grindability index, disregard the decimal point.
Oil Units Only: % Vanadium and Phosphorus (Records 03 & 04, columns 42-44 and 96-98)* - Voluntary
If the fuel type has been identified as oil (OO), kerosene (KE), JP4/5 (JP), or distillate oil (DI), enter the sum of the
average vanadium and phosphorus contents of the fuel to the nearest 0.1% (by weight) as obtained from an ash
analysis.
Ash Softening Temperature (Records 03 & 04, columns 45-48 and 99-102)* - Voluntary
Enter the average ash softening temperature (oF) of the fuel. This temperature should be determined under
reducing atmosphere conditions.
* Because the average heat content (Btu), ash, moisture, sulfur, alkalies, grindability index, vanadium and
phosphorus, and softening temperature values may change during a month due to new fuel supplies, etc., these
values should be weighted averages.
Example:
(15,000 Btu x 10 tons of coal + 18,000 Btu x 20 tons of coal)/30 tons of coal = Weighted Average Heat
Content. The shown on these sections indicates a computer-inserted decimal point. Do not manually insert
a decimal point. For example, a value of 6.8% would be entered as 068 in columns 45-48.
For years, GADS has been collecting additional design information using the forms in appendices E of the GADS
Data Reporting Instructions. This data provides information regarding installed equipment design and operating
characteristics of a unit and are used in special analyses as sorting criteria. Submittal of the additional design data
is solely voluntary. If you wish to send GADS the additional design data, complete the design data forms which
apply to the type of unit you are reporting, as detailed in table V-1. The appropriate design data forms for each
unit type are found in appendix E.
Table V-1: Location of Design Data Forms for Voluntary Design Reporting
Unit Type Pages
Fossil (Steam) E-FS-1 – 37
Fluidized Bed Combustion E-FB-1 – 49
Nuclear E-NU-1 – 7
Diesel E-DI-1 – 4
Hydro/Pumped Storage E-HY-1 – 5
Gas Turbine or Jet Engine E-GT-1 – 6
Combined Cycle and Co-generation Blocks E-CC-1 – 25
Miscellaneous E-MS-1 – 5
In 2011, GADS introduced design data collection software to make the collection of voluntary design data easier.
The software, unit design entry, has all the information in appendix E with drop-down options and other features.
For more information on the software, go to the GADS website. Contact a GADS staff member for a list of your
own units to view the design data already in GADS.
When completing the voluntary design data forms, only fill in the fields for which you have data. Do not zero fill
or asterisk fill any unused fields. In many cases, you will be asked to complete a data field by choosing one answer
from a list of alternatives. If none or all of the alternatives apply, enter a “9” in the data field. When you enter a
“9,” you must detail the correct information for that field on the reverse side of the design data form or attach an
addendum sheet.
To make a change to the voluntary design data after it has been submitted to GADS, follow the procedure
described below:
2. Fill in the utility and unit identification data in the appropriate fields.
3. Enter the new data in the appropriate fields on the design data form. If the change being
referenced defines a change in the unit's design, then also note the day, month, and year the
change was completed in the margin on the new form.
If a unit is deactivated (retired), continue to report that unit for the remainder of the calendar year using the
instructions shown on Section III of the GADS Data Reporting Instructions. Please fill out the unit information in
the Unit Purchase/Retirement section, and also the Unit Deactivation information.
If a unit is purchased, continue to report that unit for the remainder of the calendar month using the
instructions shown on Section III of the GADS Data Reporting Instructions. Submit the completed Change in Unit
Status Report Form to gads@nerc.net. Please fill out both sections of the Unit Purchase/Retirement section,
including original company and new company information. If you do not know who the new company is, please
contact NERC or your Regional Coordinator.
If a unit changes owners at a company level, but keeps the same utility and unit information, keep reporting
under the same utility and unit codes. Please fill out the NCR number information for Original Company NCR
Number and New Company NCR Number.
If a unit was previously retired but has come back into service, fill out the reactivation part on page A-3.
What major equipment work, if any, will be done while the unit is inactive?
What major equipment work, if any, was done while the unit was inactive?
When copying the GADS Data Reporting Instructions for distribution to individual plants, copy only the section(s)
of this appendix that are appropriate for the type(s) of unit(s) at each plant. Then the plant data reporter will have
only the codes needed to report events, and may avoid some data reporting errors.
Additional cause codes for combined cycle and co-generation units are shown on Pages B-CC-1 to B-CC-31. There
is also a section for geothermal units on Pages B-GE-1 to B-GE-16.
When reporting an event, select the code which best describes the cause or component responsible for the event.
The following criteria are to be used in selecting a code:
Assign the cause of the event to the major component or system that was responsible for the event, not
to an auxiliary component or operation that triggered the failure of a major component or system. For
instance, failure of an air line to one feedwater regulating valve may cause closure of that valve,
resulting in a boiler trip on low level. In this case, the cause code for the feedwater regulating valve
would be reported, not the code for the service air system. Note the fact that the valve closure was
triggered by an air line failure in the verbal description. On the other hand, if the feedwater regulating
valve closure had resulted from a complete loss of station air, the cause code for the station air system
would be reported as the primary cause of the event. In this case, the station air system problem causes
malfunctions of numerous valves and instruments throughout the plant, and no one major component
or system could be uniquely identified as causing the outage.
Report power supplies (motor control centers, breakers, etc.) which serve a particular component using
the code for that component. Report power supply systems that serve multiple components using the
code for the power supply system. For instance, if a breaker failure results in the loss of an FD fan, the
code for the FD fan would be used. However, if a problem in the AC power distribution caused not only
the loss of the FD fan but also the loss of several other major components, then use the code for AC
power distribution.
Report instruments or controls (such as pressure switches, pressure regulators, position indicators, etc.)
that are part of a particular fan, pump, or valve, using the code for that component. Codes have been
assigned to some control systems, such as feedwater control. Report all instruments, transmitters, logic
Appendix B – System/Component Cause Codes – Guide for Code Selection
modules, etc., associated with these systems using the code for that control system.
Use the codes for major overhaul only for non-specific overhaul work. Major repairs conducted during a
major overhaul are to be reported separately using the appropriate code(s). For example, consider the
case where a general turbine overhaul is conducted, during which reblading of a high pressure turbine
wheel is required. Use the code 4400 to report the overhaul and include such things as opening and
closing of the turbine, cleaning, and minor repairs as man-hours worked. Use the code 4012 to report
the reblading of the HP turbine wheel and include only the man-hours worked on the reblading in the
man-hours worked field.
Use the codes for “External” and “Safety, Regulatory, and Environmental” only when no other
system/component cause code applies. For instance, if stack emission limits are exceeded because of a
fault in the flue gas scrubber, use a scrubber code. However, if a new limit on emissions is imposed and
is exceeded even though the scrubber is functioning properly, then use an environmental code.
Cause Code
BOILER Ranges Page No.
BALANCE OF PLANT
STEAM TURBINE
Cause Code
GENERATOR Ranges Page No.
EXTERNAL
BOILER
• Boiler
• Boiler internals (tubes, refractory, supports, etc.)
• All the fuel handling, storage fuel preparation and burning equipment.
• The forced/induced draft air system.
• Slag and ash removal except for particulate and gas cleanup. These latter items are covered under
pollution control equipment.
• The main steam and reheat steam systems up to but not including the turbine stop or isolation valves.
• The feedwater system downstream of the final valve prior to entry into the economizer or boiler.
• Boiler blowdown systems.
• The startup bypass system including drains up to the heaters or condenser.
• Boiler water chemistry problems not due to problems in the condensate/feedwater system, the
chemical addition system, or the demineralizer/polisher system.
• The instruments and controls associated with the above equipment.
Burners
Cyclone
Main Steam
Desuperheaters/Attemperators
Startup Bypass
0630 Startup bypass system piping (including drain lines up to heaters or condenser)
0640 Startup bypass system valves
0650 Startup bypass tanks or flash tanks
0655 Steam by-pass system instrumentation and controls
0660 Other startup bypass system problems
Boiler Recirculation
Miscellaneous (Piping)
0860 Soot blowers - air (see code 3844 for air delivery system)
0870 Soot blowers - steam
0871 Soot blowers - sonic
0872 Soot blowers - water
0873 Soot blower drives
0876 Soot blower controls
0880 Fly ash Removal System (not precipitators, scrubbers, mechanical collectors, or baghouses)
0885 Fly ash Removal System – wet transport
0890 Bottom ash systems (wet or dry)
0891 Bottom ash hoppers (including gates)
0892 Bottom ash clinker grinders
0893 Bottom ash water pumps and motors
0894 Bottom ash piping and valves
0895 Ashpit trouble
0896 Bottom ash dewatering bin system, instruments and controls
0897 Bottom ash rotary (drag chain type) conveyor and motor
0898 Bottom ash pyrite hopper (pulverizer reject) system
0899 Bottom ash controls and instrumentation
0900 Slag-tap (cyclone furnace)
0910 Slag-tap (other than cyclone furnace)
0920 Other slag and ash removal problems
Flue Gas
1590 Stacks (use code 8430 for stack problems due to pollution control equipment)
1591 Stack damper and linkage
1592 Stack damper linkage motors
1599 Other miscellaneous boiler air and gas system problems
1700 Feedwater controls (report local controls --- feedwater pump, feedwater regulator valve, etc., ---
with component or system)
1710 Combustion/steam condition controls (report local controls --- burners, pulverizers, etc., --- with
component or system)
1720 Desuperheater/attemperator controls (not local controls)
1730 Boiler explosion or implosion
1740 Boiler gage glasses /level indicator
1741 Furnace and water gauge television auxiliary system
1750 Burner management system
1760 Feedwater instrumentation (not local controls)
1761 Combustion /Steam condition instrumentation (not local controls)
1762 Desuperheater/attemperator instrumentation (not local controls)
1799 Other boiler instrumentation and control problems
1800 Major boiler overhaul (720 hours or more) (use for non-specific overhaul only; see page B-FS-2)
1801 Minor boiler overhaul (less than 720 hours) (use for non-specific overhaul only; see page B-FS-2)
1810 Other boiler inspections
1811 Boiler Inspections – problem identification/investigation
1812 Boiler Inspections – scheduled or routine
1820 Chemical cleaning/steam blows
Boiler Water Condition
1900 Improper balance between tube sections not due to fouling or plugging
1910 Inadequate air not due to equipment problems
Miscellaneous (Boiler)
(use more specific codes - other slagging and fouling problems, other control problems, etc. - whenever
possible. Describe miscellaneous problems in the verbal description.)
BALANCE OF PLANT
Condensing System
Condenser Tubes and Support Equipment
Vacuum Equipment
Condenser Controls
3170 Condenser inspection (use code 3110 to report looking for tube leaks)
3171 Air-cooled condenser inspections
3180 Major condenser overhaul
3185 Water side cathodic protection
3186 Auxiliary condenser and associated equipment
3190 Air leakage (for losses not attributable to previously noted equipment related codes)
3199 Other miscellaneous condensing system problems
Condensate System
Polishers/Chemical Addition
Feedwater System
(excluding extraction or drain systems)
Extraction Steam
Electrical
Electrical (continued)
Auxiliary Systems
Auxiliary Steam
Service Air
Instrument Air
3898 Miscellaneous plant auxiliary process and services instrumentation and controls
3899 Other miscellaneous auxiliary system problems
STEAM TURBINE
Besides the turbine, this set includes the steam stop/control valves, turbine control system, and the turbine
auxiliaries. The extraction steam codes are contained in the Balance of Plant set.
Valves
Piping
Lube Oil
(do not include bearing failures due to lube oil)
Controls
4400 Major turbine overhaul (720 hours or longer) (use for non-specific overhaul only; see page B-FS-2)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hours) (use for non-specific overhaul only; see page B-FS-2)
4410 Turning gear and motor
4411 Steam turbine gear box (single shaft configuration)
4412 Steam turbine clutch (single shaft configuration)
4415 Shaft coupling mechanism
4420 Vibration of the turbine generator unit that cannot be attributed to a specific cause such as
bearings or blades (use this code for balance moves)
4430 Gland seal system
4450 Water induction
4460 Turbine overspeed trip test
4470 Differential expansion
4490 Turbine performance testing (use code 9999 for total unit performance testing)
4499 Other miscellaneous steam turbine problems
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note the
main leads up to and includes the generator output breaker in this set of codes.
Generator
Exciter
Cooling System
(report failures caused by water leaks into generator as codes 4500, 4510, etc.)
4610 Hydrogen cooling system piping and valves
4611 Hydrogen coolers
4612 Hydrogen storage system
4613 Hydrogen seals
4619 Other hydrogen system problems
4620 Air cooling system
4630 Liquid cooling system
4640 Seal oil system and seals
4650 Other cooling system problems
Controls
Miscellaneous (Generator)
Wet Scrubbers
Chemical Supply
Wet Scrubber
8200 Piping
8210 Valves
8220 Strainers or filters
8225 Drain pots
8230 Ducting
8235 Demister
8240 Bypass dampers
8250 Dampers other than bypass
8260 Scrubber booster I.D. fan (fan specific to the scrubber)
8261 Scrubber booster I.D. fan drive
* Use code 9510 for outages or deratings required to install pollution control equipment. Use codes 9600 to
9650 only when the pollution control equipment problems are not responsible for exceeding emission limits.
8262 Scrubber booster I.D. fan vibration (fan specific to the scrubber)
8264 Scrubber booster I.D. fan blades (fan specific to the scrubber)
8265 Scrubber booster ID fan dampers
8270 Scrubber booster F.D. fan (fan specific to the scrubber)
8271 Scrubber booster F.D. fan drive
8272 Scrubber booster F.D. fan vibration (fan specific to the scrubber)
8274 Scrubber booster F.D. fan blades (fan specific to the scrubber)
8275 Scrubber booster FD fan dampers
8280 Reagent feed piping
8290 Demister wash piping assembly
8299 Other piping, ducting, damper, and fan problems
Dry Scrubbers
Reagent\Slurry Supply
8522 Piping
8523 Valves
8524 Strainers or filters
8525 Ducting
8526 Dampers
8527 Other piping, ducting, and damper problems
Dry Scrubber
Precipitators
8800 Reagent
8801 Carrier gas
8802 Control system
8803 SNCR Performance testing
8809 Other SNCR problems
8810 Reactor
8811 Reagent
8812 Catalyst
8813 Injection grid piping/valves
8814 Catalyst support material
8815 Soot blowers
8816 Plugging
8817 Control system
8820 SCR NOx Ammonia injection grid piping/valves"
8821 SCR NOx Ammonia tanks, piping and valves (not injection)"
8822 SCR NOx Ammonia air blowers"
8823 SCR NOx Other ammonia system problems"
8825 Other SCR problems
CO Reduction
EXTERNAL
Use this set of codes to report events caused by external factors (flood, lightning, etc); economic factors (lack of
fuel, labor strikes, etc.); operator training; and transmission system problems external to the plant.
Catastrophe
9000 Flood
9001 Drought
9010 Fire including wildfires, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9031 Tornado
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Fuel Quality
(Use code 9600 to 9650 if the fuel quality results in excess stack emissions through no fault in the pollution
control equipment. Use the appropriate equipment code to report fouling and slagging.)
Miscellaneous (External)
9300 Transmission system problems other than catastrophes (do not include switchyard problems in
this category; see codes 3600 to 3629, 3720 to 3730)
9305 Ash disposal problem
9310 Operator training
9320 Other miscellaneous external problems
9340 Synchronous Condenser Operation
Regulatory
Stack Emission
(include exhaust emissions)
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
9997 NERC Reliability Standard Requirement
9998 Black start testing
9999 Total unit performance testing (use appropriate codes for individual component testing)
Cause Code
BOILER Ranges Page No.
BALANCE OF PLANT
Cause Code
STEAM TURBINE _Ranges Page No.
GENERATOR
EXTERNAL
BOILER
This set of codes contains the following:
Boiler.
Boiler internals (tubes, refractory, supports, etc.) .
All the fuel handling, storage fuel preparation, and burning equipment.
The forced/induced draft air system.
Slag and ash removal except for particulate and gas cleanup. These latter items are covered under
pollution control equipment.
The main steam and reheat steam systems up to but not including the turbine stop or isolation valves.
The feedwater system downstream of the final valve prior to entry into the economizer or boiler.
Boiler blowdown systems.
The startup bypass system including drains up to the heaters or condenser.
Boiler water chemistry problems not due to problems in the condensate/feedwater system, the
chemical addition system, or the demineralizer/polisher system.
The instruments and controls associated with the above equipment.
Burners
Cyclone
Main Steam
Desuperheaters/Attemperators
Startup Bypass
0630 Startup bypass system piping (including drain lines up to heaters or condenser)
0640 Startup bypass system valves
0650 Startup bypass tanks or flash tanks
0655 Steam by-pass system instrumentation and controls
0660 Other startup bypass system problems
Boiler Recirculation
Miscellaneous (Piping)
0860 Soot blowers - air (see code 3844 for air delivery system)
0870 Soot blowers - steam
0871 Soot blowers - sonic
0872 Soot blowers - water
0873 Soot blower drives
0876 Soot blower controls
0880 Fly ash Removal System (not precipitators, scrubbers, mechanical collectors, or baghouses)
0885 Fly ash Removal System – wet transport
0890 Bottom ash systems (wet or dry)
0891 Bottom ash hoppers (including gates)
0892 Bottom ash clinker grinders
0893 Bottom ash water pumps and motors
0894 Bottom ash piping and valves
0895 Ashpit trouble
0896 Bottom ash dewatering bin system, instruments and controls
0897 Bottom ash rotary (drag chain type) conveyor and motor
0898 Bottom ash pyrite hopper (pulverizer reject) system
0899 Bottom ash controls and instrumentation
0900 Slag-tap (cyclone furnace)
0910 Slag-tap (other than cyclone furnace)
0920 Other slag and ash removal problems
0990 Refractory
0991 Tube leaks
0992 Tube supports
0999 Other heat exchanger problems
Air Supply
Flue Gas
1590 Stacks (use code 8430 for stack problems due to pollution control equipment)
1591 Stack damper and linkage
1592 Stack damper linkage motor
1599 Other miscellaneous boiler air and gas system problems
1700 Feedwater controls (report local controls – feedwater pump, feedwater regulator valve, etc., – with
component or system)
1710 Combustion/steam condition controls (report local controls –burners, pulverizers, etc., – with
component or system)
1720 Desuperheater/attemperator controls
1730 Boiler explosion or implosion
1740 Gage glasses
1741 Furnace and water gauge television auxiliary system
1750 Burner management system
1760 Feedwater instrumentation (not local controls)
1761 Combustion /Steam condition instrumentation (not local controls)
1762 Desuperheater/attemperator instrumentation (not local controls)
1799 Other boiler instrumentation and control problems
1800 Major boiler overhaul (720 hours or longer) (use for non-specific overhaul only; see page B-FS-2)
1801 Minor boiler overhaul (less than 720 hours) (use for non-specific overhaul only; see page B-FS-2)
1810 Other boiler inspections
1811 Boiler Inspections – problem identification/investigation
1812 Boiler Inspections – scheduled or routine
1820 Chemical cleaning/steam blows
1900 Improper balance between tube sections not due to fouling or plugging
1910 Inadequate air not due to equipment problems
Miscellaneous (Boiler)
(use more specific codes – other slagging and fouling problems, other control problems, etc. – whenever
possible. Describe miscellaneous problems in the verbal description.)
BALANCE OF PLANT
Condensing System
Condenser Tubes
Vacuum Equipment
Condenser Controls
3170 Condenser inspection (use code 3110 to report looking for tube leaks)
3171 Air-cooled condenser inspections
3180 Major condenser overhaul
3185 Water side cathodic protection
3186 Auxiliary condenser and associated equipment
3190 Air leakage (for losses not attributable to previously noted equipment related codes)
3199 Other miscellaneous condensing system problems
Condensate System
Polishers/Chemical Addition
Feedwater System
(excluding extraction or drain systems)
Extraction Steam
Electrical
3600 Switchyard transformers and associated cooling systems – external (OMC)
3601 Switchyard transformers and associated cooling systems – external (not OMC)
3610 Switchyard circuit breakers – external (not OMC)
3611 Switchyard circuit breakers – external (OMC)
3612 Switchyard system protection devices – external (OMC)
3613 Switchyard system protection devices – external (not OMC)
3618 Other switchyard equipment – external (not OMC)
3619 Other switchyard equipment – external (OMC)
3620 Main transformer
3621 Unit auxiliaries transformer
3622 Station service startup transformer
3623 Auxiliary generators
3624 Auxiliary generator voltage supply system
3629 Other switchyard or high voltage system problems - external
3630 400-700-volt transformers
3631 400-700-volt circuit breakers
3632 400-700-volt conductors and buses
3633 400-700-volt insulators
3634 400-700-volt protection devices
3639 Other 400-700-volt problems
3640 AC instrument power transformers
3641 AC Circuit breakers
3642 AC Conductors and buses
3643 AC Inverters
3644 AC Protection devices
3649 Other AC instrument power problems
3650 DC instrument power battery chargers
3651 DC circuit breakers
3652 DC conductors and buses
3653 DC protection devices
3659 Other DC power problems
3660 4000-7000-volt transformers
3661 4000-7000-volt circuit breakers
3662 4000-7000-volt conductors and buses
3663 4000-7000-volt insulators
3664 4000-7000-volt protection devices
3669 Other 4000-7000-volt problems
3670 12-15kV transformers
3671 12-15kV circuit breakers
3672 12-15kV conductors and buses
3673 12-15kV insulators
3674 12-15kV protection devices
3679 Other 12-15kV problems
3680 other voltage transformers
3681 other voltage circuit breakers
3682 other voltage conductors and buses
3683 other voltage insulators
3684 other voltage protection devices
3689 Other voltage problems
3690 Station Service Power Distribution System, General
Auxiliary Systems
Auxiliary Steam
Service Air
Instrument Air
3898 Miscellaneous plant auxiliary process and services instrumentation and controls
3899 Other miscellaneous auxiliary system problems
STEAM TURBINE
Besides the turbine, this set includes the steam stop/control valves, turbine control system, and the turbine
auxiliaries. The extraction steam codes are contained in the Balance of Plant set.
Valves
Piping
Lube Oil
(do not include bearing failures due to lube oil)
4280 Lube oil pumps
4281 Lube oil coolers
4282 Lube oil conditioners
4283 Lube oil system valves and piping
4284 Lube oil pump drive
4289 Other lube oil system problems
Controls
4400 Major turbine overhaul (720 hrs or longer) (use for non-specific overhaul only; see page B-FS-2)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hrs) (use for non-specific overhaul only; see page B-FS-2)
4410 Turning gear and motor
4411 Steam turbine gear box (single shaft configuration)
4412 Steam turbine clutch (single shaft configuration)
4415 Shaft coupling mechanism
4420 Vibration of the turbine generator unit that cannot be attributed to a specific cause such as bearings
or blades (use this code for balance moves)
4430 Gland seal system
4450 Water induction
4460 Turbine overspeed trip test
4470 Differential expansion
4490 Turbine performance testing (use code 9999 for total unit performance testing)
4499 Other miscellaneous steam turbine problems
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note the
main leads up to and includesthe generator output breaker in this set of codes.
Generator
Exciter
Cooling System
(report failures caused by water leaks into generator as codes 4500, 4510, etc.)
Controls
Miscellaneous (Generator)
Wet Scrubbers
Chemical Supply
Wet Scrubber
8150 Tubes
8160 Mist eliminators/demisters and washdown
8199 Other scrubber problems
8200 Piping
8210 Valves
8220 Strainers or filters
8225 Drain pots
8230 Ducting
8235 Demister
8240 Bypass dampers
8250 Dampers other than bypass
8260 Scrubber booster I.D. fan (fan specific to the scrubber)
* Use code 9510 for outages or deratings required to install pollution control equipment. Use codes 9600 to
9650 only when the pollution control equipment problems are not responsible for exceeding emission limits.
Dry Scrubbers
Reagent\Slurry Supply
8522 Piping
8523 Valves
8524 Strainers or filters
8525 Ducting
8526 Dampers
8527 Other piping, ducting, and damper problems
Dry Scrubber
8528 Dry scrubber instruments and controls
8529 Gas dispersers
8530 Spray towers
8531 Spray machine/atomizer
8532 Spray machine/atomizer motors
8533 Spray machine/atomizer lubrication systems
8534 Spray machine/atomizer vibration problems
Precipitators
8800 Reagent
8801 Carrier gas
8802 Control system
8803 SNCR Performance testing
8809 Other SNCR problems
8810 Reactor
8811 Reagent
8812 Catalyst
8813 Injection grid piping/valves
8814 Catalyst support material
8815 Soot blowers
8816 Plugging
8817 Control system
8820 SCR NOx Ammonia injection grid piping/valves"
8821 SCR NOx Ammonia tanks, piping and valves (not injection)"
8822 SCR NOx Ammonia air blowers"
8823 SCR NOx Other ammonia system problems"
8825 Other SCR problems
CO Reduction
EXTERNAL
Use this set of codes to report events caused by external factors (flood, lightning, etc.); economic factors (lack of
fuel, labor strikes, etc.); operator training; and transmission system problems external to the plant.
Catastrophe
9000 Flood
9001 Drought
9010 Fire including wildfires, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9031 Tornado
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Fuel Quality
(Use code 9600 to 9650 if the fuel quality results in excess stack emissions through no fault in the pollution
control equipment. Use the appropriate equipment code to report fouling and slagging.)
Miscellaneous (External)
Regulatory
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
9997 NERC Reliability Standard Requirement
9998 Black start testing
9999 Total unit performance testing (use appropriate codes for individual component testing)
Cause Code
NUCLEAR REACTOR Ranges Page No.
BALANCE OF PLANT
STEAM TURBINE
Cause Code
GENERATOR Ranges Page No.
EXTERNAL
NUCLEAR REACTOR
This set of codes contains the following:
The reactor
The containment system
The reactor coolant system, including chemical, volume, and pressure control system
Safety systems, both electrical and mechanical
Residual heat removal systems
Closed loop cooling water for reactor systems
Service water for closed loop cooling and other reactor systems
Steam generators
Main steam systems up to the outboard containment isolation valve
Feedwater systems from the reactor or steam generator up to the outboard containment isolation
valve
Blowdown systems
Radioactive waste and off-gas systems
Core/Fuel
2010 Fuel failure, including high activity in Reactor Coolant System (RCS) or off-gas system
2020 Control rod pattern changes and control rod repatch. (Preconditioning following a pattern change
is to be reported using code 2031.)
2021 Power limited by rod pattern. (If rod pattern is limited by fuel limits, use appropriate code below.)
2030 Fuel limits - peaking factors
2031 Fuel preconditioning
2032 Fuel limits - MCPR (Minimum Critical Power Ratio - BWR units only)
2033 Fuel limits - MAPLHGR (Maximum Average Planar Linear Heat Generation Rate - BWR units only)
2034 Core tilt restrictions
2035 Core xenon restrictions
2036 End-of-life scram reactivity/rod worth restrictions
2037 Other fuel limits (use codes 9110 and 9120 for core coastdown, conservation, or stretch)
2040 Core physics tests
2050 Burnable poison problems including poison curtains
2060 Excore nuclear instrumentation
2061 Incore nuclear instrumentation
2062 Other fuel/core related instrumentation problems
2070 Normal refueling
2071 Refueling equipment problems
2072 Fuel storage
2080 Fueling machine and auxiliaries (CANDU)
2082 Fuel transfer problems (CANDU)
2090 Other core/fuel problems
Piping
Pressurizer
Valves
2600 High pressure safety injection, core injection, or core spray pumps (including RCIC)
2601 Motors for high pressure pumps
2602 Steam turbine drives for high pressure pumps (including RCIC)
2603 High pressure piping
2604 High pressure valves
2609 Other high pressure injection problems
2620 Low pressure safety injection, core spray, or decay heat pumps
2621 Motors for low pressure pumps
2622 Low pressure piping
2623 Low pressure valves
2624 Low pressure heat exchangers
2625 Accumulators (up to and including check valves)
Containment System
Auxiliary Systems (see codes 3110 to 3999 for other auxiliary systems)
Miscellaneous (Reactor)
2900 Reactor overhaul (use for non-specific overhaul only; see page B-FS-2)
2990 Plant radiation levels
2991 Radioactivity discharge levels to the environment
2995 Reactor performance testing (use code 9999 for total unit performance testing)
2999 Other miscellaneous nuclear reactor problems
BALANCE OF PLANT
Condensing System
Condenser Tubes
Vacuum Equipment
Condenser Controls
3170 Condenser inspection (use code 3110 to report looking for tube leaks)
3171 Air-cooled condenser inspections
3180 Major condenser overhaul
3185 Water side cathodic protection
3190 Air leakage (for losses not attributable to previously noted equipment related codes)
3199 Other miscellaneous condensing system problems
Condensate System
Polishers/Chemical Addition
Feedwater System
(excluding extraction or drain systems)
Extraction Steam
Auxiliary Systems
Auxiliary Steam
3830 Auxiliary boiler
3831 Auxiliary steam piping
3832 Auxiliary steam valves
3833 Auxiliary steam controls and instruments
3834 Auxiliary boiler tube leaks
3835 Auxiliary boiler burner management system
3836 Steam transfer to other unit
3839 Other auxiliary steam problems (also see extraction steam codes 3520 to 3529; startup bypass
codes 0630 to 0660; and soot blower steam code 0870)
Service Air
Instrument Air
3898 Miscellaneous plant auxiliary process and services instrumentation and controls
3899 Other miscellaneous auxiliary system problems
STEAM TURBINE
Besides the turbine, this set includes the steam stop/control valves, turbine control system, and the turbine
auxiliaries. The extraction steam codes are contained in the Balance of Plant set.
Valves
Lube Oil
(Do not include bearing failures due to lube oil)
Controls
4400 Major turbine overhaul (720 hours or longer ) (use for non-specific overhaul only; see page B-FS-2)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hours) ) (use for non-specific overhaul only; see page B-FS-2)
4410 Turning gear and motor
4411 Steam turbine gear box (single shaft configuration)
4412 Steam turbine clutch (single shaft configuration)
4415 Shaft coupling mechanism
4420 Vibration of the turbine generator unit that cannot be attributed to a specific cause such as bearings
or blades (use this code for balance moves)
4430 Gland seal system
4440 Moisture separator/reheater (nuclear including MSR drains, controls, etc.)
4445 Steam reheater
4450 Water induction
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note the
main leads up to and includes the generator output breaker in this set of codes.
Generator
Exciter
Cooling System
(report failures caused by water leaks into generator as codes 4500, 4510, etc.)
Controls
Miscellaneous (Generator)
EXTERNAL
Use this set of codes to report events caused by external factors (flood, lightning, etc.); economic factors (lack of
fuel, labor strikes, etc.); operator training; and transmission system problems external to the plant.
Catastrophe
9000 Flood
9001 Drought
9010 Fire including wildfires, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9031 Tornado
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Miscellaneous (External)
9300 Transmission system problems other than catastrophes (do not include switchyard problems in this
category; see codes 3600 to 3629, 3720 to 3730)
9310 Operator training
9320 Other miscellaneous external problems
Regulatory
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
9997 NERC Reliability Standard Requirement
9998 Black start testing
9999 Total unit performance testing (use appropriate codes for individual component testing)
DIESEL UNITS
INDEX TO SYSTEM/COMPONENT CAUSE CODES
(Unit Codes 400-499)
Cause Code
BALANCE OF PLANT Ranges Page No.
GENERATOR
DIESEL ENGINE
EXTERNAL
BALANCE OF PLANT
Electrical
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note the
main leads up to and includes the generator output breaker in this set of codes.
Generator
Exciter
Cooling System
(report failures caused by water leaks into generator as codes 4500, 4510, etc.)
Controls
Miscellaneous (Generator)
DIESEL ENGINE
Engine
Engine Auxiliaries
Engine Controls
5850 Governor
5855 Engine control system
5860 Control power transformer
5865 Synchronization system
5870 Other engine control problems
5880 Diesel engine unit overhaul
Miscellaneous (Diesel Engine)
5890 Major overhaul (use for non-specific overhaul only; see Page B-FS-2)
5895 Inspection
5990 Engine performance testing - individual engines (use code 9999 for total unit performance testing)
5999 Other miscellaneous diesel engine problems
Regulatory
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
9997 NERC Reliability Standard Requirement
9998 Black start testing
9999 Total unit performance testing (use appropriate codes for individual component testing)
EXTERNAL
Use this set of codes to report events caused by external factors (flood, lightning, etc.); economic factors (lack of
fuel, labor strikes, etc.); operator training; and transmission system problems external to the plant.
Catastrophe
9000 Flood
9001 Drought
9010 Fire including wildfires, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9031 Tornado
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Fuel Quality
(Use code 9605 to 9655 if the fuel quality results in excess stack emissions through no fault in the pollution
control equipment. Use the appropriate equipment code to report fouling and slagging.)
Miscellaneous (External)
9300 Transmission system problems other than catastrophes (do not include switchyard problems in this
category; see codes 3600 to 3629)
9310 Operator training
9320 Other miscellaneous external problems
9340 Synchronoous Condenser Operation
Cause Code
BALANCE OF PLANT Ranges Page No.
GENERATOR
HYDRO TURBINE/PUMP
EXTERNAL
BALANCE OF PLANT
Electrical
Auxiliary Systems
Auxiliary Steam
Instrument Air
3898 Miscellaneous plant auxiliary process and services instrumentation and controls
3899 Other miscellaneous auxiliary system problems
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note the
main leads up to and includes the generator output breaker in this set of codes.
Generator
4500 Rotor windings (including damper windings and fan blades on hydro units)
4510 Rotor collector rings
4511 Rotor, General
4512 Retaining Rings
4520 Stator windings, bushings, and terminals
4530 Stator core iron
4535 Stator, General
4536 Generator Heaters
4540 Brushes and brush rigging
4550 Generator bearings and lube oil system (including thrust bearings on hydro units)
4551 Generator bearings
4552 Generator lube oil system
4555 Bearing cooling system
4560 Generator vibration (excluding vibration due to failed bearing and other components)
4570 Generator casing
4580 Generator end bells and bolting
4590 Generator brakes
Exciter
Cooling System
(report failures caused by water leaks into generator as codes 4500, 4510, etc.)
Controls
Miscellaneous (Generator)
HYDRO TURBINE/PUMP
Turbine
7000 Shaft
7001 Shaft packing
7003 Lube oil system (use code 7007 to report bearing failures due to lube oil problems)
7007 Bearings
7008 Bearing cooling system
7009 Bearing oil system
7010 Runner cavitation damage
7011 Other runner problems
7012 Casing, wear ring, or liner cavitation damage
7014 Blade or bucket cracking
7020 Nozzle assembly
7030 Vibration (Only for unbalance, report bearing failure, etc., in appropriate category)
7040 Turbine overhaul
7050 Turbine governor
7052 Other turbine control problems (Report specific wicket gate controls, etc., using the code for the
appropriate equipment item.)
7053 Governor oil system
7070 Speed Increaser
7099 Other turbine problems
Water Supply/Discharge
7200 Major overhaul (use for non-specific overhaul only; see page B-FS-2)
7201 Inspection
7210 Canals (including siphons, radial gates, and spills)
7220 Unit out of service due to common penstock with unit under repair
7230 Pony motor (pumped storage units only)
7240 Powerhouse substructure
7299 Other miscellaneous hydro turbine/pump problems (use generator codes and balance of plant
electrical and auxiliary codes as appropriate)
7300 Routine Hydro Planned Outage (reoccurring schedule) (Use 4840 or 7201 for specific inspections.)
EXTERNAL
Use this set of codes to report events caused by external factors (flood, lightning, etc.); economic factors (lack of
fuel, labor strikes, etc.); operator training; and transmission system problems external to the plant.
Catastrophe
9000 Flood
9001 Drought
9010 Fire including wildfires, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9031 Tornado
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Miscellaneous (External)
9300 Transmission system problems other than catastrophes (do not include switchyard problems in this
category; see codes 3600 to 3629)
9310 Operator training
9320 Other miscellaneous external problems
9340 Synchronous Condenser Operation
9345 Pumping Operations
9350 Public Safety (water hazard or river rescue)
Use these codes only for events not directly attributable to equipment failures. Inspections or testing of certain
equipment due to regulation are reported using the appropriate equipment cause codes and the fact that it was
a regulatory requirement noted in the verbal description section.
Regulatory
9676 Noise limits (not for personnel safety) – hydro and pumped storage
9686 Fish kill – hydro and pumped storage
9696 Other miscellaneous operational environmental limits – hydro and pumped storage
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
Cause Code
BALANCE OF PLANT Ranges Page No.
GENERATOR
GAS TURBINE
EXTERNAL
Cause Code
Ranges Page No.
REGULATORY, SAFETY, ENVIRONMENTAL
BALANCE OF PLANT
Electrical
Auxiliary Systems
Auxiliary Steam
Service Air
Instrument Air
3898 Miscellaneous plant auxiliary process and services instrumentation and controls
3899 Other miscellaneous auxiliary system problems
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls.
Note the main leads up to and includes the generator output breaker in this set of codes.
Generator
Exciter
Cooling System
(report failures caused by water leaks into generator as codes 4500, 4510, etc.)
Controls
Miscellaneous (Generator)
GAS TURBINE
Inlet Air System and Compressors
(use HP compressor if only one)
Compressors
Exhaust Systems
5100 Chamber
5101 Hoods
5102 Vanes/nozzles
5103 Silencer
5104 Cones
5105 Diverter Dampers
5106 Exhaust Stack
5108 High engine exhaust temperature
5109 Other exhaust problems (including high exhaust system temperature not attributable to a specific
problem)
Auxiliary Systems
EXPANDER TURBINE
7800 Couplings
7810 Shaft
7820 Bearings
7830 Blades
7840 Discs
7850 Spacers
7860 Nozzles/vanes
7870 Heat shields
7880 Exhaust diffusers
7890 Seal oil system and seals
7900 Inner casing
7910 Outer exhaust casing
7920 Lube oil system
7930 Controls and instrumentation
7940 Evactor
7950 Major overhaul
7960 Other expander turbine problems
8800 Reagent
8801 Carrier gas
8802 Control system
8803 SNCR Performance testing
8809 Other SNCR problems
8810 Reactor
8811 Reagent
8812 Catalyst
8813 Injection grid piping/valves
8814 Catalyst support material
8815 Soot blowers
8816 Plugging
8817 Control system
8820 SCR NOx Ammonia injection grid piping/valves
8821 SCR NOx Ammonia tanks, piping and valves (not injection)
8822 SCR NOx Ammonia air blowers
8823 SCR NOx Other ammonia system problems
8825 Other SCR problems
EXTERNAL
Use this set of codes to report events caused by external factors (flood, lightning, etc); economic factors (lack of
fuel, labor strikes, etc.); operator training; and transmission system problems external to the plant.
Catastrophe
9000 Flood
9001 Drought
9010 Fire including wildfires, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9031 Tornado
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Fuel Quality
(Use code 9603 to 9653 if the fuel quality results in excess stack emissions through no fault in the pollution
control equipment. Use the appropriate equipment code to report fouling and slagging.)
Miscellaneous (External)
9300 Transmission system problems other than catastrophes (do not include switchyard problems in this
category; see codes 3600 to 3629)
9310 Operator training
9320 Other miscellaneous external problems
9340 Synchronous Condenser Operation
Regulatory
Stack Emission
(include exhaust emissions)
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
9997 NERC Reliability Standard Requirement
9998 Black start testing
9999 Total unit performance testing (use appropriate codes for individual component testing)
Cause Code
BALANCE OF PLANT Ranges PageNo.
GENERATOR
JET ENGINE
EXTERNAL
Cause Code
Ranges Page No.
REGULATORY, SAFETY, ENVIRONMENTAL
BALANCE OF PLANT
Electrical
Auxiliary Systems
Auxiliary Steam
Service Air
Instrument Air
3898 Miscellaneous plant auxiliary process and services instrumentation and controls
3899 Other miscellaneous auxiliary system problems
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note the
main leads up to and includes the generator output breaker in this set of codes.
Generator
Exciter
Cooling System
(report failures caused by water leaks into generator as codes 4500, 4510, etc.)
Controls
Miscellaneous (Generator)
JET ENGINE
Compressors
Turbine
(use HP if only one)
Exhaust Systems
5500 Chamber
5501 Hoods
5502 Vanes/nozzles
5503 Silencer
5504 Cones
5505 Diverter Dampers
5508 High engine exhaust temperature
5509 Other exhaust problems (including high exhaust temperature not attributable to a specific problem)
Auxiliary Systems
EXPANDER TURBINE
7800 Couplings
7810 Shaft
7820 Bearings
7830 Blades
7840 Discs
7850 Spacers
7860 Nozzles/vanes
7870 Heat shields
7880 Exhaust diffusers
7890 Seal oil system and seals
7900 Inner casing
7910 Outer exhaust casing
8800 Reagent
8801 Carrier gas
8802 Control system
8803 SNCR Performance testing
8809 Other SNCR problems
8810 Reactor
8811 Reagent
8812 Catalyst
8813 Injection grid piping/valves
8814 Catalyst support material
8815 Soot blowers
8816 Plugging
8817 Control system
8820 SCR NOx Ammonia injection grid piping/valves
8821 SCR NOx Ammonia tanks, piping and valves (not injection)
8822 SCR NOx Ammonia air blowers
8823 SCR NOx Other ammonia system problems
8825 Other SCR problems
CO Reduction
EXTERNAL
Use this set of codes to report events caused by external factors (flood, lightning, etc); economic factors (lack of
fuel, labor strikes, etc.); operator training; and, transmission system problems external to the plant.
Catastrophe
9000 Flood
9001 Drought
9010 Fire including wildfires, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9031 Tornado
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Fuel Quality
(Use code 9604 to 9654 if the fuel quality results in excess stack emissions through no fault in the pollution
control equipment. Use the appropriate equipment code to report fouling and slagging.)
Miscellaneous (External)
9300 Transmission system problems other than catastrophes (do not include switchyard problems in this
category; see codes 3600 to 3629)
9310 Operator training
9320 Other miscellaneous external problems
9340 Synchronous Condenser Operation
Regulatory
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
9997 NERC Reliability Standard Requirement
9998 Black start testing
9999 Total unit performance testing (use appropriate codes for individual component testing
Cause Code
GAS TURBINE Ranges Page No.
MISCELLANEOUS
Instruments and control 6200 B-CC-9
STEAM TURBINE
GENERATOR
Cause Code
HRSG BOILER Ranges Page No.
BALANCE OF PLANT
EXTERNAL
GAS TURBINE
Compressors
Turbine
(use HP if only one)
Exhaust Systems
5100 Chamber
5101 Hoods
5102 Vanes/nozzles
5103 Silencer
5104 Cones
5105 Diverter Dampers
5106 Exhaust Stack
5108 High engine exhaust temperature
5109 Other exhaust problems (including high exhaust system temperature not attributable to a specific
problem)
Auxiliary Systems
JET ENGINE
Compressors
5410 High pressure shaft
5411 High pressure bearings
5412 High pressure blades/buckets
5413 Other high pressure problems
5414 Compressor diaphragms/vanes
5420 Low pressure shaft
5421 Low pressure bearings
5422 Low pressure blades/buckets
5429 Other low pressure problems
5430 Supercharging fans
5435 Jet Engine Compressor Washing
5436 Compressor shaft and bearings for two-shaft machines
5439 Other compressor problems
Turbine
(use HP if only one)
Exhaust Systems
5500 Chamber
5501 Hoods
5502 Vanes/nozzles
5503 Silencer
5504 Cones
5505 Diverter Dampers
5508 High engine exhaust temperature
5509 Other exhaust problems (including high exhaust temperature not attributable to a specific
problem)
Auxiliary Systems
5510 Lube oil system
5516 Power Augmentation System Equipment
5520 Hydraulic oil system
5530 Starting system (including motor)
5540 Battery and charger system
5550 Turning gear and motor
5551 Load gear compartment
5560 Cooling and seal air system
5570 Cooling water system
5580 Anti-icing system
5590 Other auxiliary system problems
MISCELLANEOUS
6200 Combined cycle instruments and controls. (Report instruments and controls specific to the gas
turbine; steam turbine; boiler; generator; or balance of plant using the codes for the appropriate
piece of equipment.)
EXPANDER TURBINE
7800 Couplings
7810 Shaft
7820 Bearings
7830 Blades
7840 Discs
7850 Spacers
7860 Nozzles/vanes
7870 Heat shields
7880 Exhaust diffusers
7890 Seal oil system and seals
7900 Inner casing
7910 Outer exhaust casing
7920 Lube oil system
7930 Controls and instrumentation
7940 Evactor
7950 Major overhaul
7960 Other expander turbine problems
STEAM TURBINE
Besides the turbine, this set includes the steam stop/control valves, turbine control system, and the turbine
auxiliaries. The extraction steam codes are contained in the Balance of Plant set.
Intermediate-Pressure Turbine
Low-Pressure Turbine
Valves
Piping
Lube Oil
(do not include bearing failures due to lube oil)
Controls
4400 Major turbine overhaul (720 hours or longer) (use for non-specific overhaul only; see page B- FS-2)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hours) (use for non-specific overhaul only; see page B- FS-2)
4410 Turning gear and motor
4411 Steam turbine gear box (single shaft configuration)
4412 Steam turbine clutch (single shaft configuration)
4415 Shaft coupling mechanism
4420 Vibration of the turbine generator unit that cannot be attributed to a specific cause such as bearings
or blades (use this code for balance moves)
4430 Gland seal system
4450 Water induction
4460 Turbine overspeed trip test
4470 Differential expansion
4490 Turbine performance testing (use code 9999 for total unit performance testing)
4499 Other miscellaneous steam turbine problems
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note the
main leads up to and includes the generator output breaker in this set of codes.
Generator
Exciter
Cooling System
(report failures caused by water leaks into generator as codes 4500, 4510, etc.)
Controls
Miscellaneous (Generator)
6110 HP steam piping up to turbine stop valves – Greater than 600 PSIG
(see 0790 for piping supports)
6111 HP steam relief/safety valves
6112 Other HP steam valves (including vent and drain valves but not including the turbine stop valves)
6113 Other HP steam system problems
6114 HP steam isolation/boundary valves
6120 IP steam piping up to turbine stop valves – Between 200 & 600 PSIG
(see 0790 for piping supports)
6121 IP steam relief/safety valves
6122 Other IP steam valves (including vent and drain valves but not including the turbine stop valves)
6123 Other IP steam system problems
6124 IP steam isolation/boundary valves
6130 LP steam piping up to turbine stop valves – Less than 200 PSIG (see 0790 for piping supports)
6131 LP steam relief/safety valves
6132 Other LP steam valves (including vent and drain valves but not including the turbine stop valves)
6133 Other LP steam system problems
6134 Other main steam valves (including vent and drain valves but not including the turbine stop valves)
6135 LP steam isolation/boundary valves
HRSG Desuperheaters/Attemperators
6160 HP Startup bypass system piping (including drain lines up to heaters or condenser)- Greater than
600 PSIG
6161 HP Startup bypass system valves
6162 HP Startup bypass tanks or flash tanks
6163 Other HP startup bypass system problems
6164 HP startup bypass instrumentation and controls
6170 IP Startup bypass system piping (including drain lines up to heaters or condenser) – Between 200-
600 PSIG
6171 IP Startup bypass system valves
6172 IP Startup bypass tanks or flash tanks
6173 Other IP startup bypass system problems
6174 IP startup bypass instrumentation and controls
6180 LP Startup bypass system piping (including drain lines up to heaters or condenser) – Less than 200
PSIG
6181 LP Startup bypass system valves
6182 LP Startup bypass tanks or flash tanks
6183 Other LP startup bypass system problems
6184 LP startup bypass instrumentation and controls
Boiler Recirculation
Miscellaneous (Piping)
Air Supply
1590 Stacks
1591 Stack damper and linkage
1592 Stack damper linkage motors
1599 Other miscellaneous boiler air and gas system problems
1700 Feedwater controls (report local controls --- feedwater pump, feedwater regulator valve, etc., --- with
component or system)
1710 Combustion/steam condition controls (report local controls with component or system)
1720 Desuperheater/attemperator controls (not local controls)
1730 Boiler explosion or implosion
1740 Gage glasses
1750 Burner management system
1760 Feedwater instrumentation (not local controls)
1761 Combustion /Steam condition instrumentation (not local controls)
1762 Desuperheater/attemperator instrumentation (not local controls)
1799 Other boiler instrumentation and control problems
1800 Major boiler overhaul (720 hours or more) (use for non-specific overhaul only; see page B- FS-2)
1801 Minor boiler overhaul (less than 720 hours) (use for non-specific overhaul only; see page B- FS-2)
1810 Other boiler inspections
1811 Boiler Inspections – problem identification/investigative
1812 Boiler Inspections – scheduled or routine
1820 Chemical cleaning/steam blows
1900 Improper balance between tube sections not due to fouling or plugging
1910 Inadequate air not due to equipment problems
Miscellaneous (Boiler)
(use more specific codes - other slagging and fouling problems, other control problems, etc. whenever possible.
Describe miscellaneous problems in the verbal description.)
BALANCE OF PLANT
Condensing System
Condenser Tubes
Vacuum Equipment
Condenser Controls
3170 Condenser inspection (use code 3110 to report looking for tube leaks)
3171 Air-cooled condenser inspections
3180 Major condenser overhaul
3185 Water side cathodic protection
3186 Auxiliary condenser and associated equipment
3190 Air leakage (for losses not attributable to previously noted equipment related codes)
3199 Other miscellaneous condensing system problems
Condensate System
Polishers/Chemical Addition
Feedwater System
(excluding extraction or drain systems)
Extraction Steam
Electrical
Auxiliary Systems
Auxiliary Steam
Instrument Air
3898 Miscellaneous plant auxiliary process and services instrumentation and controls
3899 Other miscellaneous auxiliary system problems
6299 Other combined cycle block problems (Use other gas turbine problem codes, other steam turbine
codes, etc., whenever appropriate.)
6399 Other coal gasification equipment problems
8800 Reagent
8801 Carrier gas
8802 Control system
8803 SNCR Performance testing
8809 Other SNCR problems
8810 Reactor
8811 Reagent
8812 Catalyst
8813 Injection grid piping/valves
8814 Catalyst support material
8815 Soot blowers
8816 Plugging
8817 Control system
8820 SCR NOx Ammonia injection grid piping/valves
8821 SCR NOx Ammonia tanks, piping and valves (not injection)
8822 SCR NOx Ammonia air blowers
8823 SCR NOx Other ammonia system problems
8825 Other SCR problems
EXTERNAL
Use this set of codes to report events caused by external factors (flood, lightning, etc); economic factors (lack of
fuel, labor strikes, etc.); operator training; and transmission system problems external to the plant.
Catastrophe
9000 Flood
9001 Drought
9010 Fire including wildfires, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9031 Tornado
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Fuel Quality
(Use code 9600 to 9650 if the fuel quality results in excess stack emissions through no fault in the pollution
control equipment. Use the appropriate equipment code to report fouling and slagging.)
Miscellaneous (External)
9300 Transmission system problems other than catastrophes (do not include switchyard problems in this
category; see codes 3600 to 3629, 3720 to 3730)
9305 Ash disposal problem
9310 Operator training
9320 Other miscellaneous external problems
9340 Synchronous Condenser Operation
Regulatory
Stack Emission
(include exhaust emissions)
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
9997 NERC Reliability Standard Requirement
9998 Black start testing
9999 Total unit performance testing (use appropriate codes for individual component testing)
GEOTHERMAL UNITS
INDEX TO SYSTEM/COMPONENT CAUSE CODES
(Unit Codes 800–899)
Cause Code
BOILER Ranges Page No.
BALANCE OF PLANT
STEAM TURBINE
GENERATOR
MISCELLANEOUS - GEOTHERMAL
Cause Code
POLLUTION CONTROL EQUIPMENT Ranges Page No.
EXTERNAL
BOILER
Main Steam
Desuperheaters/Attemperators
BALANCE OF PLANT
Condensing System
Vacuum Equipment
Condenser Controls
Condensate System
Electrical
Auxiliary Systems
Auxiliary Steam
Service Air
Instrument Air
3898 Miscellaneous plant auxiliary process and services instrumentation and controls
3899 Other miscellaneous auxiliary system problems
STEAM TURBINE
Besides the turbine, this set includes the steam stop/control valves, turbine control system, and the turbine
auxiliaries. The extraction steam codes are contained in the Balance of Plant set.
Valves
Piping
Lube Oil
(do not include bearing failures due to lube oil)
Controls
4300 Turbine supervisory system (use codes 4290 to 4299 for hydraulic oil)
4301 Turbine governing system
4302 Turbine trip devices (including instruments)
4303 Exhaust hood and spray controls
4304 Automatic turbine control systems - mechanical
4305 Automatic turbine control systems - mechanical - hydraulic
4306 Automatic turbine control systems - electro-hydraulic - analog
4307 Automatic turbine control systems - electro-hydraulic - digital
4308 Automatic turbine control systems - digital control and monitoring
4309 Other turbine instrument and control problems
4310 Steam Turbine Control System - data highway
4311 Steam Turbine Control System - hardware problems (including card failure)
4312 Steam Turbine Control System - internal and termination wiring
4313 Steam Turbine Control System - logic problems
4314 Steam Turbine Control System – upgrades
4400 Major turbine overhaul (720 hours or longer) (use for non-specific overhaul only; see page B-FS-2)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hours) (use for non-specific overhaul only; see page B-FS-2)
4410 Turning gear and motor
4411 Steam turbine gear box (single shaft configuration)
4412 Steam turbine clutch (single shaft configuration)
4415 Shaft coupling mechanism
4420 Vibration of the turbine generator unit that cannot be attributed to a specific cause such as bearings
or blades (use this code for balance moves)
4430 Gland seal system
4450 Water induction
4460 Turbine overspeed trip test
4470 Differential expansion
4490 Turbine performance testing (use code 9999 for total unit performance testing)
4499 Other miscellaneous steam turbine problems
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note the
main leads up to and includes the generator output breaker in this set of codes.
Generator
Exciter
Cooling System
(report failures caused by water leaks into generator as codes 4500, 4510, etc.)
Controls
Miscellaneous (Generator)
MISCELLANEOUS - GEOTHERMAL
Plant and Auxiliaries
Wet Scrubbers
Chemical Supply
8010 Crushers/mills
8020 Mill slurry tanks supply problems
8030 Classifiers
8040 Slurry transfer pumps and motors
8050 Chemical unavailability
8099 Other chemical supply problems
Wet Scrubber
8200 Piping
8210 Valves
8220 Strainers or filters
8225 Drain pots
8230 Ducting
8235 Demister
8240 Bypass dampers
8250 Dampers other than bypass
8260 Scrubber booster I.D. fan (fan specific to the scrubber)
8261 Scrubber booster I.D. fan drive
*Use code 9510 for outages or deratings required to install pollution control equipment. Use codes 9600 to 9650 only when
the pollution control equipment problems are not responsible for exceeding emission limits.
8262 Scrubber booster I.D. fan vibration (fan specific to the scrubber)
8264 Scrubber booster I.D. fan blades (fan specific to the scrubber)
8270 Scrubber booster F.D. fan (fan specific to the scrubber)
8271 Scrubber booster F.D. fan drive
8272 Scrubber booster F.D. fan vibration (fan specific to the scrubber)
8274 Scrubber booster F.D. fan blades (fan specific to the scrubber)
8280 Reagent feed piping
8290 Demister wash piping assembly
8299 Other piping, ducting, damper, and fan problems
EXTERNAL
Use this set of codes to report events caused by external factors (flood, lightning, etc); economic factors (lack of
fuel, labor strikes, etc.); operator training; and, transmission system problems external to the plant.
Catastrophe
9000 Flood
9001 Drought
9010 Fire including wildfires, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9031 Tornado
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Miscellaneous (External)
9300 Transmission system problems other than catastrophes (do not include switchyard problems in this
category; see codes 3600 to 3629, 3720 to 3730)
9305 Ash disposal problem
9310 Operator training
9320 Other miscellaneous external problems
9340 Synchronous Condenser Operation
Regulatory
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
9997 NERC Reliability Standard Requirement
9998 Black start testing
9999 Total unit performance testing (use appropriate codes for individual component testing)
NERC assigns each utility participating in the Generating Availability Data System (GADS) a unique
identification code. This three digit code allows each system's data to be uniquely catalogued and filed in
the database. This appendix contains a list of the codes for each utility system presently participating or
assigned a NERC-GADS utility code.
Each utility participating in GADS assigns unique identification codes to its units. This three digit code
allows each unit's data to be uniquely catalogued and filed in the database.
Note that each utility must assign identification codes for individual units based on the following criteria:
Hydro/Pumped Storage
500 - 599
(Use 900-999 if additional numbers are needed)
Miscellaneous
(Multi-Boiler/Multi-Turbine, Geothermal, Combined Cycle Block, 800 - 899
Concentrated Solar Power, etc.)
212-840-1070; 212-921-1040
ReliabilityFirst (RF)
ReliabilityFirst
3 Summit Park Drive, Suite 600
Cleveland, Ohio 44131
216-503-0660
704-357-SERC(7372)
813-289-5644
651-855-1760
501-614-3200
512-583-4900
801-582-0353
This Appendix contains a list of major components by unit type. Report all work performed on these components
using the instructions in Section III “Event Reporting.”
Auxiliary systems or equipment used exclusively to support the major component are considered part of the major
component. For pumps, this would include items such as motors, steam turbines, couplings, and self-contained
lube oil systems. For turbines, it would include items such as the lube oil system, major isolation and control
valves, etc.. An auxiliary air system or a service water system is not considered a part of a major component.
Engines Generators
Startup System Exciter
Turbines Generators
Exciters
Appendix D – List of Major Components
This Appendix contains a list of major components by unit type. Report all work performed on these components
using the instructions given in Section III “Event Reporting.”
Auxiliary systems or equipment used exclusively to support the major component are considered part of the major
component. For pumps, this would include items such as motors, steam turbines, couplings, and self-contained
lube oil systems. For turbines, it would include items such as the lube oil system, major isolation and control
valves, etc.. The auxiliary air system or service water system is not considered a part of a major component.
Page
Manufacturers E-2
Manufacturers
01 General Electric
02 Westinghouse (Siemens Westinghouse)
03 Allis Chalmers (Siemens Westinghouse)
04 Stanley
05 Elliott
06 Electric Machinery
07 Gulf General
08 (Blank)
09 Other
10 ABB ASEA Brown Boveri
11 MAN
12 Parsons
13 Siemens (SiemensWestinghouse)
14 Allis Chalmers Kraftwork Unions (Siemens Westinghouse)
15 English Electric
Fuel Codes
BM Biomass
PC Petroleum Coke
CC Coal
PR Propane
LI Lignite
SL Sludge Gas
PE Peat
GE Geothermal
WD Wood
NU Nuclear
OO Oil
WM Wind
DI Distillate Oil (No. 2)
SO Solar
KE Kerosene
WH Waste Heat
JP JP4 or JP5
OS Other-Solid (Tons)
WA Water
OL Other-Liquid (BBL)
GG Gas
OG Other-Gas (Cu. Ft.)
Instructions
Use these forms to report design and installed equipment information for FOSSIL (steam) units. FOSSIL units are
units with a single steam generator connected to a single or cross-compound turbine generator drive train.
Report units that have multiple steam generators and/or multiple turbine generators connected by headers
using the forms found under the heading “MISCELLANEOUS.”
Data reported on these forms should reflect the current condition and design of the unit. Do not report data for
start-up equipment or equipment that is not used to carry normal load unless specifically requested.
Some data fields are designated as M1 and M2. These fields indicate that the equipment being reported may
have been supplied by more than one manufacturer. Use fields designated as M1 to report all the data
associated with one manufacturer’s equipment and M2 for the other
Unit name:
Regional Entity:
Subregion:
Data reporter:
Telephone number:
Date:
Appendix E – Unit Design Data Forms – Fossil Steam Units
1. Identification
A series of codes uniquely identifies your utility and units. NERC assigned a unique code to identify your utility. You
must assign the unique code that will identify the FOSSIL unit being reported. This code may be any number from 100
to 199 or 600 to 649. Enter the unique utility and unit code and the full name of the unit below:
Name of Unit
Criteria: a) The date the unit was first declared available for dispatch at some level of its capability, OR
b) The date the unit first operated at 50% of its generator nameplate megawatt capability (product of
the megavoltamperes (MVA) and the rated power factor as stamped on the generator nameplate(s)).
Architect/Engineer
Constructor
5. Boiler – Manufacturer
Enter the name of the manufacturer and the model or series name or number of the boiler:
Boiler manufacturer
6. Boiler – Enclosure
Is 50% or more of the boiler outdoors (not enclosed in building framing and siding)?
1 – Yes 2 – No
Enter the type of fuel firing system the unit was designed for:
A – Front OR Back – wall-mounted burners on either the front OR the back of the furnace.
B – Opposed – wall-mounted burners on BOTH the front and back of the furnace.
C – Vertical – burners are mounted on the ceiling of the furnace.
D – Tangential – firing from the corners of the furnace with burners capable of directing the fireball up
or down.
E – Cyclone – horizontal (burner) cylinders connected to furnace walls wherein fuel and air are
combusted in a controlled environment. Combustion gases exit through re-entrant throat into
furnace, and slag drains to slag tanks. Cyclone burners may be installed in either single walls or
opposed walls.
F – Concentric – staged combustion system, designed primarily for NO2 control, in which the walls are
blanketed with air.
G – Circulating fluidized bed – upward flow of air holds the fuel and sorbent particles (e.g., limestone)
in suspension in the combustion zone. Partially burned fuel passes into a collector and is routed
back into the combustion zone.
H – Bubbling fluidized bed – similar to circulating fluidized bed except the partially burned fuel is not
recirculated.
I – Stoker – overfeed method combined with suspension firing.
Enter the type of circulation the boiler was originally designed for:
1 – Natural (thermal) – water flows through furnace wall tubes unaided by circulating pumps.
Primarily used with subcritical units.
2 – Controlled (forced or pump assisted thermal) – water flows through furnace wall tubes aided by
boiler recirculation pumps located in the downcomers or lower headers of the boiler. Used on
some subcritical units.
3 – Once through – no recirculation of water through the furnace wall tubes and no steam drum.
Used on supercritical and some subcritical units.
1 – Injection (or injection seal) – controlled-leakage boiler recirculation pumps mounted vertically with
a rigid shaft designed to carry its own thrust.
2 – Leakless (or canned, canned-motor, or zero-leakage) – pump and its motor are an integral
pressurized sealed unit.
9 – Other, describe
Enter the type of furnace bottom the boiler was originally designed for:
1 – Dry bottom – no slag tanks at furnace throat area (throat area is clear). Bottom ash drops through
throat to bottom ash water hoppers. Design used when ash-melting temperature is greater than
temperature on furnace wall, allowing for relatively dry furnace wall conditions.
2 – Wet Bottom – slag tanks installed at furnace throat to contain and remove molten ash from the
furnace.
Fuel Characteristics
Average Heat Content in Fuel
(Btu/lb, Btu/bbl, Btu/CuFt)
% Ash Content (to one decimal place)
(Btu/lb,Btu/bbl,Btu/CuF
▲
▲
Conventional Burners
Primary fuel burner(s) manufacturer(s)
TOTAL number of primary fuel burners.
Low Nox Burners
Manufacturer(s)
Installation date:
Year Month Day
Manufacturer(s) of the motor(s) that drives the fuel oil burner supply
pump(s).
Igniter manufacturer
Enter the type of fuel the igniter(s) were originally designed for:
1 – Pilot torch lighter – an oil or gas igniter that uses an electric spark to ignite the fuel.
2 – Carbon arc – a carbon or graphite electrode that is energized and used to ignite the fuel.
3 – High energy arc – a low voltage, high energy pulse arc that is used to ignite the fuel.
4 – Plasma arc – a high dc voltage current used to ionize the air resulting in a high energy arc that
ignites the fuel.
9 – Other, describe
Feeder(s) manufacturer(s).
M1 M2
Enter the type of pulverizer or coal mill feeder(s) at the unit:
1 – Gravimetric belt – system that weighs the coal as it is fed to the pulverizer or coal mill.
2 – Volumetric belt – system that measures the volume of coal fed to the pulverizer or coal mill.
3 – Star roll – a multi-blade rotor that turns about a fixed, hollow, cylindrical core feeding a fixed
measure of coal.
4 – Rotating table – system that operates by piling coal on a rotating table, and, as the table rotates, a
stationary blade diverts the coal to a feed chute to the mill.
9 – Other, describe
Design coal flow rate in lb/hr (per pulverizer or coal mill) using design fuel.
M1 M2
Enter the type of pulverizer(s) or coal mill(s) at the unit:
1 – Ball – grinding elements are balls that operate freely in a race on a rotating grinding table.
2 – Roll race – rotating grinding table that moves coal through a series of rollers or wheels supported
within the pulverizer or coal mill.
3 – Ball tube (Hardinge) – horizontal, rotating, grinding cylinder containing steel balls that move within
the cylinder and grind or crush the coal.
4 – Impact (Attrition) – series of fixed or hinged hammers that rotate within a closed chamber
impacting and crushing the coal.
9 – Other, describe
Centrifugal – blades mounted on an impeller (or rotor) that rotates within a spiral or volute housing.
Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
M1 M2
Enter the type of exhauster fan(s) at the unit:
Centrifugal – blades mounted on an impeller (or rotor) which rotates within a spiral or volute housing.
Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
1 – Balanced draft – equipped with both induced draft and forced draft fans. The furnace operates at
positive pressure at air entry and negative pressure at flue gas exit.
2 – Pressurized draft – equipped with forced draft fans only. The furnace and draft system operate at
positive pressure.
IF the unit was designed as a pressurized draft unit and converted to a balanced draft design, enter the date the
conversion was completed:
M1 M2
Enter the type of forced draft fan(s) at the unit:
Centrifugal – blades mounted on an impeller (or rotor) which rotates within a spiral or volute housing.
Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
M1 M2
Enter the type of forced draft fan drives(s) at the unit:
Centrifugal – blades mounted on an impeller (or rotor) which rotates within a spiral or volute housing.
Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
M1 M2
Enter the type of induced draft fan drive(s) at the unit:
M1 M2
Enter the type of gas recirculating fan drive(s) at the unit:
1 – Single speed motor
2 – Two speed motor
3 – Variable speed motor
4 – Steam Turbine
9 – Other, describe
M1 M2
Enter the type of primary air heater(s) at the unit:
1 – Regenerative (Ljungstrom) – rotating heat exchanger that continuously rotates sections (baskets)
composed of metal plates from the hot flue gas furnace exit plenum to the furnace intake air
plenums.
2 – Tubular – hot flue gas from the furnace is channeled through tubes (vertical or horizontal) where
the heat is transferred to the furnace intake air passing across the outside of the tubes.
3 – Steam Coil – similar to tubular except steam is used to preheat the intake air.
4 – Regenerative (Rothemule)
9 – Other, describe
M1 M2
Enter the type of secondary air heater(s) at the unit:
1 – Regenerative (Ljungstrom) – rotating heat exchanger that continuously rotates sections (baskets)
composed of metal plates from the hot flue gas furnace exit plenum to the furnace intake air
plenums thus heating the intake air.
2 – Tubular – hot flue gas from the furnace is channeled through tubes (vertical or horizontal) where
the heat is transferred to the furnace intake air passing across the outside of the tubes.
3 – Steam Coil – similar to tubular except steam is used to preheat the intake air.
4 – Regenerative (Rothemule)
9 – Other, describe
Enter the type(s) of medium(s) used to blow the soot. If a variety of soot blowers are used at the unit, note the
number of each type used.
M1 M2 M3
1 – Steam
2 – Air
3 – Water
4 – Sonic
5 – Steam/Air
9 – Other, describe
Enter the location of the mechanical precipitator with respect to the air heaters:
Enter the location of the electrostatic precipitator with respect to the air heaters:
1 – Reverse – clean flue gas is blown in the direction counter to normal operation to remove fly ash
from the bag.
2 – Pulse (or pulse set) – short bursts of compressed air are blown into the bag to cause a momentary
expansion of the bag to dislodge the entrapped fly ash.
3 – Shaker – the bag is literally shaken to remove the fly ash collected on its surface.
9 – Other, describe
Centrifugal – blades mounted on an impeller (or rotor) which rotates within a spiral or volute housing.
Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
Was the FGD system a part of the original design of the unit? A “no” answer means the FGD system was a retrofit
after the unit entered service.
1 – Yes 2 – No
Reagent #1
Maximum design flue gas flow rate at the exit of the boiler in actual cubic feet per minute (ACFM).
Maximum design flue gas flow rate capable of passing through the FGD system in ACFM.
Percent of scrubber bypass capacity at compliance levels. (Enter 0% if no bypass capacity exists.)
Several towers may work together in series or in parallel to form a single FGD module with one or more modules
installed at a single unit. Enter the following information:
MINIMUM number of FGD fans required to obtain maximum capacity from the
unit.
M1 M2
Enter the type of FGD fan(s) at the unit:
Centrifugal – blades mounted on a impeller (or rotor) which rotates within a spiral or volute housing.
Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
M1 M2
Enter the location of the FGD fan(s) with respect to the FGD:
1 – Before
2 – After
9 – Other, describe
Enter the type of stack gas reheating method used at the unit:
1 – In-line – installation of a heat exchanger in the flue gas duct downstream of the mist eliminators.
2 – Direct combustion – firing of gas or oil burners and mixing product gases with the cooler scrubbed
flue gas.
3 – Indirect hot air – heating of ambient air in an external heat exchanger (using steam) and injecting
this heated air into scrubbed flue gas discharge.
4 – Waste heat recovery – use of unscrubbed flue gas in a heat exchanger to reheat the scrubbed
stack gas.
5 – Exit gas recirculation – a portion of the scrubbed gas is diverted from the exit stream, reheated by
a heat exchanger and then injected into the scrubbed flue gas before entering the stacks.
6 – Bypass reheater – bypass of a portion of the hot unscrubbed flue gas around the FGD system for
injection into the cooler scrubbed flue gas.
9 – Other, describe
1 – Impingement (or inertial impaction) – open or chevron vanes placed in the gas stream divert and
collect the mist on their surfaces and direct the droplets away.
2 – Electrostatic – mist removal through the use of an electrostatic field.
3 – Centrifugal – uses baffles that impart a centrifugal force on the gas.
4 – Cyclonic – uses tangential inlets which impart a swirl or cyclonic action to the gas as it passes
through the separator chamber.
9 – Other, describe
A “mist eliminator stage” is a single set of separate and distinct elements through which the flue gas must pass.
Enter the total number of mist eliminator stages on each FGD tower.
1– Yes 2 – No
Pressure (psig)
Back pressure of the high pressure condenser (if applicable) to the nearest one-tenth inch of
▲ mercury at the nameplate capacity and design water temperature.
Back pressure of the low pressure condenser to the nearest one-tenth inch of mercury at
▲ nameplate capacity and design water temperature.
The last stage blade length (inches) of the low pressure turbine, measured from hub to end of top
▲ of blade.
Manufacturer of the motor(s)/steam turbine(s) that drives the main lube oil
pump(s).
TOTAL number of steam turbine main lube oil pumps; include installed spares.
1 – Motor
2 – Shaft
3 – Steam turbine
9 – Other, describe
Generator manufacturer
1 – Yes 2 – No
RPM
Enter the mediums used to cool the generator’s stator and rotor:
A Air A
H Hydrogen H
O Oil O
W Water W
Exciter manufacturer
Enter the type(s) of exciter drive(s) used by the main exciter IF it is rotating:
1 – Shaft direct
2 – Shaft gear
3 – Motor
9 – Other, describe
TOTAL number of passes made by the circulating water as it passes through the
condenser.
TOTAL number of condenser shells.
Condenser tube materials used in the majority (50% or more) of the condenser
tubes.
Air ejector(s) or vacuum pump(s) manufacturer.
1 – Vacuum pump
2 – Steam jet air ejector
3 – Both
9 – Other, describe ___________________________________________________________
1 – River
2 – Lake
3 – Ocean or Bay
4 – Cooling Tower
9 – Other, describe
Enter the type of on-line main condenser cleaning system used at the unit:
Enter the following information about the condensate polishing system at the unit:
Enter the % of the condensate flow at maximum unit capacity that can be treated:
% Treated
▲
M1 M2
Specify coupling type used for feedwater (boiler feed) pump.
1 – Hydraulic
2 – Mechanical
9 – Other, describe
M1 M2
Enter the type of HIGH pressure feedwater heater(s):
M1 M2
Enter the type of INTERMEDIATE pressure feedwater heater(s):
M1 M2
Enter the type of LOW pressure feedwater heater(s):
Deaerator manufacturer(s)
M1 M2
Enter the type of deaerator heater(s):
1 – Spray – high-velocity stream jet atomizes and scrubs the condensate.
2 – Tray – series of trays over which the condensate passes and is deaerated.
3 – Vacuum – a vacuum condition inside the shell for deaeration.
4 – Combination
9 – Other, describe
M1 M2
Enter the type of cooling tower(s) used:
1 – Mechanical draft (induced, forced, cross-flow and counterflow) – fan(s) used to move ambient air
through the tower.
2 – Atmospheric spray – air movement is dependent on atmospheric conditions and the aspirating
effect of the spray nozzles.
3 – Hyperbolic (natural draft) – temperature difference between condenser circulating water and
ambient air conditions, aided by hyperbolic tower shape, creates natural draft of air through the
tower to cool the water.
4 – Deck-filled – wetted surfaces such as tiers of splash bars or decks aid in the breakup and retention
of water drops to increase the evaporation rate.
5 – Coil shed – a combination structure of a cooling tower installed over a substructure that houses
atmospheric coils or sections.
9 – Other, describe
The cooling tower booster pumps increase the pressure of the circulating water and force the water to the top of
the cooling tower.
Manufacturer(s) of the motor(s) that drives the cooling tower booster pump(s).
1 – Single phase
2 – Three phase
9 – Other, describe
M1 M2
1 – Yes 2 – No
M1 M2
Enter the number of plant process computers available to the unit:
M1 M2
Describe how the plant process computers are linked within the plant:
1 – Centralized
2 – Distributive
3 – Stand alone
9 – Other, describe
M1 M2
Enter the system capability of the plant process computer:
1 – Monitor only
2 – Monitor and control
9 – Other, describe
System vendor
First-certified date:
Monitoring technique
1 – Extractive
2 – Dilution
3 – In Situ
Analysis Method
1 – Wet
2 – Dry
9 – Other, describe
Manufacturer(s)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Type(s)
1 – Ultraviolet
2 – Infrared
3 – Fluorescence
9 – Other, describe
M1 M2
Instrument range (parts per million)
1 – 0-50
2 – 0-150
3 – 0-500
9 – Other, describe __________________________________________________________
M1 M2
Shared? (1 – Yes, 2 – No)
Manufacturer(s)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Type(s)
1 – Infrared
2 – Chemiluminescent
M1 M2
Instrument range (parts per million)
1 – 0-50
2 – 0-150
3 – 0-500
9 – Other, describe ___________________________________________________________
M1 M2
Shared? (1 – Yes, 2 – No)
Manufacturer(s)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Type(s)
M1 M2
Instrument range (parts per million)
1 – 0-50
2 – 0-150
3 – 0-500
9 – Other, describe _________________________________________________________
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Instrument range (parts per million)
1 – 0-50
2 – 0-150
3 – 0-500
9 – Other, describe
M1 M2
Shared? (1 – Yes, 2 – No)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Type(s)
1 – Zirconia oxide
2 – Paramagretic
3 – Fuel cell
9 – Other, describe _________________________________________________________
M1 M2
Instrument range (parts per million)
1 – 0-50
2 – 0-150
3 – 0-500
9 – Other, describe __________________________________________________________
M1 M2
Shared? (1 – Yes, 2 – No)
6. Opacity Monitors
Manufacturer(s)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Probe placement (if unit is equipped with a FGD system)
1 – Before scrubber
2 – After scrubber
Manufacturer(s)
Model number(s)
M1 M2
Number of installed monitors
M1 M2
Number of installed spare monitors
M1 M2
Flow rate measurement technique
Hardware manufacturer
Hardware architecture
Software supplier
These systems include Selective Non-catalytic Reduction, Selective Catalytic Reduction, Catalytic Air Heaters, and
Staged NOX Reduction, which is a combination of the three methods. Excluded from this category are Low NOX
burners (see Item 16, Page E-9), combustion modifications, and flue gas recirculation.
Please complete the following information for the NOX Reduction Systems installed on your unit. (The
appropriate items under each method should be completed for a Staged NOX Reduction System).
Reagent
1 – Ammonia
2 – Urea
9 – Other, describe
Injector Type
1 – Wall nozzles
2 – Lance
9 – Other, describe
Number of Injectors
1 – Steam
2 – Air
9 – Other, describe
Reactor
1 – Separate
2 – In Duct
Reagent
1 – Ammonia
2 – Urea
9 – Other, describe _______________________________________________
1 – Furnace
2 – Superheater
3 – Economizer
4 – Zoned
Duct Configuration
1 – Flow straighteners
2 – Turning vanes
3 – Dampers
1 – Plate
2 – Honeycomb
9 – Other, describe ____________________________________________________
1 – Stainless steel
2 – Carbon steel
9 – Other, describe _____________________________________________________
1 – Vertical
2 – Horizontal
9 – Other, describe _____________________________________________________
Number of layers
1 – Air
2 – Steam
3 – Both air and steam
Manufacturer(s)
Number of sootblowers
Element Type
1 – Laminar surface
2 – Turbulent surface
9 – Other, describe
1 – Stainless steel
2 – Carbon steel
9 – Other, describe
i
http://www.nerc.com/pa/RAPA/gads/MandatoryGADS/Revised_Final_Draft_GADSTF_Recommendation_Report.pdf)
(Note: The NERC Board of Trustees approved the GADS Task Force Report (dated July 20, 2011) i, which states that
design data collection outside the required nine fields is solely voluntary. However, the GADS staff encourages
that reporters report and update GADS design data frequently. This action can be completed by sending in this
form to gads@nerc.net. GADS staff encourages using the software for design entry and updating.
Instructions
Use these forms to report design and installed equipment information for FLUIDIZED BED COMBUSTION (FBC)
units. These units include atmospheric (circulating (CFB) and bubbling (BFB)) fluidized bed only.
Data reported on these forms should reflect the current condition and design of the unit (installed equipment,
etc.). Do not report data for start-up equipment or for equipment that is not used to carry normal load unless
specifically requested.
Some data fields are designated as M1 and M2. These indicate that the equipment being reported may have
been supplied by more than one manufacturer. Use fields designated as M1 to report all the data associated
with one manufacturer’s equipment and M2 for the other.
Unit name:
Regional Entity:
Subregion:
Data reporter:
Telephone number:
Date:
Appendix E – Unit Design Data Forms – Fluidized Bed Combustion Units
1. Identification
A series of codes uniquely identifies your utility and units. NERC assigned a unique code to identify your
utility. You must assign the unique code that will identify the FBC unit being reported. This code may be any
number from 650 to 699. Enter the unique utility and unit code and the full name of the unit below:
Name of unit
Criteria: a) The date the unit was first declared available for dispatch at some level of its capability, OR;
b) The date the unit first operated at 50% of its generator nameplate megawatt capability
(product of the megavoltamperes (MVA) and the rated power factor as stamped on the
generator nameplate(s)).
Architect/Engineer
Constructor
5. Boiler - Manufacturer
Enter the name of the manufacturer and the model or series name or number of the boiler:
6. Boiler - Enclosure
Is 50% or more of the boiler outdoors (not enclosed in building framing and siding)?
1 – Yes 2 – No
1 - Circulating fluidized bed (CFB) - an FBC with no clear region between the relatively dense
bed and lean phase. A circulating bed usually has a superficial velocity greater than 13
ft./sec. and has a reinjection/recycle ratio greater than 5. Compared to a bubbling bed, a
circulating bed has significantly higher solids concentration throughout the combustor.
2 - Bubbling fluidized bed (BFB) - an FBC with a definite region between the relatively dense
bed and lean phase. A bubbling bed usually has a superficial velocity of less than 13
ft./sec. and a reinjection/recycle ratio of less than 5. In addition, the fuel and sorbent are
usually fed either overbed or underbed.
For fuel:
1 Over-bed feed (BFB) – injection of solids above the fluidized bed into a slightly negative
pressure environment where the solids then fall into the fluidized bed.
2 Under-bed feed (BFB) – injection of solids through multiple points to the bottom of the
fluidized bed into a positive pressure environment.
3 Both over–bed and under-bed feed (BFB) - combination of the two above.
4 Within-bed feed (CFB) - injection of solids through a few feed points to the fluidized bed
into a positive pressure environment. (This refers to the method of fuel feed in a circulating
bed.)
For sorbent:
1 - Yes
2 - No
1 Natural (thermal) – water flows through furnace wall tubes unaided by circulating pumps
(primarily used with subcritical units).
2 Controlled (forced or pump-assisted thermal) – water flows through furnace wall and/or in-
bed evaporator tubes aided by boiler recirculation pumps located in the downcomers or
lower headers of the boiler (used on some subcritical units).
3 Once through – no recirculation of water through the furnace wall tubes and no steam
drum (used on super and subcritical units).
4 Combination natural and controlled
*If more than one material is used, indicate each type with the predominant one mentioned first.
Separator manufacturer(s).
Manufacturer(s) of the motor(s) that drives the high pressure loop seal
fan(s)/blower(s).
Number of high pressure loop seal fans/blowers per manufacturer;
include installed spares.
TOTAL number of high pressure loop seal fans/blowers for the unit.
M1 M2
Enter the type of high pressure loop seal fan(s)/blower(s) at the unit
Centrifugal – blades mounted on an impeller (or rotor) which rotates within a spiral or volute housing.
Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
5 – Positive displacement (rotary) – such blowers are essentially constant-volume blowers with variable
discharge pressure. Volume can be varied only by changing the speed or by by-passing or wasting
some of the capacity of the machine. The discharge pressure will vary with the resistance on the
discharge side of the system.
9 – Other, describe
17. Boiler – Primary and Secondary Design Fuel, Sorbents, and Non-sorbent
The PRIMARY fuel is defined as that fuel primarily used to sustain load on the unit, (i.e., the first fuel of
choice for either economic or control reasons) or that fuel contributing 50% or more of the load-carrying
Btu. The SECONDARY fuel is that normally used to sustain load if the PRIMARY fuel is unavailable or
uneconomical. Do NOT report ignition or warm-up fuel.
Sorbent is a material (usually a limestone or dolomite) that is fed into the combustor with the solid fuel
(coal) thereby reducing the SO2 that is released during the combustion process.
Non-sorbent is a material other than sorbent that is used to build the bed. All characteristics are based on
an ultimate analysis of the as-received fuel using appropriate ASTM testing methods. Additional notes are
provided where appropriate.
CC Coal PR Propane
LI Lignite SL Sludge Gas
PE Peat GE Geothermal
WD Wood NU Nuclear
OO Oil WM Wind
DI Distillate Oil (#2) SO Solar
KE Kerosene WH Waste Heat
JP JP4 or JP5 OS Other - Solid (Tons)
WA Water OL Other - Liquid (BBL)
GG Gas OG Other - Gas (Cu.Ft.)
Fuel Characteristics
Average Heat Content in Fuel
(Btu/lb, Btu/bbl, Btu/CuFt)
17. Boiler – Primary and Secondary Design Fuel, Sorbents, and Non-sorbent (Continued)
Sorbent:
Non-sorbent:
Manufacturer(s) of the motor(s) that drives the fuel oil burner supply
pump(s).
TOTAL number of fuel oil burner supply pumps for the unit.
Duct burner:
Btu rating
Warmup burner:
Warmup burner manufacturer
Btu rating
1 – Pilot torch lighter – an oil or gas igniter that uses an electric spark to ignite the fuel.
2 – Carbon arc – a carbon or graphite electrode is energized and used to ignite the fuel.
3 – High energy arc – a low voltage, high energy pulse arc is used to ignite the fuel.
4 – Plasma arc – a high dc voltage current is used to ionize the air resulting in a high energy arc
that ignites the fuel.
5 – Manual – Ignition torch or lance inserted into boiler by operating personnel.
6 – Combination of any burner types above.
9 – Other, describe
Btu rating
1 Pilot torch lighter – an oil or gas igniter that uses an electric spark to ignite the fuel.
–
2 Carbon arc – a carbon or graphite electrode is energized and used to ignite the fuel.
–
3 High energy arc – a low voltage, high energy pulse arc is used to ignite the fuel.
–
4 Plasma arc – a high dc voltage current is used to ionize the air resulting in a high energy
–
arc that ignites the fuel.
5 – Manual – Ignition torch or lance inserted into boiler by operating personnel.
6 – Combination of any burner types above.
9 – Other, describe
Crusher(s) manufacturer(s).
Type of crusher(s).
Type of crusher(s).
Crusher(s) manufacturer(s).
1 – Lance
2 – Nozzle
9 – Other, describe
M1 M2
Enter the type of sorbent crusher(s) or pulverizer(s) at the unit:
1 – Ball – grinding elements are balls that operate freely in a race on a rotating grinding
table.
2 – Roll race – rotating grinding table that moves sorbent through a series of rollers or
wheels supported within the pulverizer.
3 – Ball tube (Hardinge) – horizontal, rotating, grinding cylinder containing steel balls that
move within the cylinder and grind or crush the sorbent.
4 – Impact (Attrition) – series of fixed or hinged hammers that rotate within a closed
chamber impacting and crushing the sorbent.
9 – Other, describe
1 – Balanced draft – equipped with both induced draft and forced draft fans. The furnace
operates at positive pressure at air entry and negative pressure at flue gas exit.
2 – Pressurized draft – equipped with forced draft fans only. The furnace and draft systems
operate at positive pressure.
IF the unit was originally designed as a pressurized draft unit and converted to a balanced draft design,
indicate the date the conversion was completed:
Horsepower of fan(s)
M1 M2
Enter the type of primary air (forced draft) fan(s) at the unit:
Centrifugal – blades mounted on an impeller (or rotor) which rotates within a spiral or volute
housing. Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
M1 M2
Enter the type of primary air (forced draft) fan drive(s) at the unit:
M1 M2
Enter the type of induced draft fan(s) at the unit:
Centrifugal – blades mounted on an impeller (or rotor) which rotates within a spiral or volute
housing. Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
M1 M2
Enter the type of induced draft fan drive(s) at the unit:
M1 M2
Enter the type of secondary air fan(s) at the unit:
Centrifugal – blades mounted on an impeller (or rotor) which rotates within a spiral or volute
housing. Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
M1 M2
Enter the type of secondary air fan(s) drives at the unit:
M1 M2
Enter the type of additional air heater(s) at the unit (see item 33 for definitions of each
type):
1 – Regenerative (Ljungstrom)
2 – Tubular
3 – Steam Coil
4 – Regenerative (Rothemule)
5 – Recuperative (plate type)
6 – Heat Pipe
9 – Other, describe
Enter the type(s) of medium(s) used to blow the soot. If a variety of soot blowers are used at the unit,
note the number of each.
M1 M2 M3
1 – Steam
2 – Air
3 – Water
4 – Sonic
5 – Steam/Air
9 – Other, describe
Bed material cooler tube materials used in the majority (50% or greater)
of the tubes made by each manufacturer.
Bed material cooler type (screw, counter flow, fluid bed, other).
Number of fields.
Enter the location of the electrostatic precipitator with respect to the air
Bag material.
1 – Reverse – clean flue gas is blown in a direction counter to normal operation to remove
the fly ash from the bag.
2 – Pulse (or pulse set) – short bursts of compressed air are blown into the bag to cause a
momentary expansion of the bag which dislodges the entrapped fly ash.
3 – Shaker – the bag is literally shaken to remove the fly ash collected on its surface.
4 – Combination (reverse/shaker)
9 – Other, describe
Centrifugal – blades mounted on an impeller (or rotor) which rotates within a spiral or volute
housing. Mark the type of blades used on this type of fan:
1 – Forward curved
2 – Straight (radial or radial tipped)
3 – Backward curved (air foil or flat)
4 – Axial (fixed or variable pitch) – blades attached to central hub parallel to air flow.
9 – Other, describe
1 – Vacuum – ash-conveying system operates at a vacuum relative to the fly ash collection
hoppers. Ash is dry.
2 – Pressure – ash conveying system operates at a pressure greater than the pressure in the
fly ash collection hoppers. Ash is dry.
3 – Vacuum-pressure – employs the best features of both the vacuum and pressure systems.
4 – Water (sluice) – employs water to sluice the ash away from the hoppers.
5 – Vacuum/water slurry – ash conveying system operates at a vacuum relative to the fly ash
collection hoppers. Ash is wet.
6 – Mechanical – refers to mechanical conveying systems such as conveyor belts, bucket
elevators, and screw conveyors.
9 – Other, describe_________________________________________________
1 – Yes 2 – No
1 – Single casing – single (simple) turbine having one pressure casing (cylinder).
2 – Tandem compound – two or more casings coupled together in line.
3 – Cross compound – two cross-connected single casing or tandem compound turbine sets
where the shafts are not in line.
4 – Triple compound – three cross-connected single casing or tandem compound turbine
sets.
9 – Other, describe
Back pressure of the high pressure condenser (if applicable) to the nearest one-tenth inch
▲ of mercury at the nameplate capacity and design water temperature.
Back pressure of the low pressure condenser to the nearest one-tenth inch of mercury at
▲ nameplate capacity and design water temperature.
The last stage blade length (inches) of the low pressure turbine, measured from hub to end
▲ of top of blade.
1 – Partial arc – main steam flow is restricted to one sector of the turbine’s first stage at
startup.
2 – Full arc – main steam is admitted to all sectors of the turbine’s first stage at startup.
3 – Either – capable of admitting steam using either partial or full arc techniques.
9 – Other, describe
1 – Mechanical hydraulic control (MHC) – turbine speed monitored and adjusted through
mechanical and hydraulic linkages.
2 – Analog electro-hydraulic control (EHC) – analog signals control electro-hydraulic linkages
to monitor and adjust turbine speed.
3 – Digital electro-hydraulic control (DHC) – same as EHC except signals are digital rather than
analog.
9 – Other, describe
1 – Motor
2 – Shaft
3 – Steam turbine
4 – More than one
9 – Other, describe
Generator manufacturer
1 – Yes 2 – No
RPM
Enter the mediums used to cool the generator’s stator and rotor:
Exciter manufacturer
Enter the type(s) of exciter drive(s) used by the main exciter IF it is rotating:
1 – Shaft direct
2 – Shaft gear
3 – Motor
9 – Other, describe
1 – Vacuum pump
2 – Steam jet air ejector
3 – Both
9 – Other, describe
Enter the type of on-line main condenser cleaning system used at the unit:
Enter the following information about the condensate polishing system at the unit:
Enter the % treated of the condensate flow at maximum unit capacity that can be treated:
% Treated
▲
1 – Hydraulic
2 – Mechanical
9 – Other, describe
PERCENT (%) of the unit’s maximum capacity that can be achieved using a single startup
▲
feedwater pump.
M1 M2
Indicate the additional capabilities of the startup feedwater pump:
Feedwater heater tube materials used in 50% or more of the tubes per
manufacturer.
TOTAL number of high pressure feedwater heaters for the unit.
M1 M2
Enter the type of HIGH pressure feedwater heater(s):
Feedwater heater tube materials used in 50% or more of the tubes, per
manufacturer.
TOTAL number of intermediate pressure feedwater heaters for the unit.
M1 M2
Enter the type of INTERMEDIATE pressure feedwater heater(s):
Feedwater heater tube materials used in 50% or more of the tubes, per
manufacturer.
TOTAL number of low pressure feedwater heaters for the unit.
M1 M2
Enter the type of LOW pressure feedwater heater(s):
Deaerator manufacturer(s)
M1 M2
Enter the type of deaerator heater(s):
M1 M2
Enter the type of cooling tower used by the unit:
1 – Mechanical draft (induced, forced, cross-flow and counterflow) – fan(s) used to move
ambient air through the tower.
2 – Atmospheric spray – air movement is dependent on atmospheric conditions and the
aspirating effect of the spray nozzles.
3 – Hyperbolic (natural draft) – temperature difference between condenser circulating water
and ambient air conditions, aided by hyperbolic tower shape, creates natural draft of air
through the tower to cool the water.
4 – Deck-filled – wetted surfaces such as tiers of splash bars or decks aid in the breakup and
retention of water drops to increase the evaporation rate.
5 – Coil shed – a combination structure of a cooling tower installed over a substructure that
houses atmospheric coils or sections.
9 – Other, describe
The cooling tower booster pumps increase the pressure of the circulating water and force the water to
the top of the cooling tower.
Cooling tower booster pump(s) manufacturer(s).
1 – Single phase
2 – Three phase
9 – Other, describe
M1 M2
Enter the number of plant process computers available to the unit:
1 – One computer for this unit only.
2 – Two computers for this unit only.
3 – One computer shared by one or more units.
4 – Two computers shared by one or more units.
9 – Other, describe
M1 M2
Describe how the plant process computers are linked within the plant:
1 – Centralized
2 – Distributive
3 – Stand alone
9 – Other, describe
M1 M2
Enter the system capability of the plant process computer:
1 – Monitor only
2 – Monitor and control
9 – Other, describe
System vendor
First-certified date:
Year Month Day
Monitoring technique
1 – Extractive
2 – Dilution
3 – In Situ
Analysis Method
1 – Wet
2 – Dry
9 – Other, describe
Manufacturer(s)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Type(s)
1 – Ultraviolet
2 – Infrared
3 – Fluorescence
9 – Other, describe
M1 M2
Instrument range (parts per million)
1 – 0-50
2 – 0-150
3 – 0-500
9 – Other, describe
M1 M2
Shared? (1 - Yes, 2 – No)
Manufacturer(s)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Type(s)
1 - Infrared
2 - Chemiluminescent
9 - Other, describe
M1 M2
Instrument range (parts per million)
1 – 0-50
2 – 0-150
3 – 0-500
9 – Other, describe
M1 M2
Shared? (1 – Yes, 2 – No)
Manufacturer(s)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Type(s)
1 – 0-50
2 – 0-150
3 – 0-500
9 – Other, describe
1 - 0-50
2 - 0-150
3 - 0-500
9 - Other, describe
M1 M2
Shared? (1 – Yes, 2 – No)
Manufacturer(s)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Type(s)
1 – Zirconia oxide
2 – Paramagretic
3 – Fuel cell
9 – Other, describe
M1 M2
Instrument range (parts per million)
1 – 0-50
2 – 0-150
3 – 0-500
9 – Other, describe
M1 M2
Shared? (1 – Yes, 2 – No)
6. Opacity Monitors
Manufacturer(s)
Model number(s)
M1 M2
Number of installed analyzers
M1 M2
Number of installed spare analyzers
M1 M2
Probe placement (if unit is equipped with a FGD system)
1 – Before scrubber
2 – After scrubber
Manufacturer(s)
Model number(s)
M1 M2
Number of installed monitors
M1 M2
Number of installed spare monitors
M1 M2
Flow rate measurement technique
Hardware manufacturer
Hardware architecture
Software supplier
These systems include Selective Non-catalytic Reduction, Selective Catalytic Reduction, Catalytic Air Heaters, and
Staged NOx Reduction, which is a combination of the three methods. Excluded from this category are Low NOx
burners, combustion modifications, and flue gas recirculation.
Please complete the following information for the NOx Reduction Systems installed on your unit. (The appropriate
items under each method should be completed for a Staged NOx Reduction System).
Reagent
1 – Ammonia
2 – Urea
9 – Other, describe
Injector Type
1 – Wall nozzles
2 – Lance
9 – Other, describe
1 – Furnace
2 – Superheater
3 – Economizer
9 – Other, describe
Number of Injectors
1 – Steam
2 – Air
9 – Other, describe
Reactor
1 – Separate
2 – In Duct
Reagent
1 – Ammonia
2 – Urea
9 – Other, describe
1 – Furnace
2 – Superheater
3 – Economizer
4 – Zoned
Duct Configuration
1 – Flow straighteners
2 – Turning vanes
3 – Dampers
1 – Plate
2 – Honeycomb
9 – Other, describe
1 – Stainless steel
2 – Carbon steel
9 – Other, describe
1 – Vertical
2 – Horizontal
9 – Other, describe
Number of layers
1 – Air
2 – Steam
3 – Both air and steam
Manufacturer(s)
Number of sootblowers
Element Type
1 – Laminar surface
2 – Turbulent surface
9 – Other, describe
1 – Stainless steel
2 – Carbon steel
9 – Other, describe
i
http://www.nerc.com/pa/RAPA/gads/MandatoryGADS/Revised_Final_Draft_GADSTF_Recommendation_Report.pdf)
(Note: The NERC Board of Trustees approved the GADS Task Force Report (dated July 20, 2011) i, which states
that design data collection outside the required nine fields is solely voluntary. However, the GADS staff
encourages that reporters report and update GADS design data frequently. This action can be completed by 1)
sending in this form to gads@nerc.net. GADS staff encourages using the software for design entry and updating.
Instructions
Submit the data in this section once during the life of each nuclear unit. If a major change is made to a unit
which significantly changes its characteristics, then resubmit this section with updated information.
For coded entries, a enter a (9) to indicate an alternative other than those specified. Whenever you enter a (9),
write the column number and the answer on the reverse side of the form.
Utility name:
Station name:
Unit name:
Regional Entity:
Subregion:
Data reporter:
Telephone number:
Date:
Appendix E – Unit Design Data Forms – Nuclear Units
07 Card code
53 Type of control rod drive – (1) Magnetic jack; (2) Hydraulic water;
(3) Rack and pin; (9) Other
54 Control rod configuration – (1) Cruciform; (2) Rod cluster; (9) Other
63 Fuel cladding material – (1) Zirconium; (2) Stainless steel; (9) Other
ARCHITECT/ENGINEERING DATA
65 Architect/Engineer – (1) All A/E work inhouse; (2) Burns & Roe; (3) Black
& Veatch; (4) Bechtel; (5) Brown & Root; (6) Durham & Richardson; (7)
Ebasco Services; (8) Gibbs & Hill; (9) Gilbert Associates; (10) Offshore
Power Systems; (11) Ralph M Parsons; 12) Pioneer Services &
Engineering; (13) Sargent & Lundy; (14) Stone & Webster; (15) United
Engineers & Constructors; (99) Other
2 2 07 Card code
CONDENSER DATA
42 Number of shells
45 Cooling water origin – (1) River; (2) Lake; (3) Ocean or bay;
(4) Cooling tower
AUXILIARIES DATA
51 Number of spare feed pumps which are approximately the same size
as one normally used pump
52 Number of spare or startup feed pumps which are smaller than one
normally used pump
54 Normal feed pump type drive – (1) Motor; (2) Steam; (3) Shaft;
(4) Motor gear; (5) Steam gear; (6) Shaft gear; (9) Other
GENERATOR DATA
2 3 07 Card code
i
http://www.nerc.com/pa/RAPA/gads/MandatoryGADS/Revised_Final_Draft_GADSTF_Recommendation_Report.pdf)
(Note: The NERC Board of Trustees approved the GADS Task Force Report (dated July 20, 2011) i, which states
that design data collection outside the required nine fields is solely voluntary. However, the GADS staff
encourages that reporters report and update GADS design data frequently. This action can be completed by
sending in this form to gads@nerc.net. GADS staff encourages using the software for design entry and updating.
Instructions
Submit the data in this section once during the life of each diesel unit. If a major change is made to a unit which
significantly changes its characteristics, then resubmit this section with updated information.
For coded entries, a (9) is entered to indicate an alternative other than those specified. Whenever a (9) is
entered, write the column number and the answer on the reverse side of the form.
If a copy of the original form is being submitted, make sure that it is legible.
Utility name:
Station name:
Unit name:
Regional Entity:
Subregion:
Data reporter:
Telephone number:
Date:
Appendix E – Unit Design Data Forms – Diesel Units
4 1 07 Card code
22 Fuel, type – (1) No. 2 fuel oil; (2) Diesel oil; (3) JP 5 fuel;
(4) Kerosene; (5) Heavy oil; (9) Other
33 Coolant, type – (1) Water; (2) Oil; (3) Air; (9) Other
4 2 07 Card code
GENERATOR DATA
4 3 07 Card code
i
http://www.nerc.com/pa/RAPA/gads/MandatoryGADS/Revised_Final_Draft_GADSTF_Recommendation_Report.pdf)
(Note: The NERC Board of Trustees approved the GADS Task Force report (dated July 20, 2011)1, which
states that design data collection outside the required nine fields is solely voluntary. However, the GADS
staff encourages that reporters report and update GADS design data frequently. This action can be
completed by sending in this form to gads@nerc.net. GADS staff encourages using the software for design
entry and updating.
Instructions
Submit the data in this section once during the life of each pumped storage or hydro unit. If a major
change is made to a unit which significantly changes its characteristics, then resubmit this section with
updated information.
For coded entries, enter a (9) to indicate an alternative other than those specified. Whenever you enter
a (9), write the column number and the answer on the reverse side of the form.
When submitting an original copy of the form, make sure that it is legible.
Unit name:
Regional Entity:
Sub region:
Data reporter:
Telephone number:
Date:
Appendix E – Unit Design Data Forms – Hydro/Pumped Storage Units
5 1 07 Card code
38 Turbine runner, type – (1) Single; (2) Twin; (3) Triplex; (4) Double
discharge; (9) Other
41 Governor type – (1) Gate shaft; (2) Actuator; (3) Cabinet type;
(4) Electric; (5) Electro hydraulic, speed sensing; (6) Electronic
hydraulic, speed sensing; (7) Mechanical, speed sensing;
(9) Other
*****************************
5 2 07 Card code
GENERATOR DATA
5 3 07 Card code
1
http://www.nerc.com/pa/RAPA/gads/MandatoryGADS/Revised_Final_Draft_GADSTF_Recommendation_Report.pdf)
(Note: The NERC Board of Trustees approved the GADS Task Force report (dated July 20, 2011 i, which
states that design data collection outside the required nine fields is solely voluntary. However, the
GADS staff encourages that reporters report and update GADS design data frequently. This action can
be completed by sending in this form to gads@nerc.net. GADS staff encourages using the software for
design entry and updating.
Instructions
Submit the data in this section once during the life of each gas turbine or jet engine unit. If a major
change is made to a unit which significantly changes its characteristics, then resubmit this section with
updated information.
For coded entries, enter a (9) to indicate an alternative other than those specified. Whenever you
enter a (9), write the column number and the answer on the reverse side of the form.
Unit name:
Regional Entity:
Subregion:
Data reporter:
Telephone number:
Date:
Appendix E – Unit Design Data Forms – Gas Turbine or Jet Engine Units
3 1 07 Card code
21 Engine type – (1) Gas turbine single shaft; (2) Gas turbine split shaft; (3)
Jet engine; (9) Other
28 Startup system – (1) Air; (2) Auxiliary motor; (3) Electric motor;
(4) Natural gas; (5) Flow turbine; (6) Supercharging fan;
(7) Hydraulic; (9) Other
3 2 07 Card code
23 SNCR injector type – (1) Wall nozzle; (2) Lance; (9) Other
28 SNCR carrier gas type – (1) Steam; (2) Air; (9) Other
GENERATOR DATA
3 3 07 Card code
http://www.nerc.com/pa/RAPA/gads/MandatoryGADS/Revised_Final_Draft_GADSTF_Recommendation_Report.pdf)
(Note: The NERC Board of Trustees approved the GADS Task Force report (dated July 20, 2011 1, which
states that design data collection outside the required nine fields is solely voluntary. However, the GADS
staff encourages that reporters report and update GADS design data frequently. This action can be
completed by sending in this form to gads@nerc.net. GADS staff encourages using the software for design
entry and updating.
INSTRUCTIONS
Use these forms when no other forms in this appendix are appropriate. Specifically, use them for multi-
boiler/multi-turbine units, combined-cycle units, and geothermal units.
Submit the data in this section once during the life of each miscellaneous unit. If a major change is made
to a unit which significantly changes its characteristics, then resubmit this section with updated
information.
For coded entries, enter a (9) to indicate an alternative other than those specified, and whenever a (9) is
entered, write the column number and the answer on the reverse side of the form.
Utility name:
Station name:
Unit name:
Data reporter:
Telephone number:
Date:
Appendix E – Unit Design Data – Miscellaneous
MISCELLANEOUS
8 1 07 Card code
8 2 07 Card code
23 SNCR injector type – (1) Wall nozzle; (2) Lance; (9) Other
28 SNCR carrier gas type – (1) Steam; (2) Air; (9) Other
GENERAL DATA
8 3 07 Card code
48 Name of Unit
1
http://www.nerc.com/pa/RAPA/gads/MandatoryGADS/Revised_Final_Draft_GADSTF_Recommendation_Report.pdf)
(Note: The NERC Board of Trustees approved the GADS Task Force report (dated July 20, 2011 – here i which
states that design data collection outside the required nine fields is solely voluntary. However, the GADS staff
encourages that reporters report and update GADS design data frequently. This action can be completed by 1)
sending in this form to gads@nerc.net. GADS staff encourages using the software for design entry and updating.
Company name:
Station name:
Block name:
Data reporter:
Telephone number:
Date:
Appendix E – Unit Design Data Forms – Combined-Cycle and Co-Generation Blocks
Instructions
Here are some definitions used to eliminate some of the ambiguity concerning combined-cycle blocks.
There may be more than one block at a plant site. Reporters should complete a form for each
individual block.
o Units – Each gas turbine/jet engine and each steam turbine is considered a “unit.” Each unit
contributes to the total electric generation or steam production of the block. Each unit has its
own or shares its generator for providing electric power. They should be considered individual
parts of the block.
o Heat Recovery Steam Generator (HRSG) – There may be one or more HRSG or waste heat boilers
in a block. Some blocks may have a single HRSG per GT/jet; others may have several GT/jets
feeding a single HRSG or any combination thereof. The HRSG does not contribute electricity to
the output of the block so is considered a component rather than a “unit.”
o Other Balance of Plant Equipment – There is other equipment in the block used to support the
production of electricity/heat energy, but they are not related to any specific generating unit
and are also considered components. Submit the data in this section once during the life of each
block. If a major change is made to a site that significantly changes its characteristics, then
resubmit this section with updated information.
For coded entries, enter a (9) to indicate an alternative other than those specified. Whenever you enter a (9),
write the column number and the answer on the reverse side of the form.
If you’re submitting copy of the original form, make sure that it is legible.
__________________________________________________________
Criteria: a) The date the block was first declared available for dispatch at some level of its capability,
OR
b) The date the block first operated at 50% of its generator nameplate megawatt capability
(product of the megavolt amperes (MVA) and the rated power factor as stamped on the
generator nameplate(s)).
Architect/Engineer:
Constructor: _________________________________________
Total block rating (MW) based on sum of nameplate ratings on all units: __________________________.
6. Does the block have co-generation (steam for other than electric generation) capabilities (yes/no)?
_____
7. What is the number of gas turbines/jet engines per Heat Recovery Steam Generator (HRSG)
Identify the number of gas turbines/jet engines feeding exhaust gases into a single HRSG.
8. What is the number of gas turbines/jet engines – Heat Recovery Steam Generator (HRSG) Trains
Identify the number of sets of gas turbines/jet engines and HRSG trains supplying steam to the steam
turbine
12. Identification
A series of codes uniquely identifies your utility (company), the combined-cycle block and its units. NERC
assigned a unique code to identify your company. You must assign the unique code that will identify the
GAS TURBINE/JET ENGINE unit being reported. This code may be any number from 300 to 399 or 700-799.
Enter the unique company, block and unit code and the full name of each gas turbine/jet engine below:
Utility (Company) Code: _________ Unit Code: ___________ Block Code: _____________
Criteria: a) The date the gas turbine/jet engine was first declared available for dispatch at some level of
its capability, OR
b) The date the gas turbine/jet engine first operated at 50% of its generator nameplate
megawatt capability (product of the megavolt amperes (MVA) and the rated power factor
as stamped on the generator nameplate(s)).
Architect/Engineer:
Constructor: __________________________
16. Engine manufacturer – (1) Pratt & Whitney; (2) General Electric; (3) Siemens Westinghouse; (4) Alstom
(ABB); (5) Rolls Royce; (6) Cooper Bessemer; (7) Worthington; (8) Allison; (9)
Other.___________________________________________
17. Engine type – (1) Gas turbine single shaft; (2) Gas turbine split shaft; (3) Jet engine; (9) Other
____________________________________________
19. Type expander, if applicable – (1) Single flow; (2) Double flow
20. Cycle type – (1) Reheat; (2) Simple; (3) Regenerative; (4) Recuperative; (5) Intercooled;
(6) Pre-cooled; (7) Complex; (8) Compound; (9) Other
21. Start-up system – (1) Air; (2) Auxiliary motor; (3) Electric motor; (4) Natural gas; (5) Flow turbine; (6)
Supercharging fan; (7) Hydraulic; (9) Other
22. Start-up type – (1) Automatic, on site; (2) Automatic, remote; (9) Other
27. Time in seconds for normal cold start to full load: _________________
28. Time in seconds for emergency cold start to full load: ______________
________________________________________________________
31. SNCR reagent – (1) Ammonia; (2) Urea; (9) Other: ___________________________
32. SNCR injector type – (1) Wall nozzle; (2) Lance; (9) Other: ____________________
33. SNCR injection equipment location – (1) Furnace; (2) Super-heater; (3) Economizer;
(9) Other: ______________________________
35. SNCR carrier gas type – (1) Steam; (2) Air; (9) Other: _____________________
36. SNCR carrier gas total flow rate (thousands of lb./hr.) i.e. 6,000,000 lbs./hr. enter 6000
____________________________________________________
38. SNCR carrier gas nozzle exit velocity (thousands of ft./sec.): _________________
40. 40SCR reagent – (1) Ammonia; (2) Urea; (9) Other: ____________________
41. SCR ammonia injection grid location – (1) Furnace; (2) Super-heater; (3) Economizer;
(4) Zoned; (5) Other: ____________________________________
42. SCR duct configuration – (1) Flow straighteners; (2) Turning vanes; (3) Dampers
43. SCR catalyst element type (1) Plate; (2) Honeycomb; (9) Other: ________________
44. SCR catalyst support material – (1) Stainless steel; (2) Carbon steel;
(9) Other: __________________________________
46. SCR catalyst surface face area (thousands of square feet): ___________________________
50. SCR sootblower type – (1) Air; (2) Steam; (3) Both
52. CAH element type – (1) Laminar surface; (2) Turbulent surface;
(9) Other: ____________________________________
53. CAH catalyst material – (1) Titanium oxide; (2) Vanadium pentoxide; (3) Iron (II) oxide;
4) Molybdenum oxide; (9) Other: _____________________________________
54. CAH catalyst support material – (1) Stainless steel; (2) Carbon steel;
(9) Other: ________________________________
55. CAH catalyst material configuration – (1) Horizontal air shaft; (2) Vertical air shaft
56. CAH catalyst material total face area (thousands of square feet): _____________________
57. CAH catalyst material open face area (thousands of square feet): _____________________
Generator manufacturer:
RPM
Enter the mediums used to cool the generator’s stator (air, hydrogen, oil, water): ______________
Enter the mediums used to cool the generator’s rotor (air, hydrogen, oil, water): ______________
MINIMUM number of exciters required to obtain maximum capacity from the unit:
ENTER the type of main exciter used at the unit from the list below: _______________________
1 – Static – static excitation where dc is obtained by rectifying ac from generator terminals,
and dc is fed into rotor by collector rings.
2 – Rotating dc generator – exciter supplies dc from a commutator into the main rotor by
means of collector rings.
3 – Brushless – an ac (rotating armature type) exciter whose output is rectified by a
semiconductor device to provide excitation to an electric machine. The semiconductor
device would be mounted on and rotate with the ac exciter armature.
4 – Alternator rectifier
9 – Other, describe:
ENTER the type(s) of exciter drive(s) used by the main exciter IF it is rotating: ____________________
1 – Shaft direct
2 – Shaft gear
3 – Motor
9 – Other, describe:
66. Enter the unit code information for each GT/Jet that supplies heat energy to this single HRSG.
Utility (Company) Code: _____________ Unit Code “A”: ______________ Block Code:______________
Utility (Company) Code: _____________ Unit Code “B”: _______________ Block Code:_____________
Utility (Company) Code: _____________ Unit Code “C”: _______________ Block Code:_____________
Utility (Company) Code: _____________ Unit Code “D”: _______________ Block Code:_____________
HIGH-PRESSURE
Steam flow rate (in lbs/hr): ______________________
INTERMEDIATE PRESSURE
Steam flow rate (in lbs/hr): ______________________
LOW-PRESSURE
Steam flow rate (in lbs/hr): ______________________
REHEAT PRESSURE
Steam flow rate (in lbs/hr): ______________________
HIGH-PRESSURE
Steam flow rate (in lbs/hr): ______________________
INTERMEDIATE PRESSURE
Steam flow rate (in lbs/hr): ______________________
LOW-PRESSURE
Steam flow rate (in lb/hr): ______________________
REHEAT PRESSURE
Steam flow rate (in lb/hr): ______________________
71. Is the HRSG top-supported (pressure parts hang like in a utility boiler) or bottom-supported?
______________________
72. Does the HRSG have vertical or horizontal heat exchangers? ________________
73. Is the duct insulation cold casing (insulation on the inside of the duct) or hot casing (insulation on the
outside of the duct)? ___________________________
Does the HRSG have the capability of supplemental firing (duct firing) (y/n)?_____
MINIMUM number of HRSG recirculation pumps required to obtain maximum capacity from this
HRSG:
Manufacturer of the combustion control system that coordinates the feedwater, air, and fuel subsystems
for continuous HRSG operation:
Manufacturer of the burner management system that monitors only the fuel and air mixture during all
phases of operation to prevent the formation of an explosive mixture:
MINIMUM number of feedwater pumps required to obtain maximum capacity from the
HRSG:
PERCENT (%) of the HRSG’s maximum capacity that can be achieved with a single
feedwater pump (XXX.X format): __________________
Enter the type of equipment used to drive the feedwater (HRSG feed) pumps: ___________
Specify coupling type used for feedwater (HRSG feed) pump: ___________
1 – Hydraulic
2 – Mechanical
9 – Other, describe
PERCENT (%) of the HRSG’s maximum capacity that can be achieved with a single
Start-up feedwater pump: _______________
88. Identification
A series of codes uniquely identifies your company and generating units. NERC assigned a unique code to
identify your company. You must assign the unique code that will identify the STEAM TURBINE unit being
reported. This code may be any number from 100 to 199 or 600-649. Enter the unique company, block and
generating-unit code and the full name of each steam turbine below:
89. Does the steam turbine have bypass capability? (y/n) _________
1 – Single casing – single (simple) turbine having one pressure casing (cylinder).
2 – Tandem compound – two or more casings coupled together in line.
3 – Cross compound – two cross-connected single casing or tandem compound turbine sets
where the shafts are not in line.
4 – Triple compound – three cross-connected single casing or tandem compound turbine
sets.
9 – Other, describe: ___________________________________________
Turbine configuration and number of exhaust flows (e.g., tandem compound, four flow): ______________
High-Pressure Casings
TOTAL number of high pressure casings, cylinders or shells: ___________
Back pressure of the high pressure condenser (if applicable) to the nearest one-tenth inch of mercury at
the nameplate capacity and design water temperature. (XX.X format): ____________
Low-pressure Casings
TOTAL number of low-pressure casings, cylinders or shells: ___________________
Back pressure of the low pressure condenser to the nearest one-tenth inch of mercury at nameplate
capacity and design water temperature. (XX.X format): ______________
The last stage blade length (inches) of the low-pressure turbine, measured from hub to end of top
of blade. (XX.X format): _______________________
1 – Partial arc – main steam flow is restricted to one sector of the turbine’s first stage at
start-up.
2 – Full arc – main steam is admitted to all sectors of the turbine’s first stage at start-up.
3 – Either – capable of admitting steam using either partial or full arc techniques.
9 – Other, describe
Enter the type of turbine governing system used at the unit: ____________
1 – Mechanical hydraulic control (MHC) – turbine speed monitored and adjusted through
mechanical and hydraulic linkages.
2 – Analog electro-hydraulic control (EHC) – analog signals control electro-hydraulic linkages
to monitor and adjust turbine speed.
3 – Digital electro-hydraulic control (DHC) – same as EHC except signals are digital rather than
analog.
9 – Other, describe
Manufacturer of the motor(s)/steam turbine(s) that drives the main lube oil pump(s):
TOTAL number of steam turbine main lube oil pumps; include installed spares:
Enter the type of driver on the main lube oil pump: _________________
1 – Motor
2 – Shaft
3 – Steam turbine
9 – Other, describe
Generator manufacturer:
RPM
Enter the mediums used to cool the generator’s stator (air, hydrogen, oil, water): ______________
Enter the mediums used to cool the generator’s rotor (air, hydrogen, oil, water): _______________
Exciter manufacturer:
MINIMUM number of exciters required to obtain maximum capacity from the unit:
Enter the type(s) of exciter drive(s) used by the main exciter IF it is rotating:
1 – Shaft direct
2 – Shaft gear
3 – Motor
9 – Other, describe
Auxiliary Systems
105. Auxiliary Systems – Main Condenser
Enter the following information for the main condenser and its auxiliaries:
Condenser tube materials used in the majority (50% or more) of the condenser
tubes:
1 Vacuum pump
2 – Steam jet air ejector
3 – Both
9 – Other, describe
Enter the origin of the circulating water used in the condenser: ________________
1 – River
2 – Lake
3 – Ocean or Bay
4 – Cooling Tower
9 – Other, describe
Enter the type of on-line main condenser cleaning system used at the unit: _________________________
Enter the following information about the condensate polishing system at the unit:
Enter the % of the condensate flow at maximum unit capacity that can be treated: __________________
MINIMUM number of condensate pumps required to obtain maximum capacity from the
block:
MINIMUM number of condensate booster pumps required for maximum capacity from the
block:
MINIMUM number of circulating water pumps required to obtain maximum capacity from the block
DURING WINTER SEASON.
1 – Mechanical draft (induced, forced, cross-flow and counterflow) – fan(s) used to move
ambient air through the tower.
2 – Atmospheric spray – air movement is dependent on atmospheric conditions and the
aspirating effect of the spray nozzles.
3 – Hyperbolic (natural draft) – temperature difference between condenser circulating water
and ambient air conditions, aided by hyperbolic tower shape, creates natural draft of air
through the tower to cool the water.
4 – Deck-filled – wetted surfaces such as tiers of splash bars or decks aid in the breakup and
retention of water drops to increase the evaporation rate.
5 – Coil shed – a combination structure of a cooling tower installed over a substructure that
houses atmospheric coils or sections.
9 – Other, describe
The cooling tower booster pumps increase the pressure of the circulating water and force the water to
the top of the cooling tower.
Manufacturer(s) of the motor(s) that drives the cooling tower booster pump(s):
MINIMUM number of cooling tower booster pumps required to obtain maximum capacity from the
block:
Balance of Plant
112. Balance of Plant – Main Transformer
The main transformer is the block step-up transformer connecting the generator (or multiple generators if
block is cross compound) to the transmission system. Enter the following information for the MAIN
transformer(s) at the block:
1 – Single phase
2 – Three phase
9 – Other, describe
LOW SIDE voltage in kilovolts (kV) of the block auxiliary transformer(s) at 55:
HIGH SIDE voltage in kilovolts (kV) of the station service transformer(s) at 55:
LOW SIDE voltage in kilovolts (kV) of the station service transformer(s) at 55:
i http://www.nerc.com/pa/RAPA/gads/MandatoryGADS/Revised_Final_Draft_GADSTF_Recommendation_Report.pdf)
General Information
Appendix F discusses the relationships among the performance indexes calculated from the event and
performance data outlined in Sections III and IV. The basis for these relationships is IEEE Standard No. 762
“Definitions for Use in Reporting Electric Generating Unit Reliability, Availability and Productivity.”
2. Synchronous Condensing Hours Sum of all hours the unit is in the synchronous
condensing mode. The units are considered to be
in a non-generating service operation.
5. Planned Outage Hours - POH Sum of all hours experienced during Planned Outages
(PO) + Planned Outage Extensions (PE) of any Planned
Outages (PO).
6. Unplanned Outage Hours - UOH Sum of all hours experienced during Forced Outages
(U1, U2, U3) + Startup Failures (SF) + Maintenance
Outages (MO) + Maintenance Outage Extensions (ME) of
any Maintenance Outages (MO).
8. Maintenance Outage Hours - MOH Sum of all hours experienced during Maintenance
Outages (MO) + Maintenance Outage Extensions (ME) of
any Maintenance Outages (MO).
9. Unavailable Hours - UH Sum of all Planned Outage Hours (POH) + Forced Outage
Hours (FOH) + Maintenance Outage Hours (MOH).
10. Scheduled Outage Hours - SOH Sum of all hours experienced during Planned Outages
(PO) + Maintenance Outages (MO) + Scheduled Outage
Extensions (PE and ME) of any Maintenance Outages
(MO) and Planned Outages (PO).
Appendix F – Performance Indexes and Equations
11. Period Hours - PH Number of hours in the period being reported that the
unit was in the active state.
(NMC - NDC) x AH
NMC
13a. Equivalent Forced Each individual Forced Derating (D1, D2, D3) is
Derated Hours - EFDH transformed (D1, D2, D3) into equivalent full outage
hour(s). This is calculated by multiplying the actual
duration of the derating (hours) by the size of the
reduction (MW) and dividing by the Net Maximum
Capacity (NMC). These equivalent hour(s) are then
summed.
*Size of Reduction is determined by subtracting the Net Available Capacity (NAC) from the Net Dependable
Capacity (NDC). In cases of multiple deratings, the Size of Reduction of each derating will be determined by the
difference in the Net Available Capacity of the unit prior to the derating and the reported Net Available Capacity
as a result of the derating.
*Size of Reduction is determined by subtracting the Net Available Capacity (NAC) from the Net Dependable
Capacity (NDC). In cases of multiple deratings, the Size of Reduction of each derating will be determined by the
difference in the Net Available Capacity of the unit prior to the derating and the reported Net Available Capacity
as a result of the derating.
* Size of Reduction is determined by subtracting the Net Available Capacity (NAC) from the Net Dependable
Capacity (NDC). In cases of multiple deratings, the Size of Reduction of each derating will be determined by the
difference in the Net Available Capacity of the unit prior to the derating and the reported Net Available Capacity
as a result of the derating
* Size of Reduction is determined by subtracting the Net Available Capacity (NAC) from the Net Dependable
Capacity (NDC). In cases of multiple deratings, the Size of Reduction of each derating will be determined by the
difference in the Net Available Capacity of the unit prior to the derating and the reported Net Available Capacity
as a result of the derating.
Performance Indexes
The following sections describe performance indexes used to measure the performance of generating units. The
sections are divided into:
Calculation Notes
Please note that when you are calculating a single generating unit’s performance statistics, it does not matter if
you use unweighted- or weighted-based statistics. The answer will generally be the same. The real difference
between the unweighted and weighted statistics is in pooling (or grouping) of a set of generating units. In these
cases, a group of units of similar size will show only small differences, but a group of units where the MW size is
very different (greater than 50 MW), the statistics will be very different.
With unweighted statistics, all units are considered equal in outage impact. In the unweighted equations, no
MW size is introduced into the equations and the results are based on time, not energy produced or not
produced. In such cases, a 50 MW gas turbine and a 1,000 MW nuclear unit have the same impact on the
resulting statistics.
With weighted statistics, the larger MW size unit in the group has more impact on the final statistics than a
smaller generating unit. That is because the MW size of the unit (NMC) is part of the equation. In these cases, a
1,000 MW nuclear unit would have 20 times impact on the final outcome of the calculation than would its 50
MW gas turbine companion.
Using the unweighted equations currently in the IEEE 762 Standard (Section 7), an older, smaller, and little-run
unit will have just as much weight as a newer, larger, base-load unit. The effect of this could unrealistically and
disproportionately swing the fleet unweighted averages too high (for a very high availability on a small unit) or
too low (for a very low availability on a small unit).
However, the current IEEE 762 Standard's unweighted equations should not be abandoned even for group
statistics. There are valid applications for this method as well. (One being purely to evaluate equipment
reliability and availability regardless of size).
The weighted calculations, although primarily needed for grouping units' performance indexes, may apply to
individual units as well. The effect will be minimal, but over the months or years, many units' net maximum
capacities (NMC) change somewhat.
SPECIAL NOTE: To weight an equation, one does not simply take each unit's EFOR, for example, and multiply the
EFOR by the NMC, add them up and divide by the sum of the NMCs. Each term in the equation must be multiplied
by the NMC and then all the products are summed over all the units.
6. Unavailability Factor – UF
UF = UH x 100%
PH
7. Availability Factor – AF
AF = AH x 100%
PH
8. Service Factor – SF
SF = SH x 100%
PH
Note: Net capacity factor calculated using this equation can be negative during a period when the unit is shutdown.
(NOTE: This EUOF is identical to the Unit Capability Loss Factor except this equation includes all events, including
those outside plant management control.)
23. Forced Outage Rate Demand – FORd (See Notes 1 and 2 at the end of this section)
where
FOHd = f x FOH
The FOHd is the number of hours a unit was in a U1, U2, U3, or SF AND the unit would have operated had it been available.
load level, or energy price. When FOHd is determined directly from recorded periods of demand, service hours (SH)
in the above equation should include only those under the specified demand condition
If periods of demand are not recorded, FOHd may be estimated using the demand factor f. The demand factor is
applicable to traditional demand for economic or reliable system operation.
25. Equivalent Forced Outage Rate demand – EFORd (See Notes 1 and 2 at the end of this section)
where
FOHd = f x FOH
EFDHd = (EFDH – EFDHRS) if reserve shutdown events reported, or
= (fp x EFDH) if no reserve shutdown events reported – an approximation.
fp = (SH/AH)
The FOHd is the number of hours a unit was in a U1, U2, U3, or SF AND the unit would have operated had it been available.
ART = SH x 100%
Actual Unit Starts
MPOD = Planned Outage Hours which occur from in-service state only
Number of Planned Outages which occur from in-service state only
MUOD = Unplanned Outage Hours which occur from in-service state only
Number of Unplanned Outages which occur from in-service state only
MFOD = Forced Outage Hours which occur from in-service state only
Number of Forced Outages which occur from in-service state only
MMOD = Maintenance Outage Hours which occur from in-service state only
Number of Maintenance Outages which occur from in-service state only
AF = Σ AH x 100%
Σ PH
Σ PH
SF = Σ SH x 100%
Σ PH
*Special energy-weighted equations are not necessary for “energy terms” (GCF, NCF, GOF, NOF), because these
factors are inherently energy-weighted. These equations are the same as 7.12 – 7.15. But when calculating for a
group of units (or a unit that has a varying capacity value over time), do not simply average these factors. Follow
the equations.
* Special energy-weighted equations are not necessary for “energy terms” (GCF, NCF, GOF, NOF), because these
factors are inherently energy-weighted. These equations are the same as 7.12 – 7.15. But when calculating for a
group of units (or a unit that has a varying capacity value over time), do not simply average these factors. Follow
the equations.
55. Forced Outage Rate demand – FORd (See Notes 1 and 2 at the end of this section)
Where
FOHd = f x FOH
The FOHd is the number of hours a unit was in a U1, U2, U3, or SF AND the unit would have operated had it been available.
If periods of demand are not recorded, FOHd may be estimated using the demand factor f. The demand factor is
applicable to traditional demand for economic or reliable system operation.
r = Average Forced outage deration = (FOH) / (# of FO occurrences)
1 1 1 1 1 D = Average demand time = (SH) / (# of unit actual starts)
𝑓𝑓 = ( + )/( + + ) T = Average reserve shutdown time = (RSH) / (# of unit attempted starts)
𝑟𝑟 𝑇𝑇 𝑟𝑟 𝑇𝑇 𝐷𝐷
57. Equivalent Forced Outage Rate demand – EFORd (See Notes 1 and 2 at the end of this section)
where
FOHd = f x FOH
EFDHd = (EFDH – EFDHRS) if reserve shutdown events reported, or
= (fp x EFDH) if no reserve shutdown events reported – an approximation.
fp = (SH/AH)
The FOHd is the number of hours a unit was in a U1, U2, U3, or SF AND the unit would have operated had it been
available.
FOHd and EFDHd can be determined directly if periods of demand are recorded. Demand can be defined as the
traditional demand for the generating unit for economic or reliable operation of the system, or it can be any other
user-defined condition, such as specific weather condition, load level, or energy price. When FOHd and EFDHd are
determined directly from recorded periods of demand, service hours (SH) in the above equation should include only
those under the specified demand condition
If periods of demand are not recorded, FOHd may be estimated using the demand factor f. The demand factor is
applicable to traditional demand for economic or reliable system operation.
ART = Σ SH x 100%
Σ (Actual Unit Starts)
Σ (Service Hours)
MSTPO =
Σ (Number of Planned Outages which occur from in-service state only)
Σ( Service Hours)
MSTUO =
Σ (Number of Unplanned Outages which occur from in-service state only)
Σ (Service Hours)
MSTFO =
Σ (Number of (Unplanned) Forced Outages which occur from in-service state only)
Σ (Service Hours)
MSTMO =
Σ (Number of Maintenance Outages which occur from in-service state only)
.
81. Weighted Equivalent Maintenance Outage Factor – WEMOF
* Special energy-weighted equations are not necessary for “energy terms” (GCF, NCF, GOF, NOF), because these
factors are inherently energy-weighted. These equations are the same as 7.12 – 7.15. But when calculating for a
group of units (or a unit that has a varying capacity value over time), do not simply average these factors. Follow
the equations.
(NOTE: This is identical to the Weighted Unit Capability Loss Factor except this equation includes all events,
including those outside plant management control.)
87. Weighted Forced Outage Rate demand – WFORd (See Notes 1 and 2 at the end of this section)
Where
FOHd = f x FOH
The FOHd is the number of hours a unit was in a U1, U2, U3, or SF AND the unit would have operated had it been
available.
FOHd can be determined directly if periods of demand are recorded. Demand can be defined as the traditional
demand for the generating unit for economic or reliable operation of the system, or it can be any other user-defined
condition, such as specific weather condition, load level, or energy price. When FOHd is determined directly from
recorded periods of demand, service hours (SH) in the above equation should include only those under the
specified demand condition
If periods of demand are not recorded, FOHd may be estimated using the demand factor f. The demand factor is
applicable to traditional demand for economic or reliable system operation.
r = Average Forced outage deration = (FOH) / (# of FO occurrences)
1 1 1 1 1 D = Average demand time = (SH) / (# of unit actual starts)
𝑓𝑓 = ( + )/( + + ) T = Average reserve shutdown time = (RSH) / (# of unit attempted starts)
𝑟𝑟 𝑇𝑇 𝑟𝑟 𝑇𝑇 𝐷𝐷
89. Weighted Equivalent Forced Outage Rate demand – WEFORd (See Notes 1 and 2 at the end of this section)
where
FOHd = f x FOH
EFDHd = (EFDH – EFDHRS) if reserve shutdown events reported, or
= (fp x EFDH) if no reserve shutdown events reported – an approximation.
fp = (SH/AH)
The FOHd is the number of hours a unit was in a U1, U2, U3, or SF AND the unit would have operated had it been
available.
FOHd and EFDHd can be determined directly if periods of demand are recorded. Demand can be defined as the
traditional demand for the generating unit for economic or reliable operation of the system, or it can be any other
user-defined condition, such as specific weather condition, load level, or energy price. When FOHd and EFDHd are
determined directly from recorded periods of demand, service hours (SH) in the above equation should include only
those under the specified demand condition
If periods of demand are not recorded, FOHd may be estimated using the demand factor f. The demand factor is
applicable to traditional demand for economic or reliable system operation.
r = Average Forced outage deration = (FOH) / (# of FO occurrences)
1 1 1 1 1 D = Average demand time = (SH) / (# of unit actual starts)
𝑓𝑓 = ( + )/( + + ) T = Average reserve shutdown time = (RSH) / (# of unit attempted starts)
𝑟𝑟 𝑇𝑇 𝑟𝑟 𝑇𝑇 𝐷𝐷
Σ [(Planned Outage Hours which occur from in-service state only) x NMC]
WMPOD =
Σ [(Number of Planned Outages which occur from in-service state only) x NMC]
Σ [(Unplanned Outage Hours which occur from in-service state only) x NMC]
WMUOD =
Σ [(Number of Unplanned Outages which occur from in-service state only) x NMC]
Σ [Forced Outage Hours which occur from in-service state only) x NMC]
WMFOD =
Σ [(Number of Forced Outages which occur from in-service state only) x NMC]
Σ [(Maintenance Outage Hours which occur from in-service state only) x NMC]
WMMOD =
Σ [(Number Maintenance Outages which occur from in-service state only) x NMC]
Note: The equations for calculating unweighted (time-based) performance using outside management control
(OMC) are identical to those shown earlier in this Appendix. The only differences are that the selected OMC cause
codes are treated as non-curtailing events when analyzing the event records during the time of evaluation. In
other words, the OMC events are ignored and not used in the calculations.
The list of OMC cause codes, conditions and method for removing OMC events from the calculations is described
in Appendix K.
112. OMC Forced Outage Rate Demand – XFORd (See Notes 1 and 2 at the end of this section)
114. OMC Equivalent Forced Outage Rate demand – XEFORd (See Notes 1 and 2 at the end of this section)
Note: The equations for calculating weighted (capacity-based) performance using outside management
control (OMC) are identical to those shown earlier in this Appendix. The only differences are that the
selected OMC cause codes are treated as non-curtailing events when analyzing the event records during
the time of evaluation. In other words, the OMC events are ignored and not used in the calculations.
The list of OMC cause codes, conditions and method for removing OMC events from the calculations is described
in Appendix K.
136. OMC Weighted Forced Outage Rate demand – XWFORd (See Notes 1 and 2 at the end of this section)
138. OMC Weighted Equivalent Forced Outage Rate demand – XWEFORd (See Notes 1 and 2 at the end of this section)
PLEASE NOTE THAT after much consideration, NERC-GADS will use Method 2 in all its EFORd calculations. The
reason for method 2 is:
Consistency – all other GADS equations sum hours in both the denominator and numerator before
division.
Allow calculations of smaller groups. By allowing sums, smaller groups of units can be used to calculate
EFORd without experiencing the divide by zero problem (see Note #2 for Appendix F).
This method can give more weight to individual units with extreme EFORd that have very few service hours, but
with longer study time periods, the difference between the results of Methods I and II should be less.
This method may be more applicable in studying group statistics on units with known similar demand patterns,
especially for forecasting and modeling. By calculating the f-factors over the group’s total FOH, SH, RSH, and
starts, the f-factor is “smoothed” and not subject to be unduly influenced by an one or more single units
statistics that may have very high or very low hours or starts.
Method (III): Capacity Weighted Average of individually calculated EFORd used by PJM to calculate pool average
“unforced capacity” values for capacity market purposes.
In order to clearly demonstrate how these methods are used, two sets of comparison will be needed – the first
uses the unweighted, time-based calculations as shown in Appendix F. The second will use a weighted version of
these pooling methods.
Time-Based Pooling
This comparison of the three (3) pooling methodologies is based on the sample data and calculations found in
the following two tables. Table 1 shows the raw data reported by 5 steam turbine generating units. Table 2
shows the interim values of the calculations used to produce the individual EFORd for each unit In the interest of
simplicity each unit reported sufficient data to allow the EFORd calculation without the need for any substituted
values.
Using this data, the 3 pooling methods can be shown as follows – Note that methods 1 and 2 are unweighted,
time-based calculations.
• Method 1 uses the sums of SH and the calculated values (f x FOH), (fp x EFDH) giving a pooled EFORd of
7.591%.
(1818.598 + 347.480)
= 7.591%
(1818.598 + 26718)
• Method 2 uses the sums of the reported data to represent the average unit and then calculates the
pooled EFORd to be 7.922%
(1930.734 + 338.961)
= 7.922%
(1930.734 + 26718)
• Method 3 weights the individual EFORd values with the unit capacity (EFORd x MW) and uses the total
capacity to calculate a numeric average EFORd as 8.017%.
22.4483
= 8.017%
280
This method weights all time values by the Net Max Capactiy of the individual unit. The raw data is the same
as in the first example. Here Table 3 is added to show the weighted values used in the calculations.
Weighted values in Table 3 are denoted with preceding w to indicate that the value has been weighted by its
NMC. Below we substitute the weighted value for the expanded multiplication – wEFORd in place of (FORd x
NMC)
• Method 1 uses the sums of wSH and the weighted values (f x FOH x NMC), (fp x EFDH x NMC) giving a
pooled wEFORd of 7.601%.
• Method 2 uses the sums of the weighted reported data to represent the weighted average unit and
then calculates the pooled EFORd to be 7.912%
o
( ( f × ( ∑ wFOH ) ) + ( fp × ( ∑ wEFDH ) ) ) = wEFOR ( pooled )
( ∑ wSH + ( fp × ∑ wFOH ) )
d
Notes: From Section 7.12.2 EFORd = (FOHd + EFDHd) * 100 / (FOHd + SH)
From section 9, To energy-weight an equation, one does not simply take each unit's EFOR, for example, and
multiply the EFOR by the NMC, add them up and divide by the sum of the NMCs. Each term in the equation must be
multiplied by the NMC. Further, to calculate the sum of each term, EACH unit must be multiplied by its NMC, then
all those products summed over ALL THE UNITS, before the rest of the calculation is performed.
Another Sample
Compare this sample to the samples earlier, and you will see that the relationship between the methods does
not remain constant and is dependent on the distribution of the data.
This section also shows that a number can be forced but the results are not reasonable. The user of the EFORd
calculation must be aware of what may come from a number if the EFORd calculation is forced (see the notes at
the end of the section.)
PLEASE NOTE THAT NERC GADS will follow the recommendations of IEEE in calculating EFORd numbers. This
means that in some GADS reports, there will not be an EFORd number because a calculated EFORd would be
meaningless.
(Informational)
Typically, performance indexes are calculated using performance data over at least a year. However, if any of
the variables SH, FOH, or RSH is zero in a period, one practice has been to assign a default value of 0.001 for
computing indexes. Similarly, if any of the variables “number of FOH occurrences”, "number of attempted
starts", or "number of actual starts" is zero in the period, a value of 1 is assigned for computing indexes. The
default values can give meaningless indices in some cases as indicated in Table 7. Discretion based on history
and other factors may be used to estimate FORd and EFORd even if they can be calculated using the equations in
the standard in some cases.
The following numerical example illustrates the limiting conditions and how the indexes can become meaningless.
Case FOH EFDH SH No. of RSH Attempted Actual AH r T D f fp FORd% EFORd%
FO Starts Starts Factor Factor
Base 50 30 400 5 1600 80 80 2000 10 20 5 0.4 0.2 5.1 6.5
1 50 30 0 5 1600 1 1 2000 10 1600 0.001 0.0 0.0 83.4 83.7
2 0 30 0 1 1600 1 1 2000 0 1600 0.001 0.5 0.0 33.3 34.3
3 50 30 0 5 0 1 1 2000 10 0 0.001 0.5 0.0 100.0 100
4 0 30 400 1 1600 80 80 2000 0 20 5 1.0 0.2 0 1.5
5 0 30 400 1 0 1 1 2000 0 0 400 1.0 0.2 0 1.5
6 50 30 400 5 0 1 1 2000 10 0 400 1.0 0.2 11.1 12.4
7 0 30 0 1 0 1 1 0 0 0 0.001 0.7 1.0 40.0 1800040
Notes:
Zero hours are made 0.001. Attempted and Actual Starts are made 1 when SH or RSH is zero. Number of forced
outages is made 1 when FOH is zero.
Terms r, T, D, f, fp, FORd, and EFORd are defined in 7.16.2 and 7.17.2.
Cases 1, 2, 3, 7: Computed FORd, EFORd are meaningless; they should not be calculated using the equations in
this standard.
Introduction
The examples in this appendix illustrate the reporting of outages and deratings to GADS. They are based on a
fictional 600 MW coal-fired unit, Riverglenn #1, operated by the fictional “U.S. Power & Light Company.” All the
System/Component Cause Codes shown in these examples are real and found in Appendix B1 – Fossil Steam
Units.
Each example includes a description of circumstances surrounding the event, the effect of the event on unit
availability, and component repair time.
For the sake of space, the verbal description element (reported in Sections C and D of the event report (07)) is
left out of the event description. Completing this information provides details about a failure’s cause and
appearance, identifies any contributing factors, and describes the corrective actions taken. Please refer to pages
III-29 through III-30 for a discussion regarding the verbal description.
Index of Examples
Event Description
On January 3 at 4:30 a.m., Riverglenn #1 tripped off-line due to high turbine vibration. The cause was Low
Pressure (LP) turbine bearings. Repairs began January 3 at 8:00 a.m. and were completed on January 8 at 9:30
a.m. The unit synchronized on January 8 at 5:00 p.m.
Component Repair
The LP turbine bearings took 121.50 hours to repair (January 3, 8:00 a.m. to January 8 at 9:30 a.m.).
500_
400_
300_
200_
100_
0_
Jan 3 Jan 8
04:30 17:00
Figure 1-G - Simple Outage
Event Description
On January 10 at 8:00 a.m., Riverglenn #1 reduced capacity by 400 MW due to a fouled north air preheater.
Fouling began a few weeks earlier, but the unit stayed on-line at full capacity to meet load demand. Repair
crews completed their work and the unit came back to full load (600 MW) on January 11 at 4:00 p.m.
Thus, the availability of Riverglenn #1 is impacted for 21.33 Equivalent Derated Hours.
Component Repair
The air preheater required 32 hours to repair. The hours are not equivalent.
500_
400_
300_
200_
100_
0_
Jan 10 Jan 11
08:00 16:00
Description of Events
Riverglenn #1 experienced an immediate 75 MW derating on March 9 at 8:45 a.m. The cause was an “A”
pulverizer feeder motor failure (Derating “A”). Net Available Capacity (NAC) as a result was 525 MW.
At 10:00 a.m. the same day, the unit lost another 75 MW due to a trip of the “B” pulverizer feeder motor. The
Net Available Capacity (NAC) as a result of the second derating (Derating “B”) was 450 MW. The motor was
restarted and Derating “B” ended an hour later. The capability of the unit increased by 75 MW at this time.
Derating “A” ended when the “A” feeder motor was repaired and the unit brought back to full load at 6:00 p.m.
on March 9.
Derating “A”
Derating “B”
the second derating is determined by subtracting the Net Available Capacity as a result of second derating from
the Net Available Capacity of the unit as a result of the first derating.
The following shows the availability impact these two deratings had on the unit:
Derating “A”: [(600 MW - 525 MW) * 9.25 hour]/600 MW = 1.16 Equivalent Derated Hours
Derating “B”: [(525 MW - 450 MW) * 1.00 hour]/600 MW = 0.125 Equivalent Derated Hours
Component Repair
When “Time: Work Started” and “Time: Work Completed” are blank or asterisk-filled, the reported Start of
Event and End of Event determine component repair time.
In this example, 10.25 hours are charged against the pulverizer feeder motor for repair (9.25 hours for Derating
“A” and 1 hour for Derating “B.”) These hours are not equivalent.
Derating “A”
500_
Derating “B”
400_
300_
200_
100_
0_
March 9 March 9 March 9 March 9
08:45 10:00 11:00 18:00
Figure G-3A — Overlapping Deratings
Description of Events
A derating began on July 3 at 2:30 p.m., when capacity was reduced to 575 MW for condenser maintenance. The
maintenance began July 13 at 8:00 a.m. The event ended on July 23 at 11:45 a.m.
On July 19 at 11:15 a.m., while the maintenance derating was in progress, a feedwater pump tripped. Load
immediately fell to 360 MW. (This would have been the case, whether or not the unit was already derated.) The
feedwater water pump was back in service at noon the same day.
Report the following on Records 01, 02, and 03 of Event Report (07):
Derating “A”
Derating “B”
The second derating caused the unit’s available capacity to change from 575 to 360 — a 215 MW reduction.
Under normal conditions (no other events in progress) the feedwater pump trip would have caused a reduction
in load to 360 MW — a loss of 240 MW. This means that 25 MW, which would be attributed to Derating “B” if it
had occurred alone, are shadowed by Derating “A.” Because of the additive assumption, these equivalent hours
are not double counted.
Derating “A”: [(600 MW - 575 MW) * 477.25 hours]/600 MW = 19.88 Equivalent Derated Hours
Derating “B”: [(575 MW - 360 MW) * 0.75 hours]/600 MW = 0.27 Equivalent Derated Hours
Component Repair
Condenser maintenance took 243.75 hours. The feedwater pump was out of service for 0.75 hours. These hours
are not equivalent.
Derating “A”
500_
Derating “B”
400_
300_
200_
100_
0_
July 3 July 19 July 19 July 23
14:30 11:15 12:00 11:45
Description of Events
A 50 MW load reduction occurred on January 13 at 8:00 a.m. for a feedwater heater inspection
(Derating “A”). The inspection had been planned several months earlier.
At 10:00 a.m., Riverglenn #1 experienced excessive pulverizer vibration. Available Capacity changed from 550
MW to 350 MW — a 200 MW reduction — as a result. A foreign object was the cause.
While the mill was under repair, the feedwater heater was put back in service, ending Derating “A” at 1:00 p.m.
on January 13. This caused a 50 MW increase in the unit’s Net Available Capacity.
Derating “B” ended on January 14 at 8:00 p.m. after completing pulverizer repairs.
Derating “A”
Derating “B”
Derating “A”: [(600 MW - 550 MW) * 5.00 hours)/600 MW = 0.42 Equivalent Derated Hours
Derating “B”: [(550 MW - 350 MW) * 34.00 hours)/600 MW = 11.33 Equivalent Derated Hours
Component Repair
The feedwater heater took 5 hours to repair and the pulverizer took 34 hours.
DERATING “A”
500_
400_
200_
100_
0_
Jan 13 Jan 13 Jan 13 Jan 14
08:00 10:00 13:00 20:00
Description of Events
A circuit breaker tripped, causing an immediate 100 MW load reduction on March 10 at 6:30 a.m. (Derating “A.”)
At 7:45 a.m. the same day, a traveling screen jammed, causing one of the unit’s circulating water pumps to shut
down (Derating “B”). Net Available Capacity as a result of the event was 360 MW.
Derating “A” ended at 10:30 a.m. on March 10 when the circuit breaker repairs were completed. However, the
traveling screen problem continued, forcing the unit to remain at 360 MW. The unit was available for full load
on March 7 at 7:00 p.m. after completing repairs to the traveling screen.
Derating “A”
Derating “B”
Derating “A”: [(600 MW - 500 MW) x 1.25 hours]/600 MW = 0.21 Equivalent Derated Hours
Derating “B”: [(600 MW - 360 MW) x 11.25 hours]/600 MW = 4.50 Equivalent Derated Hours
Component Repair
The circuit breaker and the traveling screen are charged with 2.50 clock hours of repair and 11.25 clock hours of
repair, respectively.
Derating “A”
500_
Derating “B”
Derating “B”
400_
300_
200_
100_
0_
March 10 March 10 March 10 March 10
06:30 07:45 10:30 19:00
Event Description
A generator output breaker failed at 6:30 a.m. on April 10 causing a 300 MW reduction. Repairs began at 8:00
a.m. The unit returned to full capacity at 7:00 p.m. April 10.
During the generator repair, a problem with the feedwater chemistry developed, and it was corrected by 3:45. If
it had occurred alone, a reduction of 200 MW would have been needed. This was not necessary because of the
derating already in existence.
Component Repair
Although the feedwater chemistry problem does not affect unit availability, its occurrence should be reported.
This information is important for analysis purposes. Use Section D – Additional Component Worked During
Event of the Event Report (07) to do so.
Repair of the generator output breaker took 10.25 hours. It took 7.25 hours to correct the feedwater chemistry
problem.
Additional Components
Worked
500_
400_
300_
200_
100_
0_
April 10 April 10
06:30 19:00
Description of Event
A reserve shutdown began on May 31 at 7:30 p.m. Maintenance crews took advantage of the off-line time and
took one boiler feedpump (BFP) out of service (two other BFP were available). The work started at 8:00 a.m. on
June 1 and ended on June 2 at 3:30 p.m. While the BFP valve maintenance was underway, the unit would have
been able to synchronize, but would have been limited to 400 MW.
In this example, Riverglenn was available for full load until the BFP valve work began. The status of the unit
changed because it was no longer available for full load. A derating event must be reported. (An outage would
be reported if the unit would have been unable to synchronize while the BFP work was in progress.) The unit
availability impact resulting from the BFP valve maintenance is:
Component Repair
The feedwater pump steam turbine required 31.50 hours to repair.
500_
Derating
400_
300_
200_
Reserve Shutdown
100_
0_
May 31 June 1 June 2 Jan 8
19:30 08:00 15:30 17:00
Description of Events
Riverglenn #1 lost 100 MW due to a feedwater heater high-level trip at 9:45 a.m. on February 27. An L.P. heater
tube leak was the cause. Repairs began March 2 at 8:00 a.m. A superheater tube leak on March 2 at 1: 15 a.m.
caused the unit to trip off-line.
The feedwater heater (cause of the derating) was repaired by March 4 at 6:30 p.m.
Repairs to the superheater (cause of the outage) were completed on March 4 at 10:00 p.m. The unit synchronized
on March 5 at 9:22 a.m.
Once initiated, the outage assumes full responsibility for loss of availability. That is 80.12 hours in this example.
Component Repair
The feedwater heater was unavailable for 128.75 hours, the superheater for 80.12.
Derating
500_
400_
300_
Outage
200_
100_
0_
Feb 27 Mar 2 Mar 4 Mar 5
0
1
09:45 : 18:30 09:22
1
5
Description of Events
A pulverizer motor failed on May 18 at 09:45 a.m. causing a 100 MW derating.
While the unit was derated, a maintenance crew discovered a severe water wall tube leak, forcing the unit off-
line immediately. That occurred on May 20 at 6:45 p.m. The tube was welded, and the unit brought back into
service at 2:42 a.m. on May 24. Pulverizer repairs were still in progress, so the unit was limited to 500 MW. The
unit was available for full load on May 25 at 2:30 p.m. when pulverizer repairs were completed.
[(600 MW - 500 MW) * (57.00 Hours + 35.80 Hours)]/600 MW = 15.47 Equivalent Derated Hours
Component Repairs
Repair of the pulverizer motor, the cause of the derating, took 172.75 hours. The waterwall tube section repairs
took 79.95 hours.
400_
300_
Outage
200_
100_
0_
May 18 May 20 May 24 May 25
09:45 18:45 02:42 14:30
Event Description
Riverglenn began its normal 15-hour startup cycle following a two-week planned outage on October 1, 7:00 a.m.
At the end of the normal cycle; however, the unit was not ready to synchronize. The reason was excessive H.P.
turbine rotor vibration. The problem was corrected and Riverglenn #1 synchronized at 3:00 a.m. on October 3.
Component Repair
The H.P. turbine rotor shaft took 17 hours to repair.
*An outage or reserve shutdown must immediately precede a Startup Failure event. The end of the outage must
be the same as the start of the SF event (see Page III-8).
500_
Planned Outage
400_
Startup Failure
300_
200_
100_
0_
From Oct 1 Oct 3
September 22:00 03:00
Description of Events
On June 10 at 8:00 a.m., management decided to operate Riverglenn #1 at 50% capacity – 300 MW – in order to
avoid a potential fuel shortage. If system demand increased, Riverglenn would be returned to full load. Because
Riverglenn was not limited by equipment, the decision to operate at a reduced load was an economic issue.
On August 25 at 5:00 a.m., the station reported that fuel was in short supply and the unit could no longer reach
full load as a result. An unplanned derating began when fuel became a limitation. The Net Available Capacity as
a result of the derating was 300 MW.
Riverglenn’s fuel supply was exhausted on September 3 at 9:00 p.m. and the unit was forced out of service. A
new supply of fuel was delivered on September 4. The unit was restarted and synchronized at 4:00 p.m. on
September 6.
Report the following on Records 01, 02, and, 03 of Event Report (07):
The situation described typically affects fossil and hydro units. Nuclear units are sometimes operated at reduced
levels to “stretch the core” in order to prolong the time to the next refueling. If the reactor core is capable of full
load, the decision to operate at a lower level is an economic issue and therefore not reportable to GADS. When
the core can no longer support operation at full load, a planned derating (PD) is reported. This condition is
sometimes referred to as “coasting down.” The magnitude of these deratings usually increase incrementally
and should be reported as a series of PD events.
500_
Forced
Derating
400_
300_ Forced
Outage
200_
100_
0_
From Aug 25 Sept 3 Sept 6
June 05:00 21:00 16:00
Example 9: Transitions - U2 to RS to SF
Description of Events
After experiencing several hours of excessive scrubber ID fan vibration, Riverglenn was taken off line for repair on
December 3 at 3:30 p.m. After pinpointing the problem, repairs were made. The unit was ready to begin its normal
15-hour startup cycle by 21:30 p.m. on December 5. However, due to low demand, Riverglenn entered the reserve
shutdown state. Startup began at 2:30 a.m. the following morning. Several waterwall tubes burst during the
startup, requiring immediate repair. The tube problem occurred at 9:00 a.m. on December 6. After repairing the
tubes and a successful startup, Riverglenn synchronized on December 9 at 5:00 p.m.
Component Repair
The scrubber ID fan is charged with 38.50 repair hours, and the water wall tubes with 80.00 repair hours.
** Reporting a primary cause of event for Reserve Shutdowns is optional. In this example, Records 02/03 were
omitted.
500_
400_
200_
100_
0_
Dec 3 Dec 5 Dec 6 Dec 9
15:30 21:30 09:00 17:00
GADS
Codes Description
GADS
Codes Description
GADS
Codes Description
F790 Testing
F800 Thermal fatigue
F810 Torn
F820 Tripped/shutdown component --- automatic controls
F830 Tripped/shutdown component --- manual
F840 Unknown – investigation underway (change this code once failure mechanism is determined)
F850 Vibration, not within limits
F860 Vibration fatigue, leading to failure
F870 Voltage, not within limits
F880 Welded relay contacts
F890 Weld failure – broken weld
F900 Weld failure – dissimilar metals
F910 Weld failure – weld defects
F920 Wiped
F930 Worn, excessively
FA00 Silica restriction
FC00 Cleaning
FD00 Water Induction
FE00 Emission/environmental restrictions
FF00 Fouling
FP00 Personnel error
FR00 Fire
FS00 Slagging
FU00 Parts Unavailable
FV00 Vibration
FW00 Wet coal/frozen coal/debris
FX00 External equipment malfunction (outside plant management control)
Introduction
The NERC Generating Availability Data System (GADS) contains information which can be broadly classified into
two categories: design data, which is descriptive of the physical and operational characteristics of equipment,
and performance and event data, which constitutes a record of equipment availability over a period of time.
The design data is unrestricted and available to power generators, equipment suppliers and manufacturers,
architect-engineers and consultants, industry organizations (EEI, EPRI, INPO, etc.), federal governmental
organizations, and state and local governmental organizations.
To avoid the potential misuse of individual equipment data, the performance and event data are restricted and
available only as specified in these guidelines.
Special reports or studies which describe or rank power generators, pools, or Regions by performance or other
attributes – and in which specific units, power generators, pools, or regions are identifiable either by inclusion or
exclusion – will be provided only with the authorization of the appropriate power generators, pools, or regions.
Obtaining these approvals is the responsibility of the requester.
The "standard publication" mentioned in the following paragraphs is that approved and recognized as such by
the NERC Planning Committee. The current publication is the GADS Statistical Brochure. The latest versions can
be downloaded from the NERC website i.
Power generator owners/operators who do not report any GADS data or only part of the full sets of unit data as
outlined in the GADS Data Reporting Instructions Table III-1 (shown as “required” for the different unit types)
may only receive standard publications but will not receive any special data analyses or data analysis-type
software products like pc-GAR.
Appendix I - GADS Data Release Guidelines
Non-Industry Organizations
Non-industry organizations may receive the standard publication. They may also receive any analyses that do
not identify individual units, power generators, pools, or regions. Responses to requests for unit, power
generator, pool, or regional specific data will be coordinated through the appropriate power generator(s),
pool(s), or Region(s).
Foreign Correspondents
Foreign correspondents may receive the standard publication. They may also receive grouped analyses at the
discretion of the NERC staff.
Responding to Requests
All requests must be submitted in writing and will be answered on a timely basis with special attention given to
requests identified as urgent.
i
http://www.nerc.com/pa/RAPA/gads/Pages/Reports.aspx
The purpose of the amplification code is to further identify the cause of an outage by describing the failure mode.
The amplification code is two alpha-numeric characters following the cause code (see Page III-25). Failure modes
are leaks, corrosion, personnel error, fire, etc. They are almost identical to the GADS Failure Mechanism Codes
(see Appendix H) except the Cause Code Amplification Code is just two-characters. Some existing cause codes
contain these amplification codes as part of their description. The Cause Code Amplification Code allows all cause
codes to be described with the set of failure modes without increasing the number of cause codes. It will also
allow analysts to further explore the common causes of outages.
There are a few cases where the amplification code is limited to specific event types or conditions. The table below
captures the specific limits. “None” means that the amplification codes can be used with any event types.
GADS Event
Amplification Description Type
Code Limits
GADS Event
Amplification Description Type
Code Limits
Contaminated – liquid fluids (use F320 for air
17 None
contamination)
18 Contaminated – metals and solids None
20 Cooling, inadequate --- air None
19 Cooling, inadequate --- liquid None
22 Corrosion – caustic None
23 Corrosion – fatigue None
21 Corrosion – general None
24 Corrosion – high temperature coal ash None
25 Corrosion – high temperature oil ash None
26 Corrosion – low temperature None
27 Corrosion – waterwall fire-side None
28 Cracked None
29 Creep, high temperature None
30 Damaged, foreign object None
31 Damaged, insulation None
Dirty (use for air contamination or particulate/dirt
32 None
buildup)
33 Disengage, failed to None
E0 Emission/Environmental Restriction None
34 Engage, failed to None
35 Erosion – coal particle None
36 Erosion – falling slag None
38 Erosion – fly ash None
37 Erosion – sootblower None
39 Erosion – cause unknown None
40 Erratic or unexplained operating behavior None
41 Erratic, circuit None
42 Error, operator None
43 Error, wiring None
Explosion damage – initiated by the component
44 None
(ex. pump explosion)
Explosion damage – not initiated by the component
45 None
(ex. pipe damage due to pump explosion)
GADS Event
Amplification Description Type
Code Limits
External equipment malfunction (outside plant
X0 None
management control)
R0 Fire None
46 Flameout None
47 Foaming None
F0 Fouling None
48 Frozen (temperature related) None
FR Fuel related None
49 Grounded electrical component None
50 Hydrogen damage None
51 Impact damage None
52 Indication, false None
53 Inspection None
54 Leaks None
55 Loose None
56 Lubrication – excessive None
57 Lubrication – lack of None
58 Maintenance – cleaning damage None
59 Maintenance – general None
60 Material defects None
61 Modification(s) None
NF No fuels None
62 Noisy None
NF No Fuel None
63 Open None
64 Overload None
U0 Parts unavailable None
P0 Personnel error None
65 Pitting (localized corrosion) None
66 Pressure, not within limits None
Rubbing damage – axial related contacts (use F050
67 None
if contact is in radial direction)
68 Secondary damage None
69 Seized (not moving) None
71 Short-term overheating None
GADS Event
Amplification Description Type
Code Limits
70 Shorted electrical component None
A0 Silica restriction None
S0 Slagging None
ST Steam transfer None
72 Sticking None
73 Stress corrosion cracking None
H0 Temperature – high, not within limits None
Temperature – compressor discharge, not within
74 None
limits
75 Temperature – exhaust, not within limits None
78 Temperature – general, not within limits None
76 Temperature – oil, not within limits None
77 Temperature – wheel spacers, not within limits None
79 Testing None
80 Thermal fatigue None
81 Torn None
82 Tripped/shutdown component – automatic Deratings only
83 Tripped/shutdown component – manual Deratings only
In-service U1
T1 Tripped/shutdown grid separation – automatic
outage only
In-service U1
T2 Tripped/shutdown grid separation – manual
outage only
Unknown – investigation underway (change this In-service U1
84
code once failure mechanism is determined) outage only
V0 Vibration (other) None
86 Vibration fatigue, leading to failure None
85 Vibration, not within limits None
87 Voltage, not within limits None
D0 Water induction None
89 Weld failure – broken weld None
90 Weld failure – dissimilar metals None
91 Weld failure – weld defects None
88 Welded relay contacts None
W0 Wet coal/frozen coal/debris None
92 Wiped None
93 Worn, excessively None
Following this introduction of Outside Management Control (OMC) guidelines, we have listed
those cause codes that GADS recognizes as being outside plant management control. At the end
of this Appendix are guidelines for removing OMC events from standard calculations.
The electric industry in the Europe and other parts of the world has made a change to examine
losses of generation caused by problems with and outside plant management control. After
reviewing the work used by others, the following is provided as guidelines for determining what
is and is not outside plant management control:
There are a number of outage causes that may prevent the energy coming from a power
generating plant from reaching the customer. Some causes are due to the plant operation and
equipment while others are outside plant management control.
The standard sets a boundary on the generator side of the power station (see Figure D-1, below)
for the determination of equipment "outside management control".
Typical Interconnection
Generation Facility
(2) Out
Utility Distribution Co. ISO
Metering Metering
In
Disconnect Device Owned &
Operated by Generation Entity
Generator
Auxiliary Load
AUX Generator
PT A
Breaker
Generator
Figure D-1
The Physical Boundary of Outside Management Control
As shown in Figure D-1, a generating unit includes all equipment up to (in preferred order) (1)
the high-voltage terminals of the generator step-up (GSU) transformer and the station service
transformers; (2) the GSU transformer (load) side of the generator-voltage circuit breakers; or (3)
at such equipment boundary as may be reasonable considering the design and configuration of
the generating unit.
It may be assumed that all problems within the power station boundary are within plant
management control; however that is not always the case. Therefore, there is a need for some
additional clarification as to what is and what is not under plant management control.
It is easier to identify those actions outside plant management control than to identify the
responsibilities of plant management. Therefore, the following are considered to be outside
(external) of plant management control. All other items are considered within their jurisdiction
and are the responsibility of the plant management for calculating power plant performance and
statistics.
Energy losses due to the following causes should not be considered when computing the unit
controllable performance because these losses are not considered to be under the control of plant
management:
Grid connection or substation failure. This reason relates to problems with transmission
lines and switchyard equipment outside the boundaries of the plant as specified by the
“boundary of plant responsibility” shown in Figure D-1 on this Annex.
Acts of nature such as ice storms, tornados, winds, lightning, etc are not under plant
management control, whether inside or outside the plant boundary.
Special environmental limitations such as low cooling pond level, or water intake
restrictions that could not be prevented by operator action. These are acts of nature such
as high ambient temperatures where the equipment is working within design
specifications. However, if the equipment is not maintained by the plant such as opacity
out of limits or NOx out of control, etc, then plant management should be penalized.
These are equipment problems and are within plant management control.
Lack of fuels (water from rivers or lakes, coal mines, gas lines, etc) where the operator is
not in control of contracts, supply lines, or delivery of fuels.
However, if the operator elected to contract for fuels where the fuel (for example, natural
gas) can be interrupted so that the fuel suppliers can sell the fuels to others (part of the
plant fuel cost-saving measure), then the lack of fuel is under management control and is
not applicable to this case.
Labor strikes. Outages or load reductions caused by labor strikes are not normally under
the direct control of plant management. These strikes may be company-wide problems or
strikes outside the company’s jurisdiction such as manufacturers (delaying repairs) or
transportation (fuel supply) problems.
However, direct plant management grievances that result in a walkout or strike are under
plant management control and are included as penalties against the plant. If a labor strike
is caused by plant management/worker problems during an outage, any outage extensions
are included as energy losses as long as the unit is incapable of being restarted because of
equipment failures, maintenance, overhauls, or other activities.
Other weather related problems such as seasonal variations in gross dependable capacity
due to cooling water temperature variations are not within plant management control.
This completes the quote from Annex D of IEEE 762. For more comments on OMC
events, please refer to Section I-2 and III-13 of these GADS Data Reporting Instructions.
Background
The IEEE 762 “Definitions for Reporting Electric Generating Unit Reliability, Availability and
Productivity” (Annex D) is the basis for the OMC work. In part, Annex D states that:
“There are a number of outage causes that may prevent the energy coming from a power
generating plant from reaching the customer. Some causes are due to the plant operation
and equipment while others are outside plant management control.”
This Appendix K lists a number of cause codes that is universally accepted as those outside the
control of management by the GADS program. It also identifies certain conditions under which
those specific cause codes would be applied. The list may change with time and some additional
clarifications may be added.
The list of cause codes shown hereafter should be reviewed from time to time to insure the latest
cause codes are used in the OMC equations.
It is also VERY important that all cause codes (including all OMC cause codes) be reported to
GADS. Some companies may wish to exclude a forced outage or change it to a non-curtailing
event if it fits into the OMC category. THAT IS NOT RIGHT! The event should be reported as a
forced outage and the OMC calculations will show the events without the FO.
OMC events will come in two forms: outages or deratings. The OMC event types can be either
forced, maintenance or planned but it is expected that the majority will be forced outage events.
For all existing GADS equation calculations, the OMC events will be treated as a standard event,
i.e., a forced outage, forced derate, etc. The calculation will not change and will follow the
calculations shown in Appendix F of the GADS DRI.
In calculating equations without OMC events, it is important to remember that the objective of
the removal of OMC events is to affect the availability of the unit. To that end, we handle
outages differently than derates. In removing a particular event from a unit’s event records we
are faced with the question of what to put in place of the missing event. In the case of an outage,
there is no sure way of knowing in what state a unit should be considered. The only sure thing is
our objective of returning those hours to an available state. That is exactly what we do and that is
all we do. Assuming that the unit is in reserve or in service during the time of the removed OMC
outage event, and so, adding to either service or reserve hours presents a fictional summary of
the unit’s performance. In viewing the available hours we temporarily recalculate AH as
(Service + Reserve + Synchronous-Condensing. + Pumping + OMC).
In the case of a derating event, however, we know for certain the state of the unit at the time of
the removed event. Knowing this forces us to place at least part of the equivalent available hours
gained in to either reserve or service. Whenever an event is removed it is necessary to look for
any derating events that may have been shadowed by or overlapping the removed event. Those
overlapping hours must be accounted for by the software processing the OMC event. It isn’t
enough to simply recalculate Equivalent Availability by adding the sum of the removed OMC
events because we need to now take into account the effect of the newly uncovered (un-
overlapped) derating events.
Before we begin defining the methods there is an important assumption that needs to be made as
to the processing of the data. – Since the removal of the OMC outage event is seen as an
adjustment, we’ll assume that outage events have been processed as normal and that OMC
removal is acting on clean data and that performance totals have already been summed for the
unit. Also, in the case of derate events, that loss attributed to an event has been calculated
particularly in the case of overlapping and shadowed events.
2. Derate Events – In removing OMC derate events, it is important to keep in mind that
the loss of capacity originally calculated and attributed to an event is maintained when
the OMC event is removed. The removal of the OMC event then properly affects the
available capacity of the unit rather than increasing the losses attributed to the
surrounding / overlapping derating events. Illustrations are included below in order to
aid the explanations.
a. A simple OMC derate – When there are no overlapping derating events, the
equivalent hours of the OMC event can be removed from the total equivalent
hours and the associated event occurrences can also be reduced by 1. The
number of derate hours also is reduced by the duration of the event.
d. A dominant OMC derate overlaps another derate – When the OMC derate
event is marked as dominant, multiple adjustments may be necessary. The first
adjustment is to take care of the total duration and equivalent hours of the OMC
derate event. Once the OMC derate event affect is removed, the overlapped
derate event(s) need to be accounted for by subtracting those portions of the
event(s) that were overlapped by the OMC event from the equivalent hours total
as well as the any total durations. The number of derate event occurrences would
not need to be adjusted.
OMC Outage (any type) is removed from Unit available hours increase by the outage
shadowed derate. duration. Equivalent hours are adjusted
downward by the overlapped portion when
derate d1 is now accounted for at its actual
value.
OMC Derate is removed from under D2 Loss attributed to D2 remains unchanged. NAC
of the unit increases
OMC Derate is removed from inside D2 Only the portion outside the dominant derate is
adjusted back to available hours
Dominant OMC Derate is removed. Events D1, D2 and D4 are extended and
totalled at their original values.
OMC Derate is removed from being shadowed by The effect of removing the OMC event is to
an outage (any type) increase availability by the portions which
extend beyond the outage.
In the October 2003 GADS DRI, there are two equations listed in Appendix F that exclude OMC
event hours. These two equations, Weighted Unit Capability Factor (WUCF) and Weighted Unit
Capability Loss Factor (WUCLF) are used in Europe and are a start (not the only ones but a
start) of equations for excluding OMC events. WUCF is the equivalent to WEAF without OMC
events; WUCLF is the equivalent to Weighted Equivalent Unplanned Outage Factor without
OMC events. Both are capacity-weighted calculations.
There will be a number of other equations that people will want without OMC events including
FOR, EFOR, EFORd, AF, or any equation that uses forced outage or unplanned outage numbers
in it. The same principal will apply to planned or maintenance OMC events, if any. This type of
reaction to OMC is expected. But there must be a method for clarifying which calculations
include and exclude OMC events.
Please note that all equations that include OMC events be calculated in the same methods and
have the same names as that in IEEE 762 and Appendix F of the GADS DRI. In other words,
those equations will not change at all but will be the benchmark as to what the unit was able to
provide under all circumstances.
Please note also that any equation that excludes OMC events be calculated in the same methods
as that in IEEE 762 and Appendix F of the GADS DRI but the names are modified to show they
exclude OMC events. These equations will be used against the benchmark calculations to show
what the unit could have done without OMC events. Both numbers will be provided by GADS
and either number can be used based on the needs and the reports.
As a convention for identifying equations and calculations without OMC events, it is proposed
that for any equation without OMC events, that the name be modified with a starting “X” for
“exclude” as a lead. Thus, EFOR without OMC events would be XEFOR, EFORd without OMC
events would be XEFORd, POF with OMC events would be XPOF, etc. The “X” is to show that
the equation excludes OMC events and the remainder of the name shows how it is calculated.
EFOR and XEFOR are both apples but one is a Macintosh and the other a Roman Beauty.
This document applies only to reporters who wish to report event and performance data for each generating
unit individually. This document does not apply to reporters wishing to continue reporting combined-cycle data
to GADS as a ‘single unit’ (or traditional method). GADS will still accept the traditional method but it is not
favored over the reporting of each generating unit within the block.
Please Note: The majority of this document is the same as the fleet-type roll up method. The basic data gathering
process on a unit-level basis is identical in all respects. The differences are in creating block statistics from the
unit-level data.
IEEE 762 does not address reporting separate units and bringing the components together to create combined-
cycle block statistics. Therefore, this document establishes a NERC methodology for creating new combined-
cycle block event and performance records based on reported unit-level event and performance records.
Terms
To insure proper documentation, some terms must be agreed on to eliminate some of the ambiguity concerning
combined-cycle blocks in general.
Combined-Cycle Block (also known in the industry as a “Block”) – By definition, a combined cycle is a
process for generating energy (either electricity or steam) constituted by the marriage of a Brayton
Cycle (expand hot gas to turn a gas turbine) with a Rankine Cycle (use heat to boil water to make steam
to turn a steam turbine). A combined-cycle block employs electric generating technology in which
electricity and process steam is produced from otherwise lost waste heat exiting from one or more
combustion turbines. In most situations, the exiting waste heat is routed to a conventional boiler or to a
heat recovery steam generator (HRSG) for use by a steam turbine in the production of electricity.
Therefore, the combined-cycle block consists of one or more gas turbines/jet engines, one or more
steam turbines, and balance-of-plant equipment supporting the production of electricity or steam
energy.
Appendix L-1 – Calculating Combined-Cycle and Co-generation Block Data
There may be more than one combined-cycle block at a plant site. Our discussion relates to each individual
combined-cycle block reporting, not the process of reporting several combined-cycle blocks as one plant site.
Units – Each generator set is considered a “unit.” Typically in combined cycle, each gas turbine or jet
engine and each steam turbine are considered a “unit.” Each unit contributes to the total electric
generation of the combined-cycle block
Heat Recovery Steam Generator (HRSG) – There may be one or more HRSG or waste heat boilers in a
combined-cycle block. Some units may have a single HRSG per GT/jet; others may have several GT/jet
feeding a single HRSG. The HRSG does not contribute electricity to the output of the combined-cycle
block and so, is considered a component rather than a unit.
Other Balance of Plant Equipment – There are other equipment in the combined-cycle block used to
support the production of electricity. They are not related to any specific part of the block and are also
considered as components.
Units - The design data is reported as though each unit were a separate generator. This meaning that
each unit would have its own unit number and design data as described in the NERC guidelines for each
unit type. In addition to this, the unit would be marked as being part of a combined-cycle block by a field
that would hold the Identifying 800 series unit code of the combined-cycle block.
Combined-Cycle Block – Balance of plant and other equipment not directly related to each unit is coded
as described for the combined-cycle block.
Cause Codes
Since each unit of the combined-cycle block can affect the generation of the other units, it is possible to have a
situation where a derate in a gas turbine or jet engine may have a steam turbine cause code. (See Example 2
below). In other words, the cause codes for all units will be open to all task-force-approved cause codes for all
units within the combined-cycle blocks.
Therefore, if you operate a combined-cycle block with 2 gas turbines and one steam turbine, you will report 36
performance records annually – one set of 12 performance records for each gas turbine unit and one set of 12
performance records for the steam turbine unit.
Include units – ex: Create a gas turbine peer group that includes gas turbines in simple-cycle operation
with those in combined-cycle blocks.
Include units only – ex: view gas turbine units in combined-cycle blocks operation only.
Combined-cycle blocks will be available for each of the three groups shown below or groups 1 and 2 or 1
and 3:
1. Not rolled-up (neither syntheses nor fleet) but used only reported block data as supplied by the
reporter (traditional data reporting).
2. Creating block data using the synthesis event and performance method shown in this document.
3. Creating block data using the fleet-type roll up method described in a separate document
“Calculating Combined-Cycle Block Data Using a Fleet-type Roll up Method When Reporting
Each Gas Turbine/Steam Turbine Unit.”
Not everyone will wish to use some of these options. However, GADS is committed to providing options to all
since the individual needs of GADS data users vary.
Special Rules Used in Calculating Synthesized Combined-Cycle Block Data from Unit-level
Data
Some rules for calculating synthesized combined-cycle block data are necessary. The rules will insure uniformity
in creating synthesized statistics from the unit-level data.
RULE #1: the outage for the combined-cycle block starts when the breaker of the last of the units is opened and
ends when the breaker of the first unit is closed.
RULE #2: the number of attempted and actual starts for the combined-cycle block is determined when the first
unit’s breaker is closed. If the unit starts without a problem, then there is one attempted and one actual start for
the combined-cycle block. If the first unit has a startup failure and a second unit is then started, then the
combined-cycle block will have two attempted starts and one actual start.
RULE #3: A unit is on reserve shutdown when it is removed from service for economic reasons or the electricity
is not needed on the system (standard RS definition).
The reserve shutdown may affect other units (for example a GT out on reserve shutdown will reduce the steam
to the steam turbine). In cases where the steam turbine is still in operation, there would be no event reported
because of the reduction in steam flow because the steam turbine is operating as if in load following and can
return to full capacity as soon as the GT unit is returned to service.
RULE #4: A combined-cycle block is on reserve shutdown if one or more of the gas turbine/jet units is also on
reserve shutdown and the combined-cycle block is not in operation. That means other units of the combined-
cycle block may be on forced, maintenance, or planned outage, but the combined-cycle block still has the
capability to produce electricity with the one or more units on reserve shutdown.
RULE #5: As reported for other unit types, coast down to outages is not reported to GADS. Therefore, the
orderly removing of units towards an outage (standard outage procedure) is considered a coast down and is not
reported as a penalty against the combined-cycle block (See Example #7).
Examples in Synthesizing Block Outages and Deratings from Reported Unit-level Data
In each example, the status of each unit is discussed. Some units are not impacted at all by the outages or
derates. The only reason they are listed is to show they are not impacted and have no impact on available
electricity production. In actual reporting, the unaffected units would not be reported or even mentioned.
Please Note: These examples are created to simply illustrate specific cause-and-effect relationships for discussion
purposes only and may or may not be real world equipment designs, installations, configurations, or actual
outage occurrences. The purpose of these examples is to illustrate how the outage of one unit affects other units
and the entire combined-cycle block.
Our Example Combined-Cycle Block – Big Jumbo, the combined-cycle block, consists of two gas turbines, each
with its own generator. Each GT has its own HRSG. The two GT/HRSG trains are connected through a manifold to
a single steam turbine that also has its own generator. The total electrical combined capacity of this fictitious
combination is 710 MW.
• Units – The units which make up the example combined-cycle block are as follows –
• Combined-cycle block – The combined-cycle block is a 710 MW combined cycle numbered 801
GT #2 placed on RS from January 1 at 0000 until January 7 at 0315. GT #2 was capable of providing 225
MW during this period.
Steam turbine unit placed on RS from January 3 at 0010 to January 6 at 0230. The steam turbine was
capable of providing 260 MW during this period.
GT #1 placed on RS from January 3 at 0015 to January 6 at 0215. GT #1 was capable of providing 225
MW during this period.
Big Jumbo Block placed on RS from January 3 at 0015 to January 6 at 0215. The combined-cycle block
had the capability to provide 710 MW during this period.
Please note that only three events were reported: one for each unit. During the RS outages, the
combined-cycle block was not showing any derates because the block was still capable of generating the
full 710 MW but was not required to do so. There were no equipment restrictions; there were only load
requirements caused the reduced loading.
Diagrams of the units and combined-cycle block during this period are shown in Figure 1:
Figure 1: Example 1
GT #1 on D1 derate from January 7 at 1000 until January 7 at 1400. GT #1 was capable of providing 180
MW during this period. Cause code 3620 – Main Transformer.
GT #2 on D1 derate from January 7 at 1000 to January 7 at 1400. GT #2 was capable of providing 180
MW during this period. Cause code 3620 – Main Transformer.
Steam turbine unit on D1 derate from January 7 at 1000 to January 7 at 1400. The steam turbine was
capable of providing 208 MW during this period. Cause code 3620 – Main Transformer.
Big Jumbo Block was on D1 derate from January 7 at 1000 to January 7 at 1400. Cause code 3620 – Main
Transformer. The combined-cycle block was capable of generating 568 MW.
Diagrams of the units and combined-cycle block during this period are shown in Figure 2:
Figure 2: Example 2
GT #1 on forced derate for 4 hours (or 0.80 Equivalent Forced Derated Hours. )
GT #2 on forced derate for 4 hours (or 0.80 Equivalent Forced Derated Hours.)
Steam turbine on forced derate for 4 hours (or 0.80 Equivalent Forced Derated Hours.)
Combined-cycle block on forced derate for 4 hours (or 0.80 Equivalent Forced Derated Hours.)
GT #1 placed on RS from January 7 at 2115 to January 8 at 0500. GT #1 was capable of providing 225
MW during this period.
No impact on Big Jumbo Block. The combined-cycle block was capable of generating 710 MW during the
full period.
Diagrams of the units and combined-cycle block during this period are shown in Figure 3:
Figure 3: Example 3
GT #2 on Forced Outage (U1) from January 11 at 0700 to January 11 at 14:45 (cause code 5030 –
supercharging fans). No supplemental firing of HRSG. GT #2 was capable of providing no MW during this
period.
As a result, steam turbine on forced derate (D1) from January 11 at 0700 to January 11 at 14:45 (cause
code 5030 – supercharging fans). The steam turbine unit was capable of providing 130 MW during this
period.
GT #2 was placed on RS from January 11 at 1445 to January 14 at 0330. GT #2 was capable of providing
225 MW during this period.
Steam turbine was placed on reserve shutdown from January 12 at 0000 to January 12 at 11:20. The
steam turbine unit was capable of providing 260 MW during this period.
GT #1 was placed on RS from January 12 at 0015 to January 12 at 0930. GT #1 was capable of providing
225 MW during this period.
The combined-cycle block was on derate from January 11 at 0700 to January 11 at 14:45. The combined-
cycle block was capable of generating 355 MW during the full period.
The combined-cycle block was on RS from January 12 at 0015 until January 12 at 0930. The combined-
cycle block was capable of generating 710 MW during the full period.
Diagrams of the units and combined-cycle block during this period are shown in Figure 4:
Figure 4: Example 4
GT #2 on forced outage for 7.75 hours and on Reserve Shutdown for 60.75 hours.
Steam turbine on forced derate for 7.75 hours (or 3.88 Equivalent Forced Derated Hours) and on
Reserve Shutdown for 11.33 hours.
Combined-cycle block on forced derate for 7.75 hours (or 3.88 Equivalent Forced Derated Hours) and on
Reserve Shutdown for 9.25 hours.
GT #1 was placed on RS from January 14 at 2215 to January 16 at 0445. GT #1 was capable of providing
225 MW during this period.
Steam turbine was placed on reserve shutdown from January 15 at 2300 to January 16 at 0600. The
steam turbine unit was capable of providing 260 MW during this period.
GT #2 was placed on RS from January 15 at 2310 to January 16 at 0545. GT #2 was capable of providing
225 MW during this period.
GT #1 on Startup Failure outage (SF) from January 16 at 0445 to January 16 at 0600 (cause code 5030 –
supercharging fans). No supplemental firing of HRSG. GT #1 was capable of providing no MW during this
period.
As a result of the GT#1 SF, steam turbine on forced derate (D1) from January 16 at 0445 to January 16 at
0600 (cause code 5030 – supercharging fans). The steam turbine unit was capable of providing 130 MW
during this period. (Note: the steam turbine unit was on RS but it is treated as if it were in service.)
The combined-cycle block was on RS from January 15 at 2310 until January 16 at 0545 (when GT #2
came on line). The combined-cycle block was capable of generating 710 MW during the full period.
The combined-cycle block was on derate from January 16 at 0445 to January 16 at 0600 caused by the
SF of GT #1 and no potential steam flow to the steam turbine(cause code 5030). The combined-cycle
block was capable of generating 355 MW during the full period.
Diagrams of the units and combined-cycle block during this period are shown in Figure 5:
Figure 5: Example 5
GT #1 on Reserve Shutdown for 30.50 hours and on Forced Outage for 1.25 hours.
Steam turbine on Reserve Shutdown for 7.00 hours and on forced derate for 1.25 hours with a loss of
capacity of 130MW (or 0.625 Equivalent Forced Derated Hours)
Combined-cycle block on forced derate for 1.25 hours with a loss of capacity of 355MW (or 0.63
Equivalent Forced Derated Hours) and on Reserve Shutdown for 6.58 hours.
GT #2 on Forced Outage (U1) from January 22 at 0440 to January 22 at 0450 (cause code 5250 – Other
Controls and instrumentation Problems).
NOTE: Because the FO on GT#2 was so short, there was no loss of steam flow to the steam turbine.
Therefore, the steam turbine unit was capable of providing 260 MW during this period.
GT #2 on Forced Outage (U1) from January 22 at 0455 to January 22 at 0545 (cause code 5250)
As a result of GT #2 not providing steam service, steam turbine on forced derate (D1) from January 22 at
0455 to January 22 at 0545 (cause code 5250). The steam turbine unit was capable of providing 130 MW
during this period.
The combined-cycle block was on derate (D1 – cause code 5250 – Other Controls and instrumentation
Problems) from January 22 at 0440 until January 22 at 0450 (when GT #2 came on line). The combined-
cycle block was capable of generating 485 MW during the full period.
The combined-cycle block was on derate (D1 – cause code 5250 – Other Controls and instrumentation
Problems) from January 22 at 0455 to January 22 at 0545 caused by the U1 of GT #2 and no steam for
steam turbine. The combined-cycle block was capable of generating 355 MW during the full period.
Figure 6: Example 6
Steam turbine on forced derate for 0.83 hours (or 0.42 Equivalent Forced Derated Hours).
Combined-cycle block on forced derate for 1.00 hour (0.17 + 0.83 hours or 0.47 [0.05 + 0.42] Equivalent
Forced Derated Hours).
GT #2 placed on Planned Outage from January 24 at 0000 until January 31 at 1000 (cause code 5260 –
Major Gas Turbine Overhaul). GT #2 was not capable of providing power during this period.
As a result of GT #2 not providing steam service, steam turbine on Planned Derate (PD) from January 24
at 0000 to January 24 at 0515 (cause code 5260). The steam turbine was capable of providing 130 MW
during this period.
Steam turbine unit placed on Planned Overhaul from January 24 at 0515 to January 31 at 1130 (cause
code 4240 – Low-pressure steam turbine bearings). The steam turbine was not capable of providing
power during this period.
GT #1 placed on Planned Outage January 24 at 0530 to January 31 at 1015 (cause code 5272 - Boroscope
inspection). GT #1 was not capable of providing power during this period.
The combined-cycle block was placed on Planned Derate from January 24 at 0000 (when GT #2 came
off-line) to January 24 at 0515 (cause code 5260). The combined-cycle block was capable of generating
355 MW during this period.
The combined-cycle block was placed on Planned Derate from January 24 at 0515 to January 24 at 0530,
when the steam turbine was placed on Planned Outage (cause codes 5260 and 4240). The combined-
cycle block was capable of generating 225 MW during this period.
The combined-cycle block was placed on Planned Outage from January 24 at 0530 (when GT #1 came
off-line) to January 31 at 1000 (when GT #2 came on line) (cause codes 5260, 4240, and 5272). The
combined-cycle block has the capability to provide no power during this period.
The combined-cycle block was placed on Planned Derate from January 31 at 1000 to January 31 at 1015,
when GT #2 came on-line. The combined-cycle block was capable of generating 225 MW during this
period.
The combined-cycle block was placed on Planned Derate from January 31 at 1015 to January 31 at 1130,
when GT #1 came on-line. The combined-cycle block was capable of generating 450 MW during this
period.
Now, as the combined-cycle block was preparing to come off-line for the PO, each unit came off-line in steps
until the final unit (GT #1) started the combined-cycle block PO. As reported for other unit types, coast down to
outages are not reported to GADS. Therefore, the derates from removing GT #2 and the steam turbine are
considered coast downs and not reported as penalties against the combined-cycle block. However, the derates
from removing and beginning outages on GT #2 and the steam turbine prior to the block outage are not
considered coast downs unless they are placed on RS prior to beginning the block outage.
Figure 7: Example 7
There will be other outages, deratings and reserve shutdown periods at a real combined-cycle block. We could
list more but they would just be a repeat of what is shown in the seven examples shown above. So to test the
data collection methodology, we will calculate statistics for each unit and the combined-cycle block using the
data from the seven examples.
The time period with be January 1 at 0000 to January 31 at 2400. This is a total of 744 hours during the month of
January.
This document applies only to reporters who wish to report event and performance data for each generating unit
individually. This document does not apply to reporters wishing to continue reporting combined-cycle data to
GADS as a ‘single unit’ (or traditional method). GADS will still accept the traditional method, but this is not favored
over the reporting of each generating unit within the block.
Please Note: The majority of this document is the same as the synthesis method. The basic data gathering process
on a unit level basis is identical in all respects. The differences will be in creating block statistics from the unit level
data.
IEEE 762 does not address reporting separate units and bringing the components together to create combined-
cycle block statistics. Therefore, we are establishing a NERC methodology based on the generally accepted
industry practice of fleet-type roll up calculations for a group of units – in this case, the group of units consists of
the individual generating units that make up the combined-cycle block.
Terms
To insure proper documentation some terms must be agreed on to eliminate some of the ambiguity concerning
combined-cycle blocks in general.
• Combined-cycle Block (also known in the industry as a “Block”) –By definition, a combined cycle
is a process for generating energy (either electricity or steam) constituted by the marriage of a
Brayton Cycle (expand hot gas to turn a gas turbine) with a Rankine Cycle (use heat to boil water
to make steam to turn a steam turbine). A combined-cycle block employs electric generating
technology in which electricity and process steam are produced from otherwise lost waste heat
exiting from one or more combustion turbines. In most situations, the exiting waste heat is routed
to a conventional boiler or to a heat recovery steam generator (HRSG) for use by a steam turbine
in the production of electricity. Therefore, the combined-cycle block consists of one or more gas
turbines/jet engines, one or more steam turbines, and balance of plant equipment supporting the
production of electricity or steam energy.
Appendix L-2 – Calculating Combined-Cycle and Co-generation Block Data
There may be more than one combined-cycle block at a plant site. Our discussion relates to each individual
combined-cycle block reporting, not the process of reporting several combined-cycle blocks as one plant site.
• Units – Each generator set is considered a “unit.” Typically in combined cycle, each gas turbine or
jet engine and each steam turbine are considered a “unit.” Each unit contributes to the total
electric generation of the combined-cycle block, and each unit has one or more of its own
generators for providing electric power.
• Heat Recovery Steam Generator (HRSG) – There may be one or more HRSG or waste-heat boilers
in a combined-cycle block. Some units may have a single HRSG per GT/jet; others may have several
GT/jet feeding a single HRSG. The HRSG does not contribute electricity to the output of the
combined-cycle block, so is considered a component rather than a unit.
• Other Balance of Plant Equipment – These are the other pieces equipment in the combined-cycle
block used to support the production of electricity. They are not related to any specific part of the
block and are also considered as components.
• Units - The design data is reported as though each unit were a separate generator, this meaning
that each unit would have its own unit number and design data as described in the NERC
guidelines for each unit type. In addition to this, the unit should be marked as being part of a
combined-cycle block by a field that would hold the identifying 800 series unit code of the
combined-cycle block.
• Combined-Cycle block – Balance of plant and other equipment not directly related to each unit
should be coded as described for the combined-cycle block.
Cause Codes
Since each unit of the combined-cycle block can affect the generation of the other units, it is possible to have a
situation where a derate in a gas turbine or jet engine may have a steam turbine cause code. (See Example 2
below). In other words, the cause codes for all units will be open to all task-force-approved cause codes for all
units within the combined-cycle blocks.
Therefore, if you operate a combined-cycle block with two gas turbines and one steam turbine, you will report 36
performance records annually – one set of twelve performance records for each gas turbine unit and one set of
twelve performance records for the steam turbine unit.
Include units of combined-cycle blocks – create a gas turbine peer group that includes gas turbines in
simple cycle operation with those in combined-cycle blocks.
Include units of combined-cycle blocks only – i.e. view gas turbine units in combined-cycle blocks
operation only.
Combined-cycle blocks are available for each of the three groups shown below or groups 1 and 2 or 1 and
3:
1. Not rolled up (neither syntheses nor fleet) but used only reported block data as supplied by the
reporter (traditional data reporting).
2. Creating block data using the synthesis event and performance method shown in this document.
3. Creating block data using the fleet-type roll-up method described in a separate document
“Calculating Combined-cycle block Data Using a Fleet-type Roll up Method When Reporting Each
Gas Turbine/Steam Turbine Unit.”
Not everyone will wish to use some of these options. However, GADS is committed to providing options to all
since the individual needs of GADS data users also vary.
Calculating Fleet-type Combined-Cycle Block Statistics from the Unit Event & Performance
Records
Do not report combined-cycle block event and performance records to NERC. NERC only needs the individual unit
event and performance records.
Illustrated below are examples how to create a block performance record using the fleet-type roll up. Please note
that there is no double counting of penalties on the combined-cycle block; we are actually maintaining the impact
of the problem of one unit on another unit. The addition of the two units affects the overall electric production of
the block.
There will be times when the cause code of one unit (GT#1 for example) will also be shown on a second unit (the
steam turbine for example). That is because the resultant outage of the GT affected the steam production on the
steam turbine, resulting in the steam turbine’s inability to provide full capacity. This may look as if it were “double”
counting (see Example #2); however, the steam turbine itself is not in need of repairs and the cause of the
reduction in steam-turbine production to the steam turbine points to a GT (doesn’t say which GT, just “a” GT).
Therefore, the GT gets two penalties against it: one for the outage (to the GT#1 itself) and another for the derate
(to the steam turbine.) which may appear as a “double counting,” but is not. This is because the GT actually caused
the entire shortage.
1) When GT#1 is on outage, the outage time and cause is related to GT#1 via the event record (only the
outage is related to GT#1), and
2) The derate to the steam turbine is NOT related to GT#1 “directly” because the derate is shown to be
caused by a GT cause code but not identifying which GT (assuming there is more than one GT unit).
Therefore, when the computer calculates the statistics of GT#1, it only sees the outage, not the
derate. When the computer calculates the statistics on the steam turbine, it sees the derate caused
by a GT. Therefore, GT#1 is not penalized twice, but only the one time.
These values are calculated based on only the performance and event records directly attributed to each of the
individual units. However, when you report on cause code based values, the entire effect of the outage will be
taken into account. With the effect of the outage being attributed to the cause code and not the unit, the unit is
not unduly violation.
You do need to keep in mind that, when using the equivalent fleet roll-up method, you are working with energy
in MWh and not capacity and hours as separate entities. In all calculations, we can substitute the energy based
number for a particular statistic by multiplying the hours by the unit’s maximum capacity (Net Maximum Capacity).
So, for instance, service hours become service MWh-
This works for a single unit, but, if period hours are used for the block, the following relationship doesn’t work –
The relationship of service hours to period and outage hours needs to remain constant for the individual unit and
for the block when all units are added together. By multiplying each element by the capacity of the related unit,
we keep the relationship stable.
SMWh = SH x Capacity
PMWh = PH x Capacity
OHWh = OH x Capacity
Now you can sum the MWh for all units to create the values for the block
Special Rules Used in Calculating Combined-Cycle Block and Units Using Fleet-type Roll up
Method
There is a need to establish some rules for fleet-type combined-cycle blocks. The rules will insure uniformity in
creating fleet-type statistics from the unit level data.
1. The number of attempted and actual starts for the combined-cycle block is determined by the sum
of all attempted and actual starts of the units. Due to this, all unit events transfer directly to the
block without interpretation to the cumulative status of the block. In other words, if a unit is on
forced outage, the forced outage event is also posted to the block even though the other units in
the block may be producing power. In this way, a total count of all events that occur within the block
can be maintained.
2. A unit is on reserve shutdown when it is removed from service for economic reasons or the
electricity is not needed on the system (standard RS definition.) The reserve shutdown may affect
other units (for example a GT out on reserve shutdown will reduce the steam to the steam turbine).
In such cases where the steam turbine is still in operation, there would be no event reported
because of the reduction in steam flow because the steam turbine is operating as if in load-following
and can return to full capacity as soon as the GT unit is returned to service.
3. As reported for other unit types, coast down to outages is not reported to GADS. Therefore, the
orderly removing of units towards an outage (standard outage procedure) is considered a coast
down and is not reported as a penalty against the combined-cycle block. (See Example #7).
Examples in Fleet-Type Block Outages and Deratings from Reported Unit level Data
In each example, the status of each unit is discussed. Some units are not impacted at all by the outages or derates.
The only reason they are listed is to show they are not impacted and have no impact on available electricity
production. In actual reporting, the unaffected units would not be reported or even mentioned.
Please Note: These examples are created simply to illustrate specific cause-and-effect relationships for discussion
purposes only, and may or may not be real world equipment designs, installations, configurations or actual outage
occurrences. The purpose of these examples is to illustrate how the outage of one unit affects other units and the
entire combined-cycle block.
Our example Combined-Cycle block – Big Jumbo, the combined-cycle block, consists of two gas turbines, each
with its own generator. Each GT has its own HRSG. The two GT/HRSG trains are connected through a manifold to
a single steam turbine that also has its own generator. The total electrical combined capacity of this fictitious
combination is 710 MW.
Units – The units which make up the example combined-cycle block are as follows –
Combined-cycle block – The combined-cycle block is a 710 MW combined cycle numbered 801
GT #2 placed on RS from January 1 at 0000 until January 7 at 0315. GT #2 was capable of providing 225
MW during this period.
Steam turbine unit placed on RS from January 3 at 0010 to January 6 at 0230. The steam turbine was
capable of providing 260 MW during this period.
GT #1 placed on RS from January 3 at 0015 to January 6 at 0215. GT #1 was capable of providing 225 MW
during this period.
1. RS of 16,650 MWh
2. RS of 33,131 MWh
3. RS of 19,325.80 MWh
Please note that only three events were reported: one for each unit. The block impact is the sum of each RS event
by each of the three units. The equivalent block hours (65,390 MWh / 710MWh) are 96.80 hours.
GT #1 on D1 derate from January 7 at 1000 until January 7 at 1400. GT #1 was capable of providing 180
MW during this period. Cause code 3620 – Main Transformer.
GT #2 on D1 derate from January 7 at 1000 to January 7 at 1400. GT #2 was capable of providing 180 MW
during this period. Cause code 3620 – Main Transformer.
Steam turbine unit on D1 derate from January 7 at 1000 to January 7 at 1400. The steam turbine was
capable of providing 208 MW during this period. Cause code 3620 – Main Transformer.
GT #1 placed on RS from January 7 at 2115 to January 8 at 0500. GT #1 was capable of providing 225 MW during
this period.
GT #2 on Forced Outage (U1) from January 11 at 0700 to January 11 at 14:45 (cause code 5030 –
supercharging fans). No supplemental firing of HRSG. GT #2 was capable of providing no MW
during this period.
As a result, steam turbine on forced derate (D1) from January 11 at 0700 to January 11 at 14:45
(cause code 5030 – supercharging fans). The steam turbine unit was capable of providing 130 MW
during this period.
Steam turbine was placed on reserve shutdown from January 12 at 0000 to January 12 at 11:20.
The steam turbine unit was capable of providing 260 MW during this period.
1. RS of 2081.25 MWh
2. FO of 1743.75 MWh
3. RS of 13668.75 MWh
4. FO of 1007.50 MWh
5. RS of 2945.80 MWh
GT #1 was placed on RS from January 14 at 2215 to January 16 at 0445. GT #1 was capable of providing
225 MW during this period.
Steam turbine was placed on reserve shutdown from January 15 at 2300 to January16 at 0600. The steam
turbine unit was capable of providing 260 MW during this period.
GT #2 was placed on RS from January 15 at 2310 to January 16 at 0545. GT #2 was capable of providing
225 MW during this period.
GT #1 on Startup Failure outage (SF) from January 16 at 0445 to January 6 at 0600 (cause code 5030 –
supercharging fans). No supplemental firing of HRSG. GT #1 was capable of providing no MW during this
period.
As a result of the GT#1 SF, steam turbine on forced derate (D1) from January 16 at 0445 to January 16 at
0600 (cause code 5030 – supercharging fans). The steam turbine unit was capable of providing 130 MW
during this period. (Note: the steam turbine unit was on RS but it is treated as if it were in service.)
1. RS of 6,862.50 MWh
2. FO of 281.25 MWh
3. RS of 1481.25 MWh
4. RS of 1820.00 MWh
5. D1 of 162.50 MWh
GT #2 on Forced Outage (U1) from January 22 at 0440 to January 22 at 0450 (cause code 5250 – Other
Controls and instrumentation Problems).
Note: Because the FO on GT#2 was so short, there was no loss of steam flow to the steam turbine. Therefore, the
steam turbine unit was capable of providing 260 MW during this period.
GT #2 on Forced Outage (U1) from January 22 at 0455 to January 22 at 0545 (cause code 5250 – Other
Controls and instrumentation Problems).
As a result of GT #2 not providing steam service, steam turbine on forced derate (D1) from January 22 at
0455 to January 22 at 0545 (cause code 5250 – Other Controls and Instrumentation Problems). The steam
turbine unit was capable of providing 130 MW during this period.
GT #2 reports 2 forced outages for 0.17 hr x 225MW = 38.25 MWh. and 0.83 hr x 225 MW = 186.75
MWh.
Steam turbine on forced derate for 0.83 hours (or 0.42 Equivalent Forced Derated Hours) or 0.83 hr x
130 MW = 107.90 MWh.
Combined-cycle block reports the 3 events:
1. FO of 38.25MWh
2. FO of 186.75 MWh
3. D1 of 107.90 MWh
GT #2 placed on Planned Outage from January 24 at 0000 until January 31 at 1000 (cause code 5260 –
Major Gas Turbine Overhaul). GT #2 was not capable of providing power during this period.
Steam turbine unit placed on Planned Overhaul from January 24 at 0515 to January 31 at 1130 (cause
code 4240 – low-pressure steam-turbine bearings). The steam turbine was not capable of providing power
during this period.
GT #1 placed on Planned Outage January 24 at 0530 to January 31 at 1015 (cause code 5272 - Boroscope
inspection). GT #1 was not capable of providing power during this period.
1. PO of 38,868.75 MWh
2. PO of 40,050 MWh
3. PO of 45,305 MWh
The time period will be January 1 at 0000 to January 31 at 2400. This is a total of 744 hours during the month of
January.
Net Actual Generation would be taken from the meters. Values stated here are for demonstration purposes only.
There are a number of differences between the NERC-GADS and the GADS run by Independent System
Operators (ISOs), known as ISO-GADS Some of these differences are minor; others are not.
NERC-GADS collects equipment outage data on a national basis. NERC-GADS is an equipment outage system
with a focus on plant reliability and assessments. The ISOs are charged with the reliability of the bulk electrical
grid and for the dispatching of the generating units in an economical manner, so the various ISO-GADS
databases have taken on some marketing functions or overtones. As a result, there are differences between the
NERC-GADS and the various ISO-GADS reporting instructions. This means there is a need to maintain two sets of
GADS records to meet the mandatory reporting requirements of NERC and curtain ISO groups.
Listed below is a brief description on how each ISO utilizes GADS data to support their marketing function, and
specifically how their GADS procedures differ from those established by NERC-GADS.
PJM Interconnection (PJM) – Uses GADS data for ISO reliability studies and determining capacity payments to
the Generator Owners. Significant features of the PJM-GADS are:
• PJM uses the GADS data to determine capacity payments. These payments are based on the following
equation:
Capacity Payment = ICAP x Market Capacity Payment Price x (1 - EFORd of unit)
• Use of Outside Management Control (OMC) event cause codes must be approved by PJM.
• GADS data is reported and calculated against the unit’s ICAP value, which is usually its NET DEPENDABLE
CAPACITY (NDC) not its NET MAXIMUM CAPACITY.
• Maintenance Outages and Derates (Event Type MO & D4) are limited to 9 days duration during the
summer months.
• Data must be submitted monthly to PJM on or before the 20th of the following month.
• Errors in a previously submitted month require access approval from PJM to change any data.
• Generator Owners must submit the results to Real Power Testing twice a year. Winter and summer
reporting periods are defined.
New York Independent System Operations (NYISO) – Uses GADS data for calculation of derating factors for the
Installed Capacity (ICAP) Market, NYISO, the New York State Reliability Council’s (NYSRC) Reliability Studies, and
the determination of the Installed Reserve Margin (IRM) for the New York Control Area (NYCA). Differences
between NERC-GADS and NYISO generating unit reporting instructions include:
Appendix M – Differences Between NERC-GADS and ISO-GADS Data Collection and Uses
Previous text:
MB is defined by IEEE 762 and GADS as “the state in which a unit is unavailable for service but can be
brought back into service after some repairs with appropriate amount of notification, typically weeks or
months.” GADS added “after some repairs” and defines the phrase “after some repairs” to mean that
some action may be needed to prepare the unit for service because it had been sitting idle for a period
of time and some equipment parts have deteriorated or need replacing before the unit can be operated.
The unit may have also experienced a series of mechanical problems for which management may wish
to wait for a period of time to determine if the unit should be repaired or retired. A unit that is not
operable or is not capable of operation at a moment’s notice must be on a forced, maintenance or
planned outage and remain on that outage for at least 60 days before it is moved to the MB state. If
repairs are being made on the unit in order to restore it to operating status before the 60-day period
expires, then the outage must remain a forced, maintenance or planned outage and not MB. If unit
repairs for restoring the unit to operation are made after the 60-day period, then the first 60 days must
be a forced, maintenance or planned outage and the time after the 60-days including the repair time on
the unit up to operation shall be the MB event. Use Cause Code “9991” for these events.
Updated text:
MB is defined by IEEE 762 and GADS as “the state in which a unit is unavailable for service but can be
brought back into service after some repairs with appropriate amount of notification, typically weeks or
months.” GADS added “after some repairs” and defines the phrase “after some repairs” to mean that
some action may be needed because the unit had been idle for a period of time and some equipment,
systems or parts may have deteriorated and should be replaced or repaired prior to the units return to
service. The unit may have also experienced a series of mechanical problems, prior to the MB event, for
which management may wish to wait for a period of time to determine if the unit should be returned to
service or retired. Granted IEEE 762 states that the unit must be capable of operation prior to being
placed in the deactivated state; however, in actual practice management may want to delay a decision
to fix the generator and ‘suspend’ it in a deactivated state until a decision to repair or retire is rendered.
If this option is chosen the unit must enter the MB event no earlier than 60 days after the preceding
outage event (In other words the unit must incur a forced outage of a minimum 60 days prior to the
start of an MB event if the unit is inoperable). If the choice is to retire the generator after a decision is
made, then the generator can be immediately retired coincident with the end of the MB event; If the
decision is to repair, all repairs to make the unit operable must be completed under an outage of same
type that preceded the MB event (in other words, if the generator entered the MB event on the heels of
a forced outage, it must return to a forced outage for repairs to make the generator operable). If repairs
Page N-1
are being made on the unit in order to restore it to operating status once the MB event has started, the
MB event must end prior to the commencement of those repairs and the appropriate outage type
started until those repairs have been completed and the outage ended. Also, if there are long lead-time
item(s) that are ordered (such as a GSU, a generator rotor or the like) the MB event should end when
the initial order has been placed, since a decision at that time has been rendered to repair the
generating unit. Again, once a decision is rendered to repair the unit, whether or not orders are placed
and/or work is started, the mothball event must end and the appropriate outage type started. Repair
work cannot be conducted on a unit in the mothball state. Use Cause Code “9991” for MB events.
Page III-6
From:
1. Outages
An outage exists whenever a unit is not synchronized to the grid system and not in a reserve shutdown
state. The general outage event classification is divided into seven distinct event types. Special
instructions for reporting testing during and following outages can be found on Page III-13.
To:
1. Outages
An outage exists whenever a unit is not synchronized to the grid system and not in a reserve shutdown
state. The general outage event classification is divided into seven distinct event types. Special
instructions for reporting testing during and following outages can be found on Page III-11.
Page III-13
From:
Do not report deratings caused by ambient-related conditions or system dispatch requirements (see
notes on reporting deratings, Page III-18).
To:
Do not report deratings caused by ambient-related conditions or system dispatch requirements (see
notes on reporting deratings, Page III-14).
Page III-14
From:
Page N-2
Although load following is not reported to GADS, any maintenance, testing, etc. done during the load
following period should be reported as an event. Under certain conditions, this work can be reported as
a non-curtailing event (NC). See Page III-19 for details.
To:
Although load following is not reported to GADS, any maintenance, testing, etc. done during the load
following period should be reported as an event. Under certain conditions, this work can be reported as
a non-curtailing event (NC). See Page III-18 for details.
Page III-21
From:
See Notes on Reporting Deratings, Pages III-13 to III-17, for more information concerning the reporting
of deratings.
To:
See Notes on Reporting Deratings, Pages III-14 to III-17, for more information concerning the reporting
of deratings.
Section IV – Performance
Page IV-6:
Enter the code from the list below that best describes how the unit was operated or loaded during the
month being reported.
Page IV-9
From:
Page N-3
Enter the sum of all hours the unit was off-line due to planned outages (PO) as detailed on the event
reports completed for this unit. The technique used to compute hours from the event reports is
described on page IV-12.
To:
Enter the sum of all hours the unit was off-line due to planned outages (PO) as detailed on the event
reports completed for this unit. The technique used to compute hours from the event reports is
described below.
From:
Enter the sum of all hours the unit was off-line due to maintenance outages (mo) as detailed on the
event reports completed for this unit. The technique used to compute hours from the event reports is
described on Page IV-12.
To:
Enter the sum of all hours the unit was off-line due to maintenance outages (mo) as detailed on the
event reports completed for this unit. The technique used to compute hours from the event reports is
described below.
From:
Enter the sum of all hours the unit was off-line due to extensions of scheduled (maintenance and
planned) outages (ME and PE) as detailed on the event reports completed for this unit. The technique
used to compute hours from the event reports is described on Page IV-9.
To:
Enter the sum of all hours the unit was off-line due to extensions of scheduled (maintenance and
planned) outages (ME and PE) as detailed on the event reports completed for this unit. The technique
used to compute hours from the event reports is described below.
Page N-4
Enter the code from the list below that best describes how the unit was operated or loaded during the
month being reported. Generally, these are numbered from least starts to most starts.
Complete the following Change in Unit Status Report Form whenever you purchase, deactivate or
reactivate a unit from service. If a unit is deactivated (retired), continue to report that unit for the
remainder of the calendar year using the instructions shown on Page III-6 of the GADS Data Reporting
Instructions. If a unit is purchased, continue to report that unit for the remainder of the calendar month
using the instructions shown on Page III-18 of the GADS Data Reporting Instructions. Submit the
completed Change in Unit Status Report Form to gads@nerc.net.
To:
Complete the following Change in Unit Status Report Form whenever you purchase, deactivate or
reactivate a unit from service.
If a unit is deactivated (retired), continue to report that unit for the remainder of the calendar year
using the instructions shown on Section III of the GADS Data Reporting Instructions. Please fill out the
unit information in the Unit Purchase/Retirement section, and also the Unit Deactivation information.
If a unit is purchased, continue to report that unit for the remainder of the calendar month using the
instructions shown on Section III of the GADS Data Reporting Instructions. Submit the completed
Change in Unit Status Report Form to gads@nerc.net. Please fill out both sections of the Unit
Purchase/Retirement section, including original company and new company information. If you do not
know who the new company is, please contact NERC or your Regional Coordinator.
If a unit changes owners at a company level, but keeps the same utility and unit information, keep
reporting under the same utility and unit codes. Please fill out the NCR number information for Original
Company NCR Number and New Company NCR Number.
If a unit was previously retired but has come back into service, fill out the reactivation part on page A-3.
Page N-5
Plus added NCR number and extra spots for unit IDs.
PH
To
Page N-6
UOF = MOH +FOH + x 100
PH
Updated demand factor f in equation 23, 25, 55, 57, 87, and 89 to align division symbols.
From
Page N-7
To:
From:
To:
Page N-8
Appendix B4 – Diesel Cause Codes
Added:
Continued Emissions Monitoring Systems (CEMS)
8700 CEMS Certification and Recertification
8710 SO2 analyzer problems
Page N-9