The Western Electricity Coordinating Council

Doug Tucker of WECC & Brian Keel of SRP

November 16, 2010

2010 TRD/TADS Webinar

WECC TRD and NERC TADS

– General Overview – Brian Keel, SRP– Common Tower versus Common Corridor - Brian Keel– Phase 1 – Doug Tucker, WECC– Phase 2 – Doug Tucker– Data Correlation to PRC – Doug Tucker– Review previous submitted Qs of 2010 – Doug Tucker– Joint Ownership – Doug Tucker– Conclusion – Doug Tucker

WECC Transmission Reliability Database

• Started as sub group of the Reliability Subcommittee• Spring 2004• WECC PCC - OC 2005, re-tool for attributes• Formed TRDTF Fall 2005• WECC PCC, OC and Board approved Fall of 2006• Purposes of TRD:• WECC PCC Goal • WECC PCC and OC presentations over 2005• Completed with added physical attributes

3

WECC Transmission Reliability Database

• Purpose of the TRD Development– Transmission Outage Database

• PCUR, used with Performance Category Upgrade Requests

• Primary Use - RPEWG – monitor, evaluate and report performance to WECC, core charge of RPEWG

• WECC transmission line performance and tracking• Facilitate probabilistic planning• Provide common format for data collection, i.e., all of

Western adopted for their use

4

Purpose of the TRD

• In a 1996 WSCC survey, 90%, criteria expanded to be more probabilistic based.

• PBRC Phase I development and implementation of event probabilities into Performance Table. Table S-1

• Ultimate goal is to produce a more economically efficient system without sacrificing system reliability.

5

WECC TRD

• WECC TRD Sheets– Transmission Circuit Attribute Table

• Same as last year; Miles, Type, Voltage, Conductors per Phase, Overhead Ground Wires, Insulation Type, Cable Type, Structure Materials, Structure Types, Circuits per Structure, Terrain Exposure, Elevation Exposure.

– Transformer Attribute Table• Same as last year; High and Low Side kV,

Single or Multi, Rating.

WECC Table W-1

7

WECC TRD

• RPEWG– Members of the RPEWG (includes WECC Staff as

Members of RPEWG) only have access to raw outage data

– RPEWG Members listed on the WECC website– Access to data governed by RPIC, Approved

Exhibit C– Raw outage performance compared to criteria of

WECC Performance Criteria Table W-1

WECC TRD and NERC TADS

• TADS (TRD) overview– NERC wide data collection– AC circuits >= 200kV– Transformers Low Side >= 200kV– AC/DC Back to Back Converters >= 200kV

AC Voltage– DC Circuits >= +/-200kV

WECC TRD and NERC TADS• TADS Forms

– 1.1 Non – Reporting TO Statement– 1.2 Reporting TO Statement– 2.1 Tie Lines and Jointly Owned AC & DC– 2.2 Jointly Owned AC/DC BTB Converters– 3.1 AC & DC Circuit Inventory Data– 3.2 Transformer Inventory Data– 3.3 AC/DC BTB Converter Inverter Data– 3.4 Summary Automatic Outage Data– 4.1 AC Circuit Detailed Outage Data– 4.2 DC Circuit Detailed Outage Data– 4.3 Transformer Detailed Outage Data– 4.4 AC/DC BTB Converter Detailed Outage Data– 5.0 Event Code Data– 6.1 AC Circuit Non Automatic Outage Data– 6.2 DC Circuit Non Automatic Outage Data– 6.3 Transformer Non Automatic Outage Data– 6.4 AC/DC BTB Converter Non Automatic Outage Data

• Indicates WECC Members fill in these NERC TADS Forms• Indicates NERC data to be supplied by WECC from TRD Sheets

Transmission Availability Database - TADS

• TADS Metrics Calculated:– Inventory of AC & DC Equipment– Circuit & Transformer Outage F & D per

outage initiation code– Circuit Sustained and Momentary Outage

Metrics, Element or Other Initiated

11

TRD and TADS Differences

• TRD Data Differences:– Focus to Common Corridor Outages (RPEWG)– Physical Attribute Data Inputs– Circuits;

• Outage Rates per– Conductors per Phase– Number of Ground Wires– Insulator Type– Structure Material– Structure Type– Terrain Exposure– Elevation Range

12

13

Data Submittal & Review

NERC and WECC Databases

• Conclusion– WECC

• Specific to design• Structure in place and working

– NERC• Displace EIA• General Outage Information

– Not design specific• First year in 2008

CRW

COT

Data Gathering Discussion and results

• Outages with the same element ID that occur within 1-5 minutes of each other need separate event IDs

• Joint owners – need to report only the lines you are responsible for according to form 2.1

• Correlation to PRC-004 and Disturbance reports• How to code Misoperation

WECC Data Handling

• WECC converts the TRD data into the NERC forms 3.1, 3.2, 3.4, 4.1 4.2 4.3, 5.0, 6.1, 6.2, 6.3, 6.4

• Upload the data onto the NERC database

• WECC takes the additional data and creates the TRD report which will give us an insight on any patterns that will arise

• 5th annual TRD report for CY 2010

Joint Owner Form 2.1

• NERC has asked the TO’s to correlate with each other on who is reporting the information for their jointly owned lines

• TO A and TO B must be reporting jointly owned lines on Form 2.1 and indicating who is the reporting TO even if TO B owns 1% of the line and TO A owns 99% of the line

Form 2.1

TO-SRP

TO-SCE

Correlation to PRC-004 and Disturbance reports

