Transmission Availability Data System Reporting Training · 5. Participate in an overview of the OATI webTADS portal presentation. 6. Become familiar with the Annual Maintenance for

RELIABILITY | RESILIENCE | SECURITY

Transmission Availability Data System Reporting Training

2019 TADS Data Reporting TrainingOctober, 2019

RELIABILITY | ACCOUNTABILITY2

Agenda Overview

October 22, 20191:00-5:00 p.m. Eastern

October 23, 20199:00 a.m.-5:00 p.m. EasternBreakfast & Lunch provided

October 24, 20199:00 a.m.-12:00 p.m. EasternBreakfast provided

TADS 101 In-Depth Training Session Examples• Overview of TADS The why and who of TADS

• TADS Mechanics Accessing the portal Live OATI demo Annual Maintenance

• Outage Reporting In-Service State Preparing an outage for

reporting Outage reporting start to

finish

• Overview of TADSTADS Mechanics Annual Maintenance

• In-depth Coding In Service State Event code and types Fault Type Initiation code Cause code (Initiating and

sustained) Outage Mode

• Data Validation

• Test Your Knowledge Group and table top exercises Attendee supplied scenarios TADS Jeopardy

RELIABILITY | RESILIENCE | SECURITY3

• Instructors Dan King – Transmission Operations Supervisor; Ameren Margaret Pate – Liaison; NERC Kurt Weisman – Performance Analytics Consultant; ATC Mark Matthews – Lead Engineering Technologist; Duke Energy Mike Bocovich – Principal System Protection Engineer; MRO Tammy Norwood – Transmission Engineer; Southern Company Brian Nolan – Associate Director; OATI

• Contributors Scott Clemons – System Engineer; TVA Brantley Tillis – System Operations Services Initiatives; Duke Energy Sal Marino – Transmission Control Center Support Manager; Southern

Company

Instructors and Contributors


• Introduction of Attendees Your name Company TADS Experience

Welcome


TADS 101

2019 TADS Data Reporting Training1:00-5:00 p.m. EasternOctober 22, 2019


101 TADS Course Objective

Overall 101 TADS Course Objective (i.e. what you will learn):

Basic Instructions and information about the Transmission Availability Data System and reporting.


Learning Objective 1:Understand the 101 TADS Learning Objectives


• 101 TADS Learning Objectives (i.e. course objective in bite size pieces):

1. Understand the 101 objectives.2. Know why TADS is collected and how the data is used.3. Learn who your resources are and where can you find the documents to

assist in reporting.4. Know the steps to receive and access the OATI webTADS portal.5. Participate in an overview of the OATI webTADS portal presentation.6. Become familiar with the Annual Maintenance for TADS i.e. Checklist,

Contacts, Inventory, etc.7. Get acquainted with preparing an outage for TADS reporting.8. Become familiar with the mechanics of entering an outage from start to

finish in the OATI webTADS portal.

101 TADS Learning Objective


Learning Objective 2:Know why TADS is collected and how

the data is used


1. Press any button to turn the clicker on Icons in the upper corners of the

screen indicates it is on (Figure 2)

2. When ready to vote pressthe black letter button that corresponds to your answer

3. Your answer has been submitted when you see your letter with a checkmark on the screen (Figure 3)

Figure 1: Clicker

Turning Technologies

Figure 2: Clicker is on

Figure 3: Vote submitted


A. <1 YearB. 1-2 YearsC. 2-4 YearsD. 4+ YearsE. I’ve never reported

TADS data before

How many years have you reported TADS?


Yes No No, I reportannually

0% 0% 0%

A. YesB. NoC. No, I report annually

Have you reported your Q3 TADS Data?


Yes No No, I reportannually

0% 0% 0%

A. YesB. No

Have you ever attended this training?


• November 9, 1965 Northeast black out 30 million people affected $100 million of economic losses (~$770 million today)

• 1967 Federal Power Commission investigation, recommends “council on power coordination”.

• 1968 Regional groups formed NERC• August, 2003 Largest blackout in North America to date• April, 2006 NERC designated as Electric Reliability Organization

(ERO) by FERC as well as most Canadian provincial authorities

What is NERC?


What is TADS?

A - Availability

S - System

T - Transmission

D - Data


