module 7: additional real-time topics · 2018-09-14 · • telemetry data which they are...

Module 7:Additional Real-Time Topics

3

Module Objectives

• Identify principle uses of Telemetry for Real-Time Operations

• Describe general process of Forced Outage Detection

• Describe the last steps before receiving Approval-to-Energize

• Describe in general the content of a Verbal Dispatch Instruction

• Identify the levels of Emergency Communications and Alerts

Upon completion of this module you will be able to:

Telemetry

5

Telemetry

• Telemetry Requirements and Standards

• Equipment Operating Ratings and Limits

• Real-Time Data

• Telemetry of Breakers and Switches

• Requests for Telemetry

• Loss of Telemetry

• Telemetry affecting State Estimator

Telemetry Topics

6

ERCOT Telemetry Requirements

Each QSE and TSP shall continuously provide:• Telemetry data which they are responsible for.• Real-Time status and analog measurements for all

Modeled Transmission Elements.• Notice to ERCOT for known telemetry issues when

data is:• Not available• Unreliable for operational purposes

Telemetry Standard requirements (frequency of updates, means of communication, nomenclature format etc.) are defined in the Protocols, Operating Guides and ICCP Communications Handbook.

7

ERCOT Telemetry Standards

The Telemetry Standards also define the requirements for:• Performance and observability requirements of voltage

and power flow measurements on modeled Transmission elements.

• Redundancy of telemetry measurement data.• Meeting the State Estimator Standards.• QSE & TSP real-time monitoring and reporting.

8

Telemetry

Updates are accomplished through a fully redundant communication link called ICCP (ICCP = Inter-Control Center Communications Protocol)

ICCP

ERCOT real-time operation processes require the update of real-time data from QSEs and TSPs to ensure that processes run with the most up-to-date data.

Real-Time Data

ICCP links are implemented between TSP systems and ERCOT systems. However, TSPsystems communicate with their remote field devices using a variety of differentprotocols. Accurate mapping between TSPs and ERCOT is important!

9

Telemetry

ICCPERCOT Systems

TSP Control System

Remote Telemetry

TSPManualEntries

SCADA

Non-Telemetered Data

• All breakers and switches in the Network Model which are used to switch Transmission Elements or Loads

• TSPs manually enter “actual current state” of non-telemetered devices

• Upon loss of telemetry, ERCOT processes use last known state and manually replaced data.

Telemetry of Breakers and Switches

10

Telemetry

• Telemetry of bus load, voltages, tap position, and flows on Modeled Transmission elements required

• To the extent needed to estimate ALL generation injections and load withdrawals

• Must meet State Estimator performance standard• Implications of inaccurate LMP results vs. the cost to

remedy taken into account• Special requirements for non-load substations

• ERCOT can request additional telemetry to achieve N-1 redundancy

Telemetry of Real-Time Measurements Requirements

11

Telemetry

ERCOT will discuss the problem with the TSP first before requesting review/calibration of equipment

For telemetered data inconsistent with surrounding data, ERCOT may request the TSP to…• Calibrate/repair the misbehaving equipment

• Request an Outage to calibrate/repair equipment

• Provide ERCOT with plan to re-calibrate/repair in reasonable time

• Provide engineering analysis proving data element is within specifications

12

Telemetry

* Concern or deficiency cannot be due to any inadequacy of the State Estimator program

• Additional telemetry may be required* if network observability or the measurement redundancy is not adequate to produce acceptable SE results

• ERCOT will provide evidence supporting congestion or reliability problems requiring additional observability

Requests for Telemetry

13

Telemetry

The TSP is not required to provide telemetry measurements from a location that is not owned by that TSP, if the location owner does not grant access to the TSP for the purpose of obtaining such measurements.

Options available to TSP upon receipt of ERCOT request• Agree with the request and make reasonable effort to

install equipment providing measurements• Provide ERCOT an analysis of the cost to comply with

the request• Appeal the request to the TAC or present an alternative

solution to ERCOT for consideration• If ERCOT rejects the alternative solution, TSP can

appeal request to TAC within 65 days

Requests for Telemetry

14

Loss of Telemetry

Upon loss of telemetry, each QSE & TSP shall:• Notify ERCOT as soon as practicable when there are

