Control Performance Standard 2 (CPS2) is a NERC reliability metric requiring a balancing authority to maintain its average Area Control Error (ACE) within a specific threshold, known as L10, for at least 90% of the 10-minute clock-hour periods in a month. It functions as a containment boundary, ensuring that an entity's unscheduled power flows do not persistently stress the transmission system or shift regulation burden onto neighboring areas.
Glossary
Control Performance Standard 2 (CPS2)

What is Control Performance Standard 2 (CPS2)?
A NERC reliability metric that limits a balancing authority's average Area Control Error over discrete 10-minute periods to prevent unscheduled power flows from degrading interconnection stability.
The L10 limit is calculated annually based on a balancing authority's historical ACE variability and the interconnection's overall frequency sensitivity. A violation occurs when the 10-minute average ACE exceeds this statistically derived boundary. While Control Performance Standard 1 (CPS1) measures long-term frequency support, CPS2 provides the short-term operational guardrails that prevent excessive interchange volatility.
Key Characteristics of CPS2
Control Performance Standard 2 (CPS2) is a NERC reliability metric that constrains a balancing authority's average Area Control Error (ACE) within a specific threshold, known as L10, for at least 90% of the 10-minute clock-hour periods in a month.
The L10 Band
The L10 is a bounding threshold calculated for each balancing authority based on its historical Frequency Bias Coefficient and the interconnection's overall frequency response characteristic. It defines a permissible ACE envelope. The standard requires that the average ACE for each 10-minute period must not exceed this L10 limit for more than 10% of the periods in a calendar month. This ensures that sustained imbalances are bounded and do not accumulate over time.
90% Compliance Requirement
CPS2 mandates a strict 90% minimum compliance ratio. For every clock-hour, the balancing authority's ACE is averaged over six consecutive 10-minute periods. Each period is a pass/fail test against the L10 threshold. At the end of the month, the ratio of compliant periods to total periods must be at least 0.90. Falling below this threshold constitutes a violation and requires a corrective action plan to be filed with the regional reliability coordinator.
Complementary Role to CPS1
While CPS1 measures the statistical correlation between a balancing authority's ACE and the interconnection's frequency error over a rolling 12-month average, CPS2 acts as a hard boundary on sustained ACE magnitude. CPS1 can be satisfied even with large, short-lived ACE swings if they help frequency. CPS2 prevents these swings from persisting. Together, they ensure that ACE is both frequency-supportive (CPS1) and bounded in duration (CPS2).
10-Minute Averaging Window
The fundamental measurement unit for CPS2 is the 10-minute clock-hour period. The balancing authority's ACE is sampled every few seconds by the Automatic Generation Control (AGC) system, and a simple arithmetic average is calculated for each non-overlapping 10-minute block. This averaging window is designed to filter out the high-frequency noise of instantaneous ACE fluctuations and focus on the underlying, sustained imbalance trend that poses a greater risk to interconnection reliability.
Violation and Mitigation
A CPS2 violation occurs when the monthly compliance ratio drops below 90%. Upon violation, the balancing authority must perform a root cause analysis and submit a mitigation plan to its Regional Reliability Coordinator. Common causes include:
- Inadequate Regulation Reserve procurement
- Poor Renewable Generation Forecasting leading to large net load ramps
- Failure of a Dynamic Schedule or pseudo-tie resource Persistent violations can lead to financial penalties and increased regulatory oversight.
Relationship to BAAL
The Balancing Authority ACE Limit (BAAL) is a real-time operational overlay that works in conjunction with CPS2. While CPS2 is a retrospective monthly metric, BAAL provides a real-time, dynamic limit that, if exceeded, requires the operator to take immediate corrective action. BAAL is designed to prevent a balancing authority's ACE from contributing to a frequency excursion beyond a predefined limit, acting as a safety net between the long-term statistical measure of CPS1 and the bounding constraint of CPS2.
CPS2 vs. CPS1 vs. BAAL
Comparative analysis of the three primary NERC reliability standards governing balancing authority Area Control Error compliance: statistical long-term variability (CPS1), 10-minute boundary containment (CPS2), and real-time magnitude limiting (BAAL).
| Feature | CPS2 | CPS1 | BAAL |
|---|---|---|---|
Primary Objective | Limit ACE magnitude within L10 threshold for 90% of 10-min periods | Limit ACE variability correlated with frequency error over 12 months | Prevent ACE from exceeding calculated limit during sustained frequency deviations |
Compliance Period | Calendar month | Rolling 12-month period | Real-time, continuous |
Measurement Interval | 10-minute clock-hour periods | 1-minute average values | 30-second rolling average |
Frequency Dependency | |||
Pass/Fail Threshold | ≥ 90% of periods within L10 | CPS1 ≥ 100% | ACE magnitude ≤ BAAL limit |
Violation Consequence | Monthly non-compliance report to NERC | Rolling 12-month score below 100% triggers audit | Immediate operator corrective action required |
L10 Calculation Basis | Statistical envelope derived from frequency bias and interconnection characteristics | Dynamic limit derived from actual frequency deviation and frequency bias | |
Primary Mitigation Strategy | Reduce ACE magnitude through regulation reserve deployment | Reduce ACE variability through tighter AGC tuning | Reduce ACE magnitude through manual intervention or reserve activation |
Frequently Asked Questions
Clear answers to the most common questions about Control Performance Standard 2, its calculation, and its role in maintaining interconnection reliability.
Control Performance Standard 2 (CPS2) is a NERC reliability metric that requires a balancing authority to maintain its average Area Control Error (ACE) within a specific threshold, known as L10, for at least 90% of the 10-minute clock-hour periods in a month. CPS2 works by dividing each hour into six contiguous 10-minute periods. For each period, the balancing authority calculates the average ACE. If this average ACE magnitude exceeds L10, the period is considered a violation. To be compliant, a balancing authority must have no more than 14 violations across the roughly 4,320 periods in a 30-day month. This standard ensures that no single balancing authority's persistent control error significantly degrades the reliability of the wider interconnection.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Explore the foundational metrics, control mechanisms, and operational standards that interact with CPS2 to maintain bulk electric system reliability.
Area Control Error (ACE)
The raw input signal for CPS2 evaluation. ACE is the instantaneous algebraic sum of:
- Net Interchange Deviation: Actual tie-line flow minus scheduled flow.
- Frequency Bias Obligation: 10 × B × (Actual Frequency - Scheduled Frequency), where B is the Frequency Bias Coefficient in MW/0.1 Hz.
CPS2 requires that the 10-minute rolling average of ACE remains within the L10 envelope for at least 90% of clock-hour periods.
L10 Threshold
The specific MW boundary at the heart of CPS2 compliance. L10 is calculated as:
L10 = 1.65 × ε10 × √(10 × B × Bnet)
- ε10: A constant derived from the interconnection's historical frequency error.
- B: The balancing authority's frequency bias coefficient.
- Bnet: The interconnection's total frequency bias.
This statistical envelope ensures that ACE excursions are bounded to a level that limits unscheduled power flows.
Automatic Generation Control (AGC)
The closed-loop control system that executes the corrective actions needed to meet CPS2. AGC processes the ACE signal every 2-6 seconds and dispatches regulation commands to generating units.
- Filtering: AGC often applies deadbands to avoid chasing noise.
- Allocation: Participation factors distribute the regulation requirement among units.
- Constraint Enforcement: Ramp rate limiters protect equipment from thermal stress.
CPS2 compliance is unattainable without a properly tuned AGC system.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us