Transmission Availability Data System (TADS) Data Reporting Instruction Manual

Transcription

1 Version History Transmission Availability Data System (TADS) Data Reporting Instruction Manual August 8, 2013 For Calendar Year Peachtree Road NE Suite 600, North Tower Atlanta, GA of 83

2 Version History Version Date ctober 17, 2007 November 20, 2007 New Major Changes P. 4. Table 1.5, third row in the Date column. Change: December 17, 2007 was changed to January 15, P.7, Section 2.1. Addition: A new paragraph was added that defines tie line for TADS purposes. P. 14. Table 5, Column A. Addition: For the special first quarter submittal, use 2008 and not 2008Q1. That way the Event ID Codes can be used for the 2008 annual submittal as well. P. 62. AC Circuit that is directly connected to a TADS Transformer. Change: The AC Circuit and Transformer both return to service when both breakers G and H are closed. The exception for a line connected to a transformer described in the definition of In-Service State in Appendix 6, pp. 3-4 only applies to multi-terminal circuits, not two-terminal circuits. P. 67. Form 4.1. utage Code D1: This code is associated with the example on p. 62 that was changed. Change: The utage Duration was changed to 3 minutes from 1 minute utage ID Codes H2 and H3: Change: The utage Initiation Code was changed to ther Facility-Initiated since the Protection System is not part of an AC Substation. P. 67. Form 4.3. utage ID Code B2: Changes: The utage Initiation Code was changed to ther Element-Initiated (an AC Circuit) since Transformer did not initiate the reported Transformer outage. Sustained Cause Code changed Failed AC Equipment (coding error). utage ID Code D2: The utage Initiation Code was changed to ther Element- Initiated (an AC Circuit) since Transformer did not initiate the reported Transformer outage. utage ID Code G: The Fault Type was changed to None since there was no fault, just a relay misoperation. The utage Initiation Code was changed to ther Facility-Initiated since the Protection System is not part of the AC Substation. February 13, 2008 P. 1, Section We clarified that all voltages are operating voltages. P. 4, Section We added instructions on how to transmit TADS data securely via . P. 7, Section We added new language that emphasizes the need to complete the lower part of Form 1.2 that describes each form s Submission Status and Reason for Not Submitting forms. This allows us to tell whether a blank form is intended or an oversight. P. 8, Sections 2 and Form 2.1, p. 19 We required that only jointly-owned circuits are to be reported on Form 2.1. We previously required tie lines to be reported even if they were not jointly owned. We eliminated the term tie line. 2 of 83

3 Version Date Version History Major Changes February 13, 2008 P. 8, Table 2.1 and p. 19, Form 2.1 (i) We added the ability to specify a three-terminal circuit with a new column D. ther columns letters were changed accordingly. (ii) The T Element Identifier in column I is now required. With this change, it will be possible to produce outage data of jointly owned facilities for all joint owners. (iii) We extended the number of joint owners from four to ten (columns J-W). P. 9, Table 2.2 and p. 20, Form 2.2 We added a Not Applicable column F to keep the column labeling consistent between Forms 2.1 and 2.2. P. 10, Table 3.1 In column B, we clarified that the circuit inventory is not to include circuits which are not normally energized and fully connected to the system or which have not been declared commercially in service by the T. P. 12, Table 3.2 In column B, we clarified that the Transformer inventory is not to include Transformers which are not normally energized and fully connected to the system (e.g., spares) or which have not been declared commercially in service by the T. Pp , Table (Forms ) and pp , Forms (i) The T Element Identifier in column G is now required. It was previously optional. (ii) The Fault Type drop-down menus in column J were changed to correspond to updated Fault Type descriptions. In addition to being having simpler names, Fault Type 4 now includes three phase faults without a ground target. This type of fault was previously omitted. (iii) The utage Start Time date heading row label in column L was corrected to mm/dd/yyyy from dd/mm/yyyy. (iv) We also changed the utage Duration format in column M from hh:mm to hhhh:mm. Note that the format is a text field. Enter 860 hours and 20 min. as 860:20. (v) We added an utage Continuation Flag in column Q which is defined in Appendix 6, Section B. P. 15, Section 4.1 We simplified the method for recording outages that continue beyond a reporting year. This section is significantly different. P. 16, Table 5 and p. 29, Form 5 The optional description for an Event s outages in column C may be provided for any Event ID Code. It was previously restricted to Event ID Codes having an Event Type 50. P, 21, Form 3.1 The Voltage Class label for row 11 was corrected to kv DC verhead. P. 23, Form 3.3 The Voltage Class for row 4 was corrected to kv. Appendix 6 (Definitions), p. 1 For AC Circuit, we clarified that in-line sectionalizing switches inside an AC Substation are part of the AC Circuit. Also clarified that series compensation within an AC Circuit Boundaries is part of the AC Circuit, while series compensation outside of the AC Circuit boundaries is part of the AC Substation. 3 of 83

4 Version History Version Date April 4, 2008 November 21, 2008 Major Changes All circuit illustrations We consistently color-coded all breakers: red breakers are closed and green breakers are open. P. 2, Section 1.3 In the reference to Appendix 2, we changed the phrase Forms for Jointly-wned Facilities to Forms for Multiple-wner Elements. The term jointly-owned imparted a legal connotation that TADS did not intend. As an example, consider an AC Circuit that has a 50% of its length each owned separately by two Ts. In cases such as these, the physical change of ownership is usually defined at a designated structure or other landmark. In TADS, this is a multi-owner AC Circuit. Now suppose a different ownership arrangement exists whereby the entire circuit is 50% owned by each T under a joint-ownership agreement. This circuit is also a multi-owner AC Circuit. When the word facility means Element, it was changed to Element. Although similar changes appear elsewhere in the Manual regarding these terms, we do not note each incident in this version history. P. 3, Section 1.3, item 4 We had displayed columns that were not used on forms as grayed out and labeled NA. These columns are now hidden. This change was required for bulk loading on data into webtads. P. 4, Section Now that ATI is under contract with NERC for the development of webtads, we modified this section accordingly. P.11, Table 3.1 In column B, we changed the requirement to enter an NA into a blank cell. Cells without data should now be left blank. This change was required for bulk loading on data into webtads. Appendix 6 (Definitions), p.1 We stated that the terms Element and TADS Element have the same meaning. Appendix 6 (Definitions), p.12 The definition of Dependent Mode utage was clarified by removing the inclusion of Single Mode utage in the definition, which had caused confusion. Appendix 8 (Detailed Automatic utage Data Examples), p. 81 We added a note that described the correct utage Mode Code had the circuits in the example not been on common structures. P. 1, Introduction We added a reference to the Phase II requirement to keep historical supporting data for Automatic utages beginning in calendar year P. 2, Section 1.3 New Table 1.3 replaces previous text. The new table denotes what sections of the Manual contain the instructions for each form. P. 2, Section 1.3, item 4 We added new language that describes a non-reporting T and a reporting T. 4 of 83

5 Version Date Version History Major Changes November 21, 2008 P. 3, Section 1.4 We added a new section that describes who must report TADS data. To simplify administration, we do not require a non-reporting T who adds TADS Element during a reporting year to report TADS data until the next reporting year. The same consideration is given to a T who becomes newly registered during a reporting year. We describe the obligations of a reporting T who is no longer registered. P. 4, Section 1.5 We clarified how a T can change the default NERC confidentiality classification applicable to a TADS form. P. 5, Section For transmitting confidential information by , all entities should use their critical infrastructure protection (CIP) procedures. If those are not yet developed, a default method is provided. P. 5, Section 1.6 We added new language that explains the submittal of 2008 data. Section describes two changes to the 2008 Excel workbook from the previous workbook. Table has a schedule for 2008 data entry. P. 6, Section 1.7 We added new language that explains the submittal of 2009 data. Table 1.7 has a schedule for 2009 data entry. P. 7, Section We added a new section that explains the requirement to keep historical supporting data for Automatic utages beginning in calendar year P. 7, Section 1.8 We improved the explanation of webtads. P. 8, Section 1.9 We expanded the discussion on NERC IDs and T names. We describe two new Excel workbooks that contain the TADS NERC ID and T names for 2008 and P.9, Section 1.10 We included RE Coordinators as well as NERC staff in answering TADS questions. P.18, Section 4, Column L A T may now enter the utage Start Time into webtads as local time (instead of UTC) if the T is using the GUI in webtads. This feature does not apply to Ts who bulk load data. P. 18, Section 4.1 We added some examples that show the differences between a UTC calendar year (which TADS uses) and a calendar year in local time. 5 of 83

6 Version History Version Date September 29, 2009 Major Changes New Non-Automatic utage Instructions This version is the first version that has instructions for Non-Automatic utage reporting for calendar year 2010, when both Automatic and Non-Automatic utages are to be reported. For calendar year 2009, only Automatic utages are reported. As a result of adding Non-Automatic utage reporting instructions, several Non- Automatic sections/appendices were added: P. 6, Section 1.8 This section has general instructions for 2010 data entry for Automatic and Non-Automatic outages. Specific webtads enhancements are described for Non-Automatic outages. P. 23, Section 6 This section has instructions for Forms that apply to Non- Automatic utages. P. 41, Appendix 6 This section has as pictures of Forms worksheets contained in the TADS forms workbook for P. 94, Appendix 10 This section has examples for Non-Automatic utages. Renumbered Appendices Appendices 7, 8, and 9 were re-numbered from prior Appendices 6, 7, and 8. Prior Appendix 9 (Regional Entity and NERC Contacts) was replaced with a posted contacts document so that it could be easily updated see Section 1.11 for the link. UTC Time Entry As described in Section 1.7, beginning with 2009 data, utage Start Times may be entered in local times. WebTADS will offer the user a choice of local times, and webtads will convert all non-utc times to UTC and store the time as UTC in webtads. New WebTADS Error Message Interpretation Document The document is described in Section 1.9.1, and a link is provided to a posted document. n a form-by-form basis, this document shows webtads error messages and what corrections may be needed to correct the data entry error. Changes in Appendix 7 (Definitions) In addition to adding relevant Non-Automatic definitions, changes were made to clarify several definitions (listed below) as a result of questions and comments from Ts: The page numbers below are those in Appendix 7. P. 5, In-Service State; P. 8, utage Duration; and P. 18. Fault Type. A redline of Appendix 7 compared the previous Appendix 6 is posted at Ts are advised to review this redline document. Changes in Appendix 9 (Detailed Automatic utage Data Examples) This appendix has eight Automatic utage examples. The primary TADS data entries for each outage are now summarized in a table on the same page as each outage. In addition, an error was corrected in the outage on page 90 Event ID Code H The TADS worksheet on p. 91 for utage IDs H2 and H3 now has No fault as the Fault Type and ther-element Initiated as the utage Initiation Code. 6 of 83

7 Version History Version Date ctober 29, TADS Workbook (XLS) Major Changes Form 2.x Footnote (2) changed as follows: List any Multiple-wner circuit that was in-service for at least part of the reporting period. No other 2011 changes to the 2010 workbook. Data Reporting Instruction Manual (this Manual ) Multiple wner unique Element ID for use by reporting T Page 12-13?? Section 2 Form 2.x: If a Multiple-wner circuit configuration changes during the year which changes the number of circuits or mileage, list each of the configurations on Form 2.x with a different Element ID. Each multiple owner Element ID can only be used on Form 4.x and Form 6.x by the reporting T. The other multiple owners cannot use that Element ID. See Section 2 introduction and Section 2.1 Column I and J-W description. Event Identification (ID) code Form 5 format constraint does not exist. Page 21?? Form 4, Column B Event ID description, Page?? Form 5, Column A Event ID description, and Page 9?? Appendix 7 Event ID Code definition: The prior manual stated the Event ID code format should end with the reporting year, such as WXY However, webtads was originally designed to track each Ts unique Event IDs. webtads tracks each Ts Event IDs over multiple years and does not permit the same Event ID to be used twice by any given T. The above format constraint, WXY-2008, was not necessary and was not enforced by webtads. Any pattern of alphanumeric characters may be used on Form 5 to define the Event ID code. utages which continue beyond the end of the year Page 22?? Section 4.1, and page?? Section 6 utage ID data entry: Each year a new utage ID Code is required, however, the same prior year Event ID Code should be used. For any given T, over multiple years, webtads requires the T entered Form 4.x utage ID to only be used on one Automatic utage. webtads also separately tracks Form 6.x utage IDs which can only be used on one Non-Automatic utage (on Form 6.x). A unique Event ID to be used by more than one T on their Form 4.x Page 25?? Form 5 NERC Company Event ID: For a related set of two or more element Automatic utages which have different Transmission wners, a unique NERC wide Event ID code needs to be defined. webtads keeps a separate list of NERC Company wide unique Event ID codes. A NERC Company Event ID code may be established by any one T (or TADS Regional Entity Coordinator) and then used by any T on their Form 4.x. (Continued on next page) 7 of 83

