JUNE 5, 2012 | HOLYOKE, MA

Power Generating Availability

Data System (GADS)
Software Training
Customer Training Web Conference

Wing Cheng
Disclaimer for Market Training

• ISO New England (ISO) provides training to advance

participant and stakeholder understanding of the markets.
• Since not all issues and requirements are addressed by the
training, participants and other stakeholders should not rely
solely on this training for information but should consult the
effective Markets, Services, and Transmission Tariff (Tariff) and
the relevant Market Manuals, Operating Procedures and
Planning Procedures (Procedures).
• In case of a discrepancy between training provided by ISO and
the Tariff or Procedures, the meaning of the Tariff and
Procedures shall govern.

2
Before We Begin

• Presentation available on the ISO New England (ISO-NE)

web site: Support > Training > Training Materials >
Generating Availability Data System (GADS)
– WebEx recording of this session will be posted to the location above
within five business days
• General WebEx usage
– Interactivity
– Questions and answers
• Evaluation

3
Customer Support

• Phone: 413-540-4220
– Recorded/monitored conversations
• Ask ISO
– Self-service interface for submitting inquires
– Accessible through the SMD Applications Homepage
• Requires a valid digital certificate with the role of Ask ISO/External User
– Contact your Security Administrator for assistance

• Email: custserv@iso-ne.com
• Fax: 413-535-4156
– Regular Business Hours
• Monday through Friday, 7:30 A.M. to 5:30 P.M. Eastern Time

4
 Note: Your phone or computer audio has been
muted so that audio quality is maintained. Please
communicate via the Chat or Q&A windows.

Chat

• If you experience technical issues with WebEx, send a

message using the Chat panel available on the right side of
your screen

2
1
Click Send to
Type your message deliver message
in the space provided

5
 Note: Your phone or computer audio has been
muted so that audio quality is maintained. Please
communicate via the Chat or Q&A windows.

Q&A

• To expand the Q&A window, click the Q&A button located at

the top-right of the screen
• If you have questions regarding content, use the Q&A panel
available on the right side of your screen

1 Select All Panelists

from the Ask field
3
2 Click Send to
deliver message
Type your question
in the space provided

6
June 2012

ISO-NE
PowerGADS Training

7
 PowerGADS Training Agenda

Part I: GADS Data Review

• Event and Performance Data
• Submission Procedure and Format
• Divergence between ISO-NE and NERC GADS

Part II: Introduction to the Software Tool

• Data Submission
• Data Entry, Review and Modification
• Data Validation – Level 2 Validation
• Report Creation

Q&A session will be available after each topic

8
 PowerGADS Training

Part I: GADS Data Review

9
 PowerGADS – Performance & Reliability System

Generating facilities that are 5MW or greater and have cleared as a capacity
resource in the ISO-NE market are required to submit GADS event and
performance data to determine the generator’s Equivalent Forced Outage
Rate on Demand (EFORd) for use in capacity planning and reliability studies.
Member companies have the option to designate ISO-NE as the Delegated
Reporting Entity to submit the collected data to NERC thereby complying with
the NERC data submittal requirements.

NERC

Generators

10
 PowerGADS – Data To Be Collected

Three types of data are to be collected:

Event Data

Each time a unit experiences a change in operating status or capability,

an event is recorded. From these event reports a unit’s operational
history can be reconstructed.

Generation Performance Data

A unit’s actual generation, hours of operations and operational

characteristics

Fuel Performance Data

A unit’s actual fuel consumption and fuel quality

11
 PowerGADS – Event Data

Event data are to be collected:

• Event Number
• Event Type
• Start of Event
• End of Event
• Net Available Capacity
• Primary Cause and Contribution Code
• Secondary Cause and Contribution Code (Up to 48)
• Verbal Description
• Amplification Code

• Failure Code (Optional)

• Time Work Started (Optional)
• Time Work Ended (Optional)
• Man-hours Worked (Optional)

12
 PowerGADS – Unit Status – Active States
Active

Available (Zero to Full Load) Unavailable (No Load)

Reserve Shutdown In Service

