Workshop Session 2: Forms

Transmission AvailabilityData System (TADS)

TADS Workshops: January 16, 2008 and February 6, 2008 - UPDATED

Workshop Session 2: Forms

2

TADS Forms Overview

● Administrative Forms with Transmission Owner Information

● 1.1 Non-Reporting Transmission Owner Statement● 1.2 Reporting Transmission Owner Information● Forms for Ties & Jointly-Owned Facilities● 2.1 Tie Lines and Jointly-Owned AC and DC Circuits● 2.2 Jointly-Owned AC/DC Back-to-Back Converters● Forms for Element Inventory and Summary Outage

Data● 3.1 AC and DC Circuit Inventory Data● 3.2 Transformer Inventory Data● 3.3 AC/DC Back-to-Back Converter Inventory Data ● 3.4 Summary Automatic Outage Data● Forms for Detailed Element Automatic Outage Data● 4.1 AC Circuit Detailed Automatic Outage Data● 4.2 DC Circuit Detailed Automatic Outage Data● 4.3 Transformer Detailed Automatic Outage Data● 4.4 AC/DC Back-to-Back Converter Detailed Automatic Outage Data● Form for Event ID Code Data● 5 Event ID Code and Event Type No. Data

3

Form 1.1 Non-Reporting TO Information

4

Form 1.1 Non-Reporting TO Information (cont’d)

● If a non-reporting TO adds TADS facilities during the reporting year, it is required to report on those facilities in that year.

5

Form 1.2 Reporting TO Information

6

Form 1.2 Problems Encountered

● We added pseudo NERC IDs for three TOs for TADS only PSD00001: Southern Company Transmission (in SERC) to be

used instead of their five registered NERC IDsNERC ID Company NameNCR01166 Alabama Power CompanyNCR01247 Georgia Power CompanyNCR01252 Gulf Power CompanyNCR01273 Mississippi Power CompanyNCR01322 Southern Power Company

PSD00002: AltaLink Management Ltd. – An unregistered Canadian TO in WECC who will voluntarily report

PSD00003: ATCO Electric – An unregistered Canadian TO in WECC who will voluntarily report

PSD00004: ITC Midwest LLC – purchased the transmission of Alliant West. They have applied for NERC registration.

ITC Midwest LLC is registered with NERC ID NCR10192

7

Form 1.2 Reporting TO Information (continued)● The forms status table accounts for all forms for reporting

TOs

Form No. Short Form Name Submission Status Reason Not Submitted1.2 TO Info Submitted Must be submitted2.1 Tie Lines and Joint AC/DC Ckts Submitted NA; form was submitted2.2 Joint AC/DC BTB Converters Not Submitted No data of this type3.1 AC/DC Ckt. Inven. Submitted NA; form was submitted3.2 Transformer Inven. Submitted NA; form was submitted3.3 AC/DC BTB Con. Inven. Not Submitted No Elements of this type3.4 Summary Auto. Outage Data Submitted NA; form was submitted4.1 AC Circuit Outages Submitted NA; form was submitted4.2 DC Circuit Outages Not Submitted No Elements of this type4.3 Transformer Outages Not Submitted No Outages4.4 AC/DC BTB Con.Outages Not Submitted No Elements of this type

5 Event ID Codes Submitted NA; form was submitted

8

Form 2.1 Tie Lines and Jointly-Owned Circuits

● Form 2.1 is reported at the start of each reporting year and at the end of each reporting year. 2008 will have three submissions of Form 2.1 because of the

first quarter reporting requirement● The TO that reports outages for joint-owned circuits also

reports the entire circuit length in its inventory● Each DC pole (plus or minus polarity) is a separate DC

Circuit● In an AC Circuit,

Transformers are not part of the circuit In-line switches located inside an AC Substation are part of the

AC Circuit

Will expand to allow for 3-terminal circuits

NERC ID NCR00000

TRE [1]Country US [1]

2008

(A) (B) (C) (D) (E) (F) (G) (H) (I) (J) (K) (L) (M) (N) (O) (P)