8 Version History Version Date ctober 29, 2010 Major Changes Added an example of a reportable 345kV AC Circuit Non-Automatic utage during a planned 138kV outage. Page 98??, Appendix 10 See Example 3. Appendix 7 Definitions document utage which has more than one Fault Type Appendix 7 page 11??: Added guideline and Example 4a & 4b on how to determine the Fault Type to be entered on Form 4.x for an Automatic utage which has an evolving fault type during successive reclosing attempts. Clarification of Normal Clearing Appendix 7 page 13??: Added clarification for Normal Clearing of non-fault conditions. Added example of Normal Clearing prior to automatic reclosing equipment failure. Clarification of Vandalism, Terrorism or Malicious Acts Automatic utage Cause Code Appendix 7 page17??: Added clarification regarding Cyber related outages. Clarification of Automatic utage Cause Codes to be used for misoperations Appendix 7 page 19??: Added clarification regarding misoperations. Also added table of sample misoperation causes and equivalent TADS Cause Codes. Clarification of ther perational utage Non-Automatic Cause Code January 14, 2013 Appendix 7, page 21??: Added clarification and example regarding human error. Document updated to use new NERC template and styles. Sections changed to Chapters. Dates updated to reflect 2012 reporting. Chapter 5 Form for Event ID Code and Event Type Number Data Updated to use new 2012 Event Types. Chapter 7 TADS Definitions Updated Event Types to use new 2012 Event Types. Added definition for Normal Clearing Circuit Breaker Set (NCCBS). Appendix 10 Detailed Automatic utage Data Examples Updated to include new 2012 Event Types. 8 of 83

9 Table of Contents Version History... 2 Table of Contents... 9 Introduction Manual Suggestions TADS Definitions Forms verview Who Must Report...Error! Bookmark not defined. 1.5 Data Confidentiality...Error! Bookmark not defined. 1.4 Who Must Report Data Confidentiality TADS Training Calendar Year 2012 Automatic & Non-Automatic utage Reporting Calendar Year 2012 Automatic & Non-Automatic utage Reporting WebTADS - TADS Data Entry and Analysis Software NERC IDs and T Names TADS Help and TADS Contacts Administrative Forms with Transmission wner Information Chapter 2 Forms for Multiple-wner Elements Form 2.1 Multiple-wner AC and DC Circuits Form 2.2 Multiple-wner AC/DC Back-to-Back Converter Chapter 3 Forms for Element Inventory and Summary utage Data Form 3.1 AC and DC inventory Data Form 3.2 Transformer Inventory Data Form 3.3 AC/DC BTB Converter Inventory Data Form 3.4 No. of Elements with Zero Automatic utages (CY 2010 and beyond) Chapter 4 Forms for Detailed Automatic utage Data utages That Continue Beyond the End of the Year Chapter 5 Form for Event ID Code and Event Type Number Data Historical Event Type Number Cross-reference Event Analysis Guideline Event Type Number Determination Chapter 6 Forms for Detailed Non-Automatic utage Data Appendix 1 Administrative Forms with Transmission wner Information Appendix 2 Forms for Multiple-wner Elements Appendix 3 - Forms for Element Inventory and Summary utage Data Appendix 4 Forms for Detailed Automatic utage Data Appendix 5 Form for Event ID Code and Event Type Number Data Appendix 6 Forms for Detailed Non-Automatic utage Data Appendix 7 TADS Definitions Appendix 8 Inventory Data Examples Chapter 9 Detailed Automatic utage Data Examples Appendix 10 Planned utages and the 30-Minute Exclusion Examples of 83

10 Introduction From Calendar Year 2012 to Calendar Year 2013, TADS has changed to use quarterly outage reporting and annual detailed Element inventory reporting. TADS is described in two reports: 1. The Transmission Availability Data System Revised Final Report ( Phase I Report ) that was approved by the NERC Planning Committee on September 26, 2007 and by the NERC Board of Trustees on ctober 23, Phase I addresses the collection of Automatic utage data beginning in calendar year The Phase I Report can be found at %20(TADSWG)/Transmission-Availability-Data-System-Working-Group-TADSWG.aspx. 2. The Transmission Availability Data System Phase II Final Report ( Phase II Report ) that was approved by the NERC Planning Committee on September 11, 2008 and by the NERC Board of Trustees on ctober 29, Phase II addresses the collection of Non-Automatic utage data beginning in calendar year The Phase II Report can be found at %20(TADSWG)/Transmission-Availability-Data-System-Working-Group-TADSWG.aspx. Section 5.1 of the Phase II Report allows NERC to conduct data validation reviews with the submitting Transmission wners (Ts) of TADS data submissions for Automatic and Non-Automatic utages. To the extent that a review indicates systematic data entry errors, data entries for previous years may need to be revised. To facilitate the correction of potential data entry errors, Ts are required to maintain historical supporting information used to develop its TADS data for a five-year period. This requirement begins with the collection of Automatic utage Data for calendar year It is discussed in Section We developed this TADS Data Reporting Instruction Manual ( Manual ) to provide Ts with help in completing the data forms for calendar year 2013 (both Automatic and Non-Automatic utages). This version is an update of the prior TADS Data Reporting Instruction Manual. TADS has data forms, most of which have subparts, for each of the Elements for which outage information is reported. This list shows those Elements: AC Circuits 200 kv (verhead and Underground Circuits). Radial circuits are included. DC Circuits with +/-200 kv DC voltage Transformers with 200 kv low-side voltage AC/DC Back-to-Back Converters with 200 kv AC voltage, both sides 1.1 Manual Suggestions We encourage you to send suggestions for improvements to this Manual to TADSComments@nerc.net. This includes everything from typos to unclear instructions. Changes will be noted in subsequent updated versions of the Manual. 1.2 TADS Definitions The TADS Definitions document is a stand-alone document that is in Appendix 7. Most of the terms in the forms have specific definitions which may differ from the common usage of the same term. For example, the term AC Circuit is specifically defined and includes both two- and three-terminal circuits. Therefore, it is important that the T refer to the definitions when completing the forms AC and DC Voltage Classes Appendix 7 defines five Voltage Classes. Voltages are operating voltages. These cover the range of possible AC and DC voltages. For reporting, however, we have defined four AC Voltage Classes by combining two voltage ranges, of 83

11 Introduction 499 kv and kv, into one kv class since there are no AC Elements in the kv range in North America. However, all five Voltage Classes are available for DC Elements. Table 1.2: Element Voltage Classes AC Voltage Classes DC Voltage Classes kv kv kv kv kv kv kv kv kv 1.3 Forms verview The forms are depicted in Appendices 1-6 as pictures of the worksheets contained in the TADS forms workbooks. The six form categories are listed below as well as the location in the manual that has the written instructions for completing each form. Table 1.3 Form Name Appendix with Form Pictures Manual Instructions 1.1 Non-Reporting Transmission wner Statement Appendix 1 Section Reporting Transmission wner Information Appendix 1 Section Multiple-wner AC and DC Circuits Appendix 2 Section Multiple-wner AC/DC Back-to-Back Converters Appendix 2 Section AC and DC Circuit Detailed Inventory Data Appendix 3 Section Transformer Detailed Inventory Data Appendix 3 Section AC/DC Back-to-Back Converter Detailed Inventory Data Appendix 3 Section AC Circuit Detailed Automatic utage Data Appendix 4 Section DC Circuit Detailed Automatic utage Data Appendix 4 Section Transformer Detailed Automatic utage Data Appendix 4 Section AC/DC Back-to-Back Converter Detailed Appendix 4 Section 4.4 Automatic utage Data 5. ID Code and Event Type Number Data Appendix 5 Section AC Circuit Detailed Non-Automatic utage Data Appendix 6 Section DC Circuit Detailed Non-Automatic utage Data Appendix 6 Section Transformer Detailed Non-Automatic utage Data Appendix 6 Section AC/DC Back-to-Back Converter Detailed Non-Automatic utage Data Appendix 6 Section 6.4 Each data form has a common layout. 1. A T who does not own any TADS Element is referred to as a non-reporting T. Those Ts must submit Form 1.1 to its Regional Entity (RE). A T which owns TADS Elements is referred to as a reporting T. n Form 1.2, which is required for a reporting T, one portion requests the Transmission wner s name, its NERC ID number, the name of its Regional Entity (RE), its country, and the reporting calendar year. This information is input once on Form 1.2 and linked to subsequent forms. If a T owns TADS Elements in different regions and/or different countries, it must complete separate TADS submittals to for each region and country. 2. All forms except Forms , and Form 5, and Form have row numbers as well as columns with letters (A, B, etc.) The column letters and sometimes the row numbers are used as references in the instructions. Ts may add additional rows as needed. If the form has row numbers on it and you add rows, the added rows need to be numbered. 3. Many columns have drop-down menus that correspond to defined choices. For example, all Cause Codes are in a drop-down menu and provide the T the choice among the defined Cause Codes only. 11 of 83

12 Introduction 4. To keep the form format and column letter designation the same within a form type, the unused columns are hidden from view. Therefore, column letter designations will not be in sequence when a column has been hidden. Appendix 8 contains examples to assist the T in completing Forms , which contain detailed Element inventory data. Appendix 9 contains examples to assist the T in completing Forms , which contain detailed Element Automatic utage data. Appendix 10 contains examples to assist the T in completing Forms , which contain detailed Element Non-Automatic utage data. 1.4 Who Must Report For U.S. Ts, providing 2013 TADS data is mandatory for all Ts on the NERC Compliance Registry. For 2013 Non- Automatic outage TADS data, non-u.s. Transmission wners on the NERC Compliance Registry who are also NERC members are required to supply it. The reason is that as NERC members, they must comply with NERC s Rules of Procedure, and because Phase II TADS data was requested in accordance with Section 1600, these non-u.s. Transmission wners too must provide Phase II TADS data. However, NERC, through the regions, will also be requesting TADS data from non-u.s. Ts on the NERC Compliance Registry. Section 1.10 provides additional information about the registry. The following describe reporting requirements for different T situations: 1. Non-reporting Ts that do not own any TADS Elements as of the date they submit their completed Form 1.1 (in December prior to the reporting calendar year e.g., for 2009 calendar year reporting, Form 1.1 would be submitted in December 2008) are not required to report any other TADS data for the reporting calendar year even if they subsequently become owners of TADS Elements during that calendar year. However, a T may voluntarily report data for the year that the TADS Elements are added. 2. Ts that become newly registered during a reporting calendar year are not subject to any TADS reporting requirements until the next calendar year. However, a T may voluntarily report data for the year that it first becomes newly registered. 3. A non-reporting T that becomes unregistered during a calendar year is no longer subject to any TADS reporting requirements. However, if a reporting T becomes unregistered during a reporting calendar year, it has either (i) retired all its TADS Elements or (ii) sold all its TADS Elements. In case (ii), the new T shall assume the reporting obligation of the unregistered T for the entire calendar year. This will ensure that all TADS Elements continue to have their data reported Data Confidentiality Under NERC s confidentiality policy (Section 1500 of NERC s Rules of Procedures), the entity claiming that information is confidential must state the category under which such information qualifies as confidential. For practicality, data on certain forms has been judged likely confidential information because it contains critical energy infrastructure information (CEII) while other information is not confidential. A T may change NERC s default confidentiality classification in Table 1.5 by sending an to the NERC project manager see the TADS Project Manager s contact information in a Regional Entity and NERC TADS Contacts document that is posted at If a T wants non-confidential data to be made confidential, the T must indicate the category or categories defined in Section 1501 in which the data falls. See Section 1502 of the Rules of Procedure. CEII is defined by Federal Energy Regulatory Commission (FERC) rules as follows: 1 1. Critical energy infrastructure information means specific engineering, vulnerability, or detailed design information about proposed or existing critical infrastructure that: i. Relates details about the production, generation, transportation, transmission, or distribution of energy; ii. Could be useful to a person in planning an attack on critical infrastructure; 1 18 C.F.R (c)(1)-(2) 12 of 83

