Implementation Plan for COM-001-2
|
|
|
- Stanley Holt
- 5 years ago
- Views:
Transcription
1 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. Alternative Interpersonal Communication: Any Interpersonal Communication that is able to serve as a substitute for, and does not utilize the same infrastructure (medium) as, Interpersonal Communications used for day-to-day operation. Prerequisite Approvals None Conforming Changes to Requirements in s None Revision Summary The RC SDT revised the standard and is proposing retiring three requirements (R1, R5 and R6). Changes were made to eliminate redundancies between standards (existing and proposed), to align with the ERO Rules of Procedure and to address issues in FERC Order 693. Effective Dates The first day of the first calendar quarter following applicable regulatory approval or in those jurisdictions where no regulatory approval is required, the first day of the first calendar quarter following Board of Trustees adoption. To be determined. Formatted: Font color: Red, Strikethrough Formatted: French (France) Village Blvd. Princeton, NJ Formatted: Centered
2 Revisions or Retirements to s The following tables identify the sections of approved standards that shall be retired or revised when this standard is implemented. If the drafting team is recommending the retirement or revision of a requirement, that text is blue. R1. Each Reliability Coordinator, Transmission Operator and Balancing Authority shall provide adequate and reliable telecommunications facilities for the exchange of Interconnection and operating information: [Violation Risk Factor: High] R1.1. Internally. [Violation Risk Factor: High] R1.2. R1.3. R1.4. Between the Reliability Coordinator and its Transmission Operators and Balancing Authorities. [Violation Risk Factor: High] With other Reliability Coordinators, Transmission Operators, and Balancing Authorities as necessary to maintain reliability. [Violation Risk Factor: High] Where applicable, these facilities shall be redundant and diversely routed. [Violation Risk Factor: High] R1. Each Reliability Coordinator shall have Interpersonal Communications capability with the following entities to exchange Interconnection and operating information: [Violation Risk Factor: High][Time Horizon: Real-time Operations]: R1.1. All Transmission Operators and Balancing Authorities within its Reliability Coordinator Area R1.2. Adjacent Reliability Coordinators within the same interconnection. R2. Each Reliability Coordinator shall designate an Alternative Interpersonal Communications capability with the following entities to exchange Interconnection and operating information: [Violation Risk Factor: High][Time Horizon: Real-time Operations]: R2.1. All Transmission Operators and Balancing Authorities within its Reliability Coordinator Area R2.2. Adjacent Reliability Coordinators within the same interconnection. R3. Each Transmission Operator shall have Interpersonal Communications capability with the following entities to exchange Interconnection and operating information: [Violation Risk Factor: High][Time Horizon: Real-time Operations]: R3.1. Its Reliability Coordinator R3.2. Each Balancing Authority within its Transmission Operator Area. R3.3. Each Distribution Provider within its Transmission Operator Area. R3.4. Each Generator Operator within its Transmission Operator Area. R4. Each Transmission Operator shall designate an Alternative Interpersonal Communications capability with the following entities to exchange Interconnection and operating information: [Violation Risk Factor: High][Time Horizon: Real-time Operations]: R4.1. Its Reliability Coordinator R4.2. Each Balancing Authority within its Transmission Operator Area. Notes: The requirements we made clearer as to which capabilities specific entities were required to have to reliability. November 16, 2010July 30, December 30,
3 November 16, 2010July 30, December 30,
4 R1. Each Reliability Coordinator, Transmission Operator and Balancing Authority shall provide adequate and reliable telecommunications facilities for the exchange of Interconnection and operating information: [Violation Risk Factor: High] R1.1. Internally. [Violation Risk Factor: High] R1.2. R1.3. R1.4. Between the Reliability Coordinator and its Transmission Operators and Balancing Authorities. [Violation Risk Factor: High] With other Reliability Coordinators, Transmission Operators, and Balancing Authorities as necessary to maintain reliability. [Violation Risk Factor: High] Where applicable, these facilities shall be redundant and diversely routed. [Violation Risk Factor: High] R5. Each Balancing Authority shall have Interpersonal Communications capability with the following entities to exchange Interconnection and operating information: [Violation Risk Factor: High][Time Horizon: Real-time Operations]: R5.1. Its Reliability Coordinator R5.2. Each Transmission Operator that operates Facilities within its Balancing Authority Area R5.3. Each Generator Operator that operates Facilities within its Balancing Authority Area R5.4. Each Distribution Provider within its Balancing Authority Area R6. Each Balancing Authority shall designate an Alternative Interpersonal Communications capability with the following entities to exchange Interconnection and operating information: [Violation Risk Factor: High][Time Horizon: Real-time Operations]: R6.1. Its Reliability Coordinator R6.2. Each Transmission Operator that operates Facilities within its Balancing Authority Area) R7. Each Distribution Provider shall have Interpersonal Communications capability with the following entities to exchange Interconnection and operating information: [Violation Risk Factor: High][Time Horizon: Real-time Operations] 7.1 Its Transmission Operator 7.2 Its Balancing Authority. R8. Each Generator Operator shall have Interpersonal Communications capability with the following entities to exchange Interconnection and operating information [Violation Risk Factor: High][Time Horizon: Real-time Operations] 8.1 Its Balancing Authority 8.2 Its Transmission Operator. Notes: The requirements we made clearer as to which capabilities specific entities were required to have to reliability. R8 is created to address the FERC directive to expands the applicability to include generator operators and distribution providers and includes Requirements for their telecommunications facilities November 16, 2010July 30, December 30,
5 November 16, 2010July 30, December 30,
6 R2. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall manage, alarm, test and/or actively monitor vital telecommunications facilities. Special attention shall be given to emergency telecommunications facilities and equipment not used for routine communications. [Violation Risk Factor: Medium] COM-001-2: R9. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall, on at least a monthly basis, test its Alternative Interpersonal Communications capability. If the test is unsuccessful, the entity shall initiate action to repair or designate a replacement Alternative Interpersonal Communications within 2 hours. [Violation Risk Factor: Medium][Time Horizon: Real-time Operations] Notes: November 16, 2010July 30, December 30,
7 R3. Each Reliability Coordinator, Transmission Operator and Balancing Authority shall provide a means to coordinate telecommunications among their respective areas. This coordination shall include the ability to investigate and recommend solutions to telecommunications problems within the area and with other areas. [Violation Risk Factor: Lower] COM R10. Each Reliability Coordinator, Transmission Operator, Balancing Authority, Distribution Provider, and Generator Operator shall notify impacted entities within 60 minutes of the detection of a failure of its Interpersonal Communications capabilities that lasts 30 minutes or longer. [Violation Risk Factor: Medium][Time Horizon: Realtime Operations] November 16, 2010July 30, December 30,
8 R4. Unless agreed to otherwise, each Reliability Coordinator, Transmission Operator, and Balancing Authority shall use English as the language for all communications between and among operating personnel responsible for the real-time generation control and operation of the interconnected Bulk Electric System. Transmission Operators and Balancing Authorities may use an alternate language for internal operations. [Violation Risk Factor: Medium] This requirement is being vetted by the OPCPSDT in COM-003. This requirement and measure will be removed from COM-001. Notes: November 16, 2010July 30, December 30,
9 R5. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall have written operating instructions and procedures to enable continued operation of the system during the loss of telecommunications facilities. [Violation Risk Factor: Lower] EOP R1. Each Reliability Coordinator, Transmission Operator and Balancing Authority shall have a plan to continue reliability operations in the event its control center becomes inoperable. The contingency plan must meet the following requirements: R1.1. The contingency plan shall not rely on data or voice communication from the primary control facility to be viable. R1.2. The plan shall include procedures and responsibilities for providing basic tie line control and procedures and for maintaining the status of all interarea schedules, such that there is an hourly accounting of all schedules. R1.3. The contingency plan must address monitoring and control of critical transmission facilities, generation control, voltage control, time and frequency control, control of critical substation devices, and logging of significant power system events. The plan shall list the critical facilities. R1.4. The plan shall include procedures and responsibilities for maintaining basic voice communication capabilities with other areas. R1.5. The plan shall include procedures and responsibilities for conducting periodic tests, at least annually, to ensure viability of the plan. R1.6. The plan shall include procedures and responsibilities for providing annual training to ensure that operating personnel are able to implement the contingency plans. R1.7. The plan shall be reviewed and updated annually. R1.8. Interim provisions must be included if it is expected to take more than one hour to implement the contingency plan for loss of primary control facility. Notes: The RC SDT proposes retiring R5 as it is redundant with EOP Requirement R1. November 16, 2010July 30, December 30,
10 R6. Each NERCNet User Organization shall adhere to the requirements in Attachment 1-COM-001, NERCNet Security Policy. [Violation Risk Factor: Lower] None - retire Notes: The RC SDT is recommending that R6 be retired. This is an ERO procedural issue and should not be in a reliability standard. It should be included in the ERO Rules of Procedure. November 16, 2010July 30, December 30,
11 Functions that Must Comply with the Requirements in the Standards Standard Reliability Coordinator Balancing Authority Functions that Must Comply With the Requirements Purchasing Selling EntityInterc hange Authority Transmission Operator Transmission Service ProviderOwn er Load Serving Entity Generator Owner Generator Operator Distribution Provider COM Telecommuni Communications X X X X X X X X November 16, 2010July 30, December 30,
A. 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
Standard COM Communication and Coordination
A. Introduction 1. Title: Communication and Coordination 2. Number: COM-002-3 3. Purpose: To ensure Emergency communications between operating personnel are effective. 4. Applicability 4.1. Reliability
primary Control Center, for the exchange of Real-time data with its Balancing
A. Introduction 1. Title: Reliability Coordination Monitoring and Analysis 2. Number: IRO-002-5 3. Purpose: To provide System Operators with the capabilities necessary to monitor and analyze data needed
Standard TOP Transmission Operations
A. Introduction 1. Title: Transmission Operations 2. Number: TOP-001-34 3. Purpose: To prevent instability, uncontrolled separation, or Cascading outages that adversely impact the reliability of the Interconnection
TOP-010-1(i) Real-time Reliability Monitoring and Analysis Capabilities
A. Introduction 1. Title: Real-time Reliability Monitoring and Analysis Capabilities 2. Number: TOP-010-1(i) 3. Purpose: Establish requirements for Real-time monitoring and analysis capabilities to support
COM Interpersonal Communications Capabilities
COM-001-3 Interpersonal Communications Capabilities 1 Background In the FERC Notice of Proposed Rulemaking (NOPR) for COM-001-2, the Commission asked for comments on whether the standard should be modified
Standard 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
Standard 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
This 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
Standard Authorization Request Form
Standard Authorization Request Form Title of Proposed Standard: Project 2009-02: Real-time Reliability Monitoring and Analysis Capabilities Original Request Date: June 4, 2009 Revised Date: January 15,
COM Operating Personnel Communications Protocols. October 31, 2013
COM-002-4 Operating Personnel Communications Protocols October 31, 2013 Agenda Introductory Remarks: Mark Lauby Project 2007 02 Background COM 002 4 Requirements Implementation Plan Compliance VSL/VRF
Project Posting 8 Frequently Asked Questions Guide
Project 2007-02 Posting 8 Frequently Asked Questions Guide General Questions 1. What were the inputs that drove the development of posting 8 of Project 2007-02? The NERC Board of Trustees November 7 th,
Standard 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
NERC 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
New 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...
5. Effective Date: The first day of the first calendar quarter after applicable regulatory approval.
Introduction 1. Title: IROL and SOL Mitigation in the ERCOT Region 2. Number: IRO-006-TRE-1 3. Purpose: To provide and execute transmission loading relief procedures that can be used to mitigate SOL or
Implementation 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
Reliability Standard Audit Worksheet 1
Reliability Standard Audit Worksheet 1 CIP-012-1 Cyber Security Communications between Control Centers This section to be completed by the Compliance Enforcement Authority. Audit ID: Registered Entity:
Standard 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
Standards 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.
Standard 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
November 9, Revisions to the Violation Risk Factors for Reliability Standards IRO and TOP
!! November 9, 2016 VIA ELECTRONIC FILING Jim Crone Director, Energy Division Manitoba Innovation, Energy and Mines 1200-155 Carlton Street Winnipeg MB R3C 3H8 RE: Revisions to the Violation Risk Factors
Standard 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
Standard 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
Standard 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
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 is adopted by the NERC Board of Trustees (Board).
NERC Management Response to the Questions of the NERC Board of Trustees on Reliability Standard COM September 6, 2013
NERC Management Response to the Questions of the NERC Board of Trustees on Reliability Standard COM-003-1 September 6, 2013 At the August 14-15, 2013 meeting of the Board of Trustees ( Board ) of the North
Implementation 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
Implementation 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
CIP 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
Standard 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.
Standard 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
CIP 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
Standard 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)
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 is adopted by the NERC Board of Trustees (Board).
Draft CIP Standards Version 5
Draft CIP Standards Version 5 Technical Webinar Part 1 Project 2008-06 Cyber Security Order 706 Standards Drafting Team November 15, 2011 Agenda Opening Remarks John Lim, Consolidated Edison, Chair V5
TOP for Transmission Operators
Meeting Title Date TOP-001-4 for Transmission Operators Compliance Team Lead, Keith Smith Background Effective July 1, 2018 Replaces currently effective TOP-001-3 Modified to address reliability concerns
Standard 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
Project Consideration of Commission Directives in Order No. 693
Project 2009-02 Consideration of Commission Directives in Order Order P 905-906 Further, consistent with the NOPR, the Commission directs the ERO to modify IRO-002-1 to require a minimum set of tools that
Standard 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)
Standard CIP Cyber Security Physical Security
A. Introduction 1. Title: Cyber Security Physical Security of Critical Cyber Assets 2. Number: CIP-006-3 3. Purpose: Standard CIP-006-3 is intended to ensure the implementation of a physical security program
Unofficial Comment Form Project Operating Personnel Communications Protocols COM Operating Personnel Communications Protocols
Project 2007-02 Operating Personnel Communications Protocols COM-002-4 Operating Personnel Communications Protocols Please DO NOT use this form. Please use the electronic comment form to submit comments
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,
Violation Risk Factor and Violation Severity Level Justification Project Modifications to CIP-008 Cyber Security Incident Reporting
Violation Risk Factor and Justification Project 2018-02 Modifications to CIP-008 Cyber Security Incident Reporting This document provides the standard drafting team s (SDT s) justification for assignment
Standard 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
This 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
Proposed 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
Unofficial Comment Form Project Operating Personnel Communications Protocols COM-002-4
Project 2007-02 Operating Personnel Communications Protocols COM-002-4 Please DO NOT use this form. Please use the electronic comment form to submit comments on the proposed draft COM 002 4 (Operating
Standard 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
Standard 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
Concept White Paper. Concepts for Proposed Content of Eventual Standard(s) for Project : Real-Time Monitoring and Analysis Capabilities
Concept White Paper Concepts for Proposed Content of Eventual Standard(s) for Project 2009-02: Real-Time Monitoring and Analysis Capabilities Real-time Monitoring and Analysis Capabilities Standard Drafting
Standard 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)
Standard 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
Disclaimer 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...
CIP Cyber Security 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 becomes effective. Development Steps Completed
Project 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,
CIP 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
CIP Cyber Security Recovery Plans for BES Cyber Systems
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
Reliability 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
CIP 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
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. Description of Current Draft
This 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
CIP 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
Modifications to TOP and IRO Standards
Modifications to TOP and IRO Standards Jason Smith, Mgr Reliability Standards Development SPP RTO Compliance Forum September 21-22, 2016 Project 2016-01 Background FERC issued Order No. 817 in November
Québec Reliability Standards Compliance Monitoring and Enforcement Program Implementation Plan Annual Implementation Plan
Québec Reliability Standards Compliance Monitoring and Enforcement Program Implementation Plan 2017 Annual Implementation Plan Effective Date: January 1, 2017 Approved by the Régie: December 1, 2016 Table
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. Description of Current Draft
Modifications to TOP and IRO Standards
Modifications to TOP and IRO Standards Jason Smith, Southwest Power Pool Industry Webinar July 22, 2016 NERC Antitrust Guidelines It is NERC's policy and practice to obey the antitrust laws to avoid all
CIP Cyber Security Personnel & Training
A. Introduction 1. Title: Cyber Security Personnel & Training 2. Number: CIP-004-5.1 3. Purpose: To minimize the risk against compromise that could lead to misoperation or instability in the BES from individuals
ERO 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
COM Communications and Coordination
COM-002-2 Communications and Coordination February 27, 2014 Lonnie Lindekugel ~ SPP Jim Nail ~ City of Independence INTRODUCTION NERC Reliability Standard COM-002-2 (Communications and Coordination) serves
Standards 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.
Cyber 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
Comment Form for 1 st Draft of Standard for Backup Facilities (Project )
Comment Form for 1 st Draft of Standard for Backup Facilities (Project 2006-04) Please use this form to submit comments on the 1 st draft of the standards for Backup Facilities (Project 2006-04). Comments
requirements in a NERC or Regional Reliability Standard.
CIP 002 5.1 Cyber Security BES Cyber System Categorization A. Introduction 1. Title: Cyber Security BES Cyber System Categorization 2. Number: CIP 002 5.1 3. Purpose: To identify and categorize BES Cyber
Project , COM Operating Personnel Communications Protocols Rationale and Technical Justification
Project 2007-02, COM-002-4 Operating Personnel Communications Protocols Rationale and Technical Justification Posting 8: Background and Justification for COM-002-4 Requirements The purpose of the proposed
CIP Cyber Security Physical Security of BES Cyber Systems
A. Introduction 1. Title: Cyber Security Physical Security of BES Cyber Systems 2. Number: CIP-006-5 3. Purpose: To manage physical access to BES Cyber Systems by specifying a physical security plan in
CIP 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
This 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
CIP Cyber Security Recovery Plans for BES Cyber Systems
A. Introduction 1. Title: Cyber Security Recovery Plans for BES Cyber Systems 2. Number: CIP-009-5 3. Purpose: To recover reliability functions performed by BES Cyber Systems by specifying recovery plan
CIP Cyber Security Configuration Change Management and Vulnerability Assessments
CIP 010 1 Cyber Security Configuration Change Management and Vulnerability Assessments A. Introduction 1. Title: Cyber Security Configuration Change Management and Vulnerability Assessments 2. Number:
CIP Cyber Security Configuration Change Management and Vulnerability Assessments
CIP-010-2 3 Cyber Security Configuration Change Management and Vulnerability Assessments A. Introduction 1. Title: Cyber Security Configuration Change Management and Vulnerability Assessments 2. Number:
CIP Cyber Security Recovery Plans for BES Cyber Systems
A. Introduction 1. Title: Cyber Security Recovery Plans for BES Cyber Systems 2. Number: CIP-009-6 3. Purpose: To recover reliability functions performed by BES Cyber Systems by specifying recovery plan
Unofficial 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
1. 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
Standard EOP Disturbance Reporting
A. Introduction 1. Title: Disturbance Reporting 2. Number: EOP-004-1 3. Purpose: Disturbances or unusual occurrences that jeopardize the operation of the Bulk Electric System, or result in system equipment
Reliability Standard Audit Worksheet 1
Reliability Standard Audit Wksheet 1 EOP-008-2 Loss of Control Center Functionality This section to be completed by the Compliance Enfcement Authity. Audit ID: Registered Entity: NCR Number: Compliance
4.1.1 Generator Owner Transmission Owner that owns synchronous condenser(s)
A. Introduction 1. Title: Verification and Data Reporting of Generator Real and Reactive Power Capability and Synchronous Condenser Reactive Power Capability 2. Number: MOD-025-2 3. Purpose: To ensure
CIP Cyber Security Configuration Change Management and Vulnerability Assessments
CIP-010-2 Cyber Security Configuration Change Management and Vulnerability Assessments A. Introduction 1. Title: Cyber Security Configuration Change Management and Vulnerability Assessments 2. Number:
TOP/IRO Standards. RC Users Group January 21, Vic Howell Manager, Operations Engineering Support
TOP/IRO Standards RC Users Group January 21, 2016 Vic Howell Manager, Operations Engineering Support Saad Malik Manager, Real-Time Operations Engineering New/Revised TOP & IRO Standards November 19, 2015,
DRAFT. 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...
Standard Development Timeline
CIP-002-6 Cyber Security BES Cyber System Categorization Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the
Standard INT Interchange Authority Distributes Arranged Interchange
Standard INT-005-2 Authority Distributes A. Introduction 1. Title: Authority Distributes 2. Number: INT-005-2 3. Purpose: To ensure that the implementation of between Source and Sink Balancing Authorities
CIP Cyber Security Critical Cyber Asset Identification. Rationale and Implementation Reference Document
CIP-002-4 Cyber Security Critical Cyber Asset Identification Rationale and Implementation Reference Document NERC Cyber Security Standards Drafting Team for Order 706 December 2010 This document provides
4.1.1 Generator Owner Transmission Owner that owns synchronous condenser(s)
A. Introduction 1. Title: Verification and Data Reporting of Generator Real and Reactive Power Capability and Synchronous Condenser Reactive Power Capability 2. Number: MOD-025-2 3. Purpose: To ensure
Consideration 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
Violation Risk Factor and Violation Severity Level Justifications Project Modifications to CIP Standards
Violation Risk Factor and Violation Severity Level Justifications Project 2016-02 Modifications to CIP Standards This document provides the standard drafting team s (SDT s) justification for assignment
DRAFT Reliability Standard Audit Worksheet 1
DRAFT Reliability Standard Audit Worksheet 1 PRC-025-2 Generator Relay Loadability This section to be completed by the Compliance Enforcement Authority. Audit ID: Registered Entity: NCR Number: Compliance
NERC Transmission Availability Data System (TADS): Element Identifier Data Submission Addendum
Transmission Availability Data System (TADS) Element Identifier Data Submission Addendum May 28, 2013 3353 Peachtree Road NE NERC Transmission Availability Data System (TADS): Element Identifier Data Submission
PRC Coordination of Protection Systems for Performance During Faults
PRC-027-1 Coordination of Protection Systems for Performance During Faults A. Introduction 1. Title: Coordination of Protection Systems for Performance During Faults 2. Number: PRC-027-1 3. Purpose: To
NORTH AMERICAN ELECTRIC RELIABILITY CORPORATION
NORTH AMERICAN ELECTRIC RELIABILITY CORPORATION NARUC Energy Regulatory Partnership Program The Public Services Regulatory Commission of Armenia and The Iowa Utilities Board Janet Amick Senior Utility