RSS Feed for Proposed Revision Request - 1699

PRR - 1699

Value cannot be null. Parameter name: stream

Impact Analysis for PRR - 1699

-By Williamson-Duffney, Joseph on Friday, August 28, 2026 7:31:43 AM

Initial Comment for PRR - 1699

Description: Can CAISO provide more explanation as to why it is proposing to treat transmission reservations for Imbalance Reserve awards across the interties differently than other Imbalance Reserve awards?
-By alan.meck@pge.com on Wednesday, September 16, 2026 9:06:42 AM

Response: ISO response provided by Michael Martin: Here is the technical reason of why we fashioned intertie constraints in such a way: For interties, the full IRU and IRD capacity is reserved to be able to deploy if uncertainty is materialized. For the import limit: For energy, capacity is reserved for import and export system resources (allowing cancelation). For import system resources, capacity is reserved for AS in the upward direction, and imbalance reserve up. For export system resources, capacity is reserved for imbalance reserve down. Exporting IRD implies that the exporting EDAM BAA would need to receive an import of energy of the same amount of the IRD. For the export limit: For energy, capacity is reserved for import and export system resources (allowing cancelation). For import system resources, capacity is reserved for AS in the downward direction, and imbalance reserve down. For export system resources, capacity is reserved for imbalance reserve up. Exporting IRU implies that the exporting EDAM BAA would need to increase an energy export of the same amount of the IRU.
-By Madrigal, Radha on Monday, September 21, 2026 8:34:44 AM

Announcement for PRR - 1699

Description: See additional comment on reasoning for design.
-By Martin, Michael on Monday, September 28, 2026 8:14:21 AM

Announcement for PRR - 1699

Description: Intertie scheduling limits constrain only import/export and transfer schedules at the associated interties. Energy schedules and capacity awards for supply and demand resources inside a BAA are not constrained by intertie scheduling limits. The intertie/transfer capacity is reserved in the base scenario for all energy schedules and capacity awards for the relevant intertie resources (transmission profile), hence these constraints need not be enforced in the IRU/IRD deployment scenarios.
-By Martin, Michael on Monday, September 28, 2026 8:17:26 AM

Announcement for PRR - 1699

Description: 1. An intertie resource receiving IR must hold transmission covering its day-ahead energy schedule plus its full IR award. That requirement reflects that delivery to the CAISO boundary relies on transmission outside CAISO's control, which CAISO cannot redispatch, so transmission capability for the full award is the assurance that the award can be delivered. By applying the full IR award to the corresponding ITC/ISL constraint, the market gives matching treatment on the CAISO side of the boundary, so the award is deliverable on both sides of the interface. 2. The deployment factor involves a policy choice about how much tail deliverability risk to accept. At an intertie, this risk has more severe consequences than for internal constraints. The market can relieve internal transmission congestion by re-dispatching units but a binding intertie limit is different because once the intertie is full, re-dispatching units cannot create more import capability. The market can reduce another import schedule or add an export schedule as counterflow, but neither would bring additional energy into the BAA. Once an intertie reaches its limit, every new MW you add forces an existing MW out, so the net change is zero. So if an intertie IR award must deliver energy when needed, the market must reserve 100% of the required transmission capability in advance. 3. CAISO has long reserved full intertie scheduling capability for AS imports, so this applies a similar precedent.
-By Martin, Michael on Thursday, October 1, 2026 8:14:56 AM

Recommendation for PRR - 1699

Proposed Language:

Approve BPM as Submitted

Action: Approve the BPM PRR as submitted
Effective Date: 01/01/0001