RSS Feed for Proposed Revision Request - 1705

PRR - 1705

Value cannot be null. Parameter name: stream

Impact Analysis for PRR - 1705

-By Williamson-Duffney, Joseph on Friday, August 28, 2026 3:27:54 PM

Initial Comment for PRR - 1705

Description: BPA's primary concern centers on the ambiguous scope and system burden associated with the requirement for terminating entities to "retain functionality needed for ongoing EIM Entity Scheduling Coordinator obligations." Ambiguity of "Ongoing Obligations" & Software Lifecycle: • Issue: Post-termination, maintaining specialized WEIM interfaces, telemetry feeds, dynamic scheduling links, and settlement platforms places a substantial financial and administrative burden on an entity transitioning out of the market. • Request: CAISO must explicitly delineate which specific EIM Entity Scheduling Coordinator (EESC) obligations persist beyond the effective termination date (e.g., historical settlement recalculations vs. active scheduling/telemetry) and specify the duration for which these systems must remain functional.
-By sleaton@bpa.gov on Wednesday, September 16, 2026 1:23:42 PM

Response: The ISO's response to your questions has been posted in the document titled: PRR 1705 - ISO response to initial comments.
-By Madrigal, Radha on Monday, September 21, 2026 4:37:08 PM

Initial Comment for PRR - 1705

Description: Salt River Project Agricultural Improvement and Power District (SRP) is engaged in ongoing discussions with CAISO staff regarding terminating WEIM participation. SRP appreciates the CAISO providing additional details for WEIM termination and considers it critical that any BPM changes related to WEIM termination be aligned with decisions made during our discussions with CAISO staff. For the CAISO’s preparation responsibilities, SRP has the following questions and requests that the CAISO add details to the language: • How much flexibility will the CAISO provide in determining the date to disable the Real-Time Market for the terminating Entity? What are the parameters influencing that flexibility? Is there a limit to how far in advance of the WEIM Agreement termination date the CAISO would make this determination? To what degree does the CAISO’s network modeling efforts impact this flexibility? If it does, then it would be good to provide clarity in that regard. • How will the CAISO determine the disabling effective date if multiple entities desire to terminate but do not align on the timing? At what frequency would the CAISO schedule disabling effective dates (e.g., monthly, bi-annually)? SRP requests the CAISO provide additional detail on the following terminating WEIM Entity responsibilities: 1. Participating in planning meetings with CAISO and other WEIM Entities[TED1.1][MLM1.2] 2. Updating systems to retain the functionality needed for ongoing EIM Entity Scheduling Coordinator obligations[TED2.1] 3. Communicating changes to the configuration or modeling of resources that may be impactful to WEIM Entities 4. Participating in the planning and execution of testing with CAISO and Real-Time Market participants For responsibility #1, please be more descriptive in the frequency, attendees, and time requirements for the planning meetings that will need to be attended by each entity, so we can be intentional in selecting a representative(s) to be in attendance. For responsibility #2, the systems for the EIM Entity Scheduling Coordinator (EESC) seem to focus on transmission operations and scheduling, rather than the merchant functions. Can the CAISO be more clear as to which systems / EESC functions you are seeking updates to? This will enable EESCs to ensure the right party is selected. For responsibility #3, is that specific to the time the terminating entity remains in WEIM? If so, SRP requests the language specify that. For responsibility #4, SRP is unclear what testing would mean for the terminating entity. This responsibility seems more applicable to a WEIM Entity that would be affected by a terminating Entity. Please provide more information on expectations for the terminating entity.
-By marcie.martin@srpnet.com on Wednesday, September 16, 2026 3:10:09 PM

Response: The ISO's response to your questions has been posted in the document titled: PRR 1705 - ISO response to initial comments.
-By Madrigal, Radha on Monday, September 21, 2026 4:36:47 PM

Announcement for PRR - 1705

Description: Please see attached CAISO responses to questions
-By Martin, Michael on Monday, September 28, 2026 2:24:15 PM

Recommendation for PRR - 1705

Proposed Language:

Approve the BPM PRR as submitted

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