known telemetry issues.• Address the data issues with either a correction of the

telemetry data as soon as practicable, or• Manually replace the data.• Provide an estimated time for resolving if the data will be

out for two or more days.

15

Telemetry Issues affecting ERCOT Network Security Analysis

When telemetry issues affect Network Security Analysis:• Real-Time telemetry data issues can cause invalid State

Estimator solutions. • ERCOT shall notify the QSE or TSP responsible for the

incorrect telemetry data.• If the QSE or TSP cannot address the issue within 10

minutes, they will verbally agree on the best assumed data to manually replace the data point until the Real-Time issue is resolved.

16

Telemetry Issues affecting ERCOT Network Security Analysis

• If the QSE or TSP cannot resolve the Real-Time telemetry data issue within two Business Days, it shall provide an estimated time of resolution.

• QSEs and TSPs shall notify ERCOT when the Real-Time telemetry data issue is resolved.

Forced Outage Detection

18

Forced Outage Detection - Overview

Telemetry

NetworkOperations

Model

ConstraintsReal-Time Dispatch

Security-Constrained Economic Dispatch

Offers

Pricing

Dispatch Instructions

Real-Time Network Security Analysis

Resource Limits

Force Outage Detection

Real-Time Operations

19


Telemetry

NetworkOperations

Model



Offers

Pricing



Resource Limits

Force Outage Detection SCADA Telemetry

• Provides real-time breaker status and output of Resources

• Provides status of observable Transmission Elements of the Network Operations Model

• ERCOT Operator may consult QSE or TSP regarding discrepancies

20


Telemetry

NetworkOperations

Model



Offers

Pricing



Resource Limits

Force Outage Detection Forced Outage Detection

Uses logic equations to translate breaker and switch status changes into Transmission Element status changes

21

Forced Outage Detection (FOD) Purpose• Detect status changes based on associated breaker and

switch status changes for the following Transmission Facilities

Resources Transmission Transformers Loads

• Identify forced outages of Transmission Facilities

• Produce alarms for ERCOT Operators in real-time at same frequency as SCADA telemetry processing


22

EXAMPLE


Is the Line . . .

Energized?

Line CLine BO

C

C

O

O

C

C

O

Line A

Load

Is the Load energized?

C

Resource

Is the Resource on or off?

Does the status match the Current Operating Plan?

OIs the transformer energized?

O

23

EXAMPLE


What happens if the Line is . . .

Open on one end?

Line CLine BO C

O

O

C

C

O

Line A

Load


C

Resource

Is the Resource on or off? Does the status match the Current

Operating Plan?


O

O

24

EXAMPLE


What happens if the Line is . . .

Open on both ends?

Line CLine BO

O

O

C

C

O

Line A

Load


C

Resource


Operating Plan?


O

O

O

25

EXAMPLE


If open on both ends, what happens to the Load?

Line CLine BOO

C

C

O

Line A

Load


C

Resource


Operating Plan?


O O

O

O

26

Forced Outage Detection uses real-time telemetry to look at the combination of breaker and switch statuses

EXAMPLE


Line CLine BO

C

C

O

O

C

C

O

Line A

Load

C

ResourceO

O

27


Status Change & Forced

Outage Alarms

Forced Outage Displays


Breaker & Switch Status

Planned Outages

Planned Resource Status

Network Operations Model

Existing Forced Outages

Inputs and Detection

28

Forced Outage Detection (continued)

Forced Outage

Forced Extension3

Unavoidable Extension

2

1

ERCOT Operator is alerted to unplanned outages

Unplanned Outages for QSE and TSP Facilities

29


ERCOT Operator may request that a QSE or TSP

• Correct the breaker and/or switch status indication causing the alarm

• Enter an Unavoidable Extension, Forced Outage or Forced Extension into the Outage Scheduler

Unplanned Outages for QSE and TSP Facilities

30

After a configurable time into the Operating Hour, FOD detects a deviation between planned resource status from COP and FOD calculated resource status.


FOD detects a deviation between telemetered Resource status and FOD calculated Resource status

1

2

Resource Status Deviations ERCOT Operator is notified of status deviations for QSE Resources

31


FOD shall notify the ERCOT operator of an unexpected deviation from the operating plan.

