BAL-002-3: Disturbance Control Standard – Contingency Reserve for Recovery from a Balancing Contingency Even

Purpose
To ensure the Balancing Authority or Reserve Sharing Group balances resources and demand and returns the Balancing Authority’s or Reserve Sharing Group’s Area Control Error to defined values (subject to applicable limits) following a Reportable Balancing Contingency Event.

Applicability

• Balancing Authorities
• A Balancing Authority that is a member of a Reserve Sharing Group is the Responsible Entity only in periods during which the Balancing Authority is not in active status under the applicable agreement or governing rules for the Reserve Sharing Group
• Reserve Sharing Group

Effective Date: 4/1/2019

Requirements
R1.  The Responsible Entity experiencing a Reportable Balancing Contingency Event shall:

[Violation Risk Factor: High] [Time Horizon: Real-time Operations]

R1.1. within the Contingency Event Recovery Period, demonstrate recovery by returning its Reporting ACE to at least the recovery value of:

• • zero (if its Pre-Reporting Contingency Event ACE Value was positive or equal to zero); however, any Balancing Contingency Event that occurs during the Contingency Event Recovery Period shall reduce the required recovery: (i) beginning at the time of, and (ii) by the magnitude of, such individual Balancing Contingency Event,

Or,

• • its Pre-Reporting Contingency Event ACE Value (if its Pre-Reporting Contingency Event ACE Value was negative); however, any Balancing Contingency Event that occurs during the Contingency Event Recovery Period shall reduce the required recovery: (i) beginning at the time of, and (ii) by the magnitude of, such individual Balancing Contingency Event.

R1.2. document all Reportable Balancing Contingency Events using CR Form 1.

R1.3. deploy Contingency Reserve, within system constraints, to respond to all Reportable Balancing Contingency Events, however, it is not subject to compliance with Requirement R1 part 1.1 if the Responsible Entity:

R1.3.1 is (i) a Balancing Authority or (ii) a Reserve Sharing Group with at least one member that:

• • •   is experiencing a Reliability Coordinator declared Energy Emergency Alert Level, and
    • is utilizing its Contingency Reserve to mitigate an operating emergency in accordance with its emergency Operating Plan, and
    •    has depleted its Contingency Reserve to a level below its Most Severe Single Contingency, and
    • has, during communications with its Reliability Coordinator in accordance with the Energy Emergency Alert procedures, (i) notified the Reliability Coordinator of the conditions described in the preceding two bullet points preventing the Responsible Entity from complying with Requirement R1 part 1.1, and (ii) provided the Reliability Coordinator with an ACE recovery plan, including target recovery time

Or,

R1.3.2 the Responsible Entity experiences:

• • • multiple Contingencies where the combined MW loss exceeds its Most Severe Single Contingency and that are defined as a single Balancing Contingency Event, or
    • multiple Balancing Contingency Events within the sum of the time periods defined by the Contingency Event Recovery Period and Contingency Reserve Restoration Period whose combined magnitude exceeds the Responsible Entity’s Most Severe Single Contingency.

M1.   Each Responsible Entity shall have, and provide upon request, as evidence, a CR Form 1 with date and time of occurrence to show compliance with Requirement R1.  If Requirement R1 part 1.3 applies, then dated documentation that demonstrates compliance with Requirement R1 part 1.3 must also be provided.

R2. Each Responsible Entity shall develop, review and maintain annually, and implement an Operating Process as part of its Operating Plan to determine its Most Severe Single Contingency and make preparations to have Contingency Reserve equal to, or greater than the Responsible Entity’s Most Severe Single Contingency available for maintaining system reliability. [Violation Risk Factor: High] [Time Horizon: Operations Planning]

M2.   Each Responsible Entity will have the following documentation to show compliance with Requirement R2:

• a dated Operating Process;
• evidence to indicate that the Operating Process has been reviewed and maintained annually; and,
• evidence such as Operating Plans or other operator documentation that demonstrate that the entity determines its Most Severe Single Contingency and that Contingency Reserves equal to or greater than its Most Severe Single Contingency are included in this process.

R3. Each Responsible Entity, following a Reportable Balancing Contingency Event, shall restore its Contingency Reserve to at least its Most Severe Single Contingency, before the end of the Contingency Reserve Restoration Period, but any Balancing Contingency Event that occurs before the end of a Contingency Reserve Restoration Period resets the beginning of the Contingency Event Recovery Period. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]

M3.  Each Responsible Entity will have documentation demonstrating its Contingency Reserve was restored within the Contingency Reserve Restoration Period, such as historical data, computer logs or operator logs.