Standard INT Interchange Authority Distributes Arranged Interchange
|
|
|
- Veronica Casey
- 5 years ago
- Views:
Transcription
1 Standard INT Authority Distributes A. Introduction 1. Title: Authority Distributes 2. Number: INT Purpose: To ensure that the implementation of between Source and Sink Balancing Authorities is distributed by an Authority such that information is available for reliability assessments. 4. Applicability 4.1. Authority. 5. Proposed Effective Date: Upon approval of Board of Trustees. B. Requirements R1. Prior to the expiration of the time period defined in the Timing Table, Column A, the Authority shall distribute the information for reliability assessment to all reliability entities involved in the. R1.1. When a Balancing Authority or Coordinator initiates a Curtailment to Confirmed or Implemented for reliability, the Authority shall distribute the information for reliability assessment only to the Source Balancing Authority and the Sink Balancing Authority. C. Measures M1. For each, the Authority shall be able to provide evidence that it has distributed the information to all reliability entities involved in the within the applicable time frame. D. Compliance 1. Compliance Monitoring Process 1.1. Compliance Monitoring Responsibility Regional Organization Compliance Monitoring Period and Reset Time Frame The Performance-Reset Period shall be twelve months from the last non-compliance to Requirement Data Retention The Authority shall keep 90 days of historical data. The Compliance Monitor shall keep audit records for a minimum of three calendar years Additional Compliance Information Each Authority shall demonstrate compliance to the Compliance Monitor within the first year that this standard becomes effective or the first year the entity commences operation by self-certification to the Compliance Monitor. Subsequent to the initial compliance review, compliance may be: Verified by audit at least once every three years Verified by spot checks in years between audits. Draft: February 15, 2007 Page 1 of 3
2 Standard INT Authority Distributes Verified by annual audits of noncompliant Authorities, until compliance is demonstrated Verified at any time as the result of a specific complaint of failure to perform R1. Complaints must be lodged within 60 days of the incident. The Compliance Monitor will evaluate complaints. Each Authority shall make the following available for inspection by the Compliance Monitor upon request: For compliance audits and spot checks, relevant data and system log records for the audit period which indicate the Authority s distribution of all information to all reliability entities involved in an. The Compliance Monitor may request up to a three month period of historical data ending with the date the request is received by the Authority For specific complaints, only those data and system log records associated with the specific event contained in the complaint which indicate that the Authority distributed the information to all reliability entities involved in that specific. 2. Levels of Non-Compliance 2.1. Level 1: One occurrence 1 of not distributing information to all involved reliability entities as described in R Level 2: Two occurrences 1 of not distributing information to all involved reliability entities as described in R Level 3: Three occurrences 1 of not distributing information to all involved reliability entities as described in R Level 4: Four or more occurrences 1 of not distributing information to all involved reliability entities as described in R1 or no evidence provided. E. Regional Differences None Version History Version Date Action Change Tracking 1 This does not include instances of not distributing information due to extenuating circumstances approved by the Compliance Monitor. Draft: February 15, 2007 Page 2 of 3
3 Standard INT Authority Distributes Timing Table Request for Timeline with Minimum -Related Response Times Ramp Start A B C D If Actual (RFI) is IA Makes Initial Distribution of BA and TSP Conduct IA Verifies Data Complete IA Compiles and Distributes Status BA Prepares Confirmed for Implementation Minimum Total Period (Columns A through D) for all Interconnections except WECC all <20 minutes prior to < 5 minutes from all 10 minutes >20 minutes to all >1 hour to < 4 hours prior to < 20 minutes all > 39 minutes 1 hour plus 1 minute > 4 hours prior to < 2 hours from all > 1 hour 58 minutes prior to 4 hours Draft: February 15, 2007 Page 3 of 3
4 Standard INT Response to Authority A. Introduction 1. Title: Response to Authority 2. Number: INT Purpose: To ensure that each is checked for reliability before it is implemented. 4. Applicability 4.1. Balancing Authority Transmission Service Provider. 5. Proposed Effective Date: Upon approval of Board of Trustees. B. Requirements R1. Prior to the expiration of the reliability assessment period defined in the Timing Table, Column B, the Balancing Authority and Transmission Service Provider shall respond to a request from an Authority to transition an to a Confirmed. R1.1. Each involved Balancing Authority shall evaluate the with respect to: R Energy profile (ability to support the magnitude of the ). R Ramp (ability of generation maneuverability to accommodate). R Scheduling path (proper connectivity of Adjacent Balancing Authorities). R1.2. Each involved Transmission Service Provider shall confirm that the transmission service arrangements associated with the have adjacent Transmission Service Provider connectivity, are valid and prevailing transmission system limits will not be violated. C. Measures M1. The Balancing Authority and Transmission Service Provider shall each provide evidence that it responded, relative to transitioning an to a Confirmed, to each request from an Authority within the reliability assessment period defined in the Timing Table, Column B. D. Compliance 1. Compliance Monitoring Process 1.1. Compliance Monitoring Responsibility Regional Organization Compliance Monitoring Period and Reset Time Frame The Performance-Reset Period shall be twelve months from the last non-compliance to Requirement Data Retention The Balancing Authority and Transmission Service Provider shall each keep 90 days of historical data. The Compliance Monitor shall keep audit records for a minimum of three calendar years Additional Compliance Information The Balancing Authority and Transmission Service Provider shall demonstrate compliance to the Compliance Monitor within the first year that this standard becomes Draft: February 15, 2007 Page 1 of 4
5 Standard INT Response to Authority effective or the first year the entity commences operation by self-certification to the Compliance Monitor. Subsequent to the initial compliance review, compliance may be: Verified by audit at least once every three years Verified by spot checks in years between audits Verified by annual audits of non-compliant Authorities, until compliance is demonstrated Verified at any time as the result of a complaint. Complaints must be lodged within 60 days of the incident. The Compliance Monitor will evaluate complaints. The Balancing Authority, and Transmission Service Provider shall make the following available for inspection by the Compliance Monitor upon request: For compliance audits and spot checks, relevant data and system log records and agreements for the audit period which indicate a reliability entity identified in R1 responded to all instances of the Authority s communication under Standard INT-005 Requirement 1 concerning the pending transition of an to Confirmed. The Compliance Monitor may request up to a three month period of historical data ending with the date the request is received by the Balancing Authority, or Transmission Service Provider For specific complaints, agreements and those data and system log records associated with the specific event contained in the complaint which indicates a reliability entity identified in R1 has responded to the Authority s communication under INT-005 R1 concerning the pending transition of to Confirmed for that specific. 2. Levels of Non-Compliance 2.1. Level 1: One occurrence 1 of not responding to the Authority as described in R Level 2: Two occurrences 1 of not responding to the Authority as described in R Level 3: Three occurrences 1 of not responding to the Authority as described in R Level 4: Four or more occurrences 1 of not responding to the Authority as described in R1 or no evidence provided. E. Regional Differences None Version History Version Date Action Change Tracking 1 This does not include instances of not responding due to extenuating circumstances approved by the Compliance Monitor. Draft: February 15, 2007 Page 2 of 4
6 Standard INT Response to Authority Draft: February 15, 2007 Page 3 of 4
7 Standard INT Response to Authority Timing Table Request for Timeline with Minimum -Related Response Times Ramp Start A B C D If Actual (RFI) is IA Makes Initial Distribution of BA and TSP Conduct IA Verifies Data Complete IA Compiles and Distributes Status BA Prepares Confirmed for Implementation Minimum Total Period (Columns A through D) for all Interconnections except WECC all <20 minutes prior to < 5 minutes from all 10 minutes >20 minutes to all >1 hour to < 4 hours prior to < 20 minutes all > 39 minutes 1 hour plus 1 minute > 4 hours prior to < 2 hours from all > 1 hour 58 minutes prior to 4 hours Draft: February 15, 2007 Page 4 of 4
8 Standard INT Authority Distributes Status A. Introduction 1. Title: Authority Distributes Status 2. Number: INT Purpose: To ensure that the implementation of between Source and Sink Balancing Authorities is coordinated by an Authority. 4. Applicability 4.1. Authority. 5. Proposed Effective Date: Upon approval of Board of Trustees. B. Requirements R1. Prior to the expiration of the time period defined in the Timing Table, Column C, the Authority shall distribute to all Balancing Authorities (including Balancing Authorities on both sides of a direct current tie), Transmission Service Providers and Purchasing-Selling Entities involved in the whether or not the has transitioned to a Confirmed. R1.1. For Confirmed, the Authority shall also communicate: R Start and stop times, ramps, and megawatt profile to Balancing Authorities. R Necessary information to NERC-identified reliability analysis services. C. Measures M1. For each, the Authority shall provide evidence that it has distributed the final status and Confirmed information specified in Requirement 1 to all Balancing Authorities, Transmission Service Providers and Purchasing-Selling Entities involved in the within the time period defined in the Timing Table, Column C. If denied, the Authority shall tell all involved parties that approval has been denied. M1.1 For each that includes a direct current tie, the Authority shall provide evidence that it has communicated the final status to the Balancing Authorities on both sides of the direct current tie, even if the Balancing Authorities are neither the Source nor Sink for the. D. Compliance 1. Compliance Monitoring Process 1.1. Compliance Monitoring Responsibility Regional Organization Compliance Monitoring Period and Reset Time Frame The Performance-Reset Period shall be twelve months from the last non-compliance to R Data Retention The Authority shall keep 90 days of historical data. The Compliance Monitor shall keep audit records for a minimum of three calendar years. Draft: February 15, 2007 Page 1 of 4
9 Standard INT Authority Distributes Status 1.4. Additional Compliance Information Each Authority shall demonstrate compliance to the Compliance Monitor within the first year that this standard becomes effective or the first year the entity commences operation by self-certification to the Compliance Monitor. Subsequent to the initial compliance review, compliance will be: Verified by audit at least once every three years Verified by spot checks in years between audits Verified by annual audits of noncompliant Authorities, until compliance is demonstrated Verified at any time as the result of a complaint. Complaints must be lodged within 60 days of the incident. Complaints will be evaluated by the Compliance Monitor. Each Authority shall make the following available for inspection by the Compliance Monitor upon request: For compliance audits and spot checks, relevant data and system log records for the audit period which indicate the Authority s distribution of all final status and Confirmed information to all entities involved in an per R1. The Compliance Monitor may request up to a three-month period of historical data ending with the date the request is received by the Authority For specific complaints, only those data and system log records associated with the specific event contained in the complaint which indicate that the Authority distributed the final status and Confirmed information to all entities involved in that specific. 2. Levels of Non-Compliance 2.1. Level 1: One occurrence 1 of not distributing final status and information as described in R Level 2: Two occurrences 1 of not distributing final status and information as described in R Level 3: Three occurrences 1 of not distributing final status and information as described in R Level 4: Four or more occurrences 1 of not distributing final status and information as described in R1 or no evidence provided. E. Regional Differences None 1 This does not include instances of not distributing information due to extenuating circumstances approved by the Compliance Monitor. Draft: February 15, 2007 Page 2 of 4
10 Standard INT Authority Distributes Status Version History Version Date Action Change Tracking Draft: February 15, 2007 Page 3 of 4
11 Standard INT Authority Distributes Status Timing Table Request for Timeline with Minimum -Related Response Times Ramp Start A B C D If Actual (RFI) is IA Makes Initial Distribution of BA and TSP Conduct IA Verifies Data Complete IA Compiles and Distributes Status BA Prepares Confirmed for Implementation Minimum Total Period (Columns A through D) for all Interconnections except WECC all <20 minutes prior to < 5 minutes from all 10 minutes >20 minutes to all >1 hour to < 4 hours prior to < 20 minutes all > 39 minutes 1 hour plus 1 minute > 4 hours prior to < 2 hours from all > 1 hour 58 minutes prior to 4 hours Draft: February 15, 2007 Page 4 of 4
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 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 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 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 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 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)
WECC Criterion INT-001-WECC-CRT-3
WECC Criterion INT-001-WECC-CRT-3 A. Introduction 1. Title: e-tag Requirements for WECC including Wrongful Denial of Request for Interchange (RFI) 2. Number: INT-001-WECC-CRT-3 3. Purpose: To manage Arranged
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 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)
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
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).
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)
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
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
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 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
Standard 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
A. 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
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
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
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 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
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
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 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
NERC and Regional Coordination Update. Operating Committee Preston Walker January 9, 2018
NERC and Regional Coordination Update Operating Committee Preston Walker January 9, 2018 Standards Project Action End Date Project 2017-07 Standards Alignment with Registration NERC Standards Under Development
WECC Criterion INT-001-WECC-CRT-2.13
WECC Criterion INT-001-WECC-CRT-2.13 A. Introduction 1. Title: e-tag Requirements for WECC including Wrongful Denial and Loss of Communication ProceduresRequest for Interchange (RFI) 2. Number: INT-001-WECC-CRT-2.13
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
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 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
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
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
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:
Alberta Reliability Standards Compliance Monitoring Program. Version 1.1
Version 1.1 Effective: January 14, 2011 Table of Contents 1. Introduction... 1 2. Purpose... 1 3. Applicability... 1 4. Definitions... 1 5. Compliance Monitoring Overview... 2 6. Monitoring Tools... 1
Implementation Plan for Newly Identified Critical Cyber Assets and Newly Registered Entities
Implementation Plan for Newly Identified Critical Cyber Assets and Newly Registered Entities This Implementation Plan applies to Cyber Security Standards CIP-002-2 through CIP-009-2 and CIP-002-3 through
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
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
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
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
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
1. 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
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
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
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
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
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).
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:
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 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
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
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
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
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
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
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
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
Certification Program
Certification Program Ryan Stewart, Manager of Registration, NERC FRCC Reliability Performance Workshop September 20, 2017 Purpose of the Certification Program Rules of Procedure (ROP) Section 500: The
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...
requirements in a NERC or Regional Reliability Standard.
A. Introduction 1. Title: Cyber Security Information Protection 2. Number: CIP 011 1 3. Purpose: To prevent unauthorized access to BES Cyber System Information by specifying information protection requirements
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
A. 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
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
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 Information Protection
A. Introduction 1. Title: Cyber Security Information Protection 2. Number: CIP-011-2 3. Purpose: To prevent unauthorized access to BES Cyber System Information by specifying information protection requirements
Implementation Plan for Newly Identified Critical Cyber Assets and Newly Registered Entities
Implementation Plan for Newly Identified Critical Cyber Assets and Newly Registered Entities This Implementation Plan applies to Cyber Security Standards CIP-002-2 through CIP-009-2 and CIP-002-3 through
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
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 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:
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.
Implementation 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.
ERO Certification and Review Procedure
ERO Certification and Review Procedure Reliability Assurance December 15, 2016 3353 Peachtree Road NE Suite 600, North Tower Atlanta, GA 30326 404-446-2560 www.nerc.com 1 of 16 Table of Contents Table
CIP Cyber Security Configuration Change Management and Vulnerability AssessmentsManagement
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
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
Hetch Hetchy Water and Power of the City and County of San Francisco. Joint Transmission Planning Base Case Preparation Process
California Independent System Operator & Hetch Hetchy Water and Power of the City and County of San Francisco Joint Transmission Planning Base Case Preparation Process This is a living document. Please
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 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
Coordinate Interchange
Coordinate Interchange Purpose: The purpose of this standard is to define procedures for market participants to request the implementation of Interchange Transactions. Applicability: This Standard applies
Coordinate Interchange
Coordinate Interchange Purpose: The purpose of this standard is to define procedures for market participants to request the implementation of Interchange Transactions. Applicability: This Standard applies
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.
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 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
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,
WECC Board of Directors. Approved Regional Criteria
Document name Category Document date July 29, 2010 Adopted/approved by WECC Interchange Authority Backup (WIAB) Regional Criterion ( ) Regional Reliability Standard (X) Regional Criterion ( ) Policy (
Reliability 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:
Inter-Registrar Transfer Policy (IRTP) Audit Report
Inter-Registrar Transfer Policy (IRTP) Audit Report Executive Summary This is a report on an Inter-Registrar Transfer Policy (IRTP) compliance audit that ICANN recently conducted. ICANN s Contractual Compliance
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
Reliability Standard Audit Worksheet 1
Reliability Standard Audit Wksheet 1 CIP-009-6 Cyber Security Security Management Controls This section to be completed by the Compliance Enfcement Authity. Audit ID: Registered Entity: NCR Number: Compliance
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
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
Requirements for Data for Power System Modeling and Analysis (MOD-032-1) Arizona Public Service Company
Requirements for Data for Power System Modeling and Analysis (MOD-032-1) Arizona Public Service Company December 29, 2016 APS Requirements for Data for Power System Modeling and Analysis Table of Contents
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. Standard 1300 Cyber Security
These definitions will be posted and balloted along with the standard, but will not be restated in the standard. Instead, they will be included in a separate glossary of terms relevant to all standards
NERC CIP Information Protection
NERC CIP Information Protection Eric Ruskamp Manager, Regulatory Compliance September 13, 2017 1 Agenda NERC History NERC Compliance Overview of Reliability Standards Compliance with Reliability Standards
CIP Cyber Security Security Management Controls. A. Introduction
CIP-003-7 - Cyber Security Security Management Controls A. Introduction 1. Title: Cyber Security Security Management Controls 2. Number: CIP-003-7 3. Purpose: To specify consistent and sustainable security
Reliability Standard Audit Worksheet 1
Reliability Standard Audit Wksheet 1 CIP-008-5 Cyber Security Incident Repting and Response Planning This section to be completed by the Compliance Enfcement Authity. Audit ID: Registered Entity: NCR Number:
Cyber 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
Bryan Carr PMP, CISA Compliance Auditor Cyber Security. Audit Evidence & Attachment G CIP 101 Salt Lake City, UT September 25, 2013
Bryan Carr PMP, CISA Compliance Auditor Cyber Security Audit Evidence & Attachment G CIP 101 Salt Lake City, UT September 25, 2013 About Me Joined WECC in August 2012 Before WECC CIP Compliance Program
CIP Cyber Security Electronic Security Perimeter(s)
A. Introduction 1. Title: Cyber Security Electronic Security Perimeter(s) 2. Number: CIP-005-5 3. Purpose: To manage electronic access to BES Cyber Systems by specifying a controlled Electronic Security
1.0 TITLE: Auditing Procedure. 2.0 PURPOSE: To provide an outline and instructions on the GMCS auditing process of clients.
Page 1 1.0 TITLE: Auditing Procedure 2.0 PURPOSE: To provide an outline and instructions on the GMCS auditing process of clients. 3.0 RESPONSIBILITY: GMCS auditors and personnel are responsible for following