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

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.


Effective Date: 4/1/2019

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:


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:


R1.3.2 the Responsible Entity experiences:

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:

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.