• NERC Rules of Procedure Section 1600 data request• October 23, 2007 – NERC Board of Trustees approved the Phase I reporto Authorized collection of Automatic outages

• October 29, 2008 – NERC Board of Trustees approved the Phase II reporto Authorized collection of non-Automatic outage

• December 19, 2012 – NERC Board of Trustees approved Section 1600 Data Request for TADS

Quarterly and Key Inventory Collectiono Authorized quarterly reporting and detailed inventoryo Aligned the TADS definitions with the BES definition

Collection of TADS Data

https://www.nerc.com/pa/RAPA/tads/TransmissionAvailabilityDataSyatemRF/TADS_PC_Revised_Final_Report_09_26_07.pdf

https://www.nerc.com/pa/RAPA/tads/TransmissionAvailabilityDataSyatemRF/TADS_Phase_II_Final_Report_091108.pdf

https://www.nerc.com/gov/bot/Agenda%20highlights%20and%20Mintues%202013/BOT%20-%20December%2019%202012%20Conference%20Call%20Minutes.pdf


• November 2015 – NERC Board of Trustees approved the Phase II sunset memo Authorized the discontinuation of the collection of planned outages

• Premise for the collection of TADS data “…the premise that transmission availability data will help quantify system

performance and reliability.”o Source: Phase I Report page 5

Collection of TADS Data

https://www.nerc.com/gov/bot/Agenda%20highlights%20and%20Mintues%202013/BOT%20-%20November%205%202015%20Minutes.pdf

https://www.nerc.com/pa/RAPA/tads/TransmissionAvailabilityDataSyatemRF/TADS_PC_Revised_Final_Report_09_26_07.pdf


Where is TADS Data Being Used?

Annual State of Reliability (SOR) Key Findings Chapter 3: Reliability Indicator Trends Chapter 4: Severity Risk Index Chapter 5: Trends in Priority Reliability Issues

Technical & Statistical Papers Transmission Availability Data Systems Reporting and Data Analysis (IEEE

PMAPS, 2016) Research on Common-Mode and Dependent Outage Events in Power

Systems – A Review (IEEE PACME, 2016) North American AC Circuit Outages Initiated by Transmission Equipment

Failures and Human Error (IEEE PES, 2016) Performance Analysis of North American AC Circuits on Common

Structures Using TADS and CEA Outage Statistics (IEEE PMAPS, 2018) Assessment of North American Transmission Outages by Fault Type (IEEE,

2019)


• All NERC Registered Transmission Owners who own the following Bulk Electric System Elements: AC Circuits (Overhead and Underground) Transformers* with ≥ 100 kV secondary voltage AC/DC Back-to-Back Converters DC Circuits (Overhead and Underground)o *Generator Step-up Transformers are excluded from TADS reporting

Who needs to report TADS?


• Basic Company Information (Forms 1.x)• Inventory Information (Forms 2.x and 3.x)• Event Information (Form 5)• Automatic Outage Information (Forms 4.x)• Non-Automatic Outage Information (Forms 6.x)

What is being collected through TADS?









Learning Objective 3:Learn who your resources are and where can you find the

documents to assist in reporting


• Donna Pratt – Performance Analysis Manager• Jack Norris – Engineer and TADS Liaison• Margaret Pate – Reliability Risk Analysis Control Liaison• Lee Thaubald – Technical Analyst

Email [email protected]

NERC Performance Analysis

mailto:[email protected]


TADS website

https://www.nerc.com/pa/RAPA/tads/Pages/default.aspx

https://www.nerc.com/pa/RAPA/tads/Pages/default.aspx


• Transmission Availability Data System (TADS) Website The left hand menu provides

useful information such as:o TADS Newso Regional contactso TADS Data Reporting Instructions

(DRI)o Related Linkso Dashboards

.

TADS website


TADS Website: NERC Regional Entities contacts

Regional Entity (RE) Contacts

NERC [email protected]

MRO Jake Bernhagen

NPCC Rafael Sahiholamal

RF John Idzior

SERC Nick DePompei

TexasRE [email protected]

WECC [email protected]









TADS Website: TADS News and Related Links


TADS Website: Key Documents


• Always check the NERC website for the most recent versions!!• TADS Data Reporting Instructions• TADS Definitions - Appendix 7• TADS Bulk Upload Workbook

TADS Website: Key Documents and Related Links