● You will need to talk to your Operations department in order to get the PRC-004 Mis-operations reports and Disturbance reports

● Disturbance reports are also on the WECC website under Western Electricity Coordinating Council > Library > WECC Documents > Disturbance Logs and Reports > Disturbance Reports - Preliminary (Must be logged into the website in order to see the documents)

● To get an account for the website you will need to go to the website and request an account. The request form is in the top right corner next to the sign in button

Misoperation Cause Codes

• NERC Glossary of Terms (updated 4/20/2010) defines Misoperation as;– “Any failure of a Protection System element to operate within the

specified time when a fault or abnormal condition occurs within a zone of protection.

– Any operation for a fault not within a zone of protection (other than operation as backup protection for a fault in an adjacent zone that is not cleared within a specified time for the protection for that zone).

– Any unintentional Protection System operation when no fault or other abnormal condition has occurred unrelated to on-site maintenance and testing activity.”

• For each sample ‘Misoperation Cause’ below, based on the current ‘TADS Cause Code’ definitions, the following ‘Cause Codes’ should be used on Form 4.x ;

Mapping of Misoperation

Misoperation Cause TADS Cause Code

Field/Physical Execution Error - Human Error

Engineering/Design Issue/Error‐ Settings - Human Error

‐ Design - Human Error (if NERC Registered Entity staff or Entity design contractor make the error)

‐ Design - Failed Protection System Equipment (if Equipment Vendor made a design error)

Relay Failure - Failed Protection System Equipment

Relay condition - Failed Protection System Equipment

Substation AC Failure - Failed AC Substation Equipment (if failed on the primary insulation side > 200 kV)- Failed Protection System Equipment (if failure on secondary side of relay PT, relay

control system, Current Transformer core, etc.)

Substation DC 120/240 V - Failed Protection System EquipmentPower/Control Failure

Communication Failure - Failed Protection System Equipment

SCADA Control

- Human Error (if NERC Registered Entity staff or Entity contractor make the error)

Mapping of Sample Misoperation Causes to "Equivalent" TADS Cause Codes

- Other (Use 'Other' if SCADA Control equipment failed.) (Not to be coded as Failed Protection System Equipment)

Definitions ( Phase II – 2010 FORM 6.x)

Outage Type for Non-Automatic Outage

• Operational Outage (Form 6.x) A Non-Automatic Outage for the purpose of avoiding an

emergency (i.e., risk to human life, damage to equipment, damage to property) OR to maintain the system within operational limits AND an outage that cannot be deferred.

• Planned Outage (Form 6.x) A Non-Automatic Outage with advance notice for the purpose of

maintenance, construction, inspection, testing, or planned activities by third parties that may be deferred [Sustained Outage].

Definitions ( Phase II - Form 6.x continued)

Planned Outage (continued)

Additional Switching Outage – 30 minute exclusion

An Outage of a TADS Element of 30 minutes or less duration resulting from switching steps or sequences that are performed in preparation for, or restoration of, the Planned Outage are NOT reportable.

Appendix 10 “Planned Outages and the 30-Minute Exclusion Examples”

The Planned Outage actual duration is reported in HHHH:MM even if it is 1-30 minutes in duration.

Other element outages resulting from associated switching steps or outage sequences, are NOT reported unless their duration exceeds 30 minutes.

Definitions ( Phase II - Form 6.x continued)

Cause Code for Non-Automatic Outage

• Planned Outage Cause Codes (3) Maintenance and Construction

Planned Outage requests from any entity that is defined in the NERC Functional Model.

Third Party Request Planned Outage requests from highway depart., Coast Guard, etc.

Other Planned Outage Planned Outages for reasons not included in the above list, including human

scheduling error.• Operational Outage Cause Codes (4)

Emergency Operational Outages that are taken for the purpose of avoiding risk to human

life, damage to equipment, damage to property, or similar threatening consequences.

Definitions ( Phase II - Form 6.x continued)

• Operational Outage Cause Codes (continued)

System Voltage Limit Mitigation Operational Outages taken to maintain voltage on the transmission system

within desired levels (i.e., voltage control). System Operating Limit Mitigation, except voltage

Operational Outages taken to keep the transmission system within System Operating Limits, except for System Voltage Limit Mitigation. The term “System Operating Limit” is defined in the NERC Glossary of Terms Used in Reliability Standards (see text box in TADS Appendix 7)

Other Operational Outage Outages for reasons not included in the above list, including emergency

decision human judgment errors. Does NOT include manual switching Human Error. These have no advance

notice. Code these outages as Automatic Outages.

Responsibilities for Each TO

• TOs are responsible for data quality. Each Regional Entity Coordinator (REC) or Designated Regional Entity Coordinator (DRE) is available to assist TOs (Doug Tucker; dtucker@wecc.biz ).

– Form 1.1 & 1.2 contact updates & checklist of Forms

– Form 2.x “Multi-Owner” reporting coordination

– single TO is responsible for TADS reporting of outages AND inventory.

– Coordinate common Event ID code for TADS Events affecting more than one TO. Enter a TADS “NERC Company” Event ID code.

– Coordinate evaluation of AC Circuit outages on common structures when the circuits are owned by different TOs.

– Prior to March 1st, TOs should reconcile their TADS reported outages with outages to be reported in PRC and EOP required reports.

– Prior to March 1st, TOs should review their TO webTADS “Reports” for outage & inventory data consistency & completeness.

*TADS Training 11-02-2010 Part A v5.ppt

Questions