Example:

• Planned Resource status from COP is “ON”, and

• Next hour planned status is also “ON”, and

• Resource status calculated by FOD is “OFF”

Resource Status Deviations

32


ERCOT Operator may verbally request that the responsible QSE correct:

• the breaker and/or switch status indication causing the alarm

• the deviation between COP and the FOD calculated status

Resource Status Deviations

33

Voltage Profiles and Voltage Support Service

34

Definitions

Voltage Profile• Normally desired Voltage Set Points for those Generation

Resources in ERCOT, as specified in the Protocols.Voltage Set Point

The voltage that a Generation Resource:• maintains at its Point of Interconnection• is initially communicated via the Voltage Profile• may be modified by a Real-Time instruction from ERCOT or

the interconnecting TSP, (or TSP’s agent) through the Generation Resource or it’s QSE.

Voltage Support Service (VSS) • An Ancillary Service that is required to maintain transmission

and distribution voltages on the ERCOT Transmission Grid within acceptable limits.

35

System Voltage Profile

Voltage Profile• ERCOT coordinates seasonal studies with TSPs.

• Predetermined distribution of normally desired voltage setpoints across the ERCOT region.

• Based on sound engineering studies.

• Uses the appropriate Network Operations model.

• ERCOT or TSPs may modify voltage setpoints based on current system conditions.

Goal: During Normal Operating conditions, transmission voltages should not exceed 105% nor fall below 95% of the nominal voltage.

36

Posted VoltageProfile

MIS>Grid>Transmission>Voltage & Dynamic Ratings

Voltage Profiles - ERCOT Responsibilities

Post the Seasonal Voltage Profile on the MIS.

Coordinate with TSPs and QSEs to maintain transmission voltage levels within normal and post-contingency limits.

Coordinate with TSPs to deploy static Reactive Power reserves

37

Voltage Profiles - TSP Responsibilities

Monitor system voltages and operate static Reactive Resources to maintain Dynamic Reactive Reserves.

Communicate directly with Resource Entities or QSEs to maintain Voltage Setpoints at Generation Resources.



38

Voltage Profiles – Resource Entity Responsibilities

Maintain transmission system voltages in accordance with the published voltage profiles and as instructed by its QSE or TSP.

Operate with Resource’s AVR in voltage control mode and notify its QSE and TSP of any change in AVR status.

Voltage Set Point instructions shall be completed in no more than five minutes from receipt.



39

Voltage Profiles – Resource Entity Responsibilities

Except under Force Majeure or if permitted by ERCOT or the interconnecting TSP:

• operate within ± 2% of the posted Voltage Profile at the Point of Interconnection

• provide lagging or leading reactive capability up to the Resources Unit Reactive Limit (URL) at all times



40

Voltage Profiles - QSE Responsibilities

Ensure that Resources maintain the desired voltage setpoint and respond to VSS instructions. Telemeter Real and Reactive Power, AVR and PSS status to ERCOT.Notify ERCOT of any change in a Resources AVR status.Inform ERCOT if a Resource can not meet its voltage profile.



41

Definitions

Voltage Profile• Normally desired Voltage Set Points for those Generation

Resources in ERCOT, as specified in the Protocols.Voltage Set Point

The voltage that a Generation Resource:• maintains at its Point of Interconnection• is initially communicated via the Voltage Profile• may be modified by a Real-Time instruction from ERCOT or

the interconnecting TSP, (or TSP’s agent) through the Generation Resource or it’s QSE.

Voltage Support Service (VSS) • An Ancillary Service that is required to maintain transmission

and distribution voltages on the ERCOT Transmission Grid within acceptable limits.

42

Voltage Support Service

UnitReactive

Limits(URL)

The URL defines the maximumquantity of Reactive Power that

a Generator Resource iscapable of providing (Lagging) or

absorbing (Leading).95

Power Factor

Leading

+

–

MWMVA

R

+

–

Lagging

Who provides it • Generating Resources > 20 MVA

• Generation > 20 MVA aggregated to the same bus

• To qualify, must be capable of producing quantity of Reactive Reserve (MVars) at 0.95 power factor at the Resource’s maximum rated real power capability (MWs)

43


UnitReactive

Limits(URL)




Power Factor

