Transmission Availability Data Transmission Availability Data System (TADS) UpdateSystem (TADS) Update
July 22, 2008Reliability, Risk, and Probability Applications SubcommitteeIEEE PES Meeting in Pittsburgh, PA
John Seelke, NERC ([email protected])
2
Presentation Scope
We will answer these questions:
Why TADS is needed?
How TADS was developed?
What transmission facilities are included in TADS?
What outage information does TADS collect?
For TADS information, see http://www.nerc.com/filez/tadstf.html
3
Why TADS Is Needed
No systematic transmission outage data collection effort exists for all of North America
Energy Information Administration data (Schedule 7 on Form 411) is voluntary and of no use to NERC
• EIA proposed to make Schedule 7 mandatory in 2008 for 2007 data collection
TADS data is intended to provide data for improving planning and operating standards
• Will help define credible contingencies (Phase I) TADS will provide a partial measure of bulk power
system performance
44
Phase I and Phase II TADS
Phase I (approved by NERC Board for 2008 collection) Automatic Outages only – Momentary and Sustained Elements
• AC Circuits• DC Circuits• Transformers• AC/DC BacktoBack Converters
Phase II (anticipated for 2009 collection) NonAutomatic Outages – Planned and Operational Same Elements Consideration of +/ 100199 kV DC Circuits (not recommended
– only one circuit)
≥ 200 kV
5
Phase IAutomatic Outages
6
Phase I TADS Schedule
Activity
July 20, 2006 NERC became the “electric reliability organization
Oct. 24, 2006 TADS Task Force formed under the NERC Planning Committee
Oct. 23, 2007 NERC Board of Trustees approved mandatory collection of TADS Phase I data from U.S.
Transmission Owners in 2008
Jan. 2008 Open Access Technologies International selected for data entry and analysis. Their product is
webTADS
June 30, 2008 1st Quarter 2008 data submitted by ~ 190 Transmission Owners
7
Phase I Data Categories
Multiowner facilities are identified to ensure one Transmission Owner (TO) is responsible for reporting data
Element Inventory Data• Average number of Elements installed/year,
weighted for additions and retirements• For circuits, Circuit Miles and MultiCircuit
Structure Miles
Outage Data (next slide)
8
Phase I Outage Data
For each AC Circuit Outage…
Similar data collected for other Elements
continued….
continued….
continued….
9
Phase I Event ID Code Data
An Event ID Code.
• An Event is a transmission network incident that results in the Sustained or Momentary outage of one or more Elements.
• Each TO will assign its own Event ID Code, with the reporting year appended to it. Regional Entities and NERC will assign common Event ID Codes if outages affect two or more TOs.
10
Phase I – Basic Metrics
11
Phase I – Basic Metrics (cont’d)
12
Phase IINon-Automatic Outages
13
Non-Automatic Outage Definition
NonAutomatic Outage (Phase II)
An outage which results from the manual operation (including supervisory control) of a switching device, causing an Element to change from an InService State to a not InService State.
Compare with….
Automatic Outage (Phase I)
An outage which results from the automatic operation of a switching device, causing an Element to change from an InService State to a not InService State. A successful AC singlepole (phase) reclosing event is not an Automatic Outage.
14
Non-Automatic Outage Categories
Planned Outage
A NonAutomatic Outage with advance notice for the purpose of maintenance, construction, inspection, testing, or planned activities by customers or other third parties that may be deferred. Outages of TADS Elements of 30 minutes or less duration resulting from switching steps or sequences that are performed in preparation of an outage of another TADS Element are not reportable.
Operational OutageA NonAutomatic Outage for the purpose of avoiding an emergency (i.e., risk to human life, damage to equipment, damage to property) or to maintain the system within operational limits that cannot be deferred.
15
Non-Automatic Outage Cause Codes
Planned Outage Cause Codes1. Maintenance & construction, including testing2. Third party requests (highway dept., Coast Guard, etc.)3. Other (includes human error)
Operational Outage Cause Codes1. Emergency2. System Voltage Limit Mitigation3. System Operating Limit Mitigation, excluding System
Voltage Limit Mitigation4. Other (includes human error)
16
Phase II Outage Data
For each AC Circuit Outage…
Same format as Phase I
Similar data collected for other Elements
continued….
continued….
17
Phase II – Basic Metrics
18
Phase II – Basic Metrics (cont’d)
1919
Phase II Approval Schedule
Dates (2008)
Mar. 1213
April 4
April 30
Late August
Sept. 1011
October 28
Early November
Activity
PC approved Phase II preliminary report.
TF prepared a data request under Section 1600, which NERC submitted to FERC >21 days prior to posting.
TF posted data request, soliciting comments for 45 days. Comments were due on June 16, 2008
TF issues final Phase II report, considering comments received
PC review/approval of Phase II final report
NERC Board of Trustees review/approval of Phase II for mandatory implementation in 2009
Begin implementation
2020
Questions