13 iii. Introduction Is exempt from mandatory disclosure under the Freedom of Information Act, 5 U.S.C. 552; and iv. Does not simply give the general location of the critical infrastructure. 2. (2) Critical infrastructure means existing and proposed systems and assets, whether physical or virtual, the incapacity or destruction of which would negatively affect security, economic security, public health or safety, or any combination of those matters. Table 1.5 below summarizes our judgments on confidential information for each form: Table 1.5 Form Default Confidentiality 1.1 Non-Reporting Transmission wner Statement Not confidential 1.2 Reporting Transmission wner Information Not confidential 2.1 Multi-wner AC and DC Circuits Confidential-CEII 2.2 Multi-wner AC/DC Back-to-Back Converters Confidential-CEII 3.1 AC and DC Circuit Detailed Inventory Data Confidential-CEII 3.2 Transformer Detailed Inventory Data Confidential-CEII 3.3 AC/DC Back-to-Back Converter Detailed Inventory Data Confidential-CEII 4.1 AC Circuit Detailed Automatic utage Data Confidential-CEII 4.2 DC Circuit Detailed Automatic utage Data Confidential-CEII 4.3 Transformer Detailed Automatic utage Data Confidential-CEII 4.4 AC/DC Back-to-Back Converter Detailed Automatic utage Data Confidential-CEII 5 Event ID Code and Event Type Number Data Confidential-CEII 6.1 AC Circuit Detailed Non-Automatic utage Data Confidential-CEII 6.2 DC Circuit Detailed Non-Automatic utage Data Confidential-CEII 6.3 Transformer Detailed Non-Automatic utage Data Confidential-CEII 6.4 AC/DC Back-to-Back Converter Detailed Non-Automatic utage Data Confidential-CEII As described in the Section of the Phase I Report, regional and NERC annual public performance reports will show aggregated confidential information of many Ts. In doing so, no particular T s data should be identifiable. However, these reports will not inadvertently release confidential information by the display of regional or NERC information from which a T s confidential information could be ascertained. For example, if the T in a region is the only owner of assets in a particular Voltage Class, the metrics on that data would not be released if the T s name and its confidential information could be identified, unless the T agrees to such a release. If we find that a particular T s metrics could be identified in a report, the T will be asked to voluntarily allow reporting of its metrics while keeping other aspects of its data confidential. By other aspects of its data other TADS data, such the date of an AC Circuit Sustained utage or the AC Substations that identify the outaged circuit, are meant. Those inputs allow an RE or NERC to determine whether outages of different Ts are a single Event. These requests will be addressed on a case-by-case basis Transmitting TADS Data Securely by The webtads data entry software described in Section 1.9 will transmit data securely into webtads. Therefore, e- mail will primarily be used by Ts to transmit corrections to data that must be entered by a Regional Entity coordinator or NERC staff when webtads data entry is closed to Ts. If an entity (T, RE, or NERC) has its own critical infrastructure protection (CIP) procedure for transmitting confidential information by , that procedure should be followed. If those procedures are not yet developed, the following process should be followed: 1. Password-protect the document to be transmitted, and send it via to the recipient. Do not include the password in this In a second separate , send the password to the recipient of the document. 1.6 TADS Training A TADS Training Schedule document that contains the latest training information is also posted at 13 of 83

14 Introduction Training is primarily done by Web conference, and training dates, subjects and registration information is described in the posted document. Training covers both webtads and the Manual. 1.7 Calendar Year 2013 Quarterly Automatic & Non-Automatic utage Reporting webtads opened for 2013 quarterly data entry on November 19, To allow Ts time to adjust their reporting systems, 2013Q1 and 2013Q2 data are due by September 30, The 2013 workbook may be downloaded at System-Working-Group-(TADSWG)-2013.aspx. A change was made in webtads that affects the 2009 and beyond data submittal requirement regarding the entry of utage Start Time. utage Start Times need not be entered in Coordinated Universal Time (UTC) webtads offers a choice of time zones, with UTC being the default, including data that is uploaded in XML files (created either from a TADS Excel spreadsheet or directly by the T). WebTADS will convert all non-utc times to UTC and store the time as UTC within webtads. Previously, this choice of entering the data in local time was only permitted if it was directly entered into webtads via the graphical user interface (GUI). Although data may be entered in local time, remember that each reporting calendar year is a UTC calendar year. Therefore, in the Eastern Time zone, the TADS calendar year begins on December 31 at 7:00 p.m. Eastern Time. In the Pacific Time zone, the TADS calendar year begins on December 31 at 4:00 p.m. Pacific Time. Table 1.7 has the timetable for calendar year 2013 data collection. Date August 15, 2013 September 30, 2013 ctober 1, 2013 November 15, 2013 January 1, 2014 February 15, 2014 Table 1.8 Schedule for Calendar Year 2013 Data Entry Action pen webtads for 2013 data entry for Forms 1.2, 2.x, and Form 3.x. Actual 2013 outage data entry on Forms 4.x, 5 and 6.x may begin on 01/01/2013. Reporting Ts complete submission of all 2013Q1 and 2013Q2 data. Unfreeze 2013Q1 and 2013Q2 data for changes. Reporting Ts complete submission of all 2013Q3 data. Freeze 2013Q1, 2013Q2, and 2013Q3 data. Unfreeze 2013Q1, 2013Q2, and 2013Q3 data for changes. Reporting Ts complete submission of all 2013Q4 outage data and complete an update of all detailed inventory data for All quarters are closed for T data entry. 1.8 Calendar Year 2013 Automatic & Non-Automatic utage Reporting Like 2012 data entry, several options exist to enter TADS data. A T may enter all of its data directly into webtads using the GUI interface. For large volumes of data, a T may choose to use the TADS Excel spreadsheets to create XML files for uploading the forms shown in Table 1.9 into webtads. Instead of using the TADS Excel spreadsheets, a T may choose to create their own XML files directly. The instructions on how a T can use the XML design specifications posted in webtads were made available in June 2009 for Calendar Year 2010 data entry including the Non-Automatic outage Forms 6.x. These design specifications 2 are for Ts who wish to bulk-upload their data in XML format directly into webtads and bypass data entry into Excel spreadsheets to create XML files for uploading. These same 2010 options are available for 2013 data entry. The present 2013 workbook, named X, is available at Availability-Data-System-Working-Group-(TADSWG)-2013.aspx. Editorial changes to Form 2 footnotes have been made for clarity. [See the change log in the front of this Manual.] Table 1.8 has the timetable for calendar year 2013 data collection. In contrast to prior years, webtads outage data is collected quarterly. The detailed Element inventory data is updated annually and exists perpetually across reporting 2 Similar specifications are in webtads for forms that may be bulk-uploaded. 14 of 83

15 Introduction years. During each calendar quarter, only outage information for that quarter may be entered. However, from the end of a calendar quarter to 45 days after the end of a calendar quarter, data from that quarter and previous quarters in the reporting year may be entered or modified. This process is known as freezing and unfreezing the quarterly data. nce the end of the fourth quarter collection period, 45 days after the end of the quarter, occurs, all outage data and updated inventory data should be completely entered by the T. After this date, no data entry for the reporting year will be allowed by the T. Table 1.8 Schedule for Calendar Year 2013 Data Entry Date Action August 15, 2013 pen webtads for 2013 data entry for Forms 1.2, 2.x, and Form 3.x. Actual 2013 outage data entry on Forms 4.x, 5 and 6.x may begin on 01/01/2013. September 30, 2013 Reporting Ts complete submission of all 2013Q1 and 2013Q2 data. ctober 1, 2013 Unfreeze 2013Q1 and 2013Q2 data for changes. November 15, 2013 Reporting Ts complete submission of all 2013Q3 data. Freeze 2013Q1, 2013Q2, and 2013Q3 data. January 1, 2014 Unfreeze 2013Q1, 2013Q2 and 2013Q3 data for changes. February 15, 2014 Reporting Ts complete submission of all 2013Q4 outage data and complete an update of all detailed inventory data for All quarters are closed for T data entry. 1.9 WebTADS - TADS Data Entry and Analysis Software NERC contracted with pen Access Technology International, Inc. (ATI) which developed a software data system named webtads to support several processes, including: Data entry Data error checking Data management Data analysis and reporting The webtads system allows Ts to directly enter their data or have it bulk-uploaded from XML files, which are created either from the data in entered into spreadsheets or directly by the T using the XML schema that is posted in webtads. Bulk-uploading is available for most, but not all, of the TADS forms. Table 1.9 shows which TADS forms may be bulk-uploaded and which must be directly entered into webtads. Bulk-upload capability is provided for forms that we expect to contain large amounts of data. Non-reporting Ts (those who have no TADS Elements) do not have access to webtads, while reporting Ts, REs, and NERC do have access. 4 Instructions for the use of webtads are posted within webtads itself for access by authorized persons. REs are the point of contact for TADS data submittals, and they prescribe the data entry process for Ts within their region. 1. All regions require Ts to input their data into webtads directly. Through webtads, REs will have access to the data for Ts within their region so that they can review that data. 2. WECC is collecting additional data beyond that required by TADS. For convenience, this data can now be entered into webtads and is considered voluntary. 15 of 83

16 Introduction Table 1.9 Form Can be bulk-uploaded? 1.1 Non-Reporting Transmission wner Statement No Reporting Transmission wner Information No 2.1 Multiple-wner AC and DC Circuits Yes 2.2 Multiple-wner AC/DC Back-to-Back Converters Yes 3.1 AC and DC Circuit Detailed Inventory Data Yes 3.2 Transformer Detailed Inventory Data Yes 3.3 AC/DC Back-to-Back Converter Detailed Inventory Data Yes 4.1 AC Circuit Detailed Automatic utage Data Yes 4.2 DC Circuit Detailed Automatic utage Data Yes 4.3 Transformer Detailed Automatic utage Data Yes 4.4 AC/DC Back-to-Back Converter Detailed Automatic utage Data Yes 5 Event ID Code and Event Type Number Data Yes 6.1 AC Circuit Detailed Non-Automatic utage Data Yes 6.2 DC Circuit Detailed Non-Automatic utage Data Yes 6.3 Transformer Detailed Non-Automatic utage Data Yes 6.4 AC/DC Back-to-Back Converter Detailed Non-Automatic utage Data Yes WebTADS Error Message Interpretations To aid Ts in interpreting error messages from webtads, NERC developed a document WebTADS Error Message Interpretation that is posted at TADSWG)/Transmission-Availability-Data-System-Working-Group-TADSWG.aspx. n a form-by-form basis, this document shows webtads error messages and what corrections may be needed to correct the data entry error NERC IDs and T Names Each Transmission wner is identified by a NERC ID. NERC IDs are not region-specific, i.e., the same Transmission wner may have the same NERC ID in different regions if the T owns transmission facilities in different regions. The name of each Transmission wner on the NERC Compliance Registry and its NERC ID is available at under the Compliance Registry Files file at the bottom of the page. This registry is updated monthly. 1. For TADS, pseudo NERC IDs have been assigned for various purposes, including allowing for one reporting pseudo T to make one TADS submission for multiple NERC-registered Ts that are owned by a single entity. For example, five NERC-registered Southern Company Ts were given one pseudo NERC ID for a pseudo entity named Southern Transmission Company. The pseudo NERC IDs are for TADS reporting only. A document entitled NERC ID Exceptions for TADS dated February 18, 2008 and posted at Availability Data System Working Group (TADSWG)/Transmission-Availability-Data-System-Working-Group-TADSWG.aspx explains the Ts that have been assigned pseudo NERC IDs and why they were assigned. 2. For 2013 calendar year reporting, an Excel workbook X contains the 2013 calendar year consolidated TADS NERC IDs and T names (i.e., NERC IDs from Ts on the NERC Compliance Registry as well as those with pseudo NERC IDs) as of January 11, 2013 and may be downloaded at aspx TADS Help and TADS Contacts Assistance in completing the forms is available. A list of Regional Entity and NERC staff contacts is in a Regional Entity and NERC TADS Contacts document that is posted under Related Files at the following website; 3 Non-reporting Ts will their contact data to their RE coordinator, who will input it into TADS. 16 of 83

17 The following process will be used: Introduction 1. Initial questions should be directed to RE coordinators and a copy sent to NERC at tadscomments@nerc.net. The question will be answered as soon as possible. Written questions are encouraged so that RE and NERC staff can log questions and responses. 2. Particular questions may require phone support. For phone support, call the NERC TADS Project Manager. This process is intended to ensure consistency in responses to questions and, therefore, data consistency Administrative Forms with Transmission wner Information Form 1.1 Non-Reporting Transmission wner Statement Form 1.1 is for Ts who do not own any TADS Elements as of date they submit it. It will be submitted in the December time frame of the year prior to the reporting calendar year. If a Transmission wner owns no TADS Elements as of its submission date, it provides the contact information of the person completing the form on behalf of the T who is attesting to that fact. However, if after submitting From 1.1, a TADS Element is added by the T prior to December 31 of the year prior to the reporting year, the T must notify NERC and submit Form 1.2. Form 1.2 Reporting Transmission wner Information Form 1.2 asks for three types of T information. 1. It requests the business contact information for the primary and back-up TADS contact person for the Transmission wner. 2. It contains a list to confirm which forms were filed and which forms were not filed. The list has drop-down menus for Submission Status and Reason Not Submitted for the T to explain which forms were submitted and if not submitted, why they were not submitted (e.g., T has none of the Elements reported on the form, the T had no outages, etc.). This ensures that inadvertent form omissions are corrected prior to submittal. For this reason, Form 1.2 is submitted twice during each reporting cycle: a. In December time frame of the year prior to the reporting year b. At the end of the reporting cycle with all other forms. 3. Finally, it lists the NERC default confidentiality status of T data on each form. See Section 1.5 for instructions regarding changing the default confidentiality status. 17 of 83

