Reliability Coordinator Participation Brief Reliability Subcommittee... · 2015-06-09 · • Data...

GridEx IIIReliability Coordinator

Participation Brief

Operating Reliability Subcommittee meeting

May 5-6, 2015

Presentation 1

RELIABILITY | ACCOUNTABILITY2

Agenda

• Objectives

• Timeline and status of GridEx III planning

• Active and Observing organizations

• GridEx III expected participation growth

• RC involvement in planning and playing

• Inject development process

• Inject delivery

• RC conference calls

• Mid-Term Planning Conference


GridEx III Objectives

Improve communication

Identify lessons learned

Exercise crisis response and recovery

1

2

3

Engage senior leadership

4


Timeline

RCs identify Active Organizations in their control area

RCs establish and participate in RC-to-RC and RC-to-Entity coordination calls

RCs and entities understand and develop customized injects

Reliability Coordinator Planning Activities

GridEx Working

Group

Initial Planning

Phase

Mid-term Planning

Phase

Final Planning

Phase

GridEx III

After Action

Confirm exercise infrastructure

Finalize attack vectors and impacts

Work on scenario narrative

Finalize baseline MSEL

Develop Controller and Player materials

Draft After Action Survey

Send injects and oversee player actions

Capture player actions and findings

Facilitate Executive Tabletop

Distribute survey

Analyze findings and lessons learned

Draft Final Report

Finalize custom injects with RCs

Distribute materials

Conduct training

Set up venue and logistics

December 10 2014 March 11-12 June 10-11 Sept 3 Nov 18-19 Q1 2016January 23

Establish Working Group Members

Establish Mail list

GridEx Awareness

Confirm objectives

Establish boundaries

Confirm tools

2015 Conference Dates

GEWGReform

Jax Atlanta DC


Organizations and Participants

Designation Expectations Return on Investment

Your Organization

Active Organization

• Participate in NERC planning conferences and training sessions

• Engage in dynamic internal exercise play and external information sharing and coordination

• Tailor/adapt scenario to suit organization objectives and play

• Communicate externally to other exercise participants

• Close interaction with other BPS entities and relevant law enforcement and government agencies

• Incident response training opportunity

• Provide input to develop scenario and identify after action findings

• Use exercise for requirements evidence

Observing Organization

• Limited resources/support from NERC

• Receive baseline scenario injects

• Tabletop or discuss scenario events internally

• No interaction with Active organizations

• Valuable internal training opportunity

• Gain experience to participate in future exercises as an Active organization

Your Organization’s Participants

Planner

• Participate in planning conferences

• Designate and orient players and controllers

• Customize injects for more realism

• Provide after action feedback

• Opportunity to provide input on all planning materials

• Provide input to develop scenario and identify after action findings

• Observe Player response and activities

Player

• Participate in orientation and training

• Engage in 2 days of live exercise play and provide after action feedback to planners

• Realistic training opportunity with broad set of BPS entities

• Build and strengthen relationships


GridEx Participation Growth

42

115

19

97

914

6 8

0

20

40

60

80

100

120

140

GridEx 2011 (76) GridEx II (234)

GridEx Participating Organizations

Utilities

Government/Academia/Other

Reliability Coordinator/Independent System Operator

NERC Regional Entity

GridEx III (2015)?

GridEx I (2011)

76 organizations

420 individuals

GridEx II (2013)

234 organizations

2,000+ individuals


16 Reliability Coordinators

Code Name

ERCOT ERCOT ISO

FRCC Florida Reliability Coordinating Council

HQT HydroQuebec TransEnergie

ISNE ISO New England Inc.

MISO Midcontinent Independent System Operator

NBPC New Brunswick Power Corporation

NYIS New York Independent System Operator

ONT Ontario - Independent Electricity System Operator

PJM PJM Interconnection

SPC SaskPower

SOCO Southern Company Services, Inc.

SPP Southwest Power Pool

TVA Tennessee Valley Authority

VACS VACAR-South

PEAK Peak Reliability

AESO Alberta Electric System Operator

The GEWG has SMEs from 12 RCs across the BES to support GridEx planning and conduct


