Project 2007-06.2 System Protection Coordination Requirement revisions to PRC-001-1.1(ii) Texas Reliability Entity NERC Standards Reliability Subcommittee.

Slides:



Advertisements
Similar presentations
2004 NERC, NPCC & New England Compliance Programs John Norden Manager, Operations Training, Documentation & Compliance August 31, 2003 RC Meeting.
Advertisements

Business Practices Subcommittee Update August 17, 2010.
NERC TPL Standard Issues TSS Meeting #146 Seattle, WA August 15-17, 2007 Chifong Thomas.
1 MSRATF Update to TSS (Modeling SPS and RAS Ad Hoc Task Force) Scope of Work Approval January 25, 2013 Joe Seabrook Puget Sound Energy.
Western Electricity Coordinating Council Status of NERC Standards Activity WECC PCC Meeting March 6-7, 2008.
Update on NERC Project Assess Transmission Future Needs – TPL-002, footnote b Chifong Thomas July 17-18, 2012.
Jerry Rust Chair - Underfrequency Load Shedding Criterion Team
North American Electric Reliability Council 1 Coordinate Operations Standard Jason Shaver Standard Drafting Team Chair September 29, 2005.
PER
PER Update & Compliance Lessons Learned
FRCC Fall Compliance Workshop October , 2013
1 PER-005 Update Impact on Operators System Operator Conference April and May 1-3, 2012 Columbia, SC Margaret Stambach Manager, Training Services.
Project Disturbance and Sabotage Reporting (Event Reporting) Project Webinar July 30, 2012.
Key Reliability Standard Spot Check Frank Vick Compliance Team Lead.
Allan Wick, CFE, CPP, PSP, PCI, CBCP Chief Security Officer WECC Joint Meeting October 8, 2014.
COM Operating Personnel Communications Protocols
Recent NERC Standards Activities RSC – Jan. 5, 2011 NSRS Update Date Meeting Title (optional)
2014 System Operator Conference 1 Protection System Misoperations: Why Should a System Operator Give a Hoot? April 17 & May 1, 2014 – Charlotte, NC September.
State of Standards and Standards in Development Sean Cavote, Manager of Standards Development WECC Operating Committee Meeting March 26, 2015.
1. 11/26/2012: NERC Board of Trustees adopted CIP v5 CIP thru CIP CIP and CIP Version 5 Filing FERC requested filing by 3/31/2013.
System Operator Conference NERC Standards Review for: Simulator Drill Orientation 2014 System Operator Conferences Charlotte NC & Franklin TN SERC/SOS.
WECC and NERC Protection Criteria and Standards
Reliability Standards Update
WECC Standards Update Steve Rueckert – Director of Standards W ESTERN E LECTRICITY C OORDINATING C OUNCIL.
Critical Infrastructure Protection Update Christine Hasha CIP Compliance Lead Advisor, ERCOT TAC March 27, 2014.
Update in NERC CIP Activities June 5, Update on CIP Update on Revisions to CIP Version 5 –BES Cyber Asset Survey –Implementation Plan Questions.
GOP and QSE Relationship Jeff Whitmer Manager, Compliance Assessments Talk with Texas RE June 25, 2012.
B O N N E V I L L E P O W E R A D M I N I S T R A T I O N 1 Network Operating Committee (NOC) June 12 th, 2014.
ERCOT SOL Methodology for the Planning and Operations Horizons Stephen Solis 2014 OTS 1.
Lisa Wood, CISA, CBRM, CBRA Compliance Auditor, Cyber Security
Evolving NERC Standards Processes and Practices Paradigm Shift.
Implementing the New Reliability Standards Status of Draft Cyber Security Standards CIP through CIP Larry Bugh ECAR Standard Drafting Team.
SPP.org 1. EMS Users Group – CIP Standards The Compliance Audits Are Coming… Are You Ready?
Assessing Compliance. 2 NERC Compliance Workshop 11/02/07 Documentation of Compliance with NERC Reliability Standards Jeff Whitmer.
Standards Subject to Enforcement Currently Or Standards Subject to Future Enforcement TSS Meeting #169 May 6-8, 2015 By: Lesley Kayser-Sprouse.
1. 2 NERC Bulk Electric System (BES) Definition (NERC Glossary of Terms Used in Reliability Standards) FERC Order 693 FRCC Handbook Review Task Force.
Status Report for Critical Infrastructure Protection Advisory Group
July 2008 CPS2 Waiver SDT Technical Workshop for Draft BAL-001-TRE-01 Judith A. James Reliability Standards Manager TRE.
SPS policy – Information Presentation Presentation to ROS June 16, 2004.
Board of Directors Meeting February 26, 2013 Standards, Registration and Certification Report.
Project (COM-001-3) Interpersonal Communications Capabilities Michael Cruz-Montes, CenterPoint Energy Senior Consultant, Policy & Compliance, SDT.
Project Real-time Monitoring and Analysis Capabilities Mark Olson, Senior Standards Developer Texas RE NSRS October 5, 2015.
Bill Lewis, Compliance Team Lead NERC Reliability Working Group May 16, 2013 Texas RE Update Talk with Texas RE April 25, 2013.
NERC Project S ystem Protection Coordination - PRC-027​ Presentation to the NSRS Conference Call August 17, 2015 Sam Francis Oncor Electric Delivery.
Project – Alignment of Terms WECC Joint Meeting July 15, 2015.
Standards Review Subcommittee Update August 17, 2010.
NERC Project S ystem Protection Coordination - PRC-027​ Presentation to the NSRS Conference Call April 20, 2015 Sam Francis Oncor Electric Delivery.
Texas Regional Entity Report Mark Henry June 6, 2008.
Project Update TOP/IRO Reliability Standards NERC ORS May 6, 2014.
NERC Project PRC-005 FERC Order No. 803 Directive ​ Presentation to the NSRS Conference Call August 17, 2015 Sam Francis Oncor Electric Delivery.
NERC Standards Update Colleen Frosch ROS Meeting January 7, 2016.
Projects System Protection Coordination Draft 2 of TOP Texas Reliability Entity NERC Standards Reliability Subcommittee November 2, 2015.
Communications Operator Training Seminar 2016 Brian Legg & John Jarmon System Operations Training (ERCOT)
NERC BAL-005, BAL-006, FAC-001 Gary Nolan WECC ISAS April 20, 2016.
Remedial Action Scheme Workshop RAS Workshop May 9, 2016.
System Restoration & Blackstart Standards Drafting Team Presentation to Texas RE Reliability Standards Committee March 4, 2009 Rick Terrill Confidential.
Project Standard Drafting Team (IRO SDT) Stephen Solis, IRO-SDT NSRS Meeting June 1, 2015.
WECC – NERC Standards Update
NOGRR-169 OWG discussion Bill Blevins June 28, 2017.
Phase Angle Limitations
Rachel Coyne Manager, Reliability Standards Program
COM Operating Personnel Communications Protocols
Path Operator Implementation Task Force
ERCOT Technical Advisory Committee June 2, 2005
NERC Cyber Security Standards Pre-Ballot Review
Reliability Standards Development Plan
Coordinate Operations Standard
Larry Bugh ECAR Standard Drafting Team Chair June 1, 2005
WECC – NERC Standards Update
Standards Development Process
Presentation transcript:

