Remedial Action Scheme Workshop RAS Workshop May 9, 2016.

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.
Presented to PGDTF February 11, 2015
PER
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.
2014 System Operator Conference 1 Protection System Misoperations: Why Should a System Operator Give a Hoot? April 17 & May 1, 2014 – Charlotte, NC September.
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.
1 New Resource Qualification Testing Sandip Sharma Supervisor, Operations Analysis New Generation Information Forum ERCOT Public November 4, 2014.
WECC and NERC Protection Criteria and Standards
Reliability Standards Update
OH&S Management System
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.
1 Nodal Stabilization Market Call December 28, 2010.
Project WECC-0100 Update Reliability Subcommittee February 2014.
Steve Rueckert Director of Standards TPL Discussion – PCC Steering Committee March 25, 2014.
1 Renewable Technology Working Group (RTWG) July 14, 2009 Henry Durrwachter.
April 23 rd OWG UFLS Survey & Power Factor Review.
Lead from the front Texas Nodal 1 Resource Entity Owned Transmission Asset Data Collection Feb 27, 2009 Kick Off Meeting.
Actions Affecting ERCOT Resulting From The Northeast Blackout ERCOT Board Of Directors Meeting April 20, 2004 Sam Jones, COO.
September 25, 2012 Planning Working Group - PLWG Sub-Synchronous Resonance Protection & Mitigation John Adams Principal Engineer.
Lead from the front Texas Nodal 1 Registration Market Call Apr 10, 2009.
Lead from the front Texas Nodal 1 EDS 3 Release 5 Monday / Friday Market Updates November 30, 2007.
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.
Lead from the front Texas Nodal 1 Registration Market Call Mar 13, 2009.
NPRR 219 & Outage Scheduler Enhancement Workshop April 28, 2014.
© Property of ERCOT /06/20041 Overview of SPS in ERCOT February 5, 2004.
ERCOT PUBLIC 4/21/ RTP: Cascade Analysis April 21, 2015.
Problem Areas Updates Penalties FRCC Compliance Workshop September / October
1 Cutover Market Call December 01, :30 AM.
NERC Project S ystem Protection Coordination - PRC-027​ Presentation to the NSRS Conference Call August 17, 2015 Sam Francis Oncor Electric Delivery.
Transmission Outage Process April Purpose In compliance with the Protocols and the Electric Reliability Council of Texas (ERCOT) Operating Guides,
1 Market Trials Outage Scheduling Weekly Update July 02, 2010.
Overview Art Deller, P.E. Supervisor, Model Administration New Resource Workshop May 28, 2014.
NERC Project S ystem Protection Coordination - PRC-027​ Presentation to the NSRS Conference Call April 20, 2015 Sam Francis Oncor Electric Delivery.
Lead from the front Texas Nodal 1 Registration Market Call Mar 27, 2009.
MISUG Meeting Materials Jackie Ashbaugh/Jamie Lavas ERCOT 2/22/2011.
RMS/COPS Workshop VI 1 October 06, Antitrust Admonition ERCOT strictly prohibits Market Participants and their employees who are participating in.
NERC Standards Update Colleen Frosch ROS Meeting January 7, 2016.
MISUG Meeting Materials Jackie Ashbaugh/Jamie Lavas ERCOT 1/13/2011.
1 Nodal Credit Update at WMS June 16, 2010.
Projects System Protection Coordination Draft 2 of TOP Texas Reliability Entity NERC Standards Reliability Subcommittee November 2, 2015.
14 Minute Ramp Period Testing Workshop June 30, 2009.
1 Nodal Stabilization Market Call December 03, :30 PM.
1 Market Trials Outage Scheduling Weekly Update August 13, 2010.
1 Cutover Market Call November 27, 2010.
1 Nodal Stabilization Market Call December 27, 2010.
Lead from the front Texas Nodal 1 Registration Market Call June Data Collection Window June 05, 2009.
1 Nodal Stabilization Market Call December 16, 2010.
Lead from the front Texas Nodal 1 Registration Market Call Nov 14, 2008.
Voltage Control Brad Calhoun Consultant, Sr. Trainer Spring 2016.
1 Cutover Market Call November 28, 2010.
NERC BAL-005, BAL-006, FAC-001 Gary Nolan WECC ISAS April 20, 2016.
Lead from the front Texas Nodal 1 Registration Market Call Nov 21, 2008.
1 Market Trials Outage Scheduling Qualifications Weekly Update March 26, 2010.
Lead from the front Texas Nodal 1 EDS 3 Release 5 and 6 Friday Market Updates June 06, 2008.
RASRS Report to Operating Committee March 22, 2015 Gene Henneberg, Chair Remedial Action Scheme Reliability Subcommittee W ESTERN E LECTRICITY C OORDINATING.
PRC and SPSs in ERCOT RAS Workshop May 9, 2016.
Reliability Must Run Workshop RMR Study Process May 24, 2016.
RASRS Report to Operating Committee March 21, 2017
Transposition of European Network Codes
NOGRR-169 OWG discussion Bill Blevins June 28, 2017.
Planning Geomagnetic Disturbance Task Force (PGDTF) Update to the ROS
WECC Regional Standards Update
PRC Implementation Plan and Summary of Devices
Project WECC-0100 Update Reliability Subcommittee
Presentation transcript:

