​​​

Proposed Revision Request Detail Help
PRR Life Cycle*****Stakeholder Meeting on Recommendation****
PRR Details
PRR #
1691
Title Adding references back to market operations BPM on circular scheduling
Date Submitted 7/24/2026 12:23 PM
PRR Category A
Priority Normal
Owner Martin, Michael (CAISO)
Status Stakeholder Meeting on Recommendation
Status End Date 9/16/2026 11:59 PM
Related BPM Market Instruments
BPM Section 3.4.3 Circular Scheduling  
RSS Subscribe
Existing Language

​See Attached

Proposed Language

​See Attached​

Reason For Revision

​Adds references back to ​the Market Operations BPM sections 8.4.4 and Appendix Attachment H  

Click here to view the Recommendation Details for this PRR
BPM PRR Submitter

Martin, Michael (CAISO)
Modified BPM language proposed by the PBM Chnage Management Coordinator

​Approve the BPM PRR as submitted

Identification of the authorship of comments

Provided detailed response to questions attached to this PRR
Action

Approve the BPM PRR as submitted

Statement of apparent requirements of the BPM PRR

Priority and rank for any BPM PRR requiring a CAISO system change

Proposed effective date(s) of the BPM PRR

Other recommended actions

Announcements
No Announcements has been posted for this PRR.
Impact Analysis
PRR 1691 Impact Analysis Form.doc    
Notes:
Initial Comments
PRR 1691 - Response to 1690.docx    
*Please note: Because this PRR is closely linked to PRR 1690, the posted response will also be included in this PRR for reference.


PRR 1690 covers a narrow and well-defined scenario – moving power between non-contiguous portions of the same balancing authority area.  The PRR explains there is operational benefit from having such transactions reported on separate eTags.  Such schedules also do not pose the sort of operational and market risks as schedules FERC has deemed to be circular schedules in prior instances.  The CAISO understands PG&E’s concern that a market participant could cite the language from this PRR to justify breaking up the legs of a circular schedule into separate transactions and evade the impact of the settlement rule.  The CAISO addressed this concern when it proposed the circular scheduling settlement rule in 2012.  The CAISO explained that if “it believes that a market participant intentionally sought to circumvent the proposed settlement rules by submitting multiple e-Tags that “chop-up” the path of what is essentially a single transaction so as to avoid application of the proposed settlement rule, then DMM would consider referring that conduct as either potentially manipulative or involving the submission of false information.  The same would apply if there were reason to believe that a single scheduling coordinator sought to avoid the settlement rule by including a third party on the e-Tag where there was no legitimate arm’s-length transaction between the two parties.” (CAISO transmittal letter, p.15.  also review CAISO answer to protest and comments, pp.8-10).  The CAISO has been monitoring, and will continue to monitor, for transactions that seek to circumvent or evade the settlement rule.  As relates to PRR 1690,  this monitoring would include the use of separate eTags for a schedule sourcing and sinking in the same balancing authority area, unless the schedule was used to move power between non-contiguous portions of the same balancing authority area.

~Michael Martin
8/28/2026 10:43 AM
Logged By - Williamson-Duffney, Joseph (CAISO)
This PRR is related to PRR 1690 and should be considered in parallel.
PacifiCorp has submitted an Initial Comment on PRR 1691 expressing its understanding that the circular scheduling rule only applies to Scheduling Coordinators in the CAISO BAA, and the CAISO’s response agrees with that view.  The Six Cities do not agree that the circular scheduling settlement rule should apply only to Scheduling Coordinators in the CAISO BAA.  The circular scheduling settlement rule arose from determinations by the FERC following the 2000-2001 Energy Crisis that circular scheduling, as described in Attachment H, violates market conduct rules.  In an integrated market, there is no apparent reason why market conduct rules should be different for participating BAAs.  Appropriately defined exceptions for transactions between non-contiguous portions of a BAA should apply to all BAAs under comparable circumstances, but there should be no categorical limitation of the circular scheduling rule to CAISO Scheduling Coordinators alone.
8/18/2026 3:35 PM
Logged By - bblair@thompsoncoburn.com (CAISO)
Thanks for the comment and I completely agree with your recommendation.  A modification will be posted.
8/10/2026 9:40 AM
Logged By - Martin, Michael (CAISO)
PacifiCorp appreciates the opportunity to provide comments on PRR 1691. PacifiCorp requests the CAISO confirm that this PRR only affects CAISO scheduling coordinators. PacifiCorp's understanding of the Circular Schedule Rule, based on reading the Market Operations Business Practice Manual, is that the rule only applies to CAISO scheduling coordinators. If PacifiCorp's understanding is correct, PacifiCorp suggests adding language to the BPMs to specify that the Circular Scheduling rule only applies to CAISO scheduling coordinators.
8/5/2026 11:59 AM
Logged By - Vijay Singh (PacifiCorp)
Recommendation Comments
As noted previously, PRRs 1690 and 1691 are related and should be considered in parallel.  Both the Six Cities and PG&E submitted Initial Comments raising questions about the language proposed for PRR 1690 and, in the Six Cities’ Initial Comments, questioning CAISO’s response to the PacifiCorp Initial Comment on PRR 1691.  While the CAISO’s response to the Initial Comments suggests that the CAISO plans to continue enforcing the rule against circular scheduling, it does not expressly address the questions PG&E raised, and it does not clarify the meaning of the earlier response to PacifiCorp’s Initial Comment.  The Six Cities request express clarification that the CAISO will apply the rule against circular scheduling consistently for all BAAs participating in the Extended Day-Ahead Market, subject to any appropriately tailored exceptions explicitly detailed in the BPM.
9/16/2026 2:48 PM
Logged By - bblair@thompsoncoburn.com (CAISO)
Attachments