TADS Website: Key Documents


• The purpose of the Transmission Availability Data System Working Group (TADSWG) is to implement a uniform approach to reporting and measuring transmission availability, performance, and other related reliability data. To meet this purpose, the TADSWG makes recommendations on four key subjects: 1. The type of transmission availability data that Transmission Owners

(TOs) report to NERC; 2. A single process for collecting such data that avoids duplication of effort; 3. Transmission availability and performance metrics that are calculated

from the reported data; and 4. Guidelines for release of data and metrics.

• Contact [email protected] to be added to the TADSWG mailing list (there is no obligation if you monitor)

TADS Working Group



TADSWG and the Committee Structure

Board of Trustees (Board)

Reporting StructureTADSWG reports to PAS

reports to PC reports to the Board


ERO EnterpriseNERC & RE

Committee Structure TADSWG, PAS, PC, and BOT

• Owner of the application and its maintenance (webTADS)

• Responsible for providing access to definitions and data reporting requirements

• Maintains and publishes the reporting deadlines• Develops processes to ensure accuracy and

timeliness of the application data• Provide primary support to registered entities

and coordination with and TADSWG for additional SME support when necessary.

• Review the application data reported by registered entities within the specific Region and NERC

• Communicates reporting application updates with all stakeholders involved in the application data reporting

• Uses data for analysis, metrics and reports

• Provides industry stakeholder representation and subject-matter expertise to NERC

• Maintains definitions and data reporting requirements

• Suggests use of data for reports and metrics, application changes, and data quality controls

• Develops the application training materials• Reviews analysis and reports that utilize the

application data• Modifies the type of transmission availability data

being collected

What does it mean and who does what?









Learning Objective 4:Know the steps to receive and access the OATI webTADS

portal


webTADS Access Flow Chart

Entity qualify to report TADS

NERC Registered?

No

Contact your region to register

Yes OATI Certificate?

No

Contact Entity OATI assigned Security

Officer

YesEmail your regional

contact for webTADS user form

Return completed webTADS user form

to region and [email protected]

Receive NCR # Receive OATI certificate

User(s) will receive login email


Login

To log into the TADS OATI web portal go to:www.nerc.oati.com

If you have forgotten your password email [email protected]

OATI Proprietary Notice: All OATI products and services listed are trademarks and service marks of Open Access Technology International, Inc. All rights reserved.

http://www.nerc.oati.com/










Learning Objective 5:Participate in an overview of the OATI webTADS portal

presentation


OATI Demonstration









Learning Objective 6:Become familiar with the Annual Maintenance for TADS i.e.

Checklist, Contacts, Inventory, etc.


• Each year TADS reporting Transmission Owners are required to • Activate and Update the Checklist• Review their contacts Contacts should be kept up-to-date throughout the year

• Add, modify or retire shared and reporting TO’s inventory for the year

Annual Maintenance


Activating and Updating the Checklist


• Access the Tranmission Owner (TO) checklist Transmission (TADS) > Forms > Checklist

Review Contents of the Checklist



• Select the new reporting year• Click Apply




• Click on the “Update Checklist or Completion Status” button located at the bottom of the checklist form.




• Click the “Yes” radio button to attest the entity is a reporting TO for the year.




• The checklist expands once yes is selected• Exempt forms with your reason for exemption (see next two slides)

• Mark forms as completed (after data has been entered)

• Validate data (after data has been entered)

• Modify to save• Start reporting data


Checklist image shortened to fit



• Mark outage forms (4.1 – 6.4) exempt for any inventory not owned. Select the “Yes” radio button under exempt. Add a reason to the “Reason” box. o Note: the completed column will automatically mark as complete for that form.




• Mark outage forms (4.1 – 6.4) exempt for any quarter that did not experience an outage Select the “Yes” radio button under exempt. Add a reason to the “Reason” box. o Note: the completed column will automatically mark as complete for that form.





Mark outage forms complete once data has been entered

Click Modify to validate and saveOATI Proprietary Notice: All OATI products and services listed are trademarks and service marks of Open Access Technology International, Inc. All rights reserved.


ContactsForm 1.2


• TO Contacts Establishes contact information for TADS reporter or Transmission Owner Provides information for other company contacts (supervisor, operator,

analysts, etc.) Is different from TADS portal access (anyone can be a TADS contact no

certificate needed) Must be “reviewed” once a year Should be kept up-to-date throughout the year