Leading

+

–

MWMVA

R

+

–

Lagging

Intermittent Renewable Resources (IRRs)

For Resources operating at:• ≥10% of Nameplate rating – full reactive output required• ≤ 10% of Nameplate rating and unable to support POI

voltage setpoint - ERCOT may require IRR to disconnect.

44


UnitReactive

Limits(URL)




Power Factor

Leading

+

–

MWMVA

R

+

–

Lagging

Generation Resources and TSPs may enter into an agreement in which:• Generation Resource compensates TSP for providing

Voltage Support Service• TSP must certify to ERCOT that the agreement meets the

Resources reactive power requirements

45

>> Compensation

URL

Not Paid

Resource is not paid for operating within it’s normal operating range

MW

MVAR

+

–

URL

Normal Operating Range(Leading)

Normal Operating Range(Lagging)

46

>> Compensation

Not Paid MW

MVAR

+

–

VSS VAr’sPaid

When directed by ERCOT, Resource is compensated for operating above it’s normal URL



47

>> Compensation

Not Paid MW

MVAR

+

–

VSS VAr’sPaid

Lost

Opp

ortu

nity

P

aym

ent

When directed by ERCOT, Resource is compensated for real power reductions to provide for additional reactive capability



Approval-to-Energize

49

Last step before new equipment is energized to ensure all aspects of equipment have been accurately and consistently incorporated into all ERCOT Network Models

• Connectivity

• Telemetry Mapping

• Outages

• Characteristics

Approval to Energize Process

What is Approval to Energize?

50

Required prior to energization of newly installed, removed, or relocated facilities

At least 7 Business Days prior to the planned energization date, ERCOT Operations Support will review the elements planned for energization and issue approvals or rejections


ERCOT requires at least 7 calendar days prior to energization to complete the process and

confirm that equipment is accurately modeled.

51


Approval

• Is the equipment in the current Network Operations Model?

• Is telemetry being provided to ERCOT with appropriate data quality?

• Is the equipment properly represented in the Outage Scheduler?

If any responses to the questions above are ‘NO,’ then the request is rejected

52


If the equipment to be energized is not in the current production model:• Market Participant may receive a notice that the equipment

is not in the current model and that approval may be delayed.

• Market Participant is required to call ERCOT Operations and provide details as to when the equipment is expected to be changed in the model.

• With appropriate communications, the energization date should not be delayed.

http://www.google.com/url?sa=i&rct=j&q=&esrc=s&frm=1&source=images&cd=&cad=rja&docid=aMqTv4aSK0tXrM&tbnid=AAHYDIdo1_6JmM:&ved=0CAUQjRw&url=http://www.ucan.org/telecommunications/landline/lifeline/california_lifelineuniversal_lifeline_telephone_service&ei=RpPEUZ7DOoHa9QTHoIGYBg&psig=AFQjCNGCzmsozOKpqp5_uX4mAEO57pLyew&ust=1371923581153300


53


If the equipment to be energized is not in the current production model:• It impacts the situational awareness of ERCOT Operations.

• Requires a NOMCR to update the model

• Needs to be reflected in the Outage Scheduler



54

ERCOT will email the Market Participant of approved and rejected energization requests. For rejections, the reason why will be identified.

NOTE: If changes in the field energization date are anticipated, Market Participants must:

• Contact ERCOT Operations with the updated information.

• Update the Outage Scheduler.




55


On the day of energization:

• Market Participant contacts ERCOT by telephone, requesting permission to energize equipment



Verbal Dispatch Instructions

57


Verbal instructions are acknowledged by providing the receivingoperator’s identification and by repeating the VDI to ERCOT orally.

C

Line 1

CLine 2

CLine 3

CLine 4

CLine 5

CLine 6 CB 1

Auto 1 Auto 2

Auto 3

Bus Section Breaker

CB 10

138G

138C

138A138E

EPS

A

The following section applies only to Verbal Dispatch Instructions (VDIs) issued for Real-Time operations intended to change or preserve the state, status, output, or input of an element or facility of the ERCOT System.

58



Dispatch Procedures• Most Instructions between ERCOT and TSPs are Verbal.

• TSP shall immediately request clarification of Dispatch Instruction if unable to understand its responsibility under the Dispatch Instruction.