18 Chapter 2 Forms for Multiple-wner Elements Chapter 2 Forms for Multiple-wner Elements These forms are used to ensure that one T takes on the TADS reporting responsibility for multiple-owner Elements for all Automatic and Non-Automatic outages. If a T has less than 100% ownership interest in such Elements, each T must enter this Element on Form 2.1 or 2.2. These multiple entries should be coordinated by the Ts involved. This list of such Elements should also include any multiple-owner Element that was in-service for at least part of the reporting period. Such an Element and their associated multiple-owner Element Identifier (Column I below) should be listed on Form 2.x. The coordinated entries should indicate which single T will take reporting responsibility for Forms 3, 4, 5 and 6. The single T designated as the Reporting T (Column G-H below) must include that Element within their detailed inventory on the appropriate Form 3.x. The same Reporting T must enter the Element s outages on their Form 4 and 6. The calculated metrics are based on the reported inventory and outages. Selecting a single T to become the Reporting T for these inventory and outage Forms will avoid duplication of outage and inventory reporting. The other Ts who are multiple owners must be aware that they should not report to TADS on that Element. In addition to the names of all multiple owners, their registered NERC ID (or NERC assigned pseudo ID) of the designated reporting representative is also required to be entered on Form 2.x. If a T owns 100% of an Element, the reporting responsibility of that Element belongs to the T. Do not enter the Element on Forms 2.1 or 2.2. For 100% owned AC Circuits, communication among the Ts who own the AC Substations that bound the circuit is expected for the purpose of identifying data related to the cause of the outages which the reporting T must supply. Forms 2.x are submitted twice for each reporting cycle: 1. In December of the year prior to the reporting calendar year. 2. During Quarter 4 data reporting and the detailed inventory update. The first Form 2.x submission in December confirms who is the reporting T. The reporting T should internally collect the multiple owner outage information starting on January 1 st. webtads official data entry may occur later in the year, however, the multiple owner outage information should be collected by the designated reporting T starting January 1 st. The second submission reflects any additions or retirements of Elements that are covered by these forms. Among all of the owners for a particular Element, they must agree on the Element ID to be entered in Column I. nly the T declared to be the Reporting T on Form 2.x can use that Element ID. If one of the non-reporting T owners also enters that Element ID for an utage, the utage will be rejected as an error when they complete Form 4.x or Form 6.x. Therefore, Form 2.x must be marked as complete prior to final completion of Form 4.x and Form 6.x. When Form 4.x and Form 6.x are marked complete, software error checks are performed on each outage to confirm that the declared Element ID on Form 2.x has not been used by one of the wrong multiple owners declared on Form 2.x. 2.1 Form 2.1 Multiple-wner AC and DC Circuits The characteristics of each multiple-owner circuit are input on this form (one circuit per row). As discussed in Section 2, we expect Ts to mutually agree on who should report outage and inventory information (on Forms 3, 4, 5 and 6) of the multiple-owner circuit information for TADS and which other owners should not report. Do not enter circuits that you do not partially own. Table 2.1 Multiple-wner AC and DC Circuits Form Fields (TADS Form 2.1) Column Form 2.1 Descriptor None Questions 1 and 2 in the top of the form ask whether there were any additions of multiple-owner circuits during the reporting year and if so, whether those changes were incorporated into the response. These questions apply to the second submittal only, and appropriate NA responses are provided as an answer associated with a first submittal. A The type of circuit (AC or DC), input from a drop-down menu, describes the main characteristic of the Element. B From Substation or Terminal Name. The alphanumeric code designating one of 18 of 83

19 Chapter 2 Forms for Multiple-wner Elements Table 2.1 Multiple-wner AC and DC Circuits Form Fields (TADS Form 2.1) Column Form 2.1 Descriptor the Substation Names for an AC Circuit or one of the Terminal Names for a DC Circuit. If the Element has more than 3 Terminals, only list the first 3 Terminals. C To Substation or Terminal Name. The alphanumeric code designating a second Substation Name for an AC Circuit or a second Terminal Name for a DC Circuit. D To2 Substation or Terminal Name. The alphanumeric code designating a third Substation Name for an AC Circuit or a third Terminal Name for a DC Circuit. E The Voltage Class of the Element, input from a drop-down menu. The kv Voltage Class can only be used if AC is selected in column A, and the kv and kv Voltage Classes can only be selected if DC is selected in column A. ther Voltages Classes ( kv and kv) can be used for either AC or DC Circuits. Data that does not conform to this requirement will be rejected and an error notice provided. F Underground or verhead. This Element characteristic is input from a drop-down menu. See the definition of verhead and Underground in Appendix 7, Section A. G-H The NERC ID number and name of the T with TADS outage reporting responsibility for the multiple-owner circuit. I The reporting T s Element Identifier. This is a required data entry. The multiple owners of this Element shall also use the same Element Identifier on their Form 2.x for this Element. However, only one T can be designated as the reporting T for a given set of multiple-owners using the given Element ID. J-AD nly the Reporting T should enter the Element Identifier of Multiple-wner Elements on their Series 3 forms. The NERC ID numbers and name of the Ts that have an ownership interest in the Element. Up to ten owner names are provided. ne of the Ts must be the T with TADS reporting responsibility input in columns G-H. Among the multipleowners, only the reporting T can input the above Column I Element ID for reported outages on their Form 4.x and Form 6.x. The other multiple owners are not permitted to use the above Column I Element ID for outages reported on their Forms 4.x or Form 6.x. 2.2 Form 2.2 Multiple-wner AC/DC Back-to-Back Converter The characteristics of each multiple-owner AC/DC Back-to-Back Converter are input on this form (one Element per row). This form is not to be used for AC/DC Back-to-Back Converters owned 100% by a single T. Table 2.2 Multiple-wner AC/DC Back-to-Back Converters (TADS Form 2.2) Column Form 2.2 Descriptor None Questions 1 and 2 in the top of the form ask whether there were any additions of multiple-owner AC/DC BTB Converters during the reporting year and if so, whether those changes were incorporated into the response. These questions apply to the second submittal only, and appropriate NA responses are provided as an answer associated with a first submittal. A Converter Station Name. The alphanumeric code designating the converters name. B Reporting T s NERC ID. C Reporting T s Name D The reporting T s Element Identifier. This is a required data entry. The multiple owners of this Element shall also use the same Element Identifier on their Form 2.x for this Element. However, only one T can be designated as the reporting T for a given set of multiple-owners using the given Element ID. nly the Reporting T should enter the Element Identifier of Multiple-wner Elements on their Series 3 forms. 19 of 83

20 Chapter 2 Forms for Multiple-wner Elements Table 2.2 Multiple-wner AC/DC Back-to-Back Converters (TADS Form 2.2) Column Form 2.2 Descriptor E The AC Circuit Voltage Class, input from a drop-down menu, on one side of the converter F The AC Circuit Voltage Class, input from a drop-down menu, on the other side of the converter G-H The NERC ID number and name of the T with TADS reporting responsibility. I-AE The NERC ID numbers and names of the Ts that are multiple owners of the Element. Up to four owner names are provided. ne of the Ts must be the T with TADS reporting responsibility input in column G-H. 20 of 83

21 Chapter 3 Forms for Element Inventory and Summary utage Data Chapter 3 Forms for Element Inventory and Summary utage Data 3.1 AC and DC Inventory Data Form 3.1 records the detailed inventory details for AC and DC Circuit Elements. The inventory details should be updated with the 4 th quarter reporting. If entering an outage on a circuit not in the inventory detail, the identifier and circuit mileage should be entered to allow validation of the Element. Table 3.1: AC Circuit and DC Circuit Detail Inventory Form (* Indicates Mandatory for 2013Q4 Update) Column Form 3.1 Field Name Form 3.1 Descriptor A Unique Element Identifier* A T defined unique Element Identifier. Element Identifiers cannot be reused in any future reporting period for a different Element. If there are multiple owners of the Element, those Ts must agree on the Element Identifier. B Voltage Class* The Element s Voltage Class. AC Circuit= phase-to-phase DC Circuit= phase-to-return The kv Voltage Class can only be used if AC is selected in column C, and the kv and kv Voltage Classes can only be selected if DC is selected in column C. Data that does not conform to this requirement will be rejected and an error notice provided. C Circuit Type* AC = verhead AC Circuit Element ACC = Underground AC Circuit Element DC = verhead DC Circuit Element DCC = Underground DC Circuit Element D-F From Bus, To Bus, and Tertiary Bus* Data that provides a description of the physical location of the Element. AC Circuit = AC Substation Names (3 max) G Circuit Miles* The Circuit Mileage of the Element. For TADS purposes, a DC Circuit is assumed to have 2 poles. For example, a one-mile long DC Circuit with 2 poles would be reported as having 1 DC Circuit Mile. H Number of Terminals* The number of terminals that the Element connects to. I The AC Multi-wner Common Structure Flag. This flag is explained in Appendix 7, Section B where the term is fully defined. J Conductors per Phase The number of conductors on the Element per Phase. K verhead Ground Wire The number of overhead ground wires on the Element. L Insulator Type The type of insulator used on at least 80% of the Element. If multiple types are used such that at least 80% of the Element does not comprise one type, selected Mixed. CEP = Ceramic Post CES = Ceramic Suspension PP = Polymer Post PS = Polymer Suspension GLS = Glass Suspension MXD = Mixed TH = ther 21 of 83

22 Chapter 3 Forms for Element Inventory and Summary utage Data M Cable Type The type of cable used on the Element. SWD = Solid with conduit SND = Solid with no conduit WD = il filled with conduit ND = il filled with no conduit GWD = Gas filled with conduit GND = Gas filled with no conduit. N Structure Materials The type of structure materials used on at least 80% of the Element. If multiple types are used such that at least 80% of the Element does not comprise one type, selected Mixed. AL = Aluminum CN = concrete FG = fiberglass ST = steel WD = wood CM = composite T = other MX = mixed. Structure Types The type of structure materials used on at least 80% of the Element. If multiple types are used such that at least 80% of the Element does not comprise one type, selected Mixed. DLC = Double Lattice Column HFR = H Frame KFR = K Frame LAT = Lattice Tower SPG = Single Pole Guyed SPU = Single Pole Un-guyed DP = Double Pole SLC = Single Lattice Column YTY = Y Type TH = other MXD = Mixed. P Circuits per Structure The number of circuits per structure on the Element. Q Terrain The type of structure materials used on at least 80% of the Element. If multiple types are used such that at least 80% of the Element does not comprise one type, selected Mixed. If multiple types are applicable, pick the type the most influences outages. C = Coastal DS = Desert MT = Mountains FR = Forest UR = Urban PR = Prairie MX = Mixed. R Elevation Enter the range of elevation that the circuit traverses. 1 = less than 2000ft. 2 = 2001 to 4000ft. 3 = 4001 to 6000ft. 4 = 6001 to 8000ft. 5 = 8001 to 10000ft. 6 = to 12000ft. 99 = elevation varies more than 2000ft. 22 of 83

