Standard COM-002-2a Communications and Coordination

Similar documents
Standard COM Communication and Coordination

5. Effective Date: The first day of the first calendar quarter after applicable regulatory approval.

Standard EOP Disturbance Reporting

A. Introduction. B. Requirements and Measures

COM Communications and Coordination

Standard Development Timeline

Standard CIP 007 3a Cyber Security Systems Security Management

Standard INT Dynamic Transfers

Standard INT Interchange Authority Distributes Arranged Interchange

TOP-010-1(i) Real-time Reliability Monitoring and Analysis Capabilities

This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective.

Standard CIP Cyber Security Electronic Security Perimeter(s)

Standard CIP 005 2a Cyber Security Electronic Security Perimeter(s)

primary Control Center, for the exchange of Real-time data with its Balancing

Standard CIP-006-3c Cyber Security Physical Security

Standard CIP 007 4a Cyber Security Systems Security Management

Standard CIP Cyber Security Security Management Controls

Standard CIP 005 4a Cyber Security Electronic Security Perimeter(s)

Standard CIP 004 3a Cyber Security Personnel and Training

Standard INT Dynamic Transfers

November 9, Revisions to the Violation Risk Factors for Reliability Standards IRO and TOP

A. Introduction 1. Title: 2. Number: 3. Purpose: 4. Applicability: 4.1. Functional Entities: Balancing Authority Distribution Provider

Standard CIP Cyber Security Systems Security Management

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

CIP Cyber Security Personnel & Training

Standard CIP Cyber Security Electronic Security Perimeter(s)

Standard CIP-006-4c Cyber Security Physical Security

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 CIP-006-1a Cyber Security Physical Security

Standard CIP Cyber Security Physical Security

4.1.1 Generator Owner Transmission Owner that owns synchronous condenser(s)

Standard CIP Cyber Security Incident Reporting and Response Planning

Standard TOP Transmission Operations

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

Standard CIP Cyber Security Critical Cyber As s et Identification

Standard CIP Cyber Security Systems Security Management

Standard Development Timeline

4.1.1 Generator Owner Transmission Owner that owns synchronous condenser(s)

Standard CIP Cyber Security Critical Cyber Asset Identification

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

Implementation Plan for COM-001-2

Standard CIP Cyber Security Physical Security

Standard Development Timeline

CIP Cyber Security Systems Security Management

CIP Cyber Security Recovery Plans for BES Cyber Systems

Standard CIP Cyber Security Critical Cyber As s et Identification

Unofficial Comment Form Project Operating Personnel Communications Protocols COM-002-4

Standard Development Timeline

CIP Cyber Security Personnel & Training

Standard CIP Cyber Security Critical Cyber Asset Identification

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.

CIP Cyber Security Configuration Management and Vulnerability Assessments

CIP Cyber Security Recovery Plans for BES Cyber Systems

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

A. Introduction. Page 1 of 22

CANADIAN PAYMENTS ASSOCIATION LVTS RULE 11 CHANGE MANAGEMENT, TESTING AND CERTIFICATION

1. SAR posted for comment on January 15, Standard Drafting Team appointed on January 29, 2014

Standard Development Timeline

New Brunswick 2018 Annual Implementation Plan Version 1

LVTS RULE 11 CHANGE MANAGEMENT, TESTING AND CERTIFICATION 2018 CANADIAN PAYMENTS ASSOCIATION

Guidelines for Submitting NERC Reliability Standards Required Documents to the SPP Reliability Coordinator and the SPP Balancing Authority Version 1

NERC Relay Loadability Standard Reliability Standards Webinar November 23, 2010

PRC Coordination of Protection Systems for Performance During Faults

CIP Cyber Security Physical Security of BES Cyber Systems

CIP 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 the standard becomes effective.

Standard Development Timeline

CIP Cyber Security Security Management Controls. A. Introduction

TOP/IRO Standards. RC Users Group January 21, Vic Howell Manager, Operations Engineering Support

CIP Cyber Security Recovery Plans for BES Cyber Systems

1. Post for 45-day comment period and pre-ballot review. 7/26/ Conduct initial ballot. 8/30/2010

Cyber Security Reliability Standards CIP V5 Transition Guidance:

BSCP128 Production, Submission, Audit and Approval of Line Loss Factors Version 3.0. Balancing and Settlement Code. BSC Procedure DRAFT

Québec Reliability Standards Compliance Monitoring and Enforcement Program Implementation Plan Annual Implementation Plan

Cyber Security Standards Drafting Team Update

BSCP128 Production, Submission, Audit and Approval of Line Loss Factors Version 3.0. Balancing and Settlement Code. BSC Procedure DRAFT

CIP Cyber Security Physical Security of BES Cyber Systems

CIP Cyber Security Information Protection

CIP Cyber Security Configuration Change Management and Vulnerability AssessmentsManagement

requirements in a NERC or Regional Reliability Standard.

Implementation Plan for Newly Identified Critical Cyber Assets and Newly Registered Entities

Standard Development Timeline

Additional 45-Day Comment Period September Final Ballot is Conducted October/November Board of Trustees (Board) Adoption November 2014

1. SAR posted for comment on January 15, Standard Drafting Team appointed on January 29, 2014

Auction Calendar 2017/2018 for Capacity Allocation Mechanism Network Code

Alberta Reliability Standards Compliance Monitoring Program. Version 1.1

Project Posting 8 Frequently Asked Questions Guide

Standard Development Timeline

Project , COM Operating Personnel Communications Protocols Rationale and Technical Justification

DISADVANTAGED BUSINESS ENTERPRISE PROGRAM. Unified Certification Program OKLAHOMA

Standard Development Timeline

COM Operating Personnel Communications Protocols. October 31, 2013

Implementation Plan for Newly Identified Critical Cyber Assets and Newly Registered Entities

