Академический Документы
Профессиональный Документы
Культура Документы
Table of Contents
Section I: Introduction
Industry Development of GADS .................................................................................................. I-2
Unit Boundaries and Problems Outside Plant Control ................................................................. I-2
Arrangement of Data Reporting Instructions ................................................................................ I-3
A. Event Identification
Record Code ....................................................................................................................... III-3
Utility (Company) Code ..................................................................................................... III-3
Unit Code ........................................................................................................................... III-3
Year .................................................................................................................................... III-3
Event Number..................................................................................................................... III-3
Report Revision Code ........................................................................................................ III-4
Event Type ......................................................................................................................... III-5
1. Outages................................................................................................................ III-7
PO - Planned Outage
MO - Maintenance Outage
PE - Planned Outage Extension
ME - Maintenance Outage Extension
SF - Startup Failure
U1 - Unplanned (Forced) Outage Immediate
U2 - Unplanned (Forced) Outage Delayed
U3 - Unplanned (Forced) Outage Postponed
PD - Planned Derating
D4 - Maintenance Derating
DP - Planned Derating Extension
DM - Maintenance Derating Extension
D1 - Unplanned (Forced) Derating Immediate
D2 - Unplanned (Forced) Derating Delayed
D3 - Unplanned (Forced) Derating Postponed
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-3
Index of Examples
Figures
SECTION I
I-I Applications of GADS Data ......................................................................................... I-1
I-2 Regional Entities........................................................................................................... I-3
SECTION II
II-1 Reporting Requirements vs. Unit Type/Size ...............................................................II-2
II-2 Data Reporting Formats...............................................................................................II-3
SECTION III
III-1 Event Reporting Requirements vs. Unit Type/Size ................................................... III-1
III-2 Record Layout of Section A Event Identification .................................................. III-3
III-3 Unit States Diagram................................................................................................... III-5
III-4 Possible Derating Situations .................................................................................... III-19
III-5 Record Layout of Section B Event Magnitude ..................................................... III-23
III-6 Allowable Event Type Changes .............................................................................. III-24
III-7 Example of Dominant Derating Code Reporting .................................................... III-27
III-8 Record Layout of Section C Primary Cause of Event .......................................... III-29
III-9 Record Layout of Section D Additional Work During Event .............................. III-30
III-10 Allowable Cause Codes ........................................................................................... III-31
III-11 Record Layout of Event Records Using Failure Codes ........................................... III-37
SECTION IV
IV-1 Record Layout of Section A Unit Identification .................................................... IV-2
IV-2 Record Layout of Section B Unit Generation Performance ................................... IV-4
IV-3 Effects of Ambient Temperature on Gas Turbines/Jet Engines ................................ IV-6
IV-4 Record Layout of Section C Unit Starting Characteristics ..................................... IV-7
IV-5 Record Layout of Section D Unit Time Information ............................................. IV-9
IV-6 Record Layout of Section E Primary Fuel; and F Secondary Fuel ................... IV-12
SECTION V
V-1 Location of Design Data Forms.................................................................................. V-1
Section I - Introduction
These Data Reporting Instructions were developed to assist utility personnel in reporting
information to the North American Electric Reliability Corporations (NERC) 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 Figure I-1.)
GADS maintains complete operating histories on more than 5,800 generating units representing
71% of the installed generating capacity of the United States and Canada. GADS is a voluntary
industry program, open to all participants in the Regional Entities (shown in Figure I-2) and any
other organization (domestic or international) that operate electric generating facilities.
Figure I-1
Applications of GADS Data
GADS was developed by utility designers, operating engineers, and system planners to meet the
information needs of the electric utility industry. For this purpose, specific objectives for the
GADS program were established: 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, often unique, data systems
typically found at power plants, or for maintenance data programs that record detailed equipment
failures and repair techniques. Through the collective effort of participating GADS members
the cooperation in reporting to GADS and sharing information with the industry the
objectives of the GADS program can be met.
Before any data element was included in GADS, an industry committee to determine its
applicability to utility operation and RAM analyses scrutinized it. A series of industry meetings
were held to discuss the analytical usefulness of each element and to determine if utilities could
reasonably provide that data to GADS. Consequently, the only data requested in these Reporting
Instructions meet industry-prescribed needs. In reviewing this document, you will find that most,
if not all, of the requested data elements are already being collected in your utilitys plant-
specific data system.
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
done intentionally: the EEI information can be derived from GADS so analyses that include data
from earlier than 1982 can be completed.
A number of generating companies have been deregulated over the last several years. As a result,
part of the GADS database contains deregulated units and part regulated units. As more and
more electric utilities divide into generating companies (GENCO), transmission companies
(TRANSCO) and distribution companies (DISCO), GADS must also make changes to
accommodate the needs. To do so, we must determine where the GENCO responsibilities end
and the TRANSCO take over.
Based on research by the IEEE 762 committee, the boundary between the GENCO and
TRANSCO 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 with the plant management responsibilities. As a result, new
equations are introduced for measuring plant performance. See Appendix F of this manual.
Figure I-2
Regional Entities
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
RFC WECC
ReliabilityFirst Corporation Western Electricity Coordinating Council
These GADS Data Reporting Instructions detail the procedures, format, and frequency to follow
when reporting data to GADS.
This document is divided into several different sections. Each section treats a particular area of data to be
reported to GADS. Section II describes the three general types of data to be reported to GADS, event,
performance, and design as well as the frequency and transmittal specifications. 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.
To further assist you, the GADS staff holds a reporting workshop annually. During this workshop, all the
GADS data reporting requirements and procedures are thoroughly reviewed. To learn more about the
reporting workshop, contact a NERC GADS staff member or look for information on the NERC web site:
http://www.nerc.com/page.php?cid=4|43|52.
Remember, the GADS staff is always available to answer any questions you may have.
Utah office:
Princeton office:
Event and performance data are described in detail in Sections III and IV of these Data Reporting
Instructions. Design data, detailed in Section V, must be submitted before reporting any event or
performance data to NERC.
For the purposes of data reporting, the term unit is defined as follows:
Nuclear and fossil (steam) units those units consisting of a single reactor or boiler and a
single turbine-generator. In cases where multiple boilers and/or multiple turbine-generators are
headered together, the entire ensemble 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-6.
Hydro, pumped storage, gas turbine, jet engine, and diesel units those 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 ensemble may be considered as a single unit or reported as individual units. Your specific
reporting criteria should be noted 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) with a Brayton Cycle (expand hot
gas to turn a gas turbine). The combined cycle consisting of one or more gas turbines/jet engines
and one or more heat recovery boilers. The steam from the heat recovery boiler is sent to a
steam turbine for generating electricity. Each gas turbine/jet engine and each steam turbine is a
unit. The entire ensemble is considered 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-24.
Co-generation units those 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-24.
Fluidized bed combustion units those units consist of one or more bubbling, circulating or
pressurized bed boilers or steam turbines. Consider the entire group as a single 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; or,
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 (megavoltamperes) by the rated power
factor found on the nameplate affixed to the generator (nameplates in the case of
multiple generator units).
Reporting event and performance data prior to either of the above dates is required for those
organizations who wish to report data to GADS. GADS is still a voluntary database and it is
not required by the industry or by law to report unit data to GADS. However, it is required
to report to GADS if your organization owns generating facilities and wants information from
GADS (special reports, pc-GAR, etc. See Appendix I GADS Data Release Guidelines for
details).
Figure II-1 indicates the type of data each utility should report for its conventional, non-
renewable generating units depending on the type and size of those units. For renewable
generating plants (wind), please see the GADS Wind Turbine Generation Data Reporting
Instructions.
Figure II-1
Reporting Requirements vs. Unit Type/Size
We encourage all generating organizations to report all data elements currently collected for their
units and any additional information they can reasonably provide.
Submit event and performance data to GADS within 30 days after the end of every calendar
quarter throughout the life of each unit. 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 these
reporting instructions. If a unit is deactivated, please complete the Change in Unit Status form
found in Appendix A. The completed Change in Unit Status form should be submitted to
Joanne Rura at joanne.rura@nerc.net.
Data should be submitted electronically as shown in Figure II-2. When submitting data, please
indicate the number of records being submitted in your transmittal letter to assure all data is
properly retrieved.
Figure II-2
Data Reporting Formats
Media Specifications
Text format (.txt). To improve transmission times
your data files may be submitted as compressed
(.zip) files.
E-mail:
Submit your data within 30-days after the end of
every calendar quarter.
E-mail your data to: joanne.rura@nerc.net
All questions regarding data transmittals and reporting procedures should be directed to:
801-756-0972 609-524-0613
801-756-0973 Fax 609-452-9550 Fax
An event occurs any time a generating units operating status or capability changes. Four
general classifications of events are reported to GADS: outages, deratings, reserve shutdowns,
and noncurtailing 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.
Participation in the GADS program is voluntary, but once committed, each utility should report
as much detailed information as it can. 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, suggests the classes of events utilities should report for different
types and sizes of conventional, non-renewable generating units. For renewable generating
plants (wind), please see the GADS Wind Turbine Generation Data Reporting Instructions.
Figure III-1
Event Reporting Requirements vs. Unit Type/Size
Detailed event data reporting for larger units is suggested and is indicated by the term required.
The term optional implies that each utility must determine if it can reasonably provide the
detailed data. We encourage all electric generating organizations to report all event data
information currently collected for their units and any additional information they can reasonably
provide.
All units except hydro and pumped storage units without automatic data recording equipment, no
matter its size or technology, are required to report reserve shutdown events. GADS encourages
that all events (forced, maintenance, and planned) for all units be reported for providing
complete reporting. GADS interprets this as 1 MW or larger with other sizes optional.
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.
The Event Report (07) format is based on a series of 82-character images called records. The
different sections of the Event Report are on different records: Sections A and B on Record 01,
Section C on Records 02 and 03, and Section D on Records 04 and 05 through 98 and 99. Unless
otherwise stated, it is not necessary to zero-fill or asterisk-fill unused data fields of any section of
the Event Report (07 format).
Note: As of January 1, 2010, GADS will only accept the new (07) format. There was a need by
several Independent System Operators (ISO) groups to collect derating data on units smaller
than 1 MW in size. Therefore, the GADS database expanded the Gross Available Capacity
(GAC) and Net Available Capacity (NAC) to include two decimal places.
We are not asking for generating units of 0.01 MW size to report to GADS. Historically
speaking, the smallest units reported to GADS are 1 MW. With the introduction of the 07 format,
GADS can accept deratings smaller than 1 MW for units less than 1 MW in size.
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.
Figure III-2
Record Layout of Section A Event Identification
All Records
Column ID Number of Columns Starting Position
A Event Identification
Record Code 2 1
Utility (Company) Code 3 3
Unit Code 3 6
Year 4 9
Event Number 4 13
Report Revision Code 1 17
Event Type 2 18
An event occurred on December 2, 1999 and was reported to GADS on January 31, 2000.
Complete columns 9-12 as 1999. (Refer to Page III-25 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, after gathering
all the events to submit for a quarter, you find you have omitted one, 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. An event that continues from one year into the next is assigned a new
event number in the new year. Refer to Page III-25 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).
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,
Figure III-3
Unit States Diagram
Inactive States
The two most general unit states are shown at the top of the diagram: 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 moments 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 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 moments 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 the unit 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.
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
Tracing down the diagram, more detail is added to more precisely describe 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 utilities 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-13.
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 one outage ends
will be the same as when the next 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, lasts 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.
MO Maintenance Outage
An outage that can be deferred beyond the end of the next weekend (Sunday at 2400
hours), 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.
Note: If an outage occurs before Friday at 2400 hours, the above definition applies. But
if the outage occurs after Friday at 2400 hours and before Sunday at 2400 hours, the MO
will only apply if the outage can be delayed passed the next, not current, weekend. If the
outage can not be deferred, the outage shall be a forced event.
GADS Data Reporting Instructions January 2011 Page III-7
Section III Event Reporting
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 not 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 not counted as PO or MO work until the U1 repairs are complete.
All work during PO and MO events are 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 dispatch orientated
but equipment-orientated database. 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 those instances where unexpected problems or conditions 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, then any problems causing outages or deratings up until that
date are not usually considered to be part of the PO or MO.
Page III-8 GADS Data Reporting Instructions January 2011
Section III Event Reporting
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.
Please Note: SE events are still accepted by GADS. Therefore, if a reporting companys internal
programs can not or will not be modified to follow the new event types, then GADS will continue
to accept the SE event types. However, the SE event types will be converted internally by GADS
into the new event types for use in unplanned outage calculations and will be stored as a new
event type. Historical data will be converted into the new event types for use in pc-GAR and
other research work.
SF Startup Failure
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 utility. 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 the 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. We ask that during the 2010 reporting period, data reporters volunteer to
report amplification codes to mark these events as shown below. In order to maintain the
historical meanings of the existing component trip codes 82 and 83, we will create 2 new
amplification codes T1 and T2 to be used for complete, 100% unit trips:
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 before the end of the year to be
acceptable by GADS.
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. There should
be an amplification code reported for each U1 event.
Starting January 1, 2011, the need to report T1, T2 or other amplification codes will be
mandatory to pass GADS edits. For a complete list of the amplification codes see
Appendix J of these data reporting instructions.
The IEEE 762 defines the outage types and when the appropriate outage should be reported.
However, the experiences of the industry also dictate interpretations of which outage type is
most appropriate for a situation. The following are interpretations of when certain full outages
should be reported and the reason for the apparent difference to the IEEE 762 rules. In these
examples, we will illustrate the points using fictitious generating units but real life situations.
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 for 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.
On Friday, Jumbo #1, a gas turbine, began to vibrate. At first the vibrations were not severe but
over the following 4 hours, the mils of vibration increased to where the unit must be removed
from serviced. 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 vibration problems. Therefore, the outage is a Forced Outage and the FO is
enforced until the vibration problem is solved.
Although the unit was not needed, by management decision, the unit was not available for the
full 36 hours and so the forced outage is reported from the time the unit came off line until the
unit was available for operation (36 hours later). No part of the 36 hours is RS time. The RS time
starts after the repairs and unit is available for operation.
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 reason for the Planned Outage
Extension.
All hours of the outage except the last 12 hours are MO. 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.
Since the unit was not delayed from scheduled startup due to the fan repairs, there is not penalty
to the unit because of the surprise repairs. The ID Fan repair was reported 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. 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.
In reporting pumped storage units to GADS, GADS is interested in the generating aspect of
pumped storage units more than the non-generating mode. Therefore, if the unit is prevented for
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)
dont report the problem to GADS. GADS 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. All outages that limit or prevent
generating power must be reported to GADS.
2. Deratings
A derating exists whenever a unit is limited to some power level less than the units 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 units Net Maximum Capacity (NMC) and less than 30
minutes in duration, then the derating can be reported at your discretion (optional). Otherwise, all
other deratings (greater/less than 2% NMC or shorter/longer than 30 minutes) shall be reported
to GADS. For example, a derate that is 10% of the NMC but last 10 minutes should be reported
to GADS; a derate that is 1% of the NMC but last 6 hours should be reported to GADS.
PD Planned Derating
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
PDs. Report deratings of these types as Maintenance Deratings (D4).
D4 Maintenance Derating
A derating that can be deferred beyond the end of the next weekend 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 an derating occurs before Friday at 2400 hours, the above definition applies.
But if the derating occurs after Friday at 2400 hours and before Sunday at 2400 hours,
the D4 will only apply if the derating can be delayed passed the next, not current,
weekend. If the derating can not be deferred, the derating shall be a forced derating
event.
Use a DP only in instances where the original scope of work requires more time to
complete than originally scheduled. Do not use a DP 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 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 original 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.
Please Note: DE events are still accepted by GADS. Therefore, if a reporting companys
internal programs can not or will not be modified to follow the new event types, then
GADS will continue to accept the DE event types. However, the DE event types will be
converted internally by GADS into the new event types for use in unplanned outage
calculations and will be stored as a new event type. Historical data will be converted into
the new event types for use in pc-GAR and other research work.
Just like the modifications to U1 on Page III-9, GADS will collect automatic component
trips. It will be collected using D1 with the existing amplifications codes 82 and 83. The
description of amplification codes 82 and 83 focus on derating, not outages. The same
general description is used to separate automatic component trips from manual, operator
initiated component trips.
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 before the end of the year to be
acceptable by GADS.
If the D1 is not a trip but the result of a change of state (from planned derate to D1, for
example), then the amplification code can be any other amplification code. There should
be an amplification code reported for each D1 event.
Starting January 1, 2011, the need to report 82, 83 or other amplification codes will be
mandatory to pass GADS edits. For a complete list of the amplification codes see
Appendix J of these data reporting instructions.
Ambient-related Losses
Do not report ambient-related losses, such as those caused by high cooling water intake
temperatures (other than regulatory-imposed discharge limits cause code 9660, etc.), as
derating events to GADS. There are two reasons for this. First, the level of record keeping
required to track these types of losses as events is excessive. Second, ambient-related losses are
easily computed using the information you supply to GADS on the Performance Report,
specifically Maximum Capacity and Dependable Capacity. The difference in these two values
reflects losses due to ambient conditions only (see Page IV-4). To determine ambient losses in
megawatthours (MWh), simply multiply the difference between Maximum Capacity and
Dependable Capacity by the total number of hours in the study period.
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 noncurtailing event (NC). See Page III-22 for details.
Figure III-4 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 shutdown safely, with damaging equipment or posing a safety hazard to personnel. Some
shutdowns are quick as in 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.
Figure III-4
Possible Derating Situations
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 noncurtailing in nature; that is, 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, the
available capacity resulting from the derating (see below) must be estimated, 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.
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 a new derating to GADS each time the available capacity of the unit changes.
2. Determine the units average available capacity during the entire restricted period and
reporting 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 units available capacity involves first calculating
the megawatthours (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-23).
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 megawatthours (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 units 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. As a data reporter, you must realize 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, in the example, the average megawatts lost over
the 10-day period 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
An event that exists whenever 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, not 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 anytime, the work can be stopped or completed without preventing the unit from:
This criterion remains the same whether or not the unit was needed by the system.
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
is altered 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 too. Estimate the available capacity as a result of the derating.
4. Noncurtailing Event - NC
An event that exists whenever equipment or a major component is removed from service for
maintenance, testing, or other purposes that does 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 that required by system
dispatch; and,
b) Maintenance work can be stopped or completed and the units reach its net
dependable capacity (NDC) level within its normal ramp-up time, if and when the
unit was needed by the system.
If the conditions cannot be met, report an outage or derating event rather than an NC.
B. Event Magnitude
The information in this section is used 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.
Figure III-5
Record Layout of Section B Event Magnitude
Record 01
Column ID Number of Columns Starting Position
B Event Magnitude
Start of Event 8 20
(Blank Columns) 20 28
End of Event 8 48
Gross Available Capacity 4 + 2 decimals 56
Net Available Capacity 4 + 2 decimals 62
(Blank Columns) 1 68
Dominant Derating Code 1 69
(Blank Columns) 11 70
Record Number 2 81
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.
Noncurtailing 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. Midnight is recorded as 2400 and the beginning of a new day
is recorded 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
Event Transitions
Sometimes events occur in succession with no intervening unit synchronization. These events are
considered related, even though they must be reported separately. The matrix below describes the
relationships between events and details permissible event type changes, see Example 9 in
Appendix G.
Figure III-6
Allowable Event Type Changes
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 Yes No Yes
PE Planned Extension Yes No No Yes No No No Yes 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.
Yes No
Extension
DP Planned Derating
No Yes
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 could not be tested or enforced. 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.
Reserve Shutdowns time the unit was synchronized or placed in another appropriate
Unit State.
Noncurtailing 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 leaving the end date blank.
When the event does end, submit the end date as a revision, following the instructions on Pages
III-4. 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 preferred, but gross data must be reported if it is the only value available. If you 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-18 to III-21, for more information concerning the
reporting of deratings.
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.
The Dominant Derating Code will be in the unused column 69 of record 01. A dominate derate
will be identified by a D.
One example of how two derates would be reported to GADS one without the Dominant
Derating Code and one with the Dominant Derating Code is shown in Figure III-7.
Figure III-7
Example of Dominant Derating Code Reporting
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
Event#2
#2 D4CC 3112
600
500
D1-CC 3410
400
With Dominant Derating Code
300
2 events to cover 2 incidents
The data elements reported in Sections C and D are the same and will be discussed together.
Section C is used to detail the system, major component, or piece of equipment primarily
responsible for causing the event. Section C is located on Records 02 and 03 of the Event Report
(refer to Figure III-8 on Page III-29). 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 considerations, reporting Section C is optional. Only one
Section C may be reported for each event.
Section D of the Event Report is used to report factors contributing to the cause of the event (but
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 begin with Records 04 and 05 of the Event Report (refer to
Figure III-9 on Page III-30).
Section D is used for several different reasons, as described above, so multiple Section D cards
are allowed. Only one Section D can be used 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.
The even-numbered record is used to begin the description of the cause or the contributing
factors of the event and contains information like man-hours worked. 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.
Figure III-8
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 2 1
Utility Code 3 3
Unit Code 3 6
Year 4 9
Event Number 4 13
Report Revision Code 1 17
Event Type 2 18
C Primary Cause of Event
System/Component Cause Code 4 20
Cause Code Amplification Code 2 24
Time Work Started 8 26
Time Work Ended 8 34
(Blank Columns) 2 42
Event Contribution Code 1 44
Problem Alert 1 45
Man-hours Worked 4 46
Verbal Description 31 50
Record Number 2 81
Record 03
Column ID Number of Columns Starting Position
A Event Identification
Record Code 2 1
Utility Code 3 3
Unit Code 3 6
Year 4 9
Event Number 4 13
Report Revision Code 1 17
Event Type 2 18
C Primary Cause of Event
System/Component Cause Code 4 20
(Blank Columns) 2 24
Verbal Description 55 26
Record Number 2 81
Figure III-9
Record Layout of Section D Additional Work During Event (Records 4+ and 5+)
Cycle/Co-Gen
Concentrated
Gas Turbine
Geothermal
Fluidized
Combine
Nuclear
Diesel
Fossil
Solar
Bed
0000-0002 0000-0002 0000-0002 0000-0002 0000-0002 0000-0002 0000-0002 0000-0002
0010-0129 0010-0129 2010-2090 3600-3690 3600-3690 0358-0480 0500-0620 0358-0480
0200-0480 0130-0156 2110-2160 3700-3730 3700-3730 0540-0570 3110-3199 0670-0859
0500-0920 0160-0174 2170-2799 4500-4899 3810-3899 0670-0859 3210-3299 1300-1350
1000-1090 0200-0480 2805-2890 5700-5880 3950-3999 1300-1599 3300-3399 1400-1450
1100-1210 0500-0920 2900-2999 5890-5999 4500-4899 1700-1820 3600-3690 1590-1850
1300-1360 0930-1090 3110-3199 9000-9040 5000-5039 1850 & 3700-3730 1900-1999
1400-1599 1100-1200 3210-3299 9130-9160 5040-5190 1900-1910 3810-3899 3100-3889
1700-1820 1300-1360 3300-3399 9180-9199 5200-5299 1980-1999 3950-3999 3950-4580
1850 1400-1599 3401-3499 9220-9291 7800-7960 3110-3199 4200-4250 4600-4899
1900-1910 1700-1820 3501-3509 9300-9340 8656 3210-3285 4260-4314 6005-6090
1980-1999 1850 3520-3529 9504-9590 8700-8790 3290-3295 4400-4580 6110-6183
3110-3199 1900-1910 3600-3690 9605-9655 8800-8835 3299 & 4600-4650 6299
3210-3299 1980-1999 3700-3730 9665-9695 8840-8845 3300-3399 4700-4750 6399
3300-3399 3110-3199 3800-3899 9700-9720 9000-9040 3401-3499 4800-4899 6500-6599
3401-3499 3210-3299 3950-3999 9900-9999 9130-9160 3501-3509 6410-6499 9000-9040
3501-3509 3300-3399 4000-4899 9180-9291 3520-3549 8000-8499 9130-9340
3520-3549 3401-3499 9000-9040 9300-9340 3600-3690 8700-8790 9504-9694
3600-3690 3501-3509 9110-9160 9504-9590 3700-3730 9000-9040 9700-9999
3700-3730 3520-3549 9180-9199 9603-9653 3800-3899 9130-9160
3800-3899 3600-3690 9300-9340 9663-9693 3950-3999 9180-9199
3950-3999 3700-3730 9500-9590 9700-9720 4000-4899 9300-9340
4000-4899 3800-3899 9660-9690 9900-9999 5000-5299 9504-9590
8000-8590 3950-3999 9700-9720 5400-5699 9700-9720
8600-8790 4000-4899 9900-9999 6000 & 9900-9999
8800-8845 8000-8590 6005-6090
9000-9040 8600-8790 6100 &
9130-9160 8800-8845 6110-6184
9180-9291 9000-9040 6299 & 6399 Miscellaneous
9300-9340 9130-9160 7800-7960
Jet Engine
Pumped
Storage
Hydro/
Codes
Note: Event Contribution Codes 2, 3, and 5 can be reported on Section D cards, and may be
used more than once. Never leave this field blank.
Verbal Description (Record 02, columns 50-80; Record 03, columns 26-80)
This space is provided to give a more detailed explanation of the event and the cause(s) you
identified by system/component cause code(s). It can also be used to report the expanded data
format as described beginning on Page III-36. 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. There is limited space available for your
description, so we suggest you abbreviate as much as possible. Following the guidelines below
will help you to develop a complete, 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, they should be noted as well. Key words that can
be used to describe corrective actions include the following. This list is by no means
comprehensive. You may use these words as well as any others you feel 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 is burned
open and the cause is electrical overload. Corrective action would be replaced. The
verbal description would be completed as follows: RELAY COIL WIRE BURNED OPEN-
ELECTRICAL OVERLOAD REPLACED WIRE
Some utilities have expressed an interest in reporting more detailed operating and maintenance
data to GADS, which will allow them to perform more detailed reliability analyses. Also, by
including these new data elements, duplicate reporting to other industry databases can be
eliminated. To accommodate this request several new data elements have been added to GADS.
Figure III-11
Record Layout of Event Records Using Failure Codes
Record 02
Column ID Number of Columns Starting Position
A Event Identification
Record Code 2 1
Utility Code 3 3
Unit Code 3 6
Year 4 9
Event Number 4 13
Report Revision Code 1 17
Event Type 2 18
C Primary Cause of Event
System/Component Cause Code 4 20
Cause Code Amplification Code 2 24
Time Work Started 8 26
Time Work Ended 8 34
(Blank Columns) 2 42
Event Contribution Code 1 44
Problem Alert 1 45
Man-hours Worked 4 46
Failure Mechanism Code* 4 50
Trip Mechanism* 1 54
Cumulative Fired Hours at Time of Event* 6 55
Cumulative Engine Starts at Time of Event* 5 61
Verbal Description 15 66
Record Number 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 4 20
(Blank Columns) 2 24
Verbal Description 55 26
Record Number 2 81
Note: There are number of differences between the GADS national database and those
databases collected by the different Independent System Operators (ISO) organizations. Some
are minor changes and some are not. Since GADS is still a voluntary database, there are no
obligations for the ISOs to follow GADS rules and procedures 100%. For more information see
Appendix M.
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.
Note: As of January 1, 2010, GADS only accepts the new (05) format. There was a need by
several Independent System Operators (ISO) groups to collect data on units smaller than 1 MW
in size. There is also a need to collect and report generation smaller than 1 MWh. Therefore, the
GADS database expanded the Gross Maximum Capacity (GMC), Gross Dependable Capacity
(GDC), Net Maximum Capacity (NMC) and Net Dependable Capacity (NDC) to include two
decimal places. GADS also expanded the Gross Actual Generation (GAG) and Net Actual
Generation (NAG) to allow two decimal places.
We are not asking for generating units of 0.01 MW size to report to GADS. Historically
speaking, the smallest units reported to GADS are 1 MW. With the introduction of the 05 format,
GADS can accept smaller units but units less than 1 MW are optional reporting.
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 Figure 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.
Figure IV-1
Record Layout of Section A Unit Identification
All Records
Column ID Number of Columns Starting Position
A Unit Identification
Record Code 2 1
Utility (Company) Code 3 3
Unit Code 3 6
Year 4 9
Report Period 2 13
Report Revision Code 1 15
Monthly Summaries
01 - January 05 - May 09 - September
02 - February 06 - June 10 - October
03 - March 07 - July 11 - November
04 - April 08 - August 12 - December
The first time you submit a performance report to GADS it is called an original. All original
reports have a revision code of zero (0).
Use the following codes when making changes to an original performance 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 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 data provided in this section are used to calculate performance statistics. Both gross and net
values are requested. Net values are preferred but reporting gross data only is acceptable.
Reporting (either) gross and (or) net data depends on how the unit is electrically metered. Some
units are metered on a single basis (gross or net). Enter your units data on the basis of how your
unit is actually metered. If you meter both gross and net, enter both values. If you meter on a
single basis, but can estimate the other, do so and enter the estimated value in the appropriate
field. The elements to be completed in Section B are detailed below. The value you report,
GROSS or NET, must be consistent with the available capacity as a result of deratings reported
on the Event Reports (07).
Figure IV-2
Record Layout of Section B Unit Generation Performance*
Record 01
Column ID Number of Columns Starting Position
B Unit Generation Performance
Gross Maximum Capacity 4 + 2 decimals 16
Gross Dependable Capacity 4 + 2 decimals 22
Gross Actual Generation 7 + 2 decimals 28
Net Maximum Capacity 4 + 2 decimals 37
Net Dependable Capacity 4 + 2 decimals 43
Net Actual Generation 7 + 2 decimals 49
The GMC of a unit should change only as a result of a new performance test or permanent unit
modification. GMC is never changed 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 units 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), GMC or GDC
must also be reported. Similarly, if both service hours and a gross capacity value are reported,
Gross Actual Generation must also be reported. This provides consistency when calculating
performance statistics.
For consistency in calculating statistics, if Net Actual Generation is reported (negative integer or
positive integer), NMC or NDC must also be reported. Similarly, if a net capacity value is
reported, Net Actual Generation must also be reported.
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
For example, if you report only 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 those 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 (*).
Figure IV-3
Effects of Ambient Temperature
on Gas Turbines/Jet Engines
The data elements in this section are used to establish the manner in which the unit was operated
during the month. This information is needed when sorting data for use in special availability and
reliability applications. Section C is located on Record 01; refer to Figure IV-4 below.
Figure IV-4
Record Layout of Section C Unit Starting Characteristics
Record 01
Column ID Number of Columns Starting Position
C Unit Starting Characteristics
Typical Unit Loading Characteristics 1 58
Attempted Unit Starts 3 59
Actual Unit Starts 3 62
(Blank Columns) 34 65
Verbal Description 25 99
Record Number 2 124
Code Description
1 Base loaded with minor load following at night and on weekends
2 Periodic startups with daily load-following and reduced load nightly
3 Weekly startup with daily load-following and reduced load nightly
4 Daily startup with daily load-following and taken off-line nightly
5 Startup chiefly to meet daily peaks
6 Other (describe in verbal description)
7 Seasonal Operation
If the unit was off-line during the entire period, describe how the unit typically would have been
loaded had it been on-line. Never zero-fill, asterisk-fill, or leave this field blank.
If startup attempts are abandoned and 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), your description must be
abbreviated to fit in columns 99-123. No additional records may be used.
The first 15 characters of Record 02 (A Unit Identification) are identical to that of Record 01.
These 15 characters link the records together.
Figure IV-5
Record Layout of Section D Unit Time Information
Record 02
Column ID Number of Columns Starting Position
A Unit Identification
Record Code 2 1
Utility (Company) Code 3 3
Unit Code 3 6
Year 4 9
Report Period 2 13
Report Revision Code 1 15
D Unit Time Information
Unit Service Hours 3 + 2 decimals 16
Reserve Shutdown Hours 3 + 2 decimals 21
Pumping Hours 3 + 2 decimals 26
Synchronous Condensing Hours 3 + 2 decimals 31
Available Hours 3 + 2 decimals 36
Planned Outage Hours 3 + 2 decimals 41
Forced Outage Hours 3 + 2 decimals 46
Maintenance Outage Hours 3 + 2 decimals 51
Extensions of Scheduled Outages 3 + 2 decimals 56
Unavailable Hours 3 + 2 decimals 61
Period Hours 3 + 2 decimals 66
Inactive Hours 3 + 2 decimals 71
(Blank Columns) 48 76
Record Number 2 124
For information regarding work done during Reserve Shutdowns, see Section III, Page III-22.
When calculating statistics involving Maintenance Outage Hours, note that IEEE Standard 762
considers these hours as 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*
Sections E and F, shown in Figures IV-6, detail the type, amount, and quality of fuels burned in
the unit during the reporting period. These sections are used to report primary and secondary
fuels burned and are located on Record 03 of the Performance Report. Tertiary and quaternary
fuels may be reported; however, no unique sections of the Performance Report exist for this
purpose. Instead, use another Section E and another Section F, changing the record number from
03 to 04. Enter the tertiary fuel data in Section E on the 04 record and the quaternary fuel data in
Section F on the 04 record.
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.
Figure IV-6
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 2 1
Utility (Company) Code 3 3
Unit Code 3 6
Year 4 9
Report Period 2 13
Report Revision Code 1 15
E Primary Fuel
Fuel Code 2 16
Quantity Burned 5 + 2 decimals 18
Average Heat Content 6 25
% Ash 2 + 1 decimal 31
% Moisture 2 + 1 decimal 34
% Sulfur 1 + 1 decimal 37
% Alkalines 2 + 1 decimal 39
Grindability Index / % Vanadium 2 + 1 decimal 42
Ash Softening Temperature 4 45
(Blank columns) 21 49
F Secondary Fuel
Fuel Code 2 70
Quantity Burned 5 + 2 decimals 72
Average Heat Content 6 79
% Ash 2 + 1 decimal 85
% Moisture 2 + 1 decimal 88
% Sulfur 1 + 1 decimal 91
% Alkalines 2 + 1 decimal 93
Grindability Index / % Vanadium 2 + 1 decimal 96
Ash Softening Temperature 4 99
(Blank columns) 21 103
Record Number 2 124
Please Note: Performance record 04 for the tertiary and quaternary fuels is identical to
performance Record 03 except record number 04 not 03.
Report in E. Primary Fuel the code for that fuel which made the greatest contribution to thermal
generation during the period. In F. Secondary Fuel, enter the code for that fuel which made the
second greatest contribution to generation. Fuels used for ignition or warm-up can be reported in
this section only 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.
Example:
If coal is your primary fuel and 900 tons of coal was burned in the unit 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)
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:
Steam Consumption (lbs) x 1195.5 (Btu/lb)
Net Generation (kWh)
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)*
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.
Ash Softening Temperature (Records 03 & 04, columns 45-48 and 99-
102)*
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.
Figure V-1
Location of Design Data Forms
When completing the 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 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; and,
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.
The following Change in Unit Status form should be completed whenever a unit is deactivated
or reactivated 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 these data reporting
instructions. The completed Change in Unit Status form should be submitted to Joanne Rura
at joanne.rura@nerc.net.
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?
This appendix contains system/component cause codes to use when completing GADS Event
Report (97). For ease of use, it is divided into sections based on type of generating unit. Each
section contains all the codes that can be used for each unit type. For example, the section for
fossil steam units includes codes for the boiler, steam turbine, generator, balance of plant,
pollution control equipment, external, regulatory, safety, and environmental, personnel errors,
and performance testing. The section for hydro/pumped storage units contains the codes needed
to report the electrical systems, generator, the hydro turbine/pump, external, regulatory, safety,
and environmental, personnel errors, and performance testing. (Figure III-10, Page III-31, is a
convenient reference that lists the appropriate system/component cause codes applicable to each
type of generating unit.)
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.
This way, the plant data reporter will have only the codes needed to report events, and therefore,
may avoid some data reporting errors.
Please note, a separate section is not included for Miscellaneous units. Additional cause codes
for combined cycle and co-generation units are shown on Pages B-CC-1 to B-CC-34. There is
also a section for geothermal units on Pages B-GE-1 to B-GE-20.
The intent of this appendix is not to provide a code for all possible causes or all components, but
to provide, in general terms, the cause or component. The details concerning a more specific
cause/component, the type of failure, method of repair/nature of work, repair effort and/or
combination of preceding events are to be included in the Verbal Description on the event report.
Also, utilities have the option of reporting more detailed information concerning the manner in
which a system or component failed using the Failure Mechanism Code. See Page III-36 and
Appendix H for more information.
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 several other major components, then use the code for AC power distribution.
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
0358 Oil burner piping and valves
0359 Gas burner piping and valves
0360 Burners
0362 Burner tilts
0361 Burner orfices
0370 Burner instruments and controls (except light-off)
0380 Light-off (igniter) systems (including fuel supply)
0385 Igniters
0390 Burner wind boxes and dampers
0400 Burner wind box fires
0410 Other burner problems
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
1080 Economizer
1090 Other boiler tube leaks
Boiler Tube Fireside Slagging or Fouling (use codes 0860 and 0870 for fouling or slagging due to
unavailability of soot blowers or their air or steam supply)
Boiler Air and Gas Systems (excluding burner pipes, wind boxes, primary air, or pulverizer
exhausters)
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 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-
1)
1801 Minor boiler overhaul (less than 720 hours) (use for non-specific overhaul only; see page B-
1)
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
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
Extraction Steam
Electrical
Electrical (Continued)
Auxiliary Systems
Open Cooling Water System
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
Controls (Continued)
4400 Major turbine overhaul (720 hours or longer) (use for non-specific overhaul only; see page
B-1)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hours) (use for non-specific overhaul only; see page
B-1)
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 including the generator output breaker are included 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)
Use this set of codes to report problems with flue gas desulphurization equipment and stack gas particulate
removal equipment. If outages or deratings occur due to reasons other than equipment problems, use the
set of codes for Regulatory, Safety, Environmental stack emission limits.
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)
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
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
NOx Reduction Systems (Use code 0360 for Low NOx Burners)
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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
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
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
Safety
INACTIVE STATES
Cause Code
BOILER Ranges Page No.
BALANCE OF PLANT
Cause Code
STEAM TURBINE _Ranges Page No.
GENERATOR
Generator 4500-4580 B-FB-24
Exciter 4600-4609 B-FB-24
Cooling System 4610-4650 B-FB-24
Controls 4700-4750 B-FB-24
Miscellaneous (Generator) 4800-4899 B-FB-25
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
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
Boiler Tube Fireside Slagging or Fouling (use codes 0860 and 0870 for fouling or slagging due to
unavailability of soot blowers or their air or steam supply)
Boiler Air and Gas Systems (excluding burner pipes, wind boxes, primary air, or pulverizer exhausters)
Air Supply
*For FBC units, this is the same as primary air fans and their motors.
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
Boiler Control Systems (including instruments which input to the controls) (Continued)
1800 Major boiler overhaul (720 hours or longer) (use for non-specific overhaul only; see page B-
1)
1801 Minor boiler overhaul (less than 720 hours) (use for non-specific overhaul only; see page B-
1)
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
Condensate System
Pumps, Piping, and Valves
Polishers/Chemical Addition
Extraction Steam
Electrical
Electrical (Continued)
Auxiliary Systems
Open Cooling Water System
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
Controls (Continued)
4400 Major turbine overhaul (720 hrs or longer) (use for non-specific overhaul only; see page B-
1)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hrs) (use for non-specific overhaul only; see page B-
1)
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 including the generator output breaker are included 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)
Use this set of codes to report problems with flue gas desulphurization equipment and stack gas particulate
removal equipment. If outages or deratings occur due to reasons other than equipment problems, use the
set of codes for Regulatory, Safety, Environmental stack emission limits.
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)
* 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
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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Economic (Continued)
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
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
Safety
INACTIVE STATES
PERFORMANCE
9997 NERC Reliability Standard Requirement
9998 Black start testing
9999 Total unit performance testing (use appropriate codes for individual component testing)
NUCLEAR UNITS
INDEX TO SYSTEM/COMPONENT CAUSE CODES
(Unit Codes 200-299)
Cause Code
NUCLEAR REACTOR Ranges Page No.
BALANCE OF PLANT
STEAM TURBINE
Cause Code
GENERATOR Ranges Page No.
EXTERNAL
NUCLEAR REACTOR
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
Core Cooling/Safety Injection (where portions of these systems also serve in the makeup system, report
problems as CVCS problems)
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)
2628 Residual heat removal/decay heat removal system
2629 Other low pressure problems
2630 Safeguard actuation system (including sensors, logic, activators, and sequencers)
2649 Other emergency core cooling/residual heat removal system problems
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-1)
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
Pumps, Piping, and Valves
Polishers/Chemical Addition
Extraction Steam
Auxiliary Systems
Open Cooling Water System
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
Controls (Continued)
4400 Major turbine overhaul (720 hours or longer ) (use for non-specific overhaul only; see page
B-1)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hours) ) (use for non-specific overhaul only; see page
B-1)
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
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 including the generator output breaker are included 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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Economic (Continued)
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
9340 Synchronous Condenser Operation
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
Safety
INACTIVE STATES
PERFORMANCE
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
Electrical (Continued)
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note the main
leads up to and including the generator output breaker are included 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
5890 Major overhaul (use for non-specific overhaul only; see Page B-1)
5895 Inspection
5990 Engine performance testing - individual engines (use code 9999 for total unit performance
testing)
5999 Other miscellaneous diesel engine 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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
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
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
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 Page No.
GENERATOR
HYDRO TURBINE/PUMP
EXTERNAL
BALANCE OF PLANT
Electrical
Electrical (Continued)
Auxiliary Systems
Service Water (Open System)
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 including the generator output breaker are included 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
4520 Stator windings, bushings, and terminals
4530 Stator core iron
4535 Stator, General
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
7099 Other turbine problems
Water Supply/Discharge
7200 Major overhaul (use for non-specific overhaul only; see page B-1)
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)
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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
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
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
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
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
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls.
Note the main leads up to and including the generator output breaker are included 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
Compressors
Exhaust Systems
5100 Chamber
5101 Hoods
5102 Vanes/nozzles
5103 Silencer
5104 Cones
5105 Diverter Dampers
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
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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Economic (Continued)
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
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
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
Cause Code
BALANCE OF PLANT Ranges Page No.
GENERATOR
JET ENGINE
EXTERNAL
Cause Code
Ranges Page No.
REGULATORY, SAFETY, ENVIRONMENTAL
BALANCE OF PLANT
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
GENERATOR
This set of codes contains the generator, exciter, generator cooling systems, and generator controls. Note
the main leads up to and including the generator output breaker are included 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
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
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
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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Economic (Continued)
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
Use these codes only for outages or deratings 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
Safety
INACTIVE STATES
0002 Inactive Reserve Shutdown
9990 Retired unit
9991 Mothballed unit
PERFORMANCE
Cause Code
GAS TURBINE Ranges Page No.
JET ENGINE
STEAM TURBINE
GENERATOR
Cause Code
HRSG BOILER Ranges Page No.
BALANCE OF PLANT
EXTERNAL
GAS TURBINE
Compressors
Exhaust Systems
5100 Chamber
5101 Hoods
5102 Vanes/nozzles
5103 Silencer
5104 Cones
5105 Diverter Dampers
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
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
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.
Valves
Piping
Lube Oil (do not include bearing failures due to lube oil)
Controls
Controls (Continued)
4400 Major turbine overhaul (720 hours or longer) (use for non-specific overhaul only; see page B-
1)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hours) (use for non-specific overhaul only; see page B-
1)
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 including the generator output breaker are included 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
6120 IP steam piping up to turbine stop valves Between 200 & 600 PSIG
(see 0790 for piping supports)
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
Boiler Recirculation
Miscellaneous (Piping)
HRSG Boiler Tube Leaks (use code 0859 for tube/membrane failures)
Air Supply
1590 Stacks
1591 Stack damper and linkage
1592 Stack damper linkage motors
1599 Other miscellaneous boiler air and gas system problems
HRSG Boiler Control Systems (including instruments which input to the controls)
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
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
Extraction Steam
Electrical
Electrical (Continued)
Auxiliary Systems
Open Cooling Water System
Auxiliary Steam
Service Air
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
NOx Reduction Systems (Use code 0360 for Low NOx Burners)
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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Economic (Continued)
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
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
Safety
INACTIVE STATES
PERFORMANCE
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
Boiler Piping System
Main Steam
Desuperheaters/Attemperators
BALANCE OF PLANT
Condensing System
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
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-1)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hours) (use for non-specific overhaul only; see page
B-1)
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 including the generator output breaker are included 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
Use this set of codes to report problems with flue gas desulphurization equipment and stack gas particulate
removal equipment. If outages or deratings occur due to reasons other than equipment problems, use the
set of codes for Regulatory, Safety, Environmental stack emission limits.
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)
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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Economic (Continued)
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
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
Safety
INACTIVE STATES
PERFORMANCE
Cause Code
Ranges Page No.
STEAM TURBINE
GENERATOR
HRSG BOILER
BALANCE OF PLANT
EXTERNAL
Thermal Storage
Operational 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
Controls (Continued)
4400 Major turbine overhaul (720 hours or longer) (use for non-specific overhaul only; see page
B-1)
4401 Inspection
4402 Minor turbine overhaul (less than 720 hours) (use for non-specific overhaul only; see page
B-1)
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 including the generator output breaker are included 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
6120 IP steam piping up to turbine stop valves Between 200 & 600 PSIG
(see 0790 for piping supports)
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
6170 IP Startup bypass system piping (including drain lines up to heaters or condenser)
Between 200-600 PSIG
Boiler Recirculation
Miscellaneous (Piping)
HRSG Boiler Tube Leaks (use code 0859 for tube/membrane failures)
Air Supply
1590 Stacks
1591 Stack damper and linkage
1592 Stack damper linkage motors
1599 Other miscellaneous boiler air and gas system problems
HRSG Boiler Control Systems (including instruments which input to the controls)
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
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. X 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
Extraction Steam
Electrical
Electrical (Continued)
Auxiliary Systems
Open Cooling Water System
Auxiliary Steam
Service Air
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
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
9010 Fire, not related to a specific component
9020 Lightning
9025 Geomagnetic disturbance
9030 Earthquake
9035 Hurricane
9036 Storms (ice, snow, etc)
9040 Other catastrophe
Economic
Economic (Continued)
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
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
Safety
INACTIVE STATES
PERFORMANCE
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:
Fossil (Steam)
100 - 199
(Use 600-649 if additional numbers are needed)
Hydro/Pumped Storage
500 - 599
(Use 900-999 if additional numbers are needed)
Miscellaneous
(Multi-Boiler/Multi-Turbine, Geothermal, Combined Cycle Block, Concentrated 800 - 899
Solar Power, etc.)
212-840-1070
212-302-2782 Fax
115 TransCanada
116 Commonwealth Energy System
117 N.Y. State Electric & Gas Corp.
118 NRG Energy
119 Mirant New York
120 New York Power Authority
121 Public Service of New Hampshire (NE)
122 Rochester Gas & Electric Corp.
123 Wisvest-Connecticut, LLC
124 W. Massachusetts Electric Co. (NE)
125 Yankee Atomic Electric Co.
126 Massachusetts Municipal Wholesale Electric Co.
127 Dominion Energy (NPCC)
128 Connecticut Yankee Atomic Power Co.
129 Montaup Electric Co.
130 ARC-SEMASS
131 Exelon Generation (New England)
132 Global Common Greenport LLC
133 FPL Energy (NPCC)
134 Nantucket Electric
135 Kimberly-Clark
136 Mirant New England
137 Ocean State Power
138 American National Power
139 Penobscot Hydro LLC
140 TransCanada Ravenswood
141 NRG Energy New England
142 Ipswich Municipal Light Department
143 VAE Lowell Power
144 Entergy Nuclear Northeast
145 Berkshire Power Company, LLC
146 Massachusetts Bay Transportation Authority
147 Brainstree Electric Light Department
148 Indeck Pepperell Power
149 Milford Power Co.
150 Connecticut Municipal Electric Energy Coop.
151 US Power Generating Co. (USPowerGen)
152 NRG Energy New York
153 Ogden Martin Babylon
154 YESCo Power
155 Calpine (NPCC)
156 Columbia/ZAPCO
157 Montenay Power
158 Covanta Energy Corp.
159 Nissequogue Cogen
160 Marblehead Municipal Light Department
161 PPL Generation Co. (New England)
162 Equus Power One, LP (number was Aquila - NPCC)
163 Wyeth-Ayerst Pharmaceuticals
164 NAEA
165 Energy Systems Northeast (ESNE)
166 AES Energy (NPCC)
167 Taunton Municipal Light
168 Shrewsbury Electric Light Plant
169 Granite Ridge Energy
170 Masspower
171 Unitil Power Corp.
172 Fitchburg Gas and Electric Light Co.
173 NextEra Energy Resources Seabrook Station
174 Covanta Haverhill, Inc.
175 Wheelabrator Millbury, Inc.
176 Wheelabrator Technologies, Inc.
177 Barre Energy Partners, L.P./Zahren Alternative Power Company
178 Ridgewood Providence Power Partners, L.P.
179 Waste Management of New Hampshire, Inc.
180 Suncook Energy LLC
181 Massachusetts Water Resources Authority
182 Vermont Electric Power Co.
183 CHI Energy
184 Hafslund U.S.A., Inc.
185 American Paper Mills of VT
186 Hudson Light & Power
187 Sterling Municipal Electric Light Department
188 Chicopee Hydro Electric Limited Partnership
189 Swift River Co.
190 Northeast Generation Co.
191 PS&H IPPS
192 Boralex Operation Inc.
193 Pioneer Electric Hydro Co., Inc.
194 Connecticut Resources Recovery Authority
195 Springfield Water and Sewer Commission
196 Dynegy
197 Peabody Municipal Light
198 New Hampshire Electric Cooperative, Inc.
199 Indeck Pepperill Power Associates
330-456-2488
704-357-7372
813-289-5644
813-289-5646 Fax
651-855-1760
501-664-0146
512-225-7000
801-582-0353
801-582-3918 Fax
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 such items 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. Auxiliary air system or a service water system are
not considered as part of a major component.
Engines
Generators
Startup System
Exciter
Turbines
Generators
Exciters
Gas Turbines
Heat Recovery Steam Generators (waste heat boiler)
Steam Turbines
Generators
Exciters
Feedwater Pumps
Circulating Water Pumps
Main Transformers
Burners
Condensers
Boiler Circulation Pumps
Condensate/Feedwater Heaters
Condensate Pumps
This appendix contains the unit design forms described in Section V. These forms must be
completed before any event or performance data are submitted. These forms should also be
completed when the design of the unit changes. Completed forms should be sent to Mike Curley
at mike.curley@nerc.net.
Page
Manufacturers E-2
Manufacturers
01 - General Electric
04 - Stanley
05 - Elliott
06 - Electric Machinery
07 - Gulf General
08 - (Blank)
09 - Other
11 - MAN
12 - Parsons
13 - Siemens (SiemensWestinghouse)
15 - English Electric
Fuel Codes
Enter the fuel code from the table below which best describes the primary and secondary fuels
the unit was designed to burn:
Coal 13 Propane
18 Lignite
Oil
19
05 Oil Only
20
06 Oil & Coal
99 Other
07 Oil & Gas
Gas
09 Gas Only
Fossil Steam
Instructions
Use these forms to report design and installed equipment information for FOSSIL (steam) units.
FOSSIL units are those 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 that not used to carry normal load unless specifically
requested.
You will notice some data fields 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 manufacturers equipment and M2 for the other.
Utility name:
Station name:
Unit name:
Regional Entity:
Subregion:
Data reporter:
Telephone number:
Date:
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 is 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.
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)
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).
TOTAL number of fuel oil burner supply pumps; include installed
spares.
MINIMUM number of fuel oil burner supply pumps required to
obtain maximum capacity from the unit.
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.
TOTAL number of pulverizers or coal mills; include installed spares.
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 by-pass capacity at compliance levels. (Enter 0% if no by-pass capacity exists.)
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 - By-pass reheater - by-pass 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.
1 - Motor
2 - Shaft
3 - Steam turbine
9 - Other, describe
Generator manufacturer
1 Yes 2 No
RPM
Enter the mediums used to cool the generators 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
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.
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
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 that not used to carry normal load
unless specifically requested.
You will notice some data fields 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 manufacturers equipment and M2 for the other.
Utility name:
Station name:
Unit name:
Regional Entity:
Subregion:
Data reporter:
Telephone number:
Date:
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).
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:
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).
Manufacturer(s) of the motor(s) that drives the crusher(s).
TOTAL number of crushers.
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:
1 - Single-speed motor
2 - Two-speed motor
3 - Variable-speed motor
4 - Steam turbine
5 - Fluid drive
9 - Other, describe
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:
1 - Single-speed motor
2 - Two-speed motor
3 - Variable-speed motor
4 - Steam turbine
5 - Fluid drive
9 - Other, describe
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:
1 - Single-speed motor
2 - Two-speed motor
3 - Variable-speed motor
4 - Steam turbine
5 - Fluid drive
9 - Other, describe
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
Enter the location of the electrostatic precipitator with respect to the air heaters:
Bag material.
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 turbines first stage
at startup.
2 - Full arc - main steam is admitted to all sectors of the turbines first stage at startup.
3 - Either - capable of admitting steam using either partial or full arc techniques.
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 generators 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 units maximum capacity that can be achieved using a single
startup feedwater pump.
M1 M2
Indicate the additional capabilities of the startup feedwater pump:
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):
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
Nuclear
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 (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:
2 1 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
Diesel
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:
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
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, 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:
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
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, 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:
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
_________________________________________________________________________________________________________
Page E-GT-2 GADS Data Reporting Instructions January 2011
Gas Turbine or Jet Engine Units Appendix E Unit Design Data Forms
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
_________________________________________________________________________________________________________
Page E-GT-4 GADS Data Reporting Instructions January 2011
Gas Turbine or Jet Engine Units Appendix E Unit Design Data Forms
GENERATOR DATA
3 3 07 Card code
_________________________________________________________________________________________________________
Page E-GT-6 GADS Data Reporting Instructions January 2011
Combined Cycle Units and Co-generation Blocks Appendix E Unit Design Data Forms
Utility name:
Station name:
Unit name:
Regional Entity:
Subregion:
Data reporter:
Telephone number:
Date:
INSTRUCTIONS
In order to continue this discussion, some terms must be agreed on to eliminate some of the
ambiguity concerning combined cycle blocks in general.
There may be more than one block at a plant site. This design form should be completed
for each individual block.
Units Each gas turbine/jet engine and each steam turbine are considered a unit. Each
unit contributes to the total electric generation or steam production of the block. Each unit
has or shares its generator for providing electric power. They are considered to be
individual parts of the block.
Heat Recovery Steam Generator (HRSG) There may be one or more HRSG or waste
heat boiler in a block. Some blocks may have a single HRSG per GT/jet; others may have
several GT/jet feeding a single HRSG or any combination thereof. The HRSG does not
contribute electricity to the output of the block and so, is considered a component rather
than a unit.
Other Balance of Plant Equipment There are other equipment in the block used to
support the production of electricity/heat energy. They are not related to any specific
generating unit and are also considered as 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, 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.
1. Identification
A series of codes uniquely identifies your utility (or company) and the block. NERC assigned a unique code
to identify your company. You must assign the unique code that will identify the block being reported. This
block code may be any number from 800 to 899. Enter the unique company and block code and the full name
of the entire block below:
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 megavoltamperes (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 megavoltamperes (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) Seimans 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. Startup system - (1) Air; (2) Auxiliary motor; (3) Electric motor; (4) Natural gas; (5) Flow
turbine; (6) Supercharging fan; (7) Hydraulic; (9) Other
22. Startup type - (1) Automatic, on site; (2) Automatic, remote; (9) Other
27. Time for normal cold start to full load in seconds: _________________
28. Time for emergency cold start to full load in seconds: ______________
________________________________________________________
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 lbs./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 generators stator (air, hydrogen, oil, water): ______________
Enter the mediums used to cool the generators 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.
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 lbs/hr): ______________________
REHEAT PRESSURE
Steam flow rate (in lbs/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 is 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 HRSGs 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 HRSGs maximum capacity that can be achieved with a single
startup 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:
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): ______________
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): ____________
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
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
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 generators stator (air, hydrogen, oil, water): ______________
Enter the mediums used to cool the generators rotor (air, hydrogen, oil, water): _______________
Exciter manufacturer:
MINIMUM number of exciters required to obtain maximum capacity from the unit:
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
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:
Enter the type of air removal equipment used on the condenser: _______________
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:
Miscellaneous
Instructions
Use these forms when no other forms in this appendix are appropriate. Specifically, use them for
multi-boiler/multi-turbine 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, 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:
8 1 07 Card code
22 Energy medium - (1) Water and/or steam; (2) Heavy water and/or
steam; (3) Liquid metal; (4) Gas; (5) More than one;
(6) Direct conversion; (9) Other
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
> 26 R carrier gas total flow rate (thousands of lbs./hr.) i.e. 6,000,000
lbs./hr. enter 6000
69 CAH catalyst support material - (1) Stainless steel; (2) Carbon steel;
9) Other
> 72 CAH catalyst material total face area (thousands of square feet)
GENERAL DATA
07 Card code
8 3
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).
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).
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
*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
GADS Data Reporting Instructions January 2011 F-5
Appendix F Performance Indexes and Equations
* 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:
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 of 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 such 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, 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).
The current IEEE 762 Standard's unweighted equations should not be abandoned, however, 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) do change somewhat.
GADS Data Reporting Instructions January 2011 F-7
Appendix F Performance Indexes and Equations
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
1 1 1 1
f = 1 + / + + r=Average Forced outage duration = (FOH) / (# of FO occurrences)
r T r T D D=Average demand time = (SH) / (# of unit actual starts)
T=Average reserve shutdown time = (RSH) / (# of unit attempted starts)
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)
1 1 1 1
f = 1 + / + + r=Average Forced outage deration = (FOH) / (# of FO occurrences)
r T r T D D=Average demand time = (SH) / (# of unit actual starts)
T=Average reserve shutdown time = (RSH) / (# of unit attempted starts)
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
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
1 1 1 1
f = 1 + / + + r = Average Forced outage deration = (FOH) / (# of FO occurrences)
r T r T D 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)
1 1 1 1
f = 1 + / + + r = Average Forced outage deration = (FOH) / (# of FO occurrences)
r T r T D D = Average demand time = (SH) / (# of unit actual starts)
T = Average reserve shutdown time = (RSH) / (# of unit attempted starts)
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
1 1 1 1
f = 1 + / + + r = Average Forced outage deration = (FOH) / (# of FO occurrences)
r T r T D 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)
1 1 1 1
f = 1 + / + + r = Average Forced outage deration = (FOH) / (# of FO occurrences)
r T r T D 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]
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)
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:
Consistancy 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 groups 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. The first table shows the raw data reported by 5 steam turbine generating units.
The second table 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
Weighted Pooling
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 a third table is added to show the weighted values used in the
calculations.
Weighted values in the above table are denoted with preceding w to indicate that the value has been
weighted by its NMC. Below we substitue the weighted value for the expanded multiplication wFORd 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%.
o
(102152.67 + 19903.71) = 7.601%
(102152.67 + 1503618)
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
((0.8930 121148) + (0.7630 25343.59)) = 7.912%
(1503618 + (0.7630 121148))
3. Average wEFORd uses the sum of the weighted unit EFORd values to calculate the numerical average.
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 above, and you will see that the relationship between the methods
does not remain constant and is dependant 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 H-1.
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.
Table G.1
Limiting Conditions for Forced Outage Indexes
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 mythical 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 are 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 failures 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 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.).
_____________________________________________________________________________________
Page G-2 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
500_
400_
300_
200_
100_
0_
Jan 3 Jan 8
04:30 17:00
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.
_____________________________________________________________________________________
Page G-4 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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
_____________________________________________________________________________________
Page G-6 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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
_____________________________________________________________________________________
Page G-8 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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 units 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.
_____________________________________________________________________________________
Page G-10 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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.
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 units Net Available
Capacity.
Derating A
Derating B
_____________________________________________________________________________________
Page G-12 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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_
300_ DERATING B
200_
100_
0_
Jan 13 Jan 13 Jan 13 Jan 14
08:00 10:00 13:00 20:00
_____________________________________________________________________________________
Page G-14 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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 units
circulating water pumps to shutdown (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 4.00 clock hours of repair and
11.25 clock hours of repair, respectively.
_____________________________________________________________________________________
Page G-16 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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. 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.
_____________________________________________________________________________________
Page G-18 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
Additional Components
Worked
500_
400_
300_
200_
100_
0_
April 10 April 10
06:30 19:00
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:
_____________________________________________________________________________________
Page G-20 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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
Example 6A:
Derating Overlapped by a Full Outage
Derating Ends Before Full Outage
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.
_____________________________________________________________________________________
Page G-22 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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
09:45 01:15 18:30 09:22
Example 6B:
Derating Overlapped by a Full Outage
Full Outage Begins and Ends During Derating
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
_____________________________________________________________________________________
Page G-24 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
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).
_____________________________________________________________________________________
Page G-26 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
500_
Planned Outage
400_
Startup Failure
300_
200_
100_
0_
From Oct 1 Oct 3
September 22:00 03:00
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.
Riverglenns 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):
_____________________________________________________________________________________
Page G-28 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
The situation described above typically affects fossil and hydro units. Nuclear units are some-
times 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 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.
_____________________________________________________________________________________
Page G-30 GADS Data Reporting Instructions January 2011
Appendix G Examples and Recommended Methods
Component Repair
The scrubber ID fan is charged with 38.50 hours associated with repair and the waterwall tubes
with 80.00 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
_____________________________________________________________________________________
Page G-32 GADS Data Reporting Instructions January 2011
Appendix H Failure Mechanism Codes
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
NERC Generating Availability Data System (GADS) contains information which can be broadly
classified into two categories: design data, which is descriptive of equipment physical and
operational characteristics, 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, manufacturers and equipment
suppliers, 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.
Unless expressly permitted in the following sections, data by power generator, pool, Region, or
specific unit will be provided only with the authorization of the appropriate power generator,
pool, or Region. (Power generators are any owners or operators of electric generating units
owned/operated by investor-owned, independent power project (IPP), municipals, cooperative,
federal, state, and every other groups of electric providers.) 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 Generating
Availability Report and the GADS Brochure. The latest versions can be downloaded from the
NERC web site: http://www.nerc.com/page.php?cid=4|43|47.
Power generator owners/operators who report GADS data for all units outlined in the GADS
Data Reporting Instructions Figure III-1 (shown as required for the different unit types) may
receive any special data analyses, data analysis-type software products like pc-GAR or standard
publication without restriction, except that large amounts of power generator, pool, Region, or
specific unit data will be provided only with the permission of the appropriate power generator,
pool, or Region. Power generator representatives are understood to refer to employees of the
member power generators, power pools, or regional entities.
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 Figure 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.
Manufacturers and equipment suppliers may receive the standard publication. They may also
receive individual analyses and outage records concerning the equipment they supplied, as well
as total unit performance statistics. National, regional, or local summary analyses of the
manufacturer's or equipment supplier's equipment compared to all others as a group can be
provided. These analyses may collectively review all competitors, but will not identify an
individual competitor; nor will they rank competitors, power generators, pools, or regions
without their specific authorization.
Architect-engineers and consultants may receive the standard publication. They may also receive
individual analyses and outage records concerning the equipment they designed or installed, as
well as total unit performance statistics for those same units. National, regional, or local grouped
units summary analyses on the performance of the architect-engineer's or consultant's units
compared to all others as a group can be provided. These analyses may collectively review all
competitors but will not identify an individual competitor; nor will they rank competitors, power
generators, pools, or regions without their specific authorization. If an architect-engineer or
consultant is under contract to a power generator client, that architect-engineer or consultant may
receive any information the power generator may receive, as long as the client power generator is
identified and approves.
Industry organizations such as EEI, EPRI, and INPO may receive the standard publication. They
may also receive any analyses that do not identify individual units, power generators, pools, or
regions.
Federal governmental organizations may receive the standard publication. They may also receive
any analyses that do not identify individual units, power generators, pools, or regions.
State and local governmental 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 NERC region(s).
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.
Publication or re-transmittal by those who have received GADS data, reports, or analyses specific
to individual or identifiable units, power generators, pools, or regions is considered a matter
separate and distinct from requesting such data for the internal use of the requester. As such,
authorization for publication must be expressly obtained by the requester from the appropriate
power generator(s), pool(s), or NERC region(s), and NERC.
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.
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-32). 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 analyst to further explore the common causes of outages.
GADS
Code Description
GADS
Code Description
GADS
Code Description
62 Noisy
63 Open
64 Overload
U0 Parts unavailable
P0 Personnel error
65 Pitting (localized corrosion)
66 Pressure, not within limits
67 Rubbing damage axial related contacts (use F050 if contact is in radial
direction)
68 Secondary damage
69 Seized (not moving)
71 Short-term overheating
70 Shorted electrical component
A0 Silica restriction
S0 Slagging
72 Sticking
73 Stree corrosion cracking
74 Temperature compressor discharge, not within limits
75 Temperature exhaust, not within limits
78 Temperature general, not within limits
76 Temperature oil, not within limits
77 Temperature wheel spacers, not within limits
79 Testing
80 Thermal fatigue
81 Torn
82 Tripped/shutdown component automatic
83 Tripped/shutdown component manual
T1 Tripped/shutdown grid separation automatic
T2 Tripped/shutdown grid separation manual
84 Unknown investigation underway (change this code once failure mechanism is
determined)
V0 Vibration (other)
86 Vibration fatigue, leading to failure
85 Vibration, not within limits
87 Voltage, not within limits
D0 Water induction
89 Weld failure broken weld
90 Weld failure dissimilar metals
91 Weld failure weld defects
88 Welded relay contacts
W0 Wet coal/frozen coal/debris
92 Wiped
93 Worn, excessively
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 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 companys 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 units 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
units 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 isnt
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, well 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 shadowed Unit available hours increase by the outage
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 an The effect of removing the OMC event is to
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.
Overview
This document will explain the synthesis method for collecting combined cycle data on a unit-
level basis and creating combined cycle block statistics from the unit-level event and
performance information.
This document applies to only those reporters who wish to report event and performance data for
each generating unit individually. This document does not apply to those reporters wishing to
continue reporting combined cycle data to GADS as a single unit (or traditional method). The
traditional method will still be accepted by GADS but 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 are 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, 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
In order to continue this discussion, some terms must be agreed on to eliminate some of the
ambiguity concerning combined cycle blocks in general.
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. 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 boiler 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 will be reported as though each unit were a separate generator.
That being 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 will 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
conceivable 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 or 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 provide
options to all since the individual needs of GADS data users also vary.
There will be times when two units will be out (one on outage and the other on derate) and the
computer will realize by examining the units event records that the unit is not in service but the
combined cycle block is still providing electric power.
Examples of creating a block performance record are illustrated in the examples below. 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.
Now, 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 of the resultant outage of the
GT affected the steam production on the steam turbine, resulting in the steam turbines 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 (doesnt say which one, just a GT).
Therefore, the GT gets two penalties against it: for the outage (to the GT#1 itself) and 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 component (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 would be calculated based on only the performance and event records directly
attributed to each of the individual units. However, when you report on cause code or component
based values, the entire effect of the outage will be taken into account. With the effect of the
outage being attributed to the component and not the unit, the unit is not unduly penalized.
The number of MWhs generated by each unit can be added together monthly for creating a MWh
generated combined cycle block.
However, the number of service hours, forced outage hours, etc for the combined cycle block
performance record can only be created by analyzing the unit event records on an event by event
basis. This procedure is necessary to determine if the combined cycle block is generating power
or is completely off line. In the synthesis method, the sum of the units FO, PO, etc cannot be
used. For example, if a GT is on forced outage, then the combined cycle block may still be
generating power and the GT outage hours are not reflected on the block performance record
because it is a derating for the block, not a block outage.
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
by the first units 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 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.
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) are
considered coast downs and not reported as penalties against the combined cycle block. (See
Example #7).
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
Big Jumbo Block placed on RS from January 3 at 0015 to January 6 at 0215. The
combined cycle block has 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 are no
equipment restrictions. There are only load requirements caused the reduced loading.
Diagrams of the units and combined cycle block during this period is shown below:
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 to generate 568
MW.
Diagrams of the units and combined cycle block during this period is shown below:
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.)
No impact on Big Jumbo Block. The combined cycle block was capable to generate 710 MW the
full period.
Diagrams of the units and combined cycle block during this period is shown below:
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 to generate 355 MW 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 to generate 710 MW the full period.
Diagrams of the units and combined cycle block during this period is shown below:
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 to generate 710 MW 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 to generate 355 MW the full period.
Diagrams of the units and combined cycle block during this period is shown below:
GT #1 on Reserve Shutdown for 30.50 hours and on Forced Outage for 1.25 hours.
GT #2 on Reserve Shutdown for 6.58 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 to generate 485 MW 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 to
generate 355 MW the full 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 to generate 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 to generate 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 to
generate 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 to
generate 450 MW during this period.
Now, as the combined cycle block was preparing to come off line for the PO, each unit came off
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.
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.
Statistic GT #1 GT #2 ST #1 CC Block
Net Maximum Capacity 225 225 260 710
Period Hrs 744 744 744 744
Forced Outage Hrs 1.25 8.75 0.00 0.00
Planned Outage Hrs 172.75 178.00 174.25 172.50
Maintenance Outage Hrs 0.00 0.00 0.00 0.00
Reserve Shutdown Hrs 121.50 214.58 92.66 89.83
Service Hrs 448.50 342.67 477.09 481.67
Equiv.Forced Derated Hrs 0.80 0.80 5.72 5.77
EFDH During RS Hrs 0.00 0.00 0.63 0.50
Equiv. Sched. Derated Hrs 0.00 0.00 2.63 3.61
Net Actual Generation 100,000 77,000 124,000 301,000.00
Attempted Starts 6.00 7.00 4.00 4.00
Actual Starts 5.00 7.00 4.00 4.00
This document applies to only those reporters who wish to report event and performance data for
each generating unit individually. This document does not apply to those reporters wishing to
continue reporting combined cycle data to GADS as a single unit (or traditional method). The
traditional method will still be accepted by GADS but 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 are 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
In order to continue this discussion, some terms must be agreed on to eliminate some of the
ambiguity concerning combined cycle blocks in general.
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. 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 boiler 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 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 will be reported as though each unit were a separate generator.
That being 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 will 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
conceivable 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 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 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 or 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 provide
options to all since the individual needs of GADS data users also vary.
Examples of creating a block performance record using the fleet-type roll up are illustrated in the
examples below. 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 of the resultant outage of the GT
affected the steam production on the steam turbine, resulting in the steam turbines 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 (doesnt 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 would be 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 penalized.
You do need to keep in mind that when using the equivalent fleet roll-up method that you
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 units maximum capacity (Net Maximum Capacity). So, for instance, service hours become
service MW-hours.
This works for a single unit, but, if period hours are used for the block, the following
relationship doesnt 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 MW hours for all units to create the values for the block
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) are considered coast downs and not reported as penalties against the
combined cycle block. (See Example #7).
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
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.
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 Jan.14 at 2215 to Jan.16 at 0445. GT #1 was capable of providing
225 MW during this period.
Steam turbine was placed on reserve shutdown from Jan.15 at 2300 to Jan.16 at 0600. The steam
turbine unit was capable of providing 260 MW during this period.
GT #2 was placed on RS from Jan.15 at 2310 to Jan.16 at 0545. GT #2 was capable of providing
225 MW during this period.
GT #1 on Startup Failure outage (SF) from Jan.16 at 0445 to Jan.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 Jan.16 at 0445 to Jan.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
1. PO of 38,868.75 MWh
2. PO of 40,050 MWh
3. PO of 45,305 MWh
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 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.
Statistic GT #1 GT #2 ST #1 CC Block
Period MWh 167,400 167,400 193,440 528,240.00
Forced Outage MWh 281.25 1,968.75 0 2,250.00
Planned Outage MWh 38,868.75 40,050.00 45,305.00 124,223.75
Maintenance Outage MWh 0 0 0 0.00
Reserve Shutdown MWh 27,337.50 48,281.25 24,091.60 99,710.35
Service MWh 100,912.50 77,100.00 124,043.40 302,055.90
Equiv. Forced Derated MWh 180.00 180.00 1,485.90 1,845.90
EFDH During RS MWh 0 0 162.50 162.50
Equiv. Sched. Derated MWh 0 0 0 0.00
Net Actual Generation 100,000 77,000 124,000 301,000.00
Attempted Starts 6 7 4 17.00
Actual Starts 5 7 4 16.00
There are number of differences between the GADS national database and those databases
collected by the different Independent System Operators (ISO) organizations. Some are minor
changes and some are not. Since GADS is still a voluntary database, there are no obligations for
the ISOs to follow GADS rules and procedures 100%.
GADS collects equipment outage data on a national and international basis. GADS is an
equipment outage system with new ties to reliability assessments. However, it is very important
that GADS have uniformity in data collection. Meanwhile, the ISOs work in a marketing arena,
different than GADS. As a result of the differences between the ISO and GADS, it is important
to distinguish what differences exist.
These differences listed below are not in any specific order and may not cover all differences.
However, the list will present major items for discussion.
When Data is Due. In the GADS Data Reporting Instructions, we asked that utilities report
dated to GADS within 30 days after the end of each quarter year. However some companies
prefer to report their data to us on a monthly basis, at the same time some ISOs require.
GADS will accept the data either on a quarterly or monthly basis.
Amount of Data Due. GADS strongly requests that all data be sent to GADS on a year-to-
date basis. This would mean that if you are reporting for the month of September, then you
would report all data between January and September to GADS at the end of September.
This allows the databases at both the reporters facilities and GADS to be exactly the same.
If we only allowed data to be reported on a monthly basis, than any changes to the database
from earlier months would be lost at the GADS level.
We also allow updates or modifications to historical data be reported to GADS so that again
all historical data (i.e., earlier years) at the reporting facilities and at GADS would have the
same data. We encourage all ISOs to do the same thing so that uniformity will always be
between reporter and those who receive the data.
Record Formats. For many years the GADS data was collected in 82 character 97-95
format. The old record formats have been accepted since 1982 and were discontinued in
January 2010. The primary distinction of the old formats is to allow collection of data as
whole numbers and not fractions of hours, capacities, or generation. In recent years GADS
started to collect the data in a new format where reporters can report hours, capacities and
generation data out to two decimal places. The purpose of the two decimal places is to allow
more accuracy in reporting as per ISO request. It was not the purpose of GADS to allow
reporting of very small generating units. We normally do not collect units less than 1 MW in
size. However some smaller units have been reported to GADS and we do accept them into
the database.
Edit Checks. There are a number of data checking programs in GADS to insure the event
and performance records correspond correctly. These checks are made available to the
developers of all software programs. We check each event and performance record before it
is allowed into the GADS database. A list of the checks is available to anyone interested in
the editing process. ISOs also check their GADS data per their own specification for
accuracy. Many checks are identical between the two databases.
One leading characteristic is called base-loaded. The term base-loaded can mean different
things to different people. GADS does not set specific limits of what is base-loaded and what
is not a base-load unit. We do not state that there are no reserve shutdowns for base-loaded
units but GADS assumes that the majority of the time, the unit is up and operating at close to
its maximum capacity. Some ISOs state that if a unit has any RS events, then it is not base-
loaded. In GADS, such units can be considered base-loaded. There is not a definition of
base-loaded in the GADS Data Reporting Instructions.
Daylight Savings Time. Prior to 2005, daylight savings time started and ended during the
month of April and October, respectively. Starting in 2006, daylight savings time changed to
March and November. The GADS program recognizes these months as a beginning and
ending is daylight savings time. It also allows states such as Indiana and Arizona who do not
have daylight savings time report the full number of hours per month as standard operating
times.
Dominant Derates. Dominant derates were added to the GADS database several years ago.
The purpose of the dominant derates was to track the full impact of major equipment
problems when more than one equipment failure with the same time period. If more than one
derates occurs at the same time, then the operator must decide if either one of these derates is
dominant or not.
Some ISOs did not recognize dominant derates because they fear that forced derates may be
shadowed by other non-forced derates due to the dominant derates application. GADS
recognizes that this problem may occasionally occur. However, GADS still strongly
encourage the use of dominant derates for recording specific equipment failures at power
plants.
OMC Events. Outside management control or OMC events were introduced to GADS about
2004. The purpose of the OMC events is to identify problems that happen at power plants
which are outside the control of plant management. These events include such things as
transmission problems, ice storms, tornadoes or other events caused by the weather,
terrorists, or other outside elements. The list of 36 OMC cause codes that are recognized by
GADS is in Appendix K of the GADS Data Reporting Instructions.
These OMC events were taken from the Europeans and have been accepted by many
companies in the USA.
GADS recognizes that ISOs also have a group of OMC events they consider as part of
outside management control. GADS is an equipment database; ISOs work in a marketing
environment. Therefore, the focus of each group is different and the OMC's accepted by each
group may be different.
Removal of OMC Events. When GADS removes an OMC event from its calculations, it
removes the event hours and reduces the event count (forced, maintenance, planned outage or
derate) by one. If the OMC is an outage, it also reduces the number of actual starts by one
and reduces the number of attempted starts by one. In this way, we remove all traces of the
OMC event - as if the OMC event never occurred. A full description of the removal process
is described in appendix K of the GADS Data Reporting Instructions.
Some ISO groups will recognize certain OMC events and will remove the event and reduce
the event count by one but will not modify the number of actual or attempted starts. This is a
decision the ISO makes for its own purposes. The number of actual and attempted starts has
little or no impact on EFORd calculations if the differences are only 1 or 2 different.
EFORd. Equivalent Forced Outage Rate Demand (EFORd) was added to IEEE 762 in 2007.
However this equation has been used by PJM Interconnection and the Canadian Electricity
Association (CEA) for many years. It is not used by all ISO organizations as a measure of
reliability and dependability. GADS started calculating this number about 10 years ago and
adding it to our software and other reports. GADS follows the IEEE 762 formula for
calculating EFORd.
There are three methods for pooling or grouping EFORd. These methods are shown on page
59 through 64 of IEEE 762. The same calculating methods are shown in GADS Data
Reporting Instructions Appendix F. GADS uses the hourly weighted methods (method 2)
because it conforms to the other calculations used in IEEE 762. Some ISOs use capacity
weighted average methods (Method 3). Both are accepted by IEEE 762 but have different
results.
Synchronous and Pumped Storage Starts. In GADS, we encourage the reporting of unit
starts each time the unit is either in synchronous condensing or pumping mode. Although
these are not generating operations, they still cause stress and strain on the equipment where
the equipment can fail. GADS encourages that such starts and attempted starts be reported.
Some ISOs require that their members report synchronous condensing and pumping hours are
event types like GADS requires for forced, maintenance and planned outages and derates.
GADS does not recognize synchronous condensing and pumping events. GADS asks for the
number of hours in each operation each month but not the dates and times each operation
starts and end.
Run-of-river Hydro Units. GADS has collected data on fossil and nuclear units for many
years. However, starting as early as 1982, GADS started to receive data from hydro units.
Although hydro generation is less expensive, it works under different conditions than other
generating units. Therefore, these units must be treated a little bit different than the typical
generating plant.
Please note that GADS continues to collect information on equipment problems. However
since NERC became the new ERO for the United States in July 2006, we've been asked to
provide data as part of the reliability assessments and help in the projection of new power to
meet the demands of the consumers. Therefore it is very important to keep track of all power
plants and their capabilities throughout the year, no matter what type of power plant they are.
That includes run-of-river hydros too.
Here are special rules that GADS suggests for hydro units. This is GADS opinion only for
use on a national basis; each ISO will set the rule for hydro units within their jurisdiction.
All generating units of all MW sizes are invited to be part of GADS. We do not limit
small units from participating in a database. However it is not the purpose of GADS
to collect very small units (less than 1 MW). If generating companies wish to report
small units to GADS, than these units will be welcomed into the database
We have set up certain rules for collecting reserve shutdowns for hydro units. There
are some hydro units that collect reserve shutdown (RS) periods using an automatic
SCADA system. Such unit should report each and every RS event. However units
that do not have SCADA equipment can either report RS events like those with
SCADA systems or simply report the total number of RS hours per month on the
GADS performance record. The option is up to the reporter.
Each and every event that prevents a unit from generating 100% full load must be
reported to GADS. This includes equipment failures, RS times, and any other
incident at the plant including when there is insufficient water available to generate to
maximum capability.
Some run-of-river hydro units report lack of water periods as an RS event. That is not
correct! The reason is that the unit cannot operate at full capacity because it is out of
fuel. It should be reported as a forced outage. However, this out-of-fuel event is
also an OMC event in the eyes of GADS. Therefore, it should not be declared as a
penalty against the hydro plant but should be recognized as a standard condition and
credited out of the EFORd calculation just like the ISOs remove transmission events
from the calculation of EFORd. When GADS calculates EFORd, it includes all OMC
events. When it calculates XEFORd (EFORd without OMC events), it excludes out
of water conditions.
Debris in the water intake (leaves, tree branches, etc) from the river, lake or streams is
not OMC events but is normal problems with hydro units. They should be reported as
forced, maintenance, or planned events.
Insofar as the equipment at a hydro station is capable of full load but not generating
full load due to water conditions, it should not experience an EFORd reduction until
the reason for the water condition is properly identified. Once the condition or
decision for reduction is identified (be it lack of water, conservation of water or other
reasons), then the decision affecting EFORd (include or exclude the event) can be
made properly.