23 S Chapter 3 Forms for Element Inventory and Summary utage Data Change/Reconfiguration Date* Enter the date (mm/dd/yyyy) that the Circuit Mileage of the Element last changed or the initial in-service date. If this is prior to January 1, 2013, please use January 1, 2013 as the Change/Reconfiguration Date. T Retirement Date* If applicable to the Element, the date the Element became out-ofservice. U Precursor Element Identifier* The Unique Element Identifier that precedes the Element. This is used to maintain a parent/child relationship as Elements are modified. V BES Exempted Flag Reserved for future use. 3.2 Transformer Detailed Inventory Data Form 3.2 records the detailed inventory details for Transformer Elements. The inventory details should be updated with the 4 th quarter reporting. If entering an outage on a circuit not in the inventory detail, the identifier should be entered to allow validation of the Element. Table 3.2: Transformer Detail Inventory Form (* Indicates Mandatory for 2013Q4 Update) Column Form 3.1 Field Name Form 3.1 Descriptor A Unique Element Identifier* A T defined unique Element Identifier. Element Identifiers cannot be reused in any future reporting period for a different Element. If there are multiple owners of the Element, those Ts must agree on the Element Identifier. B Located at (AC Substation The substation name where the transformer is located. Name)* C High-Side Voltage Class* The Transformer s High-Side Voltage Class. D Low-Side Voltage Class* The Transformer s Low-Side Voltage Class E Phasing The phasing of the Transformer. Single = 3-Phase Bank Single Phase of 3-Phase Bank = A single phase of a 3-phase bank F Three Phase Rating The rating, in MVA, of the Transformer (all 3-phases combined). G Change/Reconfiguration Date* Enter the date (mm/dd/yyyy) that the Element last changed or the initial in-service date. If this is prior to January 1, 2013, please use January 1, 2013 as the Change/Reconfiguration Date. H Retirement Date* If applicable to the Element, the date the Element became out-ofservice. I Precursor Element Identifier* The Unique Element Identifier that precedes the Element. This is used to maintain a parent/child relationship as Elements are modified. U BES Exempted Flag Reserved for future use. 3.3 AC/DC BTB Converter Inventory Data Form 3.3 records the detailed inventory details for AC/DC Back to Back Converter Elements. The inventory details should be updated with the 4 th quarter reporting. If entering an outage on a circuit not in the inventory detail, the identifier should be entered to allow validation of the Element. Table 3.3: AC/DC Back to Back Converter Detail Inventory Form (* Indicates Mandatory for 2013Q4 Update) Column Form 3.1 Field Name Form 3.1 Descriptor A Unique Element Identifier* A T defined unique Element Identifier. Element Identifiers cannot be reused in any future reporting period for a different Element. If there are multiple owners of the Element, those Ts must agree on the Element Identifier. B Converter Name The substation name where the AC/DC BTB Converter is located. 23 of 83

24 Chapter 3 Forms for Element Inventory and Summary utage Data C Voltage Class* The AC/DC BTB Converter s Voltage Class. D Change/Reconfiguration Date* Enter the date (mm/dd/yyyy) that the Element last changed or the initial in-service date. If this is prior to January 1, 2013, please use January 1, 2013 as the Change/Reconfiguration Date. E Retirement Date* If applicable to the Element, the date the Element became out-ofservice. F Precursor Element Identifier* The Unique Element Identifier that precedes the Element. This is used to maintain a parent/child relationship as Elements are modified. G BES Exempted Flag Reserved for future use. 3.5 AC Multi-Circuit Structure Miles In contrast to the detailed inventory in Forms 3.1, 3.2, and 3.3, AC Multi-Circuit Structure Miles are collected on a summary basis. The bottom half contains Multi-Circuit Structure Mile data for AC Circuits only. If a line section contains two or more common structures which form one or more multi-circuit spans, the total span length can be measured and the associated mileage should be reported in the Multi-Circuit Structure Mile data. If multiple circuits are connected to only one common structure, that structure should be ignored for outage and inventory mileage purposes. All DC Circuits are assumed to have two circuits per structure; therefore, for each DC Circuit Voltage Class, the Multi- Circuit Structure Miles is one-half of the total Circuit Miles. Table 3.5 Column Form 3.5 Descriptor None Questions 1 and 2 ask whether the coordination requested below for AC Multi- Circuit Structure Miles Inventory Data has taken place among Ts that report separate circuits on common structures. AC Multi-Circuit Structure Miles Inventory Data Appendix 7 has an example that illustrates the data requirements for columns B-K for Multi- Circuit Structure Miles. 1. Note: Multi-circuit structures that are occupied by only one circuit do not contribute to the tabulation of Multi-Circuit Structure Miles. 2. Appendix 7 illustrates how to make this calculation for an annual submittal. For common structures that carry circuits owned by different Ts, we expect the Ts 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 Ts occupy common structures for 10 miles. For this section, the combined number of Multi- Circuit Structure Miles reported by the Ts should not exceed 10. We do not want each T to report 10 miles since that would double count the miles for the region. A AC multi-circuit structure Voltage Class. Note the Mixed Voltage class. This class applies to multi-circuit structures that have two TADS AC Circuits of different voltages (e.g., 230 kv and 345 kv) on the same structure. A structure is not a considered a multi-circuit structure for TADS reporting unless it has two or more AC Circuits, each circuit with a voltage 200 kv. Therefore, a structure with a 230 kv and a 138 kv AC Circuit does not contribute to the tabulation of Multi-Circuit Structure Miles. B NT APPLICABLE C The number of Multi-Circuit Structure Miles in the Voltage Class associated with AC Circuits reported by the T at the end of the reporting year. This includes AC Circuits that are multiple-owner circuits that are reported by the T. If you have no multi-circuit structures in a particular Voltage Class, a blank is the default entry in columns C, F, G, J, and K. 24 of 83

25 Chapter 3 Forms for Element Inventory and Summary utage Data D-E F G H-I J K L M N-Q NT APPLICABLE The number of Multi-Circuit Structure Miles added in the Voltage Class associated with AC Circuits reported by the T. The equivalent number of Multi-Circuit Structure Miles added. NT APPLICABLE The number of Multi-Circuit Structure Miles removed in the Voltage Class associated with AC Circuits reported by the T. The equivalent number of Multi-Circuit Structure Miles removed. NT APPLICABLE This is a calculated value for the equivalent annual number of Multi-Circuit Structure Miles for the reporting year. Note that column J is not used; it is requested as a sanity check for column K. NT APPLICABLE 3.6 Common Corridors The Common Corridor form, Form 3.6, is only for WECC entities. Please use the established Common Corridor definitions to populate the form. 25 of 83