Row No.

Type of Circuit (AC or DC) From To Voltage Class

Overhead or Underground

Reporting TO's NERC ID

TO with TADS Reporting

Responsibility

Reporting TO's Element

IdentifierTO#1

NERC ID TO#1 NameTO#2



NERC ID TO#4 Name1 AC Smith Jones 200-299 kV OH NCR00000 ABC P&L ShJs#1 NRC00001 XYZ Power NCR00000 ABC P&L

This form lists all the AC Circuits or DC Circuits that are either (a) tie-lines or (b) jointly-owned facilities and which are ≥ 200 kV. All tie lines in which the TO has an ownership interest, even if owned by one TO, must be reported. To insure that outage data on these Elements are reported, the TO must list each Element, the joint-owners (if any), and the TO that is reporting outage data on the Element.

Names of All Transmission OwnersSubstation/Terminal Name [1]

Form 2.1

Regional Entity:

Transmission Owner (TO): ABC Power & Light Co.NA - 1st submittal

CONFIDENTIAL INFORMATION

Reporting (Calendar) Year:

1. Were tie lines or jointly-owned AC or DC Circuits added during the reporting year?2. If the answer to the question above is "yes," does this Form 2.1 reflect the additions? NA

9

AC Circuit Transformer Exclusion

O

O

O O

A B

C

x

OO

OO

OO OO

A B

C

xO

O

A B

x

OC

OO

O

OO

OO

A B

x

OC

O

OOC

OO

AC Circuit boundaries are defined by the red “arcs” (A, B, & C)

Dashed lines are substation boundaries

Transformer boundaries are defined by the breaker or disconnect switch

10

Sectionalizing Switches

● They are considered “in-line switches,” regardless of location

3 in-line NC switches, 1 NC circuit breaker disconnect

O

O

O O

A B

C

x


OO

OO

OO OO

A B

C

x50 mi. 50 mi.

20 mi.

O

O

O

A B

C

x

O


OO

OO

OO

A B

C

x

OO


50 mi. 50 mi.

Zero mi.

In-line switches are now inside AC Substation C.

AC Circuit boundaries (A, B, & C) are the same, but Circuit Miles are different (120 vs. 100).

11

Form 2.1 Problems Encountered

● Some TOs that jointly-own a circuit are not on the NERC Compliance Registry Example: A customer owns a 345 kV tap off of a registered

TOs circuit, but the customer is not a registered TO. If the customer was registered, this would be a jointly-owned 3-terminal circuit.

The registered TO then has reporting responsibility TO registration of customers and IPPs is before the FERC

● Why report tie lines if they are not jointly owned? Originally thought to be useful for RE review See the Manual, Section 2.1: “Tie lines for TADS purposes

are those AC Circuits (or DC Circuits) that are Elements which connect the AC Substations (or AC/DC Terminals) of two Transmission Owners on the NERC Compliance Registry.”

We will probably drop tie line reporting in the future and just require jointly-owned circuits to be reported

12

Form 2.2 Jointly-Owned AC/DC BTB Converters

● Its similar to Form 2.1, but only requires the reporting of jointly-owned AC/DC BTB Converters

13

Form 3.1 AC & DC Circuit Inventory Data

● In Rows 1-18, the no. of circuits and associated Circuit Miles are adjusted for time in-service of added or retired circuits to properly account for exposure If circuits are added or retired, this data cannot be filed

out until the end of the reporting period Appendix 7 has examples that calculate the “equivalent”

data for no. of circuits and Circuit Miles(A) (B) (C) (D) (E) (F) (G)

Row No. Voltage Class [2]

No. of Circuits (End-of-Year)

Circuit Miles (End-of-Year)

No. of Circuits Added

Equivalent Annual No. of Circuits

Added [3]No. of Circuit Miles for Circuits Added

Equivalent Annual No. of Circuit Miles for Circuits Added [3]

1 200-299 kV AC Overhead 83.0 400.0 8.0 6.2 66.0 55.0

