PRR - 1130

Value cannot be null. Parameter name: stream

Impact Analysis for PRR - 1130

-By Peacock, Bonnie on Monday, January 28, 2019 9:05:00 AM

Initial Comment for PRR - 1130

Description: SDG&E supports the proposed changes, but also recommends that the CAISO take this opportunity to correct what we view as another flaw in the No Pay process. On occasion, we’ve seen fractional dispatches that are categorized in expected energy as “spinning Reserve” (Non-Spinning reserve as well) triggering Spin/NSpin no pay. In several cases that we’ve brought to the CAISO’s attention, a generator sold spin capacity and then expected energy showed Spinning Reserve dispatches of <.1MWs for the hour, which translates into five minute interval spin dispatches of less than a 1/100th of a MW. When the no pay logic evaluates the generators performance in relation to dispatch quantities, there are no thresholds used other than considering whether a unit delivered at least 90% of the Spin/Nspin dispatch. As a result, a unit that is following dispatch and would be considered as “accurately” responding when looking at expected energy compared to the meter overall, is penalized for deviations that are so small that it’s virtually impossible for the unit to monitor and comply. (The CAISO’s ADS only issues Dispatch Operating Instructions (DOTs) out to two decimal places). It’s not clear why the ISO is issuing fractional spinning reserve dispatches or why expected energy is showing these fractional quantities, but it would appear there is a problem occurring in an upstream system or with the creation of the expected energy data itself. In one of the examples we’ve provided in the past, the unit was deviating by .5% from expected energy and yet had the Ancillary Service payment rescinded for not delivering at least 90% of a spin dispatch of .007 MWs. The fractional spin dispatch in this case caused unjustified rescissions for the unit that was, in reality, following their EE when looking at the interval as a whole. We suggest that the ISO update the expected energy logic to prevent these types of dispatches from showing up in the data and flowing through to the No Pay calculations. If this is not possible, some threshold should be included in the calculation to prevent these dispatches from causing unjustified capacity payment rescissions. We do not view this as a tariff or BPM change, but rather a correction or a systematic data problem. We would be happy to provide trade dates, resource ID’s, and hours in which we’ve seen this problem occur.
-By Matt Richardson (SDGE) on Monday, February 11, 2019 2:11:16 PM

Response: Thank you for providing this request. Please work with your Customer Services Rep to open a CIDI ticket to allow the ISO to review and provide a formal response.
-By Peacock, Bonnie on Thursday, February 14, 2019 9:27:16 AM

Announcement for PRR - 1130

Description: Effective date revised to 5/1/2019 as a result of an updated deployment schedule.
-By Peacock, Bonnie on Tuesday, February 12, 2019 2:42:30 PM

Recommendation for PRR - 1130

Proposed Language:

The ISO proposes no modified BPM language beyond that proposed in the BPM PRR.

Apparent Requirement: This BPM PRR contains basic language changes
Priority: There are system changes associated with this PRR. The system changes are planned for implementation on 4/24/2019 on a normal basis.
Action: Approve the BPM PRR as submitted
Effective Date:
Other Actions: The ISO does not recommend any other actions on this BPM PRR.

Final Decision for PRR - 1130