Change Request 2025-CRF-006

BPM 202 currently includes language in Section 9 regarding how to treat planned outages for resources that qualify to receive Forced Outages in the Operations Program. However, it does not provide instructions for other resource types, nor does it distinguish whether or not a planned outage was reported in the Forward Showing Submittal for that Binding Season. In cases where a resource is not on planned outage at the time of the FS Submittal, Participants may choose whether or not to report planned outages in their Forward Showing Submittals. To ensure accuracy, clear guidance is needed on how such resources should be reported into the Operations Program Sharing Calculation. This will ensure that Participants receive correct Sharing Calculation results and, accordingly, appropriate access to Operations Program capacity.

Edit the language in BPM 202 Section 9 to add clear instructions for submitting data into the Operations Program Sharing Calculation for resources on planned outage. 

BPM 202 Participant Sharing Calculation Inputs

9.    Planned Outages
In the FS Submittal, Participants are required to provide information on all Qualifying Resources that are currently out of service with a scheduled return date that falls during or after the Binding Season. Capacity associated with such resources is then deducted from Participants’ Portfolio QCC to ensure no credit is granted for such resources during the planned outage. 
The aggregate of any additional outages that are planned to occur during the Binding Season but have not yet begun at the FS Submittal deadline must be within the Participant’s remaining surplus or replaced with other supply. If a Participant takes a planned outage during the Binding Season, they are responsible for backfilling for the entirety of the reduction in capacity and should submit zero Forced Outage MWs for that resource during the period of the planned outage. 
A planned outage shall not justify a waiver of or exception to a Participant’s holdback or energy delivery obligations under the Tariff. It is the Participant’s responsibility to ensure necessary capacity is available to meet the Operations Program requirements, regardless of planned outage schedules or FS Submittal acceptance. In addition, planned outages MW amounts will not be included in the Forced Outages hourly data submitted in the Operations Program. Furthermore, if a planned outage that was included in the FS Submittal ends earlier in the month than expected and the resource becomes available, the Participant shall not include any Forced Outages MWs for that resource in the Operations.
 

BPM 202 Participant Sharing Calculation Inputs 

9. Planned Outages

In the FS Submittal, Participants are required to provide information on all Qualifying Resources that are currently out of service at the time of the FS Submittal deadline with a scheduled return date that falls during or after the Binding Season. Capacity associated with such resources is then deducted from Participants’ Portfolio QCC to ensure no credit is granted for such resources during the planned outage.

The aggregate of any additional outages that are planned to occur during the Binding Season but have not yet begun at the FS Submittal deadline must be within the Participant’s remaining surplus or replaced with other supply. If a Participant takes a planned outage during the Binding Season, they are responsible for backfilling for the entirety of the reduction in capacity and should submit zero Forced Outage MWs for that resource during the period of the planned outage.

A planned outage shall not justify a waiver of or exception to a Participant’s holdback or energy delivery obligations under the Tariff. It is the Participant’s responsibility to ensure necessary capacity is available to meet the Operations Program requirements, regardless of planned outage schedules or FS Submittal acceptance. 

If the planned outage of a resource was submitted in the FS Submittal, then:

• Resources that qualify for under- or over-performance in the Sharing Calculation: ROR, Wind, and Solar resources must be entered as zero MW in the ROR, Wind, and Solar data in the input files.
• Resources that qualify for Forced Outage in the Sharing Calculation: Thermal, Storage Hydro, and Energy Storage Resources must be entered as zero MW in the Thermal, Storage Hydro, and Energy Storage Resources data in the input files.

If the planned outage of a resource was NOT submitted in the FS Submittal, then:

• Resources that qualify for under- or over-performance in the Sharing Calculation: ROR, Wind, and Solar resources must be entered as the QCC value of the resource in the ROR, Wind, and Solar data in the input files.
• Resources that qualify for Forced Outage in the Sharing Calculation: Thermal, Storage Hydro, and Energy Storage Resources must be entered as zero MW in the Thermal, Storage Hydro, and Energy Storage Resources in the input files.

In addition, pPlanned outages MW amounts will not be included in the Forced Outages hourly data submitted in the Operations Program. Furthermore, if a planned outage that was included in the FS Submittal ends earlier in the month than expected and the resource becomes available, the Participant shall not include any Forced Outages MWs for that resource in the Operations Program.

A Participant may take planned outages during a Binding Season at its own risk. By ensuring the resources on planned outage are properly reflected in the Operations Program, the program prevents Participants from inappropriately accessing the capacity pool as a result of   taking planned outages during the Binding Season. This change will provide clearer instructions for submitting data into the Operations Program and improve consistency and fairness in the Sharing Calculation and Holdback Requirement process.