(H) (I) (J) (K) (L) (M)

No. of Circuits Removed

Equivalent Annual No. of Circuits Removed [3]

No. of Circuit Miles for Circuits Removed

Equivalent Annual No. of Circuit Miles for

Circuits Removed [3]

CALCULATED Annual Equivalent No. of

Circuits = B-D+E+I

CALCULATED Annual Equivalent No. of Circuit

Miles = C-F+G+K

3.0 2.1 28.0 21.0 83.3 410.0

14

Form 3.1 AC & DC Circuit Inventory Data (cont’d)

● In Rows 19-25 request AC Multi-Circuit Structure Miles data only We did not define a “circuit” for common structures, so

the no. of circuits is not required• Reminders

• Multi-circuit structures that are occupied by only one circuit do not contribute to the tabulation of Multi-Circuit Structure Miles. Examples:

• A structure designed to have two 345 kV circuits that has only one circuit on the structure does not contribute

• A structure contains a 230 kV circuit and a 138 kV circuit does not contribute since the 138 kV circuit is < 200 kV

15

Form 3.1 AC & DC Circuit Inventory Data (cont’d)

• For common structures that carry circuits owned by different TOs, we expect the TOs to coordinate with each other on their reporting of Multi-Circuit Structure Miles so that no double counting takes place.• As an example, suppose two circuits owned by different

TOs occupy common structures for 10 miles. For this section, the combined number of Multi-Circuit Structure Miles reported by the TOs should not exceed 10. We do not want each TO to report 10 miles since that would double count the miles for the region.

16

Forms 3.2 and 3.3

● Form 3.2 (Transformer Inventory Data) and Form 3.3 (AC/DC Back-to Back Converter Inventory Data) are similar to Form 3.1 for the number of circuits

● For Transformers The Voltage Class is the high-side voltage Do not include spares… only include transformers that

are “in-service” energized and fully connected and that have been declared commercially in service by the TO.

17

Form 3.4

● Contains Automatic Outage summary data

● Columns B and C are self-checks based upon data reported in Forms 4.1, 4.2, 4.3, and 4.4 They may be eliminated in a future TADS update.

● Column D is a number that the TO must derive. Its based upon the number of Elements (AC Circuits, Transformers, etc.) that are “in-service” at the end of the reporting period and which are included in column B on Form 3.1 (AC & DC Circuits), Form 3.2 (Transformers) and 3.2 (AC/DC BTB Converters)

(A) (B) (C) (D) (E)

Row No. Voltage Class [2]

No. of Sustained Outages

No. of Momentary

OutagesNo. of Circuits with Zero Automatic Outages [3]

Calculated Percentage Circuits with Zero

Automatic Outages expressed as %

1 200-299 kV AC Overhead 12 8 41 49.40%

AC & DC Circuit Automatic Outage Data

18

Forms 4.1 - 4.4: Individual Element Outage Data

Data that will be recorded for each outage includes…

● Several Element descriptors. The type of Element. A different Form is used for each

Element. Its location: (e.g., Substation Names that define an AC Circuit

or Substation Name where Transformer is located) The Element’s Voltage Class The TO’s Element Identifier (optional) For AC or DC Circuits, was it an Overhead or Underground

Circuit?

● An Outage ID Code Unique ID assigned by the TO to each specific Element outage

being reported

● An Event ID Code. Data for each Event ID Code is described on slides 31-36

19

Fault Type

● Several selections are available (Updated):1. No fault 2. Phase-to-phase fault (P-P)3. Single phase-to-ground fault (P-G)4. Phase-to-phase-to ground (P-P-G), 3P, or 3P-G fault5. Unknown fault type

● Fault Types may be determined from recorded relay targets or by other analysis. TOs should use the best available data to determine (1) whether a fault occurred and, if so, (2) what type of fault occurred Relay targets should be examined as soon as possible

after a fault and re-set to prepare for the next fault

20

Fault Type (cont’d)

● If a single fault results in several Element outages, the Element’s protective relays that indicated the Fault Type should be indicated on that Element’s outage. Element’s whose relays did not indicate a fault should