C

Line 1

CLine 2

CLine 3

CLine 4

CLine 5

CLine 6 CB 1

Auto 1 Auto 2

Auto 3

Bus Section Breaker

CB 10

138G

138C

138A138E

EPS

A

59



When issuing a VDI, ERCOT shall: • Confirm the Market Participant’s response if the repeated

VDI is correct;

• Reissue the VDI if the repeated VDI is incorrect; or

• Reissue the VDI or take an alternative action if the VDI was not understood by the Market Participant.

C

Line 1

CLine 2

CLine 3

CLine 4

CLine 5

CLine 6 CB 1

Auto 1 Auto 2

Auto 3

Bus Section Breaker

CB 10

138G

138C

138A138E

EPS

A

60

ID of responsible Entity and instructing authority

Specific TSP facilities subject of Dispatch Instruction

Specific action required

Current operating level or state of facilities subject to instruction

Operating level or state to which facilities will be dispatched

Time of notification of Dispatch Instruction

Time at which TSP is required to initiate dispatch instruction

Time at which TSP is required to complete Dispatch Instruction

Verbal Dispatch Instruction (VDI) reference number


Content of Verbal Dispatch Instructions

61


Process:1. TSP or QSE notifies ERCOT2. ERCOT shall resolve the conflict

by issuing another Dispatch Instruction

Valid reasons for not complying

If Dispatch Instructions:

• create a safety issue, risk of bodily harm, or possible damage to equipment

• are not in compliance with the Protocols

• conflict with other valid Instructions

62

Responsibility after Final Dispatch Instructions:TSP is held responsible for complying with Dispatch Instructions in the Nodal Protocols and may be assessed sanctions for not complying

In the Event of Dispute of Dispatch Instructions:ERCOT and TSP will document:• Communications• Agreements• Disagreements• Reasons for their actions


Resolution process follows Alternative DisputeResolution (ADR) Procedure in Protocols

Emergency Operating Conditions

64

Emergency Operation

Emergency Operation addresses operating conditions……in which reliability of ERCOT system may not be adequate…where a market solution may not be readily apparentERCOT can instruct TSPs and QSES to take actions that would otherwise be discretionary.

65

Overview

Emergency Condition Communications

Energy Emergency Alerts

1

2

66

Communications under Emergency Conditions between ERCOT, QSEs and TSPs may relate to, but are not limited to:

• Weather

• Transmission

• Generation

• Computer Failure

It is essential that good, timely and accurate communication routinely occur between ERCOT, TSPs and QSEs.

Overview

67

Four Types of Emergency Communications

Operating Condition Notice

Emergency Notice

Advisory

Watch

68


Emergency Notice

Advisory


Watch

How ERCOT determines communication type:• Amount of time market has to respond

• May range from days in advance to immediate.

• If time is insufficient, ERCOT may skip one or more of the steps

69

Watch


Emergency Notice

Advisory


Emergency Condition Communications specify:• Severity of the situation

• Area affected

• Areas potentially affected

• Anticipated duration

70


Emergency Notice

Advisory

Watch

For each of the following four levels of communications, ERCOT shall verbally provide notice to all QSEs and TSPs and shall post the information to the MIS Public Area.

TSPs shall notify their DSPs accordingly.


71


Emergency Notice

Advisory

Watch

QSEs and TSPs are expected to:

• Establish and maintain internal procedures for monitoring system conditions

• Implement appropriate measures when conditions warrant


72

Operating Condition Notices


An Operating Condition Notice is…

• First level of communication

• Only issued if grid is still “n-1 secure”

• For informational purposes only

• ERCOT may solicit additional information from Market Participants

• Intended to give Market maximum advanced notice of potential issues

73

Conditions which may warrant anOperating Condition Notice:• Projected Reserve Capacity Shortage

• Unplanned transmission outages

• Weather-related concerns like:

• Anticipated freezing temperatures

• Hurricanes

• Wet weather

• Ice storms

Operating Condition Notices


74

Advisory

Advisory

An Advisory is…

• Second level of communication

• For informational purposes only, but may indicate that action is required of Market Participants

• Provide Fuel Capabilities

• Increase Ancillary Service Requirements

75

Advisory