26 Chapter 4 Forms for Detailed Automatic utage Data Chapter 4 Forms for Detailed Automatic utage Data These forms contain data for each and every Automatic utage of an Element, both Sustained and Momentary. This form does not have row numbers. Since each line represents an outage and each outage has a unique utage ID Code, this code is used to identify outage entry. Since there is so much similarity between the columns, all descriptors will be provided once, using the generic term of Element instead of AC Circuit, Transformer, etc. Appendix 8 provides many examples illustrating the completion of the various Form 4 series. Table Data for Elements That Had an Automatic utage Column Forms Descriptor A The utage ID Code assigned to the outage. This is assigned by the T. See Appendix 7, Section B for the definition of utage ID Code. For any given T, over multiple years, webtads requires the T entered Form 4.x utage ID to be used only once on an Automatic utage (on Form 4.x). B The Event ID Code associated with the outage. This is assigned by the T on Form 5. See Appendix 7, Section B for the definition of Event ID Code. The Event ID Code used on Form 4.x must be pre-defined on Form 5.. C A T defined unique Element Identifier. Element Identifiers cannot be reused in any future reporting period for a different Element. If there are multiple owners of the Element, those Ts must agree on the Element Identifier. The descriptions that follow use defined terms that the T 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. D The Fault Type (if any) for each circuit utage, input from a drop-down menu. E The utage Initiation Code, input from a drop-down menu. F The utage Start Time. This may be local time or UTC time. WebTADS will offer a choice of time zones, with UTC being the default. This applies whether the data is entered directly into webtads or bulk-uploaded via XML files (created either from an Excel workbook or directly by the T). WebTADS will convert all non-utc times to UTC and store the time as UTC within webtads. G H I J K The use of UTC will allow related outages occurring on Elements reported by different Transmission wners to be linked. See instructions Section 4.1 below for outages that continue beyond the end of the reporting calendar year. The utage Time Zone. The Time Zone of the reported utage. The utage Duration expressed as hours and minutes. Momentary utages 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 utage Duration exceeds the number of hours remaining in the year (based upon the utage 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. The Initiating Cause Code, input from a drop-down menu. All utages must supply an Initiating cause code. The Sustained Cause Code, input from a drop-down menu. This only applies to Sustained utages. Momentary utages enter NA-Momentary. The utage Mode, input from a drop-down menu. 26 of 83

27 Chapter 4 Forms for Detailed Automatic utage Data Column L Table Data for Elements That Had an Automatic utage Forms Descriptor The utage 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 7, Section B where the term is fully defined. 4.1 utages That Continue Beyond the End of the Year Although data may be entered in local time, remember that each reporting calendar year is a UTC calendar year. Therefore, in the Eastern Time zone, the TADS calendar year 2010 begins on December 31, 2009 at 7:00 p.m. Eastern Time. In the Pacific Time zone, the TADS calendar year 2010 begins on December 31, 2009 at 4:00 p.m. Pacific Time. If an outage begins in a reporting calendar year and continues beyond the end of the year (December 31), the calculation of a total utage Duration is not possible. In this case, the following process will be observed. 1. Two separate utage Durations will be input. a. For the reporting year when the outage started, the T inputs the utage Start Time and calculates an utage Duration from the utage Start Time until the end of the reporting calendar year. The utage Continuation Flag is input as 1. See Appendix 7, Section B for a complete description of this flag. b. For the next reporting year, the utage Continuation Flag is input as 2 and the same Event ID Code (defined on the prior year Form 5) will be entered. The utage Start Time is equal to January 1, 00:00 UTC of that reporting year. Each year a new utage ID Code is required, however, the same prior year Event ID Code should be used. If the outage is concluded in that reporting year, an utage Duration is calculated from the utage Start Time. If the outage continues to the subsequent reporting year, the utage Duration is entered as 8760:00, or 8784:00 for a leap year. The utage 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. The same Event ID Code (defined on Form 5 in the first year) is used for all subsequent years. 2. For purposes of calculating metrics, the metrics in the first reporting year will reflect the outages in that year for frequency calculations. However, the utage Duration will be split between reporting years as described above, and any outages with Event ID Codes from the prior year will not be counted towards the frequency calculation in subsequent years. An outage with a Continuation Flag equal to 2 is ignored in the frequency calculations. However, such an outage is included in the calendar year duration calculations. 27 of 83

28 Chapter 5 Form for Event ID Code and Event Type Number Data T s assign their own Event ID Codes and associated Event Type Numbers. An Event is a transmission incident that results in the Sustained or Momentary utages of one or more Elements. The table below describes the data collected for the Event ID Code: Table 5 Column Form 5 Descriptor A The Event ID Code associated with one or more outages. This is assigned by the T. See Appendix 7, Section B for the definition of Event and Event ID Code. For a given T the same Event ID Code cannot be defined more than once on Form 5. The T cannot define the same code again on Form 5 in any subsequent year. B The Event Type No. This is a descriptor of the Event. The table on Form 5 shows the permitted entries, which are in a drop-down menu. Note that if Event Type No. 10 or 20 is selected, the utage Mode on Forms 4.1, 4.2, or 4.3 (column P) must be "Single Mode utage." Table and Table show the possible Event Type Numbers. See Appendix 7, Section B for the definitions of Normal Clearing, NCCBS, Abnormal Clearing, Delayed Fault Clearing, SPS or RAS, and Event Type Number. A consistent set of definitions is necessary to determine the Event Type Number to be entered in Column B. C ptional input: Provide a brief description of the Event s outage(s) for any Event ID Code. Please limit the description to 500 characters or less. D This field indicates whether a disturbance report was filed that was associated with the Event, with the choices contained in a drop-down menu (Yes, No, or Don t know). Year-to-date public (i.e., non-confidential) data of all disturbance report filings are located at For example, a T will know which region its facilities reside (Region ID), but it should also know its associated Balancing Authority (BA) identified by a Balancing Authority ID. Since the posted information is available in a sortable Excel file, a T should first sort by its region and BA to determine if any of its Events had a possible disturbance report associated with it. If no disturbances were reported for the T s region and BA, then the T should answer No. If some disturbances were reported, the T should then examine the disturbance start and end dates and times on the posted information and compare them to the start and end dates and times associated with the individual outages associated with an Event ID. If this comparison shows that the T s Event outage times are not inside any disturbance report time windows, then the T should answer No. n the other hand, if a disturbance time interval and an Event time interval overlap, the column with the Event Description may provide enough information to determine whether the T should answer Yes. If it cannot be determined accurately from the Event Description, then the T should answer Don t know. Every Don t know answer is followed up by the Regional Entity coordinators. 28 of 83

29 Chapter 5 Form for Event ID Code and Event Type Number Data Event Type Number Table Events with Normal Clearing Description 05 Single bus section fault or failure (200kV or above) resulting in one or more Automatic utages. 06 Single internal circuit breaker fault (200kV or above) resulting in one or more Automatic utages. 11 Automatic utage of a single Element. 13 Automatic utage of two or more Elements within one Normal Clearing Circuit Breaker Set (NCCBS). 31 Automatic utages of two or more TADS adjacent AC Circuits or DC Circuits on common structures. To qualify as Event Type Number 31 the Automatic utages must be the direct result of the circuits occupying common structures. 49 Automatic utage(s) with Normal Clearing not covered by Event Type Numbers 05 through 31 above. All of the above Event Type Numbers, 05 to 49, are Events with Normal Clearing. For further explanations and examples regarding the determination of the proper Event Type Numbers, see Appendix 7 Section B definitions for Normal Clearing, NCCBS, Abnormal Clearing, Delayed Fault Clearing, SPS or RAS, and Event Type Number. These Event Type Numbers apply only when the Automatic utages are the result of Protection Systems and controls disconnecting the elements that are expected to be automatically disconnected for a single event. In contrast, the term Abnormal Clearing is for an Event when Normal Clearing did not occur. Non-TADS Element utages: Please note Event Type Number 11 (Automatic utage of a single Element) is intended to include a single Automatic utage resulting from one or more non-tads Element outages. This type of Event should not be entered as Event Type Number 49 other Normal Clearing. If the Element outage results from one or more non-tads Element outages, the utage Initiation Code (Form 4) should be entered as Dependant Mode. During annual report preparation to provide further analysis, Event Type Number 11 outages may be parsed and summarized by the utage Mode Codes of Single Mode and Dependant Mode. Event Type Number 13 versus Event Type Number 11: Event Type Number 13 is similar to Event Type Number 11 except a total of two or more Element outages occur within one NCCBS. By keeping type 13 separate from type 11, more statistical granularity can be maintained in the annual report. Also, in a similar fashion to the previous paragraph, if two or more Automatic utages occur (within one NCCBS) resulting from one or more non-tads Element outages, the Event Type Number 13 should be entered and the utage Initiation Code (Form 4) should be entered as Dependant Mode on each Automatic utage. If two or more Automatic utages occur outside the one NCCBS, do not enter Event Type Number 13. See the Event Analysis Guideline below. Event Type Number Table Events with Abnormal Clearing Description 60 Breaker Failure: ne or more Automatic utages with Delayed Fault Clearing due to a circuit breaker (200kV and above) being stuck, slow to open or failure to interrupt current. 61 Dependability (failure to operate): ne or more Automatic utages with Delayed Fault Clearing due to failure of a single Protection System (primary or secondary backup) under either of these conditions: a. failure to initiate the isolation of a faulted power system Element as designed, or within its designed operating time, or b. In the absence of a fault, failure to operate as intended within its designed operating 29 of 83

30 Chapter 5 Form for Event ID Code and Event Type Number Data Event Type Number Table Events with Abnormal Clearing Description time. (Item b is a very rare type of event.) 62 Security (unintended operation): ne or more Automatic utages caused by improper operation (e.g. overtrip) of a Protection System resulting in isolating one or more TADS Elements it is not intended to isolate, either during a fault or in the absence of a fault. 90 Automatic utage(s) with Abnormal Clearing not covered by Event Types 60 through 62 above. All of the above Event Type Numbers, 60 to 90, are Events with Abnormal Clearing. For further explanations and examples regarding the determination of the proper Event Type Numbers, see Appendix 7 Section B definitions for Normal Clearing, NCCBS, Abnormal Clearing, Delayed Fault Clearing, SPS or RAS, and Event Type Number. Event Description: An optional event description may be entered on Form 5 in the Description column. In general for Event Type Numbers 05 to 31 (Normal Clearing), and Event Types 60 to 62 (Abnormal Clearing) a description is not needed but may be entered. However, for Event Type Number 49 (other Normal Clearing) or 90 (other Abnormal Clearing), entering a description of the Event would be helpful. Such a description is not mandatory but would provide further clarification of these Events. 5.1 Historical Event Type Number Cross-reference The following table shows the previous Event Type numbers and how they map to the new Event Type numbers. Table 5.2 Previous Event Type Numbers ( ) New Event Type Numbers (Starting 1/1/2012) Separated into 2 categories: Normal Clearing 05, 06, 13, 49; Abnormal Clearing - 60, 61, 62 and Event Analysis Guideline When using the revised Event Type Numbers, to reduce the amount of analysis labor required to determine the Event Type code numbers, the following step by step process contains a sample of logical questions and answers to quickly determine the appropriate Event Type Number to be entered on Form 5. Several examples are included in this Instruction Manual with both the given Automatic utage (Form 4.x) attributes and after using the Steps below, the appropriate determination of Event Type (Form 5). Data entries for each scenario are shown in tables along with each scenario. While not all possible situations could be covered, the examples are complete enough to illustrate Event Type determination. The process below assumes that all Automatic utage information required for completion of Form 4.x have already been collected and are available to the user. The user should be familiar with the TADS definitions in Appendix 7 for Normal Clearing, NCCBS, Abnormal Clearing, Delayed Fault Clearing, SPS or RAS, Event, Event ID Code, and Event Type Number Form 4.x data and associated event analysis is necessary for the determination of the Event Type number to be entered on Form 5. Event Type analysis should not begin until a complete set of Automatic utages associated which each Event is ready for entry on Form 4.x including their associated event identification (Event ID) code. The analysis Steps below are intended to reduce the labor resources to complete the determination of Event Type for entry on Form 5. The Steps below will not reduce the labor needed to determine the Form 4 data to be entered for each Automatic utage. This is a guideline and exceptions can be made as deemed necessary to determine the appropriate 30 of 83

31 Chapter 5 Form for Event ID Code and Event Type Number Data Event Type. It is anticipated that the overwhelming majority of Automatic utages ( 2 of every 3 outages) will be a simple Normal Clearing of a single Element Automatic utage which did not result from a bus outage or internal circuit breaker fault. For such cases, no additional resources will be necessary to determine the Event Type. nly Steps N1 and N3.1 below will be needed to determine the Event Type Number. 5.3 Event Type Number Determination Begin at Step N1 with a set of one or more Automatic utages entered on Form 4.x that has a unique Event ID Code. Follow the process until an Event Type Number for each Event is determined. Step N1 - Normal Clearing determination Did Normal Clearing occur? (Refer to examples below.) Yes Proceed with Step N2) Normal Clearing below. No Proceed with Step A1) Abnormal Clearing. Example of an Event with Normal Clearing For a given Event ID and its associated Automatic utages, an Event which results from one or more unintended 200kV or above circuit breaker operations or unintended delayed clearing should be coded as Abnormal Clearing. Abnormal Clearing, per Section B definition, is the outage of a TADS Element that does not conform with Normal Clearing. For example, any 200kV or above unintended circuit breaker operations which occur beyond the Normal Clearing Circuit Breaker Set (NCCBS) and results in a total of two or more Automatic utages should be categorized as Abnormal Clearing. In addition, Delayed Fault Clearing of any one Automatic utage is also categorized as Abnormal Clearing. Example of an Event with Normal Clearing beyond the NCCBS As intended, Special Protection System (SPS) or Remedial Action Scheme (RAS) may normally trip additional 200kV or above circuit breakers beyond the NCCBS. For a given Event ID and its associated Automatic utages, an Event which results from one or more expected SPS or RAS normal operations should be coded as Normal Clearing. Step N2 - Screen for Event Type Numbers 05 and 06 If one or more Automatic utages were the result of a Bus Section fault or failure, enter Event Type Number 05. If one or more Automatic utages were the result of a single internal circuit breaker fault, enter Event Type Number 06. If not Event Type Number 05 or 06, then proceed with Step N3 below. Step N3 Screen for Event Type Numbers 11 and 13 N3.1) If the utage Mode Code was Single Mode utage, enter Event Type Number 11. N3.2) For an Event ID with a total of two or more Automatic utages that occur within one Normal Clearing Circuit Breaker Set (NCCBS), enter Event Type Number13. The utage Mode Codes on Form 4.x should be Dependent Mode Initiating utage or Dependent Mode utage. If not Event Type Number 11 or 13, then proceed with Step N4 below. Note: for a given Event ID code, each Automatic utage on Form 4.x has one of the following utage Mode Codes. Single Mode utage Dependent Mode Initiating utage Dependent Mode utage Common Mode utage Common Mode Initiating utage 31 of 83

32 Chapter 5 Form for Event ID Code and Event Type Number Data Step N4 Screen for Event Type Number 31 If two or more Automatic utages of TADS adjacent AC Circuits or DC Circuits were the direct result of the Elements occupying common structures, enter Event Type Number 31. If not Event Type Number 31, then proceed with Step N5 below. Step N5 Screen for Event Type Number 49 ther Normal Clearing If the Event included other Normal Clearing not covered by Event Type Number 05 to 31, enter Event Type Number 49. Examples of an Event Type Number 49: Event Type #49 includes, but is not limited to, Normal Clearing of two or more Normal Clearing Circuit Breaker Sets (NCCBS). For example an airplane crash causes Automatic utages of two AC Circuits on a common right-of-way. Both circuits trip as expected with Normal Clearing. Event Type #49 should be used for such an event. Event Type #49 also includes additional Automatic utages with Normal Clearing which are initiated by Special Protection Systems (SPS), Remedial Action Schemes (RAS), Under Voltage Load Shedding (UVLS), Under Frequency Load Shedding (UFLS), etc. Step A1 - Abnormal Clearing Did Abnormal Clearing occur? (Refer to examples in Step N1.) Yes Proceed with Step A2. No Return to Step N1. Step A2 Screen for Event Type Number 60; Breaker Failure Among the relay targets associated with this Event, did a Breaker Failure (BF) time-delayed relay target occur on one or more 200kV and above circuit breakers? Did this time-delayed relay operate as intended? If the answer to both of these questions is yes, enter Event Type Number 60. If one or more Automatic utages experienced Delayed Clearing due to one or more 200kV and above circuit Breaker Failures (BF), enter Event Type Number 60. If the BF relay scheme did not operate as intended, go to Step A3 below. Such delayed clearing examples include, but are not limited to, a circuit breaker being stuck, or slow to open, or failure to interrupt current. Such failures usually cause a circuit BF time-delayed relay to operate. Therefore, a BF relay target also occurs. If not Event Type Number 60, then proceed with Step A3 below. Step A3 Screen for Event Type numbers 61 and 62; Dependability or Security Failures Dependability (failure to operate); If one or more Automatic utages experienced delayed clearing due to a Dependability failure to operate, enter Event Type Number 61. A Dependability failure includes, but is not limited to, a failure of the Protection System (primary or secondary/backup scheme) to: initiate the isolation of a faulted power system Element, or failure to operate within its designed operating time, or failure to operate as intended for non-fault conditions within its designed operating time. Security (false or undesirable operations): If one or more Automatic utages are caused by a Security failure, enter Event Type Number of 83

33 Chapter 5 Form for Event ID Code and Event Type Number Data A Security failure includes improper operation of a Protection System (or its controls): in absence of a fault on the power system TADS Element, or during a fault it is not designed to protect. If not Event Type Number 60, 61 or 62 then proceed with Step A4 below. Step A4 Screen for Event Type Number 90; ther Abnormal Clearing If the Event included other Abnormal Clearing not covered by Event Type Number 60, 61 or 62, enter Event Type Number 90. Example of an Event Type Number 90 Event Type Number 90 includes, but is not limited to, additional Automatic utages with Abnormal Clearing which are initiated by Special Protection Systems (SPS), Remedial Action Schemes (RAS), Under Voltage Load Shedding (UVLS), Under Frequency Load Shedding (UFLS), etc. It also includes Abnormal Clearing of multiple faults or failures which are not covered by Event Type Number 60 to 62. For additional examples for determining the Event Type Number for Normal Clearing and Abnormal Clearing Events, see Appendix 9 Detailed Automatic utage Data examples. 33 of 83