be reported as “no fault occurred”

● Example: A 500 kV AC Circuit has a single line-to-ground fault that results in the outage of a 500/230 kV Transformer. The AC Circuit outage would have “ground target” selected as the Fault Type, while the Transformer would have “no fault” selected.

21

Outage Initiation Code

● An Outage Initiation Code that describe where an Automatic Outage was initiated on the power system. Five Outage Initiation Codes are available: Element-Initiated Other Element-Initiated AC Substation-Initiated AC/DC Terminal-Initiated Other-Facility Initiated - any facilities not includable in any

other Outage Initiation Code

● Note: The Protection System is not part of an AC Substation or an AC/DC Terminal. While almost all outages involve the operation of the Protection System, the Protection System is only considered in these codes if the Protection System misoperates and therefore initiates an outage. In this case, it will be classified as Other-Facility Initiated.

22

Cause Codes

● Sustained Outages require two Cause Codes*: An Initiating Cause Code that describes the initiating

cause of the outage. A Sustained Cause Code that describes the cause that

contributed to the longest duration of the outage. (Momentary Outages omit this second code)

Example: A lightning strike on an AC Circuit (the Initiating Cause Code is Lightning) that should have cleared normally became a Sustained Outage because of a relay misoperation (the Sustained Cause Code could be Failed Protection System Equipment or Human Error)

● Seventeen (17) Cause Codes are defined For 2008 an additional code is also allowed

(“Unavailable”)*See 2008 exceptions in the Manual, p.13, column N, and discussed next.

23

Cause Codes – 2008 Exceptions

● All Momentary Outages must supply this code, and the “Unavailable” Cause Code cannot be used for Momentary Outages. Sustained Outages may use the “Unavailable” code in 2008 only for either the Initiating Cause Code or the Sustained Cause Code, but not both. If the TO has the ability to capture Initiating and Sustained Cause Codes, the “Unavailable” code is not to be used.

24

Listing of Cause Codes

1. Weather (excl. lightning)2. Lightning3. Environmental4. Contamination5. Foreign interference6. Fire7. Vandalism, terrorism,

malicious acts8. Failed AC Substation

equipment9. Failed AC/DC Terminal

equipment

10.Failed Protection System equipment

11.Failed AC Circuit equipment

12.Failed DC Circuit equipment

13.Vegetation14.Power system condition15.Human error16.Unknown17.Other18.Unavailable

Definitions of each cause code are included in the Manual, Appendix 6

25

Vegetation Cause Code and FAC-003-1

● It is possible for more Vegetation Cause Codes to be recorded for outages than are reported as vegetation outages under FAC-003-1 (Vegetation Management Program Standard) TADS records Momentary Outages due to vegetation

while FAC-003-1 does not The TADS definition of a Sustained Outage is different

that the Sustained Outage definition in FAC-003-1. Under FAC-003-1, a Sustained Outage is “The deenergized condition of a transmission line resulting from a fault or disturbance following an unsuccessful automatic reclosing sequence and/or unsuccessful manual reclosing procedure.”

For a circuit with no automatic reclosing, a vegetation outage would not be “counted” under FAC-003-1 if the TO has a successful manual reclosing

26

Outage Mode Code

● The Outage Mode Code describes whether an Automatic Outage is related to other Automatic Outages. Several Outage Mode Codes are provided: A Single Mode Outage is an Automatic Outage which occurred

independent of any other outages (if any). A Dependent Mode Initiating Outage is a Single Mode Outage

that initiates one or more subsequent Automatic Outages. A Dependent Mode Outage is one that occurred as a result of

an initiating outage, whether the initiating outage was an Element outage or a non-Element outage.

A Common Mode Outage is one of two or more Automatic Outages with the same Initiating Cause Code and where the outages are not consequences of each other and occur nearly simultaneously (i.e., within cycles or seconds of one another).

A Common Mode Outage Initiating Outage is a Common Mode Outage that initiates one or more subsequent Automatic Outages.