Project System Protection Coordination Requirement revisions to PRC (ii) Texas Reliability Entity NERC Standards Reliability Subcommittee August 17, 2015 Michael Cruz-Montes CenterPoint Energy, SDT Vice-Chair

RELIABILITY | ACCOUNTABILITY2 There are six PRC-001 Requirements  Requirements R3 and R4 (Phase 1 – PRC-027-1)  Requirements R1, R2, R5, and R6 (Phase 2) PRC-001 presentation will be by requirement  R6 – monitoring and notification of SPS (expected to become RAS)  R5 – notification of system changes “in advance” that impact protection  R4 – being addressed by Phase 1 (i.e., proposed PRC-027-1)  R3 – being addressed by Phase 1 (i.e., proposed PRC-027-1)  R2 – notification of relay and equipment failures and corrective actions as soon as possible  R1 – knowledge of Protection Systems PRC-001 Requirements

RELIABILITY | ACCOUNTABILITY3 Proposed for retirement  BA and TOP is required to monitor the status of each SPS (being replaced by RAS) and notify affected entities of each change in status SDT explains the reliability objective addressed by:  Addressed by TOP-001-3, R10 (Monitoring – TOP)  Addressed by TOP-001-3, R11 (Monitoring – BA)  Addressed by IRO-008-2, R4 (Monitoring – RC) o Real-time Assessment is done once every 30 minutes o Implied RC must be notified of RAS status to be able to perform RTA  Addressed by IRO-010-2, R1 (Notification – RC)  Addressed by TOP-003-3, R1 and R2 (Notification – BA & TOP) PRC-001, Requirement R6