Remedial Action Scheme Workshop RAS Workshop May 9, 2016

2 Antitrust Admonition ERCOT strictly prohibits Market Participants and their employees who are participating in ERCOT activities from using their participation in ERCOT activities as a forum for engaging in practices or communications that violate the antitrust laws. The ERCOT Board has approved guidelines for members of ERCOT Committees, Subcommittees and Working Groups to be reviewed and followed by each Market Participant attending ERCOT meetings. If you have not received a copy of these Guidelines, copies are available at the Client Relations desk. Please remember your ongoing obligation to comply with all applicable laws, including the antitrust laws. RAS Workshop May 9, 2016

3 Safety RAS Workshop May 9, 2016

4 Agenda RAS Workshop May 9, New RAS Definition 2.Review of Standards PRC through PRC Upcoming Standards PRC Existing SPSs and new classification 5.Review draft NPRR 6.Review draft NOGRR 7.Review draft PGRR 8.Adjourn

5 U.S. Regulatory Status Remedial Action Scheme Standards ●PRC Remedial Action Scheme Review Procedure ●PRC Remedial Action Database ●PRC Remedial Action Scheme Assessment ●PRC Remedial Action Scheme Data and Documentation ●PRC Remedial Action Scheme Misoperations ●PRC Remedial Action Scheme Maintenance and Testing ●Approved by FERC on November 19, 2015 (Order No. 818)  RAS definition effective 4/1/2017  PRC-015-1, PRC and PRC enforcement date is 4/1/2017  PRC-012-1, PRC-013-1, and PRC will not be enforceable RAS Workshop May 9, 2016

6 Remedial Action Scheme Definition RAS Workshop May 9, 2016 Old Definition An automatic protection system designed to detect abnormal or predetermined system conditions, and take corrective actions other than and/or in addition to the isolation of faulted components to maintain system reliability. Such action may include changes in demand, generation (MW and Mvar), or system configuration to maintain system stability, acceptable voltage, or power flows. An SPS does not include (a) underfrequency or undervoltage load shedding or (b) fault conditions that must be isolated or (c) out-of-step relaying (not designed as an integral part of an SPS). Also called Remedial Action Scheme. New Definition A scheme designed to detect predetermined System conditions and automatically take corrective actions that may include, but are not limited to, adjusting or tripping generation (MW and Mvar), tripping load, or reconfiguring a System(s). RAS accomplish objectives such as: Meet requirements identified in the NERC Reliability Standards; Maintain Bulk Electric System (BES) stability; Maintain acceptable BES voltages; Maintain acceptable BES power flows; Limit the impact of Cascading or extreme events.

7 Remedial Action Scheme Definition New Definition The following do not individually constitute a RAS: Protection Systems installed for the purpose of detecting Faults on BES Elements and isolating the faulted Elements Schemes for automatic underfrequency load shedding (UFLS) and automatic undervoltage load shedding (UVLS) comprised of only distributed relays Out-of-step tripping and power swing blocking Automatic reclosing schemes Schemes applied on an Element for non-Fault conditions, such as, but not limited to, generator loss-of-field, transformer top-oil temperature, overvoltage, or overload to protect the Element against damage by removing it from service RAS Workshop May 9, 2016

8 Remedial Action Scheme Definition New Definition The following do not individually constitute a RAS: Controllers that switch or regulate one or more of the following: series or shunt reactive devices, flexible alternating current transmission system (FACTS) devices, phase-shifting transformers, variable-frequency transformers, or tap- changing transformers; and, that are located at and monitor quantities solely at the same station as the Element being switched or regulated FACTS controllers that remotely switch static shunt reactive devices located at other stations to regulate the output of a single FACTS device Schemes or controllers that remotely switch shunt reactors and shunt capacitors for voltage regulation that would otherwise be manually switched Schemes that automatically de-energize a line for a non-Fault operation when one end of the line is open RAS Workshop May 9, 2016