• Contact information is important so the ERO Enterprise can contact you about data questions as well as send you TADS related announcements (i.e. training).

Creating Contacts (Form 1.2)


• Click on the “Needs Review” or “Reviewed” link to open the TO Contacts form




• Click on “New Contact” to add a new contact (click on the hyperlinked name

to edit a contact) Fill out the form

• NOTE: Contacts can not be deleted, instead the active checkmark is removed.

.




InventoryShared InventoryForms 2.1 & 2.2


• Shared Inventory Forms• Designed to ensure only one TO reports outage information for

elements jointly owned• kV lines shared with other utilities within or across state

boundary• All TOs with a share of ownership should report element in 2.X

forms Element ID should appear only once in each entity's 2.x inventory and

should appear once in the reporting entity's 3.x inventory Element ID MUST be unique across all entities included in any form 2.X.

• Provide primary Reporting TO given NERC ID, Company Name, Region, and Country

Shared Inventory (Forms 2.1 & 2.2)


• Click on the “Needs Review” or “Reviewed” link to open the 2.1or 2.2 forms




• Click “Add” to open the 2.X form and add shared inventory

• Fill in the form• Click “Enter” to save

.




InventoryReporting TO’s InventoryForms 3.1, 3.2 and 3.3


• Inventory Forms 3.1, 3.2, and 3.3. Click the “Needs Review” for

inventory on forms 3.x Click on “Inventory Detail” to

access the current year’s inventory

Add and modify inventory from the inventory detail form for the current year

Once up-to-date click the “Review” button on the inventory summary form.o NOTE: Inventory can still be

added, modified and retired throughout the year.

.

Accessing the Inventory (Form 3.x)



• Form 3.1 required fields Circuit type kV – voltage class group Element Identifier – An

alphanumeric name that identifies the element which is outaged; Must be unique and be consistent from year to year (i.e., A1001)

From Bus/To Bus – The line end points

In Service Date – In service date if known or 1/1/YY inventory was added to TADS

Number of Terminals

.

Line Inventory (Form 3.1)



• Form 3.3 required fields Element identifier – see

previous slide Transformer location – The

physical location of the transformer

High Side kV – Higher voltage side (primary); Determines how it is reported

Low Side kV – Lower voltage side (secondary); Determines if transformer is reportable

In Service Date – In service date if known or 1/1/YY inventory was added to TADS

.

Transformer Inventory (Form 3.3)



• How often do I indicate I am reporting & update my contacts?A. MonthlyB. QuarterlyC. AnnuallyD. Never

Example


• Transformers are classified as TADS reportable based on their lower or secondary voltage classification. Transformers with secondary or lower winding voltages greater than 100kV, or are included in the BES through the inclusion criteria are reportable.

• Once a transformer has been classified as reportable, it is entered into the inventory based on its high side or primary winding voltage class.

• Examples: A 500kV to 230kV transformer would be entered into TADS as a 400-599kV A 500kV to 138kV transformer would be entered into TADS as a 400-599kV A 500kV to 765kV transformer would be entered into TADS as a 600-799kV A 345kV to 69kV transformer would not be reported into TADS

Do I report my transformer based off of low side or high side?


• If I cut circuit 100 to make a new circuit 100 (relabeled as 100-2 for TADS reporting) & new circuit 101 what is the process?

Splitting a Circuit

Element Identifier From Bus To Bus Length In Service Date Retirement Date Precursor

100 Station A Station B 33.0 2/29/2012 11/2/2017

100-2 Station A Station C 22.0 12/5/2017 100

101 Station B Station C 11.0 12/7/2017 100









Learning Objective 7:Get acquainted with preparing an outage for TADS

reporting


Automatic Outage ReportingForms 4.X


A. B. C. D.

0% 0% 0% 0%

A. I gather outage information and I enter the data into webTADSB. I gather outage information, but someone else enters it into webTADSC. I don’t gather outage information, but I do enter it into webTADSD. I’m not involved in TADS, I’m here for free food or because my boss made me come

for some reason

Reporting Duties


M6 – Determination: Is it an automatic outage?


• Automatic Outage: An outage that results from the automatic operation of a switching device,