Conditions which may warrant an Advisory :

• Projected insecure conditions

• Communication or control system limitations

• Severe weather anticipated in 3 days:

• Freezing temperatures• Hurricane / Tropical Storm• Ice storms

Advisory

76

Advisory

When Physical Responsive Capability falls below 3000MW and EEA Level 2 or 3 is anticipated, ERCOT will coordinate with TSPs to utilize:• Outage restoration

• Tap Changer adjustments

• System reconfiguration

• Constraint Management Plans

• 15-Minute Ratings

• Two Hour Rating for Post-Contingency Loading

• Risk of Double-Circuit Contingencies

Advisory

77

Watch

Watch

Watch:• Third level of communication

• Address Emergency Conditions which exist or are imminent

• Grants ERCOT additional operational authority to deal with emergency conditions

78

Watch

Watch

Conditions which may warrant a Watch:

• SCED fails to solve

• Transmission security violations

• Insufficient Ancillary Services in Operating Period

• Insufficient Ancillary Service offers in DAM or in a SASM

• Severe weather is imminent:

• Freezing temperatures• Hurricane / Tropical Storm• Ice storms• Severe heat

79

Watch

Watch

If Corrective Action required, ERCOT may:

• Send “corrective action” dispatch instructions to appropriate Market Participants

• Market Participant must comply

If Markets Fail, ERCOT may:

• Immediately procure Ancillary Services from existing offers

• Issue dispatch instructions to Resources to provide additional Ancillary Services

80

Watch due to SCED Failure

Watch

What happens if SCED fails?

• Base Points previous to failure apply, unless ERCOT advises otherwise

To resolve SCED Failure, ERCOT may:

• Relax active transmission constraints

• Reduce AS Schedules for specific Resources

• Manually issue Emergency Base Points or issue instructions to hold previous interval

81

Emergency Notice

Emergency Notice

Emergency Notice:

• Fourth level of communication

• Notification that ERCOT System is in an unreliable condition

• Requires immediate action to return ERCOT System to a reliable condition

82

Emergency Notice

Emergency Notice

Emergency Notices are issued when:

• ERCOT cannot maintain minimum reliability standards

• Transmission Grid is at risk for cascading outages and/or large scale disruption to Load

• Operating with overloaded Transmission Elements

• Severe weather is having an adverse impact on the ERCOT System

83

Emergency Notice

Emergency Notice

If Emergency Condition is due to a transmission problem, ERCOT shall act immediately to return to a reliable state by:• Instructing Resources to change output

• Curtailing or changing DC Tie Load

• Instructing TSPs to shed Load

84

Overview

Emergency Condition Communications

Energy Emergency Alerts

1

2

85

Energy Emergency Alert

At times, it may be necessary for ERCOT to reduce System Demand because of a temporary decrease

in available supply.

The Energy Emergency Alert (EEA) provides orderly pre-determined

procedures for operating under short supply conditions.

86

Energy Emergency Alert

Goals

• Use market processes to fullest extent practicable

• Provide maximum possible continuity of service

• Maintain the integrity of the ERCOT System

• Reduce the chance of cascading outages

Outlines method of curtailing demand, utilizing

• Load Resources

• Interruptible Load

• Firm Load, when necessary

Energy Emergency Alert (EEA)

87

Principles of Energy Emergency Alert

• Use of market processes to the fullest extent practicable without jeopardizing reliability

• A plan to maximize use of ERCOT capability

• Manages Interconnection Reliability Operating Limits (IROLs)

• Leverages Ancillary Services

• Maintains nuclear station service

• Secures startup power

• Operates Resources during loss of communication

• Restoration of services as defined in the Operating Guides

88

Responsibilities during Energy Emergency Alert

ERCOT is responsible for:

• Coordinating with QSEs, TSPs and DSPs.

• Monitoring ERCOT System conditions

• Initiating the EEA levels

• Maintaining transmission security limits

ERCOT may at any time issue an appeal through the public news media for voluntary energy conservation.

89

EEA Levels

Physical Responsive Capability (PRC) falls below 2,300 MW and is not projected to recover within 30 minutes.

1

2

3

Clock-minute average frequency falls below 59.91 Hz for 15 minutes or PRC falls below 1,750 MW and is not projected to recover within 30 minutes