9 Remedial Action Scheme Definition New Definition The following do not individually constitute a RAS: Schemes that provide anti-islanding protection (e.g., protect load from effects of being isolated with generation that may not be capable of maintaining acceptable frequency and voltage) Automatic sequences that proceed when manually initiated solely by a System Operator Modulation of HVdc or FACTS via supplementary controls, such as angle damping or frequency damping applied to damp local or inter-area oscillations Sub-synchronous resonance (SSR) protection schemes that directly detect sub- synchronous quantities (e.g., currents or torsional oscillations) Generator controls such as, but not limited to, automatic generation control (AGC), generation excitation [e.g., automatic voltage regulation (AVR) and power system stabilizers (PSS)], fast valving, and speed governing RAS Workshop May 9, 2016

10 PRC-012-1, Remedial Action Scheme Review ●Requirement 1:  Each Regional Reliability Organization with a Transmission Owner, Generator Owner, or Distribution Providers that uses or is planning to use a RAS shall have a documented Regional Reliability Organization RAS review procedure to ensure that RAS comply with Regional criteria and NERC Reliability Standards.  For the purposes of this requirement, ERCOT is responsible for the RAS review procedure.  RAS definition, data, documentation, testing, and maintenance requirements will be outlined in the Nodal Operating Guides.  R1.3 and R1.4 refer to TPL-001-0, TPL and TPL which are retired. For the purposes of this requirement, TPL will be used as the basis for planning performance. RAS Workshop May 9, 2016

11 PRC-013-1, Remedial Action Scheme Database ●Requirement 1:  The Regional Reliability Organization that has a Transmission Owner, Generator Owner, or Distribution Provider with a RAS installed shall maintain a RAS database.  For the purposes of this requirement, ERCOT will maintain the RAS database on the MIS. RAS Workshop May 9, 2016

12 PRC-014-1, Remedial Action Scheme Assessment ●Requirement 1:  The Regional Reliability Organization shall assess the operation, coordination, and effectiveness of all RAS installed in its Region at least once every five years for compliance with NERC Reliability Standards and Regional criteria.  For the purposes of this requirement, ERCOT will conduct the five year RAS assessment. RAS Workshop May 9, 2016

13 PRC-015-1, Remedial Action Scheme Data ●Requirement 1:  The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall maintain a list of and provide data for existing and proposed RAS as specified in Reliability Standard PRC R1. ●Requirement 2:  The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall have evidence it reviewed new or functionally modified RAS in accordance with the Regional Reliability Organization’s procedures as defined in Reliability Standard PRC-012-1_R1 prior to being placed in service.  For the purposes of these requirements, RAS data and documentation requirements will be outlined in the Nodal Operating Guides. RAS Workshop May 9, 2016

14 PRC-016-1, Remedial Action Scheme Misoperations ●Requirement 1:  The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall analyze its RAS operations and maintain a record of all misoperations in accordance with the Regional RAS review procedure specified in Reliability Standard PRC-012-1_R1. ●Requirement 2:  The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall take corrective actions to avoid future misoperations.  For the purposes of these requirements, RAS misoperation definitions, analysis of misoperations, and misoperation reporting requirements will be outlined in the Nodal Operating Guides. RAS Workshop May 9, 2016

15 PRC-017-1, Remedial Action Scheme Testing ●Requirement 1:  The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall have a system maintenance and testing program(s) in place.  Testing and maintenance of RAS components that meet the definition of a Protection System component are now covered under PRC  Requirements for functional testing of a RAS will be outlined in the Nodal Operating Guides. RAS Workshop May 9, 2016

16 In Development ●PRC  Removal of “fill-in-the-blank” requirements  Final Ballot on April 29, Received 80.4% approval  PRC replaces/retires six legacy standards (upon full implementation)  Introduces concept of “limited impact” RAS, defined as “A RAS designated as limited impact cannot, by inadvertent operation or failure to operate, cause or contribute to BES Cascading, uncontrolled separation, angular instability, voltage instability, voltage collapse, or unacceptably damped oscillations.”  Introduces “RAS-Entity,” defined as the Transmission Owner, Generator Owner, or Distribution Provider that owns all or part of a RAS RAS Workshop May 9, 2016

