NERC Transmission Availability Data System (TADS): Element Identifier Data Submission Addendum
|
|
- Hilary Clark
- 6 years ago
- Views:
Transcription
1 Transmission Availability Data System (TADS) Element Identifier Data Submission Addendum May 28, Peachtree Road NE NERC Transmission Availability Data System (TADS): Element Identifier Data Submission Addendum Suite R May 28, 600, 2013 North Tower 1 of 11 Atlanta, GA
2 Table of Contents Table of Contents Introduction Purpose Who Should Report When to Report What to Report Definitions Forms Overview Data Confidentiality Data Submission Completion Detailed Form Descriptions Non-Reporting Transmission Owner Statement Reporting Transmission Owner Information Forms for Multiple-Owner Elements Multiple-Owner AC and DC Circuits Multiple-Owner AC/DC Back-to-Back Converters AC and DC Circuit Detailed Inventory Data Transformer Detailed Inventory Data AC/DC Back-to-Back Converter Detailed Inventory Data Transmitting TADS Data Securely by NERC Transmission Availability Data System (TADS): Element Identifier Data Submission Addendum May 28, of 11
3 1 Introduction 1.1 Purpose Due to the recent modifications 1 to the TADS program, there are a number of upcoming changes that Transmission Owners (TOs) should be aware. To begin, detailed inventory will be collected for each TADS Element in contrast to the previous method of summary inventory reporting. Also, TADS reporting will change to a quarterly reporting cycle. Finally, TADS reporting will align with the Bulk Electric System definition during the 2014 reporting period. To facilitate these changes, a transition period is required. During the transition period, Table 1 shows the entity data collection schedule. This document is designed to assist TOs in preparation for the June 30, 2013 collection of Element Identifiers and Circuit Mileage fields for all TADS reportable Elements. 1.2 Who Should Report For U.S. Transmission Owners (TOs), providing TADS data is mandatory for all TOs on the NERC Compliance Registry. 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 Owners too must provide Phase II TADS data. 2 However, NERC, through the regions, will also be requesting TADS data from non-u.s. TOs on the NERC Compliance Registry. The following describe reporting requirements for different TO situations: 1. Non-reporting TOs 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. 3 However, a TO may voluntarily report data for the year that the TADS Elements are added. 2. TOs that become newly registered during a reporting calendar year are not subject to any TADS reporting requirements until the next calendar year. However, a TO may voluntarily report data for the year that it first becomes newly registered. 3. A non-reporting TO that becomes unregistered during a calendar year is no longer subject to any TADS reporting requirements. However, if a reporting TO 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 TO shall assume the reporting obligation of the unregistered TO for the entire calendar year. This will ensure that all TADS Elements continue to have their data reported. 1.3 When to Report Particularly, this document will detail the procedure required to complete data submission for the June 30, 2013 due date. This data submission will include, for all TADS reportable Elements at 200 kv or higher, the Element Identifier and Circuit Mileage (if applicable) fields. Additionally, several inventory fields are strongly recommended to be reported before June 30 but are not mandatory until the 2013Q4 reporting period (due by February 15, 2014). 1 pp Phase I was approved by the NERC Board of Trustees prior to the addition of Section 1600 to the Rules of Procedure. Because NERC s Phase I TADS approval relied upon Section 39.2(d) of the Federal Energy Regulatory Commission s regulations, 18 C.F.R. 39.2(d), Phase I is mandatory on all U.S. Transmission Owners. However, most non-u.s. Transmission Owners are voluntarily compiling with Phase I. 3 However, if after submitting From 1.1, a TADS Element is added by the TO prior to December 31 of the year prior to the reporting calendar year, the TO must notify NERC and submit Form 1.2. NERC Transmission Availability Data System (TADS): Element Identifier Data Submission Addendum May 28, of 11
4 Introduction Table 1: TADS Transition Schedule Due Date TADS Outage Data Key Inventory Data March 01, 2013 June 30, Annual (200 kv+ Elements Only) Element Identifier and Circuit Mileage Fields Only (200 kv+ Elements Only) September 30, 2013 November 15, Q1 and 2013Q2 (200 kv+ Elements Only) 2013Q3 (200 kv+ Elements Only) February 15, Q4 (200 kv+ Elements Only) Update All Key Inventory Fields (200 kv+ Elements Only) May 15, Q1 (All TADS Elements) If Applicable, Element Identifier and Circuit Mileage Fields Only (Less than 200 kv BES Elements Only) August 15, Q2 (All TADS Elements) November 15, Q3 (All TADS Elements) February 15, Q4 (All TADS Elements) Update All Key Inventory Fields (All TADS Elements) 1.4 What to Report Definitions The TADS Definitions document is a stand-alone document that is in the TADS Data Reporting Instruction Manual Appendix 7 4. 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 TO refer to the definitions when completing the forms Forms Overview In preparation for the Element ID submission, a subset of the TADS forms will be used. The relevant forms are listed below as well as the location in this document that has the written instructions for completing each form of 11
5 Introduction Table 2: Forms Overview Form Name Document Location Bulk Upload Capability? Non-Reporting Transmission Owner Statement Chapter 2.1 No Reporting Transmission Owner Information Chapter 2.2 No Multiple-Owner AC and DC Circuits Chapter Yes Multiple-Owner AC/DC Back-to-Back Converters Chapter Yes AC and DC Circuit Detailed Inventory Data Chapter 2.4 Yes Transformer Detailed Inventory Data Chapter 2.5 Yes AC/DC Back-to-Back Converter Detailed Inventory Data Chapter 2.6 No, submit via . Each data form has a common layout. 1. A TO who does not own any TADS Element is referred to as a non-reporting TO. Those TOs must submit Form 1.1 to its Regional Entity (RE). A TO which owns TADS Elements is referred to as a reporting TO. On Form 1.2, which is required for a reporting TO, one portion requests the Transmission Owner 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 TO owns TADS Elements in different regions and/or different countries, it must complete separate TADS submittals for each region and country. 2. Many columns have drop-down menus that correspond to defined choices. For example, all Cause Codes are in a dropdown menu and provide the TO the choice among the defined Cause Codes only. 3. 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 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, we have made judgments that data on certain forms will likely be confidential information because it contains critical energy infrastructure information (CEII), while other information is not confidential. A TO 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 TO wants non-confidential data to be made confidential, the TO 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: 5 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. iii. Could be useful to a person in planning an attack on critical infrastructure; 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 C.F.R (c)(1)-(2) 5 of 11
6 Introduction 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 2 below summarizes the default confidentiality for information on each form for this data submittal: Table 3: Form Default Confidentiality Status Form Non-Reporting Transmission Owner Statement Reporting Transmission Owner Information Multi-Owner AC and DC Circuits Multi-Owner AC/DC Back-to-Back Converters AC and DC Circuit Detailed Inventory Data 6 Transformer Detailed Inventory Data 6 AC/DC Back-to-Back Converter Detailed Inventory Data 6 Default Confidentiality Not confidential Not confidential Confidential-CEII Confidential-CEII Confidential-CEII Confidential-CEII Confidential-CEII 1.5 Data Submission Completion Upon completion of reporting, entities should, within webtads, go to the Checklist. This is located in the Forms Checklist menu in webtads. Then, entities should mark/verify that the Completed field is Yes for the following forms: TO TADS Statement TO Contacts Multiple-Owner AC and DC Circuits Multiple-Owner AC/DC BTB Converters AC and DC Circuit Inventory Data Transformer Inventory Data AC/DC BTB Converter Inventory Data This will indicate that the Element Identifier information has been submitted. However, the inventory fields in the Series 3.x forms will need to be updated with all fields before the 2013Q4 outage data deadline, February 15, 2014, as shown in Table 2. An updated version of the TADS Data Reporting Instruction Manual will be provided for 2013 reporting in order to facilitate the reporting of the additional fields, and they are not required for the June 30, 2013 data submission. 6 Detailed inventory data is considered Confidential-CEII. However, summary inventory data is considered not confidential. 6 of 11
7 2 Detailed Form Descriptions 2.1 Non-Reporting Transmission Owner Statement The Non-Reporting Transmission Owner Statement (TADS Form 1.1) is for TOs who do not own any TADS Elements as of date they submit it. If a Transmission Owner owns no TADS Elements as of its submission date, it provides the contact information of the person completing the form on behalf of the TO who is attesting to that fact. Please submit this form before the June 30, 2013 deadline by submitting to your TADS Regional Entity Coordinator. If after submitting this form, a TADS Element is added by the TO prior to December 31 of the reporting year, the TO must notify NERC and submit the Reporting Transmission Owner Information Form (TADS Form 1.2) within webtads. 2.2 Reporting Transmission Owner Information The Reporting Transmission Owner Information form (TADS Form 1.2) asks for three types of TO information. 1. It requests the business contact information for the primary and back-up TADS contact person for the Transmission Owner. 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 TO to explain which forms were submitted and if not submitted, why they were not submitted (e.g., TO has none of the Elements reported on the form, the TO had no outages, etc.). 3. Finally, it lists the NERC default confidentiality status of TO data on each form. If a TO wants non-confidential data to be made confidential, the TO must indicate the category or categories defined in Section 1501 in which the data falls. See Section 1502 of the Rules of Procedure. Please submit this form before the June 30, 2013 deadline by completing within webtads. Please note that this form must be completed before the subsequent forms in sections 2.3 to 2.7. Otherwise, webtads will not allow entry of subsequent data. 2.3 Forms for Multiple-Owner Elements These forms are used to ensure that one TO takes on the TADS reporting responsibility for multiple-owner Elements for all Automatic and Non-Automatic outages. If a TO has less than 100% ownership interest in such Elements, each TO must enter this Element on the Multiple-Owner Elements forms (TADS Series 2.x forms). These multiple entries should be coordinated by the TOs involved. This list of such Elements should also include any multiple-owner Element that was inservice for at least part of the reporting period. Such an Element and their associated multiple-owner Element Identifier should be listed on the relevant form within Series 2.x. The coordinated entries should indicate which single TO will take reporting responsibility for the Element. The single TO designated as the Reporting TO must include the Element s circuit mileage on their detailed inventory forms (TADS Series 3.x). Selecting a single TO to become the Reporting TO for these inventory and outage Forms will avoid duplication of outage and inventory reporting. The other TOs 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 the respective form within Series 2.x. If a TO owns 100% of an Element, the reporting responsibility of that Element belongs to the TO. The Element should not be entered on any Series 2.x form. For 100% owned AC Circuits, communication among the TOs 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 TO must supply. Among all of the owners for a particular Element, they must agree on the Element ID to be entered in Column I. Only the TO declared to be the Reporting TO on the Series 2.x forms can use that Element ID. If other TOs attempt to enter Outages for this Element, an error message will be generated. Please submit the Form Series 2.x forms to webtads before the June 30, 2013 deadline. NERC Transmission Availability Data System (TADS): Element Identifier Data Submission Addendum May 28, of 11
8 Detailed Form Descriptions Multiple-Owner AC and DC Circuits The characteristics of each multiple-owner circuit are input on this form (one circuit per row). TOs are expected to mutually agree on who should report outage and inventory information (on TADS Series 3, 4, 5 and 6 forms) 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. If an AC Circuit or DC Circuit has more than 3 Terminal Names, please list only the first 3 Terminal Names on this form. Table 4: Multiple-Owner 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 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. Other 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 Overhead. This Element characteristic is input from a drop-down menu. See the definition of Overhead and Underground in Appendix 7, Section A. G-H The NERC ID number and name of the TO with TADS outage reporting responsibility for the multiple-owner circuit. I The reporting TO 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 TO can be designated as the reporting TO for a given set of multiple-owners using the given Element ID. J-W Only the Reporting TO should enter the Element Identifier of Multiple-Owner Elements on their Series 3 forms. The NERC ID numbers and name of the TOs that have an ownership interest in the Element. Up to ten owner names are provided. One of the TOs must be the TO with TADS reporting responsibility input in columns G-H. Among the multipleowners, only the reporting TO 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 Multiple-Owner AC/DC Back-to-Back Converters 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 TO. 8 of 11
9 Detailed Form Descriptions Table 5: Multiple-Owner 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 HIDDEN C The AC Circuit Voltage Class, input from a drop-down menu, on one side of the converter D The AC Circuit Voltage Class, input from a drop-down menu, on the other side of the converter E-F HIDDEN G-H The NERC ID number and name of the TO with TADS reporting responsibility. I The reporting TO s Element Identifier. This is required. J-Q The NERC ID numbers and names of the TOs that are multiple owners of the Element. Up to four owner names are provided. One of the TOs must be the TO with TADS reporting responsibility input in column G-H. 2.4 AC and DC Circuit Detailed Inventory Data This form (TADS Form 3.1) is to report detailed inventory data for both AC and DC Circuits. For the June 30, 2013 submittal, only Element Identifiers and Circuit Mileage are required on a per-element basis. If there are AC Circuits or DC Circuits that are multiple-owner circuits reported by the TO, these Elements should be reported on this form. 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. Although only Unique Element Identifier, Circuit Miles, and the initial Change/Reconfiguration Date are required for the June 30, 2013 data submission, it is strongly recommended that Voltage Class and Circuit Type fields also be submitted. webtads will accept data without these fields, but the summary display will not display the total Circuits and Circuit Miles by Voltage Class. 9 of 11
10 Detailed Form Descriptions Table 6: AC Circuit and DC Circuit Detail Inventory Form (* Indicates Mandatory for June 30, 2013 Reporting) Column Form 3.1 Field Name Form 3.1 Descriptor A Unique Element Identifier* A TO 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 TOs must agree on the Element Identifier. B Voltage Class (Strongly Recommended) 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 (Strongly Recommended) AC = AC Circuit Element DC = DC Circuit Element D-I HIDDEN J 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. K-T HIDDEN V W-Y Change/Reconfiguration Date* HIDDEN 2.5 Transformer Detailed Inventory Data 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. This form (TADS Form 3.2) is to report detailed inventory data for TADS reportable Transformer Elements. For the June 30, 2013 submittal, only Element Identifiers are required on a per-element basis. For TADS purposes, a transformer must have a low-side voltage of 200 kv to be reportable. Although only Unique Element Identifier and the initial Change/Reconfiguration Date are required for the June 30, 2013 data submission, it is strongly recommended that the High Side Voltage Class field also be submitted. webtads will accept data without this field, but the summary display will not display the total Transformers by Voltage Class. 10 of 11
11 Detailed Form Descriptions Table 7: Transformer Detail Inventory Form (* Indicates Mandatory for June 30, 2013 Reporting) Column Form 3.2 Field Name Form 3.2 Descriptor A Unique Element Identifier* A TO defined unique Element Identifier. Element Identifiers cannot be reused in any future reporting period for a different Element. B HIDDEN C High Side Voltage Class The High-Side Voltage Class of the Transformer. (Strongly Recommended) D-F HIDDEN G H-J Change/Reconfiguration Date* HIDDEN Enter the in-service date (mm/dd/yyyy) of the Transformer. If this is prior to January 1, 2013, please use January 1, 2013 as the Change/Reconfiguration Date. 2.6 AC/DC Back-to-Back Converter Detailed Inventory Data This form (TADS Form 3.3) is to report detailed inventory data for TADS reportable Transformer Elements. For the June 30, 2013 submittal, only Element Identifiers are required on a per-element basis. For TADS purposes, an AC/DC Back-to-Back Converter must have both sides 200 kv to be reportable. Although only Unique Element Identifier and the initial Change/Reconfiguration Date are required for the June 30, 2013 data submission, it is strongly recommended that the Voltage Class field also be submitted. webtads will accept data without this field, but the summary display will not display the total AC/DC Back-to-Back Converters by Voltage Class. Table 8: AC/DC Back-to-Back Converter Detail Inventory Form (* Indicates Mandatory for June 30, 2013 Reporting) Column Form 3.3 Field Name Form 3.3 Descriptor A Unique Element Identifier* A TO defined unique Element Identifier. Element Identifiers cannot be reused in any future reporting period for a different Element. B HIDDEN C Voltage Class (Strongly Recommended) The High-Side Voltage Class of the Transformer. D E-G Change/Reconfiguration Date* HIDDEN To submit this data, please send the XML workbook to tadscomments@nerc.net. Enter the in-service date (mm/dd/yyyy) of the AC/DC Back-to- Back Converter. If this is prior to January 1, 2013, please use January 1, 2013 as the Change/Reconfiguration Date Transmitting TADS Data Securely by The webtads data entry software will transmit data securely into webtads. Therefore, will primarily be used by TOs to transmit corrections to data that must be entered by a Regional Entity coordinator or NERC staff when webtads data entry is closed to TOs. If an entity (TO, 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. 11 of 11
Physical Security Reliability Standard Implementation
Physical Security Reliability Standard Implementation Attachment 4b Action Information Background On March 7, 2014, the Commission issued an order directing NERC to submit for approval, within 90 days,
More informationNERC Request for Data or Information: Protection System Misoperation Data Collection August 14, 2014
Request for Data or Information Protection System Misoperation Data Collection August 14, 2014 3353 Peachtree Road NE Suite 600, North Tower Atlanta, GA 30326 404-446-2560 www.nerc.com 1 of 15 Table of
More informationStandard CIP Cyber Security Critical Cyber As s et Identification
A. Introduction 1. Title: Cyber Security Critical Cyber Asset Identification 2. Number: CIP-002-4 3. Purpose: NERC Standards CIP-002-4 through CIP-009-4 provide a cyber security framework for the identification
More informationStandard CIP Cyber Security Critical Cyber As s et Identification
A. Introduction 1. Title: Cyber Security Critical Cyber Asset Identification 2. Number: CIP-002-4 3. Purpose: NERC Standards CIP-002-4 through CIP-009-4 provide a cyber security framework for the identification
More informationStandard CIP Cyber Security Critical Cyber Asset Identification
Standard CIP 002 1 Cyber Security Critical Cyber Asset Identification Standard Development Roadmap This section is maintained by the drafting team during the development of the standard and will be removed
More informationBESNet User Manual. Exception Request Preparation for Registered Entities. June 29, 2014 Version 1-2
Table of Contents BESNet User Manual Exception Request Preparation for Registered Entities June 29, 2014 Version 1-2 3353 Peachtree Road NE Suite 600, North Tower Atlanta, GA 30326 404-446-2560 www.nerc.com
More informationStandard CIP Cyber Security Critical Cyber Asset Identification
Standard CIP 002 1 Cyber Security Critical Cyber Asset Identification Standard Development Roadmap This section is maintained by the drafting team during the development of the standard and will be removed
More informationIntroduction to Generation Availability Data System (GADS) Wind Reporting
Introduction to Generation Availability Data System (GADS) Wind Reporting Registration and Reporting Fundamentals Donna Pratt, Performance Analysis Manager-Data Analytics NERC Webinar April 26, 2017 Topics
More informationStandard Development Timeline
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard is adopted by the NERC Board of Trustees (Board).
More informationStandard CIP Cyber Security Security Management Controls
A. Introduction 1. Title: Cyber Security Security Management Controls 2. Number: CIP-003-4 3. Purpose: Standard CIP-003-4 requires that Responsible Entities have minimum security management controls in
More informationStandard CIP Cyber Security Incident Reporting and Response Planning
A. Introduction 1. Title: Cyber Security Incident Reporting and Response Planning 2. Number: CIP-008-4 3. Purpose: Standard CIP-008-4 ensures the identification, classification, response, and reporting
More informationStandard CIP-006-3c Cyber Security Physical Security
A. Introduction 1. Title: Cyber Security Physical Security of Critical Cyber Assets 2. Number: CIP-006-3c 3. Purpose: Standard CIP-006-3 is intended to ensure the implementation of a physical security
More informationStandard CIP 005 4a Cyber Security Electronic Security Perimeter(s)
A. Introduction 1. Title: Cyber Security Electronic Security Perimeter(s) 2. Number: CIP-005-4a 3. Purpose: Standard CIP-005-4a requires the identification and protection of the Electronic Security Perimeter(s)
More informationStandard CIP-006-4c Cyber Security Physical Security
A. Introduction 1. Title: Cyber Security Physical Security of Critical Cyber Assets 2. Number: CIP-006-4c 3. Purpose: Standard CIP-006-4c is intended to ensure the implementation of a physical security
More informationMarch 6, Dear Electric Industry Vendor Community: Re: Supply Chain Cyber Security Practices
March 6, 2019 Dear Electric Industry Vendor Community: Re: Supply Chain Cyber Security Practices On July 21, 2016, the Federal Energy Regulatory Commission (FERC) directed the North American Electric Reliability
More informationProject Retirement of Reliability Standard Requirements
Project 2013-02 Retirement of Reliability Standard Requirements Unofficial Comment Form for Paragraph 81 (P81) Project Retirement of Reliability Standard Requirements This form is provided in a Word format
More informationGuidelines for Submitting NERC Reliability Standards Required Documents to the SPP Reliability Coordinator and the SPP Balancing Authority Version 1
Guidelines for Submitting NERC Reliability Standards Required Documents to the SPP Reliability Coordinator and the SPP Balancing Authority Version 1 Revision History Version Effective Date Summary of Revisions
More informationScreening Procedures for Access to ISO Register of Transmission Facilities and Entitlements
Screening Procedures for Access to ISO Register of Transmission Facilities and Entitlements In accordance with the Federal Energy Regulatory Commission (FERC) order issued on January 24, 2003 (as modified
More informationStandard CIP Cyber Security Electronic Security Perimeter(s)
A. Introduction 1. Title: Cyber Security Electronic Security Perimeter(s) 2. Number: CIP-005-1 3. Purpose: Standard CIP-005 requires the identification and protection of the Electronic Security Perimeter(s)
More informationLesson Learned CIP Version 5 Transition Program CIP R1: Grouping BES Cyber Assets Version: September 8, 2015
Lesson Learned CIP Version 5 Transition Program CIP-002-5.1 R1: Grouping BES Cyber Assets Version: September 8, 2015 This document is designed to convey lessons learned from NERC s various CIP version
More informationStandard CIP 007 4a Cyber Security Systems Security Management
A. Introduction 1. Title: Cyber Security Systems Security Management 2. Number: CIP-007-4a 3. Purpose: Standard CIP-007-4 requires Responsible Entities to define methods, processes, and procedures for
More informationCritical Cyber Asset Identification Security Management Controls
Implementation Plan Purpose On January 18, 2008, FERC (or Commission ) issued Order. 706 that approved Version 1 of the Critical Infrastructure Protection Reliability Standards, CIP-002-1 through CIP-009-1.
More informationProcedure For NPCC Bulk Electric System Asset Database
Procedure For NPCC Bulk Electric System Asset Database Compliance Procedure 09 (CP-09) Revision 2 Table of Contents 1. Introduction and Purpose... 3 2. Responsibilities... 3 3. Overview... 3 4. Asset Database...
More informationCyber Security Reliability Standards CIP V5 Transition Guidance:
Cyber Security Reliability Standards CIP V5 Transition Guidance: ERO Compliance and Enforcement Activities during the Transition to the CIP Version 5 Reliability Standards To: Regional Entities and Responsible
More informationStandard CIP 007 3a Cyber Security Systems Security Management
A. Introduction 1. Title: Cyber Security Systems Security Management 2. Number: CIP-007-3a 3. Purpose: Standard CIP-007-3 requires Responsible Entities to define methods, processes, and procedures for
More informationProposed Clean and Redline for Version 2 Implementation Plan
Exhibit A Implementation Plans for CIP-002-2 through CIP-009-2 and CIP-002-3 and CIP-009-3 For Generator Owners and Generator Operators of U.S. Nuclear Power Plants Proposed Clean and Redline for Version
More informationStandard CIP-006-1a Cyber Security Physical Security
A. Introduction 1. Title: Cyber Security Physical Security of Critical Cyber Assets 2. Number: CIP-006-1a 3. Purpose: Standard CIP-006 is intended to ensure the implementation of a physical security program
More informationStandard INT Dynamic Transfers
Standard INT-004-3.1 Dynamic Transfers A. Introduction 1. Title: Dynamic Transfers 2. Number: INT-004-3.1 3. Purpose: To ensure Dynamic Schedules and Pseudo-Ties are communicated and accounted for appropriately
More informationA. Introduction. Page 1 of 22
The Background, VRF/VSLs, and Guidelines and Technical Basis Sections have been removed for this informal posting. The Project 2016-02 is seeking comments around the concept of the Requirement/Measure
More informationThe North American Electric Reliability Corporation ( NERC ) hereby submits
March 3, 2011 VIA ELECTRONIC FILING Ms. Erica Hamilton, Commission Secretary British Columbia Utilities Commission Box 250, 900 Howe Street Sixth Floor Vancouver, B.C. V6Z 2N3 Re: North American Electric
More informationCIP Cyber Security Systems Security Management
A. Introduction 1. Title: Cyber Security System Security Management 2. Number: CIP-007-5 3. Purpose: To manage system security by specifying select technical, operational, and procedural requirements in
More informationImplementation Plan for COM-001-2
Defined Terms in the NERC Glossary The RC SDT proposes the following new definitions: Interpersonal Communication: Any medium that allows two or more individuals interact, consult, or exchange information.
More informationNERC Relay Loadability Standard Reliability Standards Webinar November 23, 2010
Transmission Relay Loadability FERC Order 733 Project 2010-1313 NERC Relay Loadability Standard Reliability Standards Webinar November 23, 2010 Project Overview 2 Standards Involved PRC-023-2 Transmission
More informationStandard CIP 004 3a Cyber Security Personnel and Training
A. Introduction 1. Title: Cyber Security Personnel & Training 2. Number: CIP-004-3a 3. Purpose: Standard CIP-004-3 requires that personnel having authorized cyber or authorized unescorted physical access
More informationMisoperations Information Data Analysis System (MIDAS)
Misoperations Information Data Analysis System (MIDAS) End User Guide June 2016 NERC Report Title Report Date I Table of Contents Preface... iii Chapter 1 Reporting Obligations...1 Entities Obligated to
More informationEEI Fall 2008 Legal Conference Boston, Massachusetts Stephen M. Spina November 1,
EEI Fall 2008 Legal Conference Boston, Massachusetts Stephen M. Spina November 1, 2008 www.morganlewis.com Overview Reliability Standards Enforcement Framework Critical Infrastructure Protection (CIP)
More informationConsideration of Issues and Directives Federal Energy Regulatory Commission Order No. 791 June 2, 2014
Federal Energy Regulatory Commission Order No. 791 June 2, 2014 67 and 76 67. For the reasons discussed below, the Commission concludes that the identify, assess, and correct language, as currently proposed
More informationProject Physical Security Directives Mapping Document
Document Background In Order No. 802 (final order on CIP-014-1 Physical Security), issued on November 20, 2014, FERC directed NERC to remove the term widespread from Reliability Standard CIP-014-1 or,
More information1. Post for 45-day comment period and pre-ballot review. 7/26/ Conduct initial ballot. 8/30/2010
Standard CIP 011 1 Cyber Security Protection Standard Development Roadmap This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes
More information151 FERC 61,066 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION ORDER DENYING REHEARING. (Issued April 23, 2015)
151 FERC 61,066 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION Before Commissioners: Norman C. Bay, Chairman; Philip D. Moeller, Cheryl A. LaFleur, Tony Clark, and Colette D. Honorable.
More informationStandard CIP 005 2a Cyber Security Electronic Security Perimeter(s)
A. Introduction 1. Title: Cyber Security Electronic Security Perimeter(s) 2. Number: CIP-005-2a 3. Purpose: Standard CIP-005-2 requires the identification and protection of the Electronic Security Perimeter(s)
More informationProposed Improvements for NERC MOD Standards July 10, 2012
Agenda Item 3.6 Planning Committee Meeting September 18-19, 2012 Proposed Improvements for NERC MOD Standards July 10, 2012 Background This paper outlines proposed improvements for NERC Reliability Standards
More informationReliability Standard Audit Worksheet 1
Reliability Standard Audit Worksheet 1 FAC-003-4 Transmission Vegetation Management. Registered Entity Name: Applicable Function(s): Applicable only for TO and GO Compliance Monitoring Method: RSAW Version:
More informationStandard CIP Cyber Security Electronic Security Perimeter(s)
A. Introduction 1. Title: Cyber Security Electronic Security Perimeter(s) 2. Number: CIP-005-2 3. Purpose: Standard CIP-005-2 requires the identification and protection of the Electronic Security Perimeter(s)
More informationUnofficial Comment Form Project Modifications to CIP Standards Requirements for Transient Cyber Assets CIP-003-7(i)
Unofficial Comment Form Project 2016-02 Modifications to CIP Standards Requirements for Transient Cyber Assets CIP-003-7(i) Do not use this form for submitting comments. Use the electronic form to submit
More informationCIP Cyber Security Configuration Change Management and Vulnerability Assessments
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed
More informationCIP Standards Development Overview
CIP Standards Development Overview CSSDTO706 Meeting with FERC Technical Staff July 28, 2011 Objectives Historical Timeline CIP-002-4 CIP-005-4 CIP Version 5 2 Project 2008-06 Overview FERC Order 706 SDT
More informationStandard CIP Cyber Security Systems Security Management
A. Introduction 1. Title: Cyber Security Systems Security Management 2. Number: CIP-007-4 3. Purpose: Standard CIP-007-4 requires Responsible Entities to define methods, processes, and procedures for securing
More informationThis section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective.
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Description of Current Draft
More informationStandards Authorization Request Form
Standards Authorization Request Form When completed, email this form to: sarcomm@nerc.com NERC welcomes suggestions to improve the reliability of the bulk power system through improved reliability standards.
More informationThis section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective.
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed
More informationRELIABILITY COMPLIANCE ENFORCEMENT IN ONTARIO
RELIABILITY COMPLIANCE ENFORCEMENT IN ONTARIO June 27, 2016 Training provided for Ontario market participants by the Market Assessment and Compliance Division of the IESO Module 1 A MACD training presentation
More informationERO Enterprise Registration Practice Guide: Distribution Provider directly connected Determinations Version 2: July 5, 2018
ERO Enterprise Registration Practice Guide: Distribution Provider directly connected Determinations Version 2: July 5, 2018 Purpose The purpose of this Practice Guide is provide a reference to be used
More informationStandard CIP Cyber Security Physical Security
A. Introduction 1. Title: Cyber Security Physical Security of Critical Cyber Assets 2. Number: CIP-006-1 3. Purpose: Standard CIP-006 is intended to ensure the implementation of a physical security program
More informationUnofficial Comment Form 1st Draft of PRC-005-3: Protection System and Automatic Reclosing Maintenance (Project )
Unofficial Comment Form 1st Draft of PRC-005-3: Protection System and Automatic Reclosing Maintenance (Project 2007-17.2) Please DO NOT use this form for submitting comments. Please use the electronic
More informationStandard INT Dynamic Transfers
A. Introduction 1. Title: Dynamic Transfers 2. Number: INT-004-3 3. Purpose: To ensure Dynamic Schedules and Pseudo-Ties are communicated and accounted for appropriately in congestion management procedures.
More informationSecurity Standards for Electric Market Participants
Security Standards for Electric Market Participants PURPOSE Wholesale electric grid operations are highly interdependent, and a failure of one part of the generation, transmission or grid management system
More informationStandard CIP Cyber Security Systems Security Management
A. Introduction 1. Title: Cyber Security Systems Security Management 2. Number: CIP-007-1 3. Purpose: Standard CIP-007 requires Responsible Entities to define methods, processes, and procedures for securing
More informationCIP Cyber Security Configuration Management and Vulnerability Assessments
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed
More informationFrom: Laura Manz, Vice President of Market & Infrastructure Development
California Independent System Operator Corporation Memorandum To: ISO Board of Governors From: Laura Manz, Vice President of Market & Infrastructure Development Date: May 8, 2009 Re: Decision for Conditional
More informationImplementation Plan for Version 5 CIP Cyber Security Standards
Implementation Plan for Version 5 CIP Cyber Security Standards April 10September 17, 2012 Note: On September 17, 2012, NERC was alerted that some references in the Initial Performance of Certain Periodic
More informationStandard Development Timeline
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard is adopted by the NERC Board of Trustees (Board).
More informationDRAFT. Cyber Security Communications between Control Centers. March May Technical Rationale and Justification for Reliability Standard CIP-012-1
DRAFT Cyber Security Communications between Control Centers Technical Rationale and Justification for Reliability Standard CIP-012-1 March May 2018 NERC Report Title Report Date I Table of Contents Preface...
More information1. SAR posted for comment on January 15, Standard Drafting Team appointed on January 29, 2014
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed
More informationStandard COM-002-2a Communications and Coordination
A. Introduction 1. Title: Communication and Coordination 2. Number: COM-002-2a 3. Purpose: To ensure Balancing Authorities, Transmission Operators, and Generator Operators have adequate communications
More informationThis draft standard is being posted for an initial comment and ballot. The draft includes modifications to meet the directives of FERC Order No. 791.
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed
More informationDisclaimer Executive Summary Introduction Overall Application of Attachment Generation Transmission...
CIP-002-4 Cyber Security Critical Cyber Asset Identification Rationale and Implementation Reference Document September, 2010 Table of Contents TABLE OF CONTENts Disclaimer... 3 Executive Summary... 4 Introduction...
More informationImplementation Plan. Project CIP Version 5 Revisions 1. January 23, 2015
Implementation Plan Project 2014-02 CIP Version 5 Revisions January 23, 2015 This Implementation Plan for the Reliability Standards developed as part of Project 2014 02 CIP Version 5 Revisions replaces
More informationLesson Learned CIP Version 5 Transition Program CIP R1: Grouping BES Cyber Assets Version: March 2, 2014
Lesson Learned CIP Version 5 Transition Program CIP-002-5.1 R1: Grouping BES Cyber Assets Version: March 2, 2014 This document is designed to convey lessons learned from NERC s various CIP version 5 transition
More informationCIP Cyber Security Security Management Controls. Standard Development Timeline
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed
More informationCYBER SECURITY POLICY REVISION: 12
1. General 1.1. Purpose 1.1.1. To manage and control the risk to the reliable operation of the Bulk Electric System (BES) located within the service territory footprint of Emera Maine (hereafter referred
More informationStandard Development Timeline
CIP-003-67(i) - Cyber Security Security Management Controls Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when
More informationNew Brunswick 2018 Annual Implementation Plan Version 1
New Brunswick Energy and Utilities Board Reliability Standards, Compliance and Enforcement Program New Brunswick 2018 Annual Implementation Plan Version 1 December 28, 2017 Table of Contents Version History...
More informationNew York Department of Financial Services Cybersecurity Regulation Compliance and Certification Deadlines
New York Department of Financial Services Cybersecurity Regulation Compliance and Certification Deadlines New York Department of Financial Services ( DFS ) Regulation 23 NYCRR 500 requires that entities
More informationSummary of FERC Order No. 791
Summary of FERC Order No. 791 On November 22, 2013, the Federal Energy Regulatory Commission ( FERC or Commission ) issued Order No. 791 adopting a rule that approved Version 5 of the Critical Infrastructure
More informationUNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION COMMENTS OF THE PENNSYLVANIA PUBLIC UTILITY COMMISSION
UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION Physical Security Reliability : Standard : Docket No. RD14-15-000 COMMENTS OF THE PENNSYLVANIA PUBLIC UTILITY COMMISSION I. INTRODUCTION On
More information1. SAR posted for comment on January 15, Standard Drafting Team appointed on January 29, 2014
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed
More informationComparison of MANE-VU SIP Template to EPA SIP Checklist. September 17, 2007
Comparison of MANE-VU SIP to EPA SIP Checklist 9/17/07: Draft 1 Comparison of MANE-VU SIP to EPA SIP Checklist September 17, 2007 Key to Color Codes action MANE-VU work product Class I states only (and
More informationA. Introduction 1. Title: 2. Number: 3. Purpose: 4. Applicability: 4.1. Functional Entities: Balancing Authority Distribution Provider
The Background, VRF/VSLs, and Guidelines and Technical Basis Sections have been removed for this informal posting. The Project 2016-02 is seeking comments around the concept of the Requirement/Measure
More informationStandard Development Timeline
CIP-008-6 Incident Reporting and Response Planning Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard
More informationCyber Security Standards Drafting Team Update
Cyber Security Standards Drafting Team Update Michael Assante, VP & Chief Security Officer North American Electric Reliability Corp. February 3, 2008 Overview About NERC Project Background Proposed Modifications
More informationStandards Authorization Request Form
Standards Authorization Request Form When completed, email this form to: sarcomm@nerc.com NERC welcomes suggestions to improve the reliability of the bulk power system through improved reliability standards.
More informationStandard Development Timeline
Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Description of Current Draft
More informationHistory of NERC August 2013
History of NERC August 2013 Timeline Date 1962 1963 November 9, 1965 1967 1967 1968 June 1, 1968 July 13 14, 1977 1979 Description The electricity industry creates an informal, voluntary organization of
More informationConsideration of Issues and Directives Federal Energy Regulatory Commission Order No. 791 January 23, 2015
Federal Energy Regulatory Commission Order No. 791 January 23, 2015 67 and 76 67. For the reasons discussed below, the Commission concludes that the identify, assess, and correct language, as currently
More informationRe: North American Electric Reliability Corporation Docket No. RM
September 15, 2009 VIA ELECTRONIC FILING Ms. Kimberly D. Bose Secretary Federal Energy Regulatory Commission 888 First Street, NE Washington, D.C. 20426 Dear Ms. Bose: Re: rth American Electric Reliability
More informationCRITICAL ENERGY INFRASTRUCTURE INFORMATION ( CEII ) REQUEST INSTRUCTIONS
CRITICAL ENERGY INFRASTRUCTURE INFORMATION ( CEII ) REQUEST INSTRUCTIONS The attached form is intended to facilitate your request to the New York Independent System Operator, Inc. ("NYISO ) for information
More informationSmall Generator Interconnection Facilities Study Report. Completed for. ( Interconnection Customer ) Proposed Interconnection Pavant substation
Small Generator Interconnection Facilities Study Report Completed for ( Interconnection Customer ) Proposed Interconnection Pavant substation Original report dated February 17, 2016 Revised March 11, 2016
More informationFedRAMP: Understanding Agency and Cloud Provider Responsibilities
May 2013 Walter E. Washington Convention Center Washington, DC FedRAMP: Understanding Agency and Cloud Provider Responsibilities Matthew Goodrich, JD FedRAMP Program Manager US General Services Administration
More informationA. Introduction. B. Requirements and Measures
A. Introduction 1. Title: Communications 2. Number: COM-001-3 3. Purpose: To establish Communication capabilities necessary to maintain reliability. 4. Applicability: 4.1. Functional Entities: 4.1.1. Transmission
More informationSelf-Certification Tutorial. Version 1.0 April 2013
Version 1.0 April 2013 The PLAN At the end of this tutorial, you will be able to: 1. Describe the purposes of Self-Certification 2. Identify deadlines 3. Describe the use of the Self-Certification template
More informationPlease contact the undersigned if you have any questions concerning this filing.
!! November 29, 2016 VIA ELECTRONIC FILING Veronique Dubois Régie de l'énergie Tour de la Bourse 800, Place Victoria Bureau 255 Montréal, Québec H4Z 1A2 Re: North American Electric Reliability Corporation
More informationNERC Notice of Penalty regarding Upper Peninsula Power Company, FERC Docket No. NP09-_-000
May 7, 2009 Ms. Kimberly Bose Secretary Federal Energy Regulatory Commission 888 First Street, N.E. Washington, D.C. 20426 Re: NERC Notice of Penalty regarding, FERC Docket No. NP09-_-000 Dear Ms. Bose:
More informationArticle I - Administrative Bylaws Section IV - Coordinator Assignments
3 Article I - Administrative Bylaws Section IV - Coordinator Assignments 1.4.1 ASSIGNMENT OF COORDINATORS To fulfill the duties of the Fiscal Control and Internal Auditing Act (30 ILCS 10/2005), the Board
More informationImplementation Plan. Project CIP Version 5 Revisions. January 23, 2015
Implementation Plan Project 2014-02 CIP Version 5 Revisions January 23, 2015 This Implementation Plan for the Reliability Standards developed as part of Project 2014-02 CIP Version 5 Revisions replaces
More informationReliability Standard Audit Worksheet 1
Reliability Standard Audit Worksheet 1 PRC-004-3 Protection System Misoperation Identification and Correction This section to be completed by the Compliance Enforcement Authority. Audit ID: Registered
More informationWECC Criterion MOD-(11 and 13)-WECC-CRT-1.1
WECC Criterion MOD-(11 and 13)-WECC-CRT-1.1 A. Introduction 1. Title: Steady State and Dynamic Data Requirements 2. Number: MOD-(11 and 13)-WECC-CRT-1.1 3. Purpose: To establish the consistent data requirements
More informationCIP Cyber Security Personnel & Training
A. Introduction 1. Title: Cyber Security Personnel & Training 2. Number: CIP-004-6 3. Purpose: To minimize the risk against compromise that could lead to misoperation or instability in the Bulk Electric
More informationCritical Infrastructure Protection Version 5
Critical Infrastructure Protection Version 5 Tobias Whitney, Senior CIP Manager, Grid Assurance, NERC Compliance Committee Open Meeting August 9, 2017 Agenda Critical Infrastructure Protection (CIP) Standards
More informationReliability Standard Audit Worksheet 1
Reliability Standard Audit Worksheet 1 CIP-002-5.1 Cyber Security BES Cyber System Categorization This section to be completed by the Compliance Enforcement Authority. Audit ID: Registered Entity: NCR
More information