BAL-001-2 – Real Power Balancing Control Performance

Purpose
To control Interconnection frequency within defined limits.

Applicability
4.1. Balancing Authority

4.1.1 A Balancing Authority receiving Overlap Regulation Service is not subject to Control Performance Standard 1 (CPS1) or Balancing Authority ACE Limit (BAAL) compliance evaluation

4.1.2 A Balancing Authority that is a member of a Regulation 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 the governing rules for the Regulation Reserve Sharing Group

4.2. Regulation Reserve Sharing Group

Effective Date
First day of the first calendar quarter that is twelve months beyond the date that this standard is approved by applicable regulatory authorities, or in those jurisdictions where regulatory approval is not required, the standard becomes effective the first day of the first calendar quarter that is twelve months beyond the date this standard is approved by the NERC Board of Trustees, or as otherwise made effective pursuant to the laws applicable to such ERO governmental authorities.

Requirements
R1. The Responsible Entity shall operate such that the Control Performance Standard 1  (CPS1), calculated in accordance with Attachment 1, is greater than or equal to 100 percent for the applicable Interconnection in which it operates for each preceding 12 consecutive calendar month period, evaluated monthly. [Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]

R2. Each Balancing Authority shall operate such that its clock-minute average of Reporting ACE does not exceed its clock-minute Balancing Authority ACE Limit (BAAL) for more than 30 consecutive clock-minutes, calculated in accordance with Attachment 2, for the applicable Interconnection in which the Balancing Authority operates.[Violation Risk Factor: Medium] [Time Horizon: Real-time Operations]

Measures
M1. The Responsible Entity shall provide evidence, upon request, such as dated calculation output from spreadsheets, system logs, software programs, or other evidence (either in hard copy or electronic format) to demonstrate compliance with Requirement R1.

M2. Each Balancing Authority shall provide evidence, upon request, such as dated calculation output from spreadsheets, system logs, software programs, or other evidence (either in hard copy or electronic format) to demonstrate compliance with Requirement R2,

Compliance Monitoring Process

Compliance Enforcement Authority

As defined in the NERC Rules of Procedure, “Compliance Enforcement Authority” means NERC or the Regional Entity in their respective roles of monitoring and enforcing compliance with the NERC Reliability Standards.

Data Retention

The following evidence retention periods identify the period of time an entity is required to retain specific evidence to demonstrate compliance. For instances where the evidence retention period specified below is shorter than the time since the last audit, the Compliance Enforcement Authority may ask an entity to provide other evidence to show that it was compliant for the full-time period since the last audit.

The Responsible Entity shall retain data or evidence to show compliance for the current year, plus three previous calendar years unless, directed by its Compliance Enforcement Authority, to retain specific evidence for a longer period of time as part of an investigation. Data required for the calculation of Regulation Reserve Sharing Group Reporting Ace, or Reporting ACE, CPS1, and BAAL shall be retained in digital format at the same scan rate at which the Reporting ACE is calculated for the current year, plus three previous calendar years.

If a Responsible Entity is found noncompliant, it shall keep information related to the noncompliance until found compliant, or for the time period specified above, whichever is longer.

The Compliance Enforcement Authority shall keep the last audit records and all subsequent requested and submitted records.

Compliance Monitoring Assessment Processes 

Compliance Audits

Self-Certifications

Spot Checking

Compliance Investigation

Self-Reporting

Complaints

Attachment 1

Equations Supporting Requirement R1 and Measure 1

CPS1 is calculated as follows:

CPS1 = (2 – CF) * 100%

The frequency-related compliance factor (CF), is a ratio of the accumulating clock-minute compliance parameters for the most recent preceding 12 consecutive calendar months, divided by the square of the target frequency bound:

https://nercipedia.com/wp-content/uploads/sites/2/2016/12/BAL-001-2-Fig2-CF-Equation.png

Where ε1I is the constant derived from a targeted frequency bound for each Interconnection as follows:

 

The rating index CF12-month  is derived from the most recent preceding 12 consecutive calendar months of data.  The accumulating clock-minute compliance parameters are derived from the one-minute averages of Reporting ACE, Frequency Error, and Frequency Bias Settings. A clock-minute average is the average of the reporting Balancing Authority’s valid measured variable (i.e., for Reporting ACE (RACE) and for Frequency Error) for each sampling cycle during a given clock-minute.

