PRC and EOP Effective 10/1/13

Transcription

1 PRC and EOP Effective 10/1/13 Thomas Teafatiller, Senior Compliance Engineer (RE) Jason Speer, Senior Engineer (RTO) Greg Sorenson, Senior Compliance Engineer (RE)

2 Overview of PRC Automatic Underfrequency Load Shedding Purpose: To establish design and documentation requirements for automatic underfrequency load shedding (UFLS) programs to arrest declining frequency, assist recovery of frequency following underfrequency events and provide last resort system preservation measures. SPP Planning Coordinator (PC) required to develop a UFLS program PC s program and studies are done on behalf of Registered Entities System Protection and Control Working Group (SPCWG) developed a UFLS program/plan for SPP that improves on current UFLS plan in SPP Criteria 2

3 Regional UFLS Standard PRC-006-SPP-01 Regional standard PRC-006-SPP-01 was approved by SPP RE and NERC Trustees in 2012 Provides last resort for Bulk Electric System preservation Regional standard includes Generator Owner participation Continent-wide PRC does not include Generator Owner participation Regional UFLS standard serves as basis for SPP PC s UFLS Plan However, PRC-006-SPP-01 has yet to be approved by FERC and will not be monitored by SPP RE until it is effective 3

4 SPP RE Responsibilities/PC Responsibilities SPP RE will consider if Registered Entity s underfrequency relay settings conforms to PC s design SPP RE will not conduct technical review of PC s design SERC, not SPP RE, audits SPP RTO SPP RTO/PC is responsible for technical review and adequacy of SPP UFLS Plan SPP RTO/PC is responsible for technical review and adequacy of changes in SPP UFLS Plan SPP RTO/PC is responsible for event assessment 4

5 Overview of PRC-006 PC Requirements UFLS entities shall mean all entities responsible for ownership, operation, or control of UFLS equipment May include Transmission Owners and Distribution Providers R1: Develop/document criteria for island selection R2: Identify islands to serve as basis for UFLS program R3: Develop UFLS program (plan), including notification/schedule for implementation by UFLS entities within its area R4: Conduct/document UFLS design assessment at least once every five years to determine if UFLS program design meets performance characteristics in R3 for each island identified in R2 5

6 R4: Five-Year Study 2010 Evaluation and Assessment of SPP UFLS Scheme by Powertech Labs Inc. for SPP 2015 UFLS Plan Study due by December 31, 2015 Data submittal due 3Q 2014 SPCWG study review 1Q 2015 SPP UFLS Plan study approved by MOPC 3Q

7 Overview of PC Requirements R5: Coordinate with other PCs, if planning areas overlap R6: Maintain UFLS database to model its UFLS program annually R7: Provide UFLS database to other PCs within 30 days of request R11: Within one year of event, conduct/document assessment of BES islanding events R12: Within two years of event, conduct/document UFLS design assessment to consider identified deficiencies R13: Coordinate event assessment with other PCs included in event 7

8 Overview of PC Requirements R14: Respond to written comments from UFLS entities and TOs within its PC area following a comment period and before finalizing its UFLS program Regional UFLS Standard was developed through SPCWG with stakeholder input SPCWG developed UFLS Plan based on regional standard UFLS Plan presented to MOPC April 2013* MOPC directed Regional Compliance Working Group to review plan at June 2013 conference call SPCWG will recommend that MOPC approve updated UFLS Plan at July 2013 meeting * See MOPC April 16-17, 2013 Materials, SPCWG folder for initial draft 8

9 R8: UFLS Entity Requirements R8: Each UFLS entity shall provide data to its PCs according to the format and schedule specified by the PCs to support maintenance of each PC s UFLS database SPP RE will look for evidence such as: Data submittal to SPP SPP meeting documentation 9

10 R8: UFLS Data Inventory RTO will send spreadsheet to UFLS entities Primary Compliance Contact for completion 3Q or 4Q 2013 Entity Name- Balancing Area # Relay Location, Setpoint,Time Feeder or Islanding Scheme Tie Line Information (58.5 Hz or below) Entity Name- Balancing Area # Substation Name SPP Bus No. or Breaker # or circuit name if bus number not known Relay Freq. Setpoint Total Relay Clearing Time (sec) From SPP Bus No. To SPP Bus No. Circuit ID per SPP Load Flow Location & Amount Load to be shed Generation UFLS Breaker Total Clearing Time (distribution, transmission or generator) Total Forecasted Peak Load per SPP Model (Enter Value Below) MW SPP Bus No. or Breaker # MW Shed Percent of total peak system load shed per SPP model (Do not enter data here,formula column) SPP Bus No. and Id Generation MW Shed Time/Speed (sec) Peak Demand (MW) Comments 10

11 R8: RTO Internal Data Submittal Log Entity Function Status of data submittal Attestation completed? Entity Comment Reviewed By Own UFLS Own UVLS Submitted data spreadsheet? Comments Action Plan 11

12 R9: UFLS Entity Requirements R9: Each UFLS entity shall provide automatic tripping of Load in accordance with the UFLS program design and schedule for application determined by its PCs in each PC area in which it owns assets. SPP RE will look for: Show the appropriate portion of the PC s plan Demonstrate relays are set to proper trip points (such as a print-out of relay tests or relay settings) Circuit loading to show appropriate underfrequency load shed steps in accordance with program design 12

13 R10: Transmission Owner (TO) Requirements R10. Each TO shall provide automatic switching of its existing capacitor banks, Transmission Lines, and reactors to control overvoltage as a result of underfrequency load shedding if required by the UFLS program and schedule for application determined by the PCs in each PC area in which the TO owns transmission. SPP UFLS program does not currently require any automatic switching of capacitor banks, transmission lines, and reactors 13

