NERC Project 2007-06 S ystem Protection Coordination - PRC-027​ Presentation to the NSRS Conference Call August 17, 2015 Sam Francis Oncor Electric Delivery.

Slides:



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

Summary of Second Draft of the NERC Standard PRC Disturbance Monitoring and Reporting JSIS Meeting August 10, 2010 Salt Lake City, UT.
NERC Footnote b / 12 – Load Loss
Jerry Rust Chair - Underfrequency Load Shedding Criterion Team
CUG Meeting June 3 – 5 Salt Lake City, UT
NERC Operating Committee Activities Update September 16-17, 2014 Meeting.
Presented to PGDTF February 11, 2015
PER
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.
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
Update in NERC CIP Activities September 4, Update on CIP Update on Revisions to CIP Version 5  -x Posting  v6 Posting Questions Agenda.
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.
Project Cyber Security Order 706 January 10, 2012 Most of the material presented has been compiled from NERC webinars and drafting team meetings.
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
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.
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.
Determine Facility Ratings, SOLs and Transfer Capabilities Paul Johnson Chair of the Determine Facility Ratings Standard Drafting Team An Overview of the.
ERCOT SOL Methodology for the Planning and Operations Horizons Stephen Solis 2014 OTS 1.
Lisa Wood, CISA, CBRM, CBRA Compliance Auditor, Cyber Security
Implementing the New Reliability Standards Status of Draft Cyber Security Standards CIP through CIP Larry Bugh ECAR Standard Drafting Team.
Texas Regional Entity Update Sam Jones Interim CEO and President Board of Directors July 18, 2006.
2015 RTP – Study Scope of Short Circuit Analysis RPG Meeting May 19,
Actions Affecting ERCOT Resulting From The Northeast Blackout ERCOT Board Of Directors Meeting April 20, 2004 Sam Jones, COO.
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.
Critical Infrastructure Protection Update Christine Hasha CIP Compliance Lead Advisor, ERCOT TAC March 27, 2014.
SPS policy – Information Presentation Presentation to ROS June 16, 2004.
Project System Protection Coordination Requirement revisions to PRC (ii) Texas Reliability Entity NERC Standards Reliability Subcommittee.
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.
Problem Areas Updates Penalties FRCC Compliance Workshop September / October
Project Cyber Security Order 706 Version 5 CIP Standards Potential to Adversely Impact ERCOT Black Start Capability.
Business Practices Subcommittee Update Executive Committee Meeting October 20, 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.
NERC Project PRC-005 FERC Order No. 803 Directive ​ Presentation to the NSRS Conference Call August 17, 2015 Sam Francis Oncor Electric Delivery.
NERC Lessons Learned Summary LLs Published in September 2015.
Projects System Protection Coordination Draft 2 of TOP Texas Reliability Entity NERC Standards Reliability Subcommittee November 2, 2015.
WECC-0100 Scope, Content & Status Update Rikin Shah, PAC Orlando Ciniglio, IPC WECC TSS Meeting, Salt Lake City, UT January ,
Business Practices Subcommittee Update Executive Committee Meeting August 18, 2015.
Reliability Standards Development Plan David Taylor Manager Standards Development Standards Committee Meeting June 12-13, 2008.
Dennis Glass Compliance Analyst III January 21, 2016 PRC Protection System, Automatic Reclosing, and Sudden Pressure Relaying Maintenance Talk with.
Transition Plan Network Operations Model Change Requests 5/26/2010.
Communications Operator Training Seminar 2016 Brian Legg & John Jarmon System Operations Training (ERCOT)
Remedial Action Scheme Workshop RAS Workshop May 9, 2016.
Reliability Standard TPL Transmission System Planned Performance for Geomagnetic Disturbance Events September 28, 2016 TPL Standard Status.
NOGRR-169 OWG discussion Bill Blevins June 28, 2017.
COM Operating Personnel Communications Protocols
Planning Geomagnetic Disturbance Task Force (PGDTF) Update to the ROS
WECC Regional Standards Update
Updates to the Path Rating Process for Approval by the PCC
PRC Implementation Plan and Summary of Devices
Merrill Brimhall – Engineer, Staff
Training Appendix for Adult Protective Services and Employment Supports June 2018.
NERC Cyber Security Standards Pre-Ballot Review
Reliability Standards Development Plan
Coordinate Operations Standard
Larry Bugh ECAR Standard Drafting Team Chair June 1, 2005
TRTR Briefing September 2013
Standards Development Process
Presentation transcript:

