(TADS)
Written by WECC RPEWG November 15, 2007 Revised February 20, 2008 Revised November 20, 2008 Revised July 27, 2009
Table of Contents
II.Timelines for Submittals..........................................................................................5 NERC IDs and TO Names..............................................................................................7 III.Forms/Sheets for WECC/NERC Data Submittal....................................................7 a)Form 1.1 Non-Reporting Transmission Owner Statement.......................................7 b)Form 1.2 Reporting Transmission Owner Information............................................8 c)Form 2: Forms for Jointly-Owned Facilities ...........................................................8 d)Form 2.1 Jointly-Owned AC and DC Circuits ........................................................9 e)Form 2.2 Jointly-Owned AC/DC Back-to-Back Converter ...................................10 h)Transmission Circuit Attribute Table ....................................................................................................................................10 i)Transformer Attribute Table....................................................................................15 j)Form 3.3 AC/DC BTB Converter Inventory Data..................................................16 k)WECC Common Structure and ROW Reporting TO Form................................17 l)FORM 4.4 AC DC BTB Converter Outage.........................................................19 m) Outage Information Table....................................................................................20 IV.Applications of Addition and Modifications to the Tables..................................26 Appendix A WECC Members ..............................................................................35 Appendix B TRD/TADS Outage Cause Codes......................................................39 Weather, excluding lightning ....................................................................................39 Lightning....................................................................................................................39 Environmental............................................................................................................39 Contamination ...........................................................................................................39 Foreign Interference ..................................................................................................39 Fire ............................................................................................................................39 Vandalism, Terrorism or Malicious Acts ..................................................................39 Failed AC Substation Equipment...............................................................................39 Failed AC/DC Terminal Equipment..........................................................................39 Failed Protection System Equipment.........................................................................40 Failed AC Circuit Equipment....................................................................................40 Failed DC Circuit Equipment....................................................................................40 Vegetation .................................................................................................................40 Power System Condition ...........................................................................................40 Human Error..............................................................................................................40 Unknown ...................................................................................................................41 Other .........................................................................................................................41 Appendix C WECC TRD Definitions.....................................................................41 Common Corridor......................................................................................................42 Continuous right-of-way or two parallel right-of-ways with centerline separation less than the longest span length of the two transmission circuits at the point of separation or 500 feet, whichever is greater, and no natural barriers (such as hills, rivers, etc.) between the transmission circuits. This separation requirement does not apply to the last five spans of the transmission circuits entering into a substation.. .42 Appendix D NERC TADS Definitions...................................................................43 Element......................................................................................................................43
Protection System......................................................................................................43 AC Circuit..................................................................................................................43 Transformer ...............................................................................................................45 AC Substation............................................................................................................45 AC/DC Terminal........................................................................................................45 AC/DC Back-to-Back Converter...............................................................................45 DC Circuit..................................................................................................................45 Overhead Circuit........................................................................................................45 Underground Circuit..................................................................................................45 Circuit Mile................................................................................................................45 Multi-Circuit Structure Mile......................................................................................46 Voltage Class.............................................................................................................46 Automatic Outage .....................................................................................................46 Momentary Outage ...................................................................................................46 AC Multi-Owner Common Structure Flag................................................................47 In-Service State..........................................................................................................47 Substation, Terminal, or Converter Name.................................................................51 TO Element Identifier................................................................................................51 Outage Start Time......................................................................................................51 Outage Duration.........................................................................................................51 Outage Continuation Flag..........................................................................................51 Outage Identification (ID) Code................................................................................52 Event..........................................................................................................................52 Event Identification (ID) Code..................................................................................52 Event Type Number...................................................................................................52 Normal Clearing.........................................................................................................56 Even though the Protection System failed to reclose properly, the above sequence of events is still an example of Normal Clearing as defined above. .............................57 Element-Initiated Outage...........................................................................................57 Other Element-Initiated Outage.................................................................................57 AC Substation-Initiated Outage.................................................................................57 AC/DC Terminal-Initiated Outage............................................................................57 Other Facility-Initiated Outage..................................................................................57 Single Mode Outage..................................................................................................57 Dependent Mode Initiating Outage............................................................................58 Dependent Mode Outage...........................................................................................58 Common Mode Outage..............................................................................................58 Common Mode Initiating Outage..............................................................................58 Initiating Cause Code.................................................................................................59 Sustained Cause Code................................................................................................59
Section 1
I.
General:
This document serves as the instructions for submission of outage data for the WECC Transmission Reliability Database, TRD and the NERC Transmission Availability Database Systems, TADS. This combined database submittal will serve the two purposes of the voluntary WECC data submittal and the mandatory NERC TADS submittal. This document also covers Phase II non-automatic outage submittal of TADS. The data collected through the use of the following Forms and Sheets are to be supplied to WECC. Then WECC will pull off the data for the WECC TRD database the remaining data will be used to create the NERC TADS Forms, 3.1, 3.2, 3.4, 4.1, 4.2, 4.3, 5.0, 6.1, 6.2 and 6.3. All data submitted to NERC from WECC will be submitted on an individual TO basis. Forms completed by WECC and submitted to NERC: Form 3.1 AC and DC Circuit Inventory Data Form 3.2 Transformer Data Inventory Form 3.4 Summary Automatic Outage Data Form 4.1 AC Circuit Detailed Automatic Outage Data Form 4.2 DC Circuit Detailed Automatic Outage Data Form 4.3 Transformer Detailed Automatic Outage Data Form 5.0 Event ID Code and Event Type Number Data Form 6.1 AC Circuit Detailed Planned Outage Data Form 6.2 DC Circuit Detailed Planned Outage Data Form 6.3 Transformer Detailed Planned Outages Data
II.
WECC: The seventh year of the TRD submittal will be for the calendar year outage data of 2012. The TRD timeline is listed below which is coordinated with the TADS timeline. WECC Members follow the WECC timeline and the NERC timeline will be automatically covered. December, 2011 RPEWG releases to the WECC Members
Section 1
TRD/TADS data submittal sheets that will be used for the data collection for calendar year 2012 (TRD)Updated TRD and TADS Users Manual for the combined WECC/NERC data collection
October, 2012 A WECC/NERC TRD and TADS data training webinar for all WECC Members of the data submittal sheets will be held especially focused to the WECC TRD data submittal. WECC TOs supply data to WECC with CY 2012 transmission outage data in the proper Forms. .NERC: Table 1.6.2 Schedule for Calendar Year 2011 Data Entry Date December 1, 2012 February 1, 2013 Action Re-open webTADS for 2012 calendar year data entry. Instructions for re-starting TADS data entry will be provided by e-mail. Reporting TOs complete submission of all calendar year 2012 data.
February 1, 2013
General Reporting Requirements: There are 11 Forms listed in the data submittal spreadsheets. These Forms are a combination of the WECC TRD and the NERC TADS. The goal of the RPEWG, Reliability Performance Evaluation Work Group, is to have no duplication of data submittal for the WECC and NERC submittals. The TADS data entry software described in Section 1.5.1 will transmit data securely. Until this software is completed, transmittals will be made by e-mail. To securely transmit TADS data securely by e-mail (which contains CEII), the following process should be followed by TOs and REs: 1. Password-protect the document to be transmitted, and send via e-mail to the recipient. Do not include the password in this email. 2. In a second separate e-mail, send the password to the recipient of the document.
Section 1
III.
Section 1
TADS Element is added by the TO prior to December 31 of the year prior to the reporting year, the TO must notify NERC and submit Form 1.2.
Section 1
expected for the purpose of identifying data related to the cause of outages which the reporting TO must supply.
A B C D E
F G-H I J-W
Section 1
Section 1
The From Bus is a descriptive name of the facility where one of the circuits automatic isolation devices is located. To: The To Bus is a descriptive name for the facility where the other circuits automatic isolation devices are located, other than the From Bus. Tertiary Bus: The third bus on 3-terminal lines, if applicable.
Miles: Enter the length of the transmission circuit to the nearest 10th of a mile, including the length of line taps. Circuit Type: Circuit Type identifies the transmission element as overhead or cable depending on which is the majority of the circuit length. Majority is the section of the transmission circuit that is 50 percent or greater of the total length of the circuit. There are four identified circuit types based on the voltage type and construction. Select one three letter abbreviation list below. ACO AC overhead ACC AC cable DCO DC overhead DCC DC cable Voltage Class: The circuits nominal operating voltage. The operating voltage may be different from the design voltage. The kV voltage level of the circuit is entered as one of either 200-299, 300-399 or 500-599 from the drop down lists on the spreadsheet. Conductors Per Phase: Enter the number of conductors per phase. 1, 2, 3, or 4
TADS Data Reporting Instruction Manual November 21, 2008 11
Section 1
Overhead Ground Wire: Enter the number of overhead ground wires. 0, 1, or 2. Insulation Type: This indicates the insulation material and assembly. If more than 80% of the circuit length was constructed using one type insulation material and assembly, enter that insulation material and assembly three letter code, otherwise use Mixed for type of material. CEP = Ceramic Post CES = Ceramic Suspension POP = Polymer Post POS = Polymer Suspension GLS = Glass Suspension MXD = Mixed OTH = Other Cable Type: This indicates the type of insulation and trenching structure. Enter the type of insulation and trenching structure three letter codes: SWD = Solid with conduit SND = Solid with no conduit OWD = Oil filled with conduit OND = Oil filled with no conduit GWD = Gas filled with conduit GND = Gas filled with no conduit.
Structure Materials: This indicates the type of material used in the construction of the supporting structures. If more than 80% of the circuit length was constructed using one type of material, enter that material type code, otherwise use Mixed for type of material. If the material is not listed, use Other code. Enter one of the following three letter abbreviations material types. AL = Aluminum
TADS Data Reporting Instruction Manual November 21, 2008 12
Section 1
CN = concrete FG = fiberglass ST = steel WD = wood CM = composite OT = other MX = mixed. Structure Types: Structure type is the design of the structure use in the circuit. If more than 80% of the line of the circuit length was constructed using one type of design structure, enter that design structure three letter code, otherwise use Mixed for type of structure. If the structure design structure is different from those listed use Other code. Enter one of the following three letter abbreviations structure types. DLC = Double Lattice Column HFR = H Frame KFR = K Frame LAT = Lattice Tower SPG = Single Pole Guyed SPU = Single Pole Un-guyed DOP = Double Pole SLC = Single Lattice Column YTY = Y Type OTH = other MXD = Mixed. Circuits Per Structure: Enter the number of circuit positions per structure that are actually occupied. Do not include circuit positions that otherwise are not reported (i.e. circuits below 230 kV) 1, 2, 3, etc. Terrain: Terrain describes the type of geography or environment the circuit traverses. If more than 80% of the line of the circuit length is in one terrain, enter that terrain two letter code, otherwise use Mixed for type of terrain. If multiple terrain types are applicable for a given area, select the type that is most likely to cause outages. For example, if a line traverses a forest on the coast, select coastal if airborne salt content is more likely to cause outages. Enter one of the following two letter abbreviations for terrain types:
TADS Data Reporting Instruction Manual November 21, 2008 13
Section 1
CO = Coastal DS = Desert MT = Mountains FR = Forest UR = Urban PR = Prairie MX = Mixed. Elevation: Elevation describes the range of altitude above sea level that the circuit traverses. If more than 80% of the circuit length is at one elevation range, enter that elevation range number, otherwise use 99 if elevation range is greater than 2000. Enter one of range elevation number as indicated below: 1 = less than 2000ft. 2 = 2001 to 4000ft. 3 = 4001 to 6000ft. 4 = 6001 to 8000ft. 5 = 8001 to 10000ft. 6 = 10001 to 12000ft. 99 = elevation varies more than 2000ft. In Service Date Enter the date the transmission circuit was placed in service. This could be as a new circuit or a reconfiguration for an existing circuit; a significant change in the current length of the circuit or change in route. Enter the date in the mm/dd/yyyy format. It is very important that the install dates of lines entered in the current year are entered; this will allow WECC to calculate the partial year number for the NERC TADS sheets accurately. Retirement Date The date the transmission circuit was removed from service. Enter the date in the mm/dd/yyyy format. Parent Code The parent code is used to record the parent/child relation of reconfigured circuits. Assign a new Circuit Code(s) to these modified lines, and record the original Circuit Code as the Parent code. Comments:
TADS Data Reporting Instruction Manual November 21, 2008 14
Section 1
Intended for any additional pertinent information that is related to this circuit.
Transformer Location: Transformer Location indicates the physical location of the transformer. Enter the substation name or facility location of the transformer. High Side kV: The kV voltage level of the high side of the transformer is entered as one of the following 200-299, 300-399 or 500-599 from the drop down lists on the spreadsheet. Low Side kV: The kV voltage level of the low side of the transformer is entered as one of the following 200-299, 300-399 or 500-599 from the drop down lists on the spreadsheet. Single Phase or 3 Phase Bank: This describes the 3-phase transformer by the type of connection. Enter A or B for the type of transformer connection. A = 3 Phase Bank B = Single Phase of 3 phase bank
Section 1
Three Phase Bank Rating in MVA Enter the highest MVA rating of the transformer bank, (such as FO or FOA), continuous rating. For single phase transformers bank, enter the rating for the entire bank. In Service Date: Enter the date the transformer was placed in service at present location. Enter the date in the mm/dd/yyyy format. It is very important that the install dates of lines entered in the current year are entered; this will allow WECC to calculate the partial year number for the NERC TADS sheets accurately. Retirement Date: Enter the date the transformer was removed from service from that location. Enter the date in the mm/dd/yyyy format. Comments Intended for any additional pertinent information that is related to this transformer. (The Transformer Attribute table is intended to describe the location of the transformer, not the transformer.)
Section 1 Column G Form 3.3 Descriptor This is a calculated value for the equivalent annual number of AC/DC BTB Converters for the reporting year. Note that column E is not used; it is requested as a sanity check for column F.
Section 1
TOC = Common Tower. The circuit in this listed segment is on a common tower with another TRD/TADS Element. CRW = Common Right of Way. The circuit in this listed segment is in a Common Right of Way with another TRD/TADS Element. .
Example A NCE bubble is the No Common exposure portion of the D circuit. The TRD/TADS circuit is only on its own structure without Common ROW exposure.
Section 1
TOC bubble is the Common Tower exposure portion of the Circuit D. The TRD/TADS circuit is on a Common Tower with another Element. In Example A, this is the portion of the circuit in common with circuit B on a common structure. CRW bubble is the Common Right of Way exposure of the portion of the Circuit D. The TRD/TADS circuit is in a Common Right of Way with another Element. In Example A, this is the portion of the circuit in common with Circuit C. For every TRD/TADS circuit, for each type of exposure for each circuit will be given a row in the sheet. Even if there are repeats of the commonality, there must be an entry for each. This is because there may be different circuits in the different commonalities.
D-F
Section 1 Data for AC-DC BTB Converter That Had an Automatic Outage Form 4.4 Descriptor The TO Element Identifier is a required alphanumeric field that has the TOs internal identifier of the Element. This could be a circuit or transformer number or other identifier recognized by the TO.
Column G
H I The descriptions that follow use defined terms that the TO should become familiar with. They will not be repeated here. Most data fields have drop-down menus. They each describe various facets of the outage. J The Fault Type (if any) for each circuit Outage, input from a drop-down menu. K The Outage Initiation Code, input from a drop-down menu. L The Outage Start Time, in Universal Coordinated Time (UTC), not local time. There is one exception: TOs who submit outage data into webTADS using the graphical user interface (GUI) may select the appropriate local time for their data; webTADS will then convert it to UTC and store the time as UTC within webTADS. This feature is not available for bulk loading UTC must be entered on bulk-loaded data. The use of UTC will allow related outaged occurring on Elements reported by different Transmission Owners to be linked. See instructions Section 4.1 below for outages that continue beyond the end of the reporting calendar year. The Outage Duration expressed as hours and minutes. Momentary Outages will enter a 0 (zero) in this field since we round to the nearest minute. A zero entry in column M tells the reviewer that the outage was Momentary. See instructions in Section 4.1 below for outages that continue beyond the end of the reporting year. Note that the format is a text field and requires a colon (:) be entered between the hours and minutes. Enter 860 hours and 20 min. as 860:20. If the colon is absent the entry will be interpreted as hours. If the Outage Duration exceeds the number of hours remaining in the year (based upon the Outage Start Time), the data will be rejected and an error notice provided. If the previous entry of 860:20 were entered as 86020, it would be read as 86, 020 hours and rejected. 1. The Initiating Cause Code, input from a drop-down menu. All Momentary Outages must supply this code. The Sustained Cause Code, input from a drop-down menu. This only applies to Sustained Outages. Momentary Outages enter NA-Momentary. The Outage Mode, input from a drop-down menu. The Outage Continuation Flag described whether the outages stated and ended within the reporting year or not. The flag is explained in a footnote on the data form as well as in Appendix 6, Section B where the term is fully defined.
N O P Q
Section 1
Enter the WECC Member abbreviation of the operator for the circuit. See Appendix A for current list. Equipment Code: Enter the Circuit Code or Transformer Code from attributes tables.
Start Date/Time: Enter the date in mm/dd/yyyy format and the Time in GMT to nearest second, if available, otherwise to the nearest minute of when the outage started. End Date/Time: Enter the date in mm/dd/yyyy format and the Time in GMT to nearest second, if available, otherwise to the nearest minute of when the outage ended. If an outage begins in a reporting calendar year and continues beyond the end of the year (December 31) 2012, the calculation of a total Outage Duration is not possible. In this case, the following process will be observed. 1. Two separate Outage Durations will be input. a. For the reporting year when the outage started, the TO inputs the Outage Start Time and calculates an Outage Duration from the Outage Start Time until the end of the reporting year. The Outage Continuation Flag is input as 1. b. For the next reporting year, the same Event ID Code and same Outage ID Code will be entered for the outage with an Outage Start Time equal to January 1, 00:00 UTC of that reporting year. If the outage is concluded in that reporting year, an Outage Duration is calculated from the Outage Start Time. If the outage continues to the subsequent reporting year, the Outage Duration is entered as 8760:00, or 8784:00 for a leap year. The Outage Continuation Flag is input as 2. c. Most outages that are not concluded by the end of a reporting year will conclude in the next reporting year. However, an outage
TADS Data Reporting Instruction Manual November 21, 2008 21
Section 1
may span three or more reporting years. This process described in b. above continues until the outage ends. Cause Code Enter one of the three letter causes from the Cause Code Table, multiple common mode events must have the same Cause Code; dependant outages may have different Cause Codes. See Appendix B for cause code details. For Non-Automatic Outage codes see Planned or Operational Cause codes below. 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1. Weather, excluding lightning 2. Lightning 3. Environmental 4. Contamination 5. Foreign Interference 6. Fire 7. Vandalism, Terrorism or Malicious Acts 8. Failed AC Substation Equipment 9. Failed AC/DC Terminal Equipment 10. Failed Protection System Equipment 11. Failed AC Circuit Equipment 12. Failed DC Circuit Equipment 13. Vegetation 14. Power System Condition 15. Human Error 16. Unknown
1 17. Other Planned Outage Cause Codes: Used for Non-Automatic outages only. See Appendix B for cause code details . 1. NA-used if the outage is a Operational outage 2. Maintenance and Construction 3. Third Party Request 4. Other Planned Outage
Section 1
Operational Outage Cause Codes: Used for Non-Automatic outages only. See Appendix B for cause code details. 1. 2. 3. 4. 5. NA- used if the outage is a Planned Outage Emergency System Voltage Limit Mitigation System Operating Limit Mitigation, ex Voltage Other Operational Outage
Outage Mode Codes: The outage mode describes the initiating characteristics of an outage. . See Appendix C for definitions on initiating modes. Enter the initiating outage mode defined in the Definitions Section: For Non-Automatic Outages this section is not needed. IND Independent Mode DEP Dependent Mode COM - Common mode DEPI - Initiating outage for a Dependent Mode COMI Initiating Common Mode outage for Dependent Mode outage(s) Note: If an initiating event is not within the scope of this database, the event will may not have a DEPI, e.g., a 500kV breaker failure causing a 500kV line outage. Fault Type: The descriptor of the fault, if any, associated with an Automatic Outage. Several choices are possible. For Non-Automatic Outages this section is not needed. 1 - No fault 2 - Phase to Phase fault 3 - Single Phase to Ground fault 4 - Phase-Phase-Ground, 3 Phase, or 3 Phase-Ground fault 5 - Unknown Fault Type. Outage Initiation Code: The Outage Initiation Codes describe where an Automatic Outage was initiated on the power system. Non-Automatic Outages use either Planned or Operational. 1 Element-Initiated Outage 2 Other Element-Initiated Outage 3 AC Substation-Initiated Outage
TADS Data Reporting Instruction Manual November 21, 2008 23
Section 1
4 AC/DC Terminal-Initiated Outage 5 Other Facility-Initiated Outage 6 Planned 7 Operational Outage Type: Used to identify if the event was automatic versus manual forced. Options are Auto, Forced Manual and Manual. An automatic outage is one which is protective equipment initiated, and a forced manual outage is one that was operator initiated and could not be delayed beyond 30 minutes and Manual is for Planned and Scheduled outages. Event Type Number: Not needed for Planned outages. Two tables are provided for Event Type Numbers that fall into two distinct categories. Normal Clearing: This table applies under two conditions When a fault has occurred and the Element is isolated under Normal Clearing. 1. When a fault has not occurred, but the Element is isolated by the proper and intended operation of the Protection System. For example, a circuit breaker may be opened due to the detection of circuit breaker low gas pressure, causing the Protection System to operate. Or a Transformer may be isolated by the Protection System due to high oil temperature. Both of these events are categorized as Normal Clearing. Abnormal Clearing: This table applies under two conditions 1. When a fault has occurred and the Element is isolated under Abnormal Clearing. 2. When a fault has not occurred, but the Element is isolated by the failure or unintended operation of the Protection System. For example a low gas pressure sensor which is part of the Protection System may provide an incorrect sensor reading and cause the Protection System to operate when it would not otherwise have operated, but since the sensor and its controls are part of the Protection System its operation is abnormal (not-proper). The isolation of the Element was due to the Protection Systems improper operation of a protection sensor. Since an Automatic Outage was due to Abnormal Clearing, the event is categorized as Abnormal Clearing. Another example of Abnormal Clearing is where a relay has incorrect settings applied (either by design or by misapplication) and the relay causes an outage to the Element. Events with NORMAL CLEARING1 Event Description Type
Section 1 05 06 11 13 31 49 Single bus section fault or failure (200kV or above) resulting in one or more Automatic Outages. Single internal circuit breaker fault (200kV or above) resulting in one or more Automatic Outages2. Automatic Outage of a single Element. Automatic Outage of two or more Elements within one NCCBS. Automatic Outages of two or more TADS adjacent AC Circuits or DC Circuits on common structures. To qualify as Event Type 31 the Automatic Outages must be the direct result of the circuits occupying common structures 3. Automatic Outage(s) with Normal Clearing not covered by Event Types 05 through 31 above4.
62
90
Event ID Code: Up to 10 alphanumeric characters - Each event shall have a unique Event ID. Dependent mode and common mode outages have the same Event ID. For Non-Automatic Outages this section is not needed. Disturbance Reported:
Select if an outage report (EOP-004) was filed at NERC for this event or not. Options are Yes, No, and Dont Know.
TADS Data Reporting Instruction Manual November 21, 2008 25
Section 1
Outage Continuation Code: If an outage begins in a reporting calendar year and continues beyond the end of the year (December 31) or , the calculation of a total Outage Duration is not possible. In this case, the following process will be observed. 1. Two separate Outage Durations will be input. a. For the reporting year when the outage started, the TO inputs the Outage Start Time and calculates an Outage Duration from the Outage Start Time until the end of the reporting year. The Outage Continuation Flag is input as 1. b. For the next reporting year, the same Event ID Code and same Outage ID Code will be entered for the outage with an Outage Start Time equal to January 1, 00:00 UTC of that reporting year. If the outage is concluded in that reporting year, an Outage Duration is calculated from the Outage Start Time. If the outage continues to the subsequent reporting year, the Outage Duration is entered as 8760:00, or 8784:00 for a leap year. The Outage Continuation Flag is input as 2. c. Most outages that are not concluded by the end of a reporting year will conclude in the next reporting year. However, an outage may span three or more reporting years. This process described in b. above continues until the outage ends.
IV.
Section 1
terms of system operation and identifying parameters. These include system identification of the circuit, start and end dates of service, nominal voltage of the transmission element, points of connection to the system and origin (parent code). The physical characteristics describe the circuit in terms of its physical properties and provide data that describes the elements environment. The physical properties data include circuit type, structure and material type, length, conductors per phase, overhead ground wire, and insulator type. The circuit environment is described by the terrain, elevation, and common corridor data. Data entry maybe done by a translation program or manually depending on the number of data records required. It is expected that the first submission of data will require the most effort. Subsequent data submission will basically be a replication of the existing data with minor updates for configuration changes to the system and new additions. The following is an explanation of the methodology to address the entry of new data records. The primary need for a new data record is the addition of a newly constructed circuit that was place in service during the current reporting year. Circuits have to be included in order to have a link for assigning outage data In Example 1.1, the operator and the alphanumeric circuit code were entered to uniquely identify the circuit. Most operators will use an alpha numeric number to identify transmission elements within their system. As long as the identifier conforms to WECC outage data submission for circuit codes, the operator circuit identification can be used. All other data will describe the circuit by its operating and physical attributes. Example 1.1
Operator
XYZ
Circuit Code
A1B2C3D4
From
To
A second requirement for the creation of a new data record is for an extension or rerouting of an existing circuit that effectively changes the exposure of the circuit. As seen in Figure 1.1, the circuit length may also increase due to a radial section being tapped off an existing circuit. For this case, the circuit code for the existing circuit will have to be retired and a new circuit code created for the new circuit length addition. Figure 1.1
Section 1
Bus A
Bus B
Bkr
Bkr
Bus A
Bus B
In Figure 1.1, the original circuit had its length increased by the addition of a radial tap, but the circuits bounds did not change. Example 1.2 shows the changes required in the Transmission Circuit Attribute table for the circuits in Figure 1.1. Shown as Retired Circuit Code table in Example 1.2, the original circuit was retired by simply placing a retirement date on the existing circuit code. An entry was made in the Comments column that provides an explanation for the retirement of the original circuit in Figure 1.1. In the New Circuit Code example, a new circuit code was created to account for the addition of the tap: the circuit length was increased, the original circuit code was noted as the parent code, and a comment was added to provide an explanation for the new circuit code. Example 1.2 Original Circuit Code Circuit Length in Miles
6.7
Operator
XYZ
Circuit Code
A1B2C3D4
From To
Parent Code
Comm
Section 1
Operator
XYZ
From To
Miles
6.7
Parent Code
Comm
Added tap
Operator
XYZ
Circuit Code
B2C3D4E5
From To
Parent Code
Comm
New data records are also created by the reconfiguration of an existing circuit. System reconfigurations can occur when an isolation device is inserted between the existing isolation devices (breakers) that bound a circuit. These reconfigurations may or may not change the length or reroute the existing circuit, but do create a new isolation boundary. The reconfiguration of an existing circuit will create two new circuit codes and retire an existing circuit code in the Transmission Circuit Attribute table. The creation of the two new circuit codes is independent of the insertion point of the new isolation device. Figure 1.2
Section 1
Bus A
Bus B
Bkr
Bkr
Bkr
Bus A
Bus C
Bus B
Figure 1.2 shows a reconfiguration of a circuit by the insertion of a breaker between two existing breakers that bound the original circuit. The changes required to the Transmission Circuit Attribute table are shown in Example 1.3. In Example 1.3, the original circuit configuration circuit record is shown as Original Circuit Code. The original circuit has a circuit code PODX1234. PODX1234 was placed in service in 1/15/1975 and has a length of 100 miles between Bus A and Bus B. A new breaker was inserted at Bus C between Bus A and Bus B in 9/14/2001. The reconfigured existing circuit code was retired and two new circuit records were created in the table. Shown as Retired Circuit Code table in Example 1.3, the original circuit was retired by placing a retirement date on the existing circuit code and comment explaining the retirement of the circuit code record. In this example, two new circuit code table records were created. Shown as New Circuit Codes in Example 1.3, the two new circuit codes are PODX2485 and PODX2486. PODX2485 has a length of 25 miles and is bounded by the breakers at Bus A and Bus C. PODX2486 is 75 miles long and is bounded by the breaker at Bus B and Bus C. Bus C is a common isolation point for both new circuits. Example 1.3 Original Circuit Code
Section 1
Operator
ABC
Circuit Code
PODX1234
From To
Bus A Bus B
Miles
100.0
Parent Code
Comme
From To
Bus A Bus B
Miles
100.0
Parent Code
Comme
New station
From To
Bus A Bus C
Miles
25.0
Parent Code
Comme
From To
Bus B Bus C
Miles
75.0
Parent Code
Comme
Section 1
Most Outage Information table data is generally already recorded by most operators. There may be a need for a conversion in both time entry information and cause codes. The time entries for outage records should be in GMT (Greenwich Mean Time) for the Standard Time where the outage occurred. If possible, the recording time should mm/dd/yyyy format for the date and should be recorded to the nearest second. GMT Example: A Standard Mountain Time of 9:00AM will be 15:00 PM GMT. Cause codes for outages should be reported using one of the WECC General Outage Cause code for each equipment outage. This may require the operator to translate from the operator outage cause code to one of the WECC General Outage Cause code. If a transmission equipment outage is an element of a dependent mode outage, it may or may not have the same cause code as the initiating outage. For example, lightning may have initiated the original outage for a set of dependent outages, but the sequent outages may have been caused by system protection failure. The initiating outage will be assigned the Lightning (LIG) cause code and the subsequent outage will be assigned the cause code Terminal Equipment (TER) for system protection failure. Outage Mode not may be part of most WECC operators outage recording information or may be recorded differently. The Outage Information table requires two record entries to account for different initiating modes. The first of the entries is the Outage Mode. The Outage Mode describes the initiating mode for an outage or set of equipment outages. There are five Outage modes: Independent, Dependent, Initiating Dependent, Common and Common Initiating. Most outage will be classified as Independent Mode outages. The Event ID is use to identify the outage within the table and also serves as a link to identify a set of dependent or common mode outages. Dependent and Common mode outages will be assigned only one Event ID per related outages. A group of Dependent mode outages will usually have an Initiating Dependent Mode (DEPI) and a Dependent Mode (DEP) outage mode. If an initiating event is not within the scope of this database, the event will may not have a DEPI. This may include outages such as a 500kV breaker failure causing a 500kV line outage or a 69 kV under built circuit causing a 230kV outage. Independent Mode outages are outages that were isolated within the transmission element isolation devices and did not impact other elements in the system. As seen in Example 1.4, these outages records will only require an IND in the Outage Mode column and Event ID in the Outage Information table. Example 1.4
Section 1
Operator CBA
Start Date/Time (GMT) End Date/Time (GMT) 11/12/2003 18:06:39 11/12/2003 18:15:23
Event ID 789123456
Common Mode outages involve two or more transmission elements and occur almost simultaneously due to the same outage cause. Shown in Example 1.5, Common Mode outages should have the same outage Cause Code and Event ID. The duration for the elements could be different in a Common Mode outage. Example 1.5
Operator XYZ XYZ Equipment Code 150 361 Start Date/Time (GMT) End Date/Time (GMT) 06/08/2004 21:32:11 08/06/2004 22:31:16 06/08/2004 21:32:11 08/06/2004 23:26:00 Cause Code WEA WEA Outage Mode COM COM Event ID AUG6803A AUG6803A
Dependent Mode outages occur from an initiating outage and subsequently cause the outage of other transmission element(s) in the system. Example 1.6 shows that the Event ID for a Dependent Mode outage should be the same for all the associated elements. The initiating outage should be identified by placing the Initiating Dependent Mode (DEPI) identifier in the Outage Mode column. The restoration time for the elements in a Dependent Mode outage may differ in length. The initiating outage may not be within the scope of recordable outage data required for the Outage Information table. Outages that do not have an initiating outage within the scope of the Outage Information table requirements will not have a DEPI for the set of dependent outages.
Example 1.6
Operator ABC ABC ABC Equipment Code CGE54 FRG55 153 Start Date/Time (GMT) 07/12/2005 18:22:59 07/12/2005 18:23:01 07/12/2005 18:23:01 End Date/Time (GMT) 07/13/2005 02:22:59 07/12/2005 18:35:59 07/12/2005 18:35:59 Cause Code FIR TER LOS Outage Mode DEPI DEP DEP Event ID T-5588 T-5588 T-5588
A Common Mode outage could be the initiating outage event for a set of subsequent outage. As shown in Example 1.7, these outages should be identified with a Common Mode Initiating (COMI) identifier in the Outage Mode column and subsequent outages should have the same Event ID. Example 1.7
Section 1
All outage records in the Outage Information table should be submitted complete. The accuracy of the start and End time should be the only variance.
Section 1
ADOE Alberta Department of Energy AESO Alberta Electric System Operator AEUB Alberta Energy and Utilities Board AESC Allegheny Energy Supply Company, LLC ALTA AltaLink L.P. AWEA American Wind Energy Association WPE Aquila Networks-WPC ACC Arizona Corporation Commission AEPC Arizona Electric Power Cooperative, Inc. APA Arizona Power Authority APS Arizona Public Service Company ATCO ATCO Electric Ltd. AUR Auriga Corporation APX Automated Power Exchange, Inc. AVA Avista Corp. BEPC Basin Electric Power Cooperative BMI Battelle Memorial Institute BHP Black Hills Power BPAP Bonneville Power Administration Power Business Line BPAT Bonneville Power Administration Transmission Business Line BCHA British Columbia Hydro and Power Authority BCME British Columbia Ministry of Energy & Mines BCTC British Columbia Transmission Corporation BCUC British Columbia Utilities Commission BURB Burbank Water and Power CBC California British Columbia Transmission Company, LLC CDWR California Department of Water Resources CEOB California Electricity Oversight Board CEC California Energy Commission CFBF California Farm Bureau Federation CISO California Independent System Operator CORA California Office of Ratepayer Advocates CPUC California Public Utilities Commission CALP Calpine Corporation CES Cambridge Energy Solutions CRGL Cargill Power Markets, LLC CEOE CE Obsidian Energy CAWC Central Arizona Water Conservation District CINE Cinergy Services, Inc. HHWP City and County of San Francisco Hetch Hetchy Water & Power ANHM City of Anaheim GLEN City of Glendale Public Service Department RDNG City of Redding RVSD City of Riverside COPC Colorado Public Utilities Commission CSU Colorado Springs Utilities CFE Comision Federal de Electricidad COMP Compusharp Inc. CCG Constellation Energy Commodities Group, Inc. DGT Deseret Generation & Transmission Co-operative DENA Duke Energy North America, LLC DETM Duke Energy Trading and Marketing, LLC ECON Economic Insight EMMT Edison Mission Marketing & Trading, Inc.
Section 1
EQI EleQuant, Inc. EPE El Paso Electric Company ECI Electrical Consultants, Inc. ENW Energy Northwest ESL Energy Strategies LLC ENMX ENMAX Corporation EMC EPCOR Merchant and Capital L.P. EMCU EPCOR Merchant and Capital (US) Inc. EWEB Eugene Water & Electric Board FARM Farmington Electric Utility System FBC FortisBC FPLE FPL Energy LLC GEO Geo-Energy Partners-1983 Ltd. GBPP Gila Bend Power Partners, LLC PGR Gila River Power, L.P. GBT Great Basin Transmission, LLC HGC Harquahala Generating Company, LLC HESI Henwood Energy Services, Inc. HPLP Hunt Power, L.P. IPC Idaho Power Company IPUC Idaho Public Utilities Commission IID Imperial Irrigation District KEMA KEMA Inc. LCG LCG Consulting LAC Los Alamos County LDWP Los Angeles Department of Water and Power MLCI Merrill Lynch Commodities, Inc. MWD Metropolitan Water District of Southern California MTI Micron Technology Inc. MIR Mirant Americas, Inc. MID Modesto Irrigation District MATL Montana Alberta Tie Ltd. MDEQ Montana Department of Environmental Quality MPSC Montana Public Service Commission MWEC Morenci Water & Electric Company NGU National Grid USA Service Company, Inc. NREL National Renewable Energy Laboratory NCI Navigant Consulting, Inc. NVOE Nevada State Office of Energy NMPRC New Mexico Public Regulation Commission NTD New Transmission Development Company [A Trans-Elect Company] NAPG North American Power Group, Ltd. NCPA Northern California Power Agency NPCC Northwest Power and Conservation Council NWMT NorthWestern Energy NRG NRG Power Marketing, Inc. OCES Oak Creek Energy Systems, Inc. OOE Oregon Department of Energy OPUC Oregon Public Utility Commission PG&E Pacific Gas and Electric Company PAC PacifiCorp PACM PacifiCorp Merchant Function PASA Pasadena, City of PBEC Peabody Energy Corporation PRPA Platte River Power Authority PGE Portland General Electric Company PWX Powerex PPLE PPL EnergyPlus, LLC PPLM PPL Montana, LLC PPM PPM Energy, Inc. PRAX Praxair, Inc. PSC Public Service Company of Colorado PNM Public Service Company of New Mexico NPUC Public Utilities Commission of Nevada CHPD Public Utility District No. 1 of Chelan County DOPD Public Utility District No. 1 of Douglas County
Section 1
GCPD Public Utility District No. 2 of Grant County PSE Puget Sound Energy REI Reliant Energy, Inc. RES RES-North America RVE Roseville Electric SMUD Sacramento Municipal Utility District SRP Salt River Project SDGE San Diego Gas & Electric Company SME Saracen Merchant Energy LP
Section 1
WALC (Phoenix, Arizona) WASN (Sacramento, California) WAUC (Salt Lake City, Utah) WAUW (Billings, Montana) WLB Westmoreland Coal Company WEMT Williams Power Company, Inc. WIA Wyoming Infrastructure Authority WPSC Wyoming Public Service Commission
Lightning
Automatic Outages caused by lightning.
Environmental
Automatic Outages caused by environmental conditions such as earth movement (including earthquake, subsidence, earth slide), flood, geomagnetic storm, or avalanche.
Contamination
Automatic Outages caused by contamination such as bird droppings, dust, corrosion, salt spray, industrial pollution, smog, or ash.
Foreign Interference
Automatic Outages caused by foreign interference from such objects such as an aircraft, machinery, a vehicle, a train, a boat, a balloon, a kite, a bird (including streamers), an animal, flying debris not caused by wind, and falling conductors from one line into another. Foreign Interference is not due to an error by a utility employee or contractor. Categorize these as Human Error.
Fire
Automatic Outages caused by fire or smoke.
Vegetation
Automatic Outages (both Momentary and Sustained) caused by vegetation, with the exception of the following exclusions which are contained in FAC-003-1: 1. Vegetation-related outages that result from vegetation falling into lines from outside the right of way that result from natural disasters shall not be considered reportable with the Vegetation Cause Code. Examples of disasters that could create non-reportable Vegetation Cause Code outages include, but are not limited to, earthquakes, fires, tornados, hurricanes, landslides, wind shear, major storms as defined either by the Transmission Owner or an applicable regulatory body, ice storms, and floods, and 2. Vegetation-related outages due to human or animal activity shall not be considered reportable under the Vegetation Cause Code. Examples of human or animal activity that could cause a non-reportable Vegetation Cause Code outage include, but are not limited to, logging, animal severing tree, vehicle contact with tree, arboricultural activities or horticultural or agricultural activities, or removal or digging of vegetation. Outages that fall under the exclusions should be reported under another Cause Code and not the Vegetation Cause Code.
Human Error
Automatic Outages caused by any incorrect action traceable to employees and/or contractors for companies operating, maintaining, and/or providing assistance to the Transmission Owner will be identified and reported in this category. Also, any human
failure or interpretation of standard industry practices and guidelines that cause an outage will be reported in this category.
Unknown
Automatic Outages caused by unknown causes should be reported in this category.
Other
Automatic Outages for which the cause is known; however, the cause is not included in the above list.
Momentary (transient) outage: A Forced Outage of duration of less than one minute and is therefore recorded as zero duration. Generally, it covers only automatic re-closure events. Sustained Outage: A Forced Outage of duration of one minute or more. It does not include automatic reclosure events. Outage Mode: One of three initial outage characteristics: independent, dependent, and common mode. Independent Outage Mode: A Forced Outage of a single transmission element that does not impact other transmission elements. Dependent Outage Mode: An outage that would not have occurred without an initiating outage on another circuit. Example: The outage of a 500kV circuit that causes the outage of 230kV circuits that are radial fed from the 500kv line. Dependent Mode Initiating: The initiating outage that cause outage(s) on another circuit(s). Common Mode Outage: A common mode outage is an outage that results from the same outage cause as another concurrent outage; example, double circuit tower failure. Common Mode Initiating: An initiating common mode outage that initiated outage(s) on another circuit(s). Operator: The operating agent has operational control of the transmission element. The operating agent may not be the owner of the transmission element or conduct maintenance on the circuit. Common Corridor Continuous right-of-way or two parallel right-of-ways with centerline separation less than the longest span length of the two transmission circuits at the point of separation or 500 feet, whichever is greater, and no natural barriers (such as hills, rivers, etc.) between the transmission circuits. This separation requirement does not apply to the last five spans of the transmission circuits entering into a substation.
An Element may also be referred to as a TADS Element in the Manual. They have the same meaning.
Protection System
Protective relays, associated communication systems, voltage and current sensing devices, station batteries and DC control circuitry.1
AC Circuit
A set of AC overhead or underground three-phase conductors that are bound by AC Substations. Radial circuits are AC Circuits. The boundary of an AC Circuit extends to the transmission side of an AC Substation. A circuit breaker, Transformer, and their associated disconnect switches are not considered part of the AC Circuit but instead are defined as part of the AC Substation. The AC Circuit includes the conductor, transmission structure, joints and dead-ends, insulators, ground wire, and other hardware, including in-line switches. The AC Circuit includes inline switches used to sectionalize portions of the AC Circuit as well as series compensation (capacitors and reactors) that is within the boundaries of the AC Circuit even if these in-line devices are within an AC Substation. If these devices are not within the AC Circuit boundaries, they are not part of the AC Circuit but instead are part of the AC Substation. The diagrams on the next several pages explain this concept. The red arcs define the AC Circuit boundaries.2 In Figure 1 (next page), the series capacitor, bypass circuit breaker, and numerous disconnect switches are in a fenced AC Substation that is within the boundaries of the AC Circuit itself. When the series capacitor is connected and the bypass breaker is open, the capacitor and its disconnect switches are part of the AC Circuit. When the bypass breaker is closed, the bypass breaker and its disconnect switches (not shown) are part of the AC Circuit.
1 2
This definition is in the current NERC Glossary of Terms Used in Reliability Standards. To simplify future diagrams, disconnect switches may not be shown.
Figure 1
Two in-line NC switches and one series capacitor are part of the AC Circuit between AC Substations A and B. When the bypass breaker and its disconnect switches (not shown) are closed and the capacitor switches opened, the breaker and its switches are part of the AC Circuit. NO
NC
NC
In Figure 2, the series reactor and in-line switches are part of the AC Circuit since they are within the AC Circuit boundaries even though they are within the AC Substation boundaries. In Figure 3, they are not part of the AC Circuit because they are not within the AC Circuit boundaries. Figure 2
Two in-line NC switch and one series reactor are part of the AC Circuit between AC Substations A and B. The AC Circuit boundaries are the breaker disconnect switch in AC Substation A and the high-side disconnect switch on the Transformer in AC Substation B. NO
NC
NC
Figure 3
Two in-line NC switches and one series reactor are part of the AC Substation and not part of the AC Circuit between AC Substations A and B NO
NC A
NC
O
B
Transformer
A bank comprised of three single-phase transformers or a single three-phase transformer. A Transformer is bounded by its associated switching or interrupting devices.
AC Substation
An AC Substation includes the circuit breakers and disconnect switches which define the boundaries of an AC Circuit, as well as other facilities such as surge arrestors, buses, Transformers, wave traps, motorized devices, grounding switches, and shunt capacitors and reactors. Series compensation (capacitors and reactors) is part of the AC Substation if it is not part of the AC Circuit. See the explanation in the definition of AC Circuit. Protection System equipment is excluded.
AC/DC Terminal
A terminal that includes all AC and DC equipment needed for DC operation such as PLC (power-line carrier) filters, AC filters, reactors and capacitors, Transformers, DC valves, smoothing reactors and DC filters. On the AC side, an AC/DC Terminal is normally bound by AC breakers at the AC Substation bus where it is connected. On the DC side, it is bound by DC converters and filters. Protection System equipment is excluded.
DC Circuit
One pole of an Overhead or Underground DC line which is bound by an AC/DC Terminal on each end.
Overhead Circuit
An AC or DC Circuit that is not an Underground Circuit. A cable conductor AC or DC Circuit inside a conduit which is not below the surface is an Overhead Circuit. A circuit that is part Overhead and part Underground is to be classified based upon the majority characteristic (Overhead Circuit or Underground Circuit) using Circuit Miles.
Underground Circuit
An AC or DC Circuit that is below the surface, either below ground or below water. A circuit that is part Overhead Circuit and part Underground Circuit is to be classified based upon the majority characteristic (Overhead Circuit or Underground Circuit) using Circuit Miles.
Circuit Mile
One mile of either a set of AC three-phase conductors in an Overhead or Underground AC Circuit, or one pole of a DC Circuit. A one mile-long, AC Circuit tower line that carries two three-phase circuits (i.e., a double-circuit tower line) would equate to two Circuit Miles. A one mile-long, DC tower line that carries two DC poles would equate to two Circuit Miles. Also, a one mile-long, common-trenched, double-AC Circuit
Underground duct bank that carries two three-phase circuits would equate to two Circuit Miles.
Voltage Class
The following voltages classes will be used for reporting purposes: 200 299 kV 300 399 kV 400 499 kV 500 599 kV 600 799 kV For Transformers, the Voltage Class reported will be the high-side voltage, even though the cut-off voltage used in the definition is referenced on the low-side. Voltages are operating voltages. Outage Reporting Definitions
Automatic Outage
An outage which results from the automatic operation of switching device, causing an Element to change from an In-Service State to a not In-Service State. A successful AC single-pole (phase) reclosing event is not an Automatic Outage.
Momentary Outage
An Automatic Outage with an Outage Duration less than one (1) minute. If the circuit recloses and trips again within less than a minute of the initial outage, it is only considered one outage. The circuit would need to remain in service for longer than one minute between the breaker operations to be considered as two outages.
Sustained Outage3
3
The TADS definition of Sustained Outage is different that the NERC Glossary of Term Used in Reliability Standards definition of Sustained Outage which is presently only used in FAC-003-1. The
Non-Automatic Outage
An outage which results from the manual operation (including supervisory control) of a switching device, causing an Element to change from an In-Service State to a not InService State.
Planned Outage
A Non-Automatic Outage with advance notice for the purpose of maintenance, construction, inspection, testing, or planned activities by 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 or restoration of an outage of another TADS Element are not reportable.
Operational Outage
A Non-Automatic 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 and that cannot be deferred.
In-Service State
An Element that is energized and fully connected to the system. Examples of reportable AC Circuit and Transformer Automatic Outages are illustrated below.
glossary defines a Sustained Outage as follows: 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. The definition is inadequate for TADS reporting for two reasons. First, it has no time limit that would distinguish a Sustained Outage from a Momentary Outage. Second, for a circuit with no automatic reclosing, the outage would not be counted if the TO has a successful manual reclosing under the glossary definition.
In Figure 4, AC Circuit A is bound by the disconnect switches (not shown)4 of two breakers, and Transformer A is bound by a breaker and a disconnect switch. AC Circuit B is bound by a breaker and a disconnect switch, and Transformer B is bound by a breaker and a disconnect switch. 230 kV bus fault opens the green breakers. The TADS Transformers each report an outage. AC Circuit A reports an outage, but AC Circuit B does not. It is defined by the breaker on the left and the disconnect switch on the right. Since the breaker associated with AC Circuit B did not experience and automatic operation, it was not outaged. It remains fully connected by the breaker and the disconnect switch.
Figure 4
Transformer A
AC Circuit B Transformer B
In Figure 5, we have a similar situation, except that the Transformers are not reportable since their low-side voltages are less that 200 kV. The AC Circuit outages are reportable exactly the same as in Figure 4; however, the Transformer outages are not reportable. Figure 5
Transformer A
AC Circuit B
Transformer B
In Figure 6 (next page), AC Circuit 22, the only source connecting AC Substations A and B, has a fault. As a result, AC Circuits 84 and 88 are deenergized but remain fully connected. Three outages are reported: circuits 22, 84, and 88. None of them meet the In-Service State requirement of being energized and fully connected.
4
For simplification, disconnect switches may not be show in some figures. When a circuit breaker or Transformer disconnect switch define an AC Circuit boundary, we may just refer to the circuit breaker and the Transformer as defining the boundary without reference to their disconnect switches.
230 kV
AC Circuit A
500 kV
AC Circuit A
O O
230 kV
O O
34 kV
Figure 6
O
AC Circuit 22
AC Circuit 88
C
O O
An exception that an Element be fully connected to be considered in an In-Service State is provided for a multi-terminal AC Circuit with a Transformer on one terminal that shares a breaker with the circuit. Figure 7
A B A
All circuits are 230 kV In both figures, the AC Circuit is bounded by AC Substations A, B, and C as indicated by the red arcs. Each Transformers boundaries are the red disconnect switch and the red arc before the breaker. Note that the Transformer in either figure may or may not be a reportable Element (i.e., one with a low-side voltage 200 kV).
O
All circuits are 230 kV
O O
AC Circuit 84
D
Figure 8
B
Assume that each Transformer is out of service as a result of the operation of its associated breaker (indicated in green). In Figure 7, the AC Circuit would normally be considered out of service since the breaker at AC Substation C, which is shared by the AC Circuit and the Transformer, is open. Nevertheless, if all other portions of the AC Circuit are in service, the entire AC Circuit is considered to be in an In-Service State even if the Transformer is out of service. Because TADS does not recognize partial outage states, the multi-terminal exception above was developed so as to not overstate the outage contribution of a multi-terminal configuration of this type. In Figure 8, the open breaker is not shared by the AC Circuit, and the AC Circuit remains fully connected. Thus, the exception does not apply in this case since the AC Circuit is fully connected even though the Transformer out of service.
TO Element Identifier
An alphanumeric name that the TO must enter to identify the Element which is outaged (e.g., a circuit name.)
Outage Duration
The amount of time from the Outage Start Time to when the Element is fully restored to its original or to normal configuration, including equipment replacement. Outage Duration is expressed as hours and minutes, rounded to the nearest minute. Momentary Outages are assigned a time of zero Outage Duration. TADS data is reported on a calendar-year basis, and the TADS Data Reporting Instruction Manual addresses the recording of the Outage Durations of an outage that starts in one reporting year and concludes in another reporting year.
Event
An Event is a transmission incident that results in the Automatic Outage (Sustained or Momentary) of one or more Elements.
settings applied (either by design or by misapplication) and the relay causes an outage to the Element. Events with NORMAL CLEARING1 Event Description Type
05 06 11 13 31 49 Single bus section fault or failure (200kV or above) resulting in one or more Automatic Outages. Single internal circuit breaker fault (200kV or above) resulting in one or more Automatic Outages2. Automatic Outage of a single Element. Automatic Outage of two or more Elements within one NCCBS. Automatic Outages of two or more TADS adjacent AC Circuits or DC Circuits on common structures. To qualify as Event Type 31 the Automatic Outages must be the direct result of the circuits occupying common structures 3. Automatic Outage(s) with Normal Clearing not covered by Event Types 05 through 31 above4.
62
90
Fault Type
The descriptor of the fault, if any, associated with each Automatic Outage of an Element. Several choices are possible for each Element outage: 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 fault 5. Unknown fault type
The term associated with could be broadly interpreted to mean any fault, no matter how remote, which results in an Automatic Outage of an Element. Therefore, the following guide is to be used for reporting Fault Type. This guide uses the Outage Initiation Codes described in Section C below. If an Element has an Automatic Outage and its Outage Initiation Code is; a. Element-Initiated, report the Fault Type from one of the five above. b. Other Element-Initiated, report No fault as the Fault Type for the outage since a Fault Type will be reported for the other Element that initiated the outage. c. Either AC Substation-Initiated or AC/DC Terminal Initiated, report Fault Types from 2-5 above ONLY if a fault occurred on AC equipment that is 200 kV or greater; otherwise, report No fault if a fault did not occur OR if a fault occurred, but it occurred on AC equipment that is less than 200 kV. d. Other Facility-Initiated, report No fault as the Fault Type. The Fault Type for each Element outage may be determined from recorded relay targets or by other analysis. TOs should use the best available data to determine (1) whether a fault was associated with the outaged Element and, if so, (2) what type of fault occurred. Relay targets are not a fool proof method to determine the Fault Type; however, they may be the best available data to determine Fault Type. Relay targets should be documented as soon as practical after a fault and the targets re-set to prepare for the next fault. If a single fault results in several Element outages, the protective relay targets associated with each Element indicate the Fault Type for that Outage. An Element whose relays did not indicate a fault should be reported as No fault. Example #1: A 500 kV AC Circuit experiences a single phase-to-ground fault on the Element, outaging the Element. The AC Circuit outage also results in an outage of a 500/230 kV Transformer that is connected to the 500 kV circuit. The Transformer did not experience a fault. The AC Circuits Outage Initiation Code would be ElementInitiated and its Fault Type would be Single P-G fault. The Transformers Outage Initiation Code would be Other Element-Initiated and its Fault Type would be No fault. See guides a. and b. above. Example #2: A 500 kV AC Circuit trips when its relays operate due to a Protection System misoperation for a single phase-to ground fault on a 230/69 kV Transformer. The AC Circuits Outage Initiation Code should be entered as Other Facility-Initiated Outage (because it initiated on the Protection System, which misoperated) and the AC Circuit outage Fault Type should be reported as No fault. It does not matter if the fault was on the 230 kV or 69 kV side of the Transformer for this example. See guide d. above. Note that the Transformer outage will not be reported since it is not a TADS Element. Example #3: A single phase-to ground 230 kV bus fault results in the outages of two 230 kV AC Circuits that are connected to that bus. Each circuits Outage Initiation Code should be entered as AC Substation-Initiated. Because the bus is 200 kV or greater
and the outage was AC Substation Initiated, the AC Circuits Fault Type would be entered as Single P-G fault. See guide c. above. e. Outage which has more than one Fault Type An Element outage may have occurred due to multiple reclosing and tripouts prior to lockout (Sustained Outage) of the Element. In such a case during each reclosure different relay targets may have been initiated. The fault type may not have stayed the same during each reclosure. Many relay targets do not have a recorded time stamp. Therefore the type of fault during each reclosure may not be known. It is recognized the resulting list of relay targets is not a fool proof method to determine the Fault Type. However, the TO should use their best judgment on the type of fault encountered from a dynamic stability point of view. Guideline: TADS Definitions 12 September 29, 2009 The worst type of fault for dynamic stability is generally the above type 4 Phase-to-phase-to-ground (P-P-G), 3P, or 3P-G fault. If both Phase and Ground targets have been recorded without time stamps and are the only information available, the TO should use their best judgment whether item 4 above should be reported as the Fault Type. A lower impact fault on dynamic stability is the above item 2 Phase-to-phase fault (PP). The least impact fault is generally the above item 3 - Single phase-to-ground fault (P-G). It is recognized that a P-G type of fault may produce the highest single phase fault current. However for TADS purposes the Fault Type chosen, based on TO best judgment of what occurred, should represent the worst impact on system dynamic stability. The above guideline can be clarified by the following Example: Example 4a: Assume the following actual situation occurred at the site: A 230 kV AC circuit trips at both terminals due to a long horizontal antenna wire contacting the line. A bright arc occurs from one phase along the antenna wire to the grounded antenna mast. The bright arc disappears. Within a few seconds the antenna wire melts and whips across two phases. After 15 seconds, a bright arc occurs from one phase to the second phase. The arc does not travel to the antenna mast. The bright arc disappears. The AC conductor is not badly damaged and the conductor has returned to an energized condition. No one reports the above fireworks to the local utility. Utility knowledge of the above event: A momentary outage occurred on 230 kV AC Circuit X-Y: Both terminals X and Y initially tripped. After 15 seconds, terminal X auto-reclosed and tripped. After 15 more seconds, terminal X auto-reclosed and held. After 5 more seconds, terminal Y auto-reclosed and held. Therefore, the circuit was returned to an in-service state in 35 seconds. The utility did not have sequence of events or fault recorders at Substation X or Substation Y. From the utility office a relay technician dials-in to each substation to read the relay target information at generation Substation X and system Substation Y. The
recorded protective Relay Targets are: Instantaneous Ground current relay target at both terminals X & Y (with no time stamp on the relay targets). Terminal X also has an instantaneous Zone 1 Phase relay target (with no time stamp). No other information is available. We recognize perfect information is not available to the Utility. In such a case the Fault Type reported in TADS should be type 4 Phase-to-phase-to-ground (P-P-G), 3P, or 3P-G fault. Example 4b: 10 years later the above event occurs again. However, within that ten year period digital relays with time stamped Relay Targets have been installed. The protective relay targets reported are: Instantaneous Ground current relay target (at time equal zero) at generation Substation X & system Substation Y. [No Phase relay target at time zero.] Substation X also has an instantaneous Zone 1 Phase relay target (at time equal 15 seconds). [No additional Ground targets at time equal 15 seconds.] We recognize with the time stamp information, the fault impact on dynamic stability can now be properly reported. Based on the time stamp information the Fault Type reported in TADS should be type 2 Phase-to-Phase fault (P-P). The initial Single Phase to Ground fault had less impact. The actual fault type was not type 4 Phase-to-phase-toground (P-P-G). Relay targets are not a fool proof method to determine the Fault Type; however, they may be the best available data to determine Fault Type.
Normal Clearing
A protection system operates as designed and the fault is cleared in the time normally expected with proper functioning of the installed protection system.5 For TADS purposes, Normal Clearing also includes a Protection System operating as designed for a non-fault condition where an Automatic Outage occurs as expected with proper functioning of the installed Protection System. The Normal Clearing definition applies to the opening of circuit breakers. Subsequent automatic reclosing by the Protection System is not included in the Normal Clearing time frame. An example of a Normal Clearing event where reclosing did not function properly would be; An AC Circuit is struck by lightning (with no damage to the equipment) and the Protection System clears the fault as designed with Normal Clearing. However, the Protection System automatic reclosing equipment fails to re-energize the AC Circuit. It was expected that the breakers would reclose and return the line to an In-Service State.
Even though the Protection System failed to reclose properly, the above sequence of events is still an example of Normal Clearing as defined above.
Element-Initiated Outage
An Automatic Outage of an Element that is initiated on or within the Element that is outaged.
AC Substation-Initiated Outage
An Automatic Outage of an Element that is initiated on or within AC Substation facilities.
Mapping of Sample Misoperation Causes to "Equivalent" TADS Cause Codes Misoperation Cause
Field/Physical Execution Error Engineering/Design Issue/Error Settings Design Design Relay Failure Relay condition Substation AC Failure
- Human Error - Human Error (if NERC Registered Entity staff or Entity design contractor make the error) - Failed Protection System Equipment (if Equipment Vendor made a design error) - Failed Protection System Equipment - Failed Protection System Equipment - Failed AC Substation Equipment (if failed on the primary insulation side > 200 kV) - Failed Protection System Equipment (if failure on secondary side of relay PT, relay control system, Current Transformer core, etc.) - Failed Protection System Equipment
- Failed Protection System Equipment - Other (Use 'Other' if SCADA Control equipment failed.) (Not to be coded as Failed Protection System Equipment) - Human Error (if NERC Registered Entity staff or Entity contractor make the error)
As more experience is gained with TADS and other misoperation reporting as required by the Regions under the PRC Standards, TADS welcomes suggestions on how to make the requirements and definitions more consistent in TADS, PRC Standards, and NERC Glossary of Terms. However, based on the current TADS definitions, the above table should be used to determine the TADS Cause Code of misoperations.
Third-Party Requests
Use for Planned Outages that are taken at the request of a third party such as highway departments, the Coast Guard, etc.
System Operating Limit: The value (such as MW, MVar, Amperes, Frequency or Volts) that satisfies the most limiting of the prescribed operating criteria for a specified system configuration to ensure operation within acceptable reliability criteria. System Operating Limits are based upon certain operating criteria. These include, but are not limited to: 1. Facility Ratings (Applicable pre- and post-Contingency equipment or facility ratings) 2. Transient Stability Ratings (Applicable pre- and post-Contingency Stability Limits) 3. Voltage Stability Ratings (Applicable pre- and post-Contingency Voltage Stability) 4. System Voltage Limits (Applicable pre- and post-Contingency Voltage Limits).
Do not include actions in the last category (System Voltage Limits) since this is included in the previous System Voltage Limitation code.
6.x as an "Operational Outage". To qualify for such an outage its purpose must be to avoid an emergency or to maintain the system within operational limits. Such an Outage does not qualify as an Operational Outage. Also, it does not qualify as a "Planned Outage". There is no Operational rationale or advance notice of a Human switching error. Such an example per the above definition of "G. Planned Outage" and "H. Operational Outage" should not be coded on Form 6.x. For calendar year 2008 and 2009 such outages were reported on Form 4.x as an Automatic Outage with a "Human Error" Cause Code. The introduction of Form 6.x in 2010 does not change the coding of this example. The purpose of such an outage is not to avoid an emergency or to maintain the system within operational limits. There is no advance intent or notice of any kind. Outages resulting from circuit breaker control or protective control system automatic response to a human error are to be coded on Form 4.x as an Automatic Outage.