Inject Development ProcessPlanning Time Frame


Inject Delivery ProcessExercise Time Frame


• RC-to-RC Starting May 21 at 2 p.m. Eastern (every 3rd Thursday)

o Best practices for the exercise

o Coordination of impacts with neighboring control areas

o Call details will be promulgated to RC Lead Planners

Other breakout calls may be established as well

• RC-to-Entities (Active organizations) Organized by RC with Active organizations’ Lead Planners

Discuss local objectives and customized injects

Coordinate expected impacts within control area

Feed back into RC-to-RC calls

RC conference calls


Mid-Term Planning Conference

June 10, 2015 | 1:00 – 5:00 p.m. Eastern

June 11, 2015 | 8:00 a.m. – 1:00 p.m. Eastern

(Following NERC’s technical committee meetings)

• Primary objective: Finalize master scenario event list

• Discuss after-action survey with respect to exercise metrics

• Determine Controller/Evaluator and Player documentation requirements

(Still seats available! Conference call details to follow)

Final Planning Conference – September 3 in McLean, VA


Bill Lawrence

[email protected]

mailto:[email protected]

SPP Reliability:Proxy/EEA Report

May 5, 2015

CJ [email protected] 501-614-3569

Presentation 2

mailto:[email protected]

EEA’s:

2

SPP did not have any EEA-3’s during the reporting period.

Proxy Flowgates for this Period:

3

Statistics from February 1, 2015 – April 30, 2015

Flowgate (5221): RedWillow-Mingo 345kV

FG 5521 – RedWillow-Mingo 345kV

TLR_DATE ReturnToZero TLR_Level

02/17/2015 10:30 02/17/2015 13:00 3

02/17/2015 21:30 02/18/2015 00:00 3

02/18/2015 13:00 02/18/2015 18:00 3

03/01/2015 14:00 03/01/2015 20:00 3

FG 5221 – RedWillow-Mingo 345kV

• Temporary Proxy for

• Controlling North–South flows across system

• Maintaining voltage on the 115kV system around Mingo

• Controlling RTCA constraint Knoll-Redline 115kV FTLO Redwillow-Mingo

• Outages in area5

FG 5221 – RedWillow – Mingo 345kV

RedWillow-Mingo 345kV

PTDF

Post Rock-Spearville345 kV OOS

Mingo 115 kV system

Knoll –Redline 115 kV

6

NERC Seasonal Assessments

Operational Guidance for NERC’s Seasonal Assessments ORSMay 5-6, 2015

Presentation 3


Seasonal Assessments Background

• NERC in coordination with the RAS conducts two seasonal assessments in a year: Summer Reliability Assessment (SRA) Winter Reliability Assessment (WRA)

• RAS evaluates various Assessment Areas in the eight Regions• Traditionally, the focus is on planning areas; resource

adequacy, reserve margins and transmission adequacy Good for planning for the season, however short-term nature of these

assessments merit an operational perspective

• 2015 SRA included a pilot for operational analysis


2015 SRA – Operational Analysis Pilot

• Two scenarios were analyzed: Normal load with forced and planned outages Extreme load with forced and planned outages

• Outage data collected from GADS and Regions • FRCC Example


Severe Demand Example

• In some instances, like PJM, it was observed that for severe load scenario – forced and planned outages may cause tight operational flexibility

• Regions and entities have plans to mitigate these conditions by means of Demand Response, public appeals, etc.


Future Seasonal Assessments

• NERC would like to incorporate more operational/short-term scenarios and analysis into the seasonal assessments –Operational Readiness

• Reliability Assessment staff currently attends various Region’s working groups and task force meetings for seasonal assessments, for e.g. NPCC’s CO-12 working group

• ORS agenda item - Operations Review – Notes extremely helpful

• Looking for input from ORS on: Content/Insights from operations (What are you worried about?) Review assessments Timeline for review


Future of Seasonal Assessments

• Currently working on transitioning seasonal assessments to “Short-Term” Assessment

• The new product could be completed with an 18 month outlook, incorporate operational aspects of the system, and provide additional analytical information (e.g., ERS measures)