Non-Curtailing
Planned Derate Unplanned Derate Planned Outage Unplanned Outage
(NC)

DP PO PE
PD
(Extension) (Extension)

DM ME
D4 MO
(Extension) (Extension)

D1 D2 D3 U1 U2 U3 SF
Immediate Within 6 Hrs Before Next Immediate Within 6 Hrs Before Next Start Failure
Monday Monday

13
 PowerGADS – Unit Status – Active States

Derate Events

D1: A forced derate that requires an immediate reduction in capacity

D2: A forced derate that does not require an immediate reduction in capacity but
requires a reduction within six hours
D3: A forced derate that can be postponed beyond six hours but a reduction
needs to take place before next Monday
D4: A maintenance derate that can be scheduled on or beyond the next Monday
PD: A planned derate that is scheduled well in advance and is of a predetermined
duration
DM: An extension of a maintenance derate beyond its estimated completion date
DP: An extension of a planned derate beyond its estimated completion date

14
 PowerGADS – Unit Status – Active States
Outage Events
RS: Unit is available for load but is not synchronized due to lack of demand
U1: A forced outage that requires an immediate reduction in capacity
U2: A forced outage that does not require an immediate reduction in capacity but
requires a reduction within six hours
U3: A forced outage that can be postponed beyond six hours but a reduction
needs to take place before next Monday
SF: An outage that results when a unit is unable to synchronize within a specified
startup time following an outage or Reserve Shutdown
MO: A maintenance outage that can be scheduled on or beyond the next Monday
PO: A planned outage that is scheduled well in advance and is of a
predetermined duration
ME: An extension of a maintenance outage beyond its estimated completion date
PE: An extension of a planned outage beyond its estimated completion date

15
 PowerGADS – Unit Status – Inactive States
Inactive

IR MB RU
Inactive Mothball Retired
Reserve Unit

Inactive State: A unit that is idle for a lengthy period of time and some action may be
needed to prepare it for service due to equipment deterioration or
needing replacement. This preparation measures typically in days.
Additionally the unit must be on RS a minimum of 60 days before it
can move to IR status.

Mothball: A unit that is idle for a lengthy period of time due to obsolescence or
experiences with mechanical problems for which management may
wish to wait to determine if the unit should be repaired or retired. A unit
that is not operable then it 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.

16
 PowerGADS – Common Errors

Typical Errors to avoid:

• All Events are required

• While derates may overlap, outages do not overlap (RS, U1, U2, U3, SF, MO, ME,
PO, PE, IR, MB)
• Derates and Outages may overlap
• The available capacity specified in a derate event must be less than the Net
Dependable Capacity reported in the 05 data and it should be greater than zero. If
the available capacity of a derate event is greater than the Net Dependable Capacity
then it should be reported as a non-curtailing event (optional)
• Cause Codes are published by NERC and are unit type specific. Appendix B1 to B10
of the NERC GADS Data Reporting Instruction (DRI) contains a list of all the valid
cause codes for each unit type
• Observe daylight saving hours from March through October

17
 PowerGADS – Common Errors
500
Derate #1
Capacity 400 Derate #2
(MW)
300

200

100

t1 t2 t3 t4
The available capacities of derate events must decrease as additional overlapping derates are
submitted with later start date. In the example above, Derate #2 should not be submitted as a
separate event.
The user has three options:
1) The user may choose not to report Derate #2
2) The user may choose to report Derate #2 as a non-curtailing (NC) event
3) The user may choose to report the problem of derate #2 as a secondary cause of derate #1
Option 3 is the recommended method as cited in example #4 of Appendix G (Example and
Recommended Method) of the NERC DRI

18
 PowerGADS – Common Errors
500
Derate #1 Must
Capacity 400 Derate #2 Report
(MW)
300

200

100

t1 t2 t3 t4
Note: If Derate #2 ends beyond the end of Derate #1 then the portion of Derate #2 that is beyond
the end of Derate #1 must be reported as a separate event (t3 to t4)

19
 PowerGADS – Event Transition
Event Transition refers to the scenario when events occur in succession, i.e. the event start
date-time of one event coincides with the event end date-time of another event. There are
rules governing which types of event can be transitioned into other types of event.