27

Outage Example #1

● A tornado takes down a tower that is a common structure for two 230 kV circuits How many outages are reported? The Fault Type was for one circuit was determined to be

“ground target,” while the Fault Type for the second circuit was “phase target.”

What was the Outage Initiation Code? What was the Initiating Cause Code and the Sustained

Cause Code? What was the Outage Mode Code?

28

Outage Example #2

● A circuit breaker opens due to low gas pressure, resulting in the outage of a 500 kV circuit How many outages are reported? What is the Fault Type? What was the Outage Initiation Code? What was the Initiating Cause Code and the Sustained


29

Outage Example #3

● Insulator contamination causes a fault on a 230 kV AC Circuit, but a breaker on one end fails to open due to a failure of a relay to operate properly. A second 230 kV AC Circuit, which is connected to the same bus as unopened breaker, is outaged as a result of the first circuit’s breaker failing to open. The failed relay was manually isolated, and both lines were returned to service with no other repairs. How many outages are reported? The Fault Type was determined to be “ground target” for

the first circuit, and second circuit did not experience a fault, it’s Fault Type was “no fault.”

What was the Outage Initiation Code? What was the Initiating Cause Code and the Sustained


30

Outage Example #4

● A 345/138 kV Transformer in one leg of a three-terminal 345 kV AC Circuit is outaged due to a 138 kV bus fault caused by contact with a snake. The Transformer and its terminal are isolated, but the other terminals remain in service. How many outages are reported? What is the Fault Type? What was the Outage Initiation Code? What was the Initiating Cause Code and the Sustained


31

Outage Times

● The Outage Start Time - The date (mm/dd/yyyy) and time (hhhh:mm), rounded to the minute, that the Automatic Outage of an Element started Outage Start Time is expressed in Coordinated

Universal Time (UTC), not local time Common time reference will allow REs and NERC to assign

common Event ID Codes to Events that cross TO and RE boundaries

● The Outage Duration (for Sustained Outages only), rounded to the nearest minute. Momentary Outages are recorded as a zero minute

outage duration time to avoid confusion in rounding to the nearest minute

● For outages that continue beyond the reporting period, see Section 4.1 of the Manual

32

Partial Outages

● With one exception, TADS does not recognize partial power flow outages.

● The exception is a three-terminal circuit with a Transformer on one leg.

● If terminal A or B open, an AC Circuit outage is recorded.● The AC Circuit is considered to be restored when partial

power flow is restored on both A & B and the Transformer (TADS or non-TADS) is out-of-service.

O

O

A B

x

OCO

O

O

OO

OO

A B

x

OCO

OOCOO

33

Form 5: 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.

Event Type No.

Table 1 Category

from the TPL Standards

10 B20 B30 C40 C50 NA

(A) (B) (D)

Event ID Code [2]Event Type

No. [3]Disturbance

Report Filed [5]A-2008 10 Don't knowB-2008 20 YesC-2008 10 NoD-2008 10 No

Notes:[1][2]

[3]

[4] Optional input: provide a brief description of the outage (for Event Type No. 50 only). Please limit the description to 500 characters or less.[5] Was an EOP-004 filed at NERC that was associated with the Event? Year-to-date public (i.e., non-confidential) data of all disturbance

report filings are located at http://www.nerc.com/~filez/dawg-disturbancereports.html.

Description of Event Type No. 50 (Other) [4]

See the Table above for Event Type No. Note that if Event Type No. 10 or 20 is selected, the Outage Mode on Forms 4.1, 4.2, or 4.3,(column P) must be "Single Mode Outage." Outages of an AC/DC Back-to-Back Converter (Form 4.4) must select Event Type No. 50.

If a TO owns assets in a different NERC Region or in a different country, provide data for each Region and country in a separate workbook.

Automatic Outage of a DC Circuit with Normal Clearing.Automatic Outage of two ADJACENT AC Circuits on common structures with Normal Clearing.

