PRR - 1473

Value cannot be null. Parameter name: stream

Announcement for PRR - 1473

Description: Additional changes have been added - 7.1.3.1 regarding the enforced transmission constraints at initial release - 7.1.3.1.3 detail was added for data posting and API service - Appendix section N contains additional detail on market logic when dynamic regression is unavailable.
-By Fox, Jacob on Wednesday, December 14, 2022 9:08:46 AM

Announcement for PRR - 1473

Description: Additional change has been added to 7.1.3.1 for enforced transmission constraints at initial release
-By Fox, Jacob on Monday, January 23, 2023 10:12:19 AM

Recommendation Comment for PRR - 1473

Description: PacifiCorp appreciates the CAISO’s work on the improvements to the Flexible Ramping Product (FRP) and looks forward to the upcoming implementation. After recent conversations with CAISO staff on the FRP, PacifiCorp kindly asks the CAISO to consider adding language to clarify how resources’ eligibility to provide FRP may be affected by the deployment scenarios. The August 15, 2022 Tariff Amendment to Refine Flexible Ramping Product states on page 9, “The market optimization will make uncertainty awards to a resource only if its flexible ramping award is deliverable in the base case, in the case where the market calls on all upward flexible ramping product, and in the case where the market calls on all downward flexible ramping product.” This sentence indicates that a resource will only be awarded FRP if it is dispatchable in the base case and both deployment scenarios. It is PacifiCorp’s understanding that a resource can be awarded FRP Up if it is deployable only in the upward uncertainty deployment scenario, and a resource can be awarded FRP Down if it is deployable only in the downward uncertainty deployment scenario. While there may be language in other FRP documents that describes how resources’ eligibility is affected by the deployment scenarios, it is PacifiCorp’s opinion that clear language in the BPM would be best for all market participants. Furthermore, PacifiCorp asks the CAISO to clarify how FRU/FRD requirements are allocated to load, solar and wind resources. In the Draft Technical Description – Flexible Ramping Product Procurement and Deployment Scenarios in section 4.11 Flexible Ramp Deployment Scenarios, the CAISO states “The distribution of the FRU/FRD requirements in the ACPF solution is divided among load, solar and wind resources using allocation factors derived from historical data that reflect the relative contributions of these resource classes to the net demand forecast uncertainty.” This is consistent with PacifiCorp’s understanding of how the FRU/FRD requirement is distributed. However, also in section 4.11 Flexible Ramp Deployment Scenarios, the CAISO states “The distributions of these requirement components are to the solar and wind VERs in the respective BAA or BAA group pro rata on the available VER maximum capacity.” This statement conveys a different understanding as to how the FRU/FRD requirement is distributed to solar and wind resources. A pro rata distribution based on available VER maximum capacity does not seem to be the same as “relative contributions of these resource classes to the net demand forecast uncertainty”. It is PacifiCorp’s opinion that clear language in the BPM will be best for all market participants as it will not cause entities to come to different conclusions as to how FRU/FRD is distributed to load, solar and wind resources.
-By Vijay Singh (PacifiCorp) on Tuesday, January 24, 2023 3:22:18 PM

Response: The energy, upward flexible ramping capacity and downward flexible ramping capacity awards are co-optimized at the same time with the constraints of the base, upward flexible ramping deployment scenario and downward flexible ramping deployment scenario. The appendix should provide the information to the second question.
-By Fox, Jacob on Monday, March 27, 2023 9:28:55 AM

Announcement for PRR - 1473

Description: Additional changes have been added to the BPM in section 7.1.3 to addressing binding interval and sufficiency test timing. The incremental changes are highlighted in yellow.
-By Fox, Jacob on Friday, March 10, 2023 2:25:32 PM

Recommendation for PRR - 1473

Proposed Language:

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

Apparent Requirement: N/A
Priority: N/A
Action: Approve the BPM PRR as submitted
Effective Date: 02/01/2022
Other Actions: N/A

Final Decision for PRR - 1473

Final Decision: BPM changes approved as submitted.
Stakeholder Comment: One comment, no objections
Action: Adopt the recommendation as originally issued
Effective Date: 02/01/2023

RSS Feed for Proposed Revision Request - 1473

PRR - 1473

Announcement for PRR - 1473

Announcement for PRR - 1473

Recommendation Comment for PRR - 1473

Announcement for PRR - 1473

Recommendation for PRR - 1473

Final Decision for PRR - 1473