PRC-012-2 - NERC

5 downloads 179 Views 409KB Size Report
Dec 19, 2017 - PRC-013 Remedial Action Scheme Database. ▫ PRC-014 Remedial Action Scheme Assessment. ▫ PRC-015 Remed
PRC-012-2 Remedial Action Schemes Al McMeekin, Senior Standards Developer Compliance Training December 19, 2017

Project 2010-05.3 Objectives • Project 2010-05.3 Phase 3 of Protection Systems: Remedial Action Schemes (RAS) • Consolidate the reliability objectives of the existing RAS-related standards into one standard – PRC-012-2.      

PRC-012 Remedial Action Scheme Review Procedure PRC-013 Remedial Action Scheme Database PRC-014 Remedial Action Scheme Assessment PRC-015 Remedial Action Scheme Data and Documentation PRC-016 Remedial Action Scheme Misoperations PRC-017 Remedial Action Scheme Maintenance and Testing

• Correct the applicability

2

RELIABILITY | ACCOUNTABILITY

PRC-012-2 Overview • Purpose: To ensure that Remedial Action Schemes (RAS) do not introduce unintentional or unacceptable reliability risks to the Bulk Electric System (BES). • Applicability:  Functional Entities: o Reliability Coordinator o Planning Coordinator o RAS-entity – the Transmission Owner, Generator Owner, or Distribution Provider that owns all or part of a RAS

 Facilities: o Remedial Action Schemes

3

RELIABILITY | ACCOUNTABILITY

PRC-012-2 Overview • PRC-012-2 contains nine (9) requirements.  R1: RAS-entity submits Attachment 1 data (for each RAS) to RC for review  R2: RC reviews each RAS using Attachment 2 (as a guide)  R3: RAS-entity resolves each identified reliability issue and obtain RC approval prior to putting RAS in service  R4: PC performs a technical evaluation (planning analyses) of each RAS at least once every five full calendar years  R5: RAS-entity analyzes all correct and incorrect operations of a RAS  R6: RAS-entity develops Corrective Action Plan (CAP) when necessary  R7: RAS-entity implement CAP and make notifications  R8: RAS-entity performs a functional test of each RAS  R9: RC maintains a RAS database

4

RELIABILITY | ACCOUNTABILITY

PRC-012-2 “functionally modified” RAS • Any modification to a RAS consisting of any of the following:  Changes to System conditions or contingencies monitored by the RAS  Changes to the actions the RAS is designed to initiate  Changes to RAS hardware beyond in-kind replacement; i.e., match the original functionality of existing components  Changes to RAS logic beyond correcting existing errors  Changes to redundancy levels; i.e., addition or removal

5

RELIABILITY | ACCOUNTABILITY

PRC-012-2 “limited impact” RAS • A “limited impact” RAS is recognized as one for which it is not possible by inadvertent operation or failure to operate, to cause or contribute to BES Cascading, uncontrolled separation, angular instability, voltage instability, voltage collapse, or unacceptably damped oscillations.  For new or functionally modified RAS reviewed by the RCs under PRC-0122, the reviewing RC will make the final determination as to whether a RAS is “limited impact.”  RAS implemented prior to the effective date of PRC-012-2 that have been through the regional review process and designated as a Type 3 in NPCC or a LAPS in WECC will be recognized as limited impact for the purposes of Requirement 4, Parts 4.1.3 and 4.1.4.

6

RELIABILITY | ACCOUNTABILITY

PRC-012-2 Implementation • Effective Date: Thirty-six (36) months after the effective date of the applicable governmental authority’s order approving the standard. 01/01/2021

 Requirement R4: For existing RAS, initial performance of obligations under Requirement R4 must be completed within sixty (60) full calendar months of the effective date of PRC‐012‐2. (01/01/2026) For new or functionally modified RAS, the initial performance of Requirement R4 must be completed within sixty (60) full calendar months of the date that the RAS is approved by the reviewing RC(s) under Requirement R3.  Requirement R8: For each RAS not designated as limited impact, initial performance of obligations under Requirement R8 must be completed at least once within six (6) full calendar years of the effective date for PRC-012-2. (01/01/2027) For each RAS designated as limited impact, initial performance of obligations under Requirement R8 must be completed at least once within twelve (12) full calendar years of the effective date for PRC-012-2. (01/01/2033)  Requirement R9: For each Reliability Coordinator that does not have a RAS database, the initial obligation under Requirement R9 is to establish a database by the effective date of PRC012-2. (01/01/2021) Each Reliability Coordinator will perform the obligation of Requirement R9 within twelve full calendar months after the effective date of PRC-012-2. (01/01/2022)

7

RELIABILITY | ACCOUNTABILITY

8

RELIABILITY | ACCOUNTABILITY