Clock-minute average frequency falls below 59.91 Hz for 20 minutes or PRC cannot be maintained above 1,350 MW

90

1

EEA Level 1

Physical Responsive Capability (PRC) falls below 2,300MW and is not projected to recover within 30 minutes.

ERCOT shall take the following steps to maintain steady state system frequency near 60 Hz and maintain PRC above 1,750 MW:

• Instruct available off-line Resources to start

• Instruct on-line Resources to stay on

• Utilize available DC Tie Import Capability

ERCOT may also instruct QSEs to deploy available ERS-30 capacity

91

Emergency Response Service (ERS)

• Deployed by QSEs

• Can be Load, Generation or an aggregate

• Cannot be a registered Generation Resource

• Cannot be an Intermittent Renewable Resource

• Contracted by ERCOT as 10-minute or 30-minute ramp

Emergency Response Service

QSE

ERS-

10Lo

ad

ERS-

30G

en

QSEER

S-30

Load

ERS-

10G

en AggregationAggregation

92

2

EEA Level 2

Clock-minute average frequency falls below 59.91 Hz for 15 minutes or PRC falls below 1,750 MW and is not projected to recover within 30 minutes

ERCOT shall take the following steps to maintain steady state system frequency at a minimum of 59.91 Hz and maintain PRC above 1,375 MW:

• Instruct TSPs and DSPs to reduce customer load by using voltage reduction measures or load management plans

• Instruct QSEs to deploy remaining ERS

• Deploy Responsive Reserve from Load Resources on high-set under-frequency relay

• Instruct TSPs to execute available BLTs

93

• Transfers Load between ERCOT and Non-ERCOT control areas.

• Requires approval from ERCOT for Planned or Forced Outages, unless a governmental order is issued.

• Must not jeopardize ERCOT reliability

• Must be Registered and Metered

• Must be monitored by SCADA

Block Load Transfers

ERCOT

Non-ERCOT Control Area

94

3

EEA Level 3

Clock-minute average frequency falls below 59.91 Hz for 20 minutes or PRC cannot be maintained above 1,350 MW

If clock-minute average frequency falls below 59.91 Hz for 25 minutes or PRC falls below 1,000 MW and is not projected to recover within 30 minutes

• ERCOT shall direct all TSPs and DSPs to shed firm load* in 100 MW blocks in order to maintain system frequency at a minimum of 59.91 Hz and recover 1,000 MW of PRC within 30 minutes.

• Pro-rata share of load shedding based on previous year’s peaks

• TSPs and DSPs must consider health and safety of the community

* Excluding Load on low-set under-frequency relays

95

• ERCOT may immediately implement EEA Level 3 if the clock-minute average frequency falls below 59.91 Hz for 20 consecutive minutes,

• ERCOT shall immediately implement EEA Level 3 any time the steady-state frequency is below 59.5 Hz

May not be time to implement all steps in sequence . . .

Additional EEA Guidlines

96

EEA Termination

ERCOT shall:• Continue EEA until sufficient Resources are available

• Restore Normal SCED Operations

• Terminate EEA levels in reverse order, where practical

• Notify QSEs and TSPs of level termination

• Maintain a stable system frequency when restoring load

QSEs and TSPs shall:• Implement actions to terminate EEA levels

• Restore loads when specifically authorized by ERCOT

• Report to ERCOT as each level is restored

97

Module Summary

You should now be able to: • Describe requirements for communication during

Emergency Operations

• Describe impacts of Emergency Conditions on Real-Time Operations

• Explain Energy Emergency Alerts and how they impact Real-Time Operations

98

ERCOT Website http://www.ERCOT.com

ERCOT Protocolshttp://www.ercot.com/mktrules/nprotocols/

Market Educationhttp://www.ercot.com/services/training/

Market Education [email protected]

Additional Resources

http://www.ercot.com/

http://www.ercot.com/mktrules/nprotocols/

http://www.ercot.com/services/training/

mailto:[email protected]

99

Your Feedback

Got Feedback?

Scan this QR code to take the course survey!

www.surveymonkey.com/r/ERCOTMarketTraining

module 7: additional real-time topics · 2018-09-14 · • telemetry data which they are...

Documents