Additional 45-Day Comment Period and Ballot November Final Ballot is Conducted January Board of Trustees (Board) Adoption February 2015

Proposed Clean and Redline for Version 2 Implementation Plan

CIP Cyber Security Electronic Security Perimeter(s)

Implementation Plan. Project CIP Version 5 Revisions 1. January 23, 2015

NERC CIP Information Protection

Transcription:

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 and that these communications capabilities are staffed and available for addressing a real-time emergency condition. To ensure communications by operating personnel are effective. 4. Applicability 4.1. Reliability Coordinators. 4.2. Balancing Authorities. 4.3. Transmission Operators. 4.4. Generator Operators. 5. Effective Date: January 1, 2007 B. Requirements R1. Each Transmission Operator, Balancing Authority, and Generator Operator shall have communications (voice and data links) with appropriate Reliability Coordinators, Balancing Authorities, and Transmission Operators. Such communications shall be staffed and available for addressing a real-time emergency condition. R1.1. Each Balancing Authority and Transmission Operator shall notify its Reliability Coordinator, and all other potentially affected Balancing Authorities and Transmission Operators through predetermined communication paths of any condition that could threaten the reliability of its area or when firm load shedding is anticipated. R2. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall issue directives in a clear, concise, and definitive manner; shall ensure the recipient of the directive repeats the information back correctly; and shall acknowledge the response as correct or repeat the original statement to resolve any misunderstandings. C. Measures M1. Each Transmission Operator, Balancing Authority and Generator Operator shall have communication facilities (voice and data links) with appropriate Reliability Coordinators, Balancing Authorities, and Transmission Operators and shall have and provide as evidence, a list of communication facilities or other equivalent evidence that confirms that the communications have been provided to address a real-time emergency condition. (Requirement 1, part 1) M2. The Balancing Authority and Transmission Operator shall have and provide upon request evidence that could include but is not limited to, operator logs, voice recordings or transcripts of voice recordings, electronic communications, or other equivalent evidence that will be used to determine if it notified its Reliability Coordinator, and all other potentially affected Balancing Authorities and Transmission Operators of a condition that could threaten the reliability of its area or when firm load shedding was anticipated. (Requirement 1.1) D. Compliance 1. Compliance Monitoring Process 1.1. Compliance Monitoring Responsibility Page 1 of 4

Regional Reliability Organizations shall be responsible for compliance monitoring. 1.2. Compliance Monitoring and Reset Time Frame One or more of the following methods will be used to assess compliance: - Self-certification (Conducted annually with submission according to schedule.) - Spot Check Audits (Conducted anytime with up to 30 days notice given to prepare.) - Periodic Audit (Conducted once every three years according to schedule.) - Triggered Investigations (Notification of an investigation must be made within 60 days of an event or complaint of noncompliance. The entity will have up to 30 days to prepare for the investigation. An entity may request an extension of the preparation period and the extension will be considered by the Compliance Monitor on a case-by-case basis.) The Performance-Reset Period shall be 12 months from the last finding of non-compliance. 1.3. Data Retention Each Balancing Authority, Transmission Operator and Generator Operator shall keep evidence of compliance for the previous two calendar years plus the current year. (Measure 1) Each Balancing Authority and Transmission Operator shall keep 90 days of historical data. (Measure 2). If an entity is found non-compliant the entity shall keep information related to the noncompliance until found compliant or for two years plus the current year, whichever is longer. Evidence used as part of a triggered investigation shall be retained by the entity being investigated for one year from the date that the investigation is closed, as determined by the Compliance Monitor. The Compliance Monitor shall keep the last periodic audit report and all requested and submitted subsequent compliance records. 1.4. Additional Compliance Information None. 2. Levels of Non-Compliance for Transmission Operator and Balancing Authority: 2.1. Level 1: Not applicable. 2.2. Level 2: Not applicable. 2.3. Level 3: Not applicable. 2.4. Level 4: Communication did not occur as specified in R1.1. 3. Levels of Non-Compliance for Generator Operator: 3.1. Level 1: Not applicable. 3.2. Level 2: Not applicable. 3.3. Level 3: Not applicable. 3.4. Level 4: Communication facilities are not provided to address a real-time emergency condition as specified in R1. E. Regional Differences Page 2 of 4

None identified. Version History Version Date Action Change Tracking 0 April 1, 2005 Effective Date New 0 August 8, 2005 Removed Proposed from Effective Date Errata 1 February 7, 2006 Adopted by Board of Trustees Revised 2 November 1, 2006 Adopted by Board of Trustees Revised 2a February 9, 2012 Interpretation of R2 adopted by Board of Trustees Project 2009-22 Page 3 of 4

Appendix 1 Requirement Number and Text of Requirement R2. Each Reliability Coordinator, Transmission Operator, and Balancing Authority shall issue directives in a clear, concise, and definitive manner; shall ensure the recipient of the directive repeats the information back correctly; and shall acknowledge the response as correct or repeat the original statement to resolve any misunderstandings. Question: Please clarify whether routine operating instructions are directives or whether directives are limited to actual and anticipated emergency operating conditions. Response: COM-002-2 R2 does not specify the conditions under which a directive is issued, nor does it define directive. It only provides that the requirements be followed when a directive is issued to address a realtime emergency. Routine operating instructions during normal operations would not require the communications protocols for repeat backs as specified in R2. Page 4 of 4

* FOR INFORMATIONAL PURPOSES ONLY * Effective Date of Standard: COM-002-2a Communication and Coordination United States Standard Requirement Effective Date of Standard Phased In Inactive Date Implementation Date (if applicable) COM-002-2a All 06/30/2016 This standard has not yet been approved by the applicable regulatory authority. Printed On: December 04, 2017, 05:20 AM