Background Information TPL Transmission System Planning Performance Requirements
|
|
|
- Alicia Perry
- 5 years ago
- Views:
Transcription
1 Comment Form for 6 th Draft of Standard TPL Please DO NOT use this form to submit comments on the 6 th draft of the TPL standard for. This comment form must be completed by May 31, If you have questions please contact Ed Dobrowolski at ed.dobrowolski@nerc.net or by telephone at Background Information TPL Transmission System Planning Performance Requirements Comments on the 5 th draft of the TPL Transmission System Planning Performance Requirements standard were received from the industry through September 2, The Drafting Team received feedback on a number of issues, and the SDT appreciates the tremendous industry participation in the process. Below is a brief overview of the 6 th draft of the standard highlighting areas where the SDT made changes based on stakeholder feedback as well as the Standards Quality Review Team. The team s objectives remain unchanged - to create a single Transmission planning standard: 1) with clear, concise requirements set at an appropriate level to ensure reliability, and 2) that fully addresses all issues raised by FERC Orders 693 and 890, and industry inputs, including the SAR scope document. 6 th Draft Overview: The following changes were made due to industry comments: 1. The definitions of Near-Term Transmission Planning Horizon and Year One have been deleted as the same definition has already been filed by another project. 2. The following requirements were changed: a. Several grammatical changes for clarity. b. R1 Establish P0 as the normal system condition. c. R2 The VRF has been changed to High to reflect the importance of the Planning Assessment and to meet the latest guidelines. d. R2, part Change from performance to System response.. e. R2, part 2.1.4, bullet #7 Change planned to known. f. R2, part Added documentation of technical rationale. g. R2, part Added of identified System Facilities and Operating Procedures. h. R4, part Provided timing criteria and added that it is only applicable when high speed reclosing is utilized. i. R8 Changed VRF from Low to Medium to meet latest guidelines. 3. Header note changes: a. Deleted including Load as a redundant phrase. 4. Performance table changes: a. Changed Column 2 heading to Initial Condition Village Boulevard, Princeton, New Jersey Phone: Fax:
2 b. Deleted superscript for footnote 9 in P0, column 6 c. Added Breaker to P2 Event column, parts 3 & 4 and P4 Event for clarity. d. Added non-redundant to P5 Event for clarity. e. Spelled out adjustments to P6 Initial Condition for clarity. 5. Extreme event Stability 2 Changed Protection System to relay for clarity and added footnote 13 reference. 6. Footnote changes: a. #9 Added resolutions from footnote b clarification (Project ). b. #12 Added resolutions from footnote b clarification (Project ). 7. Measurement changes: a. Updated to reflect changes in requirements. 8. Data Retention grammatical changes for clarity. The following changes were made due to the Quality Review: 1. Added Category to Requirement R1 for clarity. 2. Made grammatical changes to requirement R2 for clarity. 3. Added For the Planning Assessment and made grammatical changes to Requirement R2 for clarity. 4. Added For the Planning Assessment to Requirement R2, parts 2.2, 2.4, and 2.5 for clarity. 5. Added timing elements to Requirement R8 and adjusted Measure M8 and the VSL accordingly. 6. Added dated to Measures M2, M3, M4, M5, and M6 to conform to the latest guidelines. 7. Added in-force to Data retention for Requirement R1 and Measure M1 to conform to the latest guidelines. 8. Moved one item from Moderate to Severe in the VSL for Requirements R1, R2, and R4 to conform to the latest guidelines. Page 2 of 5
3 You do not have to answer all questions. Enter All Comments in Simple Text Format. Insert a check mark in the appropriate boxes by double-clicking the gray areas. 1. The SDT has made revisions to the requirements language of TPL based on industry comments and the Quality Review. Do you agree with these changes? If you do not support these changes or you agree in general but feel that alternative language would be more appropriate, please provide specific suggestions in your comments with clear indications as to which requirement you are commenting on. Yes: No: X Comments: The wording of Part 1.1.2, known outages...with a duration of at least 6 months should be revised to at least 1 year. Also for consideration is that known outages...with a duration of at least 6 months are dealt with in operational studies rather than planning studies. Any adverse impacts that these outages might have are mitigated by operational decisions rather than planning decisions within a 6 month horizon. Moving this requirement out of the TPL Standard to an operational standard should be considered. Make the wording consistent between 2.1 and 2.2 as it relates to qualified past studies. Specifically: Parts 2.1.2, 2.1.4, The language of requirements and allowing the performance of one or more sensitivities appears to be inconsistent with language in requires multiple sensitivities to determine if actions to resolve performance deficiencies are necessary. Will varying only one measurable quantity several times in multiple simulations satisfy multiple sensitivity studies or just one sensitivity study? The numbers and types of required sensitivity studies is unclear, and subject to interpretation by PCs and TPs. The current wording in Part 2.1.5, spare strategy, appears to be open-ended regarding the number of permutations to be analyzed. It should be restricted to assessing only one piece of equipment being unavailable or outaged at a time should be consistent with R2 and 2.1 regarding the use of the terms assessment and studies. As with the preceding comment regarding Part 1.1.2, moving this requirement out of the TPL Standard and to an operational standard should be considered. It is unclear if the last sentence of R2.1.5 allows for the curtailment of firm transmission service before the application of category P0, P1 and P2 events. This last sentence states: with the conditions that the System is expected to experience during the possible unavailability of the long lead time equipment. Page 3 of 5
4 The wording in Part 2.2 be supported by the following annual current study, supplemented with qualified past studies should be replaced with the similar statement in Part 2.1: be supported by current annual studies or qualified past studies. Part lists potential system actions to address System deficiencies. It is suggested that this list be moved to a guideline or white paper. The wording in Part 8.1 needs to be amended to restrict comments to the most recent assessment only. Contingencies on back to back HVDC installations are not mentioned in the standard. The treatment of combined cycle facilities (all units in outage?) needs to be clarified, as well as Footnote 7 of Table 1 requiring clarification. In Table 1, Event 1 of Category P2 and related Footnote 7 are not clear because of the use of the word possibly. If the intension is to simulate the line end opening condition of tapped lines, this should be clearly stated in the table (without reference to Opening of a line section and use of different language in the footnote). From Table 1b: Consequential Load Loss as well as generation loss is acceptable as a consequence of any event excluding P0. Firm Transmission Services Loss is also acceptable and should be added (particularly in P1 loss of a single pole of a DC line for which the transfer is reduced accordingly to the remaining pole capability). 2. The SDT has made revisions to the VRF and VSL of TPL which will be part of a non-binding poll with this posting based on industry comments and the Quality Review. Do you agree with these changes? If you do not support these changes or you agree in general but feel that alternative language would be more appropriate, please provide specific suggestions in your comments. Yes: No: Comments: 3. If you have any other comments on this Standard that you have not already provided in response to the prior questions, please provide them here. Comments: Page 4 of 5
5 Page 5 of 5
Project Protection System Misoperations
Protection System Misoperations Please DO NOT use this form. Please use the electronic comment form at the link below to submit comments on the second draft of the PRC-004-3 standard for Protection System
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
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
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
NB Appendix CIP NB-0 - Cyber Security Recovery Plans for BES Cyber Systems
This appendix establishes modifications to the FERC approved NERC standard CIP-009-6 for its specific application in New Brunswick. This appendix must be read with CIP-009-6 to determine a full understanding
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.
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
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
Unofficial Comment Form Project Real-time Monitoring and Analysis Capabilities IRO and TOP-010-1
Project 2009-02 Real-time Monitoring and Analysis Capabilities IRO-018-1 and TOP-010-1 DO NOT use this form for submitting comments. Use the electronic form to submit comments on IRO- 018-1 Reliability
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
Industry Webinar. Project Single Points of Failure. August 23, 2018
Industry Webinar Project 2015-10 Single Points of Failure August 23, 2018 Agenda Presenters Standard Drafting Team o Chair, Jonathan Hayes, SPP o Vice Chair, Delyn Kilpack, LGE-KU NERC Staff o Latrice
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 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
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
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
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
Summary of FERC Order No. 791
Summary of FERC Order No. 791 On November 22, 2013, the Federal Energy Regulatory Commission ( FERC or Commission ) issued Order No. 791 adopting a rule that approved Version 5 of the Critical Infrastructure
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 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 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
Consideration of Issues and Directives Federal Energy Regulatory Commission Order No. 791 January 23, 2015
Federal Energy Regulatory Commission Order No. 791 January 23, 2015 67 and 76 67. For the reasons discussed below, the Commission concludes that the identify, assess, and correct language, as currently
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).
Unofficial Comment Form Project Protection System Maintenance and Testing Phase 3 (Sudden Pressure Relays)
Project 2007-17.3 Protection System Maintenance and Testing Phase 3 (Sudden Pressure Relays) Please DO NOT use this form for submitting comments. Please use the electronic form to submit comments on the
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
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:
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
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 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 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
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 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
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 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
NB Appendix CIP NB-0 - Cyber Security Personnel & Training
This appendix establishes modifications to the FERC approved NERC standard CIP-004-5.1 for its specific application in New Brunswick. This appendix must be read with CIP-004-5.1 to determine a full understanding
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 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
Critical Infrastructure Protection (CIP) Version 5 Revisions. Standard Drafting Team Update Industry Webinar September 19, 2014
Critical Infrastructure Protection (CIP) Version 5 Revisions Standard Drafting Team Update Industry Webinar September 19, 2014 Administrative Items NERC Antitrust Guidelines It is NERC s policy and practice
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
Project Modifications to CIP Standards. Technical Conference April 19, 2016 Atlanta, GA
Project 2016-02 Modifications to CIP Standards Technical Conference April 19, 2016 Atlanta, GA Agenda Welcome Steven Noess NERC Antitrust Compliance Guidelines and Public Announcement* - Al McMeekin Logistics
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).
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
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
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
Project Retirement of Reliability Standard Requirements
Project 2013-02 Retirement of Reliability Standard Requirements Unofficial Comment Form for Paragraph 81 (P81) Project Retirement of Reliability Standard Requirements This form is provided in a Word format
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 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
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
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
Please contact the undersigned if you have any questions concerning this filing.
!! November 29, 2016 VIA ELECTRONIC FILING Veronique Dubois Régie de l'énergie Tour de la Bourse 800, Place Victoria Bureau 255 Montréal, Québec H4Z 1A2 Re: North American Electric Reliability Corporation
Unofficial Comment Form Project Modifications to CIP Standards Requirements for Transient Cyber Assets CIP-003-7(i)
Unofficial Comment Form Project 2016-02 Modifications to CIP Standards Requirements for Transient Cyber Assets CIP-003-7(i) Do not use this form for submitting comments. Use the electronic form to submit
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:
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:
Memorandum. This memorandum requires Board action. EXECUTIVE SUMMARY
California Independent System Operator Corporation Memorandum To: ISO Board of Governors From: Keith Casey, Vice President, Market & Infrastructure Development Date: May 21, 2014 Re: Decision on interconnection
Response to Stakeholder Comments on Draft and Revised Draft Tariff Language CCE3 and RSI Clarifications
Response to Stakeholder Comments on Draft and Revised Draft Tariff Language CCE3 and RSI Clarifications 30.4.1.1.6.1 Six Cities Placement of the phrase on an annual basis creates ambiguity. The Six Cities
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
Project Modifications to CIP Standards. Consideration of Comments Initial Comment Period
Project 2016-02 Modifications to CIP Standards Consideration of Comments Initial Comment Period October 21, 2016 Consideration of Comments Introduction The following are the ballots associated with this
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
Reliability Coordinator Procedure PURPOSE... 1
No. RC0550 Restriction: Table of Contents PURPOSE... 1 1. RESPONSIBILITIES... 2 1.1.1. CAISO RC... 2 1.1.2. RC Working Groups... 2 1.1.3. Operationally Affected Parties... 2 1.1.4. RC Oversight Committee...
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
Unofficial Comment Form Project Disturbance Monitoring
Unofficial Comment Form Project 2007-11 Disturbance Monitoring Please DO NOT use this form for submitting comments. Please use the electronic form to submit comments on the Standard Authorization Request
Lesson Learned CIP Version 5 Transition Program CIP : Communications and Networking Cyber Assets Draft Version: August 18, 2015
Lesson Learned CIP Version 5 Transition Program CIP-002-5.1: Communications and Networking Cyber Assets Draft Version: August 18, 2015 This document is designed to convey lessons learned from NERC s various
Additional 45-Day Comment Period September Final Ballot is Conducted October/November Board of Trustees (Board) Adoption November 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
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,
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.
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 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
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
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
Order No Assessment of Protection System Single Points of Failure Based on the Section 1600 Data Request. September, 2015
Order No. 754 Assessment of Protection System Single Points of Failure Based on the Section 1600 Data Request System Protection and Control Subcommittee (SPCS) and System Modeling and Analysis Subcommittee
Lesson Learned CIP Version 5 Transition Program
Lesson Learned CIP Version 5 Transition Program CIP-002-5: BES Cyber Assets Version: December 7, 2015 This document is designed to convey lessons learned from NERC s various CIP version 5 transition activities.
Lesson Learned CIP Version 5 Transition Program
Lesson Learned CIP Version 5 Transition Program CIP-002-5: BES Cyber Assets Version: September 9, 2015 This document is designed to convey lessons learned from NERC s various CIP version 5 transition activities.
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
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
CIP V5 Updates Midwest Energy Association Electrical Operations Conference
CIP V5 Updates Midwest Energy Association Electrical Operations Conference May 2015 Bob Yates, CISSP, MBA Principal Technical Auditor ReliabilityFirst Corporation Agenda Cyber Security Standards Version
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.
Standard Development Timeline
CIP 003 7 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
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
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
Standards Development Update
Standards Development Update Steven Noess, Director of Standards Development FRCC Reliability Performance Industry Outreach Workshop September 20, 2017 Supply Chain Risk Management 1 Cyber Security Supply
Consideration of Issues and Directives Project Modeling Data (MOD B) October 7, 2013
Project 2010-03 Modeling Data (MOD B) October 7, 2013 Para 290. Project 2010-03 - Modeling Data The Commission directs public utilities, working through NERC, to modify the reliability standards MOD- 010
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,
REVISIONS TO TOP/IRO RELIABILITY STANDARDS
REVISIONS TO TOP/IRO RELIABILITY STANDARDS Meeting Notes 1. Introduction The Chair called the meeting to order at 8:00 a.m. on Tuesday, April 8, 2014 at the NERC offices in Atlanta, GA. Meeting participants
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
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)
Consideration of Comments on FRCC Standard for Regional Generator Performance During Frequency and Voltage Excursions (FRCC-S-PRC-024) Version 2
1. In response to comments received, the Drafting Team has modified the Applicability section and now includes applicability of the standard to sites > 75 MVA (gross aggregate nameplate). Do you agree
136 FERC 61,187 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION. 18 CFR Parts and 40. [Docket No. RM ]
![136 FERC 61,187 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION. 18 CFR Parts and 40. [Docket No. RM ]](/thumbs/92/108623992.jpg "136 FERC 61,187 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION. 18 CFR Parts and 40. [Docket No. RM ]")
136 FERC 61,187 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION 18 CFR Parts 39.10 and 40 [Docket No. RM11-16-000] Transmission Relay Loadability Reliability Standard (September 15, 2011)
Cyber Security Incident Report
Cyber Security Incident Report Technical Rationale and Justification for Reliability Standard CIP-008-6 January 2019 NERC Report Title Report Date I Table of Contents Preface... iii Introduction... 1 New
Mn/DOT Market Research Reporting General Guidelines for Qualitative and Quantitative Market Research Reports Revised: August 2, 2011
Mn/DOT Market Research Reporting General Guidelines for Qualitative and Quantitative Market Research Reports Revised: August 2, 2011 The following guidelines have been developed to help our vendors understand
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
SUBMISSION OF COMMENTS ON
04 Sep 2009 SUBMISSION OF COMMENTS ON Detailed guidance for the request for authorisation of a clinical trial on a medicinal product for human use to the competent authorities, notification of substantial
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
Mega International Commercial bank (Canada)
Mega International Commercial bank (Canada) Policy and Procedures for Clear Language and Presentation Est. Sep. 12, 2013 I. Purposes: The Mega ICB (C) distributes a limited range of retail banking services,
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,
Project Cyber Security - Order No. 791 Identify, Assess, and Correct; Low Impact; Transient Devices; and Communication Networks Directives
Project 2014-02 - Cyber Security - Order No. 791 Identify, Assess, and Correct; Low Impact; Transient Devices; and Communication Networks Directives Violation Risk Factor and Justifications The tables
CIP Cyber Security Physical Security of 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 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
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
151 FERC 61,066 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION ORDER DENYING REHEARING. (Issued April 23, 2015)
151 FERC 61,066 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION Before Commissioners: Norman C. Bay, Chairman; Philip D. Moeller, Cheryl A. LaFleur, Tony Clark, and Colette D. Honorable.
TickITplus Implementation Note
Title Changes to the Core Scheme Requirements V1.1.2 Date January 2014 Reference TIN010-1401 Originator Dave Wynn Version v1r0 Key Terms Core Scheme Requirements The CSR has been updated to version V1.1.2
FRCC Disturbance Reporting Processes and Procedures
Page 1 of 13 FRCC Disturbance Reporting Processes and FRCC RE OP 001-3.2 Effective Date: September 29, 2016 Version: 3.2 3000 Bayport Drive, Suite 600 Tampa, Florida 33607-8410 (813) 289-5644 - Phone (813)