RELIABILITY | ACCOUNTABILITY4 Proposed for retirement  GOP and TOP are required to notify neighboring entities “in advance” of changes in generation, transmission, load, or operating conditions that could require changes in Protection Systems SDT explains the reliability objective addressed by:  TOP-002-4, R1 and R2 (in advance – BA and TOP)  IRO-005-4, R1 (RC communication to BA and TOP)  IRO-008-2, R1 and R2 (in advance – RC)  IRO-017-1, R1, R2, R3, and R4 (in advance – RC)  TPL-001-4, R4 (in advance – PC and TP) PRC-001, Requirement R5

RELIABILITY | ACCOUNTABILITY5 Being addressed by Project (i.e., Phase 1) Proposed PRC  Addresses R3 and R4 - coordination of Protection Systems during Faults  Will allow R3 and R4 to be retired from PRC-001 PRC and TOP must be approved to ensure complete retirement of PRC (ii) PRC-001, Requirements R3 and R4

RELIABILITY | ACCOUNTABILITY6 Proposed for retirement  GOP and TOP are required to notify entities of relay/equipment failures and take corrective action as soon as possible SDT explains the reliability objective is addressed by:  TOP-003-3, R1 and R2 (Notification – BA and TOP)  TOP-001-3, R1, R2, R13, and R14 (Corrective Action via Operating Instructions, i.e., as soon as possible – BA & TOP)  IRO-001-4, R1 (Corrective Action via Operating Instructions, i.e., as soon as possible – RC)  IRO-008-2, R4 (As soon as possible – RC)  IRO-010-2, R1 (Notification – RC) Achieves directive from Order No. 693, paragraph 1449 (#3) PRC-001, Requirement R2

RELIABILITY | ACCOUNTABILITY7 Proposed to be incorporated into new TOP  Entities must be familiar with the purpose and limitations of Protection System schemes applied in its area SDT held three webinars to obtain feedback  Should PRC-001, Requirement R1 go in a PER, PRC, or a TOP standard NERC staff and the SDT met with FERC OER staff on June 16, 2015 to discuss the development of the standard  SDT discussions with FERC OER staff communicated the reliability objective of R1 is intended to ensure operating entities know how Composite Protection Systems will respond to BES conditions and their effects on the operation of the BES SDT considered FERC OER staff and industry feedback and determined R1 is best suited for a new “TOP” Reliability Standard PRC-001, Requirement R1

RELIABILITY | ACCOUNTABILITY8 TOP (Knowledge of Composite Protection Systems and Remedial Action Schemes and Their Effects) Purpose  To ensure operating entities have the requisite knowledge of Composite Protection Systems and Remedial Action Schemes (RAS), and their effects, in order to operate and maintain the reliability of the Bulk Electric System (BES) Applicability  Transmission Operator  Balancing Authority  Generator Operator Clarifies which Composite Protection Systems are important Addresses the operational functionality and effects Proposing TOP-009-1

RELIABILITY | ACCOUNTABILITY9 Knowledge of Composite Protection System  May be demonstrated through training (including the effects on the BES), operating guides, manuals, procedures, output of operational tools (e.g., databases or analysis programs), or outcomes of analyses, monitoring, and assessments that identify the impacts on the BES NERC Glossary term “Composite Protection System”  “The total complement of Protection System(s) that function collectively to protect an Element. Backup protection provided by a different Element’s Protection System(s) is excluded.”  Individual Protection System functionality is not intended in TOP SDT determined that knowledge should also extend to “Remedial Action Scheme” (RAS)  Ensures full coverage Knowledge

RELIABILITY | ACCOUNTABILITY10 Each TOP shall ensure its personnel responsible for Reliable Operation of its TOP Area have knowledge of operational functionality and effects of Composite Protection Systems and RAS that are necessary to perform its Operational Planning Analysis, Real‐time monitoring, and Real-time assessments Personnel must have knowledge of those protective systems that are used as inputs to its OPA, RTM, and RTA. For example:  Systems defined by TOP-003, R1 (i.e., operational data)  Systems logged into operational tools or using other methods  Systems that are in an abnormal or temporary state due to some issue TOP-009-1, R1

RELIABILITY | ACCOUNTABILITY11 Each Transmission Operator shall have evidence that demonstrates the knowledge according to Requirement R1. Evidence may include, but is not limited to, the following: training (including the effects on the BES), operating guides, manuals, procedures, output of operational tools (e.g., databases or analysis programs), or outcomes of analyses, monitoring, and assessments that identify the impacts on the BES. Measure M1

RELIABILITY | ACCOUNTABILITY12 Each BA shall ensure its personnel responsible for Reliable Operation of its BA Area have knowledge of operational functionality and effects of Composite Protection Systems and RAS that are necessary to perform its Real‐time monitoring (RTM) in order to maintain generation-Load-Interchange balance Personnel must have knowledge of those protective systems that are used as inputs to its RTM. For example:  Systems defined by TOP-003, R2 (i.e., operational data)  Systems logged into operational tools or using other methods  Systems that are in an abnormal or temporary state due to some issue TOP-009-1, R2

RELIABILITY | ACCOUNTABILITY13 Each Balancing Authority shall have evidence that demonstrates the knowledge according to Requirement R2. Evidence may include, but is not limited to, the following: training (including the effects on the BES), operating guides, manuals, procedures, output of operational tools (e.g., databases or analysis programs), or outcomes of Real-time monitoring that identify the impacts on the BES. Measure M2

RELIABILITY | ACCOUNTABILITY14 Each GOP shall ensure its personnel responsible for Reliable Operation of its generating Facilities have knowledge of operational functionality and effects of Composite Protection Systems and Remedial Action Schemes (RAS) that impact its generating Facilities. Personnel must have knowledge of those protective systems that impact its generating Facilities. For example:  RAS operation resulting in a generating unit trip or runback that effects the BES TOP-009-1, R3

RELIABILITY | ACCOUNTABILITY15 Each Generator Operator shall have evidence that demonstrates the knowledge according to Requirement R3. Evidence may include, but is not limited to, the following: training (including the effects on the generating Facilities), operating guides, manuals, procedures, interconnection agreements or studies, or access to third-party documentation. Measure M3

RELIABILITY | ACCOUNTABILITY16 Implementation Plan  Effective date is the first day of the first calendar quarter that is twelve (12) months after the date that the standard is approved by an applicable governmental authority…  Commensurate with Phase 1 (PRC-027-1) implementation  Required for complete retirement of PRC (ii) Required on effective date:  To have knowledge of operational functionality and effects of Protection Systems and RAS: o R1 – TOP used as inputs into its OPA, RTM, and RTA to maintain reliability of the BES o R2 – BA used as inputs into its RTM to maintain generation-Load-Interchange balance o R3 – GOP necessary to operate its generating Facilities in order to maintain BES reliability Implementation Plan

RELIABILITY | ACCOUNTABILITY17 Aligns the reliability activity in the proper family of Reliability Standards Meets the reliability objectives of PRC (ii), R1 Eliminates duplicity (R2, R5, and R6) by retiring the Requirements Eliminates ambiguous phrases  As soon as possible  Reduces system reliability  Operating conditions that could require changes in others Protection Systems Improves measurability  Functionality and effects  Which Protection Systems and RAS TOP-009-1, Key Take-Aways

RELIABILITY | ACCOUNTABILITY18 The complete retirement of PRC (ii) is contingent upon the approval of both proposed Reliability Standards PRC and TOP Project Mapping Documents  Project shows how proposed PRC addresses Requirements R3 and R4 of PRC (ii)  Project shows: o How Requirement R1 is incorporated into a new proposed TOP o How the reliability objective of Requirements R2, R5, and R6 of PRC (ii) are addressed by yet to be approved TOP/IRO standards Collective Key Take-Aways

RELIABILITY | ACCOUNTABILITY19 TOP is posted for formal comment and ballot  Comment period: July 29 – September 11, 2015  Initial ballot: September 2-11, 2015 Draft RSAW currently posted  August 12 – September 11, 2015 SDT in-person meeting to respond to comments  Week of September 21, 2015 in Ft Worth Additional or final ballot  October 2015 Anticipated NERC Board of Trustees adoption  November 2015 Project Going Forward

RELIABILITY | ACCOUNTABILITY20 Questions? Project