https://nercipedia.com/wp-content/uploads/sites/2/2016/12/BAL-001-2-Fig4-Reporting-ACE.png

The Balancing Authority’s clock-minute compliance factor (CF clock-minute ) calculation is:

https://nercipedia.com/wp-content/uploads/sites/2/2016/12/BAL-001-2-Fig5-CF-Clock-Minute.png

Normally, 60 clock-minute averages of the reporting Balancing Authority’s Reporting ACE and Frequency Error will be used to compute the hourly average compliance factor (CFclock-hour)

https://nercipedia.com/wp-content/uploads/sites/2/2016/12/BAL-001-2-Fig6-CF-Clock-Hour.png

The reporting Balancing Authority shall be able to recalculate and store each of the respective clock-hour averages (CFM clock-hour average-month ) and the data samples for each 24 hour period (one for each clock-hour; i.e., hour ending (HE) 0100, HE 0200, …, HE 2400).   To calculate the monthly compliance factor (CFmonth):

https://nercipedia.com/wp-content/uploads/sites/2/2016/12/BAL-001-2-Fig7-CF-Clock-Avg-Month.png

To calculate the 12-month compliance factor (CF 12 month)https://nercipedia.com/wp-content/uploads/sites/2/2016/12/BAL-001-2-Fig8-CF-12-month.png

To ensure that the average Reporting ACE and Frequency Error calculated for any one-minute interval is representative of that time interval, it is necessary that at least 50  percent of both the Reporting ACE and Frequency Error sample data during the one-minute interval is valid.  If the recording of Reporting ACE or Frequency Error is interrupted  such that less than 50 percent of the one-minute sample period data is available or valid,  then that one-minute interval is excluded from the CPS1 calculation.     A Balancing Authority providing Overlap Regulation Service to another Balancing Authority  calculates its CPS1 performance after combining its Reporting ACE and Frequency Bias Settings with the Reporting ACE and Frequency Bias Settings of the Balancing Authority receiving the Regulation Service.

 

Attachment 2

Equations Supporting Requirement R2 and Measure M2

When actual frequency is equal to Scheduled Frequency, BAALHigh  and BAALLow  do not apply. When actual frequency is less than Scheduled Frequency, BAALHigh  does not apply, and BAALLow  is calculated as:

https://nercipedia.com/wp-content/uploads/sites/2/2016/12/BAL-001-2-Fig9-BAAL-low.png

When actual frequency is greater than Scheduled Frequency, BAALLow does not apply and the BAALHigh  is calculated as:

https://nercipedia.com/wp-content/uploads/sites/2/2016/12/BAL-001-2-Fig10-BAAL-high.pngWhere:

BAALLow is the Low Balancing Authority ACE Limit (MW)

BAALHigh is the High Balancing Authority ACE Limit (MW)

10 is a constant to convert the Frequency Bias Setting from MW/0.1 Hz to MW/Hz

Bi  is the Frequency Bias Setting for a Balancing Authority (expressed as MW/0.1 Hz)

FA  is the measured frequency in Hz.

FS  is the scheduled frequency in Hz.

 FTLLow  is the Low Frequency Trigger Limit (calculated as FS  – 3ε1I  Hz)

FTLHigh  is the High Frequency Trigger Limit (calculated as FS  + 3ε1I  Hz)

Where ε1I  is the constant derived from a targeted frequency bound for each Interconnection as follows:

To ensure that the average actual frequency calculated for any one-minute interval is representative of that time interval, it is necessary that at least 50% of the actual frequency sample data during that one-minute interval is valid.  If the recording of actual frequency is interrupted such that less than 50 percent of the one-minute sample period data is available or valid, then that one-minute interval is excluded from the BAAL calculation and the 30-minute clock would be reset to zero.

A Balancing Authority providing Overlap Regulation Service to another Balancing Authority calculates its BAAL performance after combining its Frequency Bias Setting with the Frequency Bias Setting of the Balancing Authority receiving Overlap Regulation Service.


Top