17 PRC Comparison to PRC OLD REQUIREMENT PRC R1: Each Regional Reliability Organization with a Transmission Owner, Generator Owner, or Distribution Providers that uses or is planning to use a RAS shall have a documented Regional Reliability Organization RAS review procedure to ensure that RAS comply with Regional criteria and NERC Reliability Standards. NEW REQUIREMENT PRC R2: Each Reliability Coordinator that receives Attachment 1 information pursuant to Requirement R1 shall, within four full calendar months of receipt or on a mutually agreed upon schedule, perform a review of the RAS in accordance with Attachment 2, and provide written feedback to each RAS ‐ entity. R3: Prior to placing a new or functionally modified RAS in ‐ service or retiring an existing RAS, each RAS ‐ entity that receives feedback from the reviewing Reliability Coordinator(s) identifying reliability issue(s) shall resolve each issue to obtain approval of the RAS from each reviewing Reliability Coordinator. RAS Workshop May 9, 2016

18 PRC Comparison to PRC OLD REQUIREMENT PRC R1: The Regional Reliability Organization that has a Transmission Owner, Generator Owner, or Distribution Provider with a RAS installed shall maintain a RAS database. NEW REQUIREMENT PRC R9: Each Reliability Coordinator shall update a RAS database containing, at a minimum, the information in Attachment 3 at least once every twelve full calendar months. RAS Workshop May 9, 2016

19 PRC Comparison to PRC OLD REQUIREMENT PRC R1: The Regional Reliability Organization shall assess the operation, coordination, and effectiveness of all RAS installed in its Region at least once every five years for compliance with NERC Reliability Standards and Regional criteria. NEW REQUIREMENT PRC R4: Each Planning Coordinator, at least once every five full calendar years, shall: Perform an evaluation of each RAS within its planning area to determine whether: The RAS mitigates the System condition(s) or Contingency(ies) for which it was designed. The RAS avoids adverse interactions with other RAS, and protection and control systems. The inadvertent operation of the RAS or the failure of the RAS to operate does not cause or contribute to BES Cascading, uncontrolled separation, angular instability, voltage instability, voltage collapse, or unacceptably damped oscillations. RAS Workshop May 9, 2016

20 PRC Comparison to PRC OLD REQUIREMENT PRC R1: The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall maintain a list of and provide data for existing and proposed RAS as specified in Reliability Standard PRC R1. NEW REQUIREMENT PRC R1: Prior to placing a new or functionally modified RAS in ‐ service or retiring an existing RAS, each RAS ‐ entity shall provide the information identified in Attachment 1 for review to the Reliability Coordinator(s) where the RAS is located. RAS Workshop May 9, 2016

21 PRC Comparison to PRC OLD REQUIREMENT PRC R1: The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall analyze its RAS operations and maintain a record of all misoperations in accordance with the Regional RAS review procedure specified in Reliability Standard PRC R1. NEW REQUIREMENT PRC R5: Each RAS ‐ entity, within 120 full calendar days of a RAS operation or a failure of its RAS to operate when expected, or on a mutually agreed upon schedule with its reviewing Reliability Coordinator(s), shall: Participate in analyzing the RAS operational performance; and Provide the results of RAS operational performance analysis that identified any deficiencies to its reviewing Reliability Coordinator(s). RAS Workshop May 9, 2016

22 PRC Comparison to PRC OLD REQUIREMENT PRC R2: The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall take corrective actions to avoid future misoperations. NEW REQUIREMENT PRC R6: Each RAS ‐ entity shall participate in developing a Corrective Action Plan (CAP) and submit the CAP to its reviewing Reliability Coordinator(s) within six full calendar Months. R7: Each RAS ‐ entity shall, for each of its CAPs developed pursuant to Requirement R6: Implement the CAP. Update the CAP if actions or timetables change. Notify each reviewing Reliability Coordinator if CAP actions or timetables change and when the CAP is completed. RAS Workshop May 9, 2016

23 PRC Comparison to PRC OLD REQUIREMENT PRC R1: The Transmission Owner, Generator Owner, and Distribution Provider that owns a RAS shall have a system maintenance and testing program(s) in place. NEW REQUIREMENT PRC R8: Each RAS ‐ entity shall participate in performing a functional test of each of its RAS to verify the overall RAS performance and the proper operation of non ‐ Protection System components RAS Workshop May 9, 2016

24 Questions? RAS Workshop May 9, 2016