The Event ID Code must be appended by the reporting year no. (e.g., 2008). For the 1st quarter submissions in 2008, use "2008" and not "2008Q1" since this Event ID Code will be used for the entire reporting year.

Event ID Code Data

Automatic Outage of two ADJACENT DC Circuits on the common structures with Normal Clearing.Other - please describe the event (optional)

Description

Automatic Outage of an AC Circuit or Transformer with Normal Clearing.

(C)

34

Form 5: Event ID Code Data (cont’d)

An Event associated with a Single Mode Automatic Outage will have just one Event ID Code.

Each outage in a related set of two or more outages (e.g., Dependent Mode, Dependent Mode Initiating, Common Mode, or Common Mode Initiating) shall be given the same Event ID Code.

Event Type No.

Table 1 Category

from the TPL Standards

10 B20 B30 C40 C50 NA

(A) (B) (D)

Event ID Code [2]Event Type

No. [3]Disturbance

Report Filed [5]A-2008 10 Don't knowB-2008 20 YesC-2008 10 NoD-2008 10 No

Notes:[1][2]

[3]

[4] Optional input: provide a brief description of the outage (for Event Type No. 50 only). Please limit the description to 500 characters or less.[5] Was an EOP-004 filed at NERC that was associated with the Event? Year-to-date public (i.e., non-confidential) data of all disturbance

report filings are located at http://www.nerc.com/~filez/dawg-disturbancereports.html.

Description of Event Type No. 50 (Other) [4]

See the Table above for Event Type No. Note that if Event Type No. 10 or 20 is selected, the Outage Mode on Forms 4.1, 4.2, or 4.3,(column P) must be "Single Mode Outage." Outages of an AC/DC Back-to-Back Converter (Form 4.4) must select Event Type No. 50.

If a TO owns assets in a different NERC Region or in a different country, provide data for each Region and country in a separate workbook.

Automatic Outage of a DC Circuit with Normal Clearing.Automatic Outage of two ADJACENT AC Circuits on common structures with Normal Clearing.

The Event ID Code must be appended by the reporting year no. (e.g., 2008). For the 1st quarter submissions in 2008, use "2008" and not "2008Q1" since this Event ID Code will be used for the entire reporting year.

Event ID Code Data

Automatic Outage of two ADJACENT DC Circuits on the common structures with Normal Clearing.Other - please describe the event (optional)

Description

Automatic Outage of an AC Circuit or Transformer with Normal Clearing.

(C)

35


● The Event Type Number

● Event Type Number Possibilities

Event Type No.

Table 1 Category

from the TPL Standards Description

10 B Automatic Outage of an AC Circuit or Transformer with Normal Clearing.20 B Automatic Outage of a DC Circuit with Normal Clearing.30 C Automatic Outage of two ADJACENT AC Circuits on the same structure with Normal Clearing.40 C Automatic Outage of two ADJACENT DC Circuits on the same structure with Normal Clearing.50 NA Other - please describe the event

Element Outage Mode# of Element Outages with same Event ID

Normal Clearing?

Common Structure?

= Event Type No.

AC Circuit or Transformer Single 1 TADS Element Yes N/A 10DC Circuit Single 1 TADS Element Yes N/A 20

AC Circuit Any Other than Single 2 TADS Elements Yes Yes* possible 30**DC Circuit Any Other than Single 2 TADS Elements Yes Yes* possible 40**

AC Circuit or Transformer Any Mode >= 1 TADS Element No N/A 50DC Circuit Any Mode >= 1 TADS Element No N/A 50

AC Circuit or Transformer Any Other than Single 2 TADS Elements Yes No* 50DC Circuit Any Other than Single 2 TADS Elements Yes No* 50AC Circuit Any Other than Single 2 TADS Elements Yes Yes* possible 50**DC Circuit Any Other than Single 2 TADS Elements Yes Yes* possible 50**

AC Circuit, Transformer Any Other than Single >2 TADS Elements N/A N/A 50DC Circuit Any Other than Single >2 TADS Elements N/A N/A 50

AC/DC Back-to-Back Converter Any Mode >= 1 TADS Element N/A N/A 50

