Common use of XXXX Elections Clause in Contracts

XXXX Elections. The amount of XXXX requested by a Developer shall be stated in MW of Installed Capacity (“ICAP”), and cannot exceed the nameplate capacity of the Developer’s Large Facility; provided however, if the Large Facility is a BTM:NG Resource, its requested XXXX cannot exceed its Net ICAP. When a Developer elects XXXX, the ISO will evaluate the deliverability of the Large Facility by applying the test methodology described in Section 25.7 of Attachment S to the ISO OATT. The ISO will apply this test methodology to identify the System Deliverability Upgrades, if any, needed to make the Large Facility deliverable and will also identify the MW of Installed Capacity, if any, that are deliverable from the Large Facility with no System Deliverability Upgrades. A Large Facility electing XXXX will be able to become a qualified Installed Capacity Supplier or receive Unforced Capacity Deliverability Rights to the extent of its deliverable capacity, once it has funded or committed to fund any required System Deliverability Upgrades in accordance with the relevant provisions of Attachment S to the ISO OATT. A Developer qualifying for XXXX will have two XXXX values: one for the summer capability period and one for the winter capability period. The XXXX value, in MW of Installed Capacity, for the summer capability period will be set using the deliverability test methodology and procedures described in Section 25.7 of Attachment S to the ISO OATT. The XXXX value for the winter capability period, also in MW of Installed Capacity, will be set in accordance with Section 25.7.6 of Attachment S to the ISO OATT.

XXXX Elections. The amount of XXXX requested by a Developer shall be stated in MW of Installed Capacity (“ICAP”), and cannot exceed the nameplate capacity permissible levels set forth in Section 25.8.1 of Attachment S to the Developer’s Large Facility; provided however, if the Large Facility is a BTM:NG Resource, its requested XXXX cannot exceed its Net ICAPISO OATT. When a Developer elects XXXX, the ISO will evaluate the deliverability of the Large Facility by applying the test methodology described in Section 25.7 of Attachment S to the ISO OATT. The ISO will apply this test methodology to identify the System Deliverability Upgrades, if any, needed to make the Large Facility deliverable at its requested XXXX MW level and will also identify the MW of Installed Capacity, if any, that are deliverable from the Large Facility with no System Deliverability Upgrades. A Large Facility electing XXXX will be able to become a qualified Installed Capacity Supplier or receive Unforced Capacity Deliverability Rights to the extent of its deliverable capacity, once it has funded or committed to fund any required System Deliverability Upgrades in accordance with the relevant provisions of Attachment S to the ISO OATT. A Developer qualifying for XXXX will have two XXXX values: one for the summer capability period and one for the winter capability period. The XXXX value, in MW of Installed Capacity, for the summer capability period will be set using the deliverability test methodology and procedures described in Section 25.7 of Attachment S to the ISO OATT. The XXXX value for the winter capability period, also in MW of Installed Capacity, will be set in accordance with Section 25.7.6 of Attachment S to the ISO OATT.

XXXX Elections. The When an Interconnection Customer requests XXXX, the amount of XXXX requested by a Developer shall be stated in MW of Installed Capacity (“ICAP”), and cannot exceed the nameplate capacity of the Developer’s Large Facility; provided however, if the Large Facility is a BTM:NG Resource, its requested XXXX cannot exceed its Net ICAPpermissible levels set forth in Section 40.5.6.5. When a Developer an Interconnection Customer elects XXXX, the ISO will evaluate the deliverability of the Large Facility by applying the test methodology described in Section 25.7 of Attachment S to 40.13; provided, however, requests for XXXX for a Facility 2 MW or smaller or for an increase in XXXX permitted by Section 40.5.6.6 will not evaluated for deliverability under the ISO OATTNYISO Deliverability Interconnection Standard. The ISO will apply this test methodology to identify the System Deliverability Upgrades, if any, needed to make the Large Facility deliverable at its requested XXXX MW level and will also identify the MW of Installed Capacity, if any, that are deliverable from the Large Facility with no System Deliverability Upgrades. A Large Facility electing XXXX will be able to become a qualified Installed Capacity Supplier or receive Unforced Capacity Deliverability Rights to the extent of its deliverable capacity, once it has funded paid cash or committed to fund provided Security for any required System Deliverability Upgrades in accordance with the relevant provisions of Attachment S HH to the ISO OATT. A Developer An Interconnection Customer qualifying for XXXX will have two XXXX values: one for the summer capability period and one for the winter capability period. The XXXX value, in MW of Installed Capacity, for the summer capability period will be set using the deliverability test methodology and procedures described in Section 25.7 40.13 of this Attachment S to the ISO OATTHH. The XXXX value for the winter capability period, also in MW of Installed Capacity, will be set in accordance with Section 25.7.6 40.13.6 of this Attachment S to the ISO OATTHH.