causing an Element to change from an In-Service State to a not In-Service State. o Single-pole (phase) tripping followed by successful AC single-pole (phase)

reclosing is not an Automatic Outage.

• In-Service State: An Element that is energized and connected at all its terminals to the

system.

Automatic Outage


• AC Transformer A bank comprised of three single-phase transformers or a single three-

phase transformer. A Transformer is bound by its associated switching or interrupting devices.

Transformer A is bound by the breaker and disconnect switch. Transformer A is Not in Service if either the breaker or disconnect switch is

open. Transformer B is bound by breakers on the high and low side. Transformer B is Not in Service if either breaker is open.

AC Transformer Definition


• AC Circuit A set of AC overhead or underground three-phase conductors that are

bound by AC Substations. Note: Radial circuits which are BES elements are to be included in AC

Circuits. The boundary of an AC Circuit extends to the transmission side of an AC

Substation. A circuit breaker, Transformer, and their associated disconnect switches

are not considered part of the AC Circuit, but they are defined, instead, as part of the AC Substation.

AC Circuit Definition


• In Service State An Element that is energized and connected at all its terminals to the

system . o AC Circuit A-B is not in service in this example because it is not energized and it is

not connected to terminal A and terminal B

In Service State Definition

Substation A

AC Circuit A-B

Substation B



system . o AC Circuit A-B is not in service in this example because even though it is

energized it is not connected at terminal B


Substation A

AC Circuit A-B

Substation B



system . o AC Circuit A-B is not in service in this example because even though it is

energized it is not connected at terminal B


Substation A

AC Circuit A-B

Substation B



system . o AC Circuit A-B is in service in this example because it is energized and is

connected at terminal A and terminal B


Substation A

AC Circuit A-B

Substation B



system . o AC Circuit A-B is in service in this example because it is energized and is

connected at terminal A and terminal B


Substation A

AC Circuit A-B

Substation B

Substation CAC Circuit C-B


• Transformer B experiences a fault. The fault is interrupted by the breakers on AC circuit A and Transformer B. After the disconnect switch is opened AC Circuit A is automatically restored within a minute. AC Circuit A reports a momentary outageo AC Circuit A returns to an in service state per the multi terminal tapped

transformer exclusion o Transformer B reports an outage - is not in service

In-Service State Example

230 kV

AC Circuit A

Transformer B

230 kV

115 kV


• AC Circuit A is bound by the two breakers• Transformer A is bound by a breaker and a disconnect switch• AC Circuit B is bound by a breaker and a disconnect switch• Transformer B is bound by a breaker and a disconnect switch


230 kV

AC Circuit A

AC Circuit B

Transformer A

Transformer B

500 kV


• A 230 kV bus fault opens the designated breakers. AC Circuit A reports an outage – one terminal is disconnected Transformer A reports an outage – both terminals are disconnected AC Circuit B DOES NOT report an outage – both terminals are connected Transformer B reports an outage – one terminal is disconnected


230 kV

AC Circuit A

AC Circuit B

Transformer A

Transformer B

500 kV


• AC Circuit A-B and AC Circuit B-C Report an outage• AC Circuit B-C is not energized or connected at terminal B or

terminal C• AC Circuit A-B is energized, but is not connected at terminal B

Shared Breaker Interrupts Multiple Lines

138 kV

AC Circuit B-C

138 kV

138/34 kVTransformer 2

138/34 kVTransformer 1

AC Circuit A-B


• If Wind Farm Radial circuit is owned by GO, circuit is not reportable to TADS GO cannot be forced to register as TO WF Radial Circuit 1 and WF Radial Circuit 2 are in service in these examples

Radial connection to Wind Farm

138/4 kVGSU

138 kVWF Radial

Circuit 2

G

WF Radial Circuit 1

138/4 kVGSU

G


Determination: Is it momentary or sustained?


• Momentary Outage: An Automatic Outage with an Outage Duration less than one minute. o If the circuit recloses and trips again within less than a minute of the initial

outage, it is only considered one outage. The circuit would need to remain in service for longer than one minute between the breaker operations to be considered as two outages.

• Sustained Outage: An Automatic Outage with an Outage Duration of a minute or greater.

Momentary or Sustained


Portal or bulk upload form



• A unique alphanumeric identifier assigned by the Transmission Owner to identify the reported outage of an Element.