• Provides opportunity to develop and provide insights and analytics on “shoulder months”

MISO Market Flow Calculation

Presentation 4

MISO Market Flows:

• The calculated energy flows on a specified flow gate as a result of dispatch of generating resources serving market load within a market-based operating entity’s market (excluding tagged transactions).

2

MISO Market Flow Calculation (MFC) Logic:

• Scale down generation across the footprint for total RTO exports on a pro-rata basis.

• Scale down load across the footprint for total RTO imports on a pro-rata basis.

• Determine native generation serving for each Control Zone (CZ) or LBA native load.

3


• Calculate CZ Generation serving load in other CZs within RTO (Transfer MW with in the MISO from one LBA to another).

• Calculate generation shortage weighted load shift factor for all CZs with generation shortage.

• Calculate distribution factor (GLDF) for each unit in the exporting control zone.

• Calculate impact from generation serving native load for each control zone or LBA. (Native Generation to Load Impacts)

4


• Calculate transfer impact of generators serving non-native RTO load and sum them up to get CZ transfer impacts . (Transfer Generation to Load impacts)

• Sum native and CZ transfer impacts directionally to determine market flows in forward and reverse directions.

5

MFC Example:

6

MFC Input Data Source

• UDS (Market Solution)

– Generation; by units– Load plus Losses– Total RTO Exports and Imports

• State Estimator• – Topology for Shift Factor Calculation

7

Calculation Frequency and IDC Data Exchange

• Calculated Frequency:

– Every 5 minutes for Real-time calculation (Current Hour)– Every 15 minutes for Next Hour calculation

• Data Exchange:– Every 5/15 minutes to IDC for TLR purposes– For all MISO CFs and RCFs– Down to 0% Market Flows and down to 5% Market Flows

8

Market Flows reported to IDC

• Directional Market Flows are reported to IDC in 3 buckets– 7FN (Priority 7-FN); ED6 (Priority 6-NN); and ED2 (Priority 2-NH)

(only for RCFs; for CFs ED2 = 0)

9

Market Flows and TLR Process

• IDC calculates Relief Required from the markets using 5%Forward Market Flows

– Pro-rata share with respect to the Tag Impacts with same priority

• IDC sends Target Market Flow to the markets using 0%Net Market Flows

– MISO UDS uses Target Market Flow value from IDC to bind and provide relief

10

Questions?

11

Discussion of IDC PFV Test Metrics

NERC ORSMay 5, 2015Chattanooga

Presentation 5

Proposed Measures

• Data Availability – measure performance of data supply against requirements

• Generator outputs• line flows for branches modeled as flowgates in the IDC• tie-lines• system loads• net actual interchange• dynamic schedules• block dispatch data• next hour dispatch

Proposed Measures

• Input Data Accuracy – measure accuracy of reported data against actual value– unit output– flowgate and tie-line flow– BA load

Proposed Measures

• Validate Calculation Logic– Measure and track actual flowgate flow against

calculated flowgate flow in 15 minute increments– Test three Seams Agreement Methodologies to ensure

consistent results• POR/POD methodology• Marginal zone methodology• Slice of system methodology

– Can we test with known data?– Can we test against a study powerflow case with

identical system setup?

Proposed Measures

• Pseudo Ties– Test different pseudo tie modelling methodologies

to ensure consistent results

• Alarming– Confirm alarming for loss of data input, etc. works

as required

Questions for Input from ORS

• Is the priority of the ORS to minimize the difference of Flowgate Actual Flow and Calculated Flow (i.e. keep unaccounted for flow minimized)

• Are all of the Actual Flows (Gens, Flowgates, etc.) captured at the same time (i.e. Data latency issues)

• What if some of the data when captured for submittal has suspect quality (stale)?

• Are outages that impact flows captured and sent at the same time as the flows in the GTL calculations?

Reliability Coordinator Participation Brief Reliability Subcommittee... · 2015-06-09 · • Data...

Documents

Transcript of Reliability Coordinator Participation Brief Reliability Subcommittee... · 2015-06-09 · • Data...