NERC Project S ystem Protection Coordination - PRC-027​ Presentation to the NSRS Conference Call August 17, 2015 Sam Francis Oncor Electric Delivery

Status of PRC (Draft 6) PRC is posted for comment and additional ballot  July 29 – September 11, 2015  Additional ballot and Non-binding Poll: September 2-11, 2015

Project Key Points PRC Coordination of Protection System Performance During Faults  Addresses planning time horizon Requirements R3 and R4 of PRC-001  Corrects applicable entities to owners – TO, GO, and DP  Addresses the coordination of Protection Systems during Faults  Addresses the coordination (reviewing/updating) of existing Protection Systems that are affected by changes in Fault Current  Addresses the coordination of intra-entity Protection Systems All of PRC-001 will be retired by approval of PRC and TOP (Knowledge of Composite Protection Systems and Remedial Action Schemes and Their Effects )

PRC-027-1, Defined Term New Defined Term Protection System Coordination Study (PSCS) An analysis to determine whether Protection Systems operate in the intended sequence during Faults.

PRC-027-1, Applicability Purpose  To maintain the coordination of Protection Systems installed to detect and isolate Faults on Bulk Electric System (BES) Elements, such that those Protection Systems operate in the intended sequence during Faults Functional Entities  Transmission Owner  Generator Owner  Distribution Provider (that own Protection Systems identified in the Facilities) Facilities  Protection Systems installed to detect and isolate Faults on BES Elements

PRC-027-1, Requirement R1 R1. Each Transmission Owner, Generator Owner, and Distribution Provider shall establish a process for developing new and revised Protection System settings for BES Elements, such that the Protection Systems operate in the intended sequence during Faults. The process shall include:  1.1. A review and update of short-circuit models for the BES Elements under study.  1.2. A review of the developed Protection System settings.  1.3. For Protection System settings applied on BES Elements that electrically join Facilities owned by separate functional entities (Transmission Owners, Generator Owners, and Distribution Providers), provisions to: o Provide the proposed Protection System settings to the owner(s) of the electrically-joined Facilities

PRC-027-1, Requirement R1 o Respond to any owner(s) that provided its proposed Protection System settings pursuant to Requirement R1, Part by identifying any coordination issue(s) or affirming that no coordination issue(s) were identified. o Verify that identified coordination issue(s) associated with the proposed Protection System settings for the associated BES Elements are addressed prior to implementation. o Communicate with the other owner(s) of the electrically-joined Facilities regarding revised Protection System settings resulting from unforeseen circumstances that arise during: – Implementation or commissioning. – Misoperation investigations. – Maintenance activities. – Emergency replacements required as a result of Protection System component failure.

Measure M1 M1.Acceptable evidence may include, but is not limited to, dated electronic or hard copy documentation to demonstrate that the responsible entity established a process to develop settings for its Protection Systems, in accordance with Requirement R1.

Requirement R2 R2. Each Transmission Owner, Generator Owner, and Distribution Provider shall, for each BES Element with Protection System functions identified in Attachment A:  Option 1: Perform a Protection System Coordination Study in a time interval not to exceed six calendar years; or  Option 2: Compare present Fault current values to an established Fault current baseline and perform a Protection System Coordination Study when the comparison identifies a 15 percent or greater deviation in Fault current values (either three phase or phase to ground) at a bus to which the Element is connected, all in a time interval not to exceed six calendar years; 1 or,  Option 3: A combination of the above. 1 See next slide