• The Outage ID code is assigned by the TO• Can be alphanumeric• Must be unique across years (can’t use the ID “Outage 1” in

2016 and then again in 2017)• Examples: ACRO-YYYY-00000, INYY-00, YYYY_00000, or 00000

(where the number is usually from the entities outage system)

Outage Id Code


• Reference Module 8 for details about creating and assigning event Ids

• NOTE: Form 5 data must be entered into the portal before the system will accept form 4.X data

Determination: Event Id & Form 5


• The TO Element Identifier is the unique name assigned by the TO to TADS elements and reported via the 3.X forms

• Reference Module 5 for details about inventory reporting• Element Inventory data must be entered into the portal before

an outage can be reported

NOTE: When using the bulk upload form – The portal will accept an uploaded outage even if the TO Element identifier does not exist in the portal. However this will generate a fatal error that has to be corrected before reporting can be complete.o E.g. TO Element identifier is in the inventory as Line_A but entered in the upload

form as Line-A.

TO Element Identifier


• Reference Module 9 for details about creating and assigning fault type

Determination: Fault Type


• Reference Module 10 for details on how to select and report the outage initiation code.

• The Outage Initiation Code describes where the outage was initiated on the power system.

Determination: Outage Initiation Code


• The date and time rounded to the minute that the outage of the element started. Start Date is entered as mm/dd/yyyyo Portal entry allows data reporters to enter the date via a calendar interface

–

Time is entered as hh:mm in 24 hour clock or “military time” format.o For example, 2:00 p.m. would be entered as 14:00

• To report outages that extend past the end of the quarter, data reporters should extend the length of the outage to the end of the quarter and update each quarter until the end of the outage. Extending an outage across years will be covered below.

Outage Start Date and Time


• This is the time zone associated with the reported outage’s date and time.

• Outages should be reported as the time zone of where they occur or converted to GMT/UTC. webTADS stores data in GMT time.

• Time zones are offered as standard or prevailing time. Standard time runs from November to March. Daylight Savings time runs

March to November Prevailing time is the time on an automatically updated clock, such as a

cellphone or a computer and adjusts to accommodate daylight saving.

• Be consistent in how you select and enter your time zones!

Outage Time Zone


• Administration > User Configuration > User options• Select your time zone• Select reason for change• Click Save

Setting your default time zone in the OATI portal



• The outage duration expressed as hours and minutes hhhh:mm• Enter zero “0” for a momentary outage

Workbook Note: Be careful when pasting duration values in the TADS workbook as excel may translate the data to a date format and cause errors in the upload or accepted data.

Outage Duration


• Reference Module 11a for details on how to select and report the outage initiating cause code.

• The Initiating Cause Code best describes the initiating cause of the outage. E.g. what caused the outage.

Determination: Initiating Cause Code


• Reference Module 11b for details on how to select and report the outage sustained cause code.

• The Sustained Cause Code best describes cause that contributed to the longest duration. Note: Momentary outages do

not have a Sustained Cause Code (designated as NA-Momentary).

Determination: Sustained Cause Code


• Reference Module 12 for details on how to select and report the outage mode code.

• The Outage Mode Code describes whether an Automatic Outage is related to other Automatic Outages.

Determination: Outage Mode


Determination: Outage Continuation Code


• 0 = Outage began and ended within the same reporting period• 1 = Outage began in the reporting period but continued into the

next reporting period• 2 = Outage started in a previous reporting period

Outage Continuation Code



• If an outage begins in a reporting calendar year and continues beyond the end of the year, two separate Outage Durations will be input. Step 1 - For the reporting year when the outage started:o Create an unique Outage IDo Create an unique Event IDo Input the Outage Start Time and calculate an Outage Duration from the Outage

Start Time until the end of the year (December 31 12:59 p.m. GMT/UTC) o Outage Continuation Flag is “1 = Outage began in the reporting period but

continued into the next reporting period”

Reporting outages across years


• If an outage begins in a reporting calendar year and continues beyond the end of the year, two separate Outage Durations will be input. Step 2 - For the next reporting year:o Create an unique Outage IDo Use the same Event ID from last yearo Outage Start Time is January 1, 00:00 GMT/UTC of that reporting year and

calculate duration*o Outage Continuation Flag is “2 = Outage started in a previous reporting period”