This table was

copied from Figure
III-6 of Section III-
Event Reporting of
the NERC DRI

20
 PowerGADS – Amplification Code

Amplification code submission is mandatory starting January 2011.

• Forced Outage Event Type U1 can be further specified as “T1” and “T2”
(automatic vs. manual) using the Amplification Code.

• Forced Derate Event Type D1 can be further specified as “82” and “83”
(automatic vs. manual) using the Amplification Code.

Amplification Code submission requirements – REVISED – January 2012:

“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 appropriate amplification
code if the reporter chooses to report amplification codes”.

21
PowerGADS – Event Data

Derated Available Capacity in

PowerGADS is always Additive

22
Example of Additive Derating Events:
Event #1: A 100 MW load reduction due to a feedwater heater inspection. The inspection had been planned earlier.
Event #2: A 200 MW due to excessive pulverizer vibration. Available Capacity changed from 600 MW to 400 MW as a
result. A foreign object was the cause.

Capacity (MW)
700
Event #1
600

500
Event #2
400

300
Event 1 ended after Event 2 ends

Capacity (MW)
700
Event #1
600
Event #2
500

400

300
Event 1 ended before Event 2 ends

23
Example of Independent Derating Events:
Event #1: A circuit breaker tripped causing an immediate 100 MW load reduction
Event #2: A traveling screen jammed causing one of the unit’s circulating water pumps to shutdown

Event #3
Capacity (MW)
700
Event #1
600
Event #2
500

400

300

After the problem with the circuit breaker in event #1 is fixed, the unit continues to experience the
circulating water pump problem which maintain the available capacity at 400 MW. To indicate this
situation, the user needs to terminate Event # 2 when Event # 1 ended, and enter Event # 3 to keep the
available capacity at 400 MW.

24
 PowerGADS – Generation Performance Data
• Net Maximum Capacity
• Net Dependable Capacity
• Net Actual Generation
• Typical Unit Loading Code
• Loading Verbal Description (If Typical Unit Loading Code is 6)
• Attempted Unit Starts
• Actual Unit Starts
• Unit Service Hours
• Reserve Shutdown Hours
• Pumping Hours
• Synchronous Condensing Hours
The rest of data items specified in the NERC 05 format are recalculated by PowerGADS using event data

• Available Hours
• Planned Outage Hours
• Forced Outage Hours
• Maintenance Outage Hours
• Extension of Scheduled Outages
• Unavailable Hours
• Period Hours
• Inactive Hours

25
 PowerGADS – Fuel Performance Data

Data can be submitted for up to four types of fuel

• Fuel Type
• Quantity Burned
• Average Heat Content
• Percent Ash
• Percent Moisture
• Percent Sulfur

Primary fuel type is required.

26
 PowerGADS Training

Questions and Discussions on

Event and Performance Data

27
 Data submission Process

Data to be submitted must be prepared in one of these standard formats:

• NERC 05 and 07 (recommended)

• PowerGADS CSV

WWW

28
 System Lockout
Members are free to manipulate the current month’s event and performance data
up to the twentieth day of the following month. After that day, the system will not
accept any insertion, deletion or modification to the data.

For performance data, the lockout criterion is determined by the Year and Month
specified in each record. For example, March 2012 data is locked as of April 21st
2012.

For event data, the lock out criteria is determined by the year and month fields of
the Event Start Date. This means members can only insert or update events that
were started during the reporting month. The only exception allowed is to close an
open event that started in an earlier month.

The ISO-NE GADS administrator has the ability to unlock the system for the
members to perform update.

29
 NERC 05-07 Format
If the data are to be submitted using the NERC format, the following rules must be
observed:

• Only 05 and 07 formats are accepted. The 95 and 97 formats are imprecise and
obsolete.

• 05 and 07 records must be submitted within a single, combined file (unlike OATI’s
requirement)

• Each submission file must contain one performance record per unit-month submitted.
There may not be an event record if a unit was online the entire month without incident.

• Following the NERC convention, each month’s submission may contain YTD data.
However, previous month’s data may not be modified if the lock imposed by the
administrator is in effect. The only exception is to close an on-going event that started in
a previous month.