XXXX Elections. The amount of XXXX requested by a Developer shall be stated in MW of Installed Capacity (“ICAP”), and cannot exceed the nameplate capacity of the Developer’s Large Facility; provided however, (i) if the Large Facility is a BTM:NG Resource, its requested XXXX cannot exceed its Net ICAP; (ii) if the Class Year Project is an Energy Storage Resource, the requested MW level of XXXX cannot exceed the minimum of the following: (a) its maximum sustained four- hour injection capability in MW hours; (b) the nameplate capacity of the facility (i.e., injection capability of the facility expressed in MW); or (c) the sum of the facility’s requested and existing ERIS, as applicable; and (iii) if the Class Year Project is a request for External-to-ROS Deliverability Rights, it can request a MW level of XXXX, not to exceed the increase in transfer capability created by its associated Class Year Transmission Project, as demonstrated in the project’s System Reliability Impact Study. When a Developer elects XXXX, the ISO will evaluate the deliverability of the Large Facility by applying the test methodology described in Section 25.7 of Attachment S to the ISO OATT. The ISO will apply this test methodology to identify the System Deliverability Upgrades, if any, needed to make the Large Facility deliverable and will also identify the MW of Installed Capacity, if any, that are deliverable from the Large Facility with no System Deliverability Upgrades. A Large Facility electing XXXX will be able to become a qualified Installed Capacity Supplier or receive Unforced Capacity Deliverability Rights to the extent of its deliverable capacity, once it has funded or committed to fund any required System Deliverability Upgrades in accordance with the relevant provisions of Attachment S to the ISO OATT. A Developer qualifying for XXXX will have two XXXX values: one for the summer capability period and one for the winter capability period. The XXXX value, in MW of Installed Capacity, for the summer capability period will be set using the deliverability test methodology and procedures described in Section 25.7 of Attachment S to the ISO OATT. The XXXX value for the winter capability period, also in MW of Installed Capacity, will be set in accordance with Section 25.7.6 of Attachment S to the ISO OATT.

XXXX Elections. The amount of XXXX requested by a Developer shall be stated in MW of Installed Capacity (“ICAP”), and cannot exceed the nameplate capacity permissible levels set forth in Section 25.8.1 of Attachment S to the Developer’s Large Facility; provided however, if the Large Facility is a BTM:NG Resource, its requested XXXX cannot exceed its Net ICAPISO OATT. When a Developer elects XXXX, the ISO will evaluate the deliverability of the Large Facility by applying the test methodology described in Section 25.7 of Attachment S to the ISO OATT. The ISO will apply this test methodology to identify the System Deliverability Upgrades, if any, needed to make the Large Facility deliverable at its requested XXXX MW level and will also identify the MW of Installed Capacity, if any, that are deliverable from the Large Facility with no System Deliverability Upgrades. A Large Facility electing XXXX will be able to become a qualified Installed Capacity Supplier or receive Unforced Capacity Deliverability Rights to the extent of its deliverable capacity, once it has funded or committed to fund any required System Deliverability Upgrades in accordance with the relevant provisions of Attachment S to the ISO OATT. A Developer qualifying for XXXX CRIS will have two XXXX values: one for the summer capability period and one for the winter capability period. The XXXX value, in MW of Installed Capacity, for the summer capability period will be set using the deliverability test methodology and procedures described in Section 25.7 of Attachment S to the ISO OATT. The XXXX value for the winter capability period, also in MW of Installed Capacity, will be set in accordance with Section 25.7.6 of Attachment S to the ISO OATT.