34 Chapter 6 Forms for Detailed Non-Automatic utage Data These forms contain data for each and every Non-Automatic utage of an Element, both Planned and perational. This form does not have row numbers. Since each line represents an outage and each outage has a unique utage ID Code, this code is used to identify outage entry. Table Data for Elements That Had an Automatic utage Column Forms Descriptor A The utage ID Code assigned to the outage. This is assigned by the T. See Appendix 7, Section B for the definition of utage ID Code. For any given T, over multiple years, webtads requires the T entered Form 4.x utage ID to be used only once on an Automatic utage (on Form 4.x). B A T defined unique Element Identifier. Element Identifiers cannot be reused in any future reporting period for a different Element. If there are multiple owners of the Element, those Ts must agree on the Element Identifier. C Non-Automatic utage Type. Please refer to Appendix 7 for the definition of Non-Automatic utage Types. The descriptions that follow use defined terms that the T 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. D The utage Start Time. This may be local time or UTC time. WebTADS will offer a choice of time zones, with UTC being the default. This applies whether the data is entered directly into webtads or bulk-uploaded via XML files (created either from an Excel workbook or directly by the T). WebTADS will convert all non-utc times to UTC and store the time as UTC within webtads. E F G H I The use of UTC will allow related outages occurring on Elements reported by different Transmission wners to be linked. See instructions Section 4.1 below for outages that continue beyond the end of the reporting calendar year. The utage Time Zone. The Time Zone of the reported utage. The utage Duration expressed as hours and minutes. Momentary utages 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 utage Duration exceeds the number of hours remaining in the year (based upon the utage 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. The Planned utage Cause Code, input from a drop-down menu. All Planned utages must supply an cause code. perational utages enter NA. The perational Cause Code, input from a drop-down menu. This only applies to perational utages. Planned utages enter NA. The utage 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 7, Section B where the term is fully defined. 34 of 83

35 Chapter 6 Forms for Detailed Non-Automatic utage Data 6.1 utages That Continue Beyond the End of the Year Although data may be entered in local time, remember that each reporting calendar year is a UTC calendar year. Therefore, in the Eastern Time zone, the TADS calendar year 2010 begins on December 31, 2009 at 7:00 p.m. Eastern Time. In the Pacific Time zone, the TADS calendar year 2010 begins on December 31, 2009 at 4:00 p.m. Pacific Time. If an outage begins in a reporting calendar year and continues beyond the end of the year (December 31), the calculation of a total utage Duration is not possible. In this case, the following process will be observed. 1. Two separate utage Durations will be input. a. For the reporting year when the outage started, the T inputs the utage Start Time and calculates an utage Duration from the utage Start Time until the end of the reporting year. The utage Continuation Flag is input as 1. See Appendix 7, Section B for a complete description of this flag. b. For the next reporting year, the utage Continuation Flag is input as 2. The utage Start Time is entered as January 1, 00:00 UTC of that reporting year. If the outage is concluded in that reporting year, an utage Duration is calculated from the utage Start Time. If the outage continues to the subsequent reporting year, the utage Duration is entered as 8760:00, or 8784:00 for a leap year. 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. 2. For purposes of calculating metrics, the metrics in the first reporting year will reflect the outage in that year for frequency calculations. However, the utage Duration will be split between reporting years as described above, and any outages from the prior year will not be counted towards the frequency calculation in subsequent years. An outage with a Continuation Flag equal to 2 is ignored in the frequency calculations. However, the outage is included in the calendar year duration calculations. 35 of 83

36 Appendix 1 Administrative Forms with Transmission wner Information 1.1 Non-Reporting Transmission wner Statement 36 of 83

37 Appendix 1 Administrative Forms with Transmission wner Information 1.2 Reporting Transmission wner Information Form 1.2: 37 of 83

38 Appendix 2 Forms for Multiple-wner Elements 2.1 Multiple-wner AC and DC Circuits Continued 38 of 83

39 2.2 Multiple-wner AC/DC Back-to-Back Converters Appendix 2 Forms for Multiple-wner Elements Continued 39 of 83

40 Appendix 3 - Forms for Element Inventory and Summary utage Data 3.1 AC and DC Circuit Inventory Data 40 of 83

41 Appendix 3 - Forms for Element Inventory and Summary utage Data 3.2 Transformer Inventory Data 41 of 83

42 3.3 AC/DC Back-to-Back Converter Inventory Data Appendix 3 - Forms for Element Inventory and Summary utage Data 42 of 83

43 Appendix 4 Forms for Detailed Automatic utage Data 4.1 AC Circuit Detailed Automatic utage Data Continued 43 of 83

44 4.2 DC Circuit Detailed Automatic utage Data Appendix 4 Forms for Detailed Automatic utage Data Continued 44 of 83

45 4.3 Transformer Detailed Automatic utage Data Appendix 4 Forms for Detailed Automatic utage Data Continued 4.4 AC/DC Back-to-Back Converter Detailed Automatic utage Data Continued 45 of 83

46 Appendix 5 Form for Event ID Code and Event Type Number Data 46 of 83

47 Appendix 6 Forms for Detailed Non-Automatic utage Data 6.1 AC Circuit Detailed Non-Automatic utage Data Continued 47 of 83

48 6.2 DC Circuit Detailed Non-Automatic utage Data Appendix 6 Forms for Detailed Non-Automatic utage Data Continued 48 of 83

49 6.3 Transformer Detailed Non-Automatic utage Data Appendix 6 Forms for Detailed Non-Automatic utage Data Continued 49 of 83

50 Appendix 6 Forms for Detailed Non-Automatic utage Data 6. 4 AC/DC Back-to-Back Converter Detailed Non-Automatic utage Data Continued 50 of 83

51 Appendix 7 TADS Definitions The TADS Definitions is a separate document with its own page numbering. 51 of 83

52 Appendix 8 Inventory Data Examples The following examples demonstrate a calculation method that can be used to complete the TADS inventory spreadsheet data on the number of Multi-Circuit Structure Miles. However, the methods used to determine the inventory data associated with the number of AC Circuits can be used for any Element. The TADS Working Group acknowledges that other calculation methods can be utilized to complete the inventory spreadsheet. Every reporting entity must determine the method that is best for their organization. Base Model: Figure 1: ne-line diagram showing both new and removed circuits ne-line Diagram: All lines are 345 kv A (25) C (50) (10) (15) (25) (25) E (30) F (25) (25) Line CD-2 was energized on June 10, 2008 Line CF was energized on November 1, 2008 B (25) (25) D (75) Line CE was decommissioned on April 1, 2008 = Substation = Circuit removed during the year = Common Structure ( ) = Circuit Miles = Circuits added during the year 52 of 83

53 Appendix 8 Inventory Data Examples Calculation 1: No. of AC Circuits and Circuit Miles that were in-service at the end of the reporting year [FRM 3.1] Circuit Miles calculations (Elements at the end of the year) Element Identification Circuit Miles AB-1 25 AB-2 25 BD-1 25 BD-2 25 AE 25 AC 25 CD-1 25 DF 75 CD-2 25 CF 50 Total Circuit Miles would be entered into the column titled No. of Circuits (End of Year) 325 would be entered into the column titled Circuit miles (End of Year) Calculation 2: No. of AC Circuits and Circuit Miles that were added or removed during the reporting year [FRM 3.1] Circuit Miles Calculations (Elements added, retired or changed during the year) Element Identification Circuit Miles Number of Days from In-Service date to the end of the reporting year Equivalent Annual Element Value Equivalent Circuit Miles CD CF Totals for Elements added Element Identification Circuit Miles Number of days from retirement/change date to the beginning of the reporting year Equivalent Annual Element Value Equivalent Circuit Miles CE Total for Elements retired or changed would be entered into the column titled No. of Circuits Added 0.73 would be entered into the column titled Equivalent Annual No. of Circuits Added [3] (205/366) + (61/366) = 0.73 (2008 is a leap year) 75 would be entered into the column titled No. of Circuit Miles for Circuits Added 22.4 would be entered into the column titled Equivalent Annual No. of Circuit Miles for Circuits Added [3] 25 Miles (205/366) + 50 Miles (61/366) = 22.4 (2008 is a leap year) 1 would be entered into the column titled No. of Circuits removed.25 would be entered into the column titled Equivalent Annual No. of Circuits Removed [3] 91/366 =.25 (2008 is a leap year) 30 would be entered into the column titled No. of Circuit Miles for Circuits Removed 7.4 would be entered into the column titled Equivalent Annual No. of Circuit Miles for Circuits Removed [3] 30 Miles (91/366) = 7.4 (2008 is a leap year) 53 of 83

54 Appendix 8 Inventory Data Examples Calculation 3: Multi-Circuit Structure Miles for AC Circuits that were in-service at the end of the reporting year [FRM 3.1] Multi-Circuit Structure Miles Calculations (Elements at the end of the year) Element Identification Multi-Circuit Structure Miles AB-1 & AB-2 25 AC & AE 10 CD-1 & CD-2 25 Total Structure Miles would be entered into the column titled Multi-Circuit Structure Miles (End of Year) Calculation 4: Multi-Circuit Structure Miles for AC Circuits that were added or removed during the reporting year [FRM 3.1] Element Identification Multi-Circuit Structure Miles Calculations (Elements added during the year) Multi-Circuit Structure Number of Days from Miles In-Service date to the end of the reporting year Equivalent Multi-Circuit Structure Miles CD-1 & CD Total Equivalent Structure Miles added during the year would be entered into the column titled Multi-Circuit Structure Miles for Circuits Added would be entered into the column titled Equivalent Annual No. of Multi-Circuit Structure Miles for Circuits Added 25 Structure Miles (205/366) = (2008 is a leap year) Two Questions in Form 3.1 Base Example: None of Multi-Circuit Structure Miles are on a common structure reported by another Transmission wner. 54 of 83

55 Appendix 8 Inventory Data Examples Situation 1: Figure 2: The addition of a TADS Element on a common structure with a non- TADS Element ne-line Diagram: C (50) Line CF was energized on November 1, 2008 F = Substation ( ) = Circuit Miles = Common Structure = 345 kv Circuits added during the year = Existing 138 kv Circuits In this situation AC Circuit CF was placed on a common structure with an existing 138 kv circuit. For TADS this common structure situation shall not be included in the Multi-Circuit Structure Mile calculation. For TADS you are only to report those Multi-Circuit Structure Miles where two or more TADS Elements share a common structure. The calculations for AC Circuit CF are the same as in the Base Model. 55 of 83

56 Base Case and Situation 1 Inventory Data, Form 3.1 Appendix 8 Inventory Data Examples 56 of 83

57 Appendix 8 Inventory Data Examples Situation 2: Figure 3: Tap addition ne-line Diagram: All lines are 345 kv F M (10) Tap to substation was added on July 31 D (75) = Substation ( ) = Circuit Miles = Common Structure = Circuits added during the year In this example we are demonstrating how to calculate your inventory data if, in addition to the work that was done in the Base Model, you added a 10 mile tap off AC Circuit DF. Calculation 1a: No. of AC Circuits and Circuit Miles that were in-service at the end of the reporting year [FRM 3.1] Circuit Miles calculations (Elements at the end of the year) Element Identification Circuit Miles AB-1 25 AB-2 25 BD-1 25 BD-2 25 AE 25 AC 25 CD-1 25 DMF 85 CD-2 25 CF 50 Total Circuit Miles would be entered into the column titled No. of Circuits (End of Year) 335 would be entered into the column titled Circuit miles (End of Year) 57 of 83

58 Appendix 8 Inventory Data Examples Calculation 2a: No. of AC Circuits and Circuit Miles that were added or removed during the reporting year [FRM 3.1] Circuit Miles Calculations (Elements added, retired or changed during the year) Element Identification Circuit Miles Number of days from in-service date through the end of the reporting year Equivalent Annual Element Value Equivalent Circuit Miles CD CF DFM Totals for Elements added Element Identification Circuit Miles Number of days from retirement/change date to the beginning of the reporting year Equivalent Annual Element Value Equivalent Circuit Miles CE DF Total for Elements retired or changed would be entered into the column titled No. of Circuits Added 1.15 would be entered into the column titled Equivalent Annual No. of Circuits Added [3] (Excel will display to the first significant digit) (205/366) + (61/366) + (154/366) = 1.15 (2008 is a leap year) 160 would be entered into the column titled No. of Circuit Miles for Circuits Added 58.1 would be entered into the column titled Equivalent Annual No. of Circuit Miles for Circuits Added [3] 25 Miles (205/366) + 50 Miles (61/366) + 85 Miles (154/366) = 58.1 (2008 is a leap year) 2 would be entered into the column titled No. of Circuits removed.83 would be entered into the column titled Equivalent Annual No. of Circuits Removed [3] (91/366) + (212/366) =.83 (2008 is a leap year) 105 would be entered into the column titled No. of Circuit Miles for Circuits Removed 50.9 would be entered into the column titled Equivalent Annual No. of Circuit Miles for Circuits Removed [3] Calculation 3a: Multi-Circuit Structure Miles for AC Circuits that were in-service at the end of the reporting year [FRM 3.1] This calculation is the same as in the Base Model. Calculation 4a: Multi-Circuit Structure Miles for AC Circuits that were added or removed during the reporting year. [FRM 3.1] This calculation is the same as in the Base Model. 30 Miles (91/366) + 75 Miles (212/366) = 50.9 (2008 is a leap year) 58 of 83

59 Appendix 8 Inventory Data Examples Situation 2 Inventory Data, Form 3.1 Multi-Circuit Structure Miles data is the same as the Base Case 59 of 83

60 Appendix 8 Inventory Data Examples Situation 3: Figure 4: In/ut section addition ne-line Diagram: All lines are 345 kv F M (10) (10) In/ut section of the line was added on July 31, 2008 (50) D (25) = Substation ( ) = Circuit Miles = Common Structure = Circuits added during the year In this example we are demonstrating how to calculate your inventory data if, in addition to the work that was done in the Base Model, you added two 10-mile sections for a new substation. Calculation 1b: No. of AC Circuits and Circuit Miles that were in-service at the end of the reporting year [FRM 3.1] Circuit Miles calculations (Elements at the end of the year) Element Identification Circuit Miles AB-1 25 AB-2 25 BD-1 25 BD-2 25 AE 25 AC 25 CD-1 25 DM 35 MF 60 CD-2 25 CF 50 Total Circuit Miles would be entered into the column titled No. of Circuits (End of Year) 345 would be entered into the column titled Circuit miles (End of Year) 60 of 83

61 Appendix 8 Inventory Data Examples Calculation 2b: No. of AC Circuits and Circuit Miles that were added or removed during the reporting year [FRM 3.1] Circuit Miles Calculations (Elements added, retired or changed during the year) Element Identification Circuit Miles Number of days from in-service date through the end of the reporting year Equivalent Annual Element Value Equivalent Circuit Miles CD CF DM MF Totals for Elements added Element Identification Circuit Miles Number of days from retirement/change date to the beginning of the reporting year Equivalent Annual Element Value Equivalent Circuit Miles CE DF Total for Elements retired or changed would be entered into the column titled No. of Circuits Added 1.57 would be entered into the column titled Equivalent Annual No. of Circuits Added [3] (205/366) + (61/366) + (154/366) + (154/366) = 1.57 (2008 is a leap year) 170 would be entered into the column titled No. of Circuit Miles for Circuits Added 62.3 would be entered into the column titled Equivalent Annual No. of Circuit Miles for Circuits Added [3] 25 Miles (205/366) + 50 Miles (61/366) + 35 Miles (154/366) + 60 Miles (154/366) = 62.3 (2008 is a leap year) 2 would be entered into the column titled No. of Circuits removed.83 would be entered into the column titled Equivalent Annual No. of Circuits Removed [3] (91/366) + (212/366) =.83 (2008 is a leap year) 105 would be entered into the column titled No. of Circuit Miles for Circuits Removed 50.9 would be entered into the column titled Equivalent Annual No. of Circuit Miles for Circuits Removed [3] 30 Miles (91/366) + 75 Miles (212/366) = 50.9 (2008 is a leap year) Calculation 3b: Multi-Circuit Structure Miles for AC Circuits that were in-service at the end of the reporting year [FRM 3.1] This calculation is the same as in the Base Model. Calculation 4b: Multi-Circuit Structure Miles for AC Circuits that were added or removed during the reporting year [FRM 3.1] This calculation is the same as in the Base Model. 61 of 83

62 Appendix 8 Inventory Data Examples Situation 3 Inventory Data, Form 3.1 Multi-Circuit Structure Miles data is the same as the Base Case 62 of 83

63 Appendix 9 Detailed Automatic utage Data Examples The following examples illustrate several AC Circuit Automatic utages scenarios accompanied by (in most cases) a Transformer Automatic utage scenario. Data entries for each scenario are shown in tables along with each scenario. Finally, illustrations of the applicable sections of Form 4.1, Form 4.2, and Form 5 with the appropriate data entries for all outages are shown. While not all possible situations could be covered, the examples are complete enough to help with outage interpretation. Example 1: Three-terminal AC Circuit with a non-tads Element Example: Event ID Code A-2008, utage ID Code: A D E 345 kv Bus Substation boundary F 345/138 kv D utage took place at 11:00 AM 02/03/2008 GMT (UTC). AC Circuit outage starts when the first of these two breakers open (Breakers at D and E) E Broken crossarm causes single P-G fault F The Transformer is not a TADS Element therefore it is not reportable (Substation F) 345/138 kv D AC Circuit outage ends when the both breakers are closed 6:00 PM 02/03/2008 GMT (UTC) (Breakers at D and E) E F 345/138 kv This is a three terminal AC Circuit with a non-tads Element attached to one of the segments. The non-tads Element is the 345/138 kv Transformer. Since the Transformer is not a TADS Element, outages to the transformer are not reportable. 63 of 83

64 Appendix 9 Detailed Automatic utage Data Examples Example 1 utage reporting Fault type Single P-G fault No entries utage Initiation Code Form 4.1 Form 4.3 Form 5 Element-Initiated No entries Initiating Cause Code Failed AC Circuit No entries Equipment Sustained Cause Code Failed AC Circuit No entries Equipment utage Mode Code Single Mode No entries Event Type Number of 83

65 Appendix 9 Detailed Automatic utage Data Examples Example 2: Three-terminal AC Circuit with a TADS Element Example: Event ID Code B-2008, utage ID Codes B1 & B2 M 345 kv N Bus Substation boundary 345/230 kv M utage took place at 11:00 AM 02/05/2008 GMT (UTC) AC Circuit outage starts when the first of these two breakers open (Breakers at Substations M and N) N Broken crossarm causes single P-G fault 345/230 kv The Transformer Element outage starts when the one breaker opens (Breaker at substation ) M AC Circuit outage ends when both breakers are closed 4:00 PM 02/05/2008 GMT (UTC) (Breakers at Substations M and N) N 345/230 kv Transformer Element outage ends when the one breaker is closed 4:30 PM 02/05/2008 GMT (UTC) (Breaker at Substations ) This is a three-terminal AC Circuit with a TADS Transformer attached to one of the segments. Since the Transformer is a TADS Element, its outage is reportable. See utage reporting table below: 65 of 83

66 Appendix 9 Detailed Automatic utage Data Examples Example 2 utage reporting Fault type Single P-G fault None utage Initiation Code Initiating Cause Code Sustained Cause Code utage Mode Code Form 4.1 Form 4.3 Form 5 Element-Initiated Failed AC Circuit Equipment Failed AC Circuit Equipment Dependent Mode Initiating ther-element Initiated Failed AC Circuit Equipment Failed AC Circuit Equipment Dependent Mode Event Type Number of 83

67 Appendix 9 Detailed Automatic utage Data Examples Example 3: Bus fault that interrupts TADS Elements Example: Event ID Code C-2008, utage ID Codes, C1, C2 and C3 345 kv Bus J L1 L3 L2 Substation boundary Single P-G fault on the Bus at 6:00 PM 4/29/2008 GMT (UTC) J L1 Contamination L3 L2 Individual outages are over when corresponding line breakers are placed in-service Breakers for L1 and L2 were closed at 6:20 PM 04/29/2008 GMT (UTC) Breaker for L3 was closed at 7:00 PM 4/29/2008 GMT (UTC) J L1 L3 L2 This is an outage of a 345 kv bus caused by contamination. No damage resulted, and all the AC Circuits connected to the bus are reportable. See utage reporting table below: 67 of 83

68 Appendix 9 Detailed Automatic utage Data Examples Example 3 utage reporting Fault type Single P-G fault No entries utage Initiation Code Form 4.1 Form 4.3 Form 5 AC Substation Initiated No entries Initiating Cause Code Contamination No entries Sustained Cause Code Contamination No entries utage Mode Code Common Mode No entries Event Type Number 05 Example 4: AC Circuit that is directly connected to a TADS Transformer Example: Event ID Code D-2008, utage ID Codes D1 & D2 G In-service Element 345 kv H 345/230 kv Bus Substation boundary utage took place at 8:00:00 AM 6/08/2008 GMT (UTC) AC Circuit outage starts when the breaker at substation G opens H G Transformer Element outage starts when the breaker at substation H opens 345/230 kv Weather related outage causes a phase-to phase fault G AC Circuit outage ends when the breaker at substation G is closed 8:01:00 AM 06/08/2008 GMT (UTC) Transformer Element outage ends when the breaker at substation H is closed 8:03:00 AM 06/08/2008 GMT (UTC) H 345/230 kv 68 of 83

69 Appendix 9 Detailed Automatic utage Data Examples The AC Circuit is not damaged, and service is quickly restored. See utage reporting table below: Example 4 utage reporting Fault type P-P fault No fault utage Initiation Code Initiating Cause Code Sustained Cause Code utage Mode Code Form 4.1 Form 4.3 Form 5 Element-Initiated Weather, excluding lightning Weather, excluding lightning Dependent Mode Initiating ther-element Initiated Weather, excluding lightning Weather, excluding lightning Dependent Mode Event Type Number of 83

70 Appendix 9 Detailed Automatic utage Data Examples Example 5: Three-terminal AC Circuit Example: Event ID Code E-2008, utage ID Code E A In-service Element B 345 kv Bus Substation boundary C A Phase-to-phase fault on the AC Circuit at 1:00 PM 07/14/2008 GMT (UTC) The outage starts when any of the breakers at substation A, B or C opens (Substation A, B or C) B Broken insulator results in P-P fault C A utage ends when the breakers at substations A, B and C are closed The last breaker was returned to service at 5:00 PM 07/14/2008 GMT (UTC) B C 70 of 83

71 Appendix 9 Detailed Automatic utage Data Examples Example 5 utage reporting Fault type P-P fault No entries utage Initiation Code Initiating Cause Code Sustained Cause Code Form 4.1 Form 4.3 Form 5 Element-Initiated Failed AC Circuit Equipment Failed AC Circuit Equipment No entries No entries No entries utage Mode Code Single Mode No entries Event Type Number 11 Example 6: Common cause outage to two AC Circuits Example: Event ID Code F-2008, utage ID Code F1 & F2 Z L6 L4 Disconnect switch L1 and L2 are on a Common Structure L5 230/345 kv Z utage took place at 10:00:00 PM 12/22/2008 GMT (UTC) Both AC Circuit outages start when the their breaker opens L6 L4 L1 and L2 are on a Common Structure 230/345 kv L5 Single lightning strike hits both circuits, causing a single P-G fault Substation boundary Z utage ends at 10:00:04 PM 12/22/2008 GMT (UTC) The AC Circuit outage end when its breaker re-closes L6 L4 L1 and L2 are on a Common Structure L5 230/345 kv 71 of 83

72 Appendix 9 Detailed Automatic utage Data Examples Example 6 utage reporting Fault type Single P-G fault No entries utage Initiation Code Form 4.1 Form 4.3 Form 5 Element-Initiated No entries Initiating Cause Code Lightning No entries Sustained Cause Code NA - Momentary No entries utage Mode Code Common Mode No entries Event Type Number 31 Note: The outages would have been characterized as a Common Mode utage even if the AC Circuits had not been on common structures. 72 of 83

73 Appendix 9 Detailed Automatic utage Data Examples Example 7: Transformer outage Example: Event ID Code G-2008, utage ID Code G T L20 L21 230/345 kv Substation boundary T The Transformer Element outage started at 10:00 PM 12/22/2008 GMT (UTC) L20 Relay Misoperation L21 230/345 kv T utage ends at 11:05:04 PM 12/22/2008 GMT (UTC) L20 L21 230/345 kv nly the Transformer was outaged because of the relay misoperation. See utage reporting table below: 73 of 83

74 Appendix 9 Detailed Automatic utage Data Examples Example 7 utage reporting Fault type No entries No-Fault utage Initiation Code No entries Form 4.1 Form 4.3 Form 5 ther-facility Initiated Initiating Cause Code No entries Failed Protection System Equipment Sustained Cause Code No entries Failed Protection System Equipment utage Mode Code No entries Single Mode Event Type Number of 83

75 Appendix 9 Detailed Automatic utage Data Examples Example 8: AC Circuit outage with a breaker failure Example: Event ID Code H-2008, utage ID Code H1, H2 & H3 Bus J L1 L3 L2 Substation boundary Relay Misoperation (The relay failed to signal the breaker to open. The failure triggered the other two breakers to open) J utage took place at 10:00:00 AM 12/25/2008 GMT (UTC) AC Circuit (L1) outages start when the one breaker opened (not Shown) The breaker at substation J failed to open which caused the breakers for AC Circuits L2 and L3 to open utage for L2 and L3 started at 10:00:10 AM 12/25/2008 GMT (UTC) L1 Conductor broke, resulting in P-P fault L3 L2 Individual outages are over when corresponding line breakers are placed in-service Breakers for L1 were closed at 5:30 PM 12/25/2008 GMT (UTC) Breakers for L2 and L3 were closed at 11:15 AM 12/25/2008 GMT (UTC) J L1 L3 L2 75 of 83

76 Appendix 9 Detailed Automatic utage Data Examples Example 8 utage reporting Fault type P-P fault No fault utage Initiation Code Initiating Cause Code Sustained Cause Code utage Mode Code Form 4.1 Form 4.3 Form 5 Element-Initiated Failed AC Circuit Equipment Failed AC Circuit Equipment Dependent Mode Initiating ther Element- Initiated Failed Protection System Equipment Failed Protection System Equipment Dependent Mode Event Type Number of 83

77 Form 4.1 AC Circuit Detailed Automatic utage Data Continued Form 4.3 Transformer Detailed Automatic utage Data 77 of 83