<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>RSS Feed for Proposed Revision Request - 1445</title><link>https://bpmcm.caiso.com/_vti_bin/BPM/BPMRssService.svc/PRRRss/1445</link><description>This is a RSS feed for the BPM Proposed Revision Request - 1445</description><managingEditor>BPM@caiso.com</managingEditor><category>BPM</category><item><link>https://bpmcm.caiso.com/</link><title>PRR - 1445</title><description>Value cannot be null.&#xD;
Parameter name: stream</description></item><item><guid isPermaLink="false">1445-Comm-2112</guid><link>https://bpmcm.caiso.com/pages/viewprr.aspx?IsDlg=1&amp;PRRID=1445</link><title>Initial Comment for PRR - 1445</title><description>&lt;span style='font-size:11px;color:gray'&gt; -By Aditya Chauhan (SCE) (Southern California Edison) on Tuesday, July 5, 2022 8:51:10 AM&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;</description><a10:updated>2022-07-05T08:51:10-07:00</a10:updated></item><item><guid isPermaLink="false">1445-Comm-2114</guid><link>https://bpmcm.caiso.com/pages/viewprr.aspx?IsDlg=1&amp;PRRID=1445</link><title>Initial Comment for PRR - 1445</title><description>&lt;b&gt;Description: &lt;/b&gt;Q.  Without the ability to use “qualifying contractual limitations” as criteria for use limitations, what should PDR units utilize going forward to model their use limitations? Does the CAISO recognize PDR contract limits as “design considerations” or as “environmental restrictions”?

A.  Assuming that the appropriate documentation is submitted, PDRs can qualify for use limitations under the “design considerations” type. As noted in section 2.1.15.1.6 of the BPM for Market Operations, PDRs “… have design limitations due to programmatic limitations that refer to the maximum events or hours per a deliverability period for which customers are expected to be willing to curtail or deploy state of charge when called upon.” This designation was discussed and concluded upon in the Commitment Costs Enhancement – Phase 3 (CCE3) initiative and was carried into the BPMs at the implementation of CCE3 in 2019. 

Q. The CAISO should explain the rationale behind the proposed change and the reason of proposing rules different than CAISO Tariff.

A.  There is no difference between the requirements from the CAISO Tariff and the clarifications of the tariff provided in the BPM for Market Operations. While Tariff section 30.4.6.1.1 does enumerate qualifying contractual limitations as an acceptable use limitation, it then goes on to explain that these limitations have a sunset date of: “Effective April 1, 2022, no contractual limitations will constitute qualifying contractual limitations that satisfy the requirements of this Section.” Thus, through this PRR, the CAISO is updating the BPMs to mirror the requirements of the Tariff.

--- Kevin Head  CAISO Sr. Market Engineering Specialist&lt;br /&gt;&lt;span style='font-size:11px;color:gray'&gt; -By Martin, Michael on Wednesday, July 6, 2022 3:56:17 PM&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;</description><a10:updated>2022-07-06T15:56:17-07:00</a10:updated></item><item><guid isPermaLink="false">1445-Recomm-1476</guid><link>https://bpmcm.caiso.com/pages/viewprr.aspx?IsDlg=1&amp;PRRID=1445</link><title>Recommendation for PRR - 1445</title><description>&lt;b&gt;Proposed Language: &lt;/b&gt;&lt;div class="ExternalClass8634B2E4DCAA4A97BC6964BABF634FB0"&gt;&lt;p&gt;​The&#xD;
ISO proposes no modified BPM language beyond that proposed in the BPM PRR.&lt;/p&gt;&lt;/div&gt;&lt;br /&gt;&lt;b&gt;Apparent Requirement: &lt;/b&gt;NA&lt;br /&gt;&lt;b&gt;Priority: &lt;/b&gt;NA&lt;br /&gt;&lt;b&gt;Action: &lt;/b&gt;Approve the BPM PRR as submitted&lt;br /&gt;&lt;b&gt;Effective Date: &lt;/b&gt;&lt;br /&gt;&lt;b&gt;Other Actions: &lt;/b&gt;A comment was received by SCE and was answered. &lt;br /&gt;</description><a10:updated>2022-07-29T08:18:21-07:00</a10:updated></item><item><guid isPermaLink="false">1445-FD-1397</guid><link>https://bpmcm.caiso.com/pages/viewprr.aspx?IsDlg=1&amp;PRRID=1445</link><title>Final Decision for PRR - 1445</title><description>&lt;b&gt;Final Decision: &lt;/b&gt;Proceed with original&lt;br /&gt;&lt;b&gt;Stakeholder Comment: &lt;/b&gt;Two comments addressed during initial phase&lt;br /&gt;&lt;b&gt;Action: &lt;/b&gt;Adopt the recommendation as originally issued&lt;br /&gt;&lt;b&gt;Effective Date: &lt;/b&gt;09/15/2022&lt;br /&gt;</description><a10:updated>2022-08-24T15:07:59-07:00</a10:updated></item></channel></rss>