• YTD data must be submitted using revision code 0.

• Follow the file specifications published in the NERC GADS Manual

30
 NERC 05-07 Format Comparison Logic

Event 1 Event 1 Update Event 1

Event 2 Event 2 Update Event 2

Event 3 Delete Event 3

Event 4 Event 4 Update Event 4

Event 5 Insert Event 5

First Submission Second Submission

PowerGADS performs a record-by-record comparison between the data being

submitted and the data already stored in the system. This comparison will determine
what action the system will take with each record.

31
 PowerGADS Training

Questions and Discussions on

Submission Procedure and Format

32
Divergence
between
ISO-NE
and
NERC GADS

33
Divergence between the ISO-NE and NERC GADS

Reason:
ISO-NE and NERC have different objectives and usages
of the GADS data.
While NERC’s application is more benchmarking
oriented, ISO-NE is focused on reliability analyses and
ensuring resource adequacy.

34
Divergence between the ISO-NE and NERC GADS

Differences:
• Net vs. Gross Capacity
• Calculation of Equivalent Hours
• Cross-Year Events
• Validation on Overlapping Derates
• EFORd Calculation

35
 Net vs. Gross Capacity

NERC:
Accepts and applies both gross and net capacity

ISO:
Accepts both, but applies only net capacity
Note: If Gross is submitted, the following NERC rule must be
observed.
“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”

36
 Calculation of Equivalent Hours

NERC:
Eq. Hrs = (Duration of Derate) X (Size of Reduction)
Net Maximum Capacity

ISO:
Eq. Hrs = (Duration of Derate) X (Size of Reduction)
Net Dependable Capacity

Size Of Reduction = determined by subtracting the Net Available

Capacity (NAC) from the Net Dependable Capacity (NDC)

37
 Cross-Year Events

NERC:
Events must end at the end of the year

Feature of PowerGADS:
Events can stay open across different years

38
 EFORd Calculation
EFORd = ( FOH x f ) + ( EFDH x fp) x 100%
SH + ( FOH x f )

fp=Partial F-Factor = (SH+Synch Hour+Pump Hour / AH)

f =F-Factor = (1/r + 1/T) / (1/r + 1/T + 1/D)
r=Average Forced outage deration = (FOH) / (# of FO occurrences)
D=Average demand time = (SH+Synch Hour) / (# of unit actual starts)
T=Average reserve shutdown time = (RSH) / (# of unit attempted starts)

Limiting SH FOH RSH NERC EFORd ISO EFORd

Conditions
Base >0 >0 >0 Applicable Applicable
1 0 >0 >0 Cannot be f=1
determined
2 0 0 >0 Cannot be f=1
determined
3 0 >0 0 Cannot be f=1
determined
4 >0 0 >0 EFDH/AH 1/r = 0

5 >0 0 0 EFDH/SH f=1

6 >0 >0 0 EFOR f=1

7 0 0 0 Cannot be f=0
determined

39
 PowerGADS Training

Questions and Discussions on

Divergence between ISO-NE and NERC GADS

40
 PowerGADS Training

Part II: Introduction to the Software Tool

41
 PowerGADS Access Requirements

Software Requirements

• Java 1.5 or higher is required

• Internet Explorer 5.x and above

URLS for Accessing PowerGADS

Sandbox
• iso-ne_test.powergads.com
Production
• iso-ne.powergads.com

42
 PowerGADS Password Requirements

• The temporary password expires immediately after the user’s first successful
login

• The user must supply a new password at least 8 characters in length, containing
at least one numeric, one alpha and one non-numeric non-alpha character

• Password is invalidated after three failed attempts to log into the system

• The ISO-NE Administrator can reset the password

• The password expires every 90 days.

• The latest expired password cannot be used as the new password.

• Both the user ID and the password are case sensitive.

43
Use Menu to Navigate
between screens

44
 Data Submission
2

1) Access the “GADS Data

Import” screen from the
Operation Data Menu
2) Select the file format to
be used
3) Click “Import File”
4) Locate the file containing
the data to be submitted
5) Click “Import Card”