Notes: * Yes = two or more Common Structures. No = one or zero Common Structures.Rev. 1/07/2008 ** TO to determine based on available information.

36

Event Type No. 30 or 40

● To qualify for an Event Type No. 30 or 40, the outages must be a direct result of the circuits occupying common structures. These characteristics will generally apply.1. The Outage Initiation Codes are either Element-Initiated

or Other-Element Initiated.2. The Outage Mode Codes are one of the following: (a)

Dependent Mode Initiating (one outage) and Dependent Mode (second outage); (b) Common Mode Initiating and Common Mode (two outages); or (c) both Common Mode (two outages)

37

Assign an Event Type No.

● On one circuit, a conductor breaks (outaging the circuit), and the conductor swings into a second circuit on common structures and outages the second circuit. Both circuits have Normal Clearing. Event Type No. = ?

● Two AC Circuits on common structures are outaged due to a bus fault in the AC Substation were the circuits terminate. Both circuits have Normal Clearing. Event Type No. = ?

38


● Was the Event was associated with the filing of a disturbance report (an EOP-004-01 disturbance report filing)? TO may select “yes, “no,” or “unknown” NERC staff will examine reports to fill in “unknown”

responses Year-to-date public (i.e., non-confidential) data of all

disturbance report filings are located at http://www.nerc.com/~filez/dawg-disturbancereports.html

● Info on disturbance reports is an “impact measure” Since TADS tracks a part of the transmission system, other

potential measures (load lost, transmission service interrupted) would be a subset of the impacts

39

AC Multi-Owner Common Structure Flag

● For AC Circuits only: AC Multi-Owner Common Structure Flag = 0 Not applicable. The circuit is not on common structures

with another circuit, or the circuit is on common structures, but all circuits are owned reported by the same Transmission Owner. No analysis of the Event ID Code or the Event Type Number is required by the Regional Entity.

= 1 Circuit is on common structures with another circuit that is being reported and owned by a different TOs

Transmission Owner. The Regional Entity will need to examine Outage Start Times with this same flag to determine whether a second circuit had an outage with nearly the same Outage Start Time, and if so, whether the TOs properly coordinated their Event ID Codes and Event Type Numbers.

Examples: Inventory & Outage Mode

● Examples in the Manual were developed to assist TOs in responding properly to TADS data request

● Both inventory and outage mode examples are included in the data instruction manual

● Inventory examples are designed to demonstrate proper calculation of entries in Form 3.1 (AC/DC Circuit Inventory Data) But they are applicable to all Elements

● Outage mode examples are provided to illustrate several AC Circuit & Transformer outage scenarios

41

TADS Metrics

● Intent of the proposed metrics is to assist in measuring performance

● Given richness of the data collected, metrics can be computed for many data combinations

● Comprehensive set of metrics not established yet – waiting until sufficient amount of data collected

● Basic metrics presented here will be reported to describe the performance of each Element for the reporting year.

42

Metrics and Data Analysis - Basic Metrics

1. Outage frequency (Sustained, Momentary, and total)2. For AC and DC Circuits:

a. Outage frequency/100 Circuit Miles (Sustained, Momentary, and total). Additional calculations for Events 30 and 40 per 100 Multi-Circuit Structure Miles

b. Additional calculations will exclude outages not related to mileage

3. For Sustained Outages:a. Outage Durationb. Mean Time Between Failure -MTBF c. Mean Time to Repair – MTTRd. Median Time to Repair - MdTTR

4. Percent Availability5. Percent of Elements w. zero outages.6. Percent of Element outages that were associated with

a disturbance report.

43

Metrics and Data Analysis- Additional Items

● MTBF and Percent Unavailability will not follow standard industry terms since no planned outage data will be collected in Phase I

● Lots of ways to “slice” metrics (Cause Code, Outage Mode, Event Type#, etc.) Additional metrics will be determined – we will work

with the data looking for meaningful information

Workshop Session 2: Forms

Documents

Transcript of Workshop Session 2: Forms