Footnote 1 The initial Fault current baseline(s) shall be established by the effective date of this Reliability Standard and updated each time a Protection System Coordination Study is performed (PSCS). If an initial baseline was not established by the effective date of this Reliability Standard because of the previous use of an alternate option or the installation of a new Element, the entity may establish the baseline by performing a PSCS. Key point  If Option 2 is initially used, the Fault current baseline must be established prior to the Effective Date (12 months after regulatory approval)  Once a PSCS is performed, the entity may reset or establish a Fault current baseline

Measure M2 M2.Acceptable evidence may include, but is not limited to, dated electronic or hard copy documentation to demonstrate that the responsible entity performed Protection System Coordination Study(ies) and/or Fault current comparisons in accordance with Requirement R2.

Attachment A The following Protection System functions are applicable to Requirement R2 if available Fault current levels are used to develop the settings for those Protection System functions: 21 – Distance if:  infeed is used in determining reach (phase and ground distance), or  zero-sequence mutual coupling is used in determining reach (ground distance). 50 – Instantaneous overcurrent 51 – AC inverse time overcurrent 67 – AC directional overcurrent if used in a non- communication-aided protection scheme

Requirement R3 R3. Each Transmission Owner, Generator Owner, and Distribution Provider shall utilize its process established in Requirement R1 to develop new and revised Protection System settings for BES Elements.

Measure M3 M3. Acceptable evidence may include, but is not limited to, dated electronic or hard copy documentation to demonstrate that the responsible entity utilized its settings development process established in Requirement R1, as specified in Requirement R3.

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 2 (TOP-009-1) implementation Required on effective date:  R1 – documented process  R2 – a Fault current baseline (if using Option 2)  R3 – utilize the process

Key Take-Aways The purpose of PRC is to maintain the coordination of Protection Systems installed to detect and isolate Faults on BES Elements, such that those Protection Systems operate in the intended sequence during Faults. Requirement R1 mandates that an entity establish a process to develop settings for its BES Protection Systems to operate in the intended sequence during Faults; and stipulates certain attributes that must be included in the process. Utilizing the process (Requirement R3) will promote consistency in developing Protection System settings and will minimize the introduction of errors.

Key Take-Aways Requiring entities to periodically assess (Requirement R2) the state of their BES Protection Systems that are affected by changes in Fault current minimizes the risk that incremental changes in Fault current have accumulated enough to impact coordination. Requirement R2 requires a PSCS to be performed if:  (1) Entity desires a time-based approach (every 6 years), or  (2) Fault current comparisons (present-day to baseline) identify a deviation of 15 percent or more Baselines  If Option 2 is initially used, the Fault current baseline must be established prior to the Effective Date (12 months).  A baseline may be established anytime a PSCS is performed.

Key Take-Aways Attachment A lists the Protection System functions (21, 50, 51, and 67) that are applicable to Requirement R2 if available Fault current levels are used to develop the settings for those Protection System functions. The above Protection System functions are susceptible to changes in the magnitude of available short-circuit Fault current. These functions utilize current in their measurement to initiate tripping of circuit breakers. The functions listed above are included in a Protection System Coordination Study (PSCS) because they require coordination with other Protection Systems.

Key Take-Aways Retirement of PRC (ii).  The complete retirement of PRC (ii) is contingent upon the approval of both proposed Reliability Standards PRC and TOP NERC is proposing the complete retirement of PRC (ii) in the implementation plans associated with both PRC and TOP The Project System Protection Coordination Mapping Document shows how PRC addresses requirements R3 and R4 of PRC (ii). The remaining requirements of PRC (ii) – Requirements R1, R2, R5, and R6 are proposed for retirement in Project Phase 2 of System Protection Coordination (see the Mapping Document for Project Phase 2 of System Protection Coordination).

Going Forward PRC is posted for formal comment and ballot  Comment period: July 29-September 11, 2015  Additional ballot: September 2-11, 2015 Draft RSAW to be posted for feedback  August 12-September 11, 2015 Standard Drafting Team in-person meeting to respond to comments  Week of September 21, 2015 Anticipated final ballot  October 2015 Anticipated NERC Board of Trustees adoption  November 2015

Questions?