45
 Data Submission
2

1) View the errors

found in the
submission data
2) Click the “Edit
Submission Data”
button to make
changes

46
 Data Submission

1) Select the tab to 3

locate the problem
2) Right-click on the
entry that has error to
view the error
message. Edit
changes in the field to
make corrections
3) Click on “Re-
Submit”

47
 Data Submission

1) A pop-up screen
will alert the user
that the submission
is successful
Note: It is important
to remember that
this is an “All or
Nothing” import. If
you do not see this
message, it means
non-of the data was
saved

48
 Data Review Using Cards View
1 2

5
1) Access the “Card 95
Performance” screen
from the Operation Data
Menu
2) Select the year, month,
utility and unit
3) Click on “Retrieve”
4) Click on the record to
be edited
5) Click on “Update” to
modify the record

49
 Data Review Using Cards View

1) Make changes where

necessary
2) Click on “Save” to save
the changes

The review and edit

process is similar 2
when using the Card
97 Event and Card 99
Fuel screens.

50
 Data Review Using Monthly View
1 2

1) Access the
“Monthly Operation
View” screen from
the Operation Data
Menu 6
3
2) Select the year,
month, utility and unit
4
3) Click on “Retrieve”
4) Click on Daily
Detail to review daily
data 5

5) Review or Edit
Performance Data.
After editing the
performance data,
click on the “Save”
button to the right
6) To Edit the data,
Double-click on the
event or Right-Click
on an event entry
6

51
 Data Review Using Monthly View

When the Event Data

screen pops up, make
changes where
necessary, then click
on the “Save” button.

52
 Data Review Using Monthly View

To add a new event,

right-click on the
graph and choose the
event type to be
added. The Event
Data panel will appear
to enable data entry.

53
 Level 2 Validation
1
The Level 2 Validation
screen allows the user to
execute level 2 validations.
It is the member
company’s obligation to
get all its data validated
before the 20th day of the
month for the previous
month.

1)To perform the

validation, the user selects
a year, a month, and a unit
or multiple units.

2) Click on “Run Check” 2

3) If error is encountered 3
during the validation, an
error log is displayed on
the screen. The error
messages are color coded
depending on the severity.

Fatal errors are colored

red. Warnings are colored
yellow. Notes are colored
white. Notes are
information that are
important to the users but
do not indicate problems
of any kind.

54
 Generating Reports
To run a report, access the
Report screen under the
Report menu.
Select a Report and fill in the
criteria.
Vertical Format generates
report in easy to read and print
style.
Horizontal Format generates
report in spreadsheet-friendly
style.
The “Generate in PDF
Format” and the “Generate in
CSV Format” button will create
a report while you wait.
The “Generate in
Background” button generates
a report while you perform
other tasks.
To view the completed
report, use the “Completed
Reports” screen under the
Report Menu.

55
 Ad Hoc Reporting

2 3 4
A user may use the Ad
Hoc Metrics Reports
dashboard to create
custom reports. To
start, a user must: 1

1. Select Date Range or

Custom Date Range
from the drop down
menus.

2. Select NERC or PJM

radial dial button

3. Click on Include
OMC to check box

4. Select Excel or PDF

radial dial buttons

56
 Ad Hoc Reporting
1)Click on the Selected Data
Items button. Pop up screen
appears with metrics.

2)If there is a drop down

menu of previously created
custom groups. Select one to 3
view the metric contents of a
particular group.Custom
metrics will appear in the text
box on the right side of the
screen

3)Add or Unselect metrics by

selecting the Select or
Unselect buttons in the center
of the screen. Selected
metrics will appear on the text 1
box on the right side of the
2
screen, or remove by putting 4
them back in the left list.

4)The user can change the

position that a metric will
appear in a report by using
the Up or Down buttons on
the upper right hand side of
the screen.

5)If a user wishes to use a

particular combination of
metrics more than once, he or
she may "Save as Group" or
click "OK" for one time use.
5

57
 Log Out

If the user does not

logout properly, the
system will be
inaccessible for up to
five minutes.

58
 PowerGADS Training

Questions and Discussions

59
60