– *Note: if the outage continues to the subsequent reporting year, the Outage Duration is entered as 8760:00, or 8784:00 for a leap year and step 2 is repeated.

Reporting outages across years


Operational Outage ReportingForm 6.X


M7 – Determination: Is it an operational outage?


• Non-Automatic Outage: An outage that results from the manual operation (including supervisory

control) of a switching device, causing an Element to change from an In-Service State to a not In-Service State. Includes outages caused by personnel during on-site maintenance, testing, inspection, construction, or commissioning activities.

• Operational Outage: Non-Automatic Outage for the purpose of avoiding an emergency (i.e., risk

to human life, damage to equipment, damage to property) or to maintain the system within operational limits and that cannot be deferred. Includes Non-Automatic Outages resulting from manual switching errors.

Determination: Non-Automatic Outage


• TADS reporting exclusions (current for the 2019 reporting year): Planned Outages Operational Outages less than

200 kV

Determination: Non-reportable Non-Automatic Outages


Automatic vs Non-Automatic Outages

Field Automatic Outages Non-Automatic

TADS Elements All BES 200 kV and above

Momentary and Sustained Momentary (200kV+ only) and Sustained (All BES)

Momentary and Sustained(Outages of any duration)

Outage Id Yes Yes

Event Id Yes No

TO Element Id Yes Yes

Fault Type Yes No

Outage Initiation Code Yes No

Start Time & Date Yes Yes

Duration Yes Yes

Cause Code Initiating and Sustained Operational

Outage Mode Yes No

Outage Continuation Code Yes Yes


• Assigns a non-automatic outage type. Select Operational.• Hold over from the collection of planned outage.

Workbook Note: If Planned is selected in the bulk upload workbook you will receive an error when importing.

Non-Automatic Outage Type


M7 – Determination: Operational Cause Code


M7 – Determination: Outage Continuation Code


A. B. C. D.

0% 0% 0% 0%

• Non-automatic outages entered into form 6.X do NOT require which of the following fields?A. Outage IDB. Event IDC. Element IDD. Duration

M7 – Non-Automatic Outage Question


• On Monday, September 27, 2018 at 18:47 EPT an insulator fails causing a phase to ground fault to occur on the 230 kV Line A-B. The line was out for 3 hours and 45 minutes for insulator repairs.

Use the TADS Outage Decision Tree to help prepare your outage for reporting.

The TADS Workbook is also useful for preparing outages for reporting

Preparing an outage for TADS reporting

https://www.nerc.com/pa/RAPA/tads/Key_TADS_Documents/Outage%20Decision%20Tree.pdf

https://www.nerc.com/pa/RAPA/tads/Key_TADS_Documents/TADS_Workbook_2018.zip


Form 3.1Detailed AC and DC Circuit Inventory

Element Id Voltage Class

Circuit Type From Bus To Bus Tertiary Bus Circuit Miles # of Terminals


Form 3.1Detailed AC and DC Circuit Inventory


Form 5.0Event ID Codes

Event Id Code Event Type No. Description Disturbance Report Filed


Form 5.0Event ID Codes


Form 4.1AC Circuit Outage Data

Outage Id Code Event Id Code AC Circuit Fault Type Outage Initiation

Start Time (mm/dd/yyyy hh:mm) Time Zone Outage Duration hhhh:mm

Initiating Cause Sustained Cause Outage Mode Outage Continuation Code


Form 4.1AC Circuit Outage Data





Contacts, Inventory, etc.7. Get acquainted with preparing an outage for TADS reporting.8. Become familiar with the process of entering an outage from start to




Learning Objective 8:Become familiar with the mechanics of entering an outage

from start to finish in the OATI webTADS portal


OATI Graphic User Interface DemonstrationEntering a prepared outage





Contacts, Inventory, etc.7. Get acquainted with preparing an outage for TADS reporting.8. Become familiar with the process of entering an outage from start to




Questions


• Overall 101 TADS Course Objective (i.e. what you will learn): Basic Instructions and information about the Transmission Availability Data

System and reporting.

101 TADS Course Objective


[email protected]



BREAKReturn at: XX:XX a.m.

TADS TrainingOctober 22-24, 2019


ExerciseReturn at: XX:XX a.m.

TADS TrainingOctober 22-24, 2019