14 PRC Reliability Standard Audit Worksheet (RSAW) RSAW should be posted in early July: Standard-Audit-Worksheets-(RSAWs).aspx 14

15 SPP Criteria 7.3 Criteria 7.3 is current UFLS Plan Criteria 7.3 will need to be assessed SPP RE does not audit on SPP Criteria 15

16 If PRC-006-SPP-01 (regional UFLS standard) is approved UFLS entities must be compliant with the following regional requirements one year after FERC approval: - R4: Post-Event Technical assessment - R5: UFLS Entity Data submittal - R6: Generator Owner Data submittal Three years after FERC approval, must be compliant with remaining regional requirements SPP will provide further outreach on regional UFLS standard if it is approved 16

17 Elements of a Control Activity What Develop brief, concise description of what is done Who Use titles not names And designee Frequency For each operating day, for each week, etc. Documentation/Evidence What is it, where is it, who gets it, how is it accessed, how is it backed up 17

18 Example PRC-006 Internal Control (Best Practice) Objective UFLS plan will arrest frequency decline in an emergency Control Type - Preventive and Detective Sample Control Activity Risk Reviewing SPP plan prior to approval - Blackout/cascading UFLS event Risk Measurement Likelihood of plan failure Risk Response Mitigating risk of blackout/ cascading UFLS event Who Use titles not names List responsibilities of titles Evidence See previous slides Frequency Varies 18

19 EOP-003-2: LOAD SHEDDING PLANS 19

20 EOP R1 R1. After taking all other remedial steps, a TOP or BA operating with insufficient generation or transmission capacity shall shed customer load rather than risk an uncontrolled failure of components or cascading outages of the Interconnection. No changes Compliance monitoring is event-driven Evidence: a) Taking all other steps in capacity emergency plan or transmission emergency plans (such as logs, phone conversations, checklists), and b) Load shedding (such as EOP-004 report) 20

21 EOP R2 R2. Each Transmission Operator shall establish plans for automatic load shedding for under-voltage conditions if the Transmission Operator or its associated Transmission Planner(s) or Planning Coordinator(s) determine that an under-voltage load shedding scheme is required. REQUIREMENT MOVED: Underfrequency load shed plan now covered by PRC R3 Evidence: UVLS plan that meets the needs of the TOP/TP or PC Plan should identify the specific buses to trip and voltage levels at which they should trip 21

22 EOP R3 R3. Each Transmission Operator and Balancing Authority shall coordinate load shedding plans, excluding automatic underfrequency load shedding plans, among other interconnected Transmission Operators and Balancing Authorities. Interconnected TOPs and BAs must be aware of load shedding plans (manual and undervoltage) Evidence such as: Public posting SPP meeting documentation, load shed plan meets SPP Criteria 7 22

23 EOP R4 R4. A Transmission Operator shall consider one or more of these factors in designing an automatic under voltage load shedding scheme: voltage level, rate of voltage decay, or power flow levels. REQUIREMENT MOVED: Underfrequency design considerations addressed by PRC R2 and R3 Evidence: UVLS scheme should identify design factors 23

24 EOP R5 R5. A Transmission Operator or Balancing Authority shall implement load shedding, excluding automatic under-frequency load shedding, in steps established to minimize the risk of further uncontrolled separation, loss of generation, or system shutdown. REQUIREMENT MOVED: PRC R9 covers UFLS implementation (TOs, DPs) Evidence could include: Identifying trip points and time delays Evidence in relay test results that installed settings match plan SCADA/EMS grouping of systems Load plan should have more than one step which may be condition-based or geographic in nature 24

25 EOP R6 R6. After a Transmission Operator or Balancing Authority Area separates from the Interconnection, if there is insufficient generating capacity to restore system frequency following automatic underfrequency load shedding, the Transmission Operator or Balancing Authority shall shed additional load. No change Compliance monitoring is event-driven Best practice (not required) is to conduct training or a simulation, particularly if multiple personnel involved 25

26 EOP R7 R7. The Transmission Operator shall coordinate automatic undervoltage load shedding throughout their areas with tripping of shunt capacitors, and other automatic actions that will occur under abnormal voltage, or power flow conditions. REQUIREMENT MOVED: Underfrequency coordination of generation now covered by PRC-006 R4, along with overfrequency and automatic Load restoration for frequency recovery Evidence: UVLS plan should consider what else on the system changes as a result of voltages changing 26

27 EOP R8 R8. Each Transmission Operator or Balancing Authority shall have plans for operator controlled manual load shedding to respond to real-time emergencies. The Transmission Operator or Balancing Authority shall be capable of implementing the load shedding in a timeframe adequate for responding to the emergency. No change Evidence: Manual load shed plan considers SCADA control options or travel time to substation 27

28 Example EOP R8 Internal Control Objective Validate operator familiarity with and feasibility of load shedding plan Control Type - Detective and Corrective Sample Control Activities Training on load shed plan, scenario walkthrough, review manual load shed with line personnel, practice truck dispatch Risk - Confusion over implementation Risk Response Reduction of uncertainty Who System Operator East District Line Foreman Evidence See previous slides Frequency Annually per operator 28

29 EOP RSAW Standard-Audit-Worksheets-(RSAWs).aspx RSAW includes FERC commentary which provides additional insight 29

30 Questions or Comments SPP PC Plan: Harvey Scribner, Monitoring/Compliance with PRC-006-1: Thomas Teafatiller, Monitoring/Compliance with EOP-003-2: Greg Sorenson,

31 Summary PRC Requirements for PC PRC Requirements for UFLS Entity SPP RTO Process for UFLS Data Collection EOP Requirements RSAWs and Internal Controls 31