Balancing Authority ACE Limit (BAAL)

BAAL establishes a dynamic, frequency-dependent envelope for ACE. Unlike CPS2, which uses a fixed limit (L10), the BAAL limit expands and contracts based on the interconnection's actual frequency deviation. The limit is calculated as a linear function of frequency error, creating a wider tolerance when frequency is near nominal and a tighter, more restrictive boundary when frequency deviates significantly.

The standard defines two limits: BAAL_High and BAAL_Low. These are calculated using the formula: BAAL = -10B * (FA - FS) * (FTL_High - FS) / (FA - FS). Where B is the frequency bias (MW/0.1 Hz), FA is actual frequency, FS is scheduled frequency, and FTL is the Frequency Trigger Limit. The calculation ensures the limit is proportional to the balancing authority's size and the severity of the frequency excursion.

BAAL relies on predefined Frequency Trigger Limits (FTL) set by the reliability coordinator. For the Eastern Interconnection, a common FTL is ±0.036 Hz from 60 Hz. If frequency remains within the FTL, the BAAL limit is effectively infinite, allowing normal operation. Once frequency exceeds the FTL, the BAAL boundary tightens, requiring the balancing authority to actively correct its ACE to avoid a violation.

A BAAL violation occurs when a balancing authority's ACE exceeds its calculated limit for more than 30 consecutive clock-minutes. This is a more stringent, sustained-duration metric compared to CPS2's 10-minute average windows. The standard is designed to catch entities that are persistently contributing to a frequency deviation rather than penalizing momentary, self-correcting ACE swings.

BAAL acts as a complementary 'safety valve' to the statistical CPS1 and CPS2 standards. While CPS1 measures long-term statistical correlation with frequency error and CPS2 bounds 10-minute ACE averages, BAAL provides a hard, real-time operational limit. It directly addresses the risk that a balancing authority's sustained, large ACE could be the primary driver of an interconnection-wide frequency excursion, regardless of its CPS1 score.

When frequency approaches an FTL, the BAAL standard forces a more aggressive Automatic Generation Control (AGC) response. Control room operators must monitor their BAAL compliance dashboard and may need to manually deploy additional regulation or contingency reserves if AGC alone cannot correct a sustained ACE within the tightening limit. This shifts operational focus from purely statistical compliance to active, real-time frequency support.

A statistical metric that measures ACE variability relative to interconnection frequency error over a rolling 12-month period. CPS1 and BAAL are complementary — CPS1 ensures long-term non-detrimental behavior, while BAAL enforces real-time boundaries.

• Compliance ratio: Must exceed 100% monthly
• Frequency link: Ties ACE directly to frequency deviation magnitude
• Violation consequence: Requires root-cause analysis and mitigation plan

A setting expressed in MW/0.1 Hz that quantifies a balancing authority's expected response to frequency deviations. This coefficient directly shapes the ACE calculation and therefore the BAAL boundary.

• Typical value: 1% of peak load per 0.1 Hz
• Annual review: Must be updated by January 15 each year
• Over-bias risk: Causes over-correction and potential oscillation

The secondary frequency control system that executes corrective action on ACE. AGC is the actuator that BAAL constrains — when ACE approaches the BAAL limit, AGC must respond with sufficient ramp to prevent exceedance.

• Cycle time: Typically 2-6 seconds
• Control modes: Tie-line bias, flat frequency, flat tie-line
• Resource assignment: Uses participation factors to distribute regulation

A NERC standard requiring recovery of ACE to pre-disturbance levels within 15 minutes after a reportable contingency. BAAL provides the real-time operating envelope, while DCS governs post-event recovery obligations.

• Reportable threshold: Loss of generation ≥ 80% of most severe single contingency
• Recovery timeline: ACE must return to zero or pre-disturbance value
• Relationship to BAAL: DCS recovery actions must respect BAAL limits

Ancillary service capacity held on synchronized resources that responds to AGC signals within seconds. BAAL compliance depends directly on sufficient regulation reserve being available to arrest ACE excursions before they breach the limit.

• Response time: Full output within 5 minutes
• Procurement: Based on historical ACE variability analysis
• Depletion risk: Inadequate reserves trigger BAAL violations during ramping periods